LCLS Project Change Control Procedure - Earned Value Management System Change Control Procedure - Revision 0.0

Sep 12, 2026

Uploaded by Stanford

Earned Value Management System change control procedure for the LCLS project schedule and cost baselines. Defines how to initiate, review, approve, track, and implement Baseline Change Requests (BCRs), aligned with LCLS Project Execution Plan, Project Management Plan, and EVM System Description. Specifies when BCRs are required (scope, responsibility, schedule, budget, funding) and when they are not required, and describes the Change Control Board review and approval thresholds for levels 2, 3, and 4.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages14

Reading Time5 min

AccessFree to download

1.0 PURPOSE

2.0 SCOPE

3.0 REFERENCES

4.0 DESCRIPTION

5.0 PROCEDURE DETAILS

5.1 Initiate Change Request

5.2 Review and Approve Change Request

5.3 Implement Change Request

| LCLS Project Management
Document \# 1.1-019 | | Project Management | | Revision 0.0 | | --- | --- | --- | --- | --- | | Earned Value Management System Change Control Procedure | | | | | | Patricia Mast
(LCLS Project Controls Manager)
Mark Reichanadter
(LCLS Deputy Project Director)
John Galayda
(LCLS Project Director) | Signature Signature
Signature | | Date Date
Date | | Change History Log | Rev
Number | Revision Date | Sections Affected | Description of Change | | --- | --- | --- | --- | | 0.0 | 03/21/2006 | All | Initial version released. | | | | | | | | | | | Table of Contents 1.0 PURPOSE .......................................................................................................... 1 2.0 SCOPE ............................................................................................................... 1 3.0 REFERENCES ................................................................................................... 1 4.0 DESCRIPTION ................................................................................................... 1 5.0 PROCEDURE DETAILS ..................................................................................... 3 5.1 Initiate Change Request .......................................................................... 3 5.2 Review and Approve Change Request.................................................... 6 5.3 Implement Change Request .................................................................... 9 LIST OF FIGURES Figure 1. Initiate Change Request ................................................................................. 3 Figure 2. Review and Approve Change Request ........................................................... 6 Figure 3. Implement Change Request ........................................................................... 9 Change Control Procedure 1.0 PURPOSE This document describes the process used to initiate, approve, track, and implement changes to the LCLS project schedule and cost baselines following all change control guidelines in the LCLS Project Execution Plan, Project Management Plan, and Earned Value Management System Description. 2.0 SCOPE This procedure applies for the entire life cycle of the LCLS project. This procedure must be followed for any baseline change that triggers the change control thresholds defined in the LCLS Project Execution Plan. 3.0 REFERENCES LCLS Project Execution Plan, Section 7, Project Management, Control, and Reporting LCLS Project Management Plan, Section 7, Configuration Management LCLS 1.1-015 Earned Value Management System Description, Section 5, Change Control LCLS 1.1-018 Control Account and Work Package Planning Procedure LCLS 1.1-020 Project Schedule Procedure LCLS 1.1-021 Cost Estimating Procedure LCLS 1.1-022 Monthly Status and Reporting Procedure Change Control Board Presentation Outline (template) Change Control Log (database) Baseline Change Request Form (template) 4.0 DESCRIPTION Change control rules and restrictions are described in Section 5 of the LCLS Earned Value Management System Description. In summary, a Baseline Change Request (BCR) is required whenever there is a change in the: • Scope of work. This can include changing the scope of existing tasks (a description change) or adding/deleting work scope (the work breakdown structure) . • Responsibility. This includes instances where tasks, scope, and budget are moved from one WBS element to another or from one organization to another and thus impacts control account assignments. • Schedule. This includes instances where replanning work tasks impacts key customer or management milestones or impacts other control accounts. Existing tasks with assigned chargeable accounts may need to be deleted; new tasks may need to be added. Changes to the schedule also impact the related budget costs. • Budget. This includes instances where contin

FAQs

When is a Baseline Change Request (BCR) required for the LCLS project?

A BCR is required when changes affect work scope, responsibility (including WBS or organization moves), schedule impacts (including replanning and milestone effects), budget usage/contingency, or funding that alters schedule and cost baselines.

When are Baseline Change Requests not required?

BCRs are not required for internal replanning or routine maintenance within a control account when there is no impact to scope, schedule, or budget, and not for updating current schedule and estimate-to-complete to reflect current conditions.

Which body reviews and manages Baseline Change Requests?

The Change Control Board (CCB) reviews, approves, and manages all Baseline Change Requests, and the approval cycle and responsibilities are defined in the LCLS Project Management Plan.

Sep 12, 2026

Uploaded by Stanford