The Data Standards for New Pipeline Construction. Joint PODS and IPLOCA Workgroup

Transcription

1 The Data Standards for New Pipeline Construction Joint PODS and IPLOCA Workgroup

2 About PODS Pipeline Open Data Standard d Missioni The PODS Association s mission is to develop and support open data storage and interchange standards to meet the needs of the pipeline industry.

3 About PODS Pipeline Open Data Standard d The PODS Pipeline Data Model is the globally recognized g y g industry standard for pipeline data management. PODS provides pipeline operators an open, vendor neutral, highly scalable, and proven database architecture to integrate critical life cycle records, inspection, and analysis ii llif l i i d l i data, with geospatial information. PODS is a voluntary standard, collaboratively developed and maintained by pipeline industry members. pp y

4 About PODS Pipeline Open Data Standard d PODS Membership by Location* 122 member companies as of August 15, 2012 Greece France Germany Kazakhstan Indonesia Norway India Russia Ukraine United Arab Emerates United Kingdom Canada Austria Australia United States

5 About PODS Pipeline Open Data Standard d

6 Centerline Inline Inspections Design and Construction Data andconstructiondata Risk Analysis Results Geographic Features Links to External Documents Physical Inspections US Regulatory Compliance Compression Site Facilities CathodicProtection Offshore About PODS Pipeline Open Data Standard d Damage Prevention & One Call Domains, Domains, Domains Data managed by PODS

7 About PODS Pipeline Open Data Standard d PODS Implementation Methods Implementation method is determined by each each operating company. Some relevant factors include: Company philosophy Planned integration Technology paths Support resources Available applications IT infrastructure PODS Standard Relational Open Spatial ESRI Spatial

8 About IPLOCA International Pipeline & Off Shore Contractors Association ti lpi li t t i ti Mission (abbreviated) To promote, foster and develop the science and practice of develop the science practice of constructing onshore and offshore pipelines. To promote good and co operative relationships amongst the Membership of the Association and between contractors, owners, operators, statutory and other organizations and the public generally. Membership 255 member companies Large construction companies and engineering companies ti i i i i Majority of IPLOCA member companies are international

9 About IPLOCA International Pipeline & Off Shore Contractors Association ti lpi li t t i ti Novel Construction Initiative Publish the Road to Success best practices for onshore pipeline construction Mission Stimulate innovation in the technology and processes required for execution of onshore pipeline projects by engaging all contributors to the pipeline construction supply chain.

10 About IPLOCA International Pipeline & Off Shore Contractors Association ti lpi li t t i ti Novel Construction Initiative

11 Work Group Formation Future Trends and Innovations Group Data standards for new construction was first introduced in the Road to Success Volume 1 Led by the Future Trends and Innovations Group. It was suggested to adopt the PODS model, but the tdt d tth d l tth model dl concentrates on O&M and does not have a structure for new construction. In March 2012, the NOVEL Forum invited the Executive Director of PODS, Janet Sinclair, to be part of the NOVEL meeting and put forth the idea of a joint working group with PODS to create a world wide data standard for new ithpods t t id d t t d d f pipeline construction.

12 Key Drivers Compliance (Regulations post San Bruno) no) Traceability Quality Assurance Interoperability Project Monitoring and Control

13 Key Drivers If the data is already in an industry standard (PODS) format: Money can be saved and better, more accurate data developed. GIS software tools (automated alignment sheet generation, and web based GIS viewing and reporting applications) can be utilized. applications) can The project database (now PODS) can be tapped into to share project information across participants. Data is easily moved from the Operator s PODS database into the construction workflow at initial stages of the project and back to the Operator s PODS database at completion of the project. of the project

14 Objectives Adapt the PODS Pipeline Data Model for use during the design and construction phases for both onshore and offshore pipelines. pp Streamline the transfer of critical as built information from the construction workflow into the Operator s PODS database. Document the data and metadata requirements throughout the pipeline project stages, identifying the gaps between the new projectstages, identifying the gaps the new project requirements and the current PODS data model, and allow industry stakeholders to speak a common language of well defined data requirements. data

15 Objectives

16 Work Group Plan May Kick off meeting held. August Charter submitted to the PODS Board of Directors h d i for Approval. Leadership Appointed i d Chair Cheryl Bradley, Chevron (PODS) Co Chair Michael Gloven, Petro IT (IPLOCA) Charter focused on Data, Process Requirements and Scoping (Phase 1)

17 Scope Study the use of PODS Pipeline Data Model during the design and construction phases of a new pipeline construction project. Identify all states or stages and the essential data elements that should be collected at each stage of the process including the type and data requirements of key survey data. y Perform a gap analysis between the new project data requirements and the current PODS data model. Study how pipeline stationing and centerline representation is managed through a project lifecycle.

18 Deliverables Project data document including survey data requirements. Gap analysis study document to include recommendations on the type of modification needed to the PODS model, including new tables, or additions to existing tables to bridge the gaps additions to existing to bridge the gaps identified. A Draft Phase 2 PODS Workgroup charter for consideration by the Board.

19 Future Project Phasing and Deliverables Phase 2 Feasibility and Preliminary Design (Logical) y g Develop specifications for required PODS enhancements, and interchange process. Develop data dictionary. Develop plan and estimates for Phase 3.

20 Future Project Phasing and Deliverables Phase3 Phase 3 Detail Design (Physical) Design Develop physical data model. Develop detailed design for interchange process. Joint IPOCA PODS document for Model Update Process.

21 Sub Teams Established 4 sub teams, plus a steering committee, each is meeting once or semi monthly. Design, Engineering & Material Logistics Data & Process Requirements Team Captain: Lee Davis, Worley Parsons Field Survey Data & Process Requirements Team Captain: Terry Strahan, Morris P. Hebert Construction Activity Data & Process Requirements Team Captain: Elissa Adams, CH2MHill CH2MHill Operations Activity & Process Requirements Team Captain: Rob McElroy, McElroy Consulting Cons lting

22 Sub Team Status Design & Engineering (FEED/FEL) Gathering data management best practices, Polling PODS membership, andpods Examining different phases of design work regarding: PODS feature and table gaps Management of change and Stationing Domain lists Relationships Offline and landbase features

23 Sub Team Status Construction Compiling definitions of meta data related to construction activities of meta data to activities 1. Pipe Receiving 2. Survey and staking 3. Clearing 4. Front end grading 5. Topsoil stripping within ROW 6. Restaking centerline of trench 7. Stringing 8. Initial weld 9. Final weld 10. X ray inspection, weld repair 11. Coating field welds ed eds 12. Trenching 13. Inspection and repair of coating 14. Lowering pipe into trench 15. As built survey 16. Pad, backfill, rough grade 17. Hydrostatic testing 18. Replace topsoil, restoration

24 Sub Team Status Field Survey Identifying PODS extensions and modifications to support Field Survey Activity Mapping existing table attributes to new Field Survey features Defining data dictionary Examining domain/code specifications

25 Sub Team Status Operations Defining data requirements to be transferred between the construction activities and Operator s s PODS database PODSdatabase Polling Operators regarding: Typical formats, and lf Document and data transfer processes Coordinate Depth_of_Cover DOT_Class Drip_Riser Elbow Exposure External_Coating Flange Foreign_Line_Crossing Ground_Bed HCA_CA_Segment Internal_Coating Land_Use Launcher_Receiver MAOP_Rating Marker Meter Pig_Signal Pipe_Bend Pipe_Join Pipe_Segment

26 GIS Emphasis Growing GIS User Community Growing light weight and simplified tools available Collaborative, Web based Wbb Growing regulatory specifications with spatial definitions Project and frequent revision based nature of new construction Growing field data collection and GPS process integration

27 Challenges Ahead GIS Emphasis & DBA resources Process & Quality Management Pipeline Stationing Domain/Code Standardization d di ti Education & Usability

28 Status Continuing to meet while Charter is reviewed and approved by the PODS Board of Directors. PODSBoardof Directors. Deliverables presented to PODS BoD at end of each phase for review/approval to continue. lt ti Collaborative documentation is taking place on the IPLOCA Wiki. Data requirements gathering and documentation ongoing Data requirements gathering and documentation ongoing and no limit to participation. Contact Cheryl Bradley, Michael Gloven, or Janet Sinclair to get involved.

29 QUESTIONS?