Understanding Esri’s Network Management Framework

Written by Kim Sundeen, GIS Analyst/Developer, RAMTeCH

You’ve been hearing more and more about Esri’s Utility Network as part of its new Network Management Framework. RAMTeCH is here to help answer questions about what the new network offers and why it makes sense to transition. If you’re like most ArcMap users, you might be wondering:

  • What are the Basics of Network Management?
  • How Should I Transition to Network Management?
  • What is the Business Case for Transitioning to Network Management?
  • What are Technical Reasons for Transitioning to Network Management?
  • How Does the Geometric Network Compare to the Utility Network?
  • How Do Rules and Editing in the Geometric Network Compare to the Utility Network?

In a series of posts on the Utility Network and Network Management Framework, we will address these questions in detail and provide clarity as you explore what making the transition means to your business.

What are the Basics of Esri Network Management?

Moving to the Network Management Framework is a complete paradigm shift, combining new architecture, workflows, and data structures. To set the stage for the transition, it’s critical to understand the following basics:

  • ArcGIS Enterprise as the Everywhere Platform: Maps will be available on all devices and platforms, from mobile to desktop. ArcGIS Pro replaces ArcMap/ArcCatalog. You can view utility network layers as well as update attributes of those layers in Collector and ArcGIS Explorer. The Esri Enterprise Platform comprises ArcGIS Server, Portal for ArcGIS, ArcGIS Data Store, and ArcGIS Web Adaptor.Web GIS
  • Services-Based: All data for a utility network must be published and edited as feature services accessible through ArcGIS Portal (and through ArcGIS Online in later releases).
  • New Data Model: The data model is compressed into five Domain Network classes and three Structure Network feature classes.
    • Domain Network: Each utility (i.e. gas, water, electric) will have its own Domain Network containing the five feature classes: Assembly, Device, Junction, Line, and SubnetLine. The SubnetLine feature classes are ArcGIS system-managed and store multipart polylines features and specific sub-system types. Subnetwork features represent the flow of asset across sub-systems like circuits, pressure or isolation zones, or systems of transmission or distribution.
    • Structure Network: The feature classes of StructureJunction, StructureLine, and StructureBoundary model supporting structures or boundaries that do not participate in the modeling of asset flow.New Model

Later in this series of posts, we’ll be introducing you to more details surrounding the business and technical values and workflows. In all, key functions for the new model include overall improved and compressed model structure, more connectivity and tracing behavior, improved editing environment, and better realism through containment. In addition, we will share examples from editing in Esri’s Utility Pipeline Data Model (UPDM) specific to managing gas and hazardous liquids. Ultimately, the new functionality results in a more performant system to query the database fewer times and display results for the user.

Leave a Reply