Domain networks contain the network features through which the delivered resource flows.
A traditional domain network is used to model utility resources through subnetwork management. This domain network type is ideal for modeling sink-based systems, such as storm or wastewater systems that model pump stations and water treatment plants as controllers, and source-based systems such as electric distribution systems in which circuit breakers and transformers model the source of flow.
There are five features classes and two tables in a traditional 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 traditional domain network consists of five feature classes and two tables that are created when you use the Add Domain Network tool to 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. Additional classes cannot be added to 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 the utility resource flows, and devices can affect the 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 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 the 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 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 uses both a traditional gas and water domain network to serve 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 traditional domain network are listed in the following table. Additionally, an alias name is provided for each class when a domain network is created. For example, a GasDevice feature class could have a default alias name of Gas device. This alias can be changed.
The following table includes example names and aliases for classes in a traditional gas domain network:
Class names in a traditional gas domain network
| Class suffix name | Class name | Class alias |
|---|---|---|
Device | GasDevice | Gas Device |
Line | GasLine | Gas Line |
Assembly | GasAssembly | Gas Assembly |
Junction | GasJunction | Gas Junction |
SubnetLine | GasSubnetLine | Gas Distribution |
EdgeObject | GasEdgeObject | Gas Edge Object |
JunctionObject | GasJunctionObject | Gas Junction Object |
Traditional domain network attributes
All classes in a traditional 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 | 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 | 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 | Indicates whether there is connectivity to a subnetwork controller in the network. |
| FLOWDIRECTION | Flow direction | Indicates whether resources flow with or against the digitized direction of a line, or if flow is indeterminate when modeling flow using the digitized direction of lines. To learn more, see Flow direction in a utility network.
Note:Utility Network Version 7 and later. |
The Junction class has the following additional attributes:
| Field name | Field alias | Description |
|---|---|---|
| ISCONNECTED | Is connected | 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 | 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 | Indicates whether there is connectivity to a subnetwork controller in the network |
| FLOWDIRECTION | Flow direction | Indicates whether resources flow with or against the From and To global ID of the edge object in the association, or if flow is indeterminate Note:Utility Network Version 7 and later. |
For information about the SubnetLine class attributes, see SubnetLine feature class.