PODS Design Standards

The PODS Pipeline Data Model provides the database architecture pipeline operators use to store critical information organized for usability and analysis about their pipeline systems. It is paramount that this data is managed geospatially in a linear-referenced database which can then be visualized as a digital twin in any GIS platform.

This linear reference system incorporates location information with every record stored in the database. The ‘address’ or engineering station describes either a linear section of the pipeline or a point where that record applies.

In a similar manner, the same linear referencing system is used to locate, and effectively overlay, inspection reports, events, activities, or features, which occur on or near the pipeline. This is important for any operational, maintenance or field activity in that it promotes project prioritization, efficiencies and compliance to every regulation based on opportunistic field data capture.

PODS also allows for external documents such as reports, procurement records, hydrostatic test charts, or even photographs, to be linked to the physical assets they describe.

The PODS Pipeline Data Model houses the asset information, inspection, integrity management, regulatory compliance, risk analysis, history, and operational data that pipeline companies have deemed mission-critical to the successful management of natural gas and hazardous liquids pipelines.

Typical information stored in a PODS database includes (partial list):

• centerline location
• pipeline materials and coatings
• MAOP
• valves and pipeline components
• cathodic protection facilities
• inspection results
• hydrotesting
• operating conditions
• physical inspection results
• leak detection surveys
• repairs
• foreign line crossings
• inline inspection (ILI) results
• close-interval survey results
• pump and compression equipment specs
• geographic boundaries
• external records
• risk analysis methods and results
• regulatory reports
• pipeline and ROW maintenance activities

PODS can be implemented via traditional databases, such as Oracle or SQL Server, or integrated within the ArcGIS Enterprise platform, utilizing a versioned geodatabase.

The data model itself is designed based on standard design principals in a well-documented manner which allows for easy development of addon-applications, scripts and business intelligence integrations. Visit the PODS member listing to find providers for additional information on PODS-ready applications. Or you can email info@pods.org.

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.

This pipe-centric approach to managing pipeline data in a single data repository, a PODS database, helps pipeline owners to collect, verify, manage, analyze, update, maintain, and deliver all the information about their pipelines quickly and reliably to applications and end-users. Since the data records are linked to the pipe segment, re-route, change of service, asset transfer or sale, abandonment, removal, repair, and replacement are all managed within the PODS database.

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.

The PODS Pipeline Data Model is configurable to maintain history of important data records, and accommodates history tracking for re-routes, replacement, looping, coatings, maintenance, crossings, inspections, testing, operations, new data sources (such as GPS), engineering analyses, and regulatory reports, among others.

the PODS ILI, IR, CP and TVC modules work very well to house records specific to regulation and integrity management.

• ILI – Inline Inspection
  Stores and standardizes millions of ILI data points, enabling run-to-run analysis across different vendor tools.
• IR – Integrity Regulatory
  Supports submission of regulatory reports (192, 195, TX RRC) by tracking IMP activities, prioritizing projects, and aiding risk analysis.
• CP – Cathodic Protection
  Provides detailed cathodic protection reporting for optimized operations, aligned with PHMSA requirements.
• TVC – Traceable, Verifiable, Complete
  Organizes data for calculating operating pressure in compliance with Gas Mega, Gathering, and Hazardous Liquids Rules.