API RP 1161-2012 pdf free download

API RP 1161-2012 pdf free download.Recommended Practice for Pipeline Operator Qualification (OQ).
1 Scope The purpose of this recommended practice is to provide guidance for developing and maintaining a compliant Operator Qualification (OQ) program. Operators may choose to use all, part or none of this document. Additionally, many components of this recommended practice also apply to Gas Transmission Lines regulated under 49 CFR 192. Therefore, Operators may choose to utilize the recommended practice as applicable for these lines. Operators should be aware that the OQ regulation is applicable only to United States Department of Transportation (DOT) jurisdictional pipelines. For purposes of this document, the word “pipeline” is used interchangeably with pipeline, pipeline facility and pipeline system and any and all jurisdictional pipeline components as defined in 49 CFR Part 195. This document is written to provide guidance for achieving compliance with the regulation at the time of publication and is comprised of three individual components: the Guidance Document, the API Covered Task List (Annex A), and the Covered Task Standards (Annex B). A separate publication, the API Covered Task Standards, will contain guidance on the individual Covered Tasks. This guidance will include knowledge and skill components, span of control and abnormal operating conditions. 2 Abbreviations For the purposes of this document, the following abbreviations apply. AOC abnormal operating conditions API American Petroleum Institute CFR Code of Federal Regulations DOT Department of Transportation FAQ frequently asked question HQ headquarters NDT nondestructive testing OPID Operator identification OPS Office of Pipeline Safety OQ Operator Qualification PHMSA Pipeline and Hazardous Materials Safety Administration
3.2 Participation in an Industry Group The Operator may consider participating in an industry OQ group. These groups develop and update OQ guidance materials, share best practices and interact with regulatory agencies. 3.3 Language The Operator’s OQ program should include a policy on language to ensure effective communication when non- English speaking individuals perform covered tasks. Options may include but are not limited to the following: — maintain a single-language policy, whereby all individuals performing covered tasks speak the same language (i.e. English); — utilize bilingual individuals to interpret for non-English speaking individuals performing covered tasks; — ensure availability of acceptable qualification methods in applicable language(s). 3.4 Program Improvement 3.4.1 General While not specifically required by the regulation, an Operator may consider developing processes for periodic review of the written program and auditing program implementation. Operators should determine the process for incorporating program improvements based on the findings. 3.4.2 Written Program Review The purpose of a periodic review of the written program is to insure that it meets current regulatory compliance and any additional needs of the Operator. The Operator has the flexibility to structure the review as formally or informally as deemed necessary and should document the results and identify appropriate modifications, if any. 3.4.3 Internal Audit The purpose of an internal audit is to assure the program is being implemented as written. The Operator has the flexibility to structure the audit as formally or informally as deemed necessary and should document the results of the audit and identify appropriate modifications, if any. 4 Element 1: Identify Covered Tasks 4.1 General The program shall identify and document covered tasks. A covered task is an activity, identified by the Operator that: — is performed on a pipeline facility, and
4.2 Guidance on Identifying Covered Tasks 4.2.1 General In developing the covered task list, the Operator shall consider tasks performed on the pipeline facility, regardless of who performs them (employees, contractors, subcontractors, or other entities such as other pipeline Operators or those with access to the Operator’s equipment). For example, if an Operator contracts out pipeline repair activities, those activities shall be considered in the identification of covered tasks. The Operator has flexibility to determine how to accomplish covered task identification. The Operator should document the method and justification for selecting covered tasks. Options for establishing a covered task list may include but are not limited to the following two methods. 4.2.2 Adoption of an Industry-Developed Covered Task List Industry and technical associations, qualification product providers, and others have developed covered task lists through subject matter expert consensus. The Covered Task List developed by API (in conjuction with the Operator Qualification workgroup under the Pipeline Committee) is attached to this document as Annex A. The Operator should take additional steps if adopting such a list and at a minimum, should compare the covered task list to its operations and maintenance activities in order to ensure completeness. The Operator has the flexibility to combine or separate covered tasks as suitable to its operations and, if gaps are identified should apply the four-part test to add or delete covered tasks as applicable.