ArcGIS Utility Network Associate cheat sheet

The utility network is a feature dataset inside a feature class geodatabase; it requires an enterprise geodatabase (SQL Server, Oracle, PostgreSQL, or SAP HANA) and a branch versioned dataset.

Core asset types: Device (point features that can have terminals, e.g., transformers, switches), Junction (point features without terminals, e.g., valves, service points), Line (polyline features that connect devices/junctions), Edge Object (non-spatial connectivity for lines, e.g., fiber strands), Junction Object (non-spatial connectivity for junctions).

Terminals define connectivity points on devices; a device can have up to 8 terminals. Terminal configurations define which terminals are internally connected (e.g., a transformer with two terminals connected).

Subnetworks are collections of features that share a common network characteristic (e.g., pressure zone, circuit). They are defined by a subnetwork controller (source or sink) and are used for tracing and analysis.

Tiers define network hierarchy and trace behavior; tiers are assigned to subnetwork controllers and determine which features are included in a trace (e.g., hierarchical trace).

Associations model non-spatial relationships: connectivity associations (e.g., junction-edge connectivity) and containment associations (e.g., a transformer bank containing transformers).

The network topology is a set of tables that store connectivity and is built/maintained with the Enable Network Topology and Validate Network Topology tools; it must be validated after edits.

Attribute rules (calculation, constraint, validation) enforce data integrity and are evaluated during editing; they are stored in the geodatabase and can be batch-calculated.

Utility network services are published from ArcGIS Pro to ArcGIS Enterprise (Portal/Server) as feature services with the utility network capability enabled; editing requires branch versioning and the utility network service.

The utility network is created with the Create Utility Network tool, which requires a feature dataset containing the input feature classes; the tool adds system tables and fields and builds the network topology.

Asset groups and asset types are defined in the utility network properties; asset types are the specific categories (e.g., 'Single-phase overhead transformer') and asset groups are broader classifications (e.g., 'Transformer').

Terminal configurations are configured per asset type; they define the number of terminals and the internal connectivity (e.g., 'Load' and 'Source' terminals connected via a transformer).

Subnetwork controllers are defined by assigning a subnetwork controller asset type to a device or junction and configuring the tier; a subnetwork can have multiple controllers (e.g., multiple sources).

Tiers are configured with a rank (1-10), a trace configuration, and a subnetwork definition; rank determines hierarchy for traces like 'upstream' or 'downstream'.

Attribute rules: calculation rules (e.g., set a field value based on another field), constraint rules (e.g., restrict valid values), and validation rules (e.g., check for nulls). They are authored in ArcGIS Pro and stored in the geodatabase.

Network attributes (e.g., phasemodel, pressure) are assigned to feature classes and used in traces; they must be configured with data types and may have bitwise or numeric values.

Connectivity rules define which asset types can connect (e.g., line to transformer) and are configured per asset type; they are enforced during editing and topology validation.

The utility network requires a schema with specific system fields (e.g., assetid, assettype, assetgroup) and is versioned; branch versioning must be enabled before creating the utility network.

Editing requires a branch versioned feature service with the utility network capability; edits are made in ArcGIS Pro or ArcGIS Enterprise and saved to the default version or a named version.

The network topology must be validated after edits to update connectivity and associations; use the Validate Network Topology tool or the Validate button on the Utility Network tab.

Associations are created with the Create Association tool; connectivity associations connect junctions to edges, and containment associations connect features to a container (e.g., transformer bank).

When editing, the utility network enforces connectivity rules and terminal configurations; invalid connections are flagged as errors and can be inspected with the Error Inspector.

Attribute rules are evaluated during editing; calculation rules run on insert/update, constraint rules prevent invalid edits, and validation rules are evaluated during validation.

To move features along the network, use the Modify Associations or the Move tool; the network topology must be updated to reflect changes.

Subnetwork management: subnetwork controllers define the subnetwork; after edits, update subnetworks with the Update Subnetwork tool to refresh subnetwork names and traces.

Batch calculation of attribute rules can be run on a selection or entire feature class using the Calculate Attribute Rules tool; this is useful for existing data.

Versioning: edits are saved in a named version; reconcile and post to the default version to publish changes; the utility network service must be stopped/started for some schema changes.

Trace types: Connected, Upstream, Downstream, Loops, Shortest Path, Subnetwork, Isolation, and Protective Device. Each trace uses a starting point (flag) and trace configuration.

Trace configuration includes: include containers, include content, include barriers, traversability (e.g., only traverse features with certain attributes), and output options (e.g., select features, generate results).

Upstream trace finds features that are upstream of the starting point based on flow direction or subnetwork controller; Downstream trace finds features downstream.

Subnetwork trace returns all features in the subnetwork containing the starting point; it requires a subnetwork controller and uses the tier's trace configuration.

Isolation trace identifies the section of the network that can be isolated by protective devices; it requires protective devices to be configured.

Trace results can be saved as selection sets, feature classes, or used in other analyses; the Trace tool is available in ArcGIS Pro and via the utility network service REST API.

Network attributes (e.g., phasemodel) can be used as traversability criteria; for example, trace only features with a specific phase.

The Trace Locations pane manages starting points and barriers; barriers stop the trace at specified features.

Tracing requires the network topology to be enabled and validated; traces can be run on a version or the default version, and results reflect the version's edits.

Publishing: share the utility network feature dataset as a feature service with the Utility Network capability enabled; this requires ArcGIS Enterprise (Portal for ArcGIS and ArcGIS Server) with the utility network service extension.

The feature service must be branch versioned; the service publishes the default version and allows editing of named versions.

Service administration: use ArcGIS Server Manager or ArcGIS Pro to manage the service; capabilities include Query, Update, Create, Delete, and Sync (for offline).

Version management: create versions, reconcile, post, and delete versions using the Versions view in ArcGIS Pro or the REST API; the utility network service must be stopped to perform some administrative tasks (e.g., enable/disable topology).

Backup and recovery: use geodatabase backup tools (e.g., SQL Server backup) and export the utility network; the network topology can be rebuilt if corrupted.

Performance: ensure network topology is validated, indexes are present, and traces are optimized; use the utility network service's trace REST endpoint for web apps.

Security: assign privileges to the feature service (e.g., editing, querying) via Portal; utility network editing requires the 'Edit' privilege and version access.

Upgrades: upgrade the geodatabase and utility network using the Upgrade Geodatabase tool and the Upgrade Utility Network tool; this is required after ArcGIS software upgrades.

Monitoring: use ArcGIS Server logs and the utility network service's REST API to monitor trace performance and errors; the network topology can be disabled to improve bulk editing performance.