TITLE:

ES&H Manual

 

DOCUMENT ID:

3510 Appendix T4

Review of Emergency Procedures

 

 

1.0          Purpose

 

At Jefferson Lab all site wide emergency plans and procedures, including any local procedures that may potentially require integration and/or resources beyond the local area, are annually reviewed by the Emergency Manager.  This appendix provides the process steps for reviewing emergency procedures.

 

2.0          Scope

 

Jefferson Lab’s Emergency Management Plan, Section 13.2, Program Maintenance, requires ongoing effort by the Emergency Manager and others to draft emergency procedures for the Lab’s evolving needs.  These procedures must be readily accessible for Lab sectors with active emergency management roles.

 

3.0          Responsibilities

NOTE:     Management authority may be delegated at the discretion of the responsible manager.

 

3.1            Anyone at Jefferson Lab

·       Develop emergency procedures in accordance with the process steps outlined in this appendix.

·       Submit emergency procedures to supervisor or other appropriate party for initial review.

 

3.2            Supervisor/Subcontracting Officer’s Technical Representative (SOTR)/Sponsor

·       Review emergency procedures and ensure they are accurate, updated, and relevant. 

·       Submit emergency procedures to Emergency Manager for evaluation.

·       File emergency procedures in an appropriate filing system that includes an annual review and approval process.

·       Notify affected groups of any new or revised emergency procedures.

·       Ensure emergency procedures are readily accessible.

 

3.3            Emergency Manager

·       Review and evaluate emergency procedures annually.

·       Provide feedback and guidance, as necessary, during development or revision of emergency procedures.

·       Ensure emergency procedures are annually reviewed and updated.

·       Maintain copies of emergency procedures within Emergency Management.

 

4.0          Process Steps

In addition to the steps outlined below, Figure 1 illustrates the process flow for review of emergency procedures.

 

4.1            Development 

Anyone at Jefferson Lab may write or revise emergency procedures.

 

                                           Step 1          Write procedure(s), considering the following (not all inclusive):

o   Triggers

o   Controls

o   Actions

o   Recovery

o   Level of emergency

o   Notification

o   Reporting

o   Responsibilities

 

                                           Step 2          Include the following:

o   Title of document

o   Revision #

o   Name of document owner (coordinate with supervisor to determine owner)

o   Document location

o   Release date

o   Review required date

o   Page numbers (page # of #)

 

                                           Step 3          Submit procedure(s) to supervisor or other appropriate party for review.

 

4.2            Initial Review

Supervisor or other appropriate party performs initial review process.

 

                                           Step 1          Review procedure(s) for accuracy and relevance.

                                           Step 2          Submit procedure(s) to Emergency Manager for evaluation.

OR                     

Alternate Step 2         Edit or return procedure(s) for correction.

 

IF Emergency Procedures are:

THEN

Accurate, relevant, and meet minimum requirements

Submit to Emergency Manager.

Not accurate, irrelevant, or do not meet minimum requirements

Edit or return for correction.

 

4.3            Evaluation

Emergency Manager performs evaluation process.

 

                                           Step 1          Evaluate procedure(s) to ensure coordination with the overall emergency management program.

                                           Step 2          Return procedure(s) to supervisor or other appropriate party.

 

IF Emergency Procedures are:

THEN

Acceptable

Sign, date, copy, and file copy of emergency procedure(s); and

Return original to supervisor or other appropriate party for release.

Not acceptable

Return with feedback and coordinate with supervisor or other appropriate party.

 

4.4            Revision

Anyone at Jefferson Lab may revise emergency procedures.

 

                                           Step 1          Write the revised procedure(s), considering any changes, such as new hazards or any additional requirements, such as training.

                                           Step 2          Discuss revisions with supervisor, emergency manager and other appropriate parties.

                                           Step 3          Submit revised procedure(s) to supervisor or other appropriate party.

 

4.5            Release

Upon determination of acceptability, supervisor or other appropriate party performs release process.

 

                                           Step 1          Notify affected groups.

                                           Step 2          Implement procedures into emergency plan.

                                           Step 3          File emergency procedures in an appropriate filing system that includes:

o   Accessibility

o   Annual review

o   Approval process

 

Figure 1 - Review of Emergency Procedures

 

5.0          Revision Summary

 

Revision 0.1  11/11/13  Added “including any local procedures that may potentially require integration and/or resources beyond the local area” to 1.0 Purpose; changed all instances of “periodic review” to “annual review” throughout entire document for clarification per TMenefee; changed review date from 3/20/18 to 7/14/15 to coincide with main 3500 chapter review date with concurrence from MLogue and SSmith.

Revision 0     03/20/13  Written to reflect Jefferson Lab’s Emergency Management Plan, Section 13.2, Program Maintenance.

 

 

ISSUING AUTHORITY

TECHNICAL POINT-OF-CONTACT

APPROVAL DATE

REVIEW REQUIRED DATE

REV.

ESH&Q Division

Tina Menefee

03/20/2013

07/14/2015

0.1

This document is controlled as an on-line file.  It may be printed but the print copy is not a controlled document.  It is the user’s responsibility to ensure that the document is the same revision as the current on line file.  This copy was printed on 11/11/2013.