API RP 1174 pdf download

API RP 1174 pdf download

API RP 1174 pdf download Recommended Practice for Onshore Hazardous Liquid Pipeline Emergency Preparedness and Response
d) identification of legal and other applicable emergency response requirements or standards that the operator uses
for compliance;
e) processes intended to ensure continuity and promote system improvement; andfymeasurable goals and objectives.
4.3.2 Procedures
The operator should ensure that all procedures referenced within this system are established,documented,implemented , evaluated, maintained, and periodically reviewed.
4.3.3Communication of Management System
The operator should communicate the emergency management system to appropriate personnel within variousdepartments of an operator’s organization.These departments may include:
-emergency response;
risk management;
health, safety, environmental, and security;
insurance, finance, and procurement;
-communications and public relations.4.3.4Control of Documents
The operator should maintain a documented procedure for the identification, distribution, and control of documentsthat are required for its emergency management system and by this RP.The procedure should specify responsibilitiesfor document approval and re-approval,and should identify the controls needed to ensure that the requiredemergency response documents, including revisions,translations, and updates:
a) are reviewed and approved for adequacy prior to issue and use;
b) identify changes and revision status; and
c) remain legible and available.
The operator should remove obsolete documents from all points of issue or use or otherwise identify documents toprevent unintended use if they are retained for any purpose.
4.3.5Control of Records
The operator shall verify the records requirements of all applicable laws and regulations (federal, state, local, or tribal)and develop a documented procedure to identify the controls and responsibilities needed for the identification,collection,storage,protection,retrieval,retention time,and disposition of records. The operator shall establish,control, and retain records as required by law, regulations, internal company policy, and this RP.
4.4Management of Change4.4.1General
The operator shal maintain a documented procedure for management of change(MOC).For each MOC, theoperator shall identify any required approvals prior to the introduction of such changes.
This procedure shall consider permanent or temporary changes. The process shall incorporate planning for theeffects of the change for each of these situations.
NOTE MOC is a formalized approach used to introduce and approve proposed modfications and to transiton organizations,teams, and individuals to a desired future state, environment, procedure, or process.
4.4.2Types of Change
The types of changes that an MOC procedure addresses shall include the following:- technology,
personnel (interna and contractor),organizational roles and responsibilities,-training.
4.4.3Elements of MOC Procedure
An MOC procedure should include the following:
-reason for change,
authority for approving changes,
analysis of implications,
documentation of change process,
communication of change to affected parts of the organization,time limitations,
-qualification and training of personnel affected by the change (including contractors).
NOTE Application of MOC may trigger use of risk assessment to evaluate the impact of change on overall risk.5 Preparedness
The operator shall have a documented emergency preparedness program as part of an emergency managementsystem. The operator shall account for the preparedness requirements of federal, state, local, and tribal agencies.The operator’s emergency preparedness program should incorporate the recommendations of this RP.

The previous

API RP 1168 pdf download

The next

API RP 1177 pdf download

Related Standards