The following sections describe some recommended guidelines to follow when you integrate Oracle Utilities Network Management System with a GIS.

The GIS extractor utilized should either be supported by Oracle or by one of our modeling partners. The extractor should produce Oracle standard model preprocessor (MP) files and utilize the Oracle conventions for model building and an approved incremental update process.

The Oracle Utilities Network Management System standard preprocessor supports eighteen different rules that allow for data translation (for instance, expand elbows, or add recloser bypass switch). It is acceptable to use as many of these rules as necessary to build an acceptable operations model. The standard preprocessor takes as input model preprocessor (MP) files and produces Oracle standard model build (MB) files - generally on a feeder or substation basis but possibly on a geographic tile basis.

Select which device types (classes) are used from the standard model definition, mapping the customer's GIS data to these existing classes.

There are a number of NMS software configuration aspects that depend upon the device types that are chosen to be built within the NMS data model. In so far as the data model can change for different facilities, the software configuration must be adapted. The following configuration settings are dependent upon the resulting NMS model definition and require adaptation for every project. These configurations are generated automatically by Oracle to match the defined NMS model.