Database Architecture for a Linear-Referenced Database
The PODS Pipeline Data Model provides the database architecture pipeline operators use to store critical information and analysis data about their pipeline systems and manage this data geospatially in a linear-referenced database which can then be visualized 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.
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.
A Repository for Mission-Critical Data
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
- valves and pipeline components
- cathodic protection facilities and inspection results
- operating conditions
- physical inspection results
- leak detection surveys
- 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
‘Open’ – A GIS Neutral –or– ESRI Compatible Platform
PODS can be implemented via traditional RDBMS database platforms, 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 and vendor area for additional information on PODS-ready applications.
A Pipe-Centric Approach
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.
A Holder of Important Historical Records
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.