Logo GISdevelopment.net

GISdevelopment > Proceedings > GITA > 2000


GITA 2002 | GITA 2001 | GITA 2000 | GITA 1999 | GITA 1998 | GITA 1997 |  
Sessions

Data development and evolution

Engineering and design applications

Exploiting field and mobile technologies

Invited presentations

It's a brave new world

Leveraging web-based technologies

Mobilizing the enterprise

Operations support

People issues

System architecture

The best of the rest

Uniting the enterprise

User perspectives

Work management solutions



GITA 2000


Operations Support


Savannah electric - Fast track OMS implementation from a mature GIS


Starting the savannah electric OMS project
Savannah Electric had the desire to implement a new OMS in a short period of time. The plan was to implement, rollout, and gain the benefits of a graphical OMS in less than one year. The primary reason for the speedy implementation path was because our previous OMS was not millennium compliant, and resided on a mainframe that was not millennium compliant and which Savannah Electric did not wish to continue to use.

Savannah Electric had two significant relationships to draw on to support a quick implementation. First, two of its sister utilities had been working on an OMS implementation for an extended period of time. Much of the base functionality and required interfaces were either designed or implemented. Second, the selected OMS vendor had a functionally rich system and a growing installed customer base.

Major milestones to the Savannah Electric OMS implementation included:
  • GIS Interface Implementation and GIS/OMS Model Clean Up and True Up
  • OMS User Environment Implementation
  • Customer Information Systems Integration
  • User Training and preparation for Production
  • On Line Production
The GIS to OMS interface
The GIS information is fundamental to the OMS. The GIS is the source for
  1. The geographic presentation of information,
  2. The facility model including object definition and connectivity, and
  3. The integration information for other systems including the customer information system (CSS).
The GIS is the maintenance source for this information. The OMS depends on the GIS for this information. After initially loading this information into the OMS, the information must be incrementally imported into the online OMS as the GIS is updated. This is called the Model Build process.

The implementation of this interface included four major efforts:
  • Model Specification
  • Model Extraction
  • DS/0 and DS/1 Configuration
  • Model Interface Delivery and Rollout
Model Specification
The model specification process was a learning experience for both the Savannah Electric staff and the OMS members of the model interface project team. The following steps were followed to develop the model interface specification:
  • Establish an understanding of the base OMS operations model and its user environments
  • Compile a set of specifications on Savannah Electric information sources (SEGIS, CSS)
  • Merge the standard OMS operations model structure and the Savannah Electric information sources into a Savannah Electric specific operations model supporting the needs of the operation staff.
  • Generate an interface specification to support the building and maintaining of an OMS operations model.
It should be obvious that to make this process successful, four groups of people had to be involved: the OMS implementation engineers, customer information source application programmers, GIS application programmers, and operations staff.

To gain a good understanding of the OMS operations model and its user environments, the model interface team had access to demonstration systems, formal OMS training courses, and OMS staff.

Compiling a set of specifications on the SEGIS and CSS systems was easy. Both systems had been fully documented.

The next stage of the process required merging the CES operations model and the customer information sources into a project operations model. Alabama Power and Gulf Power had already done much of this work, so Savannah Electric just needed to fine-tune it for it's specific work practices. Much of the symbology work had also been standardized, but some fine-tuning for scale differences was required.

Upon completion of the above three activities, the interface team documented the interface specification. Once the model interface specification was complete, the formal model interface configuration commenced.

Page 2 of 5
| Previous | Next |

Applications | Technology | Policy | History | News | Tenders | Events | Interviews | Career | Companies | Country Pages | Books | Publications | Education | Glossary | Tutorials | Downloads | Site Map | Subscribe | GIS@development Magazine | Updates | Guest Book