Presentation on theme: "Don Wells Hess Corporation"— Presentation transcript:
1 Don Wells Hess Corporation API 17N Subsea Production System Reliability, Integrity, and Technical Risk ManagementDon WellsHess Corporation
2 History / Status Document released in 2009 Specification contains: Life Cycle Process (LCP)Define, Plan, Implement, Feedback (DPIF) Loop12 Key Practices (KP)Technology Qualification ProcessTechnology Readiness LevelThis is what was delivered in the first revision of 17N
3 Initial Plan / Path Forward ProcessSplit into 5 subgroups (now 6)Industry LeadersCommon TemplateIntroduce IM into the scope of 17N:Define IMExpand the Life Cycle ProcessesReassessment through remediationDefine TRL progressionThis is what we originally reported that we would do.
4 Specification Development Expand the Life Cycle ProcessFeasibilityConcept SelectionFEEDDetailed DesignManufacturing & AssemblySIT, Installation, & CommissioningOperationDecommissioningThis represents Revision 1The second thing the committee did was agree we needed to add…….Hit button
5 Detail Change to a Dual-DPIF loop Add Remediation cycle Facilitates Integrity ManagementThis is what we have shown you as our progress in previous presentations, adding a second loop to cover Operations or Brownfield
6 Specification Development (Greenfield Projects) The red box represents the latest revision and its tie-in to what you have seen before. In addition to adding Integrity Management and additional depth to each of the key practices to the overall document, we added the “Evaluate” step to highlight You will also see the Note “Greenfield Projects” as an indication is that this process only takes it too the point of Installation and does not include Operations or changes during Operations or existing Assets.
7 Specification Development (Brownfield Projects) And it was equally important to the Operations or Brownfield phase of the Development...and acceptance criterion
8 Lifecycle Application of DPIEF Cycle . DPIEF Assurance Cycle applied at each lifecycle stageFeasibility through to decommissioningDouble DPIEF loop in operationsNormal operationsCorrective actionThis is how the full Life Cycle now looks with the addition of the last two stages covering from feasibility through DecommissioningWhen combined with the other stages, we call the two loops in the Operations stage Normal Operations and Corrective Actions
9 Progress Winter Meeting Workgroups Submitted InputUsing Common TemplateEdited into a Single DocumentAstrimarCirculated for Comment within 17N Committee3 rounds, 1,000+Last Comments Due Dec 10thClarification Discussions at Jan 13th meeting
10 Key Process Changes Kept Same 12 KPs from the First Revision Updated Names and Content to Accommodate the inclusion of Integrity ManagementWe also had to revise much of the details included in the Key ProcessesAs we increased the Scope of the document, we had to revise a number of the names to be less specific. For Example:“Organizing and Planning for Availability” became “Planning and Organisation”The main change in terms of the description and content of the KPs is the inclusion of Integrity and also additional recommendations for:The Preparation associated with implementing the Key PracticesSenior Management and Corporate level guidelinesProduct, Project, or Operations Management
11 Annex Changes Standardized and Significantly Updated Annex A – Split into Two Separate AnnexesAnnex A -Technical Risk & Uncertainty CategorizationAnnex C - Risk Based Scope of Work for Reliability Technical & Integrity ManagementAnnex B - Better Explanations and Guidance for ManagementAnnex D – New This will change to accommodate reincorporation of 17Q stuffIntegrity Management Data CollectionThe annexes which are a significant part of the document are also being significantly revisedAnnex A – ReadAnnex B was revised to provide Better………..Objectives & Preparation for Each Key ProcessRecommendations for Senior ManagementRecommendations for Project and Operations ManagementDetailed Process DescriptionThe Original Annex CAbsorbed into KP 9Annex DNew - Integrity Management Data CollectionThe Original Annex D is being absorbed into API 17Q which I will speak about shortly
12 Issues to be Addressed at High Level The following Subjects have been introduced and referenced without Full Fidelity:DecommissioningObsolescenceField Life ExtensionHuman FactorsConfiguration Management / MOCIntegration with Other Standards / Regulatory DocumentsThere are a number of subjects in the latest edition that are being addressed at a high levelThe list you see on the screen are subjects that referenced without full fidelity.When we say Not full Fidelity, we are not saying we have not done a good job or will deliver a quality document, we are saying that this is a subject that is maturing and that the Oilfield is incorporating on a continuous basis.It is recognized however that there are learnings being made on a continuous basis that we know will need to be worked and incorporated into future editions of the document.These include
13 17Q HistoryLast meeting, we were asked to consider combining 17Q into 17NWork indicated that this was not best approachRationaleDifferent SubjectsQualification Not Unique to 17NExpect Revision at a Different RateQualification /Verification details from 17N will be Incorporated into 17QAccepted by Committee 17
14 Technology Qualifications As work on the document progressed, it became obvious that:A great deal more effort was required to address all Qualification issuesThe field of Qualification was faster moving and less mature than Reliability and Integrity ManagementQualification needed to align with DNV A-203, API 17A, API 17QBased on the above, the 17N Qualification workgroup has recommended that the Qualification, Verification and Test Statistics content will be transferred to API 17QBut A funny thing happened on the way to the Forum:Committee 17 asked us if we could incorporate API 17Q – Qualification into our document17Q was…… set of instructions and forms designed to facilitate the qualification of similar components from different suppliers fairlyAs the committees progressed this request it became obvious to us that:A great deal of effort was required to address all of the issues associated with QualificationQualification and IM moved at a different paceQualification needed to be aligned with other Industry documentsCLICKSO it is our recommendation that the Qualification, Verification and Test Statistics should be incorporated into a revised 17QThe plan is that 17N will introduce the subject and its context, but the real bulk of the detail will be incorporated into API 17QThe 17Q and 17N committees are actively planning and working this recommendation for formal presentation before the API summer meetings.
15 17Q Plans/Progress Path Forward 17Q Committee reestablished to Work PlanMade up of members of both 17Q and 17NCurrently Working PlanIt was recognized and last Working Meeting that 17N and 17Q can progress at separate paces as long as 17N appropriately defines, references, etc.17N Workgroup 4 has done a great deal of work, but had visions of more details, etc. The working committee has agreed to first assess where we are, what our future is and a plan to get there. This will then be communicated to API and Committee 17 with an SRRR which defines the plan and resource requirements.
16 17N Progress Original Plans included a “Pre-Ballot” Workshop Change of PlansNot a New DocumentLarge Active CommitteePotential to Circulate to Washington Workshop attendeesOK?OTC Paper submitted and PresentedAs part of API 17 Session
17 17N PlansAstrimar to Complete incorporation of Comments and 17Q ReferenceMay require help from Working CommitteesDeliver Summary Report on CompletionIssue Document to APIFormat, Ballot, etc.QuestionHow do we “Deliver” to IndustryAPI UniversityIndustry Training
19 Options A – Complete 17N ASAP Minimum with updates of all but QualificationB – Complete 17N fully incorporating Qualification / ValidationComplete incorporation of Qualification where current 17Q becomes annex of 17NC – Complete 17N and 17Q17N (see A above) which refers to the new 17Q which will also be developed
20 Pros / Cons A – Complete 17N ASAP Document Completed with available resourcesQualification will happen when it happensB – Complete 17N fully incorporating Qualification / ValidationComplete document deliveredAdditional funds / time / resources neededC – Complete 17N and 17QComplete documents deliveredBenefits described beforeUpdatable at separate pacesDifferent SubjectsEtc.More Additional funds / time / resources needed
21 Explain A-203We believe………….This will be confirmed as part of work….
22 Question on Definitions Questions re definitions of Verification / Validation/ etc. have been raisedAPI 17A will take responsibilities for definitionsAPI 17N will provide technical input / expertise
23 Thanks You’s To Everyone Involved Large Amount of Effort by everyone Workgroup LeadersParticipantsWorkshop AttendeesAstrimarBSEELarge Amount of Effort by everyoneLarge amount of detail developed, considered and WorkedEven with the Growth in Scope, effort continued and quality maintainedA great deal of quality work was completed!