Lawrence Berkeley National Laboratory masthead LBNL Home A-Z Index U.S. Department of Energy logo Phone Book Jobs Search

RPM

REQUIREMENTS AND POLICIES MANUAL

Search the RPM
 
Home

Requirements Management Policy

Title:

Requirements Management Policy

Publication date:

1/2/2012

Effective date:

1/2/2012

BRIEF

Policy Summary

Berkeley Lab must establish and maintain a system for managing its U.S. Department of Energy Contract 31 requirements and their flow-down into Laboratory policies and procedures.

Who Should Read This Policy

  • The Laboratory Director and the Chief Operating Officer and their direct reports
  • Persons specifically assigned by their Senior Line Managers to monitor, interpret, and/or determine detailed implementation of the portions of Contract 31 applicable to the respective Senior Line Manager's responsibilities

To Read the Full Policy, Go To:

The POLICY tab on this wiki page.

Related Policy:

Document Management Policy

Contact Information

Requirements Management Program Manager
Office of Contractor Assurance
requirementsmgmt@lbl.gov

Title:

Requirements Management Policy

Publication date:

1/2/2012

Effective date:

1/2/2012

POLICY

A. Purpose

This policy calls for the establishment and maintenance of a system for managing Lawrence Berkeley National Laboratory's U.S. Department of Energy (DOE) Contract 31 requirements and their flow-down into Laboratory policies and procedures.

B. Persons Affected

The results of this policy directly affect all members of the Berkeley Lab community. However, a far smaller set of persons drive implementation of this policy, including the Laboratory Director and the Chief Operating Officer and their direct reports; and persons (Subject Matter Experts) specifically assigned by their Senior Line Managers to monitor, interpret, and/or determine detailed implementation of requirements applicable to the respective Senior Line Manager's responsibilities.

C. Exceptions

Not applicable

D. Policy Statement

Berkeley Lab must establish and maintain a system for managing the requirements set forth in U.S. DOE Contract No. DE-AC02-05CH11231 (Contract 31); the requirements specified by its contracting manager, the University of California; and any Laboratory-generated requirements and policies. The system for managing requirements must include at least controls for:

  1. Defining information that flows from requirements through to Laboratory policies and supporting documents
  2. Finding information
  3. Ensuring that information is accurate
  4. Ensuring that information is easy to read

The Requirements Management Committee (RMC) is comprised of representatives from at least each of the Laboratory Operations functions, the Technology Transfer Office, the Research and Institutional Integrity Office, and the Office of Institutional Assurance. The RMC has been chartered by the Laboratory's Chief Operating Officer to provide centralized coordination and communications on Contract 31 requirements and related Laboratory policy matters. (See documents 04.04.001.002, LBNL Requirements Management Governance; and 04.04.001.003, LBNL Requirements Management Process, for more information.)

E. Roles and Responsibilities

The Laboratory Director and the Chief Operating Officer and their direct reports are expected to provide financial and resource support for the establishment and maintenance of a Requirements Management (RM) System.

The RMC provides centralized coordination and communication on Contract 31 requirements and related Laboratory policy matters.
Persons (Subject Matter Experts) specifically assigned by their Senior Line Managers to monitor, interpret, and/or determine detailed implementation of the portions of Contract 31 applicable to the respective Senior Line Manager's responsibilities are expected to follow the RM System process and procedures.

F. Definitions/Acronyms

Term

Definition

Contract 31

"Contract 31" is short for Contract No. DE-AC02-05CH11231 between the U.S. Department of Energy and the University of California describing the terms for management of Berkeley Lab. The contract includes a statement of work (SOW) for the science missions and details the requirements for managing the operations and business of Berkeley Lab.

Document

Written, visual, audio-, or video-recorded information stored in the form of hard copy, film, magnetic tape, electronic data, or in an online, Web-based format

Implementing Document

A document required to carry out a policy, process, procedure, system, or work instruction
Examples: Expense form, Corrective Action Tracking System (CATS) Database User Manual, Environment, Health & Safety (EH&S) Division Chemical Storage Guidelines

Institutional Document

A publication authorized by Laboratory management that delineates Laboratory-wide or multifunctional policy, procedures, regulations, or plans. A subset of authoritative documents. Scientific and technical publications and reports are not included in this definition.
Examples: Procurement policy, Radiation Protection Program

Policy

Statements or directives from the federal, state, or local government; the University of California; or Berkeley Lab senior management that set a course of action, define acceptable conduct, or implement governing principles
Example: Berkeley Lab Site Access

Requirement

A specific obligation to perform an action mandated by Berkeley Lab senior management or the University of California or the federal, state, or local government; or an obligation to comply with the Laboratory's contract with the U.S. Department of Energy

Senior Line Manager

The highest level or most senior level of authority within a division or office Examples: The EH&S Division Director, the Chief of Human Resources Officer, Chief Financial Officer, or Public Affairs Department Head

G. Recordkeeping Requirements

Not applicable

H. Implementing Documents

Document Number

Title

04.04.001.002

LBNL Requirements Management Governance

04.04.001.003

LBNL Requirements Management Process

04.04.001.004

Requirements Management Database Requirements Specification

04.04.001.101

Analyzing Requirements, Risk and Impact Procedure

04.04.001.102

Developing, Reviewing, Approving an Implementation Plan

04.04.001.201

Analyzing Requirements, Risk and Impact Form

04.04.001.202

Implementation Plan Form

04.04.001.203

Parsing Requirements Form (tbd)

04.04.001.206

Determining Significance Rating

04.04.001.208

Record of Decision(ROD) form

10.06.001.000

Document Management Policy

I. Contact Information

Questions on this policy should be directed to:
Requirements Management Program Manager
Office of Contractor Assurance
requirementsmgmt@lbl.gov

J. Revision History

Date

Revision

By whom

Revision Description

Section(s) affected

Change Type

1/2/2012

0

L.Young

Release for publication in wiki

all

Major

DOCUMENT INFORMATION

Title:

Requirements Management Policy

Document number

04.04.001.000

Revision number

0

Publication date:

1/2/2012

Effective date:

1/2/2012

Next review date:

1/2/2015

Policy Area:

Requirements Management

RPM Section (home)

Contractor Performance Management

RPM Section (cross-reference)

none

Functional Division

OCA

Prior reference information (optional)

none

Source Requirements Documents

Implementing Documents

Document Number

Title

Type

04.04.001.002

LBNL Requirements Management Governance

System

04.04.001.003

LBNL Requirements Management Process

Process

04.04.001.004

Requirements Management Database Requirements Specification

Specification

04.04.001.101

Analyzing Requirements, Risk and Impact Procedure

Procedure

04.04.001.102

Developing, Reviewing, Approving an Implementation Plan

Procedure

04.04.001.201

Analyzing Requirements, Risk and Impact Form

Form

04.04.001.202

Implementation Plan Form

Form

04.04.001.203

Parsing Requirements Form (tbd)

Form

04.04.001.206

Determining Significance Rating

Form

04.04.001.208

Record of Decision(ROD) form

Form

10.06.001.000

Document Management Policy

Policy

  • No labels

Adaptavist ThemeBuilder EngineAtlassian Confluence