_RP_1162-2010_2020.pdf

Public Awareness Programsfor Pipeline OperatorsAPI RECOMMENDED PRACTICE 1162 SECOND EDITION,DECEMBER 2010REAFFIRMED,OCTOBER 20152-YEAR EXTENSION:JULY 2020 Public Awareness Programsfor Pipeline OperatorsPipeline SegmentAPI RECOMMENDED PRACTICE 1162 SECOND EDITION,DECEMBER 2010REAFFIRMED,OCTOBER 20152-YEAR EXTENSION:JULY 2020 Special NotesAPI publications necessarily 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 any warranty or representation,either express or implied,with respect to the accuracy,completeness,or usefulness of the information contained herein,or 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 privately owned rights.API publications may be used by anyone desiring to do so.Every effort has been made by the Institute to ensure 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 hereby 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 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 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 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.All rights reserved.No part of this work may be reproduced,translated,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 Street,NW,Washington,DC 20005.Copyright 2010 American Petroleum Institute ForewordThis is the second edition of API Recommended Practice(RP)1162.Through clarifications,enhancements,andstreamlining,it attempts to make the original guidance more useful to operators in developing,managing,andimproving public awareness programs.Representatives from natural and other gas and hazardous liquids transmission companies1,local distributioncompanies,gathering systems,trade associations,and federal and state pipeline regulators have contributed to thenew edition.Additionally,other stakeholders,such as emergency responders,have provided input.This secondedition of API 1162 reinforces the goals and objectives of the original document and is largely similar in organizationand principal components.However,some changes have been made based on the experiences and insights ofstakeholders,including operators from all pipeline segments,who for several years have been implementing publicawareness programs under federal regulations incorporating API 1162.The changes aim to make API 1162 easier tounderstand and use and to increase the effectiveness of operator public awareness programs.A key alteration to thedocument was aligning baseline messages(those operators must communicate)with core safety messages.Thedecision to focus on safety messages was based on the recognition,well supported by research and experience,thatreducing the number of messages will improve overall message retention.The RP continues to provide operatorswith other messages for use as circumstances and practicality dictate.To enhance program efficiency and facilitatecollaborative efforts,the RP also increases alignment among the pipeline sectors except in cases where variationwas felt to be necessary to achieve program effectiveness.Nothing 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.Neither should anythingcontained in the publication be construed as insuring anyone against liability for infringement of letters patent.Shall:As used in a standard,“shall”denotes a minimum requirement i