![](media/image1.wmf){width="1.1in" height="1.0465277777777777in"}

**K-ELV-02.14**

National Aeronautics and Space Administration **Basic**

John F. Kennedy Space Center, Florida **3/02/01**

**Expendable Launch Vehicles Program**

EXPENDABLE LAUNCH VEHICLES (ELV) PROGRAM REQUIREMENTS CONTROL BOARD
CHARTER

> APPROVAL:
> **\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**Date**\_\_\_\_\_\_\_\_\_**

S. M. Francois

ELV & Payload Carriers Programs Office

**THIS PAGE INTENTIONALLY LEFT BLANK**

**TABLE OF CONTENTS:**

1.  **AUTHORITY
    ..................................................................................5**

2.  **PURPOSE
    ....................................................................................5**

3.  **SCOPE
    ........................................................................................5**

4.  **ORGANIZATIONAL RELATIONSHIPS &
    RESPONSIBILITIES..................5**

5.  **DEFINITIONS & PROCESSES
    ...........................................................6**

6.  **MEMBERSHIP
    ...............................................................................8**

7.  **APPLICABLE DOCUMENTS
    ......................................................\....10**

8.  **DOCUMENTATION
    .......................................................................11**

9.  **MEETING SCHEDULE
    ..................................................................11**

**ATTACHMENT A -- CCBD
..................................................................\...A-1**

**ATTACHMENT B -- CCR
.....................................................................\...B-1**

**ATTACHMENT C -- ESR
.....................................................................\...C-1**

**ATTACHMENT D -- TA
........................................................................\....D-1**

**ATTACHMENT E - DCR
\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....E-1**

**ATTACHMENT F - RIS
\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...F-1**

**THIS PAGE INTENTIONALLY LEFT BLANK**

# 1.0 AUTHORITY {#authority .unnumbered}

> The Expendable Launch Vehicles (ELV) and Payload Carriers Program
> Office hereby authorizes the ELV Program Requirements Control Board
> (PRCB) to function as the change authority for modifications to ELV
> Program Requirements and Resources. This plan and the processes
> defined herein become effective upon its approval.

# 2.0 PURPOSE  {#purpose .unnumbered}

The purpose of this plan is to establish the PRCB and describe its
functions and operation.

# 3.0 SCOPE {#scope .unnumbered}

> The scope of the PRCB is to:

1.  Initiate, assess, and implement changes to program requirements.

2.  Control the ELV Program's resources baseline (including launch
    service contracts, mission-unique hardware, and government-owned
    facilities.

3.  Provide change authority for funding contract modifications and
    contract turn-ons.

4.  Provide technical and funding concurrence for KSC-sustained
    facility/systems/equipment changes affecting, or to be funded by,
    the ELV Program.

5.  Support program/project elements external to KSC for the various
    configuration management activities.

6.  Dispose of Program assets.

7.  Disposition Program-level risks.

##  {#section .unnumbered}

## 4.0 RELATIONSHIPS AND RESPONSIBILITIES {#relationships-and-responsibilities .unnumbered}

The ELV Program Office administers the configuration management program
for the ELV Program. Certain functions may be delegated within the
organization at the Program Manager's direction. Regardless of such
delegation, the Program Requirements Control Board will be the final
authority for any items that (1) cause the program to deviate from the
program operating plan; (2) add new requirements to the program,
including baselining flights on the manifest; (3) create new program
policy or direction; or (4) implement new or unusual requirements such
as new launch sites or new vehicles. Additionally, the PRCB will be the
final authority for (1) documents that require the program manager's
signature; (2) waivers to any program requirements; (3) changes that
affect launch vehicle flight safety; (4) changes to program or launch
schedules; (5) launch vehicle return to flight issues; (6) major
hardware developments; (7) new contracts or changes to existing
contracts; and (8) Program-level risks.

> The Program Manager chairs the Program Requirements Control Board
> (PRCB) for the ELV Program. The Program Manager may delegate the
> Deputy Program Manager or an Associate Program Manager to chair the
> PRCB, as appropriate. In the absence of the Program Manager, the
> Chief, ELV Program Integration Office is delegated the authority to
> approve \"in-scope\" contract changes and funding authority. In the
> case of KSC-sustained Engineering Support Requests (ESRs) for
> facilities used by ELV, but controlled by KSC (i.e., Hangar AE), the
> appropriate Payloads/ISS Configuration Control Board (CCB) (Level III
> or IV) has the approval authority, with PRCB technical and funding
> concurrence.
>
> The Mission Integration Managers (MIM's) are delegated the authority
> to commit up to \$500,000 for special studies or analyses under the
> existing Launch Vehicle contracts.

The PRCB will serve as the Program Level Risk Management Control Board
as required.

# DEFINITIONS AND PROCESSES

5.1 Baseline

> The composition of a configuration-controlled item in its initial
> configuration-controlled condition is defined to be its baseline
> (Launch Services Provider baselines are established by contract and
> maintained by the contractor). Modifications to a baseline occur when
> a change is made to one of its configuration items.

5.2 Configuration Control

> Configuration control is the function of change control. It is the
> process of inhibiting unauthorized change to a baselined configuration
> item and controlling authorized change to the item.

5.3 Configuration Control Board Directive (CCBD)

> A CCBD (see Attachment A, CCBD) is the form used as the authority to
> proceed with implementation of a KSC-sustained Engineering Support
> Request (ESR).

5.4 Configuration Item

A configuration item is defined as an item to be controlled.

5.5 Configuration Change Request (CCR)

> A CCR (see Attachment B, CCR) is a form used to submit a requirement
> or request for change to the ELV PRCB. This form is for changes
> requested by the government, and can require government funding or be
> at no cost to the government. A CCR, through mutual agreement, can be
> written by the government at the request of a contractor. With some
> exceptions (e.g., launch date changes), CCRs with funding requirements
> less that \$500K are not submitted to the board, but are dispositioned
> by the combined signatures of the MIM, LSM, and the Program Analysis
> Officer (if any funding is required). Signature authority may not be
> delegated to a lower level.

5.6 Configuration Management (CM)

> CM is an administrative system integrating (1) Configuration
> Identification (identifying program requirements and hardware/software
> end items to be under configuration control); (2) Configuration
> Control (system for processing changes to requirements and
> configuration baseline); (3) Configuration Verification (assuring by
> reviews that the design satisfies approved requirements, and changes
> have been incorporated per instructions); and (4) Configuration
> Accounting (recording, storing, maintaining, statusing, and reporting
> configuration data).

5.7 Document Change Request (DCR)

> A DCR is the form used to request release of a new ELV document or
> modification to an existing ELV document.

5.8 Engineering Support Request (ESR)

> An ESR is the form used to request changes to KSC-sustained facilities
> (i.e., Hangar AE), systems, or equipment under configuration control
> of the Payloads/ISS Level III and IV Control Boards, affecting, or to
> be funded by, the ELV and Payload Carriers Programs(see Attachment C,
> ESR). The Payloads/ISS Level III Control Board is a NASA-chaired board
> with responsibility for modifications funded at a prescribed
> threshold. The Level IV Control Board is a PGOC-chaired board with
> responsibility for modifications funded below the prescribed NASA
> threshold.

5.9 ESR Assessment and Cost Estimate (EACE)

> An EACE is the formal document used to describe the method of
> implementation and the cost estimate of implementing a KSC-sustained
> ESR.

5.10 In-scope Work

> Work that has been approved and funded as part of the Annual Operating
> Plan. At appropriate times, CCRs will be brought to the Board to
> initiate this work.

5.11 Out-of-Board

> Out-of-board is defined as the process by which a change request may
> be acted upon by a board prior to the next scheduled board meeting. In
> this case, the Board Chairman, or designee, may disposition any board
> action normally exercised at a regularly scheduled meeting. The action
> will be reported in the next PRCB Disposition Report.

5.12 PRCB Process

The major elements of the PRCB process are:

1\. Decision Process: Each member will provide advice and
recommendations to the board, particularly concerning their areas of
responsibility. The Board Chairman has the authority to make all
approval/disapproval decisions on items submitted to the PRCB.

2\. Baseline Management: ELV Launch Services Provider configuration
baselines are established by contract. Changes to those baselines will
be authorized only by following the change processes authorized by this
charter. The contractor who owns/sustains the hardware maintains the
baseline drawings and documentation. KSC-sustained baselines are managed
by NASA and KSC Contractors under the auspices of the KSC Configuration
Management Handbook, KHB 8040.4C.

3\. Approval of Work: The PRCB will approve/disapprove work to be done
to satisfy a requirement/ requested change submitted to the board.

4\. Closure: Notification of contractual implementation of items
approved by the PRCB will be made electronically to the PRCB members.

5.13 Rough Order of Magnitude (ROM)

A ROM is a document that provides a rough estimate of the cost of a
project.

5.14 Not to Exceed (NTE)

> A Not to Exceed is a document that defines a price not to be exceeded
> by a project or task.

5.15 Risk Information Sheet (RIS)

The RIS is the document used to submit an ELV risk (see Attachment F,
RIS).

5.16 Task Assignment (TA)/Task Order (TO)

> A TA or TO is a request made by the government to the launch
> contractor to perform special studies or analyses in support of firm
> or future missions contemplated under the contract. The Mission
> Integration Manager has change authority up to \$500,000 for these
> requests. All requests with a cost over \$500,000, or which will
> exceed the Mission Integration Manager's mission-unique budget
> authority, will be presented to the ELV PRCB for disposition (see
> Attachment D, TA/TO).

5.17 Walk-on Change Requests

> A walk-on change request is defined as a change request not included
> in the agenda of a scheduled meeting. Walk-on change requests must be
> limited to those cases where time constraints and the urgency to work
> a requirement do not allow the normal board process to be followed.

# 6.0 MEMBERSHIP {#membership .unnumbered}

> The PRCB membership will consist of the Chairman, the Secretariat, and
> members representing all functional areas for which the PRCB provides
> control. The authority and responsibilities of the PRCB members are
> described below:

## 6.1 Chairman (Manager, ELV and Payload Carriers Program Office) {#chairman-manager-elv-and-payload-carriers-program-office .unnumbered}

The Chairman (or designee) has the following responsibilities:

1.  Has the sole authority to approve, disapprove, revise, defer for
    further study, or otherwise disposition all proposed changes.

6.1.2 Conducts meetings of the board, as required.

6.1.3 Approves the PRCB Disposition Reports.

6.1.4 Assigns action items, as required, to resolve differences or
complete the change evaluation.

6.1.5 Disposition each item submitted.

6.1.6 Dispositions changes Out-of-Board, as required.

## 6.2 Voting Members {#voting-members .unnumbered}

> Each PRCB member represents an area of functional importance. These
> members review proposed changes and provide technical recommendations
> and support to the PRCB Chairman as needed. The following functional
> positions or their designee will support the PRCB:

6.2.1 Director, ELV Launch Services

6.2.2 Chief, ELV Program Integration Office

3.  Chief, Mission Management Office

6.2.4 Chief, Vehicle Engineering Division

6.2.5 Chief, Safety and Flight Assurance Office

6.2.6 Chief, Launch Site Operations Division

6.2.7 ELV Launch Director

**6.3 PRCB Secretariat**

The following items will be the responsibility of the PRCB Secretariat:

6.3.1 Receive items to be submitted to the board and the attached
requirement, if applicable.

6.3.2 Verify appropriate signatures are present when a change form is
submitted. Ensure the form is completed correctly. Obtain coordination
signatures.

6.3.3 Receive, screen, and forward ELV-generated ESRs for KSC-sustained
facilities/ systems/equipment to the PGOC CM Office for number
assignment and coordination processing.

6.3.4 Develop the agenda for each PRCB meeting.

6.3.5 Distribute the agenda to designated recipients prior to the
scheduled meeting.

6.3.6 Submit the change request package to the PRCB, allowing for review
and coordination. The PRCB board members will be notified, via
electronic media, of the change packages scheduled for the next meeting.

6.3.7 Attend all meetings, record the disposition of each change package
presented, and distribute meeting minutes.

6.3.8 Track and retain change package information required by the PRCB
and community.

6.3.9 Record a list of attendees at board meetings.

6.3.10 Maintain the historical records of the PRCB meetings.

# 7.0 APPLICABLE DOCUMENTS {#applicable-documents .unnumbered}

7.1 NPG 7120.5A, "NASA Program and Project Management Processes and
Requirements"

7.2 NPD 8610.23A, "Technical Oversight Management of Expendable Launch
Vehicle Launch Services"

7.3 KHB 8040.4C, "KSC Configuration Management Handbook"

7.4 NAS10-11400, "The Boeing Company at Kennedy Space Center Payload
Ground Operations Contract (PGOC)"

7.5 SPP E-05, "Processing Changes to Hardware/Software"

# 8.0 DOCUMENTATION  {#documentation .unnumbered}

> All proposed changes under the authority of the PRCB shall be properly
> documented, coordinated, evaluated and disposed of using approved
> forms. The following forms are authorized by the PRCB. Other forms are
> at the discretion of PRCB support functions.

8.1 Change Request Forms

> All proposed changes to ELV contract baseline(s), requiring government
> funding greater than \$500,000, will be presented to the ELV PRCB on a
> Configuration Change Request Form (CCR) (see Attachment B). Task
> Assignments/Task Orders (see Attachment D) with funding greater than
> \$500,000, or which exceed the Mission Integration Manager's
> mission-unique budget authority, will also be presented to the ELV
> PRCB. All changes requested by ELV to KSC-sustained
> facilities/systems/equipment, will be presented to the PRCB for
> technical and funding concurrence on an ESR (see Attachment B),
> complete with ROM or EACE. Document change requests will be presented
> on an ELV/Payload Carriers Program Control Board Document Change
> Request/Directive (see Attachment E).

8.2 Agenda

The PRCB Secretariat will create and distribute an agenda of items
scheduled for each meeting.

8.3 Meeting Minutes

The PRCB Secretariat will prepare the minutes of each PRCB meeting, and
distribute them electronically.

8.4 Action Notification

> Each PRCB representative, at the direction of the Board Chairman, is
> responsible for notifying organizations affected by, or assigned
> actions by, PRCB decisions.

# 9.0 MEETING SCHEDULE {#meeting-schedule .unnumbered}

The PRCB is scheduled to meet weekly. Special sessions may be called if
circumstances require more immediate action.

![](media/image2.png).

![](media/image3.png){width="6.981944444444444in" height="9.1in"}

![](media/image4.png)

![](media/image5.png){width="5.895833333333333in" height="4.8in"}

![](media/image6.wmf)

![](media/image7.png){width="6.770833333333333in" height="9.1in"}