Utility Network Fundamentals
This domain tests the vocabulary and architecture of the ArcGIS Utility Network: what a utility network is, how it differs from a geometric network, and which components must exist before editing or tracing works. Questions often ask you to identify the correct association, rule, or network element for a modeling situation.
Core architecture
- A utility network is an enterprise geodatabase model plus a feature service with the Utility Network capability. It requires branch versioning and an enterprise geodatabase; it is not supported in a file geodatabase or ArcMap.
- Feature classes are typed as device, junction, edge, structure, or assembly. Every utility network feature class carries Asset Group and Asset Type fields, which drive rules, terminals, and traces.
- Associations record relationships: connectivity connects features that are not geometrically coincident; containment places a feature inside another; structure and attachment relate features to supporting structures such as poles or vaults.
- Connectivity, containment, and attachment rules define what is allowed. Rules are evaluated during validation; editing can create a temporary violation that becomes a topology error.
- Domain networks contain tiers. Tiers define subnetwork management. A subnetwork controller, such as a circuit breaker or pressure-reducing valve, acts as a source for a subnetwork.
Worked example
A jumper connects two conductor ends that are 3 meters apart and do not touch. Geometric coincidence cannot create the connection, so the correct model is a connectivity association between the two edge features. If the jumper were modeled as its own line feature, its endpoints would need to snap to the conductors and connectivity rules would need to allow those asset types. The reasoning is: association type answers “what is related,” while a rule answers “what is allowed.”
Traps that cost marks
- Treating network topology as geodatabase topology. Utility network topology is maintained separately, with dirty areas and validation.
- Assuming connectivity rules block an edit immediately. They are checked during validation, producing errors or exceptions.
- Confusing containment with connectivity. A fuse inside a cabinet is contained; a conductor connected to a busbar is connectivity.
- Forgetting that subnetworks need controllers and that tiers define subnetwork behavior.
- Choosing a file geodatabase or ArcMap workflow, both of which are invalid for a utility network.