Utility Network Management in ArcGIS: Advanced Capabilities of the Utility NetworkDavid CrawfordErik Hoel

Agenda

• Architecture• Versioning• Tracing• Propagation• Network attributes• Subnetwork management• Network diagrams

Architecture

Architecture

• Sud Menon challenged the team to make the new dataset type completely services-based

• No client-server interaction once published• Significant extension to the web geodatabase model

• The utility network is serving as the pattern for future service-based dataset development

• E.g., parcel fabric

Device• View, Query• Simple Design/Inspections• Tracing

Desktop• Design, Maintenance• Analysis, Modeling• Map Authoring

Web• Simple Editing, QA/QC• Tracing• Executive Dashboards

Server Online Content and Services

EnterpriseUtility Network

Transaction ModelEditing Tools

Attribute Rules

Continuing the growth of the platform

Architectureoverview

• Extensions to existing services:• Feature Service (creation of

assemblies/groups of featuresvia applyEdits, Global IDs, publishing a utility network, branch versioning)

• New services:• Utility Network Service (validate

network topology, trace, update subnetworks, etc.)

• Network Diagram Service (all things diagram)• Version Management Service (branch versioning only - version creation, reconcile, post, etc.)• Validation Service (attribute validation rules) – available at 2.2/10.6.1

Architectureclient-server

ArcGIS Pro

Geodatabase

SDEWorkspace

EnterpriseGeodatabase

SDK

Architectureservices

ArcGIS Pro

Geodatabase

Feature Service Workspace

SDEWorkspace

MobileGeodatabase

SDK

ArcGIS Enterprise

Geodatabase

SDE Workspace

NetworkDiagram Service

VersionMgmt

Service

EnterpriseGeodatabase

RESTAPIFeature

Service

UtilityNetworkService

JSON

ValidationService

Architectureservices – web apps

JavaScript SDK

ArcGIS Enterprise

Geodatabase

SDE Workspace

NetworkDiagram Service

VersionMgmt

Service

EnterpriseGeodatabase

RESTAPIFeature

Service

UtilityNetworkService

JSON

ValidationService

Architectureservices – runtime Runtime Core

Runtime Geodatabase

MobileGeodatabase

iOS SDKQt SDKJava SDKmacOSAndroid.NET

ArcGIS Enterprise

Geodatabase

SDE Workspace

NetworkDiagram Service

VersionMgmt

Service

EnterpriseGeodatabase

RESTAPIFeature

Service

UtilityNetworkService

JSON

ValidationService

Utility networkkey technologies

• Service architecture• Information model• Associations• Terminals• Branch versioning• Network topology• Tracing framework• Network diagrams• Subnetwork management

• Attribute rules• Contingent attribute values• Framework• Pro SDK (C#)• Mobile SDKs• JavaScript SDK• Single user geodatabases• Non-spatial features

Versioning

What is versioning?

• A multiuser, long transaction, concurrent editing model• Allows multiple users to edit the same data at the same time without

making multiple copies of the data over a long period of time• Versioning manages and records changes to a multiuser geodatabase

by creating a virtual copy of the database to each user.

What is branch versioning?

• A highly performant versioning model created to work in services• Only available through the version management service• Version Management Server only supports branch versioning

• Access to branch datasets in client / server is read only

Benefits

• The only way to get versioning and long transactions for feature services

• Undo or redo changes as you're editing feature services• Conflict resolution can occur concurrently and over multiple sessions• Supports the utility network (traditional versioning is not supported)• Enhanced editor tracking capabilities allow you to also track users

who delete features within a version.• Unlike traditional versioning, the compress operation is not required

for geodatabases with branch versioned datasets

Limitations

• Can be used only in ArcGIS Pro and edited only with feature services• Simple features and the utility network are currently the only

datasets available for editing through branch versioning• If you would like to edit topology or a network dataset in a versioned

environment, you'll have to work with traditional versioning

• Allows only one editor per branch version or multiple readers• Once an editor begins editing within a branch version, an exclusive lock is

obtained and no further users can connect to the version

Sharing and editing versioned data

• Editing branch versioned data is only available through feature services

• After registering data as branch versioned, you publish the data to your organization's portal

• The data is available as a feature service and can edited and participate in branch versioning workflows

• When you publish branch versioned data, there is an option to enable Version Management capabilities

• The version management service exposes the management capabilities that support feature services that work with branch versioned datasets

• To work with the data in named versions, Version Management must be enabled when publishing the service

Publishing constraints

• 10.5 and earlier ArcGIS Server instances are not supported• If Version Management is enabled under Capabilities, all datasets must be

of the same registration type• If Version Management is not enabled under Capabilities, publishing a mix

of data types is allowed with the exception of traditional versioning• All data must belong to a branch workspace• All data must be published from the default version• The connected geodatabase user must be the owner of the data• If the feature layer is going to participate in a utility network, the following

must also be true:• Definition queries must not be present and all fields must be visible

Tracing

Analyze Your Network

• The ArcGIS Utility Network Management extension has an array of analysis and tracing tools to support a large variety of analytic workflows:

• Perform inspection of the network in the aftermath of an event such as a severe storm

• Determine the number of customers with access to your resource, e.g., you can create a load summary report to present the number of customers being supplied by a specific circuit in an electric network

• Trace network features upstream or downstream from a given location, e.g., water utilities can determine which valves to shut off when a pipe bursts

• Model multiple utility systems within one utility network and run tracing analysis on all of them

https://pro.arcgis.com/en/pro-app/help/data/utility-network/what-is-a-utility-network-.htm

20

What is tracing?

• Tracing entails assembling a subset of utility network elements that meet a specified criteria

• Tracing uses network data to provide business value to utilities• Answers questions and solves problems about the current state of the network

• What valves need to be closed to shut off gas to this location?• Helps design future facilities

• How many houses are fed by a transformer, and can the equipment handle another connection?• Helps organize business practices

• Create a circuit map to give to work crews for damage assessment after an ice storm

Starting points

• Many traces require radiating outward from a specific location or set of locations

• Starting points define these locations

• May be added or deleted using the Trace Locations pane

• Can be placed on junctions or edges

22

Starting points

• Trace Locations pane provides a way to specify terminals

• Starting points assembled via the pane are stored in a feature class in default project workspace

23

Barriers

• Barriers define locations at which the traversal of a trace should terminate

• May be added or deleted using the Trace Locations pane• Can be placed on junctions or edges• Barriers are stored in a feature class in the default project

workspace

24

C2C1 C3

Input

C2C1 C3

OutputConnection Point

Starting point

Trace ResultLine: Med. Voltage

Barrier

Trace types

• Trace types define the basic algorithm that is used to perform the analytic

Trace configuration

• Provide input to the Trace to define• What constitutes traversability• What features should be returned• What calculations should be performed

Traversable group 2Traversable group 1

Connectivity vs. traversability

• Connectivity describes the state where two or more features either share a connectivity association, or the collection of features are geometrically coincident at an endpoint (or midspan at a vertex), and a connectivity rules exists that supports the relationship

• Traversability describes the state where two features that are connected also have a path between them that satisfies the trace configuration Line:MedVoltage

ConnectivityAssociation

Non-TraversableLine

User experience workflow

1. Place one or more starting points2. Place barriers (optional)3. Choose a trace type4. Fill in trace configuration options5. Run!

Network attributes

Definitionnetwork attributes

• Network attributes are properties of the network elements that control traversability over the network (phase, kVA, Diameter,)

• Cost. Certain attributes are used to measure and model impedances (voltage/pressure drop)

• Descriptors. Those are attributes that describe characteristics of the network or its elements (open/closed switch)

• Network attributes are derived from feature attributes. They are cached for rapid consumption.

• Attributes should be specified during the network creation

Definitionnetwork evaluators

• Each network attribute defined in the network must have values for each network element.

• An Evaluator assigns values for the network attribute of each element

• Currently UN only has Field evaluator – identify a single field that will be used to evaluate the network attribute

• If a Field evaluator is not specified for a given feature class the values for that attribute are set to default value - 0.

Subnetwork management

What is subnetwork?

Subnetwork managementoverview

• Subnetworks are connected sub-portions of the network that are used for:• Driving analytic operations• Labeling and map production• Visualization (circuit map, pressure zone)• Assigning units of work• Business reports and industry compliance• Exporting subset of network to external systems

• Subnetworks correspond to circuits in electric, and pressure zone in gas or water, trunk lines in waste water

Subnetworks

exactly one

one or more47

UtilityNetwork {Network}

StructureNetwork

DomainNetwork

Device

Line

Junction

SubnetLine

Assembly

StructureJunction

StructureLine

StructureBoundary

TierDirtyAreas

PointErrors

ServiceTerritory

LineErrors

NetworkTopology

NetworkDiagrams

DiagramTemplates

DiagramFolders

Diagrams

Subnetwork

Rules

Subnetworks

exactly one

one or more48

UtilityNetwork {Network}

StructureNetwork

DomainNetwork

Device

Line

Junction

SubnetLine

Assembly

StructureJunction

StructureLine

StructureBoundary

TierDirtyAreas

PointErrors

ServiceTerritory

LineErrors

NetworkTopology

NetworkDiagrams

DiagramTemplates

DiagramFolders

Diagrams

Subnetwork

Rules

Subnetwork managementoverview – domain networks

• The first architectural piece used to organize networks

• Allows to model large, logically separate sections of whole system• E.g. one for electric transmission and one for electric distribution

• Utility network can have one or more domain networks

• The number of domain networks depends on type of model being built and the industry being managed

DomainNetwork Tier

Subnetwork

Subnetwork managementoverview – tiers

• Each domain network supports a collection of tiers, which demarcate a logical level within the network

• E.g., in an electric distribution network, there can be Subtransmission, Medium Voltage, Low Voltage tiers

• Some networks may only have one tier; having more than one tier is not required

• Domain networks can have one or more tiers

• Structure networks do not have any tiers, nor do they have subnetworks

DomainNetwork Tier

Subnetwork

Subnetwork managementoverview – subnetworks

• A tier contains collections of features that form groupings that represent logical subnetworks that deliver the resources

• In an electric network, a subnetwork corresponds to a circuit• In a gas or water network, a subnetwork may correspond to a pressure zone

• Subnetworks are associated with one or more subnetwork controllers• A subnetwork controller (source or sink) is associated with one subnetwork• Sources are the origin of resources (or the destination of resources with sinks) flowing through the

subnetwork

• Subnetwork names and subnetwork controller names are maintained as system managed attributes on Device feature class

• Each subnetwork within a tier has an aggregated geometry representing the features within the subnetwork

DomainNetwork Tier

Subnetwork

Network diagrams

• Comparable to ArcGIS Schematics extension• Core capability of every utility network• Full suite of Geoprocessing tools

Network Diagramsoverview

• System generated diagrams- Created and updated with ‘Update Subnetwork’

• User generated stored diagrams- Diagrams which a user has created and saved into their geodatabase

• User generated temporary diagrams- Diagrams which reside in the current project and are deleted when

no longer referenced

Network Diagramsdiagram types

• 16 layout options• Determines how features display in the diagram relative to other

features- Examples: Smart Tree, Geo Position

• Can be applied to all types of diagrams

Network Diagramsdiagram layouts

• 18 rules• Defines a rule that will impact the overall layout of the diagram

- Examples: reduce junction rule, trace rule• Can be applied to all types of diagrams

Network Diagramsdiagram rules

• Created and stored with the utility network• Incorporates a set of rules and a layout to display the diagram.• Can be applied to all types of diagrams

- User generated diagrams – set at creation time- System generated diagrams – set in the subnetwork definition

Network Diagramsdiagram templates

Network Diagramsgeneration process

58

1. Elementary Build phase ― primarily, a diagram feature is created for each network feature identified as input

2. Diagram Rules phase [OPTIONAL] ― when they are configured on the diagram template, diagram rules are executed each-in-turn to discard certainfeatures, add extra objects, simplify diagram content by reducing or collapsing objects, expand containers, etc

3. Diagram Automatic Layouts phase [OPTIONAL] ― when they are configured on the diagram template, automatic layout algorithms are chained

Network DiagramsArcGIS Pro integration

• Network Diagram ribbon• Panes to interact

• selections• editing• dynamic mode

Road ahead

Utility networksroad ahead

• Performance and scalability• Non-spatial objects

• Support for telco and electric underground

• Mobile/Runtime• Mobile SDKs for partners and end users• Connected tracing (100.6)

• Flow direction• Visualization of resources flowing through the network

• Single user• File geodatabases, required for small utilities

Utility networksroad ahead

• Tracing framework • Updates to handle network loops and isolation traces

• Change network portal ownership and identity• Attribute rules

• Enhancements to enable traversing associations and relationships

• Conflict and lock management UX in Pro