Blueprints for Industry Excellence

PODS Data Models

The PODS Data Model organizes, standardizes, and manages pipeline data for integrity, compliance, and operational efficiency.

PODS for ArcGIS Enterprise

The PODS Data Model was built for regulated pipeline and is continuously updated as new regulations are published. In fact, PHMSA is a PODS member and uses the model as a baseline for NPMS, so having your data in PODS is the easiest way for operators to submit their annual reports and NPMS uploads.

At its most basic level, an ArcGIS geodatabase is a collection of geographic datasets of various types held in a common file system folder. Geodatabases come in many sizes; have varying numbers of users; and can scale from small, single-user databases built on files up to larger workgroup, department, and enterprise geodatabases accessed by many users.

Our vision is to align more with the needs of operators, especially those with multiple types of assets, and offer specific data solutions geared towards risk, regulation, and compliance. PODS will now offer two core data models – PODS 7 and PODS 7 Utility Network with the option to add regulatory and industry specific modules quickly and cost effectively.

Esri’s Advantage Program is an enablement program for organizations to optimize their use of Esri technology and accelerate business initiatives with the strategic guidance of Esri experts. The program has a flexible framework to provide customers with hands-on support from Esri consultants, instructors, and tech support staff. Each organization is paired with an Esri Advisor who has industry domain knowledge, and through close collaboration and partnership the Advisor becomes familiar with their GIS capabilities, working to ensure they stay at the forefront of Esri resources, technology, and best practices. Unique to the PODS Association, the PODS Advantage Program with Esri will focus on maximizing the technical alignment of products offered by both organizations to enhance end-user experience when using industry-standard data models with ArcGIS.

There are currently two main geodatabase implementations of PODS for ArcGIS Enterprise

1. PODS for ArcGIS Enterprise + ArcGIS Pipeline Referencing (APR)

The out of the box PODS for ArcGIS implementation requires only ArcGIS Pro Standard plus an ArcGIS Pipeline Referencing extension for ArcPro. ArcGIS Enterprise is not required.nor are any ESRI software extensions. Pipeline location is managed via an M-aware centerline and events are located by stationing attributes on top of the centerline (as ‘route events’).
Learn more about ESRI linear referencing and route events here. This version requires the ArcGIS Pipeline Referencing extension for ArcPro

As an expansion of PODS for ArcGIS Enterprise Standard, users can implement PODS with the ESRI ArcGIS Pipeline Referencing extension. This extension will allow the ESRI platform to manage all centerline and event editing processes. This version requires ArcGIS Enterprise, and the ArcGIS Pipeline Referencing extension for Server, and the ArcGIS Pipeline Referencing extension for ArcPro. Learn more about ESRI ArcGIS Pipeline Referencing extension here.

2. PODS for ArcGIS Enterprise + ArcGIS Pipeline Referencing (APR) with Utility Network

This PODS Utility Network + APR Implementation Pattern release combines the centerline and feature management components of the ArcGIS Pipeline Referencing extension with the to create traceability, containers, and data integrity management features of the ArcGIS Utility Network extension. When implemented at the Enterprise level, this version requires ArcGIS Enterprise, the ArcGIS Pipeline Referencing extension for Server and the ArcGIS Pipeline Referencing extension for ArcPro.the Utility Network extension.

Learn more about Esri Utility Network extension here.

Learn more about PODS 7.0 for Utility Network + APR here.

Hear Jeff Allen talk about the release on the Pipeliners Podcast here.

New PODS Modules, Focused on Integrity and Regulation: Opening the Model to More Pipeliners

Now more than ever, visibility and optimization of in-ground assets are vital to our industry. The rising cost of failure, the public’s focus on pipelines and the energy future, and the need for data transparency and accuracy to meet new regulations and newly regulated assets… everything is changing, so PODS is also!

The PODS Data Model was built for regulated pipeline and is continuously updated as new regulations are published. In fact, PHMSA is a PODS member and uses the model as a baseline for NPMS, so having your data in PODS is the easiest way for operators to submit their annual reports and NPMS uploads.

Our vision is to align more with the needs of operators, especially those who manage assets within various segments of the pipeline supply chain. PODS will now offer two core data models - PODS 7.0 and PODS 7.0 with Utility Network support. Both these core models will have the option to add to them regulatory and industry specific modules. With PODS standardizing on the core Esri Geodatabase, operators who have implemented the Esri Utility and Pipeline Data Model (UPDM) can also leverage these industry specific modules within their implementations.

PODS Modules

01 ir

IR – Integrity Regulatory

Traces how IMP activities drive the repairs in the field while supporting submission of annual reports (192, 195 and TX RRC) thus improving project prioritization, identifying why you performed a task, and supporting risk analysis and calculations.
02 tvc

TVC – Traceable, Verifiable, Complete

Organizes data for calculation of operating pressure in compliance with Gas Mega, Gathering and proposed Distribution Rules as well as Hazardous Liquids Rules.
03 ili

ILI – Inline Inspection

Stores all ILI data with millions of data points, allowing run-to-run analysis no matter the vendor tool.
04 cp

CP – Cathodic Protection

Integrates reporting features for in-depth cathodic protection analysis for optimized operations, while meeting the reporting requirements outlined by PHMSA.
05 sl

SL – SCADA Link

Includes physical ties to sensor locations along a pipeline system, such that the volume factors for line pack calculations can be automated via a Unique ID that links back to SCADA.
06 off

OFF – Offshore

Houses and standardizes data attributes specific to offshore pipeline systems for the first time, allowing links to 3D data for the ability to “walk the line” thousands of feet below sea level.