API 17 H ROVROT Interfaces January 2016 BACKGROUND

API 17 H ROV/ROT Interfaces January, 2016

BACKGROUND • API 17 H 2 nd edition was published in June 2013 • API 17 M was withdrawn and replace with API • • 17 H Errata to correct hot stab drawings issued January 2014 SRRR has been submitted and accepted for the third revision

API 17 H TEAM MEMBERS Name Company E-mail Charles White BG Norge Charles. white@bg-group. com Andy Lee FMC Andy. lee@fmcti. com Brian Skeels FMC Brian. skeels@fmcti. com Karl Schnakenburg BHP Karl. Schnakenburg@BHPBilliton. com Didier Renard Technip drenard@technip. com Erich Luzi Statoil Luzi@statoil. com Steve Liso Chevron sliso@chevron. com Eirik Kloster Jacobsen Blue Logic ekj@bluelogic. no Aiyueh. Kwan@bp. com BP

CURRENT STATUS • Inquiries related to second edition hotstab drawings recieved • Released Errata to correct Figure 20 January 2014 • Held several meeting to review inquiries related to hotstab drawings • 17 TR 15 currently out for ballot

CURRENT STATUS • Historically the hotstab drawings have been donated to API • use the drawings as provided without making any design changes to the design • drawings do not use a common approach – for stab/receptacle alignment – seal squeeze/location – panel clearance requirements – datum for dimensioning • misinterpretation of the drawings and a number of inquiries to the taskgroup

CURRENT STATUS • Task group is recommended to publish a technical report related to the hotstab drawings – Normalize the drawings – Clarify the intent of the drawings as interface drawings – Adopt new straegy to control the recepticle dimentions – Allow more freedom for manufactures to innovate male hot stab designs while maintaining subsea interchangeabiltiy

CURRENT STATUS • SRRR issued to develop hotstab technial report • Technical report to be issued for comment ballot (December 2015) • Contents of technical report will be incorporated into 3 rd edition API 17 H

CURRENT STATUS Focus areas for the next edition are: • Incorporate comments from hotstab technical report • Clarification of quality requirements • Consider outstanding comments left from the previous edition • Add references to recently released recommended practice • Incorporate Deepstar AUV Document into API 17 H

NEXT STEPS • Resove any comments to 17 TR 15 • Issue hotstab technical report • Continue work on third edition API 17 H

MILESTONES