Rev 2 November 27, 2017 Please e-mail any feedback you may have on this Revision of the document to Mike Kucharski (IADC JIP Project Manager) at ([email protected]) RAPID-S53 Reliability and Performance Information Database For: API S53 Well Control Equipment Guidance Document
51
Embed
RAPID-S53 Guidance Document Rev 2 Draft 112217 Guidance Document Rev 2... · will immediately comply with any directions given by The IADC Project Manager ... , the above list defines
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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.
No JIP Participant will, directly or indirectly, receive from or give, or offer to give, anything ofmaterialvaluetoanyotherJIPParticipant,contractor,official,orotherpersonassociateddirectly,orindirectly,withtheexecutionoftheJIP.
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.
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.
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.
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.
SubjectMatterExpert: Person or personswith an in-depth knowledge of asubject of interest. Suchknowledgewill havebeengained through direct and practical dealings withsubjectmatterofinterest.
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.
With all of the above in place the database is set up to auto-populate the non-technical fieldsassociatedwithgeneratinganincidentreport,thus,reducingtheamounttimespentbyEquipmentOwneruserscreatingeventrecords.
OnlyMasterUsersareauthorizedtosetupnewusersforEquipmentOwnersandusersrequiringaccess to the database should send an internal e-mail to their nominatedMater User requestingaccess.
Onceinthedatabase,userscanutilizethe“MyProfile”(toprightcorneroflandingpage),“ChangeYourPassword”and“SaveChanges” tabs topersonalize their log-onbasedontheuseofastrongpasswordthatiseasyfortheindividualusertoremember.
The “Start Date” and ”End Date” data, required in the “Period of validity” section of the WCEConfigurationsetupprocess,areusedtoprovideinformationonequipmentoperatingperiods,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.
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.
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”.
Rig: Thisdropdownboxisfilteredtoshowonlythecurrentrigsownedby the selectedequipmentowner.Use thisdropdownboxtoselectthenameoftherigassociatedwiththeevent.
Operator: This dropdown box is populated with a list of thecurrent participating operators contained in the
Owner’sPrimaryContact: Title of person who is familiar with the issue in casefurtherinformationisrequired.Thiscouldbethepersonreporting,butthatisacompanydecision.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
“Assessment Pending” should be selected if, for instance, the BOP stack is still subsea. TheunderstandingisthatthefailurewillbeinvestigatedwhentheBOPstackbecomesaccessibleandtherootcausewillbeevaluatedatthattimeandtheeventrecordupdatedtoreflectthemostcurrentunderstandingoftherootcause.
Itisimportanttounderstandthattheselectionofeitheroftheaboveoptionsdoesnot,andwill not, automatically initiate the investigation and analysis processes. The EquipmentOwnermustaddressthisoutsideofthedatabaseand,intheeventthatanRCFAisrequired,thismustinvolvetheOEMorasuitablycompetentthird-party.
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.
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.
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.
Selectionof the “ProceduralError”optionsignifies that therewasamistake,misuseoroversightduringoperation.Thiscouldbe that theBOPram leakedbecause testpressurewasappliedafterclosingpressurewasvented,butwithouttheramhavingfirstbeenmechanicallylocked.Thiswasaproceduralerror.
The“WearandTear”optionshouldonlybeselectediftherootcauseofthefailuredoesnotfitoneofthe other root cause options and where a component has irrefutably failed before reaching itsintendedmaintenanceintervalorcyclecount.
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.
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.
Thisselectionwillprovidetheuserwithalistofalltheorganization-specificeventrecordsthathavebeencompletedandsubmitted,witheventdatesthatfallwithintheperiodselectedonthelastfiltertab, and that are waiting approval by either the Equipment-Owner Master User or one of the
Theuserhastheabilitytoviewtheapprovedeventrecorddataforeventsthatoccurredduringthecurrentmonthbysubunitandwiththeemphasisbeingplacedontheimpactofthecurrentmonth’seventsonproductivity.Inaddition,thenumberofeventrecordsforthecurrentmontharecomparedwith the numbers from previousmonths, benchmarked by relating the number of events to thenumberofworkingrigsavailabletoproducerecords.Thiscomparisonisavailableforthelast12andlast60months.
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.
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.
Thismoduleprovidesuserswithalistoforganizationsthatarecontainedinthedatabaseandareavailableforuseinthecreationofeventrecords.Italsoprovidesuserswiththeabilitytocontroltheir organization’s access to the database in terms of the number of users, type of users, rigassignmentsandtheallocationofsystemcredentials.
Itshouldbenotedthatthedifferencebetweenadatabase“Participant”andaJIPParticipantisthatonly JIP Participants have user-access to the database. A list of the user roles available to JIPParticipants,andtheirassociatedaccessrights,isprovideinAPPENDIX6.
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.
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.
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.
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.
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”.
Effectiveinvestigationisessentialtoidentifytherootcausesofanevent.Theaccurateidentificationofrootcausesfacilitateslearning,continuousimprovementandleads,ultimately,tothereductionofpotential component malfunctions. The drive to reduce the number of potential componentmalfunctionsincreasestheinherentreliabilityandsafetyoftheequipmentusingthecomponent.
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:
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.
Itshouldbenotedthattherewillbeoccasionswhereeventsthathavepreviouslybeencategorizedas“CauseImmediatelyKnown”or“SMEReview”become“RCFArequired”becausesucheventshavebeenidentifiedasoccurringasignificantnumberoftimesand,asaresult,theeventsbecomeclassedas “Reoccurring”. The previously event records do not need to be reclassified, but theymay bereferredtointheRCFA.
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.
An SMEReview is conductedwhen the cause of the event is questionable and the event has nottriggeredanRCFA(nolossofwellbarrier,nounplannedBOPpull,notpartofaseriesofreoccurringevents).
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.
WellControlEquipmentcomponentsarefrequentlyfieldrepairableand,inmanycases,theremaynot be a replacement assembly readily available. In such an instance, ensuring full and detailedrecordcaptureofphysicalevidenceiscritical,evenifthesituationnecessitatestheevidencebeingintheformofphotographs,dimensions,sketchesandwrittenreports,toallowrepairstobeeffectedandtoultimatelygettherigbacktowork.
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.
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.
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
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”.