Skip To Content

Domain networks

When you create a utility network, a structure network is automatically created with predefined feature classes. The next step in configuring a utility network is to add one or more domain networks for each type of utility service that your organization serves.

Each utility network can contain one or more domain networks. You might create multiple domain networks for different levels of the same utility resource such as distribution and transmission levels of gas, water, or electricity. Or you might add domain networks if your organization has multiple types of services such as natural gas and electricity.

Each of these domain networks will share the same structure network so that you can find the devices and lines in your domain networks that are supported by common structures.

Domain networks contain the features through which your delivered resource flows. There are five types of features in a domain network: lines through which a resource flows; devices that control the flow of that resource; junctions placed where features are connected; assemblies representing collections of lines, junctions, and devices; and subnetwork lines that define the extent of resource flow.

Feature classes in a domain network

Each domain network consists of five feature classes that are created when you add a domain network: Device, Line, Junction, Assembly, and SubnetLine. These feature classes are created with system attribute domains assigned to system fields for use by the utility network and require additional configuration for use.

Feature classes in a domain network

The five feature classes are described as follows:

  • Device—Represents point features such as valves, meters, transformers, and switches. These are compact features through which your utility resource flows, and devices can affect your resource in several ways. For example, a valve controls the flow of water; a transformer changes electrical power from one voltage level to another; or a meter measures the gas, water, or electricity consumed by the customer. Devices can optionally have terminals when there are distinct entry points to the device. Devices can be connected to other devices, junctions, and lines. Devices can be contained in assemblies as well as in structure junctions, structure lines, or structure boundaries, which are containers.
  • Line—Represents linear features such as wires and pipes. These are the lines that deliver your utility resource such as gas, water, electricity, or communications. Lines can be connected to other lines, junctions, and devices. Lines can be contained in assemblies as well as in structure junctions, structure lines, or structure polygons.
  • Junction—Represents locations where lines connect to lines or lines connect to devices. A key use of junction features is to allow devices or lines to connect to another line at an intermediate vertex. Junctions are placed as needed to complete the connection of all the features of a utility network. Junctions can be contained in assemblies as well as in structure junctions, structure lines, or structure polygons.
  • Assembly—Represents point features that contain other devices and lines. As with device features, assembly features are compact features, but they differ in that assemblies contain other significant devices. Examples of assembly features are switchgear, transformer banks, and pump assemblies. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. Assemblies can contain devices, lines, and junctions. You can view the internal features of an assembly on the map or in the diagram view.
  • SubnetLine—A collection of subnetwork lines that define the current extent of a resource flow. For water or gas utilities, subnetworks are called pressure zones. For electric utilities, subnetworks are called circuits or feeders. Subnetworks are not directly edited like the other features in a domain network. Rather, they are generated by a command to update subnetworks. This command traces the flow of a resource from a subnetwork controller (such as a substation or water tank) through all the devices and lines until either that resource is consumed or the flow is blocked by an interrupting device such as a switch or valve. Because of switching devices, subnetworks frequently change and can be quickly regenerated on demand.

A utility network consists of one or more domain networks and a structure network. The following diagram shows the feature classes in a utility network for a municipal utility that serves both gas and water to its customers:

Example set of domain networks for a municipal utility

Domain network feature class naming

Feature class names are standard across all domain networks. To distinguish them, each feature class name is prefixed with the name of the domain network. The feature classes included in a domain network are listed in the following table. Additionally, an alias name is given to all the domain network feature classes. This alias is set when a domain network is added. For example, a GasDevice class could have a default alias name of Gas device. This alias can be changed.

The following table includes name examples for feature classes in a gas domain network:

Feature class names in a Gas domain network

Feature class suffix nameFeature class name











Domain network attributes

All feature classes in a domain network share the following attributes:

Field nameField aliasDescription

Asset group

Subtype field with the major classification of feature types.


Asset type

Field with minor classifications implemented as attribute domains for each asset group type.


Association status

Describes the type of association in which a feature participates, the role it plays in the relationship, and visibility properties for content features. For more information, see Associations and Association status attribute.


Subnetwork name

Name of the subnetwork in which the feature resides.


Global ID

Globally unique identifier used throughout a utility network.



Editor tracking field designating who created the feature.


Creation date

Editor tracking field designating the time the feature was created.


Updated by

Editor tracking field designating who last edited the feature.


Last update

Editor tracking field designating when the feature was last edited.

Features from the Device class have the following additional attributes:

Field nameField aliasDescription

Is subnetwork controller

Indicates whether a terminal on a device feature is set as a subnetwork controller.


Is connected

The Is connected attribute indicates whether or not a device has connectivity to any subnetwork controller in the network.


Subnetwork controller name

Stores the names of the subnetwork controllers present on a device feature.


Tier name

Name of the tier in which the feature resides.


Tier rank

Rank of the tier in which the feature resides.


Terminal path

The terminal path configuration present for a device.

Features from the Line class have the following additional attributes:

Field nameField aliasDescription

From device terminal

The ID of the terminal to which the FROM end of a line is connected.


To device terminal

The ID of the terminal to which the TO end of a line is connected.

For information about the SubnetLine class attributes, see SubnetLine feature class.