API 17NSubsea Production System Reliability and

Technical Risk Management

Don WellsHess Corporation

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

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

Detail

• Expand the LCP– Provides balance and depth to the document– Communication of goals & requirements

4

Feasibility

Concept Selection

FEED Detailed Design

Manufacturing & Assembly

SIT, Installation, & Commissioning Operation

Decommissioning

Detail

• Change to a Dual-DPIF loop– Add Remediation cycle – Facilitates Integrity Management

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

Specification DevelopmentDefine Goals and

RequirementsKP1

Planning and Organisation

KP2

Design and Deliver for reliability and Integrtity

KP3

Evaluate ResultsKP3

Feedback and AssuranceKP4

Verification and Validation KP6

Project risk managementKP7

Risk and RAM AnalysisKP5

Supply Chain Management

KP10

Management of ChangeKP11

Performance tracking and data management

KP9

Core Processes

Qualification of Technology

KP8

Organisational LearningKP12

Supporting Processes

Defineü SegmentsüRisksüMitigations

Planü Inspections üMonitoring ü Testing

Implementü Data collectionü Data analysisü Performance

evaluation

Evaluate ü Analyse dataü Evaluate against

requirements

Feedback üAssuranceü Lessons Learnt

Are Requirements

met?

DefineüCorrective actions üRemediation actionsüQualification actionsü Intervention actions

PlanüCorrective actionsüRemediation actionsüQualification actionsü Intervention actions

Implementü Interventionü Changesü Performance

improvement

Evaluate ü TestsüChange implementedüAgainst requirements

Operational Reliability and Integrity

Assurance cycle

Remediation and corrective action cycle

Specification Development

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?

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-Q2 2013 ?• Peer & Industry Review Q3 2013 ?• Submittal Planned Q4 2013 ?

ThursdayInvitation:• 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!