Approved by Joe Dionne
Revised 02/13
Contents
1.1 Policy
1.2 Scope
1.3 Applicability
1.4 Exceptions
1.5 Introduction to the ES&H Manual
1.6 ISM Overview: General Process
1.7 Roles and Responsibilities
1.8 Definitions
1.9 Required Work ProcessesWork Process A. Developing or Revising ES&H Policies and Programs
Work Process B. The Use of “Shall,” “Must,” “Should,” and “May” in EHSS Documents
| NOTE: |
|
![]() |
Denotes a new section. |
![]() |
Denotes the beginning of changed text within a section. |
|
Denotes the end of changed text within a section. |
_____________________
The Lawrence Berkeley National Laboratory (Berkeley Lab) Environment Safety & Health (ES&H) Manual, previously known as PUB-3000, describes the detailed and technical work processes used to control hazards in Berkeley Lab workplaces and environments in accordance with Laboratory policy. The standards in this manual are designed to:
The ES&H Core Policy supported by this Program is found in the Laboratory’s Requirements and Policy Manual (RPM) and is re-stated here:
These requirements are intended to address all hazards that may be encountered.
The requirements of the Berkeley Lab ES&H Manual apply to all Berkeley Lab employees, affiliates, contractors, and visitors to the Berkeley Lab main site, its off-site locations, and field operations.
None
The ES&H Manual is a collection of documents within the RPM that describes how LBNL integrates ES&H technical program requirements into the operating conditions found at LBNL. Separate ES&H programs have been developed for most ES&H technical areas. Following the principles of ISM and the LBNL ISMS Manual, technical programs use a graded approach to describe requirements at the activity, division, and institutional levels. While the technical requirements of each program area are unique (e.g., lead, ionizing radiation, or waste management), the administrative procedures used to manage these programs have commonalities that are leveraged to make it easier for workers to implement at the activity level and ensure compliance at the institutional level. At the division or facility level, ES&H technical program requirements are tailored to the physical conditions present and balance the need to work efficiently and safely while meeting institutional protection and compliance requirements. The ES&H Manual is designed and implemented to support and promote a strong safety culture at LBNL using the functions and principles of ISM. In this manual, EHSS is used to refer to the LBNL Environment, Health, Safety, and Security Division and its activities; ES&H is used to refer to the Environment, Safety & Health discipline and associated DOE regulations and requirements.
ISM Core Functions:
An ISM System Overview is found in the ES&H Core Policy of the RPM. |
ISM Guiding Principles:
|
The ES&H Manual also contains programs that cross technical areas such as Authorization Basis, Training, and Emergency Preparedness. The administrative procedures within these programs are designed to assist line management in meeting their ISM responsibilities during the normal course of doing business at the laboratory. This General ES&H Requirements chapter provides the overarching general requirements, responsibilities, and work practices for integrating ES&H into LBNL work at the activity, division, and institutional levels. The ES&H Manual is updated and revised on an on-going basis using the process described in Work Process A. The terms “shall,” “must,” “should,” and “may” in EHSS documents are used to differentiate between requirements and recommendations as described in Work Process B.
Berkeley Lab articulates its overarching environmental, safety and health policies and programs through its Integrated Environment, Safety & Health Management Plan (PUB-3140, ISM Plan). The policies and programs are established per the framework set by the principles and guidelines of ISM. Policy and technical program implementation, review, continuous improvement, and change are aligned with ISM guidelines and the Laboratory’s Requirements Management and Document Management policies. The ES&H technical program areas are defined by DOE Contract 31, the ES&H Standards Set in Appendix I of Contract 31, and applicable federal, state, and local regulations.
Every person working in an LBNL workplace must be familiar with and implement the LBNL safety standards that are applicable to them. Clear, unambiguous lines of authority and responsibility for ensuring safety must be established at all organizational levels.
The principal roles and responsibilities of the various stakeholders in the ISMS are listed in the table below.
Role |
Responsibility |
Workers |
1. Must protect themselves, other workers, the public, and the environment
2. Must integrate ES&H into all work activities
3. Must actively communicate ES&H and Integrated Safety Management issues
|
Supervisors and Managers |
In addition to their individual responsibilities as workers, Supervisors and Managers: 1. Must protect their staff, other workers, the public, and the environment
2. Must integrate ES&H into all work activities
3. Must actively communicate ES&H and Integrated Safety Management issues
4. Must recognize language and cultural barriers
5. Additional supervisor and manager responsibilities when using work leads
|
Work Leads |
These are persons who are delegated with select safety responsibilities by their supervisors and managers. Work leads are expected to apply these responsibilities under their Supervisors or Managers authority to perform these specific assignments. Work leads may decline to accept safety responsibilities with the permission of their supervisor. |
Area Safety Leaders |
Area safety leaders are coordinators and are not part of Safety Line Management. An area safety leader is an individual assigned by the division controlling a technical area to oversee coordination of safety issues within the area. The area safety leader may also be a manager, supervisor, or work lead. They are usually designated when multiple organizations do work within the technical area.
|
Casual Visitors and Sponsors |
Sponsors must:
Casual visitors must:
|
Division Directors |
|
Associate Laboratory Director for Operations / Chief Operating Officer |
|
Laboratory Director |
|
EHSS Division Director |
|
Environment, Health, Safety, and Security (EHSS) Division |
|
Office of Contractor Assurance |
|
Building Managers |
|
Division Safety Coordinator (DSC) |
|
EHSS ALD Liaisons |
EHSS Division Liaisons are designated for each Associate Laboratory Directorate (ALD). They provide a convenient, single EHSS point of contact between a customer division and the EHSS Division and function as the troubleshooter and problem-resolution facilitator. This relationship does not preclude any LBNL employee from directly approaching an EHSS professional or subject matter expert to address a particular issue or need. The EHSS Division Liaison:
|
Safety Advisory Committee (SAC) |
The SAC is an interface between the research and operations divisions of Berkeley Lab, as well as between the ES&H technical programs (mainly in the EHSS Division) and assurance and assessment activities of the Office of Contractor Assurance (OCA), see RPM, Policy Area – Quality Assurance. To effectively execute this role, the SAC has direct access to the Laboratory Director and the Senior Management Team. Its responsibilities include:
|
Requirements Management Committee (RMC) |
The RMC is an institutional committee chartered by the ALDO/COO. It reviews and oversees disposition of Requirements Review Cases related to requirements, Laboratory policies, and, on a case-by-case basis, Laboratory implementing documents. It is responsible for overseeing the Requirements Management process to ensure that:
The RMC applies cross-functional knowledge on requirements matters and:
|
OCA Requirements Management Program Manager (RM PM) |
|
EHSS Division Requirements Management Program Coordinator |
|
NOTE: Some functions and definitions overlap, depending on the specific situation.
Term |
Definition |
Affiliate |
Non-Laboratory employees engaged in on-site Laboratory activities. Affiliates are subject to training in safety and other subjects. They are also issued a Berkeley Lab identification badge. Affiliates may receive system accounts, research access to facilities, and a per diem allowance for housing and living expenses. Examples: facility users, scientific collaborators, students. |
area |
An entity that is separately listed in the LBNL Space Database maintained by Facilities Division and assigned to a division for programmatic use. Areas may be further described by their functional use (e.g., laboratories, shops, offices, conference rooms). |
Area Safety Leader |
The individual assigned by the division controlling the technical area to oversee coordination of safety issues within the area |
EHSS |
Environment, Health, Safety, Security Division |
employee |
An individual who is hired by LBNL to provide services on a regular basis in exchange for compensation |
ES&H |
Environment, Safety & Health; the discipline, interchangeable with “safety” |
ES&H Coordinating Committee |
The ES&H Coordinating Committee is formed when a significance level A or B program or project is ready for the LBNL Director review. The purpose of the ES&H Coordinating Committee is to advise the LBNL of the readiness and effects of implementing the program. The EHSS Division Director identifies and contacts the most affected division directors and other senior LBNL management personnel to serve on the Committee. The SME provides a briefing to the members of the Committee to ensure that they are ready to advise the LBNL Director on the new policy or program. |
faculty scientist |
Faculty scientists hold dual appointments at LBNL and an academic institution (usually UC Berkeley). When they perform work at or for LBNL, they are Staff members. Work includes being a HEERA supervisor, matrix supervisor, or work lead for one or more workers. See Supervisory Employees in the RPM Glossary. |
HEERA |
Higher Education Employer-Employee Relations |
host |
A host provides oversight to users at user facilities. A host has ultimate responsibility for safety at an assigned scientific station and ensures that all users receive proper training and oversight. A host may be a matrix supervisor, HEERA supervisor, or a work lead. |
ISM |
Integrated Safety Management |
JHA |
Job Hazards Analysis |
key personnel |
This is a Contract 31 term that includes the Senior Management Group and LBNL Counsel, Director of EHSS Division, Director of the Facilities Division, and the Director of the Office of Institutional Assurance. |
Berkeley Lab, the Laboratory, LBNL |
Lawrence Berkeley National Laboratory |
Line Manager, Line Management |
Managers are individuals responsible for formulating and administering policies and programs of LBNL; collectively, they are the Line Management. Typically, this includes some level of responsibility for staffing, performance review, work direction and evaluation, and/or finance. The formal “chain of command” management structure at LBNL starts at the top with LBNL Director and ends with Supervisors or Matrix Supervisors. Examples include, but are not limited to program heads, group leaders, department heads, division deputies, superintendents, administrators, supervisors. |
Matrix Supervisor |
A Matrix Supervisor is responsible for providing day-to-day technical direction and oversight, including responsibilities for proper execution of ES&H activities of employees and affiliates within their purview. A Matrix Supervisor is required to be HEERA-designated and can be in a division separate from the employee’s home division. The Matrix Supervisor can act as the host and point of contact on behalf of the division for affiliates and visitors of LBNL. A Matrix Supervisor partners with the HEERA Supervisor on matters of staffing, performance review, work direction, and evaluation. |
mentor |
A mentor is a work lead for a student. Mentors do not need to be line managers, HEERA-designated supervisors, or LBNL employees. |
OJT |
On-the-job training |
Principal Investigator (PI) |
Most U.S. Federal and State agencies that support scientific and technical research use the interchangeable titles “Principal Investigator” or “project director” for the scientist or researcher responsible for the technical leadership and administrative accountability of a project. A PI is ultimately responsible for the administration, direction, and management of the project and for its results. Often, funding for the project is also the PI’s responsibility. The designation is specific to a single contract and terminates with the closing of that project. The designation is thus of a different character than for such ongoing leadership positions as division director, department head, and group leader. A PI is always part of line management, and from a safety line management perspective, the PI is no different from any other staff. A PI’s role may include being a HEERA Supervisor or Matrix Supervisor. |
RPM |
LBNL Requirements and Policy Manual, PUB-201 |
safety |
Safety is used generically to cover all aspects of Environment, Safety & Health (ES&H) including regulatory requirements and is interchangeable with ES&H. |
Safety Line Management |
The unbroken linear safety management chain linking the LBNL Director to each worker. Above the lowest organizational unit in each division, the chain is defined by the succession of direct reports that establish job assignments, appraise performance, and determine salaries. Below this level, the chain can include workers at any level and may include non-management work leads who guide the day-to-day activities of one or more workers. |
Senior Management |
Senior Management includes the Senior Management Group plus the division directors, Chief Human Resources Officer, Chief Procurement Officer, Laboratory Counsel, Internal Audit Manager, Laboratory Security Manager, and Public Affairs Manager. This group is also known as “Upper Management.” |
Senior Management Group (SMG) |
The Senior Management Group includes the LBNL Director, deputy directors, associate laboratory directors, and the Chief Financial Officer. |
staff |
Anyone who works at LBNL and has been issued a current LBNL badge |
student/student intern |
Students or student interns often work at LBNL in different positions. Students can be employees or affiliates. Students are part of the Safety Line Management, no matter what their positions. Types of students employed at LBNL are:
|
subcontractor |
An individual worker or company hired by LBNL to perform a specific task as part of an overall project |
subject matter expert (SME) |
An SME has been designated by the group leader to provide technical direction to the LBNL population in a specific area. The SME is the focal point and responsible for all technical questions in that area. |
supervisor (HEERA) |
Supervisory employees are defined by the Higher Education Employer-Employee Relations Act (HEERA) as "any individual, regardless of the job description or title, having authority in the interest of the employer to hire, transfer, suspend, lay off, recall, promote, discharge, assign, reward or discipline other employees, or responsibility to direct them, or to adjust their grievances, or to effectively recommend such action, if, in connection with the foregoing, the exercise of such authority is not of a merely routine or clerical nature, but requires the use of independent judgment. Employees whose duties are substantially similar to those of their subordinates shall not be considered to be supervisory employees." |
Technical Area |
Technical areas generally include laboratories, shops, workrooms, and similar areas. Offices, conference rooms, food preparation, and consumption areas such as the cafeteria, kitchenettes, and break rooms are generally not technical areas. |
user |
A subset of employees or affiliates who come to LBNL as users at one or more of its various user facilities. They may be LBNL employees from other divisions than the user facility or under a completely different management structure (other UC, DOE, or private/public enterprises). Users bring their own scientific work and are responsible for its execution. While here, they are responsible for understanding and implementing LBNL safety requirements. They work under the auspices of an LBNL host. |
work |
Work is defined broadly to include all LBNL activities undertaken by staff independent of sponsor, program, or location of activities. |
work lead |
A work lead is anyone who directs, trains, or oversees the work and activities of one or more workers. Work leads provide instruction on working safely and the precautions necessary to use equipment and facilities safely and effectively. Work leads do not need to be line managers, HEERA-designated supervisors, or LBNL employees. |
worker |
Defined broadly to include anyone who performs work at or for LBNL |
RMC |
Requirements Management Committee: an institutional committee |
Requirements review case |
An instance or a question related to a requirement that has been logged into the Requirements Management database for disposition by the RM Committee |
The EHSS Division follows the LBNL Requirements Management Process, document number 04.04.001.003; Developing, Reviewing and Approving Non-Policy Institutional Documents Procedure, document number 10.06.001.101; and Developing, Reviewing and Approving Institutional Policy Documents Procedure, document number 10.06.001.102. This includes steps of identifying the Subject Matter Expert (SME) for a particular requirement, analyzing meanings and impacts of a new or changed requirement, and then setting forth applicable implementation mechanisms for the requirement to ensure flow-down to the workforce. Additionally, user input and management’s review and approval are key elements of the process. Implementing mechanisms include, but are not limited to, documents, training programs, communication, and definitions of roles and responsibilities. All institutional documents are subject to the Laboratory’s Managing Institutional Documents Process, document number 10.06.001.001 and Document Management Policy, document number 10.06.001.000. The Document Management Process imposes a “graded” rating for documents: major, minor, editorial. All major changes to institutional policies must be reviewed by the Laboratory Requirements Management Committee (RMC). Minor changes to institutional policies must be reviewed by the EHSS Requirements Management (RM) Representative. However, if cross-functional actions are needed, the EHSS RM Representative can recommend an RMC review. Additionally, the EHSS RM Representative must review major and minor changes to institutional non-policy documents and can recommend an RMC review if cross-functional activity is involved.
EHSS SMEs and their managers follow the steps below for developing or revising ES&H policies and programs:
Occasionally, there may be a need to quickly implement a requirement- or policy-related change. Such "stop work" or "stop practice" mandates must have at least EHSS Division Director authority. These high-urgency situations are still subject to completion of the applicable elements of the Requirements Management process. However, the Requirements Management elements may be worked on in parallel or in a different sequence. EHSS, through assigned SMEs, is expected to drive completion. Because the matter is urgent, emphasis on communication is likely needed. The following is an example of re-ordering the RM process for a highly urgent situation:
1. Approving manager may be EHSS Division Line Management, the Chief Operating Officer, or the Laboratory Director depending on the significance rating.
EHSS uses “shall,” “must,” “should,” and “may” statements in the following manner to convey requirements and best practices:
Document Number |
Title |
04.04.001.000 |
Requirements Management Policy |
04.04.001.003 |
LBNL Requirements Management Process Description |
04.04.001.101 |
Procedure: Analyzing Requirements and Determining Risks and Impacts |
04.04.001.102 |
Procedure: Developing, Reviewing, Approving an Implementation Plan |
04.04.001.103 |
Procedure: Parsing Requirements |
04.04.001.202 |
Form: LBNL Implementation Plan Template |
04.04.001.201 |
Form: Analyzing Requirements and Determining Risks and Impacts |
04.04.001.203 |
Form: Parsing Requirements |
10.06.001.102 |
Procedure: Developing , Reviewing, Approving Institutional Policy Documents |
_____________________
Table of Contents || Chapter 2>>