1、Recommended Practice for Onshore Hazardous Liquid Pipeline Emergency Preparedness and ResponseAPI RECOMMENDED PRACTICE 1174 FIRST EDITION, DECEMBER 2015Special NotesAPI publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, and federal
2、laws and regulations should be reviewed.Neither API nor any of APIs employees, subcontractors, consultants, committees, or other assignees make any warranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of the information contained herein, or
3、 assume any liability or responsibility for any use, or the results of such use, of any information or process disclosed in this publication. Neither API nor any of APIs employees, subcontractors, consultants, or other assignees represent that use of this publication would not infringe upon privatel
4、y owned rights.API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in them; however, the Institute makes no representation, warranty, or guarantee in connection with this publication and he
5、reby expressly disclaims any liability or responsibility for loss or damage resulting from its use or for the violation of any authorities having jurisdiction with which this publication may conflict.API publications are published to facilitate the broad availability of proven, sound engineering and
6、 operating practices. These publications are not intended to obviate the need for applying sound engineering judgment regarding when and where these publications should be utilized. The formulation and publication of API publications is not intended in any way to inhibit anyone from using any other
7、practices.Any manufacturer marking equipment or materials in conformance with the marking requirements of an API standard is 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
8、the applicable API standard.Classified areas may vary depending on the location, conditions, equipment, and substances involved in any given situation. Users of this Recommended Practice should consult with the appropriate authorities having jurisdiction.Users of this Recommended Practice should not
9、 rely exclusively on the information contained in this document. Sound business, scientific, engineering, and safety judgment should be used in employing the information contained herein.All rights reserved. No part of this work may be reproduced, translated, stored in a retrieval system, or transmi
10、tted by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from the publisher. Contact the Publisher, API Publishing Services, 1220 L Street, NW, Washington, DC 20005.Copyright 2015 American Petroleum InstituteForewordNothing contained in any A
11、PI publication is to be construed as granting any right, by implication or otherwise, for the manufacture, sale, or use of any method, apparatus, or product covered by letters patent. Neither should anything contained in the publication be construed as insuring anyone against liability for infringem
12、ent of letters patent.Shall: As used in a standard, “shall” denotes a minimum requirement in order to conform to the specification.Should: As used in a standard, “should” denotes a recommendation or that which is advised but not required in order to conform to the specification.This document was pro
13、duced under API standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API standard. Questions concerning the interpretation of the content of this publication or comments and questions concerning the procedures under wh
14、ich this publication was developed should be directed in writing to the Director of Standards, American Petroleum Institute, 1220 L Street, NW, Washington, DC 20005. Requests for permission to reproduce or translate all or any part of the material published herein should also be addressed to the dir
15、ector.Generally, API standards are reviewed and revised, reaffirmed, or withdrawn at least every five years. A one-time extension of up to two years may be added to this review cycle. Status of the publication can be ascertained from the API Standards Department, telephone (202) 682-8000. A catalog
16、of API publications and materials is published annually by API, 1220 L Street, NW, Washington, DC 20005.Suggested revisions are invited and should be submitted to the Standards Department, API, 1220 L Street, NW, Washington, DC 20005, standardsapi.org.iiiContentsPage1 Scope . . . . . . . . . . . . .
17、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Normative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
18、3 Terms, Definitions, Acronyms, and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 Terms and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19、. . 23.2 Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Emergency Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20、 . . . . 54.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.2 Management Commitment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21、 . . . . . . . . . . . . . . . . . . . . 54.3 Management System Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.4 Management of Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22、 . . . . . . . . . . . . . . . . . . . . . . 75 Preparedness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85.3 Training and Exercises . . . . . .
24、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1 Ge
25、neral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.2 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26、. . . . . . . . . . . . . . . . . . . 236.3 Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.4 Resource Mobilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.5 Incident Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.6 Response Priorities. . . . . . . . . . . . . . . . . . . .
28、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.7 Business Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.8 Response Transition . . . . .
29、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.9 Debriefing and Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Managem
30、ent System Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31、. . . . . . . . 317.2 Monitoring, Measuring, and Improving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317.3 Corrective Action and Continual Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32、. . . . . 327.4 Management Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Annex A PlanDoCheckAct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33、 . . . . . . . . . . . . 33Annex B Incident Command System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34、. . . . . . . . . . . . . . . . . . . . . . . . . . 38FiguresA.1 PDCA Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33B.1 The Operational Period Planning Cycle . . . . . . . . . . . . . .
35、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36B.2 NIMS ICS Organization Structure Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Tables1 Initial Emergency Response Phases . . . . . . . . . . . . . . . .
36、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13vviii0 IntroductionThis Recommended Practice (RP) has been developed for onshore hazardous liquid pipeline operators (hereinafter “the operator”), with the intent to align industry, government, and emergency response org
37、anizations expectations, practices, and competencies and to promote safe, timely, and effective response to incidents. It defines the fundamental emergency response requirements for those claiming conformity to the requirements of this document.While this document may include some elements of other
38、management systems (such as safety, environmental, financial, or risk management), it does not include all requirements specific to those systems. This document may be used either in conjunction with or independent of other industry-specified documents.For an operator to function effectively, it mus
39、t determine and manage numerous linked activities. An activity that transforms inputs into outputs is one way to define a process. This document promotes a process approach for the application of specific clauses when developing, implementing, and improving the effectiveness of pipeline emergency re
40、sponse programs. This approach provides for uninterrupted control over the stated requirements, as well as facilitating the overlap of processes, including the following:a) demonstrating management commitment,b) structuring risk management decisions,c) increasing confidence in risk controls,d) provi
41、ding a platform for sharing knowledge and lessons learned, ande) promoting a safety-oriented culture.Process activities include determination of needs throughout pipeline operations, provision of resources, identification of the proper sequence or order of a series of activities, monitoring and meas
42、uring the effectiveness of the activities performed, and applying changes or corrections to those activities as needed.Goal of the DocumentThe goal of this document is to provide operators with an enhanced framework to enable continual improvement of pipeline emergency response. The framework builds
43、 on an operators existing pipeline-related activities and draws upon industry experiences, lessons learned, and existing standards. The framework is comprehensive in its intent to define the managerial elements for safe, timely, and effective emergency response.NOTE “Pipeline” is defined in Terms an
44、d Definitions (see 3.1.16) to address, more broadly, pipeline systems. Figure 1 illustrates this RPs four strategic areas of focus (communication, training, exercise, and learning) and the associated goals of each. API 1174 EmphasisThis RP emphasizes: increased proactivity through training and plann
45、ed exercises, improved communications and clarified response management responsibilities throughout the operators organization (including contractor support), and provision of safe, timely, and effective emergency response by regularly evaluating operations to identify and address risksThese factors
46、 make response management activities more effective, comprehensive, and integrated.Standard Management System PrinciplesThis RP is based on the following standard management system principles. Commitment, leadership, and oversight from top management are essential to the overall success of an emerge
47、ncy response process. Management commitment ensures that the elements set forth in this RP are established with clear accountability for implementation and with a clear connection from objectives to day-to-day activities. A safety-oriented culture is essential to enable the effective implementation
48、and continual improvement of emergency response processes and procedures. Management of risk is an integral part of the design, construction, maintenance, and operation of a pipeline. Pipelines are designed, constructed, operated, and maintained in a manner that complies with federal, state, and loc
49、al regulations and conforms to applicable industry codes and consensus standards with the goal of reducing risk, preventing incidents, and minimizing the occurrence of abnormal operations. Application of a comprehensive and systematic approach to pipeline emergency response creates an organization that can mitigate incidents and promotes a learning environment for continual improvement. Protection of life and property and minimization of adverse environmental consequences are essential.Figure 0.1Strategies and GoalsEmergency response organizations and operators have ac
