Utility Network Data Management and Editing
This domain tests how utility network data is loaded, edited, validated, and maintained in a branch-versioned enterprise geodatabase. It covers version workflows, dirty areas, error inspection, association editing, subnetwork updates, and attribute rules.
Core editing workflow
- Editors work in branch versions in ArcGIS Pro using the Utility Network tab. Reconcile and post changes to the default version when the work is complete.
- Edits mark features dirty. Validate rebuilds network topology for dirty areas and creates errors and exceptions. The Error Inspector lists violations and lets you zoom to, fix, or mark them as exceptions.
- Errors are invalid conditions that must be corrected. Exceptions are violations you explicitly accept; they remain recorded rather than silently ignored.
- Associations are edited with Modify Associations. Use it to create or delete connectivity, containment, structure, and attachment associations. Import Associations loads associations when migrating data.
- After edits that affect a subnetwork, run Update Subnetwork so subnetwork names and membership are current. Export Subnetwork can write a subnetwork to a feature class.
- Attribute rules support calculation, constraint, and validation behavior. Batch calculation can apply a calculation rule to existing features.
Worked example
An editor moves a conductor endpoint away from a transformer terminal. The edit creates a dirty area. Validation rebuilds topology and reports a connectivity rule violation or a lost connection. The editor uses Error Inspector to locate the feature, restores the snap or creates the correct association, validates again, then runs Update Subnetwork. The reasoning is that geometry edits do not automatically repair topology; validation is the step that recomputes connectivity and exposes invalid states.
Traps that cost marks
- Validating while network topology is disabled, which cannot rebuild connectivity.
- Marking every error as an exception instead of correcting invalid geometry or rules.
- Forgetting Update Subnetwork after edits, leaving subnetwork membership stale.
- Editing associations by changing geometry only; non-coincident relationships need explicit associations.
- Posting a version without reconciling conflicts first.