TITLE:	ES&H Manual
DOCUMENT ID:	3310 Operational Safety Procedure Program

Individuals are encouraged to work under this new procedure; however it does not become effective until January 1, 2010, after training has been provided. Until that time you may access the prior procedure documents at:

Standard Operating Procedures and Operational Safety Procedures

or

https://jlabdoc.jlab.org/docushare/dsweb/Get/Version-16250/3310SOPsOSPs.pdf

1.0 Purpose

All work at Jefferson Lab having an unmitigated Risk Code (RC) of 3 or 4, determined by a Task Hazard Analysis (THA), requires a formal work control document known as an Operational Safety Procedure (OSP).

OSPs are utilized by all organizations at Jefferson Lab in order to document how hazards are mitigated and communicated through work procedures.

2.0 Scope

The level of risk assigned to work determines the level of scrutiny and thus the type of documentation required. If work is assigned a RC of 3 or 4 by a THA it requires an OSP.

All required OSPs have the associated THA attached as defined in ES&H Manual 3210 Work Planning, Control, and Authorization Policy.

The single exception to the above requirement is when Standard Protecting Measures are used to mitigate the risk to below a RC of 3. When Standard Protecting Measures are utilized to reduce the risk, no OSP or documented THA is needed to perform the work.

Standard Protecting Measures include basic non-specialized (this does not include: electrical, chemical, welding, fire, etc.) personal protection equipment (hard hat, safety glasses with side shields as needed, safety shoes, hearing protection, face shield, gloves, knee pads, proper work clothes) and engineered safeguards that are already in place and have been reviewed. Any safety measures other than these Standard Protecting Measures used to reduce risk are not credited, and therefore the work requires an approved OSP and an associated THA before work proceeds.

OSPs are valid for up to three years and are reviewed prior to expiration.

For tasks with a RC 3 or 4 with anticipated durations of three months or less a Temporary Operational Safety Procedure (TOSP) is developed and followed. TOSPs are used to document safety procedures, address the control of unusual hazards, and establish work procedures. TOSPs are reviewed with the same scrutiny as OSPs

3.0 Responsibilities

3.1 Document Author:

· Is a Jefferson Lab employee.

· Develops OSPs to outline a procedure for a particular process or activity.

· Involves ESH&Q staff in the development of OSPs as necessary.

· Acquires appropriate review and approval signatures including those of the responsible Division Safety Officer, Department or Group Head, and Safety Warden prior to initiating the procedure.

· Forwards the official copy of the approved OSP to ESH&Q Document Control.

· Implements the approved OSP:

o Posts the OSP in-or-around the affected area,

o Ensures affected personnel are aware of the procedure,

o Ensures that those who need to follow the procedure are trained and a list is maintained of those individuals.

o Verifies the effectiveness of the procedures by job walk-throughs and procedure review, and

o Integrates self-assessment findings, continuous improvements, and lessons learned.

· Reviews and updates the OSP prior to expiration (Docushare generates an automated reminder to the author on record) and whenever there is a change that affects the work activity (e.g., work group reorganization or equipment upgrade).

3.2 Department Managers, Hall, or Group Leaders

· Review and approve OSPs involving areas or individuals under their responsibility to ensure work processes and all hazards have been addressed.

3.3 Division Safety Officers (DSO)

· Review all new OSPs involving areas or individuals under their responsibility and verify the indicated RCs assigned.

· Ensure all environmental protection aspects have been addressed. (For guidance involving current regulatory requirements, contact Jefferson Lab’s Environmental Engineer.)

· If appropriate, personally inspect the relevant area with the document author and the cognizant department manager prior to recommending approval.

· Recommend approval or justify need for revision/re-submittal.

3.4 ESH&Q Staff

· Support the development of OSPs, encouraging consistency between organizational units.

· Assist line management in developing environmental management OSPs and associated implementation plans.

3.5 ESH&Q Document Control:

· Provides the document serial number

· Records the serial number, author, appropriate expiration date, and content in the Jefferson Lab authorized electronic filing system.

· Registers the Document Author and DSO to the document.

· Maintains a record of all active and expired OSPs.

· Ensures electronic files are accessible and current.

3.6 Safety Warden

· Be aware of conditions under your responsibility.

· Ensure that precautions are adequate to protect workers and population

4.0 Expectations

4.1 Operational Safety Procedure (OSP) Document Descriptions

· OSPs and TOSPs follow the standard format specified in ES&H Manual Chapter 3310 Appendix T2 Operational Safety Procedure Form.

· They are signed by the appropriate authorities before work proceeds.

· Are read and signed by each worker before they take part in the work.

· OSP are valid for up to three years.

· TOSP are valid for up to three months.

4.2 When to use an OSP/TOSP

· If a THA indicates an unmitigated RC of 3 or 4.

· If work hazards are considered unique, complex, or not addressed by the ES&H Manual.

· To address significant environmental impacts.

4.3 When an OSP/TOSP is not required, but may be recommended:

· If the work is subject to periodic reviews, audits, or assessments.

· When an activity is envisioned to be standardized for a location or specific piece of equipment.

ISSUING AUTHORITY	CHAPTER AUTHOR	APPROVAL DATE	EFFECTIVE DATE	EXPIRATION DATE	REV.	Page 2 of 4
ESH&Q Division	Harry Fanning	10/05/09	01/01/10	10/05/12	0

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 10/21/2009.