Recommended Practice for Reliability, Technical Risk, and Integrity Management
- Adam Wilson (JPT Special Publications Editor)
- Document ID
- Society of Petroleum Engineers
- Journal of Petroleum Technology
- Publication Date
- August 2014
- Document Type
- Journal Paper
- 108 - 111
- 2014. Offshore Technology Conference
- 1 in the last 30 days
- 114 since 2007
- Show more detail
- View rights & permissions
|SPE Member Price:||Free|
|SPE Non-Member Price:||USD 17.00|
This article, written by Special Publications Editor Adam Wilson, contains highlights of paper OTC 25412, "API RP 17N - Recommended Practice for Subsea-Production- System Reliability, Technical-Risk, and Integrity Management," by John Strutt, Astrimar, and Don Wells, SPE, Hess, prepared for the 2014 Offshore Technology Conference, Houston, 5-8 May. The paper has not been peer reviewed.
The American Petroleum Institute Recommended Practice 17N (API RP 17N) provides a structured approach that organizations can use to manage risk and uncertainties related to reliability and integrity performance throughout the life of a project. The basic approach is simple and consistent and has the potential to reduce the financial risk of designing, manufacturing, installing, and operating subsea equipment or systems. This paper presents the principles and approaches used in API RP 17N, and discusses what it is in general and why it was written. It also describes the status of its recent update.
Why API RP 17N Was Originally Developed
Throughout the 1990s and the early 2000s, there were widespread concerns relating to the reliability of subsea technologies. A number of operators of subsea fields were experiencing equipment failures that had significant adverse effects on production. Many of these failures occurred in the early stages of production and involved more than one component.
Although there are elements of chance in all accidents and failures, when actual failures are studied, the root causes always amount to a failure of management to identify, assess, or manage the risks that they faced. Moreover, the causes of failure cannot be leveled at one organization.
To ascertain the root causes, it would be necessary to address industry reliability- management practices not only during operations but also at the design stage, where there is the greatest opportunity to influence component- and system-reliability performance. Tackling the problem on a company-by-company basis was also not viable. Likewise, it was not realistic for suppliers, with a wide customer base, to invest in reliability-management practices to meet the requirements of just one or two customers in particular. What was required was some form of guidance on reliability and its management that the whole subsea industry and its supply chain could buy into. This was the reason for the development of API RP 17N.
The Principles of API RP 17N
API RP 17N was developed to provide guidance to the subsea industry on the management of reliability and technical risk related to subsea production systems. The objective is to provide a common language and approach to the management of reliability that the whole industry could accept as good practice and that could be used to help all companies achieve higher levels of reliability performance.
The 2009 edition of API RP 17N has a particular focus on production reliability and availability and the management of risks to reliable production performance. Its underpinning assumptions are that
- The achievement of system availability will add value to a field development through maximization of equipment reliability and minimization of intervention for maintenance or replacement of failed equipment.
- The achievement of equipment reliability and system availability is primarily founded on the implementation of good reliability and technical riskmanagement practices formally integrated with good subsea engineering using the best available analytical tools and techniques to inform engineering decisions throughout the project life cycle.
- Reliability is a core business value that companies are seeking to achieve.
The approach had to be sufficiently generic to be applicable to a wide range of companies and company organizational structures but, at the same time, sufficiently well-defined to enable companies to check their compliance with the practice. The approach adopted by API RP 17N is based on a set of 12 key processes considered necessary for effective management of reliability and technical risk. The 12 key processes are broken down into four categories of process.
|File Size||115 KB||Number of Pages||3|