Protocol:
A B C D E F G H I J K L M N O P F.01 Periodic Evaluations
Verify the operator conducts a periodic evaluation of pipeline integrity based on data integration and risk assessment to identify the threats specific to each covered segment and the risk represented by these threats. [§192.917 and §192.937(b)]
[See Details...]F.02 Reassessment Methods
Verify that the approach for establishing the reassessment method is consistent with the requirements in §192.937(c). [§192.937(c) and §192.941]
[See Details...]F.03 Low Stress Reassessment
For pipelines operating at < 30% SMYS, the operator may choose to use a "low stress reassessment" method to address threats of external and internal corrosion. If this method is used, verify that the operator addresses the following requirements [§192.941]:
[See Details...]F.04 Reassessment Intervals
Verify that the requirements for establishing the reassessment intervals are consistent with section §192.939 and ASME B31.8S-2004. [§192.937(a), §192.939(a), §192.939(b), §192.913(c), and ASME B31.8S-2004, Section 5, Table 3]
[See Details...]F.05 Deviation from Reassessment Requirements
If the operator elects to deviate from certain requirements listed in §192.913(c), verify that the operator uses a performance based approach that satisfies the requirements for exceptional performance as follows: [§192.913 and ASME B31.8S-2004]
[See Details...]F.06 Waiver from Reassessment Interval
Verify that the operator's program requires that it apply for a waiver, should it become necessary, from the required reassessment interval. The waiver request must demonstrate that the waiver is justified as specified in the rule. Such a waiver request may only be made in the following limited situations: [§192.943]
[See Details...]Explanation of Protocol Format
Each protocol element will have top-tier protocols that address the high level requirements. The regulatory requirement upon which the protocol is based is contained in brackets; e.g., [§192.905(a)]
Each top-tier protocol will have detailed "sub-tier" protocols which collectively lead the inspector to draw overall conclusions about compliance with the top-tier protocol. The regulatory requirement, upon which each sub-tier protocol is based, is also contained in brackets.
Notes on protocols:
- The typical sentence structure used in the protocols follows the form of "Verify that [describe the requirement]." The use and meaning of the term "verify" is expanded upon below.
- PHMSA will "verify" an operator’s compliance status with respect to each requirement. In order to perform this verification, PHMSA will inspect the operator’s documented processes and procedures in order to determine if a program has been established that complies with rule requirements. In addition, PHMSA will inspect an operator’s implementation records to determine if the operator is effectively implementing its programs and processes. The purpose of the PHMSA verification/inspection is not to perform a quality check of every integrity related activity. The PHMSA inspection is conducted in the form of an audit. As a result, the PHMSA inspection will typically perform an inspection of selected operator records sufficient in breadth and depth to give the inspection team adequate understanding regarding the degree of an operator's commitment to compliance with applicable requirements and/or the degree to which the operator's program has been effective with respect to achieving compliance. PHMSA may use any number of inspection or audit techniques to identify potential compliance issues. Program documents may be inspected to determine if adequate processes have been developed and documented to the degree necessary for competent professionals to understand and effectively implement the process with results that are consistent and repeatable. For example, one technique that might be used by the inspection team is a "vertical slice" in which a specific covered segment or pipeline system is selected to perform a detailed inspection of every aspect of integrity management, thus following a specific example through the entire process of integrity management. Based on those reviews, OPS will identify potential non-compliances with rule requirements. PHMSA can not and will not certify nor conclude that an operator is in full compliance with rule requirements, even if the inspection does not identify any areas of non-compliance. Operators are wholly responsible for compliance with regulations.
- References to regulatory requirements may include references to specific rule sections/paragraphs and/or to industry standards that are invoked in the rule. As specified in §192.7, any requirement invoked by reference is a requirement of the rule as though it were set out in full in the regulation.
- Protocols are subject to change without notice.
- Protocols are an initial guide for use by OPS inspectors during Integrity Management inspections. Inspectors will develop additional questioning during the course of the inspection to investigate the specifics of an operator's program. Protocols are not to be construed as an exhaustive list of questions that may be presented to operators during an inspection.
- Protocols are made publicly available as a courtesy to operators as they develop their Integrity Management program, as well as other stakeholders.
Protocol:
A B C D E F G H I J K L M N O P