Lawrence Berkeley National Laboratory masthead A-Z Index Berkeley Lab masthead U.S. Department of Energy logo Phone Book Careers Search

Requirements Management Program

The Lawrence Berkeley National Laboratory (LBNL) is managed and operated by the University of California (UC) under U.S. Department of Energy Contract No. DE-AC02-05CH11231 (Contract 31). The requirements of Contract 31 and UC must be translated into Laboratory poli cies, programs, and procedures that its workforce can use to effectively and efficiently meet the needs of its customers and stakeholders.

The Laboratory’s Requirements Management (RM) Program oversees the system and processes for managing contractually-based requirements.  The RM Program has three main elements:

  • A RM process to manage new or changed requirements,
  • A business (or database) system to manage and trace the relationships among Laboratory requirements, policies, programs, and other institutional documents and information,
  • A document management process for managing Laboratory policies, programs, and procedures.

Requirements Management Committee (RMC)
The Requirements Management Committee (RMC) provides centralized coordination and communications on Contract 31 requirements and related Laboratory policy matters. The RMC reports to the Associate Laboratory Director of Operations. Its current membership includes all the Operations functions, Technology Transfer, Office of Contractor Assurance, and Engineering. The RMC champions requirements management and institutional document management processes.  It applies cross-functional knowledge to the review and oversight of matters related to requirements, Laboratory policies, and on a case-by-case basis Laboratory implementing documents.  It applies a systematic approach for reviewing and analyzing impact of requirements, and then generating an implementation plan.  Analysis includes the weighing of costs, persons impacted, and risks to safety, environment, security as well as fiscal, legal, and compliance considerations.  The results of a detailed analysis can then drive practical implementation of a requirement.  The overall process includes the vital step of communicating changes and impacts to the affected Lab community members. 

The RM process, RM governance and the RMC charter and membership may be found in the links below.

RM Database
The business system to manage and trace the relationships between requirements, policies and supporting programs, procedures, processes is currently under development.  It will be LDAP accessible and its targeted launch is mid-2012.  A typical question that may be answered by this business system might be: what policies, programs, procedures are impacted by a change in DOE Order XYZ?

Document Management
Meaningful outcomes from both the RM process and the business (database) system are only possible if a disciplined document management process for Laboratory policies and procedures is established.  The document management policy and process (see links below) provide the framework for managing not only Laboratory policies and procedures, but also divisional and departmental documents.

PUB-201 Requirements and Policy Manual (RPM)
Most visible to the Laboratory community is the re-organized Requirements and Policy Manual (RPM).  It collects all Laboratory policies into one searchable wiki-space and presents information that is easier to understand and easier to find.  Major contributors to this effort include all of the Operations and Laboratory Directorate functions.  The wiki-RPM launched in April, 2012.

Send questions or feedback to:

Application of Procedures and Forms per General Process Flow for Requirements, Policies, and Non-Policies


A. Requirements Management Processes and Tools

1. Requirements Management Process,
2. Requirements Management Governance,
3. Requirements Management Committee (RMC) Charter

-RMC members and contacts

4. Analyzing Requirements and Analyzing Risks and Impacts to Determine Significance Rating

- Form,

5. Developing, Reviewing, Approving an Implementation Plan

- Procedure,
- Form,

6. Determining Significance Rating based on Analysis of Impacts and Risks, Form,

7. Submitting Contract Deliverables Procedure, (tbd)

8. Software Requirements for RM Database,

9. Graded Approach for Requirements and Documents (pilot),

10. Processing of Approved Contract 31 changes (pilot),

11. Record of Decision (ROD) template,

B. Document Management Processes and Tools

1. Document Management Process,
2. Developing, Reviewing, Approving Institutional Policy Documents

- Procedure,
- Template,
- Approval Form,

3. Developing, Reviewing, Approving Non-Policy Documents

- Procedure,
- Template, (tbd)
- Approval Form,

C. Other references:

1. Requirements Management Policy, RPM
2. Document Management Policy, RPM  
3. Quality Assurance Policy, RPM   
4. Operating and Quality Management Plan (OQMP), PUB-3111