Smart Grid (ArcGIS) (5-50)

What is a utility network?

A utility network is the main component users work with when managing utility and telecom networks in ArcGIS, providing a comprehensive framework of functionality for the modeling of utility systems such as electric, gas, water, stormwater, wastewater, and telecommunications. It is designed to model all of the components that make up your systems—such as wires, pipes, valves, zones, devices, and circuits—and allows you to build real-world behavior into the network features you model.

With a utility network, you can do the following:

• Create and edit features and objects that model every type of utility equipment.
• Discover how features and objects in the network are connected.
• Trace how resources, such as gas, water, and electricity, flow through the network.
• Provide an operational view of how all the dynamic devices of your utility are currently configured.
• Analyze how the network is affected by real-world events such as storms, outages, or equipment failure.

The utility network can be accessed with either an enterprise or single-user deployment:

• An?enterprise deployment?provides the richest capabilities of the utility network through a services-based architecture using?ArcGIS Enterprise. This model enables large-scale, multiuser deployments and full network display, editing, and analysis capabilities through web maps and apps, mobile apps, and?ArcGIS Pro?on the desktop.
• A?single-user deployment?provides the full analytic capability of the utility network while hosted on a file or mobile geodatabase. In this model, you interact with the utility network through?ArcGIS Pro?on the desktop or mobile device.

Visualize your network

A utility network offers a number of ways to view your network system and assets:

• View thematic cartographic maps for different use cases, such as customer service, field collection, and inspection, or distribution management.
• Create network diagrams that allow you to readily check network connectivity and create logical views of your network in a more simplified, symbolic representation of the information.
• View inside complex assemblies of devices and lines and manage how assets are connected within them.
• Visualize a selected pressure zone or circuit with a display filter.

Analyze your network

The utility network provides an array of analysis and tracing tools to support a large variety of analytic workflows:

• Perform inspection of the network in the aftermath of an event such as a severe storm.
• Determine the number of customers with access to your resource. For example, you can create a load summary report to present the number of customers being supplied by a specific circuit in an electric network.
• Trace network features upstream or downstream from a given location. For example, water utilities can determine which valves to shut off when a pipe bursts.
• Model multiple utility systems within one utility network and run tracing analysis across all of them. For example, an outage from an electrical network can affect the delivery of another resource, such as gas or water. You can run a trace across all systems involved, see where the problems lie and decide on the best course of action.

Edit your network

You can edit a utility network with core?ArcGIS Pro?functionality to streamline your editing workflows:

• Use templates to create collections of related utility assets with a single click, such as creating a power pole with transformers already attached.
• An?enterprise deployment?allows multiple users to edit and manage network features concurrently using a services-based architecture.
• Editing rules and validation in the network ensure data quality by preventing the entry of logically invalid data and associations. For example, a reducer must be connected to pipes of the correct diameter on either end.

Benefits of a utility network

A utility network supports the requirements of utilities in delivering resources to customers safely, reliably, and economically. It can serve as the system of record for the assets of a utility and provide information about the past, present, and planned future state of a utility network system. A utility network is available where it is needed, from mobile devices in the field to the desktop in operation centers.

Work with a high-performing model that is scalable to large utilities

A utility network is designed for quick information delivery with large datasets. The core data models are engineered for maximum efficiency by limiting the number of feature classes and reducing slow relationship queries. The classification system uses attribute domains and subtypes and is built-in for each of the utility network feature classes. This allows for a fine-grained model of every utility feature. A utility network is engineered to rapidly traverse network features that are connected or attached to structural features.

Model how components of your system are connected

The connectivity model allows a utility to define exactly how each part of a utility system is connected. You can connect features that touch each other and you can connect features that are offset from one another. This allows you to place utility features on the map in a natural way and spread them as needed for clarity. You have full control over how your utility features are connected.

Represent dense areas of your system without map clutter

Parts of a utility are quite dense. A station or yard or cabinet may be a compact size but contain dozens or hundreds of utility features. Representing these dense areas on a map creates a cluttered and difficult-to-use map representation. The containment model lets you represent these dense areas with simplified containment features. Containment features can also model assemblies of features such as a cluster of electrical devices on a pole top or inside a cabinet or vault. When necessary, you can switch on and off features that are contained and see exactly how the internal features are laid out and connected.

Model significant components of your system

All significant parts of your network can be modeled in the utility network. Some features (such as electrical fuses or small water valves) may be considered minor but do affect the flow of resources in a utility system. All utility features, major and minor, can be represented in a data model and contained in device assemblies as necessary. The scalability of a utility network enables a more detailed model of every part of your utility, from small but critical components to large assemblies of devices.

Enforce data integrity and reduce data entry errors

A utility network has a built-in mechanism to detect any logically inconsistent associations among features. This is done by a user-defined network rule base that specifies exactly which type of feature can be connected and associated with another. For example, a medium-voltage transformer cannot be connected to a high-voltage line. The network rule base for the utility network is integrated into the editing environment to prevent the creation of incorrect connectivity and associations between features. New features and associations are also tracked with dirty areas to mark the area that needs to be updated in the network topology. If attribute values are modified for existing features that impact the network topology, these features are flagged by dirty areas. During validation of the network topology, the utility network updates the network topology in the dirty areas and checks for invalid features. These features are highlighted in the map display with?error features?(point, line, and polygon error features).

Enable advanced analysis of your network

A utility network is a collection of subnetworks through which a resource flows at a given time. These subnetworks are dynamic and can be altered by the opening and closing of devices such as switches and valves. A utility network uses the sources of the resource to define the start points of a subnetwork and traces down to the ends (or sinks) of a subnetwork to discover its entire extent. When a switch or valve is changed, the extent of a subnetwork is recalculated. Categories are also defined on devices to enable more advanced tracing analysis, such as setting which devices are protected in case of a condition such as overloading current or excessive pressure that can potentially threaten the subnetwork.

Provide a comprehensive view of your network

Your utility system is complex and dynamic. A utility network provides a variety of ways to explore the assets and connectivity of your system. The map view shows the overall picture of your utility, and you can set the layer visibility to show progressively more features as you zoom in to the map. In the map view, you can control the amount of detail visible by showing or hiding features inside containers such as stations, yards, cabinets, and vaults. The diagram view shows a schematic representation of your utility features.

A Quick Tour of a Utility Network

ArcGIS Pro?has a variety of utility network tools to help you create, configure, and work with your utility network system. You can access utility network tools and commands, network properties, and dirty areas through the utility network layer.

Create and configure the utility network

Before creating and configuring a utility network, it is important to understand the differences in deployment types and options for configuration. The geodatabase type that stores the utility network will determine the type of deployment, or vice versa. This will impact the configuration, sharing, and licensing of the utility network.

You can create and configure a utility network manually by using core tools or using the?Utility Network Package Tools?to automate the process.

After the initial implementation, you can use these same tools to modify the configuration based on changes in the data model.

Utility network dataset and layer

When a utility network is created, a utility network dataset is generated with the name specified. This name represents part of the fully qualified name for the utility network when viewed in the?Catalog?pane.

When added to an active map, the layer provides access to the?Utility Network Data?tab,?network properties, and?dirty areas. The layer name shown in the?Contents?pane is the utility network name + Utility Network. For example, EsriCoOp Utility Network.

Utility Network Data tab

Under the?Utility Network?tab, the?Data?tab becomes available when you add a utility network to a map. This tab contains tools and commands that are most commonly used in utility network workflows.

There are a variety of tools and commands under the?Utility Network?tab, and on the?Data, tab that allows you to work with the network topology, associations, tracing, and network diagrams, and perform subnetwork management tasks.

The?Data?tab includes commands to create new network diagrams, find existing diagrams, and overwrite or append features to opened diagrams. The more specific network diagrams, commands, and tools are grouped on the?Network Diagram?tab. This is a contextual tab that becomes available when you create a new diagram or open an existing diagram.

Utility Network toolbox

The?Utility Network toolbox?contains a number of tools that can be used to create and manage the utility network for individual use, modeling, and scripting purposes. These tools can be accessed via the?Analysis?tab in the?Geoprocessing?group. Some of the same operations available using the geoprocessing tools can also be accessed from the?Utility Network Data?and?Network Diagram?tabs as described previously.

Utility network vocabulary

Essential utility network terms are listed along with their descriptions.

Analytics

Analytics is the process of analyzing the utility network data to perform inspections of the network (utility network traces) and schematically represent the whole or parts of the utility network (network diagrams).

Asset group

The asset group attribute represents the major classification of utility network classes. The?ASSET GROUP?field is part of the schema for all classes in the structure network and domain network, with the exception of the SubnetLine class. It is also defined as the subtype field. Subtype values are configured to define the major classification of your assets. Further classification of assets is accomplished by assigning attribute domains at the subtype level on the?ASSET TYPE?field.

Asset type

The asset type attribute represents the minor classification of utility network classes. This allows further classification for each asset group. The?ASSET TYPE?field is part of the schema for all classes in the structure and domain network, with the exception of the SubnetLine class. To extend the classification of assets, attribute domains are assigned on the?ASSETTYPE?field at the subtype level (asset group) for each network class. This allows for a rich classification of network features using the asset group as a major classification and asset type as a minor classification..

Associations

Associations enable the modeling of connectivity, containment, and structural attachment between nonspatial and non-coincident network features.

Connectivity

You can connect network features in a utility network to each other in two basic ways:

• Either with a shared endpoint, vertex, or point (common x-, y-, and z-values) or
• With a defined connectivity association between two features or objects that are not spatially coincident. This is called connectivity.

Example

A pump placed at the end of a water pipe will have connectivity established because of the shared location.

Complex edge

A complex edge allows resources to enter one end of the edge and exit the other end. They also allow resources to flow in or out along the edge without the need to physically split the edge. This behavior is supported by complex edges because they allow?midspan connectivity.

Connectivity association

Junction-junction connectivity associations are used to establish a relationship between two point features or junction objects. Junction-junction connectivity associations also support connectivity between?terminals?on features. You can define connectivity associations for point feature classes and junction object tables in the domain network and structure network as long as network rules exist to support the association. Two-point features, such as a transformer and fuse, that are not coincident can be offset from each other by x and y or z while connectivity is maintained through a connectivity association.

Container

A container represents an assembly of network features that are normally referenced as a single feature on a map. For example, an electrical switchgear container feature contains internal switches, fuses, and a busbar, which are important for tracing analysis, but a map showing all these internal features would be too dense. You can connect network features or objects inside a container to features or objects outside a container.

Example

Electrical substations and pumping stations are examples of container features.

Containment edit mode

Containment edit mode is enabled using the?Enter Containment?command in the?Association's?group on the?Data?tab on the?Utility Network?tab. In this mode, creating features that have a supporting rule are automatically added to the active container as content. Editing in containment edit mode shows what network features are inside the active container and how they are connected. Analysis results are also shown inside the container view.

Example

While editing an assembly of features, you will usually enter containment edit mode. New features that are created are automatically added as content for the assembly.

Containment associations

Containment allows a dense collection of features to be represented by a single feature. For example, devices, wires, and conductors can be placed inside of features such as substations, switch gears, trenches, and ducts. Content features can be shown or hidden in the map view to improve visibility and reduce map clutter. Features that contain other features are called a container and the features being contained are called content.

Database utility network owner

When working with a utility network stored in an enterprise geodatabase, there are two owners for a utility network dataset: the database owner and the?portal owner.

The database utility network owner is determined by the database user used in the data source when a utility network is created. You must access the utility network as the database utility network owner for configuration and publishing tasks.

Diagram view

The diagram view shows a schematic view of your network. A diagram is a symbolic representation of features in a utility network with an applied visualization technique. Diagrams can also show the results of a tracing analysis.

Example

At an electric utility, one type of diagram view is called a one-line diagram.

Directionality

Directionality defines how resources flow through terminals on a feature. All terminal configurations require directionality to be defined as directional or bidirectional. A directional terminal configuration indicates that the network commodity can travel only one way through a device or junction object. A bidirectional terminal configuration indicates that the network commodity can travel in either direction through the Device or JunctionObject; there are no distinct upstream or downstream terminals.

Dirty areas

Dirty areas?mark modified features in a map that are out of date in the network topology. Dirty areas are used as visual cues to show the areas that must be validated to maintain the network topology. Dirty areas are cleared when the network topology is validated.

Example

A new medium-voltage line is constructed on the map, and a new dirty area is created that is visible around this feature.

Disjoint subnetwork

If subnetwork controllers that share the same subnetwork name cannot be traversed to one another, the subnetwork is considered disjoint. For tiers in a partitioned domain network, the?Set Subnetwork Definition?geoprocessing tool includes a?Support Disjoint Subnetworks?option. The default is to not support disjoint subnetworks for partitioned domain networks. Tiers in a hierarchical domain network always have this option to support disjoint subnetworks set as true. You can view this property of the tier using the?Network Properties?tab?of the utility network properties.

Domain network

When you create a utility network, you add one or more domain networks to it. A?domain network?is an industry-specific collection of feature classes and tables such as electric distribution or gas transmission. Sometimes a utility network will have two domain networks at the transmission level and distribution level. A utility network can also have crossing domain networks, such as gas and water if they are both managed by that utility.

Example

An electric, gas, or water utility may have two domain networks for modeling the delivery of its resource: transmission and distribution.

Edge elements

The utility network comprises a logical network of junction and edge elements. Edge elements compose the logical component of edge (or line) features in a utility network. A?complex edge?feature is associated with a set of junction and edge elements in the logical network.

Example

A water main represented by a single line feature may be composed of multiple edge elements separated by taps for service lines. In the example below, the addition of a junction with midspan connectivity creates a single line (or edge) feature comprised of multiple edge elements.

Enterprise deployment

An enterprise deployment is the primary deployment pattern for a utility network that employs an enterprise geodatabase to publish, edit, and work with services from?ArcGIS Enterprise. This services-based architecture allows for multiuser access and the sharing of a utility network across all platforms (desktop, mobile, and web).

Geometric coincidence

When two or more features exist in the same x-, y-, and z-location, they are geometrically coincident.

Example

Sometimes features can occupy the same x- and y-locations, such as devices stacked on a pole. Assigning z-values features at the same x- and y-locations will help ensure features are not geometrically coincident.

Inconsistent subnetwork

When a subnetwork has multiple subnetwork controllers and the?Subnetwork Name?attribute is not consistent, the subnetwork is considered inconsistent.

For example, in a subnetwork with five subnetwork controllers, four of the subnetwork controllers have the correct subnetwork name, while the fifth has a different name.

If inconsistent subnetworks are discovered during the update process, an error is returned in the?Update Subnetwork?tool and errors are generated for the subnetwork controllers. Inconsistent subnetworks are also reported when performing a subnetwork trace.

Junction-edge connectivity rule

A junction-edge connectivity rule is a type of connectivity rule that governs which junction network features you can connect to endpoints or vertices of lines and edge object classes.

Example

You can connect a switch to the endpoint of a medium-voltage line.

Junction-junction connectivity rule

A junction-junction connectivity rule is a type of connectivity rule that governs the junction and junction object classes that can be connected to other junction or junction object classes. Applying this rule allows a connectivity association to be defined between two disjointed classes.

Example

You can connect a capacitor to a switch.

Map view

The map view shows a cartographic display of your utility network. When edits are performed, dirty areas appear on the map showing where the network topology is not current.

Midspan connectivity

When connecting network features to a line or edge object, you can make connections at either the endpoints or the midspan vertices. Using the midspan vertices allows you to create network features without breaking network lines where the physical line is continuous.

Example

A typical location for midspan connectivity is where a service drop connects to an electric distribution line. Subnetwork taps also occur midspan of line features and edge objects.

Network attribute

Network attributes are associated with attributes on feature classes and object tables in your network. They are derived from the network feature's attributes and cached inside the network topology to aid in performance while attributes are evaluated during a trace or while performing subnetwork management tasks. The values stored as attributes for features and objects are reflected or updated in the associated network attribute each time you validate the?network topology.

Example

You can model electric phases as a network attribute so that a trace can be run on only one of three electric phases.

You can define pipe diameters as a network attribute to constrain gas and water traces.

Network categories

A network category is a tag used to represent a characteristic of an asset in your network. They are created and assigned to network features for specific asset groups and asset type combinations.

Example

You can use a network category of Protective to limit traces of electric network features to devices or equipment that is used to protect the system, such as fuses or reclosers.

Network diagrams

Network diagrams provide a simplified view of a network, which is useful for different types of engineering analysis. These are also called schematic representations and apply user-specified algorithms to collapse nonessential features and highlight crucial features for an engineer's view of the network.

Example

A one-line diagram for electric utilities is a network diagram.

Network topology

The network topology enables tracing analysis and rapid retrieval of network features. When edits occur on a utility network, affected parts of the network topology are displayed as dirty areas to indicate that the network topology does not match the edited features. The network topology stores all types of associations—connectivity, containment, and structural attachment—in the utility network. A validate network topology operation updates the associations in the area where edits took place and produce accurate tracing results.

Nonspatial objects

Junction and edge objects are nonspatial network objects used to model and work with a large number of real-world features that share a common geographical space, for example, the strands inside of a fiber cable or conductors in an underground duct. This allows organizations to model their network in more detail without the need to create features with shapes for every asset.

Portal utility network owner

When working with a utility network stored in an enterprise geodatabase, there are two owners for a utility network dataset: the?database owner?and the portal owner.

The active portal user when the utility network is created serves as the portal dataset owner. The portal utility network owner must meet certain?requirements and prerequisites. Having the portal utility network owner signed in is a prerequisite for certain network configuration tasks as well as for publishing utility network layers. Tools that require an active portal connection with the portal utility network owner list this requirement in the usage notes.

Dive-in:

When accessed from a database connection established as the?database utility network owner, the portal utility network owner is listed in the?General?section of the?Network Properties?dialog box.

Preset template

A preset template allows an editor to quickly place a complex collection of features. Preset templates create all types of needed associations as well as place network features. Preset templates are part of the core?ArcGIS Pro?editing framework and work with the association framework in the utility network.

Example

A preset template places a switchgear container with all its internal switches, fuses, and busbars and connects them properly.

Service territory

The service territory is an m- and z-enabled polygon feature class containing one or more features. This is used as input when?creating a utility network. The extent of the features in the service territory feature class is used to define the network extent. The network extent is a single polygon feature that is calculated by aggregating the spatial extents of all input features; it is created slightly larger than the aggregated extent from the input service territory features. You can view the polygon that encompasses the network extent by displaying the dirty area for a utility network when the network topology is disabled.

The network extent represents the area in which the network topology is maintained. This also restricts the editable area for all of the structural network and domain network features collectively. To restrict the creation of network features at a finer level, create a constraint?attribute rule?using?Arcade?geometry functions such as Intersects as part of the script expression.

Example

A service territory spans the operational area of a utility. It can be roughly the area of a city, state, or province.

Single-user deployment

A single-user deployment is an alternate deployment pattern for a utility network stored in a file or mobile geodatabase that provides access to the full analytic capability of the utility network. While concurrent access is enabled for read-only operations, locking processes on a?mobile geodatabase?and at the?feature dataset level of a file geodatabase?prevent editing by more than one user.

Structural attachment association

A structural attachment association allows the modeling of supporting structures and attachments in a network. Often, a utility needs to report what structural features, such as poles, are associated with a subnetwork, or it may need to locate a manhole where a critical piece of equipment can be reached. Structures are not part of the network for purposes of tracing the resource, but there is a need to quickly identify and list structures that have network features attached to them. Structural attachments logically associate structure features with other features in a utility network. These associations allow you to model the relationship between structures that support equipment and associated assets that are attached. For example, a pole can serve as the structure, with a transformer as the attachment.

• A structure can have many attachments (for example, a pole with a transformer, ground, riser, and arrester attached to it).
• Attachment features, such as platforms, can also be associated with multiple poles (structures).

Structure network

Every utility network has a structured network that represents the classes that support the devices and lines that convey a resource. All domain networks in a utility network share a common structure network.

Example

An electric network has poles, pads, cabinets, and other structural features that are utility assets but do not directly carry the delivered resource.

Subnetwork

A subnetwork represents a topological subpart within a tier where all the connected features are defined by the same subnetwork controller or controllers. To create a subnetwork, a subnetwork controller is set, the network topology is validated, and the subnetwork is updated.

Example

Subnetworks are called circuits in electric systems and pressure zones in gas and water systems.

Subnetwork-based trace

There are many core trace types provided with the?Trace?geoprocessing tool. Subnetwork-based traces rely on information from the?subnetwork trace configuration. This is part of the?subnetwork definition?for a tier and is used to limit the scope of the trace results when specifying the?Domain Network?and?Tier?parameters in the?Trace?tool.

Subnetwork-based traces that use the?subnetwork definition?in the trace configuration include the following:

Subnetwork controller

A subnetwork controller is a type of network feature from which a resource is delivered or collected. A subnetwork controller type is defined for each domain network, and when the tier is configured, it is defined to use one or more of the controllers in the domain network. You can configure certain asset group and asset types to allow them to be set as subnetwork controllers; this is done by assigning a network category. Subnetwork controllers are set for device features and junction objects using a specific terminal and are used as start or end points for tracing analysis.

Example

For an electric system, a subnetwork controller for electricity is a power-generating station or substation. For a gravity-fed system, a subnetwork controller can be a reservoir for a water delivery system.

System junction

A system junction is a hidden network feature that is placed at the endpoint of a network edge element when there is no user-defined junction. System junctions are generated during the initial enabling of the network topology or through validating the network topology. These features are hidden in the map view, but you can display them in a network diagram view.

There are a few situations in which system junctions are created:

• A single edge element with no user-defined junctions at the endpoints
• Two edge elements that share an endpoint and do not have a user-defined junction connecting them
• If the edge features have the same?Asset group?and?Asset Type?attributes, a system junction is created between the edge features, and connectivity is established.
• If the edge features have different?Asset groups?and?Asset Type?attributes, a system junction is created at the end of each edge feature, and connectivity is not established.?Errors?are created.

Terminal

Terminals model physical connections on a class such as a Device or JunctionObject. While terminals are not required, there are cases where terminals are necessary. Classes that serve as a subnetwork controller require terminals when there are three or more connections to the feature. The use of terminals allows more realistic modeling of some features and enables more accurate data exchange to external analytic systems.

Example

A transformer has high- and low-side terminals. A circuit breaker has source-side and load-side terminals.

Terminal configuration

A terminal configuration defines how a resource can flow within a network feature that has defined terminals. When you create a terminal configuration, you define whether the resource can flow in both directions or only one direction, the name of terminals, whether a terminal is on the upstream or downstream side of the network feature, which paths between terminals are valid, and the default path through terminals. Once created, a terminal configuration is assigned to an asset type of an asset group in the Device feature class or JunctionObject table.

Example

A delta-wye transformer has a terminal configuration that specifies the valid pathways between the high-side and low-side terminals.

Tier

Tiers are used to segregate and manage the final architectural piece of a network: subnetworks. A single-tier defines a collection of individual subnetworks that all share the same properties and adhere to the same restrictions. Properties are defined when you add a domain network and create tiers for the utility network. These properties determine the layout of tiers and their position relative to the rest of the tiers in a domain network.

Example

You can model an electric distribution domain network with two tiers, where the medium-voltage tier starts at the load-side terminal of the outbound circuit breaker of the substation. The circuit breaker converts transmission-level voltages to medium-level voltages and traverses all the lines and devices until it reaches the high-side terminal of distribution transformers, which converts electric power to low voltages.

Trace analysis

Common types of analysis done with a network involve traces. A utility may want to know every network feature that is connected to a source, find loops in a network, or find all network features upstream or downstream from a selected point. Some types of traces are constrained by specific devices, such as protective devices, and the definitions of those device types are specified by device categories in a domain network.

Example

Examples of trace analysis are upstream traces, downstream traces, and connected traces.

Traversability

Two related concepts in the utility network are connectivity and traversability. Connectivity describes the potential range of the resource flow (electricity, water, gas, or other). Traversability describes the actual range of resource flow according to the current state of devices that can impede flow, such as valves or switches. The definition of subnetworks that are delimited by the present status of interrupting devices (switches and valves) illustrates the concept of traversability.

Example

A water system can have many connected pipes, but closed valves disconnect zones of water delivery from one another. Both point and line features can be disabled, limiting the flow of a resource.

Unlocatable objects

Nonspatial junction and edge objects are represented visually through associations with another feature. Associations are also used to determine the location of an object. If this association is deleted, this can create a scenario in which the junction or edge object is unlocatable. Junction and edge objects are referred to as unlocatable when they do not have a connectivity association, do not serve as content, or are not structurally attached to a feature in their association hierarchy.

Utility network

A utility network is a geodatabase dataset that provides advanced capabilities to visualize, edit, and analyze your network data in ArcGIS. It is the main component users work with when managing utility and telecom networks in ArcGIS, providing a comprehensive framework of functionality for the modeling of utility systems such as electric, gas, water, stormwater, wastewater, and telecommunications.

A utility network is a collection of domain networks (gas, water, electric, or other) plus a structured network. An organization specifies the set of domain networks that it manages when it configures a utility network. You can define associations across domain networks and enable tracing analysis across those domains. For example, you can perform electric tracing analysis from the transmission to distribution levels with a utility network with electric transmission and electric distribution domain networks.

Example

A utility network can contain multiple domain networks. This enables the utility to define associations from common structures. For example, a municipal utility can manage poles that carry cable TV and electrical power.

Utility Network Version

When a utility network is created or upgraded, the?Utility Network Version?value is recorded in the?network properties?in the?General?section.