Oracle Utilities Network Management System– Schematics can automatically generate orthogonal schematic overviews of the nominal network.

In order to use Oracle Utilities Network Management System Schematics, the following is required of the data model:

Since Oracle Utilities Network Management System Schematics uses a splayed-tree representation of the nominal network, it is necessarily geared towards radial networks and will have difficulty representing nominally looped, parallel or meshed areas. Oracle Utilities Network Management System Schematics is also geared towards simple network objects (for example, a switch) and cannot keep related devices in close proximity (for example, the internals of a switching cabinet).

All schematic configuration is done through Configuration Assistant's Schematica Options Tab and the configured options are stored in a database table called schematic_options. Default options are populated by [project]-schematica.sql file. The script that contains the configuration of the default option packages to be executed is called [project]-create-schematics.

The script performs these three actions:

The schematic generation is triggered from the Configuration Assistant by passing the option package and selected maps that invokes a script called nms-schematics, which in turn invokes schematic-generator (schematica) where all the options of the selected option package are queried from the table and executed. See "Using the Schematica Options Tab" section in the Oracle Utilities Network Management System User's Guide Configuration Assistant chapter for more information.

Script nms-schematics can also be run through command line by passing the arguments ‑schoption, option package and the -maps, the list of schematic map filenames (excluding file extension) that should be rebuilt, with spaces between the map names. Only these maps will be rebuilt. If -maps is not provided then the schematic generation applies to all the maps by default.

The following table describes all of the options that can be configured through Schematica Options tab, organized categorically.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The following figure shows the deviceHeight, branchWidth, and feederOffset.

 

The following figure shows substationBoxSize, feederHeight, tierHeight, and connectionClass.

 

 

The following figure shows a feeder-to-feeder connection.

 

Populate the new schematic_symb_class database table with any symbology state classes you wish to use in the auto-generated schematic maps. Use this if you want devices or conductors to appear different in the schematic maps than they do in the nightly build maps.

Note that this is non-product configuration; product does not add any schematic-specific symbology state classes to this table.

To create schematics, the customer-specific script [project]‑postbuild must have a call to [project]‑create‑schematics.

After the build process has processed the final map, it calls nms‑postbuild. If there is a [project]‑postbuild script, nms‑postbuild will call it. If there is an entry for create-schematics, it calls it at this time.

Once invoked, the schematic generator loads in the entire nominal network model and attempts to group all feeders with their parent substations. After it finishes determining the layout and spacing for all feeders and substations, it writes out one import file for each substation.

After the schematic-generator creates the import files, the schematic script compares the most recent previous version of each file. If no changes are detected, it skips the map. Otherwise it proceeds to build the import file as per the normal model-build process.