1 / 11

API 17N Subsea Production System Reliability and Technical Risk Management

API 17N Subsea Production System Reliability and Technical Risk Management. Don Wells Hess Corporation. History / Status. Document released in 2009 Specificatio n contains: Life Cycle Process ( LCP ) Define, Plan, Implement, Feedback ( DPIF ) Loop 12 Key Practices ( KP )

robbin
Download Presentation

API 17N Subsea Production System Reliability and Technical Risk Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. API 17NSubsea Production System Reliability and Technical Risk Management Don Wells Hess Corporation

  2. History / Status • Document released in 2009 • Specification contains: • Life Cycle Process (LCP) • Define, Plan, Implement, Feedback (DPIF) Loop • 12 Key Practices (KP) • Technology Qualification Process • Technology Readiness Level

  3. Plan / Path Forward • Process • Split into 5 subgroups (now 6) • Industry Leaders • Common Template • Introduce IM into the scope of 17N: • Define IM • Expand the Life Cycle Processes • Reassessment through remediation • Define TRL progression

  4. Detail • Expand the LCP • Provides balance and depth to the document • Communication of goals & requirements

  5. Detail • Change to a Dual-DPIF loop • Add Remediation cycle • Facilitates Integrity Management

  6. Current Progress • We are in the middle of the “Design Spiral” • We are revising TQL levels from 0-7 to 1-9 • We are adding comments on “Safety” to comments on Integrity • We are considering adding “E” (Evaluate) to DPIF Spiral →DFIEF • We are moving forward as a separate Step • Will reevaluate after completion of effort to consider making it an overlying requirement / reminder • Addition of Decommissioning may delay completion

  7. Specification Development

  8. Specification Development

  9. We need your feedback and help! • Human Factors • Communication from Ed Baniak – May 2, 2013 • How does your company currently assess human reliability? • Does you have a dedicated group to assess human reliability ? • If not, how is the work currently performed?   • What is the perceived need for human reliability by your projects? • Do you request human reliability assessments from your suppliers/subcontractors?

  10. Next • Remaining challenges: • Incorporating Human Factors • Competency of People • Decommissioning (Well Abandonment) • Document Matrix • Technology Qualification Appendix • 17N is currently in first edition drafting • Final Draft Review late-Q22013 ? • Peer & Industry Review Q32013 ? • Submittal Planned Q42013 ?

  11. Thursday Invitation: • Reliability, Availability, and Integrity Management Forum • Thursday Morning June 27th from 8:00 – Noon Intention: • Leave with an understanding of where the various API committees have either common goals or needs • Can we use 17N as a framework across API? • Agree a Path Forward. Agenda: • Overview of API 17N and Current Revision Activities (Don Wells) • Issues 17N (John Strutt) • Issues - Other API Committees – Open Discussion (John Allen / Jim Raney) • Current Boundaries and What’s Next (John Strutt) • Agree Common Plan to address issues raised – ALL!

More Related