API RP 70-2010 pdf download

API RP 70-2010 pdf download

API RP 70-2010 pdf download.Security for Offshore Oil and Natural Gas Operations.
1 Scope, Purpose and Objective This publication is intended to assist the offshore oil and natural gas drilling and producing operators and contractors in assessing security needs during the performance of oil and natural gas operations. The offshore oil and natural gas indus- try uses a wide variety of contractors in drilling, production, and construction activities. Contractors typically are in one of the following categories: drilling, workover, well servicing, construction, electrical, mechanical, transportation, painting, operating, and catering/janitorial. 2 Definitions 2.1 company security officer (CSO): The CSO is responsible for the maintenance of the Security Plan. The CSO shall have access to relevant security information. The CSO shall determine which information, and by what means, it is communicated. The CSO may delegate duties as neces- sary to assure timely completion of responsibilities. The CSO may be assigned other duties and responsibilities unrelated to security. 2.2 contractor: The individual, partnership, Þrm, or cor- poration that is hired to do a speciÞc job or service, such as a production operator, drilling or well servicing contractor or to provide contract employees to an owner/operator; a contrac- tor is also the individual, partnership, Þrm, or corporation retained by the owner or operator to perform other work or provide supplies or equipment. The term contractor shall also include subcontractors. 2.3 facility: Any artiÞcial island, installation, or other device permanently or temporarily attached to the subsoil or seabed of offshore locations, erected for the purpose of exploring for, developing, or producing oil, natural gas or mineral resources. This deÞnition includes mobile offshore drilling units (MODUs), but does not include pipelines or deepwater ports.
2.6 point of embarkation: The heliport or dock facility from which personnel and materials are shipped to or received from the offshore facility. 2.7 security vulnerability assessment (SVA): A sec- ondary evaluation that examines a facilityÕs characteristics and operations to identify potential threats or vulnerabilities and existing and prospective security measures and proce- dures designed to protect a facility. 2.8 threshold characteristics: Criteria established and published by the U.S. Coast Guard for screening offshore facilities. 3 Relevant Operational Standards and Industry Practices API and the oil and gas industry maintain a number of design and operational recommended practices that address aspects of safety and security in offshore oil and natural gas operations. While none of these were developed speciÞcally for security reasons, aspects of them are directly applicable. In many cases, prudent safety procedures would also serve to address appropriate security precautions. These recom- mended practices provide a starting point for developing guidance on security, if needed, at offshore oil and natural gas operating facilities. The following list of recommended practices address oper- ational measures: ¥ Recommended Practice 2A Planning, Designing, Con- structing Fixed Offshore Platforms . Contains engineer- ing design principles and practices for Þxed offshore platforms including assessment of existing platforms, and Þre, blast, and accidental overloading. ¥ Recommended Practice 2FPS Planning, Designing, Constructing Floating Production Systems (FPSOs). This recommended practice provides guidelines for design, fabrication, installation, inspection and opera- tion of ßoating production systems.
7 Security Plans 7.1 SECURITY PLAN CONSIDERATIONS Security planning starts with sound policy and procedures in place. The facility owner/operator should develop either an owner/operator-wide, multiple-facility or facility-speciÞc ¥ Additional measures as determined by the SVA, if con- ducted; and ¥ Coordination with Point of Embarkation. 7.3 SECURITY LEVELS security plan. Refer to Appendix D for an Example Model Security Plan. The security plan should include the following elements: 1. The measures being taken to detect or deter an attack or incursion; 2. The responses that may be considered at various secu- rity alert conditions, including the response to an actual attack, intrusion, or event; 3. Means of mitigating the consequences of an incident, if Homeland Security Advisory System (HSAS) Low: Green Guarded: Blue Elevated: Yellow High: Orange Severe: Red Note: *See Appendix B. Maritime Security (MARSEC) Level* Level 1 Level 1 Level 1 Level 2 Level 3 any, and; 4. If applicable, any additional security measures identi- Þed in the SVA described in Section 6. The plan should be kept conÞdential for security reasons. The plan should be reevaluated and updated periodically. A brief overview of the individual framework elements is provided in this section, as well as a roadmap to the more spe- ciÞc and detailed description of the individual elements that comprise the remainder of this recommended practice. 7.2 SECURITY PLAN ELEMENTS In developing a security plan, the facility owner/operator should consider several basic elements. This document recognizes the importance of ßexibility in designing security plans and provides guidance commensu- rate with this need. It is important to recognize that a security plan could be a highly integrated and iterative process. 7.2.1 Develop Baseline Security Plan A plan is developed to address awareness, communication and response actions, as applicable to the most signiÞcant risks to the facility.

The previous

API RP 1162-2010 pdf download

The next

API STD 674-2010 pdf download

Related Standards