Data for DMS/OMS - How much is enough and where to get it

Printer Friendly Format

Page 3 of 5
| Previous | Next |

Data for DMS/OMS - How much is enough and where to get it

Data Development

Conversion Process
Once the level of DMS/OMS data required to meet the desired DMS/OMS functionality is identified, the next step is to begin the conversion process of loading the network connectivity model into the DMS/OMS system. The conversion process is a painstaking and laborious process, the quality of which will ultimately determine the accuracy of DMS/OMS predictive algorithms and outage area calculations. Therefore, following a rigorous conversion methodology is essential to achieve the required DMS/OMS functionality.

The following conversion steps should be followed for populating DMS/OMS:

Develop conversion specification(s): A conversion specification documents all conversion rules necessary to interpret the network sources. The source and conversion rules for each network object and attribute must be identified, default values for each attribute should be identified if data is missing from the source, and priority among sources should be identified if sources are in conflict. If source documents differ among operating companies or districts, a conversion specification must be developed for each unique documentation set.
Develop data scrub procedures: Data scrub procedures are required to clarify, correct, and consolidate all source materials before they are delivered to the conversion team.
Conduct a prototype: A small prototype conversion (one or two feeders) provides a minimum test of the conversion specifications to ensure the rules documented by a few experienced individuals can be interpreted by a larger conversion team. The prototype should adequately test all procedures, including a test of all data loading software and quality assurance (QA) software.
Review prototype and modify conversion specifications: The prototype will demonstrate where changes, additions, and clarifications must be made. Take the time to make the changes. Once the prototype is complete, you are ready to begin full conversion:
Freeze records: As you prepare each subarea district or feeder for conversion, you must formally freeze the source records. As the records are being converted, as-built and asoperated changes will be made in the area. You must be able to identify what has changed after you froze the records.
Perform data scrub: Perform all data cleanup and consolidation tasks identified in your scrub procedures.
Deliver sources to the conversion team: Require the conversion team to document all documents received.
Implement a problem resolution process: No matter how good your sources and conversion specifications are, the conversion team will still have questions throughout conversion. Implement a system to report problems for clarification, track all problem resolution reports, and respond in a timely manner.
Implement QA procedures: Ensure the conversion team is implementing a QA process at key steps in the conversion process that include both manual and automated checks. This process must include reporting procedures to track trends throughout the process.
Implement an independent QA team: Once a delivery is made by the data conversion team, an independent QA assessment using manual and automated checks is essential.
Post frozen records: Once the data is accepted, all changes that occurred after the records were frozen must be posted.

You can deploy DMS/OMS as operating districts are completed.

Typical Data Sources
The following identifies typical data sources for each level of network model:

Model Representation	Typical Data Sources
Graphical representation - schematic or geographic	Schematics, paper maps, CAD drawings, and/or GIS files are the typical sources for the primary network connectivity model. If these sources are not available, field inventory is required.
Secondary network model	Schematics, paper maps, CAD drawings, and/or GIS files are the typical sources for the secondary network connectivity model. If these sources are not available, field inventory is required.
Three-phase connectivity model	Schematics, paper maps, CAD drawings, and/or GIS files are the typical sources for the phasing model. If these sources are not available, field inventory is required.
Model of spans in addition to device connectivity	Paper maps, CAD drawings, and/or GIS files Including facility attribution in the network model Paper maps, CAD drawings, GIS files, databases, spreadsheets, and manual records
Without device internals versus with device internals	Schematics, CAD drawings, GIS files, and manual drawings.
Landbase information	Existing paper maps, CAD drawings, GIS files, new landbase information created from orthophotography, purchased commercial landbase information (ETAK, GDT, etc.), and local government shared/public information.

Conversion Costs
The following factors will impact the cost and time of the project:

Internal team versus external contractor: Internal team may appear to be cheaper. An external contractor can do it faster; therefore benefits can be realized sooner while decreasing the total project cost.
Data quality: Your network data is not as good as you think it is.
Data migration: If you have a functioning network model in a GIS, your data is likely suitable for migration. If you have an automated mapping system, your data may or may not be suitable for migration (see bullet above). Migration is cheaper than manual conversion.
Customer-transformer-network link: Establishing this link is essential for successful
DMS/OMS implementation. Availability and quality of this link will impact cost and duration.