130 likes | 268 Views
API RP 17N Subsea Production System Reliability and Technical Risk Management & Integrity Management. 19 th January 2012 Don Wells (Hess). Agenda. Introduction Scope Membership General Progress Detail Progress Integration 17 Committee/ISO. Introduction.
E N D
API RP 17NSubsea Production System Reliability and Technical Risk Management& Integrity Management 19th January 2012 Don Wells (Hess)
Agenda • Introduction • Scope • Membership • General Progress • Detail Progress • Integration 17 Committee/ISO
Introduction • Incorporate Integrity Management into current API 17N …Subsea Reliability and Technical Risk Management • Recognize and incorporate integration with other Industry initiatives • Incorporate updates based on feedback from using existing 17N document • Respond to recent industry experiences
Scope • Review of Summer Meeting topics • Continue previously presented scope • Additional scope – API 17A requirements Design and Operations of Subsea Production Systems • Greenfield • Brownfield • Future requirements
Membership • Organized into subcommittees • Design and Decommission • Manufacture, Assembly, SIT, Installation, Commissioning • Operations • Technology Qualification • Regulations • Room for additional membership • Opportunity to Make a Difference
General Progress • 2010 – 2011 • Storming and forming - Complete • Gap Analysis – Mostly Complete • Interfacing with Runar Østebø – • Statoil & convener of ISO/TC67 WG4 • 2012 - Planned • Define Tone (prescriptive / recommend) • Work the Gaps • Work the Interfaces • Industry Peer Assist Workshop • SURF IM Forum
Detail Progress • Define Scope - Completed • Define Charter – Completed • Divide and Conquer • Design and Decommission • New Key Process (KP) for Through Life to be Developed • Does API want Risk Based or Safety Case Approach? (Hybrid?) • Do we want/need to meet with BSEE to discuss?
Detail Progress • Divide and Conquer • Manufacture, Assembly, SIT, Installation, Commissioning • Matrix Developed • Where & How to test being worked • Does Verification and Validation need new KP? (Rewrite KP06?) • MOC being worked
Detail Progress • Divide and Conquer – cont. • Operations • Reviewed and Raised issues with existing 12 KPs • Proposed 3 additional KPs • Field Modifications • Inspection and Monitoring • Remedial Intervention • Added 3 Processes to “Project Phase Guide to Processes”
Detail Progress • Divide and Conquer – cont. • Technology Qualification • New Risks Identified • Obsolescence – Misuse of TRLs • New Technologies • New materials • Keep integrated as a section in API 17N • If not, make it a Technical Reference • Make Generic vs. Prescriptive • Robust, Goal Based with examples • Utilize DNV RP A-203 as much as possible • Evaluate the use in early conceptual phase • Survey Industry to ID Qualifying Technologies main challenges
Detail Progress • Divide and Conquer – cont. • Regulations • Managing Committees 1-4 Interfaces • Will lead Prescriptive vs. Recommend discussions • On hold until more definition / decisions from other committees
Path Forward • Path Forward • Continue Subcommittee work • Outline of Process to use as QA tool • Common Matrix to combine / review completed work • Work the idea of using SURF IM Forum to discuss with industry and gather additional input • Write • Review • Ballot
Interface / Integration • API 17A, API Q1 • ISO • 14224 - Collection and exchange of reliability and maintenance data for equipment • 20815 - Production assurance and reliability management • 15663 - Life Cycle Costing • TR 12489 - Reliability modeling and calculation of safety systems • Review committee draft document • Feedback 17N specific comments • DNV RP A203/API RP 17Q?