When you create a utility network, a structure network is automatically created with predefined feature classes and tables. 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 network 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.
Classes in a domain network
Each domain network consists of five feature classes and two tables that are created when you add a domain network: Device, Line, Junction, Assembly, SubnetLine, JunctionObject, and EdgeObject. These classes are created with system-provided attribute domains assigned to system fields for use by the utility network and require additional configuration for use.
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.
- 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.
- Assembly—Represents point features that contain other features. As with device features, assembly features are compact features, but they differ in that assemblies contain other significant devices. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. You can view the internal features of an assembly on the map or in the diagram view. Examples of assembly features are switchgear, transformer banks, and pump assemblies.
- 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.
The two tables are described as follows:
- JunctionObject—Represents nonspatial junction objects such as racks or ports that are contained or associated with other network features. Junction objects can optionally have terminals when there are distinct entry points for the object.
- EdgeObject—Represents nonspatial edge objects such as fibers in a cable. These are stored in a table due to the large number of features that may be contained in a cable.
A utility network consists of one or more domain networks and a structure network. The following diagram shows the classes in a utility network for a municipal utility that serves both gas and water to its customers:
Domain network class naming
The names given to classes are standard across all domain networks. To distinguish them, each class name is prefixed with the name of the domain network. The classes included in a domain network are listed in the following table. Additionally, an alias name is given to all the domain network classes. This alias is set when a domain network is added. For example, a GasDevice feature class could have a default alias name of Gas device. This alias can be changed.
The following table includes name examples for classes in a gas domain network:
Class names in a gas domain network
| Class suffix name | Class name |
|---|---|
Device | GasDevice |
Line | GasLine |
Assembly | GasAssembly |
Junction | GasJunction |
SubnetLine | GasSubnetLine |
EdgeObject | GasEdgeObject |
JunctionObject | GasJunctionObject |
Domain network attributes
All classes in a domain network share the following attributes:
| Field name | Field alias | Description |
|---|---|---|
| ASSETGROUP | Asset group | Subtype field with the major classification of feature types. |
| ASSETTYPE | Asset type | Field with minor classifications implemented as attribute domains for each asset group type. |
| ASSOCIATIONSTATUS | 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. |
| SUBNETWORKNAME | Subnetwork name | Name of the subnetwork in which the feature resides. The Assembly feature class does not have a subnetwork name field. |
| SUPPORTEDSUBNETWORKNAME | Supported subnetwork name | Name of the subnetwork that the container or structure feature supports. Note:Utility Network Version 4 and later. |
| SUPPORTINGSUBNETWORKNAME | Supporting subnetwork name | Name of the subnetwork that supports the content feature. The Assembly feature class does not have a Supporting subnetwork name field. Note:Utility Network Version 5 and later. |
Note:
Additional fields are added when Global ID and editor tracking are enabled.Features from the Device class have the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| ISSUBNETWORKCONTROLLER | Is subnetwork controller | Indicates whether the feature is set as a subnetwork controller. |
| ISCONNECTED | Is connected | The Is connected attribute indicates whether there is connectivity to a subnetwork controller in the network. |
| SUBNETWORKCONTROLLERNAME | Subnetwork controller name | Stores the subnetwork controller name of the feature. |
| TIERNAME | Tier name | Name of the tier in which the feature resides. |
| TIERRANK | Tier rank | Rank of the tier in which the feature resides. |
| TERMINALCONFIGURATION | Terminal path | The terminal path configuration present for the feature. |
Features from the Line class have the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| FROMDEVICETERMINAL | From device terminal | The ID of the terminal to which the from end of a line is connected. |
| TODEVICETERMINAL | To device terminal | The ID of the terminal to which the to end of a line is connected. |
| ISCONNECTED | Is connected | The Is connected attribute indicates whether there is connectivity to a subnetwork controller in the network. |
The Junction class has the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| ISCONNECTED | Is connected | The Is connected attribute indicates whether there is connectivity to a subnetwork controller in the network. |
The JunctionObject table has the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| ISSUBNETWORKCONTROLLER | Is subnetwork controller | Indicates whether a terminal on an object is set as a subnetwork controller. |
| ISCONNECTED | Is connected | The Is connected attribute indicates whether there is connectivity to a subnetwork controller in the network. |
| SUBNETWORKCONTROLLERNAME | Subnetwork controller name | Stores the subnetwork controller name of the object. |
| TIERNAME | Tier name | Name of the tier in which the object resides. |
| TIERRANK | Tier rank | Rank of the tier in which the object resides. |
| TERMINALCONFIGURATION | Terminal path | The terminal path configuration present for the object. |
The EdgeObject table has the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| ISCONNECTED | Is connected | The Is connected attribute indicates whether there is connectivity to a subnetwork controller in the network. |
For information about the SubnetLine class attributes, see SubnetLine feature class.