API RP 1130

Abstract

<strong>Scope Limitations</strong> <br>This recommended practice is not all-inclusive. The reader must have an intimate knowledge of the pipeline system and may have to refer to other standards for background or additional information <br>This recommended practice was written considering single phase, liquid pipelines. However many of the principles apply to liquid pipelines in intermittent slack line flow or liquid pipelines that may have permanent slack line flow. Slack line operation creates uncertainties in pressure and flow. For these operating conditions, the user of API RP 1130 will have to carefully consider what parts of API RP 1130 do and do not apply. <br>This recommended practice also may not apply to the special case of determining leaks during shut-in conditions that occur when the line is shutdown (sometimes called static conditions). For example, a Volume Balance CPM cannot evaluate volume loss if there is no flow through the meters during a line shutdown. <br>It is recognized that no one particular CPM methodology or technology may be applicable to all pipelines because each pipeline system is unique in design and operation. In addition, detectable limits are difficult to quantify because of the unique characteristics presented by each pipeline. Limits must be determined and validated on a system-bysystem and perhaps a segment-by-segment basis. <br>CPM is intended to enhance human judgement when some type of intervention or shutdown of the affected pipeline segment(s) is warranted. Effective operation of a pipeline requires that the Pipeline Controllers be familiar with the pipeline and all the tools at their disposal. CPM can also enhance human judgement during decisions to activate remotely controlled valves and directing field staff to re-position hand operated valves on the pipeline. <br>This recommended practice complements but does not replace other procedures for monitoring the integrity of the line. CPM systems, as well as other commodity release detection techniques, have a detection threshold below which commodity release detection cannot be expected. Application of the information in this recommended practice will not reduce the threshold at which a commodity release can be detected. For example, trained Pipeline Controllers analyzing SCADA-presented operating data can be effective at detecting certain sizes (i.e. larger) of commodity releases. Third party reports, pipeline patrols, and employee on-site examinations can also be effective procedures when used to verify the integrity of the pipeline within their range of applicability. <br>It is important to note that this recommended practice is in keeping with standard industry practice and commonly used technology; however, it is not intended to exclude other effective commodity release detection methods. <br>Annex A provides a discussion of CPM thresholds and other information related to understanding pipeline leaks and practical detection limits for commodity releases. <br><strong>Purpose</strong> <br>This recommended practice focuses on the design, implementation, testing and operation of CPM systems that use an algorithmic approach to detect hydraulic anomalies in pipeline operating parameters. The primary purpose of these systems is to provide tools that assist Pipeline Controllers in detecting commodity releases that are within the sensitivity of the algorithm. It is intended that the CPM system would provide an alarm and display other related data to the Pipeline Controllers to aid in decision-making. The Pipeline Controllers would undertake an immediate investigation, confirm the reason for the alarm and initiate an operational response to the hydraulic anomaly when it represents an irregular operating condition or abnormal operating condition or a commodity release. <br>The purpose of this recommended practice is to assist the Pipeline Operator in identifying issues relevant to the selection, implementation, testing, and operation of a CPM system. It is intended that this document be used in conjunction with other API standards and applicable regulations.