Template-Wiki-Policy

Title:
Publication date:	(CSO to fill in)
Effective date:

Brief

Policy Summary

(text here)

Who Should Read This Policy

(text here)

To Read the Full Policy, Go To:

(link)

Contact Information

(Requirements Management Program Manager
Office of Contractor Assurance
[email protected])

(Policy page)

Title:
Publication date:	(CSO to fill in)
Effective date:	01/01/11

Policy

1. Purpose of this Policy

(text)

2. Persons Affected

(text)

3. Exceptions

(text here, or "not applicable")

4. Policy Statement

Eligibility for Employment - In general, to be eligible for employment at the Laboratory, individuals must meet and/or fulfill the following requirements:
1. Have reached age 15 at the time of hire for any position other than those located within any clinical or research laboratory.
2. If under age 18, a work permit from the superintendent of the employee's school is required, and the employee's hours of employment.
  1. Staff required to be licensed, certified or credentialed must present documentation of such status before employment and as required thereafter.
  2. Staff must authorize the Laboratory to conduct a background check. Employment is contingent upon the successful outcomes of this screening process.
    1. Limited-appointment employees who accept a career position in the same classif division reporting to the same supervisor.
    2. Individuals hired into Research Scientist/Engineer, Staff Scientist. See [RPM §2.07 (Professional Research Staff)|http://www.lbl.gov/Workplace/RPM/R2.07.html].
    3. dfgdfgd
Background Checks -- Any list text must be part of a bullet or it will break the wiki list.
1. Requirements - With the exceptions noted below, all new career employees and term employees hired with an initial appointment of a year or more must work a minimum probationary period of six months.

Individuals hired into Term appointments for one year or less and Career employees who transfer from another University of California employer without a break in service
successfully completed a full probationary period at a UC location.

5. Roles and Responsibilities

Role	Responsibility
Laboratory Division managers	Text text text text text text text text text text text text text text text text text text text text text text text text text text.
Persons who develop authoritative documents	Text text text text text text text text text text text text text text text text text text text text text text text text text text.
Persons who use authoritative documents	Text text text text text text text text text text text text text text text text text text text text text text text text text text.
Requirements Management Program Manager	Text text text text text text text text text text text text text text text text text text text text text text text text text text.

(If R&R can be described in a single sentence, paragraph form is acceptable. In the case of multiple roles, use table form)

6. Definitions/Acronyms

Term	Definition
Document	Written, visual, audio- or video-recorded information stored in the form of hard copy, film, magnetic tape, electronic data, or in an on-line, web-based format.
Implementing Document	A document required to carry out a policy, process, procedure, system, or work instruction. Examples:- Expense form- CATS (Corrective Action Tracking System) User Manual- EHS Chemical Storage Guidelines
Institutional Document	A publication authorized by Laboratory management that delineates laboratory-wide or multi-functional policy, procedures, regulations, or plansExamples:- Procurement policy- Radiation Protection Program
Policy	Statements or directives from the federal, state, or local government; the University of California; or LBNL senior management that set a course of action, define acceptable conduct, or implement governing principles.Example: LBNL Site Access

7. Recordkeeping Requirements

(text here – optional)

8. Implementing Documents (optional – for ease-of-use for user – List LINKS….)

(Link Title 1)
(Link Title 2)

9. Contact Information

Questions on this policy should be directed to:
Requirements Management Program Manager,
Office of Contractor Assurance
[email protected].

10. Revision History

Date	Revision	By whom	Revision Description	Section(s) affected	Change Type
2/28/11	0	L. Young	Initial	all	Major

(Tab 3: Doc Info page)

Title:	Document Management
Document number	10.06.001.000
Revision number	-00
Publication date:	(CSO to fill in)
Effective date:	12/01/11
Next review date:	12/01/14
Policy area:	Document Management
Functional area	Office of Contractor Assurance
Prior reference information (optional)	RPM Chapter 5.08

Document Information

Source Requirements Documents

DOE Order 414.1C, Quality Assurance, Attachment 2, CRD, Criteria 1, 4, 5
Contract 31, Section I.76 (DEAR 970.5203-1), Management Controls
LBNL/PUB 3111, Operations and Quality Management Program
LBNL Requirements Management Policy, 04.04.001.000

Implementing Documents (mandatory here – this is for RM database – must specify doc numbers)

Document number	Title
10.06.001.001	Managing Institutional Documents Process
10.06.001.101	Developing, Reviewing, Approving, Non-Policy Institutional Documents Procedure
10.06.001.102	Developing, Reviewing, Approving, Institutional Policy Documents Procedure
10.06.001.103	Archiving and Storing Institutional Documents Procedure
10.06.001.202	Policy Template & Information Form
10.06.001.201	Procedure, Program, System, Process Template
10.06.001.901	Style Guide for Institutional Documents

(Tab 4: Add'l. Information – special permission to view page)

Title:	Document Management
Document number	10.06.001.000
Revision number	-00
Publication date:	(CSO to fill in)
Effective date:	12/01/11
Next review date:	12/01/14
Policy area:	Document Management
Functional area	Office of Contractor Assurance
Author name/contact info

Revision 0 publication date	12/01/11
Retirement date	n/a
Prior reference information (optional)	RPM Chapter 5.08

Inputs from more than one Functional Area?	Yes
List additional Functional Areas & contacts	IT, Adam Stone

Inputs from more than one Policy Area?	Yes
List additional Policy Areas & contacts	Requirements Management – L. Young Archiving Documents – J. Stoner

30-day notification needed?	No
30-day start date	n/a
30-day end date	n/a

LDAP protected?	No

Need TABL reminders?	No
Frequency	n/a
Brief reminder text:	n/a

Approval Sheet for this revision received (date) [Note: author is responsible}

Additional Information

Keyword search words, phrases:

Text, text, text

New terms that need to be added to Glossary/Acronym list:

(list items not found and context (Policy Area name) – full definition would be included in Policy)

Implementing Documents restricted to department/functional use (optional – these would primarily be used for tracing between requirements and associated documents)

Document number	Title

Space shortcuts

Page tree

RPM | REQUIREMENTS AND POLICIES MANUAL