rapid-s53 guidance document rev 2 draft 112217 guidance document rev 2... · will immediately...

Rev2

November27,2017

Pleasee-mailanyfeedbackyoumayhaveonthisRevisionofthedocumenttoMikeKucharski(IADCJIPProjectManager)at([email protected])

RAPID-S53

Reliability and Performance Information Database

For:

API S53 Well Control Equipment

Guidance Document

mailto:[email protected]

https://www.rapid4s53.com/index.html

2

RELIABILITYANDPERFORMANCEINFORMATIONDATABASEFORAPIS53WELLCONTROLEQUIPMENTGUIDANCEDOCUMENT

TableofContents

1.0 TheBusinessEthicsAssociatedwithuseoftheRAPID-S53Database 41.1. Preamble 41.2. BasicRequirement 41.3. ConflictsofInterest&CorruptPractices 41.4. AntitrustRequirements 41.5. CompliancewiththeLaw 5

2.0 Fair-UsePrinciples 62.1. Preamble 62.2. MissionStatementoftheJointIndustryProject 62.3. Rationalefor,andLimitationsonUseof,Database 6

3.0 ScopeandPurposeofGuidanceDocument 73.1. Scope 73.2. Purpose 7

4.0 DefinitionsandAcronyms 84.1. Definitions 84.2. Acronyms 10

5.0 InstructionsforEquipment-OwnerReporters 115.1. ReportGenerationCriterion&MandatoryPrerequisites 115.2. AccessCredentials–AcquisitionandPersonalization 115.3. RigSet-up 125.4. WellControlEquipment(WCE)ConfigurationSet-up 125.5. ContractSet-up 125.6. WellSet-up 135.7. CreationofaDraftEventRecord 135.8. ClarificationofReportContent&DataInputinstructions 145.9. RootCauseDefinitions,ClarificationsandExamples 225.10. Useofthe“Save”FunctionandtheSubmissionofEventRecords 24

6.0 DatabaseFeatures 256.1. General 256.2. EventReportsModule 256.3. DatabaseReportingModule 266.4. AdvancedFilterReportingModule 276.5. RigsModule 276.6. ParticipantsModule 296.7. MonthlyReport 30

7.0 EventRecordApprovalProcess 317.1. Submittal 31

3


7.2. Review 317.3. Editing 317.4. Approval 31

8.0 Analysis 338.1. Basics 338.2. Overview 338.3. CauseImmediatelyKnown 338.4. SMEReview 348.5. RCFA 35

9.0 CaptureandShareLessonsLearnt 37

EventDataReportingOfflineInputForm(ROIF) 38

ReportingProcess 39

Five-Why’sAnalysisMethodology 40

SMERevieworanRCFAReport 41

LibraryofMakesandModelsStoredinDatabase 42

UserAccessRightsMatrices 49

FurtherGuidanceonTerms“InOperation”&“NotinOperation” 51

4


1.0 The Business Ethics Associated with use of the RAPID-S53Database

1.1. Preamble

The purpose of this section is to outline, in some detail, the main business ethics that regulateparticipation in the BOP Reliability Joint Industry Project (the “JIP”) and use of the RAPID-S53Database. It shouldbeunderstoodbyeveryuseraccessing thedatabase that it is each individualuser’s responsibility to ensure that their behavior, as concerns the database, its output orassociatedby-products, includingmeetings, isgovernedbytherulesoutlinedbelowandthattheycomplywiththeFair-UsePrinciplesdetailedinSection2.

1.2. BasicRequirement

Each JIP Participant shall uphold the highest standards of business ethics and shall require itsdirectors, officers, employees, consultants, agents and contractors to conduct themselves inaccordancewiththeprinciplesofintegrity,fairnessandtransparency.

1.3. ConflictsofInterest&CorruptPractices

EachJIPParticipantshallavoidanyconflictofinterestbetweenitsowninterestandtheinterestsofotherJIPParticipantsindealingwithorganizationsorindividualsdoing,orseekingtodo,businesswiththeJIP.

No JIP Participant will, directly or indirectly, receive from or give, or offer to give, anything ofmaterialvaluetoanyotherJIPParticipant,contractor,official,orotherpersonassociateddirectly,orindirectly,withtheexecutionoftheJIP.

1.4. AntitrustRequirements

EachJIPParticipantshall,whileperforminganytaskassociatedwiththeexecutionoftheJIP,complywithalltherelevantantitrustandanti-competitionlawsofthecountriesorterritoriesinwhichtheyoperate.

NoJIPParticipantwill,directlyorindirectly,obtainorattempttoobtainanydatacontainedinthedatabasetowhichthatJIPParticipantisnotentitled.

No JIP Participant will, directly or indirectly, approach any other JIP Participant with a view todiscussing,sharing,providingorrequestingdatafromthedatabase,rawdatawhichisdestinedforthe database, or any other information relating, directly or indirectly, to the execution of the JIP(includinganytechnicalorcommercialconclusionsanyJIPParticipantmaydrawfromsuchdataorinformation)exceptasmaybenecessaryforperformingtasksassociatedwiththeexecutionoftheJIP or in respect of any contract or other project onwhich the JIP Participants, in question, areparticipating.

5


AnyJIPParticipantthatbelievesthatitmaybeabletoaccess,ormayhavereceivedfromthedatabaseoranotherJIPParticipant,data,orotherinformationrelating,directlyorindirectly,totheexecutionoftheJIP(includinganytechnicalorcommercialconclusionsanyJIPParticipantmaydrawfromsuchdataorinformation),towhichitwouldnotbeentitledwillrefrainfromviewingtheinformationandwill immediatelyreport the incident to theIADCProjectManager.TheIADCProjectManagerwillreviewtherelevantinformation,advisetheJIPParticipantonhowtoproceedandtheJIPParticipantwill immediately comply with any directions given by The IADC Project Manager, including thepermanentdeletionoftherelevantinformation.

1.5. CompliancewiththeLaw

Each JIPParticipantshall comply,andshall require itscontractorsandsubcontractors tocomply,with all applicable laws and regulations of all government authorities, including any restrictionsdealingwiththeexportationoftechnicaldata,andthedirectproductsthereof,butexcludinganylawsorregulationsorJIPdirectionsforwhichcompliancemaycause,orresultin,non-compliancewithanotherconflictinglaworregulation.

NoJIPParticipantwill,directlyorindirectly,whileperforminganytaskassociatedwiththeexecutionoftheJIP,offer,pay,promisetopay,orauthorizethegivingofmoney,oranythingofvalue, toanOfficial,ortoanyotherperson,whileknowing,orbeingawareofaprobability,thatall,oraportionof, suchmoney, or thing of value,will be offered, given or promised, directly or indirectly, to anOfficialforthepurposeofinfluencingtheact,decisionoromissionofsuchOfficialtoobtainorretainbusinessrelatedtheexecutionoftheJIP,todirectbusinessrelatedtotheexecutionofthisJIPtoanyperson,ortoobtainimproperadvantageorbenefit.

NoJIPParticipantisauthorizedtotakeanyactiononbehalfofanotherJIPParticipantthatwouldresultinaninadequateorinaccuraterecordingandreportingofworkrelatedtotheexecutionofthisJIP.

IfanyinformationcomestotheattentionofanyJIPParticipantthat indicatesanydeparturefromcompliancewiththelawtheJIPParticipantshallimmediatelynotifytheIADCProjectManager.

6


2.0 Fair-UsePrinciples

2.1. Preamble

Thepurposeofthissectionistoidentifythekeyprinciplestowhichusersofthedatabasemustagreetoinordertoprotectthebestinterestsofallpartiesinvolvedandtokeepallusersfocusedonsafetyandproductimprovementandfreeofimproperuseforcommercialconsiderations.

2.2. MissionStatementoftheJointIndustryProject

ThemissionoftheBOPReliabilityDatabaseJointIndustryProject(the“JIP”)istoadvancethesafetyand efficiency of global drilling operations by promoting improvements in the reliability andperformanceofWellControlEquipmentandrelatedproductsandservices.

2.3. Rationalefor,andLimitationsonUseof,Database

TheintentofthedatabaseistocollectacomprehensivebodyofdatathatcanbeusedbyindividualcompaniestoimprovethereliabilityandefficientoperationofWellControlEquipment.Despitethenumerousbenefitsofthiseffort,itmustberecognizedthatsimilareffortshavebeenunsuccessfulinthe past, often due to inattention to the commercial risks of certain parties and concerns overimproperuseofdata.

Toavoidtheserisks,thegoverningstructure,principlesandoperationsoftheJIParedesignedto

further theMission Statement and for no other purpose. In addition to observing the foregoing,

meaningful collaboration and support from each of the JIP Participants is essential to enhance

industryknowledgeanddriveinnovationeffortsintheareaofBOPreliabilityandperformance.

Itisalsorecognizedthatindividualdatabaseusers,representingtheJIPParticipants,mustadhereto

certainconfidentialityconcernsaswellasconductallactivitiesincompliancewithintheletterand

spiritofallapplicableantitrustandanti-competitionlaws.Consequently,itisunderstoodthatusers

of the database agree to not use this database, its output or associated by-products, including

meetings,todrawjointtechnicalorcommercialconclusions(jointmeaningmorethanoneOperator,

Drilling Contractor or OEM) from the data in violation of such applicable anti-trust and

anti-competitionlaws.

It is also understood that certain data fields associated with each database record will be kept

confidentialfromJIPParticipantsotherthanthoseJIPParticipantsassociatedwiththedatafieldsin

questionasameansoffurthermitigatingtheaboverisks.

7


3.0 ScopeandPurposeofGuidanceDocument

3.1. Scope

This document provides guidance for use by well control equipment owners when reportingreliability-relatedequipmentevents.

Regarding the range of well control equipment covered by the database, compliance with thereportingrequirementsofAPIStandard53continuestobetheprincipaldriverforthedatabasebutthe JIP can, from time to time, add items of equipment to the data collection processwhere theaddition of such items of equipment is recommended by the JIP Technical Reference Group andapprovedbytheJIPOversightCommittee.

Therangeofequipmentcoveredcurrentlybythedatabaseisasfollows:

• AuxiliaryEquipment(drillstringvalvesandgasseparationequipment)• BOPStack• BOPControls(primary,secondaryandemergency)• ChokeManifoldEquipment• DiverterSystem• RiserSystem

Consequently,theabovelistdefinestheWellControlEquipment(WCE)SystemfromaRAPID-S53perspective.

3.2. Purpose

Theintentofthisdocumentistoprovidethedefinitionsandinstructionsrequiredtofacilitatethedevelopmentandmaintenanceofastandardizedindustryreliabilityandperformancedatabase.

8


4.0 DefinitionsandAcronyms

4.1. Definitions

Cause: Somethingthatinitiates,shapesorinfluencesanoutcome.

CauseImmediatelyKnown: Whenthereisahighdegreeofcertaintyinthecauseofanevent,theeventreportdescribedinSection5iscompleteddescribingtheeventanddefiningtherootcausebasedoninspectionandmaintenancepersonnelexperienceandknowledge.

CorrectiveAction: Anaction,whichistakentoenableoperationstocontinueand/ortocorrecttherootcauseofanevent.

Effect: Aneventorconditionthatiscausedbyanothereventorcondition.

Evidence: Information,dataand/oritemsgatheredwhichdirectlyrelateto,orhavebeen,affectedbyanevent.

Failure: Asituationwhereacomponentmalfunctionsandis,consequently,preventedfromoperatingasdesigned.

(AleakingO-ringisafailureevenifthepistonthatitshouldsealcanfullystroke)

‘Five-Whys’Analysis: A‘question-answer’processusedtoexploretherelationshipsbetweenCauseandEffectunderlyingaspecificproblem.

InOperation: TheBOPstackisdeterminedtobe“InOperation”

afterithascompletedasuccessfulpressuretestofthewellheadconnectiontothewell-boreperapprovedwellplan.

NotinOperation: TheBOPstackchangesfrom“InOperation”to“Notin

Operation”wheneithertheBOPisremovedfromthe

9


wellheadortheLMRPisremovedfromthelowerstack.

When running, or pulling (retrieving) the stack, theBOPstackisdeemedtobe“NotinOperation”.

Reoccurring: Occurringasignificantnumberoftimeswheresignificanceisdeterminedbythelikelihoodofoccurrenceundernormaloperatingconditions.

RootCause: Isthecause(conditionoraction)thatbeginsacause/effectchainthatendsinacomponentevent.Correctionofsucharootcausewouldpreventreoccurrenceoftheevent(underinvestigation)andsimilaroccurrences.SeeSection5.9formoreinformation.

RootCauseFailureAnalysis: Acomprehensivesystematicinvestigationprocessundertakentoidentifytherootcausesofacomponentevent.

SMEReview: AninternalassessmentofthepossibleandprobablelocalrootcauseofthecomponenteventundertakenbyaSubjectMatterExpert(SME)withtheintentofrecommendingintermediateactionsorchangestoreducetheprobabilityofreoccurrence.

StackPull: Itisa“StackPull’wheneithertheBOPisremovedfromthewellheadortheLMRPisremovedfromthelowerstacktorepairthecomponentthatisthesubjectoftheeventrecord.

Aneventcannotbecategorizedasresultingina“StackPull”untilaftertheBOPStackhasbeen“InOperation”,asdefinedabove.

SubjectMatterExpert: Person or personswith an in-depth knowledge of asubject of interest. Suchknowledgewill havebeengained through direct and practical dealings withsubjectmatterofinterest.

10


ReferenceshouldbemadetoAPPENDIX7forfurtherguidance,throughtheuseofexamples,ontheterms“InOperation”,“NotinOperation”and“StackPull”.

4.2. Acronyms

API AmericanPetroleumInstitute LMRP LowerMarineRiserPackageBOP BlowoutPreventer NPT Non-ProductiveTimeBWM BetweenWellsMaintenance OEM OriginalEquipmentManufacturer

BSEE Bureau of Safety and EnvironmentalEnforcement RCFA RootCauseFailureAnalysis

BTS BureauofTransportationStatistics RWP RatedWorkingPressureHSE Health,SafetyandEnvironment SFI SkipstekniskForskningsinstitutt

IADC International Association of DrillingContractors SME SubjectMatterExpert

JIP JointIndustryProject QA/QC QualityAssurance/QualityControl

11


5.0 InstructionsforEquipment-OwnerReporters

5.1. ReportGenerationCriterion&MandatoryPrerequisites

Areportshallbecreatedforeacheventwhereanycomponentofwellcontrolequipmenthasbeendeemedtohavemalfunctioned,whetherthatcomponentisinuseornotandwhetherthereisNPTornot.ThisdatabasewasdesignedtotrackandtrendeventsofthisnaturetoallowJIPParticipantstofocusonproblemareas.

Theoriginalpolicywasrigidinthat,ifallsucheventswerenotreported,therewasapotentialthatvaluable data would be lost. With the benefit of hindsight, it has been acknowledged that thisapproachwastoorigid.Inthebeginning,forexample,situationswhereachokevalvedidnotholdatest,evenifasingleopen/closecyclewassufficienttocorrectthis,werereported.Whilethecyclingofavalvetotryandachieveasuccessfultestisnotcondoned,therearecaseswhereaforeignbodycouldpreventthefullclosureofavalveandclearingthiswithasinglefunctioncycleshouldnotintheequipmentbeingcategorizedashavingmalfunctioned.

Ifnoimmediatephysicalcorrectiveactionisrequiredtobeapplieddirectlytoacomponenttomakethecomponentoperateasdesigned,thenthereisnoeventtoreport.

However,events thatcometo lightduringmaintenanceandtesting,aswellasduringoperations,shouldcontinuetobereportedonbutreplacementofarampacker,forinstance,becauseitisnotexpectedtolastthenextwell,isnotamalfunction.Thisissimplymaintenance.

Reportsshouldbecreated,andsubmitted,assoonaspossibleaftertheeventisdiscovered.

Thefollowingmandatoryprerequisitestepsarerequiredtobetakentofacilitatethecreationofaneventrecord:

1. Acquireandpersonalizeaccesscredentials2. Verifythattheappropriaterigissetupinthedatabase3. Verifythattherighasafullycompletedversionofthewellcontrolequipment(WCE)

configurationsetupinthedatabase4. Verifythatthereisavalidcontractsetupinthedatabasefortherig5. Verifythatthereisavalidwellsetupinthedatabaseforthedefinedcontract

With all of the above in place the database is set up to auto-populate the non-technical fieldsassociatedwithgeneratinganincidentreport,thus,reducingtheamounttimespentbyEquipmentOwneruserscreatingeventrecords.

5.2. AccessCredentials–AcquisitionandPersonalization

OnlyMasterUsersareauthorizedtosetupnewusersforEquipmentOwnersandusersrequiringaccess to the database should send an internal e-mail to their nominatedMater User requestingaccess.

12


Toaccessthedatabaseforthefirsttime,usersmustlogintothedatabaseusingthecredentialsthataresenttothemintheformofasystem-generatede-mail.

Onceinthedatabase,userscanutilizethe“MyProfile”(toprightcorneroflandingpage),“ChangeYourPassword”and“SaveChanges” tabs topersonalize their log-onbasedontheuseofastrongpasswordthatiseasyfortheindividualusertoremember.

5.3. RigSet-up

Intheeventthattherigassociatedwiththeincidentreport isnotsetupinthedatabasethenthe“Rigs/AddRig”pathmustbeused,byauthorizedusers,tocreateanewrig.

Iftherigalreadyexistsinthedatabasethe“Rigs/Actions/EditRig”pathcanbeused,byauthorizedusers,toamendtheprincipaldataassociatedwiththatrig.

OnlytheEquipmentOwnerMasterUsersandSuperUsersareauthorizedtoaddrigsandedittheprincipaldataofexistingrigs.

5.4. WellControlEquipment(WCE)ConfigurationSet-up

TheWCEConfigurationcanbesetupintwoways.TheWCEConfigurationcanbesetupbyuploadingtheWCEConfigurationOfflineInputForm(COIF)orbyaddingtheWCEConfigurationdatadirectlyonline.

IfauserelectstousetheCOIF,theformmustbedownloadedfromthedatabasepriortousetoensurethattheuserisutilizingthecorrectrevisionoftheCOIF.Todownloadtheform,usethe“Rigs”tabandthe“DownloadWCEConfigurationForm”tabatthetopright-handsideofthescreen.OncetheCOIFiscompleteditcanbeuploadedusingthe“Rigs/Actions/UploadWCEConfiguration”pathandthisaddstheWCEConfigurationtothedatabase.

TheWCEConfigurationcanalsobesetupdirectlyonline.Tocompletetheset-updirectlyonline,usethe“Rigs/Actions/AddWCEConfiguration”pathtoaddtheWCEConfigurationtothedatabasebycompletingeachofthefivesectionsoftheconfigurationset-upprocess.

The “Start Date” and ”End Date” data, required in the “Period of validity” section of the WCEConfigurationsetupprocess,areusedtoprovideinformationonequipmentoperatingperiods,foruseinperformanceandreliabilityanalytics.

IfaWCEConfigurationalreadyexists,minoreditscanbemadetothisexistingWCEConfigurationusingthe“Rigs/Actions/EditWCEConfiguration”path.

OnlytheEquipment-OwnerMasterUsers,SuperUsersandSeniorReportersareauthorizedtoaddWCEConfigurationsandeditexistingWCEConfigurations.

5.5. ContractSet-up

Contractsaresetupbyusingthe“Rigs/Actions/ManageContract/AddContract”pathandexistingcontractscanbeeditedusingthe“Rigs/Actions/ManageContract/Actions/Edit”path.

13


OnlytheEquipment-OwnerMasterUsers,SuperUsersandSeniorReportersareauthorizedtoaddcontractsandeditexistingcontracts.

5.6. WellSet-up

Wells are set up using the “Rigs/Actions/ManageWell/AddWell” path. The data required is asfollows:

• LeaseNo.• WellNo.• APIWellNo.• NumberofJointsofRiserRun• RiserManufacturer• RiserModel• StartDate• EndDate• StackInUse

Theriserdataisusedtocreatepopulationdatawhenchartingrisereventsagainstthequantityofriserjoints,inuse,acrossthedatabase.The“NumberofJointsofRiserRun”shouldbesettozerointhecaseofPlatform,Jack-upandLandrigs.

The“StartDate”,”EndDate”and“StackinUse”dataareusedtoprovideinformationoncomponentpopulation,andassociatedoperatingperiods,foruseinperformanceandreliabilityanalytics.

Theabovedatawillbeusedtosetupadefaultwellwhichwillbeutilizedtopopulateallreportsuntilthe data is changed for subsequent wells. The well data can be edited using the“Rigs/Actions/ManageWell/Actions/Edit”path.

The Equipment-Owner Master Users, Super Users, Senior Reporters, Roaming Reporters andReportersareauthorizedtoaddwells,editexistingwellsandassigndefaultwells.

5.7. CreationofaDraftEventRecord

Therearetwooptionsforcreatingadrafteventrecord.

The first, and preferred, option is to submit the data directly on line by using the “EventReports/SubmitEventReport/Filloutreport”pathandbycompletingeveryfield,inallfourphasesoftheinputprocess,thathasnotbeenauto-populatedbydatastemmingfromthecompletionofthemandatoryperquisiteworkoutlinedabove.Oncethepopulationofallthefieldsiscompletedandthecompletedinputformissavedinthe“Draft”statebyutilizingthe“Submit”option(onlyaccessibleinthelastphaseoftheinputprocess)theMasterUserandalloftheSuperUserwillbenotifiedthatthereisa“Draft”recordavailableforreview.

ThesecondoptionisbasedontheuseoftheEventDataReportingOfflineInputForm(ROIF).ThereisanexampleoftheROIFinAPPENDIX1.IftheEquipment-Owner’sreportingprocessisbasedon

14


thecompletionoftheROIF,beforesendingittoaSuperUserforuploading,itisessentialthatthedatabasebeaccessedtodownloadtheformtoensurethatthecorrectrevisionoftheROIFisbeingutilized. To download theROIF, use the “Event Reports/Download Event Report” path. Once thedownloadedExcel-spreadsheetversionoftheformiscompleted,andtheresultingfilesaved,itcanbe forwarded to the appropriate Super User or Master User for uploading using the “EventReports/SubmitEventReport/Uploadreport”path.OncompletionoftheuploadtheSuperUsercansavetherecordinthe“Draft”stateandtheMasterUserandalloftheSuperUserwillbenotifiedthatthereisa“Draft”recordavailableforreview.

5.8. ClarificationofReportContent&DataInputinstructions

The clarifications in this sectionarevalid forbothof the inputoptionsoutlined in Section5.7. Itshouldbeborneinmindthatafairamountofthenon-technicalfieldsassociatedwithgeneratinganincidentreportareauto-populatedwhensubmittingthedatadirectlyonline.Hence,theinstructionsintherestofthissectionrelate,inthemain,totheuseoftheROIF.Allthedatashouldbeconsideredmandatoryunlessstatedotherwise.

5.8.1. WellIdentification

LeaseNo.: Numberasprovidedbyoperator.

WellNo.: Numberasprovidedbyoperator.

APIWellNo.: Numberasprovidedbyoperator.

Not everywell has all of these valuesbut the “WellNo.” shouldbe consideredmandatory for alloperatingrigs.Intheeventthat“LeaseNo.”and“APIWellNo.”usershoulduse“Notknown”asinputor these fields. If the rig is not on contract (Cold orWarm Stacked), then input should be “NotApplicable”.

5.8.2. RigOwnerInformation

RigOwner/DrillingContractor: UsethisdropdownboxtoselectthecompanythatownstheWCE(andhencethecomponent)thatisthesubjectofthereport.

Rig: Thisdropdownboxisfilteredtoshowonlythecurrentrigsownedby the selectedequipmentowner.Use thisdropdownboxtoselectthenameoftherigassociatedwiththeevent.

Operator: This dropdown box is populated with a list of thecurrent participating operators contained in the

15


database This includes both members and non-membersoftheJIP.Usethisdropdownboxtoselecttheoperatorthattherigwascontractedtoatthetimeoftheevent.

InacasewheretherigwasColdorWarmStackedatthetimeoftheevent,thisfieldshouldbeignoredwhenusingtheROIFand“ColdStacked”or“WarmStacked”mustbeselectedwhensettinguptherelevantrig“Contract”online.

Owner’sPrimaryContact: Title of person who is familiar with the issue in casefurtherinformationisrequired.Thiscouldbethepersonreporting,butthatisacompanydecision.

EmailofOwner’sPrimaryContact: EmailaddressforthePrimaryContactoftheEquipmentOwner.

NameofPersonReporting: Thisthenameofpersonfillingouttheeventreport.

OEMRep.Onboard,ifapplicable: NameoftheOEMrepresentativethatvisitedtherigandwas involved in an assessment of the componentassociatedwiththeevent.Thisisafree-textfieldand,incases where this is not applicable, this field can beignored when using the ROIF and “Not Applicable”shouldbeusedwhencreatingthereportonline.

5.8.3. OtherInformation

OwnerSpecificEquipmentIDNumber: AnSFIcode,orsimilar,thattheequipmentownerusestoidentifythespecificequipmentorcomponent.

Systemintegrator’sIncidentReferenceNo: Reference number issued by the System Integrator, ifinvolved.Thisisafree-textfieldand,incaseswherethisisnotapplicable, this fieldcanbe ignoredwhenusingthe ROIF and “Not Applicable” should be used whencreatingthereportonline.

Componentsentonshore: Use this dropdown box to record whether or not thecomponentinquestionisontherigand,ifithaslefttherig,thereasonfordispatchingitfromtherig.NOshouldbeselectedinthisdropdownboxifthecomponenthas

16


not left the rig. If the componenthas left the rig, theappropriatereasonshouldbeselected.

5.8.4. Equipment

TypeofWCESystem: UsethisdropdownboxtoselectthetypeofWCESystem.SelectSUBSEAifthesystemutilizesaBOPdesignedtobe operated underwater; SURFACE OFFSHORE orLAND,asappropriate,forothers.

SystemIntegrator: Use this dropdown box to select the name of thecompany that provided or assembled the impactedsystem.This is not necessarily the original equipmentmanufacturer.TheoptionsavailabletothereporterareCameron,GE,NOVortheEquipmentOwner.

Subunit: Use thisdropdownbox to select theappropriateWCESystemsubunitcategory.

Thisisthefirstofthreedropdownboxesthatdeterminethecontentsofeachsubsequentboxinalogicalmanneruntilthecorrectcomponentisidentified.

Item: Use this dropdownbox to select the appropriate itemcategory. The items listed in the dropdown box arecontingentupontheselectedSubunit.

Component: Use this dropdown box to select the appropriatecomponent category. The components listed in thedropdown box are contingent upon the selected item.This is the lowest maintainable item and where thereportercanidentifythecomponentthatisthesubjectoftheeventreport.

ComponentManufacturer: Usethisdropdownboxtoselecttheoriginalequipmentmanufacturerofthecomponentthatisthesubjectoftheeventreport.

ThelistisprettycomprehensivebutifaparticularOEMis missing from the list contact the IADC JIP ProjectManagertohavethemissingOEMaddedtothelist.

17


ObservedFailure: Usethisdropdownboxtoselectandcapturethemeansbywhichthecomponentmalfunctionwasidentified.

Model: ReferenceshouldbemadetoAPPENDIX5foralibraryofequipmentMakesandModelsstoredinthedatabase.

Use this dropdown box to select the model of thecomponent, in question, if the component is listed inAPPENDIX5.Otherwise,usethisfield(thisisafree-textfieldifthemodelisnotlistedinAPPENDIX5)toidentifythemodelofthecomponent.

Pleaseensurethatifthecomponent,inquestion,ispartofanintegrateditemthatthemodelofthecomponentisprovidedandnotthemodeloftheitemorsubunit.Forexample, the model of the control pod should not beinput as the model for a pressure regulator if it thepressure regulator that is the subject of the eventreport.

OEMPartNumber: UsethisfieldtoidentifythepartnumberasestablishedbytheOEM.Thisisafree-textfield.

OEMSerialNumber: Use this field to enter the unique, identifying serialnumberutilizedbytheOEM.Thisisafree-textfield.

Size: Use the two available dropdown boxes to select thewholeandfractionalsizeforthecomponent.

Ifthecomponent,inquestion,isnotdefinedbya“Size”(e.g.Software),thetwofieldsshouldbeleftblankintheROIFand0shouldbeselectedinbothboxeswhenusingtheonlineinputdropdownboxes.

PressureRating: Usethetwoavailabledropdownboxes to firstlyselectthestandardizedpressurethatthecomponentisratedfor, and to secondly indicate whether this pressureratingisa“WellBore”or“OperatingCircuit”pressure.

If the component, in question, is not defined by a“PressureRating”(e.g.Software),thetwofieldsshouldbeleftblankintheROIFand0and“OperatingCircuit”should be selected when using the online inputdropdownboxes.

5.8.5. ComponentHistory

18


DateAffectedComponentwasinstalled: Usethisfieldtorecordthedatethatthecomponentwasinstalledintothesystemontherig.

Thiscouldbethedatethattheequipmentwasdelivered,oritcouldbeaftermajorinspection/maintenancework(e.g.five-yearly).

MaintenanceDeferredonComponent: Use this dropdown box to record whether plannedmaintenance was overdue at the time the eventoccurred.

IfYES,whatmaintenancewasdeferred: Use this dropdown box to select what category ofmaintenancethatwasdeferred(BWM/EOW,Annual,5-Year,etc.).

Ifplannedmaintenancewasnotoverduethenthisfieldshould be left blank when utilizing the ROIF and theonlineinputdropdownboxcanbeignored.

DateofLastMaintenance: Use this field to record the date of the last plannedmaintenanceactuallycompleted.

DescriptionofLastMaintenance: Usethisdropdownboxtoselectthetypeofmaintenancethatwasactuallyperformedinconnectionwiththelastplannedmaintenance.

AmountofUsageattheTimeofFailure: Usethefirstfree-textfieldtoinputawholenumberanduse the dropdown box to select the units (Hours orCycles) to associate with the number. If the “UsageAmount” is not known then leave the free-text fieldblankandselect“Unknown”astheunits.

Ifthereporterhasaccesstoautomaticcyclecounters,or the discipline to actually count cycles exists, thenrecord cycle counts for valves, cylinders and pistons.Record hours for pumps, and all other components,wherecyclecountsarenotavailable.

5.8.6. SiteSpecificInformation

IADCCodeDescription: Use this dropdown box to select the IADC code andassociateddescriptionoftherigoperationthatreflectstheongoingoperationatthetimetheeventoccurredorwasdiscovered.

19


Notethatthesehaverecentlybeenupdated,byIADC,toinclude specific options for Running/retrieving riserequipmentandfortestingsurfaceequipment.

Location(Region): Use this dropdown box to select the appropriatecontinentassociatedwiththerigoperationsatthetimetheeventoccurredorwasdiscovered.

Location(Country): Usethisdropdownboxtoselecttheappropriatecountryassociatedwiththeselectedregionofoperations.

Waterdepth: Usethefree-textfieldtoinputtheactualwaterdepthattheoperatinglocationandthedropdownboxtoselectthe units (Feet orMeters) to associatewith the valueprovided.

DrillingFluidType: Use this dropdown box to select from the list ofcommonlyuseddrillingfluids.

BOPControlFluid: Use this dropdown box to select from the list ofcommonlyusedBOPcontrolfluids.

Concentration: Use this dropdown box to select the percentage ofcontrol fluid concentrate in the BOP control fluidmixture.

Glycol: UsethisdropdownboxtoselectthepercentageofglycolintheBOPcontrolfluidmixture.

Wasthelastlaboratorysampleacceptable?: UsethisdropdowntorecordtheanswertothequestionoppositeregardingtheBOPcontrolfluid.

N.B.Thisspecificallyreferstothelastlaboratorysample(asopposedtoarigtest).

Dateoflastsample: Use this field torecord thedateof the last laboratoryanalysis.

5.8.7. EventData

20


EventDate: Usethisfieldtorecordthedateoftheevent.

EventDateis: Use this dropdown box to select whether the “EventDate” is associated with the occurrence of themalfunctionorwhether it is thedate themalfunctionwasdetected.

Whendidtheeventoccur?: Use this dropdown box to record whether the eventoccurredwhile theWCE Systemwas in the operatingmode (“BOP # 1 or 2 In Operation”) or in themaintenancemode(“BOP#1or2NotinOperation”).

If you only have one BOP then select the appropriatestatusforBOP#1.

DescriptionofEvent: This is free-text fieldwhere reporters are required toprovidesufficient,butconcise,informationontheeventinorderthatotherdatabaseusercanunderstandwhatmalfunctioned, what were the symptoms of themalfunction,whatwasbeingfunctionedatthetimeofthemalfunction andwhywas it being functioned. Allrelated details that are deemed pertinent should beincluded. Any information that does not add to theunderstandingoftheeventshouldbeexcluded.Theuseof information that can identify any of the entitiesinvolvedintheeventmustbeavoided.

HoursofNPT– This field is to be used to record the total number ofhours,inclusiveofBOPrecoveryandreinstallationetc.,between the detection of themalfunction and gettingback to the point in the operation at which themalfunctionoccurred.

This is typically IADC Code 8 time. If the rig contractincludesmaintenance,orsimilar,timeallowances,theseshouldbeignored,inthiscontext,andtheactualtotalofNPThourrecorded.

HoursofRepairtime: This fieldshouldonly includetheactualtimetakentorepairandtestthecomponentthatisthesubjectoftheeventrecord.

DidtheeventcauseaBOPStackpull?: Use this dropdown box to record whether or not thecomponent malfunction was a direct factor in thedecisiontoretrievethesubseaBOPstackforrepairs.

21


DetectionMethod: Use thisdropdownbox to selecthow themalfunctionwasdiscovered.

There must be consistency between the selectedoperatingstate(“BOP#1or2InOperation”or“BOP#1or2NotinOperation”)andtheoptionselectedforthe“DetectionMethod”field.Itisinconsistenttoselectforthe“Whendidtheeventoccur?”field“BOP#1or2Notin Operation” and to record “Function Testing inOperation” in the “Detection Method” field. Similarly,“BOP # 1 or 2 In Operation” and “Function TestingSurface”donotbelongtogetherevenifthecomponentatthecenteroftheeventbelongstoanitemofsurfaceequipment.

ImmediateCorrectiveAction: Usethisdropdownboxtorecordtheimmediateactiontaken on the rig to address the issue with themalfunctioning component and to place the WCESystembackintoanoperationalstate.

RootCause: Usethisdropdownboxtoselectthecorrectrootcauseoptionfortheevent.

Theselectionofanyoptionotherthan“RCFArequired”or“AssessmentPending”willresultinthereportbeingclosed on approval by the appropriate Equipment-OwnerSuperUser.

Theselectionof ‘AssessmentPending’willopenafree-textboxtobeutilizedtojustifytheselection.ThiswillprobablybesomethingtotheeffectthattheBOPstackis still subsea and an MOC and risk analysis hasdetermined that it is safe to continueoperationswiththeparticularmalfunctionunresolved.

Selecting ‘RCFArequired’or ‘AssessmentPending’willinitiateaprocesswherebytheappropriatestakeholderswillberemindedbysystem-generatede-mailsthatthedefinitionof theactual rootcause isoutstanding.Theinitial reminder will be generated 99 days from theeventdateandsubsequentreminderswillbegeneratedevery30daysthereafter.

Quantity: Use this field to record the quantity of identicalcomponentsthatmalfunctionedatthesametime.

22


Itshouldbenotedthataquantitygreaterthan1shallonly be used if the components are identical in everyway.Forexample, if twoSPMvalvesmalfunctionedatthesametimebutwereinstalledatdifferenttimesoriftherearedifferencesofanykindbetweenthetwovalves,thecomponentsarenot considered tobe identical forthe purpose of event reporting and, consequently, thequantityshouldbesetto1andindividualeventreportsmustbecreatedforeachofthevalves.

5.9. RootCauseDefinitions,ClarificationsandExamples

TheRootCauseisthefundamentalreasonfortheoccurrenceofaproblematicalevent.

“ASSESSMENTPENDING” “RCFAREQUIRED”

Theseoptionsareavailableforselectionincaseswheretheinvestigationandanalysisprocesseshavenotbegunorareincompleteand,asaconsequence,therootcauseisunknownatthetimetheeventrecordisbeingcreated.

“Assessment Pending” should be selected if, for instance, the BOP stack is still subsea. TheunderstandingisthatthefailurewillbeinvestigatedwhentheBOPstackbecomesaccessibleandtherootcausewillbeevaluatedatthattimeandtheeventrecordupdatedtoreflectthemostcurrentunderstandingoftherootcause.

Ontheotherhand,“RCFARequired”mustbeselectediftherewas;alossofawellbarrier,iftherewasanunplannedstack/LMRPrecovery,oriftherewasareoccurringevent.ItshouldbenotedthattheoutcomesoftheinvestigationsassociatedwithanyoftheotherlevelsofanalysiscanresultintherequirementforanRCFA.

Selectionofeitheroftheaboverootcauseoptionswilltriggera99-dayreminderwhichwillbeissuedtoSuperUsers.TheintentofthisistoprovideSuperUserswithadequatenoticetoensurethatthe120-dayUSCSrequirementsaremet.BothEquipment-OwnerandOperatorSuperUserswillreceiveacopyofthisreminder.

Also,reportswheretherootcauseiseither“AssessmentPending”or“RCFARequired”willremaininthe“Approved(Open)”stateuntiltheinvestigationandanalysisprocessiscompleteandthereporteditedtoreflecttheagreedtruerootcause.

Itisimportanttounderstandthattheselectionofeitheroftheaboveoptionsdoesnot,andwill not, automatically initiate the investigation and analysis processes. The EquipmentOwnermustaddressthisoutsideofthedatabaseand,intheeventthatanRCFAisrequired,thismustinvolvetheOEMorasuitablycompetentthird-party.

23


It isalso important toremember thatanRCFA is typicallycarriedoutat facilitiessetup forsuchinvestigative work and when shipping the applicable component to the relevant facilities theEquipmentOwner’ssupportresourcesneedtobenotified.

Theremainingoptionsshouldonlybeselected insituationswhere the investigationandanalysisprocesses,irrespectiveofthelevelofanalysisrequired,aredeemedtobecompleteandtherootcauseestablished.

“DESIGNISSUE” “QA/QCMANUFACTURING”

Theseoptionsaremanufacturerrelated.However,theolderandmoreusedtheequipmentgets,thelesslikelyitwillbethattherootcausewillfallintoeitherofthesecategories.

A “Design Issue” is related to inadequate design or configuration. This can only be confidentlyidentifiedafteranRCFAhasbeencompletedorifthedesignissuehasbeenpreviouslyidentifiedbyRCFAornotificationfromthemanufacturerand,forwhateverreason,themodification/upgradehasnotyetbeenimplemented.

“QA/QC Manufacturing” is a failure that is entirely related to the manufacturing and/or repairprocessesoftheOEM.Forexample,anewannularpistonwaspurchasedfromtheOEMbutwewereunable to install it. Investigationshowedthat ithadbeenmachined incorrectly.Anotherexamplewouldbethefailedbench-testofanewlyreceivedvalve.

“DOCUMENTATIONERROR” “MAINTENANCEERROR” “PROCEDURALERROR”

Thesethreeoptionsaremuchlessambiguous.

Theselectionofthe“DocumentationError”optionshouldsignifythattheeventoccurredasaresultofamistakeoroversightinthedocumentationusedbytheindividualsresponsibleforoperatingandmaintaining the equipment. In other words, the installation, operations and maintenancedocumentationwasfollowedbuttherewasan inherenterror inthedocumentationsupplied.Thedocumentationcanbe in the formofdrawings,manuals,procedures,work instructionsandworkordersandcanoriginatefromeithertheOEM,SystemIntegratorortheEquipmentOwner.Exampleswould include drawings that containedmistakes, working to outdated revisions ofmanuals andworkingtomaintenanceproceduresthataeoutofdateduetothefactthattheydonotreflectlessonslearnedfromtheuseofcomponentinoperation.

Theselectionoftheoption“MaintenanceError”signifiesthatamistake,misuseoroversightoccurredduringmaintenance.Anexamplecouldbethatachokelineflangeleakedafterthemaintenancehadbeencompleted.Investigationshowedthattheflangestudshadbeentorquedto380Nminsteadofthe380ft-lbstatedintheprocedure.Thiswasamaintenanceerror.

Selectionof the “ProceduralError”optionsignifies that therewasamistake,misuseoroversightduringoperation.Thiscouldbe that theBOPram leakedbecause testpressurewasappliedafterclosingpressurewasvented,butwithouttheramhavingfirstbeenmechanicallylocked.Thiswasaproceduralerror.

24


“WEARANDTEAR”

The “WearandTear”optionhasa tendency tobemisunderstoodand is, as a result, selected toofrequently.

“WearandTear”isanexpectedconditionofacomponentthathasreachedapointwhereitisunabletoperformitsintendedfunctionastheresultofattaining,orpassing,theusagelevelthatformedthebasisofdesignforthecomponentinquestion.

Consequently,inasituation,whereacomponenthasreached,orpassed,itsdesignusagelevel,“WearandTear”isnottherealrootcauseoffailureandif“WearandTear”featuresrepeatedlyinthefailureofacomponentinoperation,thensuchatrendwouldtendtoindicatethattherewasanerrorinthemaintenancedocumentation(plan,proceduresand/orworkinstruction)andthatareviewofthatdocumentationisrequired.

The“WearandTear”optionshouldonlybeselectediftherootcauseofthefailuredoesnotfitoneofthe other root cause options and where a component has irrefutably failed before reaching itsintendedmaintenanceintervalorcyclecount.

5.10. Useofthe“Save”FunctionandtheSubmissionofEventRecords

The creation of a draft event record requires the completion of a four-stage input process. Thedatabaseallowsforthesituationwhereadraftrecordneedstobesavedandstoredwhileitisintheprocess of being created and prior to the input being fully completed. This is known as the “InProgress” state and the “In Progress” state is initiated immediately on commencement of recordcreationandtherecordremainsinthisstateuntilallfourstagesoftherecordcreationprocessarefullycompletedandtherecordisreadyforsubmittalandreviewasacompleted“Draft”eventrecord.

Thesavingofan“InProgress”recordisachievedintwoways.Alldatafedintothedatabaseduringtherecordcreationprocessisautomaticallysaved(theauto-savefunctionissetasasystemdefault)as it isentered.Theusercanalsosuspendrecordcreationatanytimeusingthe“Save”tabatthebottomofeachscreenassociatedwitheachstageofrecordcreation.Thisresultsinthesavingofthedataentered,uptothatpoint,andallowstheusertocloseapartiallycompleteeventrecordsafelyinthe“InProgress”state.

Onceallfourstagesofthedatainputprocessarefullycompleted,utilizationofthe“Submit”buttonwillloada“Draft”versionofthereportintothedatabaseandalerttheMasterUserandSuperUsersthata“Draft”reporthasbeencreated.TheappropriateSuperUserwillthencheckthequalityofthedata contained in the “Draft” report, correct any errors and approve it thereby adding it to the“Approved”reportsinthedatabase.

Eachtimean“Approved”recordisgenerated,modifiedorexperiencesachangein“State”(“Open”to“Closed”,forexample),theEquipment-OwnerMasterUserandSuperUsersandtheSuperUsersoftheappropriateOEMandtheOperatorreceivesystem-generatednotificatione-mails.

25


6.0 DatabaseFeatures

6.1. General

Initialaccesstothedatabaseisgainedbyusingthecredentialsthataresenttousersintheformofasystem-generatede-mail.

Onceinthedatabase,the“MyProfile”(toprightcorneroflandingpage),“ChangeYourPassword”and “SaveChanges” tabs canbeused topersonalize a user’s log-onbasedon theuse of a strongpasswordthatiseasyfortheusertoremember.

The database consists of the modules outlined in the rest of this section and the amount offunctionalityavailabletoanyuserwithinaparticularmoduleisdependentonaccessrightsassignedtotheuser’srole.ReferenceshouldbemadetoAppendix6toobtaindetailsoftheAccessRightsforthevarioususerrolescoveredbythedatabase.

6.2. EventReportsModule

TheprimaryfunctionofthismoduleistoprovideEquipment-Owneruserswithaccesstotheareaofthe databasewhere event records can be created and processed. The secondary function of themoduleistofurnishuserswithalistingofalloftheeventrecordsassociatedwiththeorganizationtowhichauserbelongsandtodosoinmannerthatenablestheusertofiltertherecordsbytheirprocessing state and event date. It also enables the user to utilize the filtering process to accessindividualrecordwithaviewtoinvokingcertainactionssuchasediting,duplicating,viewingandexportingrecordsofinterest,dependingontheuser’saccessrights.Theprocessingstatesofarecordareoutlinedinthefollowingsubsections.

6.2.1. All

Withthisfiltertabhighlighted,theuserwillbeprovidedwithalistofalltheorganization-specificeventrecordsassociatedwiththeuser’srig,rigs,andcompanythathavebeencreatedwitheventdatesthatfallwithintheperiodselectedonthelastfiltertab.

6.2.2. InProgress

Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeenopenedandsaved,butnotyetcompletedandsubmitted,witheventdatesthatfallwithintheperiodselectedonthelastfiltertab.RecordsinthisstateareonlyaccessiblebyEquipment-Ownerusersand,thus,thistabisonlyavailabletoEquipmentOwners.

6.2.3. Draft

Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeencompletedandsubmitted,witheventdatesthatfallwithintheperiodselectedonthelastfiltertab, and that are waiting approval by either the Equipment-Owner Master User or one of the

26


Equipment-OwnerSuperUsers.RecordsinthisstateareonlyaccessiblebyEquipment-Ownerusersand,thus,thistabisonlyavailabletoEquipmentOwners.

6.2.4. Approved(Open)

Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeenapproved,witheventdatesthatfallwithintheperiodselectedonthelastfiltertab,andwitheither‘AssessmentPending’or‘RCFARequired’selectedastherootcause.

6.2.5. Approved(Closed)

Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeenapprovedandclosedandthathaveeventdatesthatfallwithintheperiodselectedonthelastfiltertab.

6.2.6. Reject

Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeenrejectedandarchivedinthedatabase,forwhateverreason,duringtheperiodselectedonthelasttab.RecordsinthisstateareonlyaccessiblebyEquipment-Ownerusersand,thus,thistabisonlyavailabletoEquipmentOwners.

6.2.7. Days

Thistabcanbeusedtoselectthetimeperiodassociatedwiththeeventdatesoftheorganization-specificrecordsofinterest.Theoptionsare30days,60days,90daysorALL.

6.3. DatabaseReportingModule

Thismoduleprovidesuserswithasimplerollingoverviewofthebreakdownoftheapprovedeventrecordscontainedinthedatabase.

Theuserhastheabilitytoviewtheapprovedeventrecorddataforeventsthatoccurredduringthecurrentmonthbysubunitandwiththeemphasisbeingplacedontheimpactofthecurrentmonth’seventsonproductivity.Inaddition,thenumberofeventrecordsforthecurrentmontharecomparedwith the numbers from previousmonths, benchmarked by relating the number of events to thenumberofworkingrigsavailabletoproducerecords.Thiscomparisonisavailableforthelast12andlast60months.

Usercanalsoutilizetheavailablefilterstoviewtheapprovedeventrecordsbrokendownbysubunit,byitemandbycomponent.Eventrecorddistributionscanbeproducedforboththelast12monthsandthelast60months.Inaddition,thesubunitdistributionchartscaneitherbebasedontherawnumberofrecords,associatedwitheachitemreportedon,orontherecordcount,associatedwitheachitemreportedon,asapercentageofthetotalnumberofrecordsloggedagainstthesubunitofinterest.

27


6.4. AdvancedFilterReportingModule

Thismoduleprovidestheuserwithaccesstoalloftheapprovedrecordsinthedatabase.

The filtersallowtheuser toselect specificdata fieldsasameansofpreparingacustomizeddataextract forexport from thedatabase in the formofanExcel file.TheExcel file isdownloadedbyutilizingthe“Export”tab.ThemainfiltersallowtheusertofocustheirdatasearchonEquipmentOwner,RigandOperatorbut there isalso theability to increase thenumberof filtersappliedbyselectingadditionalfiltersfromthelistavailableunderthe“MoreFilters”tab.

Intheeventthattheuserisinterestedinextractingalloftheapprovedeventrecordsinthedatabase,filters should not be applied and the Excel file containing all the approved event records in thedatabasecanbedownloadedbyutilizingthe“Export”tab.Thisallowstheusertosearchthroughthedata,createcustomizedsetsofanalytics,andproducead-hocreportsonareasofspecificinterest.

ItshouldbeborneinmindthatthedatabasecomplieswiththeJIPAntitrustRequirementsandFair-UsePrinciplesand,asaresult,certaindatafieldswillbeanonymized.However,thetechnicaldataassociatedwith all the approved event records in the databasewill be available for review andanalysis.

It is the responsibility of the user to ensure that all data extracted from the database is used inaccordancewiththerequirementsofSection2.3ofthisdocument.

6.5. RigsModule

ThismodulegivesEquipment-Owneruserstheabilitytomanagetheirfleetofrigs,thewellcontrolequipment(WCE)Configurationsassociatedwitheachrigintheirfleetandthecontractsandwellsthat define how the rigs, and their WCE Systems, are utilized – an important element in theassessmentoftheperformanceandreliabilityofWCEcomponents.

Dependingon theroleof theuserand theassociateduseraccessrights, the landingpage for thismodule provides the userwith an overview of the rigs in the user’s fleet that are set up in thedatabase.ItalsoprovidesEquipment-OwnerMasterUsersandSuperUserswiththeabilitytoaddarigusingthe“AddRig”tabandtheabilitytodownloadtheWCEConfigurationOfflineInputForm(COIF)Excelfileusingthe“DownloadWCEConfigurationForm”tab.

Theright-handcolumnofthetableonthemodulelandingpage(“Actions”tab)haseightoptionsthatcanbeusedtoundertakethetasksoutlinedinthefollowingsubsections.

6.5.1. EditRig

Thisallowsanauthorizedusertoeditthebasicriginformationrelatingtoarigalreadyaddedtothedatabase.Italsoallowstheusertodefinewhethertherigusesasingleordualstackconfiguration.

6.5.2. EditWCEConfiguration

28


HereyoucanchangethedetailsoftheWCEConfigurationontherig.ItisnotacompleteIADCwellcontrolequipmentlistasthedatabaseonlycoversthewellcontrolequipmentdefinedinSection3.1.

6.5.3. AddWCEConfiguration

Thisisusedtoaddanewconfigurationforanexistingrig.IntheeventthattherigofinterestalreadyhasavalidWCEConfiguration,thisoptionshouldonlybeusedinthosecaseswhereyouaremakingasignificantchangetotheexistingWCEConfiguration.Asanexample,thetypeofchangethatwouldfallintothiscategoryisonewhereanexistingannularisbeingreplacedbyanannularofadifferentmake but with the same technical capabilities as the original annular. Another example of asignificant change to a WCE Configuration would be a situation where there is an addition orreductioninthenumberpiperamsinthestack.AnemptyWCEConfigurationiscreatedintheeventthat“AddConfiguration”isselectedaccidentally.

6.5.4. UploadWCEConfiguration

This isusedtouploadaWCEConfigurationthathasbeencollatedofflineusingthedownloadableCOIFExcelfile.OncetheCOIFiscompleted,storedontheuser’scomputerandavailableforupload,theuserneedonlyselectthisoptionandidentifythefilethatneedstobeuploadedtohavetheWCEConfigurationassignedtotherelevantrig.

6.5.5. AssetDisposal

ThisshouldonlybeusedintheeventthatarigisnolongerapartofanEquipmentOwner’sfleetand,asaresult,theassethaseitherbeendisposedofeitherthroughasaleorbyscrapping.Oncearigisdisposedofitwillnolongerbepossibletocreateeventrecordsforthatrigbutthehistoricaleventrecordswillbeavailable for reviewandanalysis. In theevent thatanasset is sold toanother JIPParticipant,theeventrecordswillultimatelybetransferredtothenewEquipmentOwner.

6.5.6. ShowWCEConfigurations

ThisallowsuserstoviewallofthecompletedWCEConfigurationsthathavebeensubmittedforarig.WCE Configurations associatedwith approved event records cannot be deleted because of theirassociationwithcomponentutilization.However,Equipment-OwnerMasterUsersareabletodeleteWCEConfigurationsthathaveneverbeenappliedtoaneventrecordorthathavebeensubmittedaccidentally.

6.5.7. ManageWell

Thisallowsuserstoaddnew,andeditexisting,welldata.

NoteverywellwillhaveLease,WellandAPIWellnumbersassignedtoitbutwellswillnormallyhaveatleastoneofthesenumbersandeveryeffortshouldbemadetodefineatleastoneofthesewellattributes.Thoseattributesthatcannotbedefinedshouldbecharacterizedas“Notknown”.

29


Forrigswherethe“TypeofWCESystem”isdesignatedas“Subsea”,thereisarequirementtoprovidedetailsofthe“NumberofJointsofRiserRun”onthewell.Thisdataisusedforcollatingdataonriserutilizationandforchartingrisereventsagainstthequantityofriserjointsinoperationatanyonetimeacrosstheentirefleetofrigssetupinthedatabase.Forrigswherethe“TypeofWCESystem”isdesignatedaseither“SurfaceOffshore”or“Land”the“NumberofJointsofRiserRun”shouldbesettozero.

Thiswelldatawillbeusedtoauto-populatealleventreportswheretheeventdatecoincideswiththeperiodthattherigisworkingonthatwellanditisimportantthatawellissetuptocovertheeventdateassociatedwithaparticulareventeitherpriortocreating,orduringthecreationof,therecordforthatevent.

6.5.8. ManageContract

ThisallowsuserstolinktherigwiththeOperatorcontractingtherig.This informationisusedtoauto-populatetheeventrecordwithnotonlythenameofthe“Operator”butalsothe“Region”oftheWorldthattherigisoperatinginandthe“Country”thathasjurisdictionoverthewellbeingdrilled.

Newcontractdatacanbeinputusingthe“AddContract”tabandthedataassociatedwithanexistingcontractcanbeeditedbyselectingthe“Edit”optionunderthe“Actions”tab.

6.6. ParticipantsModule

Thismoduleprovidesuserswithalistoforganizationsthatarecontainedinthedatabaseandareavailableforuseinthecreationofeventrecords.Italsoprovidesuserswiththeabilitytocontroltheir organization’s access to the database in terms of the number of users, type of users, rigassignmentsandtheallocationofsystemcredentials.

“Participants”fallintothefollowingthreecategories:

1. EquipmentOwners(inthemain,DrillingContractors),2. Operatorsand3. SystemIntegrators.

Itshouldbenotedthatthedifferencebetweenadatabase“Participant”andaJIPParticipantisthatonly JIP Participants have user-access to the database. A list of the user roles available to JIPParticipants,andtheirassociatedaccessrights,isprovideinAPPENDIX6.

6.6.1. Participants

Thedatabaseparticipants(DrillingContractors,OperatorsandOEMsthatareSystemIntegrators)list isaccessedbyusingthe“Participants”tab.UsersshouldcontacttheIADCJIPProjectManagershouldtherebeaneedtoaddanorganizationtothedatabaseasadatabase“Participant”.

6.6.2. ManageUsers

30


MasterUsers and SuperUsers can access a current list of their organizations users by using the“Users” tab. Only the Equipment-OwnerMaster Users and the Super Users of the Operators andSystemIntegratorscansetup,editordisableusers.TheauthorizedMasterUsersandSuperUsersneedtoensurethataccessisgrantedinaccordancewiththeJIPAntitrustRequirementsandFair-UsePrinciples.

6.7. MonthlyReport

ThismoduleprovidesuserswithaccesstocopiesofthepublishedJIPMonthlyReports.Thereportsarelistedbyyearandmonthandeachreportprovidesahigh-levelanalysisofdatabaseactivityforthemonthinquestion.Usershavetheabilitytoviewanddownloadreportsofinterest.

The Information Bulletin section of JIP Monthly Report provides an ideal vehicle for thedissemination of anonymized information to the other organizations participating in the JIP andmembers are encouraged to submit summariesof theirownexperiences andpractices to the JIPProjectManagerforinclusionintheJIPMonthlyreport.

31


7.0 EventRecordApprovalProcess

The process for ensuring compliance with API Standard 53 and mandatory, country-specificregulatoryrequirementsisoutlinedintheflowdiagramfoundinAPPENDIX2.

ThefollowingsectionsprovidedetailsofthereviewandapprovaloptionsavailabletoEquipment-OwnerMasterUsers andSuperUsers aspart of theprocess associatedwith converting an eventrecordfromthe“Draft”stateintothe“Approved”state.

7.1. Submittal

Equipment-OwnerMasterUsersandSuperUsersarenotifiedimmediatelyoneoftheirteam(MasterUser,SuperUsers,Reporters,RoamingReportersorSeniorReporters)submitsa“Draft”reporttothedatabase.This isdonebya system-generatede-mail andsignifies the startof the reviewandapprovalprocess.

7.2. Review

Theuser, assigned toapprove theevent record, should review thedraft record,using the “View”optionunderthe“Actions”tab,toensurethatthedataisaccurate,consistentwithfielddefinitionsasoutlinedinSection5.8andlogical.

Special attention should be paid to the section of the report that covers the “Event Data” withemphasisbeingplacedonthefree-textfield“Descriptionofevent”tomakesurethattheinformationprovidesafulldescriptionoftheevent,istotallyanonymizedandisbasedontheuseofvocabularyconsistentwithtechnicalreportwriting.

Acriticalaspectofthereviewofthedraftrecordisassociatedwithensuringconcurrencebetweenthereportedeventdataandtheselectedrootcause.

Atthispointtheusercanchoseto“Approve”thedraftrecordifitisdeemedtobesatisfactory(refertoSection7.4),“Return”thedraftreporttotheindividualthatcreatedthedraftrecordforediting,completewithanoteprovidingdetailsofwhatisrequiredtobeedited,or“Reject”thedraftrecordentirelyintheeventthatthedraftrecordisfoundtoberedundant,forwhateverreason.Rejecteddraftrecordsareneverdeletedfromthedatabasebutarearchived.

7.3. Editing

Intheeventthattheuser,taskedwithapprovinga“Draft”eventrecord,chosesto“Edit”the“Draft”eventrecordratherthan“Return”ittotheindividualthatcreatedthedraftrecord,theusershouldselectthe“Edit”optionunderthe“Actions”tabandproceedtonavigatethroughthevarioussectionsofthedraftrecord,editingthefieldsrequiringeditingwithineachsection,savingthechangesmadein each section prior tomoving to the succeeding section and ultimately submitting a newdraftrecordusingthe“Submit”tabprovidedinthelastsectionoftheprocess.

7.4. Approval

32


AsstatedunderSection7.2,the“EventReportView”(selectthe“View”optionunderthe“Actions”tab)isthemosteffectivewayofreviewingadrafteventrecordforcompletenessandaccuracyandforchanginganeventrecordstatusfromdrafttoapproved.The“EventReportView”alsoprovidestheuserwiththeabilitytoeditthe“Descriptionofevent”andthe“Rootcause”fields.Consequently,providingtheuserissatisfiedwiththedatacontainedelsewhereintheeventrecord,theuserhastheability,withthedrafteventrecordopeninthe“EventReportView”mode,toeditthe“Descriptionofevent”andthe“Rootcause”fieldswithoutopeninguptheentire“Draft”eventrecordforeditingpriortoapprovingtherecord.

Oncethe“Draft”eventrecordhasachievedthedesireddataqualitystandard,andwiththerecordopeninthe“EventReportView”mode(selectthe“View”optionunderthe“Actions”tab),theuser,taskedwith approving the event record, can approve the event record andmove it to either the“Approved(Open)”stateorthe“Approved(Closed)”state.

The“Approved(Open)”statuswillbeautomaticallyassignedtotheeventrecordifthevalueselectedfor the “Root cause” field is either “Assessment Pending” or “RCFA Required”. The “Approved(Closed)statuswillbeautomaticallyassignedtoalleventrecordswherethe“Rootcause”isoneoftheavailable,permittedrootcausevaluesotherthan“AssessmentPending”or“RCFARequired”.

33


8.0 Analysis

8.1. Basics

Effectiveinvestigationisessentialtoidentifytherootcausesofanevent.Theaccurateidentificationofrootcausesfacilitateslearning,continuousimprovementandleads,ultimately,tothereductionofpotential component malfunctions. The drive to reduce the number of potential componentmalfunctionsincreasestheinherentreliabilityandsafetyoftheequipmentusingthecomponent.

Theinitialscopeofanyinvestigationmustbebasedonthefactual information(e.g.hoserupture,valveleakinginclosedposition)relatingtotheevent.DiligentandeffectiveanalysisistheonlywaytoleadinvestigatorstooneoftherootcauseslistedinSection5.9.

It should be noted that if the component event being logged is part of a wider event then theappropriateinvestigativeproceduremayneedtobefollowedinadditiontothecreationofaneventreportforthecomponentatthecenteroftheeventbeinglogged.

8.2. Overview

Thereare three levelsofanalysis tobeappliedwithregard toevents recorded in theRAPID-S53database:

• CauseImmediatelyKnown.• SMEReview.• RootCauseFailureAnalysis.

Itshouldbenotedthatifaninvestigationatonelevelfailstodeterminetherootcauseofanevent,thentheanalysiscanbepromotedtothenextlevelup,asappropriate.

As shown in theReportingProcess flowchart (APPENDIX2), in aneventwhere the root cause isimmediatelyknown,therelevantnotificationsareissuedimmediatelyacomponentfailurereportissubmittedtothedatabaseandismovedtoan“Approved(Closed)”state.

Iftheeventresultsinalossofawellbarrier,ifitresultsintheretrievaloftheLMRPorBOPstack,or if it is identifiedaspartofaseriesofreoccurringevents, thenanRCFA isalwaysrequired.

OthereventsrequireanSMEReviewtobeconductedbyasubjectmatterexpert,andreported.

Itshouldbenotedthattherewillbeoccasionswhereeventsthathavepreviouslybeencategorizedas“CauseImmediatelyKnown”or“SMEReview”become“RCFArequired”becausesucheventshavebeenidentifiedasoccurringasignificantnumberoftimesand,asaresult,theeventsbecomeclassedas “Reoccurring”. The previously event records do not need to be reclassified, but theymay bereferredtointheRCFA.

8.3. CauseImmediatelyKnown

34


8.3.1. Approach

An O-ring damaged during installation can, for example, normally be categorized as ‘CauseImmediatelyKnown’.Itisimportanttoreportsucheventsbecauseifaneventofthistypeweretoescalate to a reoccurring event then itmaywarrant a change to the design or to the installationand/ormaintenanceprocedures.

8.3.2. Resources

TheSeniorSubseaEngineershoulddiscusswhathappenedwithanothertechnicalmemberofthecrewtodetermine:

• Whathappened?• Howithappened?• Whyithappened?

8.3.3. Closure

Whentherootcauseoftheeventisimmediatelyknown,theinvestigationisconsideredclosedwhen:

• Areportiscreatedinthedatabase,withsufficientjustificationprovidedinthe“Descriptionofevent”fieldtosupporttheroot-causeselectedfromthedropdownbox.

• TheselectionandthereportareapprovedbyanauthorizedEquipment-Owneruser.

8.4. SMEReview

8.4.1. Approach

An SMEReview is conductedwhen the cause of the event is questionable and the event has nottriggeredanRCFA(nolossofwellbarrier,nounplannedBOPpull,notpartofaseriesofreoccurringevents).

Ifaramfailedtoholdpressureduringpre-deploymenttestinganduponopeningthedoors/bonnetsitwasclearlyseenthatthepackerswerewellworn,thenanSMEReviewcouldchecktherecordstoseeifthenumberoffunctionsmettheexpectations.Thenaftertheramshavebeensuccessfullytestedwithnewpackerstoconfirmthattherewasnootherissue,andassumingthenumberoffunctionsmetexpectations,thefailurecanbeattributedto‘WearandTear’.If,however,theramsfailtotestandthefunctioncycleswerelessthanexpected,thecausalagentissomethingotherthan‘WearandTear’.

8.4.2. Resources

Two,ormore,SMEs.

8.4.3. Closure

35


AnSMEReviewReport(SeeAPPENDIX4), identifiedby theuniquenumberusedwhentheeventrecordwasinitiallycreated,mustbeproduced.Thisreportshouldarriveatalogicalconclusionbasedonasoundevaluationofthephysicalcausesofwhat,howandwhytheeventoccurred.TheincidentcanbeconsideredclosedwhentheauthorizedEquipment-Owneruserupdatestheeventrecordinthedatabase(byaugmentingtheinformationinthe“Descriptionofevent”field,asnecessary),selectsthe appropriate “Root cause” from thedropdownbox, andapproves the event record “Approved(Closed)”,thusmovingtherecordfromthe“Approved(Open)”statetothe“Approved(Closed)”state.

8.5. RCFA

8.5.1. Approach

Thisinvestigationismoredetailedandassuchtakesmoreresourcesandtime.

TheperformanceofaRCFAismandatoryiftheeventresultsinanyoneofthethreeconditionsshowninthefigurebelowbeingmet.

Thisanalysisshouldoutputrootcausesthatcanbeturnedintoactionitemstopreventreoccurrence;forexample,OEMproductbulletins,Equipment-Ownermaintenancesystemchanges,etc.

8.5.2. PhysicalEvidence

36


WellControlEquipmentcomponentsarefrequentlyfieldrepairableand,inmanycases,theremaynot be a replacement assembly readily available. In such an instance, ensuring full and detailedrecordcaptureofphysicalevidenceiscritical,evenifthesituationnecessitatestheevidencebeingintheformofphotographs,dimensions,sketchesandwrittenreports,toallowrepairstobeeffectedandtoultimatelygettherigbacktowork.

8.5.3. Resources

Typically,atleastoneSMEplustheOEMorasuitablyqualifiedthird-partyareutilized.

8.5.4. Closure

AnRCFAreport(SeeAPPENDIX4),identifiedbytheuniquenumberusedwhentheeventrecordwasinitiallycreated,mustbeproduced.Thisreportshouldarriveatalogicalconclusionbasedonasoundevaluationof thephysicalandanyhumancausesofwhat,howandwhy theeventoccurred.Thisdocumentisforinternalusewithintheaffectedcompany.

The incident can be considered closedwhen the authorized Equipment-Owner user updates theeventrecordinthedatabase(byaugmentingtheinformationinthe“Descriptionofevent”field,asnecessary), selects theappropriate “Rootcause” fromthedropdownbox,andapproves theeventrecord “Approved (Closed)”, thus moving the record from the “Approved (Open)” state to the“Approved(Closed)”state.

37


9.0 CaptureandShareLessonsLearnt

When these reports have been finalized and the event records approved, it is necessary for thelearningsfromtheeventtobesharedinternallywithintheequipmentowner’sorganizationandwiththeappropriatestakeholdersasdictatedbybothAPIStandard53andtheregulations.

Alessonisonlylearnedwhenthedataisproperlyshared.

The Information Bulletin section of JIP Monthly Report provides an ideal vehicle for thedissemination of anonymized information to the other organizations participating in the JIP andmembers are encouraged to submit summariesof theirownexperiences andpractices to the JIPProjectManagerforinclusionintheJIPMonthlyreport.

38


EventDataReportingOfflineInputForm(ROIF)

39


ReportingProcess

40


Five-Why’sAnalysisMethodology

Five-WhysAnalysisisasimpleiterativetechniquethatcanbeusedwitheithertheSMERevieworwithanRCFAtounderstandthecause-and-effectrelationshipsunderlyingaparticularproblem.Theprimary goal of the technique is todeterminethe(root)causeofaneventorproblembyrepeatingthequestion"Why?"

Eachquestion forms thebasisof thenextquestion.The"5"inthenamederivesfromanempiricalobservationonthenumberofiterationstypicallyrequiredtoresolvetheproblem.

Themethodprovidesnofixedrulesaboutwhatlinesofquestionstoexplore,orhowlong tocontinue thesearch foradditionalroot causes. The following outlines atypical5WhysAnalysisprocess:

Identify and define the componentinvolvedintheeventandthen:

• Definetheevent• Brainstorm and list the possible

causes• Select themost likely cause (must

be able to explain why it wasselected)

• Applythe“5Why”principle(ontheselected“mostlikely”cause)

• Repeatasking“why”untilthe“rootcause”isidentified

• Suggestpossiblesolution• Implement and validate the

solution

Q1.Whydidthiscomponent

fail?

Q2.Whydidthathappen?




A1.

A2.

A3.

A4.

A5.

41


SMERevieworanRCFAReport

Whilebeingcompanyspecificindesign,thefinalreportsmustinclude:

TheinitialreportuniqueidentificationnumberDetailsofthecomponentinvolvedintheevent(PartNumber,SerialNumber,Description,)DateoftheeventDetailsoftheeventDatethattheinvestigationcommencedDatethattheinvestigationwascompletedandthereportpublishedInvestigationteammemberdetailsRootcause(s)oftheeventFindings(includinganyphotographsordrawings, thirdpartyreportsorothersupportinginformation.Recommendations

42


LibraryofMakesandModelsStoredinDatabase

ANNULARBOP

ANNULAR CAMERON GE NOV

MODEL D GL Standard(BigBoy)MODEL

DL GX SL

MODEL T-84 GXCompact NXT

MODEL T-90 MSP 7012(OldT3)

RAMBOP

RAMBODY CAMERON GE NOV

MODEL EVO Compact 6012MODEL

T-81 Conventional NXT

T-82 Quik-Lok SL

MODEL TL SLX

MODEL U

MODEL UII

43


RAMBonnet/Door

BONNET/DOOR CAMERON GE NOV

MODEL EVO,SuperShear,4,000psi,N/ACompact, 14-1/4”, Low Torque,3,000psi,MPL

6012, 14” x 10” Booster,3,000psi,Poslock

MODEL

EVO, Tandem Booster, 5,000psi,EVOLock

Compact, 14-1/4”, PressureDifferential,3,000psi,MPL

NXT, 14” Booster, 3,000psi,Poslock

MODEL EVO,3,000psi,EVOLockCompact 15-1/2”, Low Torque,3,000psi,MPL

NXT 22”, CVX, 5,000psi,Poslock

MODEL T,3,000psiMOP,STLockCompact, 15-1/2” PressureDifferential,3,000psi,MPL

NXT, 22” LFS, 5,000psi,Poslock

MODEL T,3,000psiMOP,WedgelockCompact,19”LowTorque,3,000psi,MPL

NXT, 22” x 14”, 3,000psi,UltralockIIBILF

MODEL TL,SuperShear,3,000psi,N/ACompact,19”PressureDifferential,3,000psi,MPL NXT,3,000psi,Manual

MODEL TL,SuperShear,4,000psi,N/ACompact,22”PressureDifferential,3,000psi,MPL NXT,3,000psi,Poslock

MODEL TL,SuperShear,5,000psi,N/ACompact,22”PressureDifferential,4,000psi,MPL NXT,3,000psi,UltralockIIB

MODEL TL,TandemBooster,3,000psi,STLock

Compact,22”PressureDifferential,5,000psi,MPL

NXT, 3,000psi, Ultralock IIBILF

MODEL TL, Tandem Booster, 4,000psi,Ramlock

Compact,22”PressureDifferential,5,000psi,N/A

NXT, Booster, 4,500psi,Poslock

MODEL TL,TandemBooster,4,000psi,STLock

Conventional, 14-1/4” Low Torque,3,000psi,MPL SL,3,000psi,Poslock

MODEL TL,3,000psi,RamlockConventional, 15-1/2” Low Torque,3,000psi,MPL SL,3,000psi,UltralockIIB

MODEL TL,3,000psi,STLockConventional, 15-1/2” PressureDifferential,3,000psi,MPL SL,Booster,5,000psi,Poslock

MODEL TL,5,000psi,RamlockConventional, 19” Low Torque,3,000psi,MPL SL,OldT3,3,000psi,Manual

MODEL TL,5,000psi,STLock

Conventional, 19” PressureDifferential,3,000psi,MPL

SLX, 16” Booster, 3,000psi,Poslock

MODEL U, Large Bore with TandemBooster,3,000psiWedgelock

Conventional, 22” Low Torque,3,000psiMPL

SLX, 18” Booster, 3,000psi,Poslock

MODEL U, Large Bore, 3,000psi MOP,Wedgelock

Conventional, 22”, PressureDifferential,3,000psi,MPL SLX,3,000psi,Manual

MODEL U, Tandem Booster, 3,000psi,Manual

Quik-Lok, 14-1/4” Low Torque,3,000psi,MPL SLX,3,000psi,Poslock

MODEL UII, Tandem Booster, 3,000psi,Wedgelock

Quik-Lok, 14x14” Dual CylinderShearBoost,3,000psi,MPL SLX,3,000psi,UltralockIIB

MODEL UII, without cylinder, 3,000psi,Wedgelock

SLX, Booster, 5,000psi,Poslock

MODEL UII,3,000psiMOP,Wedgelock

MODEL U,3,000psiMOP,Wedgelock

MODEL U,3,000psi,Manual

44


BOPMountedChokeandKillValves

BOPC/KVALVES CAMERON NOV SRI WOM

MODEL AF–FailOpen DB–FailOpen FailOpen Magnum – FailOpen

MODEL

AF–FailClose DB–FailClose FailClose Magnum – FailClose

MODEL DF–FailOpen HB–FailOpen SL

MODEL DF–FailClose HB–FailClose SLX

MODEL FCS–FailOpen HPT–FailOpen

FCS–FailClose HPT–FailClose

MCS–FailOpen

MCS–FailClose

ChokeandKillStabs

CONNECTORS CAMERON GE NOV

MODEL Mini-Collet Stab1 Ext/RetLocking MODEL

Stab2 Ext/Ret Non-Locking

MODEL Stab3 FixedLocking

MODEL FixedNon-Locking

MODEL

ChokeandKillFlexLoop/Hose

CONNECTORS CONTITECH COPPERSTATE OILSTATE TECHNIP

MODEL HNBR 16CCompliant FlexLoop RilsanMODEL

NBR StainlessLined Coflon

MODEL NBR/CR Standard

MODEL PA

MODEL Taurocool

MODEL Tauroflon

45


Connectors

CONNECTORS CAMERON DRIL-QUIP GE NOV

MODEL DWHC DX-10 H4DWHD CHXMODEL

EVO-Con DX-15 H4DxE

MODEL HC DX-DW H4E

MODEL HCH4 DQ-DX H4ExF

MODEL Model70 DQ-VX H4ExFHAR

MODEL H4SHD

RiserMandrel


MODEL DWHC DX H4 H4MODEL

H4 H4

MODEL HC

FlexJoint

CONNECTORS CAMERON GE OILSTATES

MODEL FlexKing6.0 Annuflex SubseaLP MODEL

Subsea2.0

MODEL Subsea2.5

MODEL Subsea3.0

MODEL Subsea3.5

MODEL Subsea4.0

MODEL Subsea5.0

MODEL Subsea6.0

46


ConduitFlexLoop/Hose

CONNECTORS CONTITECH COPPERSTATE OILSTATE TECHNIP

MODEL HNBR 16CCompliant FlexLoop RilsanMODEL

NBR StainlessLined Coflon

MODEL NBR/CR Standard

MODEL PA

MODEL Taurocool

MODEL Tauroflon

Riser

RISER AFGLOBAL CAMERON GE MHWIRTH NOV

MODEL UDWHybrid RCK HMF-D CLIP DT-1MODEL

RF HMF-E QTR-4000LS DT-2

MODEL LoadKing2.0 HMF-F QTR-3500 DT-E

MODEL LoadKing2.5 HMF-G DT-F

MODEL LoadKing3.0 HMF-H DT-G

MODEL LoadKing3.5 HMF-J FT-GB

LoadKing4.0 MR-10 FT-H

LoadKing4.5 MR-6C FT-HB-DG

RD21 MR-6E FT-I

MR-6HSE UDW

FT-DGD

DiverterHousing


MODEL 49-1/2” 49-1/2”

49-1/2” 49-1/2”MODEL

60” 60” 60” 60”

MODEL 75” 75” 75” 75”

47


DiverterAssembly


MODEL CF-A CSO CSO CSOMODEL

CF-B KFDJ

MODEL KFDS

ChokeManifoldValves

VALVES CAMERON NOV QOT WOM

MODEL FC B QFC MagnumMODEL

FLS F-C

MODEL T-B

HPY

E-Mk2

AutoChokes

AUTOCHOKE CAMERON EXPRO NOV QOT MASTERFLO SWACO

MODEL Hydraulic SCB2 MS QC P25 SuperChokeMODEL

CSO(Varco)

MODEL CSO3-15x3-10

MPX-40D

HxEG3

ManualChokes

MANUALCHOKE CAMERON EXPRO NOV QOT MASTERFLO

MODEL Manual SCB2 B-H2 QH2 P25 MODEL

E-S

MODEL CSO3-15x3-10

HxEG3

48


BOPControlPods

PODS AXON CAMERON GE KOOMEY NOV OCEANEERING

MODEL Type80 Hyd48Line Hyd-P56B Hyd46line Hyd42Line Hyd68LineMODEL

HydModular MUXGen1 Hyd60Line MUX98Line

MODEL MUXMk-I MUXGen2 Hyd64Line MUX132Line

MUXMk-II MUXGen3 Hyd80Line

MUXMk-III SeaOnyx MUX80Line

MUXMk-IV MUX9XLine

MUX112Line

MUXRCX

49


UserAccessRightsMatrices

50


51


FurtherGuidanceonTerms“InOperation”&“NotinOperation”

Thefollowingparagraphscontainexampleswhichshouldhelpprovidefurtherguidanceontheterms“InOperation”and“NotinOperation”.

ThesubseaBOPstack is testedondeckand thenrundown to thewellheadand theconnector islatched.Thepre-initialsubseatestingworkiscarriedoutandthetestassemblyisrunintothestack.Thefirstramsinthesequenceundergoa250-350psitestforfiveminutesandthentotheapprovedwellpressureforfiveminutes.UponacceptanceofthesetestresultstheBOPstack,fromaRAPID-S53eventreportingperspective,isnow“InOperation”.

Whiledrillingthewellthereisamalfunctionofthemanifoldregulatorinthebluepodwhichcannotbemitigated.Appropriatebarriersareinstalledtomakethewellsafe,theriserisdisplacedtoseawaterandthestackisunlatchedtorecoverittosurfaceforrepairs.Thisisa“StackPull”andthestackisnow“NotinOperation”.Theregulatorisrepairedonsurfaceandtherequiredtestingiscomplete.ThesubseaBOPstackisthenrundowntothewellheadandtheconnectorislatched.Thepre-initialsubseatestingworkiscarriedoutandthetestassemblyisrunintothestack.Thefirstramsinthesequenceundergoa250-350psitestforfiveminutesandthentotheapprovedwellpressureforfiveminutes.Upon acceptanceof these test results theBOP stack, fromaRAPID-S53 event reportingperspective,isnow“InOperation”.

TheweatherhasturnedbadanditisnecessarytounlatchtheLMRPtorideoutthestorm.Thepipeispulledandtheshearramsareclosed.TheLMRPconnectorisunlatchedandtherigmovesawayfromthewell.Thisisa“StackPull”andthestackis“NotinOperation”.Thestormhaspassed.Therigreturnstolocation,theROVinspectstherisermandrelandtheLMRPislandedandlatchedtothelower stack. The necessary tests are successfully completed and the BOP stack is then back “InOperation”.

Thedrillingprogramiscomplete.Theregulatorybarriersareinplace;theriserhasbeendisplaced.Thewellheadconnectorisunlatchedandthestackliftedoffthewellhead.TheBOPstackisnow“NotinOperation”.

rapid-s53 guidance document rev 2 draft 112217 guidance document rev 2... · will immediately...

Documents