• SEGIS must contain sufficient data and be organized to support application development.
• SEGIS must meet reasonable performance expectations related to specific application requirements.
• SEGIS must be easy to use and the design should minimize complexity of operation.
• SEGIS data redundancy should be minimized.
• SEGIS design must be flexible to allow currently designed applications to change and it must be extensible to facilitate new applications.
• SEGIS must support critical business requirements unique to the nature of electrical utilities business functions.

• 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

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).

• Model Specification
• Model Extraction
• DS/0 and DS/1 Configuration
• Model Interface Delivery and Rollout

• 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.

The Model Processor (.mp) file format is a simple ASCII file format intended to 
support the extraction of data from GIS systems with limited or proprietary export 
formats. The .mp file format is ASCII and is easy to read.

Each .mp file will contain a map sheet definition with the following format:

ADD map_class id {
NAME = map_name;
[COORD_SYSTEM=coord_system;]
[SCALE_FACTOR = scale;]
[diagram]
[attributes]
};

Following to the map sheet definition will be the object definitions until the end of the file.
Object definitions have the following format:

ADD class_name [ index ] {
PORT_A = node_id;
PORT_B = node_id;
[diagram(s)]
[attributes]
};

The PORT_A/B specify the connectivity information about the object and is not included for 
non-connectivity object.

The diagram section(s) for each object can contain the following:

DIAGRAM [diagram_id]
{
[ HEIGHT = height; ]
[ ANGLE = angle; ]
[ SCALE = scale; ]
[ COLOR = color; ]
[ WIDTH = width; ]
[ SYMBOLOGY = symbol_id; ]
[ TEXT = text; ]
[ JUSTIFICATION = LL|CL|UL|LC|CC|UC|LR|CR|UR | ]
[ THICKNESS = thickness;]
GEOMETRY = {
[ ( x_coord1, y_coord1 ),
. . .
( x_coordN, y_coordN ), ]
( x_coord, y_coord );};
};

Here is an example of the first few records of a Savannah Electric SEGIS/.mp file:

ADD partition d_elec.1019 {
NAME = tile1019|
DIAGRAM = {
GEOMETRY =
(882000,876000),
(888000,876000),
(888000,880000),
(882000,880000)|
}|
}|

ADD d_elec.XFRSNG 5557000000157971 {
PORT_A=|
DIAGRAM = {
ANGLE = 349.5085144043|
SCALE = 100|
SYMBOLOGY = 129|
GEOMETRY =
(882968.3032836,876332.0569578)|
}|

DIAGRAM = {
HEIGHT = 10|
JUSTIFICATION = LU|
TEXT = "10B-9379"|
GEOMETRY =
(882999.5385847,876326.2535151),
(883019.1385847,876326.2535151)|
}|

ATTRIBUTE="5557000000157971"|
ATTRIBUTE="XFRSNG"|
ATTRIBUTE="1302702"|
ATTRIBUTE="000157971"|
ATTRIBUTE="N"|
JOIN = {
ATTRIBUTE="5557000000158059"|
ATTRIBUTE="5557000000157971"|
ATTRIBUTE="10.0"|
ATTRIBUTE="B"|
ATTRIBUTE="-9379"|
}|
}|

ADD d_elec.Ckt 5557000000157479 {
PORT_A=|
PORT_B=|
DIAGRAM = {
GEOMETRY =
(880377.0031308,876681.9670278),
(881573.0142294,876590.4437362),
(882968.3032836,876332.0569578)|
}|

DIAGRAM = {
HEIGHT = 10|
JUSTIFICATION = LC|
TEXT = "1-4ACSR"|
GEOMETRY =
(882647.9021725,876391.5126072),
(882667.2044044,876388.1091029)|
}|

ATTRIBUTE="5557000000157479"|
ATTRIBUTE="13P1"|
ATTRIBUTE="1302702"|
ATTRIBUTE="N"|
ATTRIBUTE="1"|
ATTRIBUTE="4"|
ATTRIBUTE="ACSR"|
ATTRIBUTE="N"|
ATTRIBUTE="2619"|
ATTRIBUTE="13.2KV"|
ATTRIBUTE="7.62KV"|
ATTRIBUTE="O"|
ATTRIBUTE="B"|
}|

1. Populate the customer information into the OMS system, and
2. To exchange information about customer calls from the CSS, and
3. To cxchange information about trouble grouping, status, and restoration from the OMS.