API RP 17A - Discussion Points

Slides:



Advertisements
Similar presentations
INSPIRE Drafting Team „Data Specifications“
Advertisements

SEM10-04 Initiation of a Work Item ETSI Seminar © ETSI All rights reserved.
SC8 Liaison Report API SC8 – Subcommittee on Drilling Structures & Equipment Chair: Robert Urbanowski Vice-Chair: Mark Trevithick.
Don Wells Hess Corporation
SUBSEA PRODUCTION SYSTEMS (SC17) Liaison Report
How an idea becomes an IEC standard Gary Johnson Chairman IEC SC45A
SC8 Liaison Report API SC8 – Subcommittee on Drilling Structures & Equipment Chair: Mark Trevithick.
Kent Grebing, API SC 16 Chair
Page 1 ISO/IEC JTC 1/SC 7/WG 7 N Summary of the Alignment of System and Software Life Cycle Process Standards The material in this briefing.
9104/1 Rewrite Team Report / Review to the AAQG-RMC 11 March 2009 Michael C Roberts Boeing, Technical Fellow.
API WIWC TG-5   Well Intervention Well Control   Task Group   Winter Conference Update   Alex Sas-Jaworsky P.E   Chairman.
DICOM to ISO-DICOM Report to joint ISO TC215/WG2 – DICOM WG10 meeting January 24, 2004, San Diego.
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP m-session-63-closing-report Title: m Session #63 Closing Report Date Submitted:
Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC-18 Liaison Report TG-3: Definition of.
WG or TG # SC17 Liaison Report Mohsen Shavandi / Virgilio Garcia Soulé SC17 Liaisons Update from SC18 Summer 2013 Meeting January 2014.
Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC18 Liaison report for SC6 Rick Faircloth.
API 17N (and Q) Subsea Production System Reliability, Integrity, and Technical Risk Management.
Doc.: IEEE /0281r1 Submission James D. Allen (Appairent Technologies, Inc.) Project: IEEE P Working Group for Wireless Personal Area Networks.
Doc.: IEEE /0147r0 Submission January 2012 Rolf de Vegt (Qualcomm)) Slide ai Spec Development Process Update Proposal Date:
San Francisco, CA. SC8 Liaison Report
Doc.: IEEE Submission March, 2014 Pat Kinney, Kinney ConsultingSlide 1 Project: IEEE P Working Group for Wireless Personal Area.
Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC18 Liaison report for SC6 Rick Faircloth.
Task Group API 19SS Sand Screens
API SC19 HPHT Template (Proposed as SC19TR1)
Prepared by Rand E Winters, Jr. ASR Senior Auditor October 2014
API SC 10, Work Group 3 Update:
Updates from SC18 Summer Meeting
Task Group API 19SS Sand Screens
TG Chair: Darrin Willauer Baker Hughes
SC 6 Task Group 1 Pipeline and Valve Standards Status Report
API 17Q Proposed Technical Changes to Rev 0
Part C State Performance Plan/Annual Performance Report:
Standards and Certification Training
Jan Project: IEEE P Working Group for Wireless Local Area Networks (WLANs) Submission Title: Liaison Report, January 2003 Date Submitted:
API 17Q – Subsea Equipment Qualification
ISO Task Group Update Wayne Mabry.
  API SC 17 Subcommittee on Subsea Production Systems   API RP 17U   Recommended Practice for Wet and Dry Thermal Insulation of Subsea Flowlines.
I & C TC Korea Chapter Liaison Report
Specification on float equipment
ISO TC64/SC4/WG2 May 2011 status
First 8 slides are what was presented in San Fransisco…
RAISING PERFORMANCE. TOGETHERTM
Informal document GRSG
API SC-16 task group for Specification 16D
API SC 10, Work Group 3 Update:
WG Technical Editor’s Report
API 16TR2 now 16TR1 June 2017 Shear Ram Performance Test Protocol
API 17H TASK GROUP January 15, 2013.
Standards Break Out Session
API Summer Standardization Conference
API 17P SUBSEA STRUCTURES & MANIFOLDS
<month year> doc.: IEEE < e> <July 2018>
RTI University ScorecarD
NERC Reliability Standards Development Plan
<month year> doc.: IEEE < e> <May 2018>
<month year> doc.: IEEE < e> <May 2018>
Specification on float equipment
<month year> doc.: IEEE < e> <Mar 2018>
API Publication Types From “API Document Format and Style Manual” and “Procedures for Standards Development” the following are “standards” 1. Bulletin.
NERC Reliability Standards Development Plan
Discussion Points API RP 17A Task Group Members
WG Technical Editor’s Report
Singular Selection of Format
API RP 17Q Status January, 2014 First Edition issued June 18, 2010
Submission Title: [LB 28 Results] Date Submitted: [14 March 2005]
doc.: IEEE <doc#>
[Ballot code, contract number] [Project title]
  API SC 17 Subcommittee on Subsea Production Systems   API RP 17U   Recommended Practice for Wet and Dry Thermal Insulation of Subsea Flowlines.
API 17H TASK GROUP June 26, 2013.
API 16C Choke and Kill Equipment
Presentation transcript:

API RP 17A - Discussion Points Task Group Members There are over forty task group members which includes the Work Group Chair for each of the other API 17 series documents. updated TARGET DATES FOR DELIVERABLES Currently addressing the comments received from the last send out. The document will then be submitted to API for editorial review and future ballot. MAJOR ISSUES There were two actions noted in the June meeting to address the major issues outstanding on the document. They are: Action: The task group is to address “What is the purpose of this document?” Action: API 17A is the “traffic-cop” to determine content with other SC17 documents. These will be addressed in the next two slides. API RP 17 A – Winter 2016 Update

API RP 17A - Discussion Points Action: What is the purpose of this document? - This has not changed and is stated in the beginning of the document: API RP 17A provides general requirements and recommendations for the development of subsea production systems, from the design phase to decommissioning and abandonment. System Engineering has already been addressed in this document and its sister ISO document in previous revisions. This latest revision has expanded the information on it since no other API 17 series document addresses it. This is also an area that can be further expanded on in the future. However how general requirements and recommendations are addressed in the document has changed: Equipment requirements intended to specific types of equipment have been removed. Previously the document did have to state requirements for equipment not covered in a specific API 17 series document, however now there are specific documents for all major subsea equipment. Reference and describe the other API 17 series documents and technical reports in the document. This provides an overview of all of the API 17 series documents . Additionally: Proposes common terminology for testing in API 17 series documents. This is being worked with the API 17Q Task Group. Title of Presentation

API RP 17A - Discussion Points Action: API 17A is the “traffic-cop” to determine content with other SC17 documents. In the June meeting, the Chairman emphasized that all Task Group Leaders are members of the 17A Task Group and should collectively make decisions as to what is kept in individual documents versus what should be elevated for general coverage in 17A. To address this the following approach was taken: To avoid duplication of equipment requirements in multiple documents, API 17A does not repeat requirements which already existed in another document for equipment.  Instead it references the other document. API 17A cannot impose requirements on subsea equipment across multiple API 17 series documents without agreement by their Task Groups that they are correct and acceptable for their equipment. This resulted in the document moving to using general statements since it is not only difficult to state a requirement that works across several types of equipment, but it is also difficult for other Task Groups to meet to review the 17A document to see if there are issues. This is especially true for Task Groups that are not regularly meeting at this time. Title of Presentation

TR13 and TR14 - Discussion Points TR13 - General Overview of Subsea Production Systems updated TARGET DATES FOR DELIVERABLES Document already balloted. All comments addressed and document now ready to be published. MAJOR ISSUES There are no issues. TR14 - Flow Assurance It is the recommendation based on the comments received and subsequent discussions that this document is not released and the project is closed. To conclude this work a formal vote is needed. This was discussed in the August meeting. A straw vote was then taken and everyone was in agreement to close the project without releasing a document at that time. API RP 17 A – Summer 2015 Update