2012 FEPA Presentation: Erik Kirkpatrick
- 1. MAOP Verification Best Practices Florida Energy Pipeline Association – July 18, 2012 Eric Kirkpatrick Director – Pipeline Services Structural Integrity Associates, Inc. www.STRUCTINT.com 877-4SI-POWER
- 2. Webinar Objectives • Brief Overview of PHMSA Guidance • Best Practices learned from MAOP projects • Q&A (Please hold questions until the end) Best Practices of an MAOP Verification Program- SLIDE 2
- 3. About • Founded 1983 • Headquartered in San Jose with offices in Denver, Salt Lake City, Charlotte • 230 employees • Specialists in Pipeline Integrity Management • MAOP Verification • Software and Data Acquisition Systems • Non-Destructive Examination (NDE) and field services Best Practices of an MAOP Verification Program- SLIDE 3
- 4. About • Founded 1998 • Offices in Chico and Walnut Creek Ca. • 140 employees and growing • Certified woman owned business by the California PUC • Senior staff of previous utility leaders in Gas Transmission and Distribution • Recognized with 2011 Small Business of the Year Award by PG&E • Proven performance in MAOP Verification, Hydrostatic Test Engineering, Pipeline Engineering, Quality Assurance and Compliance Auditing. Best Practices of an MAOP Verification Program- SLIDE 4
- 5. MAOP Verification PHMSA Guidance April 22, 1998 - PHMSA 1998 Guidance Document – Determination of Maximum Allowable Operating Pressure in Natural Gas Pipelines September 9, 2010 – San Bruno Pipeline Rupture January 10, 2011 - PHMSA Advisory Bulletin (ADB-11-01) - Establishing Maximum Allowable Operating Pressure Using Record Evidence (source of “Traceable, Verifiable and Complete” and “ensure company records accurately reflect the pipelines physical and operational characteristics”) Best Practices of an MAOP Verification Program- SLIDE 5
- 6. MAOP Verification PHMSA Guidance May 7, 2012 - PHMSA Advisory Bulletin (ADB-12-06) – Verification of Records Establishing MAOP and MOP Traceable = clearly linked to original information Verifiable = confirmed by other complementary, but separate, documentation. Complete = finalized as evidenced by signature, date or other appropriate marking Operators to submit data via the 2013 Annual Report PHMSA intends to act on NTSB recommendation to eliminate the Grandfather Clause Best Practices of an MAOP Verification Program- SLIDE 6
- 7. Start with a Specific Plan Best Practices of an MAOP Verification Program- SLIDE 7
- 8. Best Practices of an MAOP Verification Program- SLIDE 8
- 9. MAOP Project - SCOPE Options Scope of Effort Benefit Concerns Only Class 3 and Class 4 Limited Scope may result Ongoing evaluation locations and Class 1 and in faster completion of required for class location Class 2 high consequence evaluation changes and new HCAs. areas. All Transmission No ongoing evaluation of Completion may take class locations and new longer. HCAs required. More verified knowledge of system. New Construction Evaluate whether existing processes are adequate. Eliminate future MAOP verification re-work!!!! Non-MAOP data Efficiency, only 1 review of May impact schedule records Best Practices of an MAOP Verification Program- SLIDE 9
- 10. Best Practices of an MAOP Verification Program- SLIDE 10
- 11. MAOP Criteria • Design Criteria – Pipe • Design Criteria – Standard Fittings (e.g. elbows, tees) • Design Criteria – valves, flanges, fittings • Pressure Test – constructed prior to November 1970 • Pressure Test – constructed after November 1970 • Historic Operating Pressure – 5 yrs. preceding July 1, 1970 • Maximum Safe Pressure • Subpart K Uprates • §192.611 provisions for change in class location and confirmation of MAOP • State Specific Requirements?????? Best Practices of an MAOP Verification Program- SLIDE 11
- 12. PHMSA 1998 Guidance Document – Determination of Maximum Allowable Operating Pressure in Natural Gas Pipelines Part 192.619(a)(1) Design Pressure: Lowest design pressure Part 192.621(a)(1) for any of the following system elements Pipe (including service lines) Valves Flanges Fittings Mechanical Couplings Leak Clamps Instruments Odorizers Overpressure protection devices Upstream Regulator(s)-Outlet Pressure Rating Downstream Regulators-Inlet Other (list) Best Practices of an MAOP Verification Program- SLIDE 12
- 13. Best Practices of an MAOP Verification Program- SLIDE 13
- 14. Illustration of Key Data required to support MAOP • Current Class Location • Component nominal outside • Current Pipeline MAOP diameter • • Component ASA/ASME/ANSI Date of Operation Rating • Converted under 192.14? • Component Max Working • Pipe Grade Pressure • Pipe Nominal Outside • Road crossing or encroachment Diameter with no casing? • Pipe Wall Thickness • Railroad crossing or • encroachment with no casing? Pipe Longitudinal Joint Type • Supported by bridge? • Component Type (e.g. Valve, • Compressor Station, Regulating Flange, Elbow) Station, or Metering Station? • Component Grade • Component wall thickness Best Practices of an MAOP Verification Program- SLIDE 14
- 15. Illustration of Key Data required to support MAOP • Minimum Actual Test Pressure • Recording Chart or Record of • Pressure Test Date Pressure Readings? • Operator Name at • Highest Elevation Construction • Lowest Elevation • Name of Operator's employee • Recorder Elevation responsible for making • Leaks and Failures & pressure test Disposition noted • Name of any Test Company • Date that Historic Operating used Pressure was recorded • Test Medium Used • Historic Operating Pressure • Test Duration • Uprate Test Date • Uprate Test Pressure Best Practices of an MAOP Verification Program- SLIDE 15
- 16. Best Practices of an MAOP Verification Program- SLIDE 16
- 17. What Records are Applicable? Where are they? Best Practices of an MAOP Verification Program- SLIDE 17
- 18. Inventory of Target Data by Record Type Illustrative example only Best Practices of an MAOP Verification Program- SLIDE 18
- 19. Identification of Valid and “Verified” Record Sources? Best Source – Consider Verified if confirmed by other 1 complementary record. Illustrative example Acceptable Source – Consider Verified if confirmed by only 2 other complementary record. May be used as a complementary record. May only be used as a complementary record. 3 4 May not be used Practices of an MAOP Verification Program- SLIDE 19 Best
- 20. Completeness? Signature? Date? Best Practices of an MAOP Verification Program- SLIDE 20
- 21. Completeness Grading Document Quality – Illustrative Example: Test Pressure Doc ( Best Practices of an MAOP Verification Program- SLIDE 21
- 22. Best Practices of an MAOP Verification Program- SLIDE 22
- 23. Scanning Records • ADB-12-06 requires traceable records linked to original info • The benefit of scanning applicable records is to avoid future loss and establish easier traceability. • Scanned Images should reside on a server that is backed up for data loss prevention and security. • Establish protocols for moving, scanning and returning records; this is yet another opportunity to loose key records! • Avoid confusion, only scan the targeted records you need. • Consider pre-sorting records Best Practices of an MAOP Verification Program- SLIDE 23
- 24. Scanning Records • Establish metadata system to capture key aspects of every image (e.g. Pipeline #, Project Number, Document Type, Date, Unique ID #, etc.) • Establish rules for color vs. black and white, two-sided originals, scan resolution, format type, continuity of stapled documents, etc. • Index each image in a logical manner; consider linking data to the associated image in some manner. • Consider following same protocol for new construction records. Best Practices of an MAOP Verification Program- SLIDE 24
- 25. Best Practices of an MAOP Verification Program- SLIDE 25
- 26. Data Capture Considerations include: •Loss Prevention •Integration into other uses •Ongoing access or one-time project? Best Practices of an MAOP Verification Program- SLIDE 26
- 27. Example 1 Data from records identified that support pipeline features on transmission plat or other references and entered into MS Excel and MAOP calculated. Best Practices of an MAOP Verification Program- SLIDE 27
- 28. Example 2 Data from records entered into MS Access. Data Management and MAOP Calculation in MS Access. Final Verified Data resides in GIS Best Practices of an MAOP Verification Program- SLIDE 28
- 29. Best Practices of an MAOP Verification Program- SLIDE 29
- 30. Application of Conservative Defaults? Illustrative example Best Practices of an MAOP Verification Program- SLIDE 30
- 31. Best Practices of an MAOP Verification Program- SLIDE 31
- 32. RECORD EVALUATION Data Conflicts (same data element from different records) Evaluate Against Records Acceptance Criteria Best Practices of an MAOP Verification Program- SLIDE 32
- 33. Quality Control Considerations • 100% QC until confidence in process is established • Records not Meeting Protocols Go through Different Process – Operating Experience, Subject Knowledge – Engineers Best Practices of an MAOP Verification Program- SLIDE 33
- 34. Best Practices of an MAOP Verification Program- SLIDE 34
- 35. MAOP CALCULATION & VERIFICATION • Handwritten, Spreadsheet, Database, linked to GIS?? • Detail Process Flow • Validation & Verification of spreadsheets or software – Test Cases Best Practices of an MAOP Verification Program- SLIDE 35
- 36. Start with a Specific Plan Best Practices of an MAOP Verification Program- SLIDE 36
- 37. How to Contact Us SI: ekirkpatrick@structint.com GTS: www.gtsinc.us/contact-us/contact-us-1/ Best Practices of an MAOP Verification Program- SLIDE 37
Editor's Notes
- #2: 07/25/12 P91 / T91 Workshop