What GIS data models are used for electric utility and pipeline networks?

Electric and pipeline operators in ArcGIS Pro build on layers of GIS data models. The utility network models how assets connect so they can be traced. A linear referencing system (LRS) locates pipeline assets by measure along a route. The Utility and Pipeline Data Model (UPDM) holds both in one geodatabase, and industry standards such as PODS and the IEC Common Information Model (CIM) shape how the data is organized and shared.

Key Points

• A utility network is the main component users work with in ArcGIS when managing utility and telecom networks. It provides a framework for modeling electric, gas, water, stormwater, wastewater and telecommunications systems.
• Pipeline operators often add an LRS to the utility network. The network supplies connected topology, and the LRS supplies measures along the route.
• UPDM contains the feature classes, tables and relationship classes needed to support both a utility network and an LRS in a single geodatabase.
• PODS and the IEC CIM are industry standards, not Esri products. PODS is built for pipelines, and the CIM covers electric grid and utility business data.
• Validation rules built into the utility network stop logically invalid data from being entered, which keeps tracing and reporting reliable.

Understanding the Layers

The foundation is the utility network. According to ArcGIS documentation, it is designed to model all components of a system, such as wires, pipes, valves, devices, circuits and zones, and to build real-world behavior into the modeled features. When a utility network is created in ArcGIS Pro, a preconfigured set of feature classes is created. The first three model the structural features that support the utility features, and together they are called the structure network. The structure network carries no resource such as water or electricity itself, but it can contain and support features of the resource-delivering network.

Resource-delivering features live in one or more domain networks, which are standardized classes configured for each system a utility operates. Features are classified with the ASSETGROUP and ASSETTYPE fields, which allows fine-grained classification with a compact number of feature classes. Because the model is shared across electric, gas and water, a single network can also support tracing across systems. Esri documentation notes that an outage in an electrical network can affect delivery of another resource such as gas or water, and a trace can be run across all the systems involved.

Pipelines add a second need. Operators must locate integrity findings and inspections by position along a route, and those positions must not drift when the map is edited. Esri's Gas and Pipeline Referencing Utility Network Foundation solution addresses this by configuring ArcGIS Enterprise, the ArcGIS Utility Network and ArcGIS Pipeline Referencing to represent gas and hazardous liquid pipelines as a single pipe system with both connected topology and linear referencing. The solution features UPDM and is typically implemented by vertically integrated gas utilities and by gas and hazardous liquid pipeline operators. In its 2.0 release in Nov 2021, the solution was renamed and its data model was updated to UPDM 2021.

Standards sit above the software. PODS describes itself as the worldwide industry standard and community for efficient pipeline asset data management, and it lists an Esri Utility Network Implementation Pattern among its technical solutions. On the electric side, the EPRI CIM Primer explains that the IEC CIM comprises three series of standards, each with a specific focus, all based on a single, unified model.

How It Works

Several mechanisms in the utility network make the model useful for tracing and reporting.

1. Tiers and subnetworks: In a traditional domain network, features are organized into tier groups and tiers. A tier typically represents a pressure or voltage level. Esri's example is an electric distribution system divided into subtransmission, medium-voltage and low-voltage levels, with some analysis performed in only one level. The extent of resource delivery at a given time is a subnetwork, which corresponds to a pressure zone for gas and water or a circuit for electric.
2. Tracing from a controller: Subnetworks are discovered on demand. The trace starts at the subnetwork controller and runs through the network until it reaches closed valves, open electric switches or consumption points. A controller is either a source, where resources originate, or a sink, where resources flow toward a point.
3. Terminals and containers: Terminals on devices track ports such as the high side and low side of service, which gives more accurate tracing by controlling the valid paths for a resource. Cabinets, vaults, yards and banks can be modeled as containers, so the map stays free of clutter from their internal features.
4. Rules that block bad data: Editing rules and validation prevent invalid entries. For example, a reducer must be connected to pipes of the correct diameter on either end.
5. Linear referencing on the same pipe: In a combined deployment, the Pipeline Line feature class represents all of the pipes in the system and also serves as the LRS centerline feature class. Calibration points are placed at the beginning and end of each centerline segment, which keeps measures on the route from changing when other edits take place along it.

Esri's documented deployment steps for a combined system start by staging a utility network. The next step is applying an asset package such as the gas configuration. The last is creating an LRS with the Create LRS or Create LRS From Existing Dataset tool. Operators with existing data can use the Migrate To Utility Network tool, which can convert a geometric network or nonnetwork data into a utility network in a mobile geodatabase while preserving the existing feature class schema. Its mapping parameter assigns each source feature class to a target domain network class, an asset group and an asset type.

Esri documents two deployment styles. An enterprise deployment uses a services-based architecture on ArcGIS Enterprise for large-scale, multiuser work. A single-user deployment provides the full analytic capability on a file or mobile geodatabase.

Why It Matters

The data model determines what an operator can ask of its records. Esri says configuring an LRS and a utility network in a single geodatabase combines the analysis capabilities of both products, including checks for connectivity and traversability on the entire utility network, its subnetworks, or upstream and downstream of specific areas. The LRS is typically used by integrity and compliance applications for analysis and reporting, and many of those processes apply dynamic segmentation using the Overlay Events tool.

Standards matter because assets and regulators sit outside any one vendor. PODS says it represents the only geospatial data model specifically designed by the pipeline industry for pipeline operators. It names pipeline safety, a single system of record for asset locations and specifications, regulatory and integrity management, and inspection analysis as its focus. It also states that since its inception in 1998 its data model has been implemented by over 200 pipeline operators, representing over 3 million miles of linear pipeline assets and systems.

On the electric side, EPRI says proprietary formats for sharing data between applications required a myriad of translators and caused exponential growth in complexity, which drove adoption of a model-based exchange approach. It adds that the CIM gained momentum when ERCOT implemented a CIM-based approach for network model data, and that adoption expanded when ENTSO-E required CIM-based exchanges for compliance with grid codes.

The scale of the assets raises the stakes. The EIA says the U.S. natural gas pipeline network has about 3 million miles of mainline and other pipelines linking production areas and storage facilities with consumers. It also says a large portion of the local distribution network, along with part of the existing mainline transmission network, was installed in the 1950s and 1960s, and that some older transmission and distribution lines have reached the end of their useful lives. Accurate connectivity and location records are what let operators plan that replacement work.

Related Terms

• Utility network: A connectivity-based model of wires, pipes, valves, devices and zones, with built-in tracing and editing rules.
• Linear referencing system (LRS): A method of locating features by measure along a route, supported in ArcGIS by Pipeline Referencing.
• UPDM: The Utility and Pipeline Data Model, which supports a utility network and an LRS in one geodatabase.
• Dynamic segmentation: The process, often run with the Overlay Events tool, that builds segments from events along a route for analysis and reporting.
• PODS: The Pipeline Open Data Standard, an industry data model for pipeline asset management.
• IEC CIM: A unified model behind standards for exchanging data among grid operations and utility business systems.

Frequently Asked Questions

What is the difference between a utility network and an LRS?

A utility network models connectivity, so features are linked and can be traced through valves, switches and devices. An LRS models position, locating features by measure along a route. For pipelines, the two are integrated so the same pipe carries both connectivity and measures.

What do the main IEC CIM standards cover?

Per EPRI, IEC 61970 covers information exchange among systems involved in operation and planning of the interconnected electric grid, using power system network models at all voltage levels. IEC 61968 covers exchange among systems supporting business functions such as asset management, work management, meter data management, customer information, geographic information systems and engineering design.

Does the data model change over time?

Yes. According to Arcgis, in release 4.0 (Mar 2026) the Lifecycle Status field was renamed to Asset Lifecycle Status in all Utility Network feature classes. It also added an Asset State field used for subnetwork management and tier definitions. Operators should check the current release documentation before planning a schema change.

Last updated: November 5, 2026. For the latest energy news and analysis, visit stakeandpaper.com.