PCS Facilities Traceability | Pipeline Week 2016

14
Facilities Traceability Brett Vogt, P.E. Project Consulting Services, Inc. Mind the Gap Between As-Built Redline Drawings and Documentation

Transcript of PCS Facilities Traceability | Pipeline Week 2016

Page 1: PCS Facilities Traceability | Pipeline Week 2016

Facilities Traceability

Brett Vogt, P.E.Project Consulting Services, Inc.

Mind the Gap Between As-Built Redline Drawings and Documentation

Page 2: PCS Facilities Traceability | Pipeline Week 2016

Ever Seen This?

Page 3: PCS Facilities Traceability | Pipeline Week 2016

Can you read it all?

Page 4: PCS Facilities Traceability | Pipeline Week 2016

Problems• 49 CFR 192 and 49 CFR 195 require asset-level

traceability for pipelines and pipeline-related facilities

• Redlines are the only as-built deliverables with traceability data for facilities

• Redlines are prone to illegible data, and sometimes incompleteness or inaccuracy

• Systems to ensure data is traceable, verifiable, and complete are inefficient

Page 5: PCS Facilities Traceability | Pipeline Week 2016

A Data Problem• 49 CFR 192 and 49 CFR 195 require asset-level

traceability for pipelines and pipeline-related facilities

• Redlines are the only as-built deliverables with traceability data for facilities

• Redlines are prone to illegible data, and sometimes incompleteness or inaccuracy

• Systems to ensure data is traceable, verifiable, and complete are inefficient

Data Standards

Final Data Set

Data Collection

Data Validation

Page 6: PCS Facilities Traceability | Pipeline Week 2016

What it looks like

Page 7: PCS Facilities Traceability | Pipeline Week 2016

Engaging Stakeholders

• Highlight the standards: – “reliable, traceable, verifiable, complete”

• Explore how technology can make existing systems more robust

• Customize processes to projects• Agree on a standard data collection

process

Page 8: PCS Facilities Traceability | Pipeline Week 2016

Data Collection

• Provide P&IDs and ISOs specifically created for traceability to be completed on a tablet or laptop

• Inspectors complete the traceability P&IDs and ISOs on the tablet or laptop

• Completed P&IDs and ISOs submitted to a central repository

Page 9: PCS Facilities Traceability | Pipeline Week 2016

Data Validation

• Validate data entered on P&IDs and ISOs versus data from documentation– Algorithm looking for gaps in traceability

against documents in an EDMS• Flag discrepancies and report immediately

– Correct discrepancies on as-built reports– Find missing documentation

Page 10: PCS Facilities Traceability | Pipeline Week 2016

The Deliverable• Close gaps discovered in Data Validation

phase• Build an interactive “job book” with report

hierarchy:– Facility map– P&IDs– ISOs

• Link to key traceability documentation for all components

• “Job book” can be searched with keywords

Page 11: PCS Facilities Traceability | Pipeline Week 2016

Demonstration

Page 12: PCS Facilities Traceability | Pipeline Week 2016

Lessons Learned• Complete traceability is possible in a facility

– Requires engagement for filling in gaps found in the validation and reporting process

• Technology adoption is always a challenge, and experience managing field personnel is critical to build trust

• Be able to support inspectors that do not embrace the system during transition

Page 13: PCS Facilities Traceability | Pipeline Week 2016

Conclusion• Asset-level traceability is required on

pipeline facilities• Plan for traceability in facilities• Introduce the end goals and any necessary

technology as early as possible• Complete traceability is possible in facilities

by combining planning, technology, and communication to the entire project team

Page 14: PCS Facilities Traceability | Pipeline Week 2016

Contact InformationBrett Vogt, P.E.

Project Consulting Services, Inc.

[email protected]