1、Computational Pipeline Monitoring for LiquidsAPI RECOMMENDED PRACTICE 1130FIRST EDITION, SEPTEMBER 2007REAFFIRMED, APRIL 2012Computational Pipeline Monitoringfor LiquidsPipeline SegmentAPI RECOMMENDED PRACTICE 1130FIRST EDITION, SEPTEMBER 2007REAFFIRMED, APRIL 2012Special NotesAPI publications neces
2、sarily address problems of a general nature. With respect to particular circumstances, local,state, and federal laws and regulations should be reviewed.Neither API nor any of APIs employees, subcontractors, consultants, committees, or other assignees make anywarranty or representation, either expres
3、s or implied, with respect to the accuracy, completeness, or usefulness of theinformation contained herein, or assume any liability or responsibility for any use, or the results of such use, of anyinformation or process disclosed in this recommended practice. Neither API nor any of APIs employees,su
4、bcontractors, consultants, or other assignees represent that use of this recommended practice would not infringeupon privately owned rights.Classified areas may vary depending on the location, conditions, equipment, and substances involved in any givensituation. Users of this recommended practice sh
5、ould consult with the appropriate authorities having jurisdiction.Users of this recommended practice should not rely exclusively on the information contained in this document. Soundbusiness, scientific, engineering, and safety judgment should be used in employing the information contained herein.API
6、 publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure theaccuracy and reliability of the data contained in them; however, the Institute makes no representation, warranty, orguarantee in connection with this publication and hereby expressly discl
7、aims any liability or responsibility for loss ordamage resulting from its use or for the violation of any authorities having jurisdiction with which this recommendedpractice may conflict.API publications are published to facilitate the broad availability of proven, sound engineering and operating pr
8、actices.These publications are not intended to obviate the need for applying sound engineering judgment regarding whenand where these publications should be utilized. The formulation and publication of API publications is not intended inany way to inhibit anyone from using any other practices.Any ma
9、nufacturer marking equipment or materials in conformance with the marking requirements of an API standardis solely responsible for complying with all the applicable requirements of that standard. API does not represent,warrant, or guarantee that such products do in fact conform to the applicable API
10、 standard.All rights reserved. No part of this work may be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from the publisher. Contact the Publisher, API Publishing Services, 1220 L
11、 Street, N.W., Washington, D.C. 20005.Copyright 2007 American Petroleum InstituteForewordNothing contained in any API publication is to be construed as granting any right, by implication or otherwise, for themanufacture, sale, or use of any method, apparatus, or product covered by letters patent. Ne
12、ither should anythingcontained in the publication be construed as insuring anyone against liability for infringement of letters patent.This document was produced under API standardization procedures that ensure appropriate notification andparticipation in the developmental process and is designated
13、as an API recommended practice. Questionsconcerning the interpretation of the content of this recommended practice or comments and questions concerning theprocedures under which this recommended practice was developed should be directed in writing to the Director ofStandards, American Petroleum Inst
14、itute, 1220 L Street, N.W., Washington, D.C. 20005. Requests for permission toreproduce or translate all or any part of the material published herein should also be addressed to the director.Generally, API standards and recommended practices are reviewed and revised, reaffirmed, or withdrawn at leas
15、tevery five years. A one-time extension of up to two years may be added to this review cycle. Status of therecommended practice can be ascertained from the API Standards Department, telephone (202) 682-8000. A catalogof API publications and materials is published annually and updated quarterly by AP
16、I, 1220 L Street, N.W.,Washington, D.C. 20005.Suggested revisions are invited and should be submitted to the Standards Department, API, 1220 L Street, NW,Washington, D.C. 20005, standardsapi.org.iiiContentsPage1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Contents . . . . . . . . . . . . . .
18、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Scope Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
19、1.4 Transportation Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.5 Regulatory Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20、 . . . . . . . . . . 22 Applicable References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21、 . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Technical Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.1 Leak Detection Technology . . . . . . . . . . . . . . . . . . . . . . . . . .
22、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2 Selection Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.3 Commodity Properties. . . . . . . . . . . . . . . . . . .
23、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Infrastructure Supports for CPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.1 Field Instrumentation and Measurement. .
24、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.2 Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.3 SCADA. . . . . . . . . . .
25、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.4 Data Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26、 . . . 195.5 Integration of CPM and SCADA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205.6 Data Historian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27、 . . . . . . . . . . . . . . . . 206 CPM Operation, Maintenance, and Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.1 CPM Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28、 . . . . . . . . . . . . . . . . . . . . . . 206.2 System Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.3 Operating Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256.4 CPM System Data Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.5 Pipeline Controller Training and Retraining . . . . . . .
30、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.6 CPM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Annex A Discussion of CPM Thresholds. . . . . . .
31、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Annex B Description of Types of Internal Based CPM Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Annex C Metrics and Other Pertinent Text from API 1155 . . .
32、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figures1 Generalized Example of the Software-based Leak Detection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Examples of Sensitivity Curves Based on DIfferent Operating Thresholds. . . . . . .
33、 . . . . . . . . . . . . . . . . . 383 Examples of Sensitivity Curves Typical of Event Oriented Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 Tabular Format for the Ranking of the Level of Importance for Each Performance Metric, andan Optional Table for Qualitative or Quanti
34、tative Specification of Performance Criteria Relatedto Each Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42vIntroductionComputational Pipeline Monitoring (CPM) is a term that was dev
35、eloped by the API to refer to software-based,algorithmic monitoring tools that are used to enhance the abilities of a Pipeline Controller to recognize hydraulicanomalies on a pipeline. These anomalies may be indicative of a pipeline leak or commodity release. CPM systemsare often generically called
36、leak detection systems. However, pipeline leak detection can be accomplished by avariety of techniques such as: aerial/ground line patrol; third party reports; inspections by company staff; hydrocarbondetection sensors; SCADA monitoring of pipeline conditions by Pipeline Controllers; and software-ba
37、sed monitoring.To provide a clear reference, the term CPM was developed to specifically cover leak detection using software-basedalgorithmic tools. Simple monitoring tools such as observations of meter over-short reports, observations of pressuredeviations and observation of flow rate deviations, wi
38、thout use of an inference engine and alert algorithm, althoughproviding valuable information to the Controller, are not considered to be CPM systems because they do not meet thedefinition of CPM.This is the first edition of API RP 1130 issued as a recommended practice. The first edition of API 1130
39、was publishedin 1995. The second edition was published in 2002. Between the first and second editions and now between thesecond and this RP, the users of this information (e.g. Pipeline Operators, system developers, system integrators andthe regulators) have had an opportunity to use and evaluate th
40、e document. Their suggestions for improvements,correcting of inconsistencies and error elimination have been considered and incorporated in this latest edition.All editions of this document have been written by Work Groups of the API Cybernetics Subcommittee. The purposeof the work was to develop an
41、 API recommended practice for CPM as it is used in the liquids pipeline industry. Thisupdate includes input from all committee members as well as a broad community of CPM system developers andsystem integrators.The five-year cycle of re-writing and re-authorizing API RP 1130 is necessary under API s
42、tandard rules and isespecially important because the document is referenced in the federal pipeline safety regulations which arediscussed in the following section.1Computational Pipeline Monitoring for Liquids1Scope1.1 PurposeThis recommended practice focuses on the design, implementation, testing a
43、nd operation of CPM systems that usean algorithmic approach to detect hydraulic anomalies in pipeline operating parameters. The primary purpose ofthese systems is to provide tools that assist Pipeline Controllers in detecting commodity releases that are within thesensitivity of the algorithm. It is
44、intended that the CPM system would provide an alarm and display other related datato the Pipeline Controllers to aid in decision-making. The Pipeline Controllers would undertake an immediateinvestigation, confirm the reason for the alarm and initiate an operational response to the hydraulic anomaly
45、when itrepresents an irregular operating condition or abnormal operating condition or a commodity release.The purpose of this recommended practice is to assist the Pipeline Operator in identifying issues relevant to theselection, implementation, testing, and operation of a CPM system. It is intended
46、 that this document be used inconjunction with other API standards and applicable regulations. 1.2 ContentsThis recommended practice includes definitions, source and reference documents, concepts of data acquisition,discussion of design and operation of a pipeline as related to CPM, field instrument
47、ation for CPM purposes, alarmcredibility, Pipeline Controller response, incident analysis, records retention, maintenance, system testing, training,considerations for setting alarm limits, trending and recommendations for data presentation. The relationship betweenthe Pipeline Controller and the CPM
48、 system is also discussed.1.3 Scope LimitationsThis recommended practice is not all-inclusive. The reader must have an intimate knowledge of the pipeline systemand may have to refer to other standards for background or additional information.This recommended practice was written considering single p
49、hase, liquid pipelines. However many of the principlesapply to liquid pipelines in intermittent slack line flow or liquid pipelines that may have permanent slack line flow. Slackline operation creates uncertainties in pressure and flow. For these operating conditions, the user of API RP 1130 willhave to carefully consider what parts of API RP 1130 do and do not apply.This recommended practice also may not apply to the special case of determining leaks during shut-in conditions thatoccur when the line is shutdown (sometimes called static conditions). For example, a Volume Balance CPM canno
