Utility Network Configuration and Data Modeling
This domain tests schema design: asset groups and asset types, terminals, connectivity rules, network attributes, categories, tiers, subnetwork controllers, and attribute rules. The exam expects you to translate a utility system into a working utility network model, not just name tools.
Core rules and concepts
- Build the schema with the Create Utility Network tool or from an asset package, then add domain networks, tiers, feature classes, asset groups, asset types, terminals, rules, network attributes, and categories.
- Asset Group is the broad class; Asset Type is the specific type within that group. Both fields use coded value domains, so invalid combinations should be prevented by the schema.
- Terminals are defined on device feature classes and referenced by connectivity rules. A transformer may have high-side and low-side terminals; a rule can allow a primary conductor only on the high side.
- Connectivity rules include junction-junction, junction-edge, edge-edge, containment, and attachment rules. Rules can be restricted or allowed and can reference terminals.
- Network attributes support traces and analysis, for example source, distance, capacity, or flow. Categories let you filter traces and rules by asset type groups.
- Subnetwork controllers are asset types designated at the tier level. Update Subnetwork populates subnetwork names after edits.
Worked example
A pad-mounted transformer is modeled as a device with two terminals, High and Low. Create a connectivity rule from the primary conductor asset type to Transformer:High, and another from the secondary conductor asset type to Transformer:Low. At validation, a primary conductor connected to the Low terminal is flagged as a rule violation. The reasoning is that terminal-specific rules encode which side of the device is valid for each conductor type.
Traps that cost marks
- Creating terminals but never referencing them in rules, so terminal restrictions do nothing.
- Confusing attribute rules with connectivity rules. Attribute rules calculate, constrain, or validate field values; connectivity rules govern network connections.
- Adding network attributes but not assigning values or using them in trace configurations.
- Changing the schema without re-enabling or validating network topology.
- Defining a subnetwork controller on the wrong asset type or tier.