Pipeline SIG PODS Pipeline Open Data Standard Ron Brush New Century Software, Inc.
Special Thanks to ESRI PUG Special Thanks to ESRI PUG! Bill Wally - Chevron Dave Frye - ESRI Andrew Zolnai - ESRI
Meeting Agenda 2:00 - 2:30 - Ron Brush 2:30 - 3:00 - Tracy Thorleifson Introduction to PODS Association 2:30 - 3:00 - Tracy Thorleifson Technical Discussion of PODS 3:00 - 3:30 Future Directions
PODS Purpose To develop and promote standards for the exchange and storage of data in the pipeline industry. The PODS data model is particularly related to geo-spatial information for pipelines.
What is PODS Today? Enterprise pipeline data model Facilities, Compliance, Inspections and more 300+ tables The PODS Association Group of pipelines and vendors who help define and implement useful pipeline data standards
Three Viewpoints A design approach An example for pipeline companies to use A data model that can be implemented
The PODS Association Incorporated August 2000 Seeking new members Membership: $1000 per company per year Supported by ESRI, GTI www.pods.org
PODS Contributors Williams Gas Pipelines ESRI Dynamic Risk Assessment Eagle Information Mapping GeoFields New Century Software Bass-Trigon Software Stoner Associates Kinder Morgan Reliant Energy TransCanada Pipelines Coral Energy Conoco Chevron Dynegy PPDM plus Others
Brief History Initiated in 1998 by GRI Volunteer membership to date Core group of members contributing their knowledge Developed the PODS data model based on earlier Williams work Incorporated parts of ISAT
Brief History One goal was to establish an industry association to further support and develop the work Incorporated August 2000 Profit -- Not-for-profit Membership letter sent out in January To date -- 3 members, plus more to come
General Structure Board of Directors Officers Workgroups Technical Implementation Direction Committee Public Relations - Marketing
Board of Directors Keith Leewis - GTI (formerly GRI) Tim McCallum - Advanced Data Design Kenneth Greer - Reliant Energy J.B. Padgett - Eagle Information Mapping Ron Brush - New Century Software
Officers Ron Brush - Interim President Kenneth Greer - Secretary Tim McCallum - Treasurer
Benefits of Joining Input into model development Input on organizational structure Networking/communications Acquiring best practices Forum for resolution and implementation issues
Benefits of Using PODS Comprehensive data model Less risk in implementing GIS The more companies that use it, the easier it will be to integrate applications Applying best practices - evolving Association directed and driven
More Information www.pods.org Literature available Ask Membership Letter Bylaws Executive Summary Hardcopy printout of data model Ask
Perspectives on PODS...
ISAT 1.0 - Areas to Enhance No support for multiple sources of coordinate data No direct support 3D centerlines No support for multiple versions of pipeline centerlines Limited support for historical tracking Limited support for modeling branching pipeline systems (gathering / distribution systems) No support for “network” topology (required for flow modeling) Limited support for inspection data
PODS – Core Tables Line Route Series Station Point Event
PODS – Coordinate Tables Line Coordinate Source Route Series Coordinates Location Station Point Centerline Geometry Event
PODS – Line Hierarchy Tables Connection Route Series Station Point Event
PODS – Network Tables Line Route Series Network Station Point Junction Event Segment
PODS – Inspection Tables Line Route Series Inline Inspection Station Point Physical Inspection Event Event Group CP Inspection Work Order
Future Directions
Short-Term Goals Membership Promotion Election of Officers Publish a PODS CD PODS DDL Domain (lookup) table values Example applications Documentation Sample Database
Other Goals More pipelines implementing PODS More vendors writing PODS applications Approve inspection pigging submodel
Planned Enhancements Improve Inspections and Maintenance Submodel Compressor Station - Emissions Better Documentation Published Domain Tables
Future Directions Extensions or new models for: Gathering Distribution Liquids
Future Directions Integration with ArcSDE Geo-database Networking Versioning Connectivity - Trace Network
Future Enhancements Example GPS Data Dictionaries Easier to load data into PODS Improved domain tables XML Schemas
Applications Data Loading Tools Data Maintenance Tools Sheet Generators Analysis Tools Construction Integration Inspection and Maintenance Compliance Assistance Tools
Applications Bridges to Third-Party Applications Risk Assessment Flow Modeling SCADA Land Records Cathodic Protection
More Information www.pods.org Literature available Ask Membership Letter Bylaws Executive Summary Hardcopy printout of data model Ask
Again, Special Thanks to ESRI PUG!
Questions... Discussion...