Gallup_Database_Conversion_SOW_KTmn2.092525_(1).pdf

STATEMENT OF WORK

DATABASE CONVERSION

Prepared for Milsoft customer:

City of Gallup Attn: Riley Crain

Utilities Department

230 S. Second St.

Gallup, NM 87301

TABLE OF CONTENTS

Introduction/Background

Scope of Work

Place of Performance

Data Sources

Data Destination

Conversion Process

Customer Deliverables

Milsoft Deliverables

Installation

Post Installation Customer data review and clean-up

Database Acceptance Criteria

Change Orders

Attachment A: Customer data required to complete Milsoft E&O Model

Introduction/Background

Gallup Joint Utilities Department, City of Gallup (hereafter referred to as “Customer”) has engaged Milsoft Utility Solutions (hereafter referred to as “Milsoft”) to convert data from [ESRI to a format that is compatible with the Milsoft’s Engineering and Operations (E&O) Model. The database conversion process is interdependent between Customer and Milsoft and will require several review iterations.

Scope of Work

The scope of work is limited to electrical circuit elements and map points recognized by Milsoft’s

E&O software. Corrections or modification to the source data will be the responsibility of

Customer and will not be included in Milsoft’s scope of work.

-Convert your existing GIS data into a Milsoft WindMil model.

-Migrate the work orders currently in ESRI into WindMil.

-Confirm phasing reflected from the existing model.

-Ensure the model is in the best possible condition for system analysis in WindMil.

-Establish the framework for ongoing maintenance using WindMil Map and Milsoft FieldSyte

Staking.

-Enforce best practices moving forward to maintain data integrity and model reliability.

Place of Performance

Milsoft will perform work at one or more of the following places:

• Abilene, Texas

• Pensacola, Florida

• Bowling Green, Missouri

• Customer’s site, or Employee’s Remote

Data Sources

• Customer-supplied data sets correlated to Attachment A

• Supplemental data outside Customer data set in compliance with Attachment A

Data Destination

• Milsoft E&O Model (FairCom)

• Milsoft Data Set/Internal Tables (MS SQL)

Conversion Process

During the conversion process, Milsoft will expect Customer to provide prompt (typically within two business days) and detailed reviews of mapped and converted data. Milsoft cannot provide any missing data or independently identify/fix latent data errors. Engineering assumptions (e.g.

snapping transformers and lines to poles based on proximity) will be used to create data.

However, assumptions are not guaranteed to be engineering-accurate.

1. Milsoft will provide connection details to a secure FTP site to be used in the exchange of

Customer data files. Connection details for the FTP will be communicated to Customer prior to the kick-off call.

2. Milsoft will initiate and conduct a database conversion project kick-off call with Customer team to discuss and identify:

a. Required Interfaces (e.g. Billing, AMI, Staking …)

b. Grid Requirements

c. Coordinate System

d. Workflow

e. Data Sources and Request Data

f. Project Contacts

3. If Customer wishes to use grid-based naming within the Milsoft E&O Model, a schema must be provided by Customer supplying unique element names which can be programmatically defined within the Milsoft E&O Model. The grid-based naming may be used for all electrical elements within the Milsoft E&O Model. Customer is responsible for all renaming of elements within Customer’s model and database.

4. Customer will be provided an evaluation of Customer’s electric model including overall accuracy (Gap Analysis). Missing or inaccurate information will be detailed so Customer can update the source data.

5. Database conversion will be limited to data from Customer’s data sources selected by Milsoft. Milsoft will create data mappings based on Customer’s data and

Milsoft’s standardized file structure. In the event that the element data required for a connectivity model is not provided, Milsoft will insert the elements without electrical connectivity. Customer is responsible for data cleanup not provided in source data.

6. The transmission portion of the electric model, if contracted by Customer, can be included in the conversion; however, transmission will be isolated/disconnected from the distribution network model to optimize outage predictions.

7. Milsoft supports Center Tap transformer modeling; however, not all 3rd party software systems recognize Xn phasing. If Customer requires Center Tap transformer modeling in

WindMil/EA and standard phasing for Outage Management or Staking, Milsoft recommends the model be delivered in standard phasing (A/B/C). Altering existing single-phase transformers to Center Tap is relatively easy using WindMil tools prior to running analysis. Typically, two and three phase Power & Light transformer banks require engineering assumptions because the source data doesn’t identify which transformer is center tapped. The Customer has the ability to store Center Tap information in the transformer unit table (external SQL table) even when only standard phasing is selected.

8. After initial conversion, Milsoft will conduct an evaluation of Customer’s electric model and provide a report assessing the overall accuracy. The report will detail missing or inaccurate information. It is Customer’s responsibility to update source data.

Milsoft will provide Customer with ongoing analysis of the data quality throughout the conversion process, and will work with Customer to address any issues.

CUSTOMER DELIVERABLES

1. Customer will provide a defined detailed list of data requested by Milsoft, and linking information for Internal Tables in their database by:

a. Collectively determining how equipment not presently modeled by Milsoft will be handled to include underground switchgear, feed-thru cabinets, pad-mounted transformers, and open-points.

b. Defining:

i. Naming conventions

ii. Unique identifiers required to link devices in the Milsoft E&O Model to Internal data

iii. Attributes to use for the Milsoft E&O Model’s equipment device definitions (EQDB)

2. Customer will provide the current data source to be used for the conversion and attribute data associated with the model elements to be used with Milsoft Internal

Tables prior to the start of the conversion project.

3. Customer must establish a cut-off date for posting changes to the source data prior to the final conversion and the transition to the Milsoft E&O Model.

Customer will make corrections to the source data requested by Milsoft as errors and/or inconsistencies surface during the joint reviews of the Milsoft E&O Model generated by the database conversion. Corrections will be completed and returned to Milsoft within two (2) business days to prevent software installation delays for Customer. Customer may elect to forego some corrections at their discretion if the corrections cannot be made in a timely manner prior to the cut-off date.

MILSOFT DELIVERABLES

1. Milsoft will deliver a completed Milsoft E&O Model and attribute data associated with the model elements in the form of Milsoft Internal Tables (MS SQL). This delivery is contingent upon the timely participation and prompt responses of Customer throughout the data conversion work.

2. Upon request, a virtual machine will be hosted for Customer to facilitate the review of their converted data using Milsoft’s WindMil software. If Customer is not familiar with WindMil, basic training can be obtained by contacting Milsoft.

3. Milsoft will convert Customer data using proprietary coding and conducting detailed quality assurance reviews of the Milsoft E&O Model and data provided from the data conversion.

4. Milsoft will initiate joint reviews of the Milsoft E&O Model throughout the conversion process.

a. Programmatic changes to correct issues discovered during joint reviews will be completed by Milsoft.

b. Customer and Milsoft will evaluate progress toward a final conversion and cut-off date after the second data review.

c. All third-party updates must be posted prior to the cut-off date.

INSTALLATION

Milsoft will install the Milsoft E&O Model on Customer’s system following the review of the final conversion.

POST INSTALLATION CUSTOMER DATA REVIEW AND CLEAN-UP

Customer will receive Milsoft Standardized Tables and “External Tables” (MS SQL) with the completed data conversion. Only source tables relevant to the conversion will be stored in the

Milsoft Standardized Tables. The “External Tables” typically contain fields that have a great deal of redundant and legacy data that could unnecessarily inhibit the performance of the software;

therefore, Milsoft will leave “external tables” turned off upon delivery, to optimize performance of the system while retaining the legacy data Customer might need for other purposes.

If Customer wishes to link the “external tables,” Customer is advised to use SQL Server to review the database and delete data fields that are redundant or no longer required. Depending on the amount of extraneous data contained within the original database, this can be a significant task, but failure to review and delete legacy “external tables” SQL data fields can cause sluggish performance of Milsoft products.

Wholesale deletion of the “external tables” database is an option, as it is provided as an archive of the data Milsoft received. Such deletion is only recommended once Customer is certain they have no need for this archived data.

Database Acceptance Criteria

Acceptance of the database conversion will occur when Customer has reviewed the conversion and found no significant errors within Milsoft’s scope of work.

Change Orders

Any modification to this Statement of Work must be requested by one party’s Project Manager

(PM) to the other party’s PM, reviewed, and agreed to by both parties. Any proposed Change

Order will be drafed by Milsoft and submitted for Customer review and approval. Such changes may result in required adjustment of the project deadlines or additional fees; any change that requires an increase in cost should be coordinated through the RAM and Customer. Once signed by Milsoft’s CEO of Business Operations and Customer’s authorized representative, the Change

Order will become effective.

Statement of Work Acceptance/Authorization

MILSOFT UTILITY SOLUTIONS, INC. GALLUP JOINT UTILITIES,

CITY OF GALLUP

By: __________________________ By: __________________________ Signature Signature

Adam Turner __________________ _____________________________

Printed Name Printed Name

CEO of Business Operations ______ _____________________________

Title Title

Date Date

Project Acceptance by Customer upon Completion

By: __________________________ Signature of Customer Representative

Printed Name & Title

Date

Attachment A:

Customer data required to complete Milsoft E&O Model.

Customers Coordinate System and Projection (WGS-84) to be used

Customers Location Data for each element

The Parent and Child data (Up-line & Down-line) information for all model elements

Equipment Database (eqdb) (if current WindMil customer)

Elements

Each data element must be identified. Elements are required to have a unique name, type and include attribute data listed in this attachment.

1. Overhead

a. Unique Name (ID) include preferred prefixes to distinguish OHP, OHS

b. Phase Data

c. Conductor Definitions (both phase and neutral conductors)

d. Impedance Length

2. Underground

a. Unique Name (ID) include preferred prefixes to distinguish UGP, UGS

b. Phase Data

c. Conductor Definitions (phase conductor, if neutral is concentric, or tape shield)

d. Impedance Length

3. Regulator

a. Unique Name (ID) include preferred prefix

b. Phase Data (phase of the bank, include the controlling phase where applicable)

c. Regulator Size (in kva or amps/designate equipment definition)

d. Voltage Level

e. LD Comp R&X (preferred)

f. First House High & Low (preferred)

4. Transformer

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. Winding Connections

d. Transformer Equipment/Impedance Definition

e. Rated L-L Input Voltage

f. Rated L-L Output Voltage

g. Nominal of Output System

h. Overhead, Step, or Pad Mounted? – Transclosures will be typed as Pad-Mounted. If identified in the data, they can be given unit tables in the External Data Tables

i. kva data

j. input/output voltage data (preferably line-to-line)

5. Switch

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. Switch Status (open/closed/looped)

d. Switch ID (optional)

e. Open Points can be modeled as switches, or nodes, if data supports this. This will require a unique prefix (OP)

6. Source

a. Unique Name (ID)

b. Phase Order (?) Data (position of lines leaving substation)

c. Impedance Code Minimum (often this is the substation number and name)

d. Impedance Code Maximum(often this is the substation number and name)

e. Sub Number (optional)

f. Bus Voltage

g. Overhead Ground Ohms

h. Underground Ground Ohms

i. Nominal L-G

j. Nominal L-L

k. Connection (wye/delta)

l. Regulation (yes or no)

7. Generator

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. Generator Model

d. Total Generator kVA

e. PU Volts

f. Output (kW)

g. Maximum Leading Output (kvar)

h. Maximum Lagging Output (kvar)

i. Connection (wye/delta)

8. Motor

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. Motor Mode (example: horse power)

d. Total Motor HP

e. Rated LG Volts

f. Rated LL Volts

g. Load in kW

h. Load in kVAR

i. Motor Status (off/on)

j. Locked Rotor

k. Soft Start (if applicable)

9. Device

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. Device Code (example: 3-phase operation)

d. Device Status (phase open/closed)

e. If Feeder Device (require feeder number/feeder alias)

f. Device Equipment Definitions

g. Current and Link Ratings, Device Type data

10. Capacitor

a. Unique Name (ID) include preferred prefix

b. Phase Data

c. How Capacitor Bank Connected (series/shunt)

d. Capacitor Connection (same as parent/wye/delta)

e. Capacitor kVAR Rating (total/phase)

11. Consumer

a. Unique Name (ID) unique tie between model and CIS

b. Phase Data

c. Active (yes/no)

d. Consumer Type (example: residential/small commercial/traffic light)

e. Meter Number

12. Map Points and Assemblies (requires all domain values and codes necessary for identifying the proper categories noted below)

a. Assembly Label/Code

b. Parent Type

i. Pole

ii. Junction Box

iii. Tower

iv. Pad

v. Pedestal

vi. Enclosure

vii. Vault

viii. Pull Box

ix. Marker

x. Light

xi. Surface Structure

xii. Foreign Structure

xiii. Storage Location

xiv. Non-Utility Facility

c. Quantity

13. The foregoing list contains data elements and attributes Milsoft typically requires to build an E&O Model. If the data supplied does not contain all information needed, Milsoft will request missing data from Customer. If Customer does not have all data required, Milsoft will work with Customer to establish default values where possible. Milsoft reserves the right to define what data is needed to create the Milsoft E&O Model and External Tables.

Potential Data Sources

The list of potential data sources is will be tailored to each Customer. This list is typical of

ESRI based GIS users:

1. ESRI Personal Geodatabase (.mdb) without class extensions

2. Billing Export, (.csv) format is preferred, with column headers

3. If using ArcSDE please provide a SQL back up file (.bak)

4. ESRI Domains and Coded Values

5. Any substation 1-line drawings that show substation regulators/transformers/reclosers, etc

6. Copy of the Engineer's WindMil model and corresponding equipment database

(eqdb) (if available)

7. Shape Files of Landbase (roads, water ways, board districts, etc...)

8. Shape File of Grid used for Grid-based naming, along with the format of the Grid naming

9. List of switchgear, including Manufacturer, Type (Box/Retangular) and

Configuration (Example: S&C PME-9)

10. Percent Impedance, X/R, and NL Losses values for transformers (typically from the Engineer)

11. Substation impedance information (positive/negative/zero sequence values)

12. Line Reclosers and Sectionalizers information (Manufacturer/Current

Rating/Type) if not contained within the GIS database

14. Export of CIS Transformer database in (.csv) format with column headers

15. Any additional notes, data, etc. that are pertinent to the final converted model, but not contained within the GIS database.