L1 Series COR CDRL Rev 11-8-2023.docx

L1 Series Project COR CDRL L1SERIES-COR-CDRL-0002, Revision - Effective Date: TBD

GSFC SW Next L1 Series CMO

Released

L1SERIES-COR-CDRL-0002, Revision - Space Weather Next L1 Series Project, Code 493

Space Weather Next (SW Next) Program Lagrange (L1) Series Project Coronagraph (COR) Contract Deliverables Requirements List (CDRL)

U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) NOAA Satellite and Information Service (NESDIS) National Aeronautics and Space Administration (NASA)

Effective Date: TBD Expiration Date: TBD

L1 Series Project Coronagraph CDRL L1SERIES-COR-CDRL-0002, Revision -

Check the L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

v Check the L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

Lagrange 1 (L1) Series Project Coronagraph Contract Deliverables Requirements List (CDRL) Signature/Approval Page

Mark Edison

SW Next L1 Series Coronagraph Instrument Lead

NASA Goddard Space Flight Center

Hudson DeLee

SW Next L1 Series Instrument Systems Manager

NASA Goddard Space Flight Center

J. Timothy Van Sant

Project Manager, SW Next L1 Series

NASA Goddard Space Flight Center

Preface

This document is under L1 Series Program configuration control. Once this document is approved, L1 Series approved changes are handled in accordance with Class I and Class II change control requirements as described in the L1 Series Configuration Management Procedure, and changes to this document shall be made by complete revision.

In this plan, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall”. The terms “may” or “can” denote discretionary privilege or permission; “should” denotes a good practice and is recommended but not required; “will” denotes expected outcome; and “are/is” denotes descriptive material.

Any questions should be addressed to:

L1 Series Configuration Management Office

NASA/GSFC

Code 493 Greenbelt, MD 20771

Change History Log

(Reference the CCR & CCB/ERB Approval Date)

Baseline

Table of Contents

L1 Series Project Coronagraph CDRL L1SERIES-COR-CDRL-0002, Revision -ii Check the L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

INTRODUCTION

This Space Weather Next (SW Next) Lagrange 1 (L1) Series (L1 Series) Instrument Contract Deliverables Requirements List (CDRL) document defines the requirements for deliverable items to be provided by the L1 Series Coronagraph Contractor. All data shall be prepared, maintained/updated, and delivered to the Government in accordance with the requirements specified in the governing contract, delivery order, Statement of Work (SOW), Mission Assurance Requirements (MAR), and this CDRL and its associated Data Item Descriptions (DIDs).

DEFINITION OF DUE DATES/MATURITY, DEFINITION OF CATEGORIES, AND DELIVERY INSTRUCTIONS The following definitions apply to the "Delivery" column in Table 2 L1 Series Coronagraph Contract Deliverables Requirements List (CDRL) Due Date

a. Proposal: Items that are provided with the proposal.

b. At CDR, PER, etc.: Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc.

c. As Generated: After each initial edition, revision, addition, etc. Monthly: Monthly by the 15th of each month or as required or as modified by CO

d. Weekly: Weekly status reports by Tuesday close of business or as modified by Contracting Officer (CO)

e. L: Launch Date

f. DACA: Days after contract award

g. MACA: Months after contract award Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

Maturity

a. Preliminary: The initial submission of an item. To be completed with available information as of the time of preparation for the due date.

b. Update: The best up-to-date information available at the time.

c. Final: The complete thorough submission of an item for approval, review, or information. This does not preclude updating later.

NASA Acceptance Code A Approval: Documents in this category require approval by the Goddard Space Flight Center (GSFC) Contracting Officer’s Representative prior to use by the contractor. If the Government disapproves, the requirement for resubmission by the Contractor shall be as specified by the Government Contracting Officer. Normally, the requirement for resubmission will be within 30 days of receiving the Government’s comments. If the Government does not provide comments in the prescribed time, the Contractor may proceed with the associated work after notifying the Government of the intention to proceed.

R Review: Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column of this document. They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives. Following submission, the Contractor may proceed with the associated work. Starting when the Government receives the document, the Government Contracting Officer may provide written (electronic) comments within 21 calendar days. When the Government identifies a deficiency, the Contractor shall re-submit within 30 calendar days of receiving Government comments (3 days for Spacecraft-level test and calibration/validation procedures) or provide a plan within 7 calendar days (1 day for test calibration/ validation procedures), as specified by the Government Contracting Officer, for approval by the Government to close the deficiency.

I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the COR Contract Deliverables Requirements List for the purpose of determining current program status, progress, and future planning requirements. The Government Contracting Officer may provide written (electronic) comments within 21 calendar days to identify errors and omissions, and the Contractor shall make the corrections and re-submit as specified by the Government Contracting Officer. The Contractor shall address Government comments in the next version delivered, or in a revised version if it is the final delivery

CORONAGRAPH CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

Items with an “As Generated” due date that are critical to schedule, performance, or interface shall be transmitted to GSFC by within 48 hours of generation.

Any updates to items of “Final” maturity shall require the same "approval/review" process as was required for the previous submissions.

All Data items shall be delivered in electronic format to a GSFC L1 Series specified web portal unless otherwise noted in the Coronagraph Contract Deliverables Requirements List.

Individual CDRL items may be combined with other CDRL items to increase documentation efficiency if the content and requirements of the CDRL items are satisfied.

Electronic deliverables shall be delivered in the following formats unless otherwise approved by the government:

a. Text Documents: PDF (searchable) or MS Word

b. Presentations: PDF (searchable) or PowerPoint

c. Spreadsheets: Microsoft Excel

d. Database: Delimited ASCII files accompanied with database schema document defining tables and entries.

e. Schedules: MS Project

f. Schematics and Drawings: PDF

g. Photographs: JPEG or current industry standard.

h. Video: Any readily available open standard (e.g., AVI, MPEG)

DATA ITEM DESCRIPTION (DID) OVERVIEW

Each CDRL item is defined by a corresponding DID. The DID includes the title, number, SOW reference, purpose, applicable documents, and required preparation information.

Much of the required information specified in the DIDs may already exist in the Contractor’s documentation. In those cases, existing documents and formats should be used if they meet the intent of the DID requirements. If so, a notation shall be supplied in the deliverable which indicates where in the Contractor’s document the information that satisfies the requirement can be found.

DELIVERY INSTRUCTIONS

a. The Contractor shall deliver each CDRL item via the media indicated below in accordance with the schedule and any special instructions indicated in Table 2 and/or the corresponding DID, and in accordance with the contract or mission-specific Delivery Order (DO) requirements and provisions.

b. All CDRL items shall be delivered electronically (one electronic copy for each CDRL item) to an electronic library designated by the Government. If all or a portion of a CDRL item is not well suited for electronic delivery, the item may be delivered via hard copy upon mutual agreement between the Contractor and the Government.

c. Upon submitting each CDRL item, the Contractor shall notify via email the Government Contracting Officer (CO), the CO Representative, and the Data Management Office.

CDRL ITEMS OVEVIEW

Table 1 provides a list of CDRL item categories as follows:

a. Item #: An alpha-numeric identifier for each CDRL item category and its respective DID. The alpha descriptor is based on the subject matter of the deliverable:

Table 1 Alpha-numeric identifiers for each CDRL

b. Requirements Reference: The reference indicates the section of the L1 Series Instrument SOW, MAR, and/or Instrument Requirements Specification (SPEC) where the CDRL item is called out.

c. Title: (self-explanatory)

d. Delivery: The contract baseline schedule of delivery for the CDRL item. Many of the dates are referenced to reviews or other milestones. Unless stated otherwise, days are calendar days.

e. Flight Model: This column describes if a deliverable is required for the first flight model, all fight models or a subset of all flight models.

f. Purpose: The purpose of the CDRL item submission (i.e., The Government’s role following receipt of a CDRL item) is based on the definitions below. The designation for an item applies to all submissions (e.g., preliminary/initial, update, final) of that item unless noted otherwise. UAR indicates Update as Required with the approval letter indicated in the parenthetical. An A, R, or I indicate the delivery is required, with the Government’s role following a receipt as indicated.

Table 2 L1 Series Coronagraph Contract Deliverables Requirements List (CDRL)

Final: PDR+14 days

Final: PDR + 14 days

4.5.9

4.7

Final: PDR + 14 days

Oct. 31, of each contract year for prior year.

Final: CDR

(no later than the 15th calendar day or each month)

Final: 15 DACA Updates: As generated

4.6

Monthly Updates by the 15th of each month Baseline: Submission includes PCM list NLT 90 days after ATP

I

SDR/SRR –14 days Update:

SDR/SRR – 7 days Final:

NLT SDR/SRR review – 2 days

PDR– 14 days Final:

NLT PDR review – 2 days

(CDR) Data Package Preliminary:

CDR – 14 days Final:

NLT CDR review – 2 days

R

PER Dry Run– 7 days Final:

PER

R

PSR Dry Run – 7 days Final:

PSR

R

Preliminary:

2 days after review Final:

14 days after review

A

30 days after assigned Updates: As agreed

R

Final: PDR – 30 days

5.6

6.1

Final: SDR

A

6.3 Detailed Design Specifications Preliminary: Applicable subsystem PDR Final: Applicable subsystem CDR

R

Update: CDR, FM1 PER, FM1 PSR, and as generated

R

Update: CDR, PER, PSR, and as generated

R

Update: CDR, PER, PSR, and as generated

R

SE-8

4.4 6.1.1

Final: PSR Update: CDR

R R

6.3.2

Update: SDR/SRR Final: PDR

A

6.3.2

Final: PSR

R

6.3.2

SE-12

5.1

Final: CDR – 14 days Update: As Required

A A

1 day after test Preliminary: 5 days after test Final: 30 days after Test

ALL

R R R

6.1

Final: PSR Update: As requested by government

I I

6.5.4

Final: 90 days before Test

Final: CDR

R

Component and Subassembly Test Reports for all Subcontracted Items As generated Maintained on site

Final: CDR

R

Operations Manual for the Coronagraph Emulator

6.2 Request for Use of Multi- Mission or Previously Designed, Fabricated, or Flown Hardware Preliminary: 60 DACA Final: SDR/SRR + 60 days

R

Final: 15 DACA

A

Updates: As updated by Contractor

Interim ODAR and Draft EOMP: 60 days prior to mission CDR Final: 90 days prior to Instrument PSR

I I

Final: 45 days prior to PDR Updates: 30 days prior to implementation

A A

Final: 45 days prior to CDR Updates: 45 days prior to Implementation

A A

Intermediate: 30 days prior to instrument CDR Final: 30 days prior to instrument PSR

A

A

6.5

Launch Range Hazardous Procedures: 65 days prior to first use

45 days prior to SSR Final:

45 days prior to CDR Updates:

45 days prior to PSR

A

A

Criticality Analysis (FMECA) and Criticality Items List (CIL) Preliminary:

30 days prior to PDR Update:

30 days prior to CDR and each subsequent milestone review leading to LRR

MA 4-3

Final: 30 days prior to CDR Updates: 30 days after identification of updates or changes

R R

Final: CDR

R

Preliminary: 30 days prior to CDR Updates: 30 days after identification of updates or changes

R R

Final: 30 days prior to CDR Revisions: 30 days after identification of updates or changes

A A

Revisions within 30 days after identification of updates or changes

Final: 15 days prior to PDR Updates: 30 days prior to implementation

I I

Changes: 14 days prior to manufacturing

Updates prior to inclusion

Final: CDR

30 days prior to PDR 30 days prior to CDR

A A

New or revised after CDR: 30 days after their identification

30 days prior to PDR Final:

30 days prior to CDR Updates within 30 days after identification As-built MIUL 30 days prior to PSR

A A A

30 days after acceptance test completion

I

30 days prior to PDR 30 days prior to CDR

A A

30 days prior to AMRR

A

Final: 30 days before CDR Final thermal vacuum bakeout results: within 30 days of completion Contamination Certificate of compliance with EIADP

A R

R

Disposition of new Alerts within 30 days of Alert release

R

Final: 30 days prior to End Item delivery Updates: 30 days after identification

Final: PSR

R

Final: PSR Updates: As required

R

Final: PSR

A

Algorithms Test and Validation Plan Preliminary: PDR Update: CDR Final: PSR - 3 months

A A

Update: CDR Final: PSR -3 months

A A

Final: PSR - 6 months

R

Final:

CDR as generated

R

Updates: As needed

R

30 DACA

Final:

SW Acceptance Review Update:

PDR, CDR, TRR

A A

Packages Preliminary: PER Final: PSR Updates: At major revision releases

R R

Final: CDR

Final: 2 months after test

Final: PSR

Update: PDR Final: CDR

A A

Final: 30 days before PDR

R

30 days before PDR Updates: As generated Final: 30 days before CDR

Check the L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

PROGRAM DATA ITEM DESCRIPTIONS

Program Management Plan CDRL No. PM-1

Reference:

COR SOW Section 1.1

Purpose:

Describes how the program is organized and managed. It provides the management structure, its system of operation, responsible lines of communications, and key personnel assignments

Preparation Information:

1. The Program Management Plan shall address the overall organization, management approach, and structure of the COR Program plus its interrelationships with the parent company and the subcontractors, and relationship with the Government.

2. The Program Management Plan shall delineate how the requirements of the Statement of Work (SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.

3. The Program Management Plan shall address interfaces with the Government and with any Government Furnished Equipment (GFE) suppliers.

4. The Program Management Plan shall indicate critical paths, long-lead items and significant milestones down to the lowest level of the WBS.

5. The Program Management Plan shall indicate the need for additional definition of spacecraft and mission information, and when this information is required to avoid schedule slippage.

6. The Program Management Plan shall include graphical displays such as flow diagrams, WBS, logic networks, etc., to reduce verbal descriptive material.

7. The Program Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the program showing inter- relationships of technical management, business management, and subcontract management, from lower level through intermediate management to top-level management with detailed explanation of:

a. The authority of the COR Program Manager relative to other ongoing programs and applicable support organizations within the company structure. Discuss the program manager’s control over essential resources and functions necessary to accomplish the work.

b. How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.

c. Process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions not under the program manager’s direct control such as personnel, finances, and facilities.

d. The lead program team members with names, functions, and qualifications

8. The Program Management Plan shall provide contractual procedures proposed for the program to effect administrative and engineering changes, describing any differences from existing procedures.

9. The Program Management Plan shall describe management techniques to be employed in minimizing program costs and schedule impacts, including controls to be exercised over subcontractors and suppliers.

10. The Program Management Plan shall describe how issues will be surfaced in a timely manner and at the proper levels.

11. The Program Management Plan shall describe how supply chain performance will be tracked.

12. The Program Management Plan shall discuss and illustrate the proposed COR Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

13. The Program Management Plan shall discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours) are presently on payroll and immediately available for this work.

14. The Program Management Plan shall state the number and kind of persons who would have to be hired and plans to obtain them.

15. The Program Management Plan shall describe how the schedules are developed, maintained and updated.

16. The Program Management Plan shall describe how subcontracts will be managed and reviewed and describe the performance milestones of each.

17. The Program Management Plan shall list and describe the planned subsystem reviews.

WEEKLY STATUS REPORTS AND TELECON MINUTES

CDRL No.

PM-2

Reference:

COR SOW Section 4.5.8

Purpose:

Contract status evaluation.

Preparation Information:

1. The Weekly Status Report shall indicate the status of the contract as of close of business the preceding Friday, including a summary of progress made.

2. The Weekly Status Report shall address the work completed during the week against the work planned for the week, and address recovery plans if necessary.

3. The Weekly Status Report shall include technical progress, including significant accomplishments and milestones reached.

4. The Weekly Status Report shall include problems encountered and proposed corrective action.

5. The Weekly Status Report shall indicate any actual or anticipated slip in schedule.

6. The Weekly Status Report shall include identification of any Class I or Class II changes.

7. The Weekly Status Report shall detail the work planned for the next week and summarize the work planned for the next month.

8. The Weekly Status Report shall contain Action Item Status for any overdue action items and any action items due in the next two weeks.

9. The Weekly Status Report shall contain status of any open Non-Conformance Reports.

10. The Weekly Status Report shall contain status on any open contract actions, including Special Engineering Analyses.

11. The Weekly Status Report shall contain status on any red risk item.

Note: This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

CONFIGURATION MANAGEMENT PLAN

CDRL No.

PM-3

Reference:

COR SOW Section 4.4.1

Purpose:

To define the contractor’s configuration management system and provide a means of control for all changes affecting form, fit, or function and any impact on performance, cost or schedule.

Preparation Information:

1. The Configuration Management Plan shall describe the scope, approach, methods, and procedures of the system used to control changes of requirements, design, and any other configuration managed item.

2. The Configuration Management Plan shall describe the organization of the configuration management program and how it relates to the rest of the COR program.

3. The Configuration Management Plan shall list all tools used for configuration management.

4. The Configuration Management Plan shall use the following product change classifications:

a. A change or request for Deviation/Waiver is classified as Class I when it affects one or more of the following factors:

i. Program baseline documentation

ii. Technical requirements contained in the product configuration identification, including the following:

1. Form, fit, or function

2. Performance

3. Power

4. Reliability outside stated requirements

5. Weight, balance, moment of inertia

6. Interface characteristics

7. Hardware and process qualifications

iii. Non-technical contractual provisions

1. Fee

2. Incentives

3. Cost

4. Schedule

5. Guarantees or deliveries

iv. Other factors

1. Government-furnished property (GFP)

2. Safety

3. Electromagnetic characteristics

4. Deliverable operational, test, or maintenance computer programs

5. Compatibility with support equipment

b. A change is classified as Class II when it does not fall within the definition of a Class I change.

CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

CDRL No.

PM-4

Reference:

COR SOW Section 4.4.1

Purpose:

Class I changes are to be used as a vehicle for orderly processing of change requests to appropriate level of approval authority for disposition.

Preparation Information:

Class I Configuration Change Requests shall document proposed changes impacting form, fit, function, cost, schedules or performance per the Configuration Management Plan or per the Software Configuration Management Plan section of the Software Management Plan.

PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

CDRL No.

PM-5

Reference:

COR SOW Section 4.5

Purpose:

To summarize the progress since the previous Program Management Status Review.

Preparation Information:

The Program Management Status Review Data Package shall include the following items:

1. Accomplishments since last review, including 20 milestone events depicting critical items of program status for the succeeding two months with a report on the previous two months milestone events

2. Schedule

3. Technical issues and concerns, including summaries of technical progress and descriptions of the current technical issues and concerns

4. Business issues and concerns, including personnel changes

5. Open contract items

6. Open action items

7. Planned effort for next review period

8. Reliability and quality assurance information

9. Mass properties and power summary

10. Software metrics for each Class A, B or C Computer Software Configuration Item (CSCI) including:

a. Number of software requirements and their change status

b. Number of software change requests and problem reports and their status

c. Resource utilization estimates and measurements of memory, CPU and I/O Bandwidth

11. Financial summary including a summary of actuals versus planned manpower

12. Subcontractor status including:

a. Efforts under contract

b. Efforts waiting contract award

c. Changes to first tier and sub-tier contractors

d. Change orders, problems, issues

e. Pending subcontractor consent packages

f. Supply chain performance will be tracked using the table below, updated bi-monthly. This includes items 12. a. through 12. e. for subcontracts.

(on contract)

13. A list of actions requested of GSFC management

14. Update of corporate changes, for example: early warning of

a. Restructuring activities (including internal reorganizations)

b. Indirect/direct rate changes

15. Risk assessment including approach for mitigation

16. Any additional data requested by GSFC

RISK MANAGEMENT PLAN

CDRL No.

PM-6

Reference:

COR SOW Section 4.1 and 4.7

Purpose:

To describe the methodologies and processes used to identify, analyze, plan, track, control and communicate the contractor’s risks. The identification, characterization, mitigation plan, and mitigation responsibilities associated with specific risks are described and specific risk abatement strategies or contingency planning processes are discussed. “Risk” refers to anything that can prevent a team from meeting the Delivery Order objectives.

Preparation Information:

1. The Risk Management Plan shall document the process the Contractor will follow to manage risk throughout the life cycle of COR. This includes technical performance, programmatic, cost, and schedule risks.

2. The Risk Management Plan shall provide descriptions of the processes to provide management at all levels with 1) a disciplined system for early identification of technical uncertainties, 2) a disciplined assessment of current program status, and 3) key indicators of mission success.

3. The Risk Management Plan shall describe the basis for taking action to control risk and for measuring the effectiveness of that action.

4. The Risk Management Plan shall be tailored from NPR 8000.4 and cover:

a) Overview of Risk Management Process

b) Process Details

1) Risk identification - The process to determine and define all risks.

2) Risk analysis - The process to convert risk data into decision-making information. This process should include estimating the probability, impact and time frame of the risks, eliminating duplicates and grouping similar risks, and prioritizing them according to consequences.

3) Risk planning - The process to develop mitigation options and decide what to do with the risks.

4) Risk tracking - The process to acquire, compile and report risk status data, including risk indicators and mitigation actions. Appropriate risk metrics should be identified so that the Government can evaluate the quality of the risk management.

5) Risk control - The process covering decisions to re-plan mitigation, close risks, invoke contingency plans or continue to track risks. The plan should define responsibilities, typical milestones/reviews, and describe the key risk control activities.

6) Communications and documentation - Present in all the above processes, this is the means by which the output of the processes is documented and communicated to all team members.

5. Risk Information Documentation

6. Constraints and De-scope options

7. For the Top Risks, risks having both a high probability and high impact/severity, the plan shall require, the following (see NPR 8000.4):

a) Description of the risk

b) Primary consequence should the undesirable event occur

c) Estimate of probability of occurrence and the fidelity of the estimate

d) Significant cost impacts, given its occurrence

e) Significant schedule impacts, given its occurrence

f) Potential mitigation measure not already taken and the cost to implement them

g) Characterization of the risk as acceptable or unacceptable with rationale

PM-7 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

Title:

NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

CDRL No.

PM-7

Reference:

COR SOW Section 3.4

Purpose:

For budget, cost, and property control

Preparation Information:

The NASA Property in the Custody of the Contractors report shall consist of NASA Form 1018 in accordance with NFS 1845.505-14, the instructions on the form, subpart 1845.71, and any supplemental instructions for the current reporting period issued by NASA.

CONTRACTOR TASK PLAN

CDRL No.

PM-8

Reference:

COR SOW Section 3.4

Purpose:

The task plan is the contractor's resources plan for accomplishing the work described in the task order.

Preparation Information:

The Contractor Task Plan shall be prepared in accordance with Contract Clause H.8

DOCUMENT TREE

CDRL No.

PM-9

Reference:

COR SOW Section 3.4

Purpose:

For ready reference list of all COR and GSE documents.

Preparation Information:

1. The document tree shall list all documents for the COR and separately for the GSE.

2. The document trees shall be organized and identified to serve as a ready reference list.

3. The document tree shall identify documents by name and number.

4. The document tree shall include a brief description defining the scope of each document

RESOURCE MANAGEMENT

MONTHLY AND QUARTERLY FINANCIAL REPORT

CDRL No.

RM-1

Reference:

COR SOW Section 4.5

Purpose:

For budget and cost control

Preparation Information:

1. The Monthly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR 9501.2D, NASA Contractor Financial Management Reporting on NASA Form 533M.

2. The Monthly Financial Report shall be submitted within 15 days of the end of the reporting period.

3. The Quarterly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR 9501.D, NASA Contractor Financial Management Reporting on NASA Form 533Q. The report is due 2 weeks prior to the period being reported.

4. At a minimum, the reporting structure shall be in accordance with and to Level 1 of the WBS as set forth in Attachment J.

5. The reporting categories shall include as a minimum:

a. Direct labor by labor category

b. Overhead

c. Fringe Benefits

d. Materials

e. Material Overhead

f. Subcontracts

g. Travel

h. Other Direct Costs

i. Facilities Capital Cost of Money

j. Fee

k. Total Cost-Plus Fee

CONTRACTOR’S WORK BREAKDOWN STRUCTURE DIAGRAM AND DICTIONARY

CDRL No.

RM-2

Reference:

COR SOW Section 4.

Purpose:

To facilitate program planning and control and for financial and technical reporting.

Preparation Information:

1. The Contractor's Work Breakdown Structure (WBS) Diagram shall document Government accepted changes to the Government WBS with an updated WBS diagram and description of task elements.

2. The Contractor's WBS Diagram shall define all work included in the COR development life cycle.

3. The Contractor's WBS Diagram shall provide a framework for program work definition to a level of detail consistent with cost, schedule, technical, and risk oversight as desired by contractor's management.

4. The Contractor's WBS Diagram shall contain a companion WBS dictionary that narratively describes the overall structure and content of each individual element of the WBS.

EARN VALUE MANAGEMENT (EVM) PLAN

CDRL No.

RM-3

Reference:

COR SOW Section 4.2

Purpose:

Provide a comprehensive description of the Contractor’s plan for utilizing an EVM System (EVM) that complies with the Electronic Industries Alliance (EIA)-748 guidelines.

Preparation Information:

1. The EVM plan shall present the Contractor's approach to comply with the EIA-748 guidelines.

2. The EVMS description or EVM Plan shall address:

a. Establishing and maintaining the Project Management Baseline (PMB),

b. The processes for changing the PMB through Baseline Change Requests (BCRs),

c. The processes for conducting variance analysis,

d. The processes to determine and implement solutions to resolve the causes of variances,

e. Developing ongoing comprehensive estimates at completion,

f. Flowing down requirements to all applicable subcontracts, and

g. Managing technical scope, schedule, cost, and risk.

3. The EVMS description or EVM Plan shall address the requirements of NASA’s Federal Acquisition Regulation Supplement (NFS) 1852.234-2 or Alternate I. Guidelines are available in the Earned Value Management Systems EIA-748-C Intent Guide Appendix Compliance Map Template.

Applicable Documents:

Industry Guidelines for Earned Value Management Systems, EIA-748 Earned Value Management System, NFS 1852.234-2 (or Alternate I) Earned Value Management System, EIA-748 Intent Guide Appendix Compliance Map Template

DETAILED SCHEDULES

CDRL No.

RM-4

Reference:

COR SOW Section 4.4.1 and 4.6

Purpose:

For understanding and mapping out in detail the most efficient way of melding together all elements necessary for providing the program deliverables by their required delivery times.

Preparation Information:

1. The schedule shall encompass all phases of the program indicating critical path and schedule slack and reserve.

2. The contractor shall establish, implement, and maintain an instrument schedule. Each Flight Model (FM) development and delivery shall be tracked in the schedule.

3. Phase 1 schedules shall include the instrument and GSE design, the Program Reviews, fabrication and test of the Engineering Development Unit (EDU) and GSE.

4. Phase 2 schedules shall include the fabrication, test, calibration, and delivery of the Flight Models (FMs) instruments and their integration to the L1 Series spacecraft.

5. Design schedules shall be detailed by task with expected start and completion dates.

6. Procurement schedules shall be detailed by major items, assembly, or definable subassembly.

7. Procurement schedules shall be subdivided into standard electrical parts, integrated circuits, etc.

8. Fabrication schedules shall be detailed to the mechanical subassembly level and to the electronic board level, and show the expected start and completion dates, as well as substantive in-process milestones.

9. Detailed schedules shall indicate critical paths.

10. Detailed schedules shall indicate slack and reserve.

REVIEW DATA ITEM DESCRIPTIONS

RVW-1 INTEGRATED BASELINE REVIEW (IBR) DATA PACKAGE

Title:

INTEGRATED BASELINE REVIEW (IBR) PACKAGE

CDRL No.

RVW-1

Reference:

COR SOW Section 4.5.2

Purpose:

An IBR is a joint assessment conducted by NASA’s Project manager and the Contractor to verify the realism and accuracy of the performance measurement baseline (PMB). This includes verifying the technical content of the baseline and assessing the realism and accuracy of the related resources (cost, risk, and schedule). The IBR is the major review for the contract. The review occurs within the first 180 days after contract award and as required after exercising significant contract options or 60 calendar days after a significant funding or work scope realignment. The IBR package is a compilation of on-going operational Project documents for the purpose of assessing the PMB.

Preparation Information:

1. The IBR package shall contain the following:

a. Work breakdown structure (WBS) dictionary

b. Statement of Work with WBS cross-reference index

c. Integrated Master Plan (IMP), if available, or key Project milestones

d. Project risk register

e. Risk management plan

f. Organizational breakdown structure – to the control account manager level

g. Subcontractor listing by WBS element and value of subcontracts, if applicable

h. Contractor/Subcontractor earned value management system flow- down requirements

i. Responsibility assignment matrix showing dollars allocated by control account (CA)

j. Earned value management system description and related business process descriptions (e.g. risk management)

k. Initial Control Account Plans, including Basis of Estimates, Assumptions, and Risks

l. Latest Estimate at Completion and supporting documentation

m. Work Authorization Documents (all levels)

n. Baseline/Budget Change Requests approved thus far, if applicable

o. Baseline control logs (management reserve, undistributed budget, contract budget base)

p. Integrated master schedule with linkages to IMP, if available

q. Supporting schedules (intermediate, and detailed, as applicable)

r. All integrated program management reports to date

s. Financial reports such as 533M/Q or equivalent

t. Performance measurement reports used for internal management purposes

u. CA/work package summary showing:

i. Number of work packages and total value by type of earned value method/performance measurement technique

ii. Longest CA, shortest CA, mean and median duration, total value of account

iii. Largest CA, smallest CA, mean and median values – number of planning packages (PP) and total PP budget

v. All contract changes to date.

2. The above list is intended to be a comprehensive example of the final list. This list should be tailored based on information required for preparation and insight. The supplier may have the data described above in different formats or naming conventions.

Applicable Documents

1. NASA Procedural Requirement 7120.5, NASA Space Flight Program and Project Management Requirements

2. NASA’s Federal Acquisition Regulation Supplement 1852.234-2, Earned Value Management System

3. NASA/SP-3406, NASA IBR Handbook

RVW-2 SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

Title:

SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

CDRL No.

RVW-2

Reference:

COR SOW Section 4.5.4.1

Purpose:

To evaluate the requirements, requirements flow-down, and the operational concepts and to validate the realism of the functional and performance requirements and their congruence with the system configuration selected to conduct the mission.

Preparation Information:

1. The SDR Data Package shall discuss contractor system level requirements, rationale, and flow- down plans to lower-level requirements.

2. The SDR Data Package shall cover the COR System Specification and the traceability matrix to applicable government requirements documents.

3. The SDR Data Package shall cover requirements for the COR instruments (Flight Models), Ground Support Equipment, flight software, ground test software, and processing algorithm.

4. The SDR Data Package shall show how the current concept meets all government specified requirements including interface requirements.

5. The SDR Data Package shall identify any COR technologies that are below Test Readiness Level (TRL) 6.

RVW-3 PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

Title:

PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

CDRL No.

RVW-3

Reference:

COR SOW Section 4.5.4.2

Purpose:

To demonstrate the Flight Equipment and GSE designs meet the documented requirements.

Preparation Information:

1. The PDR…