Export subnetwork information

A subnetwork represents a topological subpart within a tier where all the connected features are defined by the same subnetwork controller or controllers. The maintenance of subnetwork information is optimized by exporting subnetwork information to external systems for modeling and analysis.

Export subnetworks

The Export Subnetwork tool is used to export information about a subnetwork to a .json file. That information can then be used by outside systems such as outage management and asset tracking programs.

Information about a subnetwork that is exported includes information about the features, their connectivity and association information, and the the controllers that define the subnetwork. Information in the output .json file can be used to build a topology locally to perform analytics, or for sharing with external systems to help manage assets and operations.

The Features result types option and Include propagated values parameter can be used to return propagated values on demand during the export without the need to perform an update subnetwork operation. You can also use the export subnetwork operation to delete a subnetwork that is marked as deleted in the Subnetworks table using the Set export acknowledged parameter.

See Export subnetworks for more information.

Export subnetwork controller information

You can export subnetwork controllers that define subnetworks using the Export Subnetwork Controllers geoprocessing tool. Information about each subnetwork controller is extracted to a .csv file from the Subnetworks table. The subnetwork controllers can be imported back into another utility network as long as the specific device features that are referenced in the .csv file exist.

See Export subnetwork controllers for more information.