API RP 1167

Abstract

<strong>Scope Limitations</strong> <br>This document is not intended to be a step by step set of instructions on how to build an alarm management system. Each pipeline operator has a unique operating philosophy and will therefore have a unique alarm philosophy as well. This document is intended to outline key elements that should be considered when building an alarm management system. <br>SCADA systems and similar technologies used within the pipeline industry vary in their alarm related capabilities. There are also many different software systems available to aide in alarm management. It is the responsibility of the operator to determine the best method to achieve their alarm management goals. <br>This document uses industry best practices to help illustrate aspects of alarm management. The scope is intended to be broad. There are several publications and standards listed in Section 2 (Normative References) and the Bibliography that provide greater detail on the various elements of alarm management. Operators are encouraged to consult these publications. <br><strong>Purpose</strong> <br>This document is intended to provide pipeline operators with recommended industry practices in the development, implementation, and maintenance of an alarm management program. It provides guidance on elements that include, but are not limited to, alarm definition, alarm philosophy, documentation, management of change, and auditing.