About API RP 1162, Third Edition: Overview
API RP 1162, Third Edition, was developed under API’s American National Standards Institute (ANSI) accreditation process and introduces the iterative four-step Plan, Do, Check, Act (PDCA) approach into the pipeline Public Awareness Programs framework.
The First Edition of API RP 1162 was published in 2003 and was incorporated into federal regulation by reference in 2005. The Second Edition of API RP 1162 was published in 2010 and reaffirmed in 2015 but was not incorporated by reference into federal regulation. The Third Edition introduces several key changes, which are introduced in this section and detailed in other sections of the site, including the use of digital platforms and other technologies that did not exist in 2003 and whose adoption by pipeline operators was just beginning in 2010.
API RP 1162, Third Edition, provides guidance for operators of regulated transmission, distribution, gathering pipeline, and underground storage systems to develop and manage Public Awareness Programs tailored to meet the needs of communities. Through this site, we aim to help operators understand new or changing requirements in the Third Edition and provide additional information that was not appropriate to include in the RP itself.
We encourage operators to explore this guidance site and use it as a resource for their program, and we also encourage the submission of questions and requests for information. This site is by no means exhaustive, nor was it intended to be; if there are additional resources that may be helpful to operators, please consider submitting that information as well.
About API RP 1162, Third Edition: Can, May, Should, Shall
The Third Edition incorporates the terms “can,” “may,” “should,” and “shall” according to API definitions:
- Shall: As used in a standard, “shall” denotes a minimum requirement in order to conform to the standard.
- Should: As used in a standard, “should” denotes a recommendation or that which is advised but not required in order to conform to the standard.
- May: As used in a standard, “may” denotes a course of action permissible within the limits of a standard.
- Can: As used in a standard, “can” denotes a statement of possibility or capability.