API RP 17A DESIGN AND OPERATION OF SUBSEA PRODUCTION SYSTEMS
STATUS REPORT
API C2 / SC 17SUBCOMMITTEE ON SUBSEA PRODUCTION SYSTEMS
API 17A RECOMMENDED PRACTICE
for
DESIGN AND OPERATION OF SUBSEA PRODUCTIONSYSTEMS
REVISION TASK GROUP STATUS
JANUARY 2013
API RP 17A DESIGN AND OPERATION OF SUBSEA PRODUCTION SYSTEMS
STATUS REPORT
1.introduction
The API 17A document, most recently issued by API in January 2006, is currently being revised and updated. Revision to the document had beenled by ISO, with support from an API workgroup.Following the recent changes in the API/ISO relationship this review needs to be taken over by API.
2.status
Due to changes in the task force, the high level of industry activity and ongoing concerns regarding working with ISO, little progress has been made since June in revising API 17A.
A draft of an API 17A Recommended Practice for subsea pressure testing and test pressure limitations/evaluation has been completed. This draft will be iincluded as a New Annex in 17A (when it is updated)
API Task Group
The supporting API task group comprises:
TABLE 1-1: API 17A Task Group Members
Name / Company / e-mailJohn Upchurch / Technip/Genesis /
John McManus / Aker Solutions /
Ross Frazer / ATP /
Harold Reeves / BP /
Chris Curran / BP /
Mark Siegmund / BP /
Ray Flemming / BP /
David Morgan / Cameron /
Ron Pfluger / Cameron /
Dewey Compton / Chevron /
Chris White / Doris /
KrassimirDoynov / ExxonMobil /
Brian Skeels / FMC /
Mike Williams / FMC /
Bobby Voss / GE /
Steve Mansfield / J P Kenny /
Ian Still / Shell /
Rick Hill / Universal Pegasus /
Felipe Ramirez / Universal Pegasus /
3.uPDATED TARGET DATES FOR DELIVERABLES
The target for issuing an updated version of 17A is yearend 2013.
4.MAJOR ISSUES
The high level of industy activity is putting a strain on resources, slowing work on the revision to 17A.
5.anticapted new work items
None.
6.plans for future meetings
A meeting for the API 17A task force will be scheduled for February 2013. The primary deliverable from this meeting will be a schedule for completing the revision to API 17A.
In order to facilitate issuing of a revised API 17A document we do not plan on a complete rewrite of the document. Rather, we will be reviewing the existing API 17A document, comparing it to ISO 13628-1 and revising sections that have seen major technological changes or additions. We will attempt to resolve / eliminate contradictions between the two documents, but we will not be trying to make the documents identical.
7.RESOURCE NEEDS
Resource requirements for this work will also be identified at the February meeting.
-1-June 28th, 2011