Attachment D Coronagraph_CDRL_SWFO-MGMT-CDRL-0010.pdf

Effective Date: TBD o

Expiration Date: TBD

Space Weather Observations Program Division, Code 490.0

SWFO-MGMT-CDRL-0010, Revision –

Space Weather Next Lagrange 1 Series (L1 Series) Coronagraph

Contract Deliverables Requirements List

(CDRL)

SWO CMO

<Date>

Released

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

NOAA Satellite and Information Service (NESDIS)

National Aeronautics and Space Administration (NASA)

Space Weather Observations (SWO) Program Division rrect version prior to use.

L1 Series Coronagraph CDRL SWFO-MGMT-CDRL-0010

Effective Date:

iii

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to use.

Electronic Approval available on-line at:

https://swfowc.ndc.nasa.gov/SWFOWC/app/#ptc1/homepage iv

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

Preface

This document is under SWO Program Division configuration control. Once this document is approved, changes are handled in accordance with Class I and Class II change control requirements as described in the SWO 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:

SWO Configuration Management Office

NASA/GSFC

Code 490.0

Greenbelt, MD 20771 v

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

Change History Log

Revision Effective Date Description of Changes

(Reference the CCR & CCB/ERB Approval Date)

Draft 04/08/2022 Notional document for Formulation RFP vi

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

Table of Contents

1 INTRODUCTION

1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions

2 CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

3 DATA ITEM DESCRIPTIONS

3.1 Program Management Plan

3.2 Weekly Status Reports and Telecon Minutes

3.3 Monthly and Quarterly Financial Report

3.4 NASA Property in the Custody of the Contractors

3.5 Reserved

3.6 Contractor’s Work Breakdown Structure Diagram and Dictionary

3.7 Reserved

3.8 Reserved

3.9 Detailed Schedules

3.10 Configuration Management Plan

3.11 Configuration Change Requests (CCR) Class I

3.12 Reserved

3.13 Safety and Health Reports

Reserved

3.14 Error! Bookmark not defined.

3.15 Responses to Requests for Action

3.16 System Definition Review (SDR) Data Package

3.17 Preliminary Design Review (PDR) Data Package

3.18 Critical Design Review (CDR) Data Package

3.19 Pre-Environmental Review (PER) Data Package

3.20 Pre-Storage/Pre-Ship Review Data Package

3.21 Reserved

3.22 Program Management Status Review Data Package

3.23 Subsystem Review Minutes and Action Items

3.24 Subcontract and Subsystem Review Data Packages

3.25 Reserved

3.26 Reserved

3.27 Reserved

3.28 Reserved

3.29 Risk Management Plan

3.30 Systems Engineering Management Plan

3.31 Engineering Analyses Reports

3.32 Reserved

3.33 Document Tree

3.34 Instrument Description Document (IDD)

vii

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

3.35 Flight Telemetry and Command Database

3.36 Flight Telemetry and Command Handbook

3.37 System Specification

3.38 Contamination Control Plan

3.39 Solid Math Model

3.40 Thermal Math Models and Reports

3.41 Structural Math Model and Reports

3.42 Contractor Task Plan

3.43 Reserved ............................................................................ Error! Bookmark not defined.

3.44 Instrument Block Diagrams and Approved or Controlled Drawings

3.45 Detailed Design Specifications

3.46 Software Management Plan

3.47 Software Delivery Packages

3.48 Reserved

3.49 Reserved

3.50 Digital Imagery and Video Records

3.51 Reserved

3.52 System Performance Verification Plan

3.53 Individual Test Plans

3.54 Performance Verification Procedures

3.55 Environmental Verification Specification

3.56 Radiation Shielding and Dose Analysis Report

3.57 Single Event Effects Control Plan

3.58 Reserved

3.59 Magnetic Control Plan

3.60 Verification Reports

3.61 Component and Subassembly Verification Reports for All Subcontracted Items

3.62 EMC/EMI Compatibility Plan

3.63 Mass Properties and Power Report

3.64 Calibration Program Plan

3.65 Calibration Data Books

3.66 Ground Processing Algorithm Document

3.67 Ground Processing Algorithms Test and Validation Plan

3.68 Ground Software Acceptance Plan Input

3.69 Packetized Data

3.70 Reserved

3.71 Maintenance, Test, and Operations Manual for the Coronagraph Emulator

3.72 Reserved

3.73 Reserved

3.74 Request for Use of Inherited, Build-to-Print, or Modified Heritage Items

3.75 Software Assurance Plan

3.76 Non-Conformance Reports

3.77 System Safety Program Plan (SSPP)

viii

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

3.78 Safety Assessment Report

3.79 Reserved

3.80 Reserved

3.81 Operations Hazard Analysis and Hazard Verification Tracking Log

3.82 Pre-Mishap Plan

3.83 Failure Mode, Effects, and Criticality Analysis (FMECA) and Critical Items List (CIL) 91

3.84 Worst-Case Analyses

3.85 Reliability Predictions

3.86 Trend Analysis Plan and Data Reports

3.87 Limited Life Items List

3.88 EEE Parts Control Plan

3.89 Master EEE Parts List

3.90 Reserved ............................................................................ Error! Bookmark not defined.

3.91 Materials Usage Agreement and/or Stress Corrosion Evaluation Form

3.92 Electrostatic Discharge Control Plan

3.93 GIDEP Alert/NASA Advisory Dispositions

3.94 Transportation Handling Plan and Procedures

3.95 Reserved

3.96 On-Site Data Analysis Reports

3.97 Observatory Level Test Procedures

3.98 Observatory Level Test Report

3.99 Operations Handbook

3.100 Post-Launch Test Reports

3.101 Major Anomaly Report

3.102 System Performance Verification Report

3.103 Reserved

3.104 Reserved

3.105 Field Programmable Gate Array (FPGA) Development Plan

3.106 Reserved

3.107 End Item Acceptance Data Package

3.108 Mission Assurance Requirements Compliance Matrix

3.109 Supplier List

3.110 Reporting of Material Review Board Actions

3.111 Input to Orbital Debris Assessment Report and End of Mission Plan

3.112 Safety Requirements Compliance Checklist

3.113 Safety Data Package

3.114 Hazardous Procedures for Payload I&T and Prelaunch Processing

3.115 Parts Stress Analysis

3.116 Alternate Printed Circuit Board Standard Report

3.117 Printed Circuit Board Procurement Plan

3.118 Lot Acceptance and Quality Conformance Test Results for Printed Circuit Boards

3.119 Materials and Processes Selection, Control, and Implementation Plan

3.120 Materials Identification and Usage List

ix

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov/SWFOWC/app/#ptc1/homepage to verify that this is the correct version prior to

3.121 Foreign Object Debris Prevention and Control Plan

3.122 Instrument Operations Configurable Items

3.123 Initiating GIDEP Alerts

4 HARDWARE DELIVERABLE ITEMS

APPENDIX A ABBREVIATIONS AND ACRONYMS ............ ERROR! BOOKMARK NOT

DEFINED.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

1 INTRODUCTION

This Contract Deliverables Requirements List (CDRL) document defines the requirements for deliverable items to be provided by the contractor. Section 1.1 includes definitions and instructions for distribution. Section 2 presents the deliverable item by item with due dates.

Section 3.0 provides the Data Item Description (DID), a description of each item and describes use, and preparation information. Section 4.0 defines the hardware and software deliverable items and due dates.

1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions

The following definitions apply to the "DUE DATE, MATURITY" column in the Coronagraph

Contract Deliverables Requirements List.

a) DUE DATE:

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

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

Review, etc.

3. As Generated: After each initial edition, revision, addition, etc.

4. Monthly: Monthly by the 15th of each month or as required or as modified by CO

5 Weekly: Weekly status reports by Tuesday close of business or as modified by

Contracting Officer (CO)

6. L: Launch Date

7. DACA: Days after contract award

8. MACA: Months after contract award

Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

b) MATURITY:

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

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

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

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

c) NASA Acceptance Code

A Approval: Documents in this category require approval by the GSFC Contracting

Officer’s Representative (COR) prior to use by the contractor.

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.

I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the Coronagraph Contract

Deliverables Requirements List for the purpose of determining current program status, progress, and future planning requirements.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

2 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.

Receipt of “Approval”, “Review”, and “Information” coded items by the Government shall occur within the time specified in the "Due Date" column of the Coronagraph Contract

Deliverables Requirements List of this document.

Requirements for re-submission of “Approval” coded items shall be as specified in the letters of disapproval. For most cases, the contractor will be required to resubmit the document within 30 days of receiving comments from the Government.

If the contractor has not received response from GSFC within 60 days of delivery of an

“Approval” coded CDRL item (15 days for test procedures), the contractor may proceed as if the document has been approved.

When Government evaluations of “Review” coded items reveal inadequacies, the Contractor shall correct the documents within 30 days of receiving comments or provide a plan approved by the Government for closing deficiencies.

All Data items shall be delivered in electronic format to a government-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:

1 Text Documents: PDF (searchable) or MSWord

2 Presentations: PDF (searchable) or PowerPoint

3 Spreadsheets: Microsoft Excel

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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

5 Schedules: MS Project

6 Schematics and Drawings: PDF

7 Photographs: JPEG or current industry standard.

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

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Contract Deliverables Requirements List (CDRL)

ID

No.

Document Title

Due Date, Maturity

NASA

Accept.

Program Management Plan Preliminary: 30 DACA

Final: PDR+14 days

R

Weekly Status Reports and

Telecon Minutes

Weekly

I

Monthly Financial Report

Quarterly Financial Report

Per Contract Clause B.3 (no later than the 15th calendar day or each month)

NASA Property in the

Custody of the

Contractors

Per Contract Clause G.6

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

Reserved

Contractor’s WBS

Diagram and Dictionary

Final: 15 DACA

Updates: As generated

A

007 Reserved

008 Reserved

Detailed Schedules

Preliminary: 15 DACA

Monthly Updates by the 15th of each month

Configuration Management

Plan

Preliminary: 15 DACA

Final: PDR + 14 days

Configuration Change

Requests (CCR) Class I

As generated

012 Reserved

Safety and Health Report

Per the contractual requirements in clause B.3

Data Package

Responses to Request for

Actions

Preliminary: 30 days after assigned

Updates: As agreed

System Definition Review

Preliminary: SDR/SRR – 14 days

Update: SDR/SRR – 7 days

Final: SDR/SRR

Preliminary Design Review

Data Package

Preliminary: PDR Dry Run – 7 days

Final: PDR

Critical Design Review

Data Package

Preliminary: CDR Dry Run – 7 days

Final: CDR

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Pre-Environmental Review

Preliminary: PER Dry Run of each

Model – 7 days

Final: PER of each Model

Pre-Storage/Pre-Ship

Review Data Package

Preliminary: PSR Dry Run of each

Model – 7 days

Final: PSR of each Model

021 Reserved

Program Management

Status Review Data

Package

Bi-Monthly (starting in July 2020)

Subsystem Review

Minutes and Action Items

Preliminary: 2 days after review

Final: 14 days after review

R

R

Subcontract and Subsystem

Review Data Packages Final: Review R

025 Reserved

026 Reserved

027 Reserved

028 Reserved

029 Risk Management Plan

Final: PDR + 14 days R

Systems Engineering

Management Plan

Preliminary: 30 DACA

Final: 15 May 2021 R

Engineering Analyses

Reports As generated R

032 Reserved

Document Tree Preliminary: PDR

Flight Telemetry and

Command Database

Baseline: PER of FM1

Flight Telemetry and

Command Handbook

Preliminary: PDR

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Coronagraph System

Specification

Preliminary: SDR – 14 days

Final: SDR

Contamination Control

Plan

Preliminary: 30 days before

PDR

Final: 30 days before CDR

Solid Math Model

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

Thermal Math Model and

Reports

Preliminary: PDR

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

Structural Math Model and

Preliminary: PDR

Update: CDR, PER, PSR, and as generated

Contractor Task Plan

Per Contract Clause H.8 (only required once a special study is requested/awarded)

Instrument Block

Diagrams, and

Approved or Controlled

Drawings

Update: CDR

Final: PSR

Detailed Design

Specifications

Preliminary: Applicable subsystem

PDR

Final: Applicable subsystem CDR

Software Management

Plan

Preliminary: 30 DACA

Update: PDR, CDR, TRR

Final: SW Acceptance Review

Software Delivery

Packages

Digital Image and Video

Records

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

System Performance

Verification Plan

Preliminary: With Proposal

Update: SDR/SRR

Individual Test Plans Preliminary: CDR

Final: 90 days before Test

Performance Verification

Procedures

30 Days prior to use

Environmental Verification

Specification

Radiation Shielding and

Dose Analysis Report

Single Event Effects

Control Plan

Magnetic Control Plan

Verification Reports Preliminary: 1 day after test

Final: 30 days after Test

Component and

Subassembly Test Reports for all Subcontracted Items

As generated.

Maintained on site

EMC/EMI Compatibility

Plan

Mass Properties and Power

Report Monthly NLT 15th of each month

Calibration Program Plan

Preliminary: SDR/SRR

Update: PDR

Calibration Data Books

Ground Processing

Algorithm Document

Preliminary: PDR

Final: PSR -3 months

Ground Processing

Algorithms Test and

Validation Plan

Preliminary: PDR

Final: PSR - 3 months

Ground Software

Acceptance Plan Input

Final: PSR - 6 months

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

069 Coronagraph Packetized Data As generated I

070 Reserved

Maintenance, Test, and

Operations Manual for the

Emulator

Final: With Delivery of Emulator

072 Reserved

073 Reserved

Request for Use of Multi-

Mission or Previously

Designed, Fabricated, or

Flown Hardware

Preliminary: 60 DACA

Final: SDR/SRR + 60 days

Software Assurance Plan

Preliminary: 30 days prior to

SDR/SRR

Final: 15 days prior to CDR

Updates: Review for updates if software criticality or classification is updated and when [CDRL-46]

Software Management Plan is updated.

Non-Conformance Report

Notify In-plant Resident Office by the next business day.

Written Notification: < 1 week

Update: Completion of analysis, Assignment of Corrective Action

Final: Closure

System Safety Program Plan Preliminary: SDR/SRR

Final: 30 days prior to PDR

Safety Assessment Report

Preliminary: PDR + 30 days

Update: Coronagraph CDR

Final: Coronagraph PSR -30 days

079 Reserved

080 Reserved

Operations Hazard Analysis

Final: 45 days prior to PER

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

082 Pre-Mishap Plan 45 days prior to PDR A

Failure Mode, Effects, and

Criticality Analysis and Criticality Items List

Preliminary: 30 days prior to PDR Final: 30 days prior to CDR

084 Worst-case Analyses 30 days prior to CDR Revisions within 30 days

R

085 Reliability Predictions Preliminary: PDR

Trend Analysis Plan

Trend Analysis Data

Preliminary: PDR

As Generated

Limited Life Items List

Preliminary: 30 days prior to PDR

Updates: Revisions within 30 days

EEE Parts Control Plan

Master EEE Parts List

Materials Usage

Agreement and/or Stress

Corrosion Evaluation Form

New MUAs: 30 days prior to CDR

Updated MUAs: as generated

Electrostatic Discharge

Control Plan

Preliminary: 2 MACA

GIDEP Alerts

Disposition of existing Alerts within

30 days of identification

Disposition of new Alerts within 30 days of Alert release

Transportation, Handling

Plan and Procedures

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

On-site Data Analysis

Observatory Level Test

Procedures

Preliminary: PER

Observatory Level Test

Report

Observatory PSR

Operations Handbook Preliminary: PER

Post Launch Test Reports

Preliminary: 2 weeks after test

Final: 2 months after test

Major Anomaly Report

Preliminary: Electronic submission within 24 hours of occurrence

Updates: Electronic notification of a change in status within 24 hours of occurrence

Final: prior to closure

System Performance

Verification Report

103 Reserved

FPGA Development Plan

Preliminary: SRR/SDR

Update: PDR

106 Reserved

End Item Acceptance Data

Package

Preliminary: PSR – 14 days

Final: 30 days post delivery

Mission Assurance

Requirements Compliance

Matrix

Preliminary: 60 DACA

Update: 30 days prior to implementation

Supplier List

Preliminary: 60 DACA

Update: semi-annually after contract award

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Reporting of MRB Actions

Major MRB actions: within 5 working days of MRB action

Minor MRB actions: within 5 working days of MRB action

Input to Orbital Debris

Assessment Report

Preliminary: 15 days prior to mission

PDR

Updates: 60 days prior to mission CDR

Final: 90 days prior to Instrument PSR

Safety Requirements

Compliance Checklist

Preliminary: 45 days prior to

SDR/SRR

Final: 45 days prior to PDR

Updates: 45 days prior to CDR

Safety Data Package

Preliminary: Coronagraph PDR – 30 days

Updates: Coronagraph CDR

Final: Coronagraph PSR -30 Days

Hazardous Procedures for Payload I&T and Prelaunch

Processing

Payload I&T Hazardous Procedures:

7 days prior to first use

Launch Range Hazardous

Procedures: 60 days prior to first use

Parts Stress Analysis Final: 45 days prior to CDR

Revisions: NLT 30 after identification

Alternate Printed Circuit

Board Standard Report

30 days prior to use

Printed Circuit Board

(PCB) Procurement Plan

Preliminary: 30 days prior to procurement

Updates: 14 days prior to circuit board manufacturing

Lot Acceptance and Quality

Conformance Test Results for PCBs

Materials & Processes

Selection, Control, and

Implementation Plan

60 DACA

Materials Identification and

Usage List

30 days prior to PDR

30 days prior to CDR

Updates within 30 days of identification

R

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Foreign Object Debris

Prevention and Control

30 days prior to PDR

Instrument Operations

Configurable Items

Preliminary: 30 days prior to launch

Updates: As needed

123 Initiating GIDEP Alerts Within 30 days of identification R

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

3 DATA ITEM DESCRIPTIONS

3.1 Program Management Plan

DESCRIPTION OF REQUIRED DATA

1. CDRL No.: 001

2. Title: PROGRAM MANAGEMENT PLAN

3. Use: 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.

4. Preparation Information:

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

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.

The Program Management Plan shall address interfaces with the Government and with any

Government Furnished Equipment (GFE) suppliers.

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

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.

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

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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 Coronagraph 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.

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

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.

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

The Program Management Plan shall discuss and illustrate the proposed Coronagraph Mission

Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

The Program Management Plan shall discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

this program (as indicated in your proposed labor hours) are presently on payroll and immediately available for this work.

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

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

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

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

3.2 Weekly Status Reports and Telecon Minutes

1. CDRL No.: 002

2. Title: WEEKLY STATUS REPORTS AND TELECON MINUTES

3. Use: Contract status evaluation.

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.

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.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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

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

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

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

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

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

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

The Weekly Status Report shall contain status on any open contract actions, including Special

Engineering Analyses.

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.

3.3 Monthly and Quarterly Financial Report

1. CDRL No.: 003

2. Title: MONTHLY AND QUARTERLY FINANCIAL REPORT

3. Use: For budget and cost control

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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.

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

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.

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

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

3.4 NASA Property in the Custody of the Contractors

1. CDRL No.: 004

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

2. Title: NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

3. Use: For budget, cost, and property control

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.

3.5 Reserved

3.6 Contractor’s Work Breakdown Structure Diagram and Dictionary

1. CDRL No.: 006

2. Title: CONTRACTOR’S WORK BREAKDOWN STRUCTURE DIAGRAM AND

DICTIONARY

3. Use: To facilitate program planning and control and for financial and technical reporting.

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.

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

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.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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.

3.7 Reserved

3.8 Reserved

3.9 Detailed Schedules

1. CDRL No.: 009

2. Title: DETAILED SCHEDULES

3. Use: 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.

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

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

Phase 2 schedules shall include the fabrication, test, calibration, and delivery of the Proto-Flight

Model (PFM) instruments and their integration to the spacecraft.

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

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

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

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

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.

Detailed schedules shall indicate critical paths.

Detailed schedules shall indicate slack and reserve.

For the build-up of an instrument, an assembly/test flow diagram shall show sequences of fabrication, assembly, integration, and test for assemblies, subsystems and system, and includes quality assurance test points and associated inspection level requirements.

The Detailed Schedules shall include views in Microsoft Project that, as a minimum, summarize the following information:

a) Level 1 Program Schedule - This schedule should include the programmatic milestone/events for the Coronagraph Program reflecting the development of all of the models.

b) Level 2 Model Schedules - These schedules should include programmatic milestones/events for the individual Model from design, manufacturing, integration and test through launch including data on major procurements.

c) Intermediate Logic Networks - These networks should be established for each subsystem or subassembly to the electronic board level. Upon request for the Government, the

Contractor will supply the Government with more information from the detail schedules, which the Contractor maintains.

d) 180-Day Window Report - This report should reflect all the events which are expected to start/complete within 180 days after the current reporting cycle.

e) End Item Float Report - A monthly report should be submitted for each deliverable subsystem or subassembly comparing the current month float to the float of the previous month and explain any changes.

A monthly analysis shall be submitted that will contain a brief description of the current status of each subsystem or subassembly along with descriptions of any existing or potential problems areas.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

3.10 Configuration Management Plan

1. CDRL No.: 010

2. Title: CONFIGURATION MANAGEMENT PLAN

3. Use: 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.

The Configuration Management Plan shall describe the scope, approach, methods, and procedures of the system used to control changes of requirements and design.

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

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

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:

1) Program baseline documentation

2) Technical requirements contained in the product configuration identification, including the following:

i) Form, fit, or function

ii) Performance

iii) Power

iv) Reliability outside stated requirements

v) Weight, balance, moment of inertia

vi) Interface characteristics

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

vii) Hardware and process qualifications

3) Non-technical contractual provisions

i) Fee

ii) Incentives

iii) Cost

iv) Schedule

v) Guarantees or deliveries

4) Other factors

i) Government-furnished property (GFP)

ii) Safety

iii) Electromagnetic characteristics

iv) Deliverable operational, test, or maintenance computer programs

v) 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.

3.11 Configuration Change Requests (CCR) Class I

1. CDRL No.: 011

2. Title: CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

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

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.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

3.12 Reserved

3.13 Safety and Health Reports

1. CDRL No.: 013

2. Title: SAFETY AND HEALTH REPORTS

3. Use: To document any accident, incident, or exposure resulting in fatality, lost-time occupational injury, occupational disease, contamination of property beyond any stated acceptable limits.

The Safety and Health Report shall be per the contractual requirements.

3.14 Reserved

3.15 Responses to Requests for Action

1. CDRL No.: 015

2. Title: RESPONSES TO REQUESTS FOR ACTION

3. Use: To evaluate replies to issues raised during all Instrument Reviews.

Preliminary Responses to Requests for Action (RFAs) may be in any form, such as fax or telecon, to promote coordination with the Project.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

Final Responses to RFAs shall include any supportive material, such as:

a) Engineering reports

b) Sketches

c) Drawing changes

d) Documentation narrative changes

e) Test reports, graphs, etc.

3.16 System Definition Review (SDR) Data Package

1. CDRL No.: 016

2. Title: SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

3. Use: 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.

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

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

The SDR Data Package shall cover requirements for the Coronagraph instrument, Ground

Support Equipment, flight software, ground test software, and processing algorithm.

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

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The SDR Data Package shall identify any Coronagraph technologies that are below Test

Readiness Level (TRL) 6.

3.17 Preliminary Design Review (PDR) Data Package

1. CDRL No.: 017

2. Title: PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

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

The PDR data package shall include Science/Technical Objectives, Requirements, and General

Specification.

The PDR data package shall include responses to action items from previous reviews, including subsystem PDRs.

The PDR data package shall include changes since the last review.

The PDR data package shall address system performance budgets and margins.

The PDR data package shall include processor resource utilization estimates.

The PDR data package shall address mass, power, data rate, commands, Electromagnetic

Compatibility (EMC) / Electromagnetic Interference (EMI).

The PDR data package shall address interface requirements.

The PDR data package shall address mechanical/structural design, analyses, and life tests.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The PDR data package shall address electrical, thermal, and sensor design and analyses.

The PDR data package shall address software requirements, design, and development environment.

The PDR data package shall address Ground Support Equipment design and work flow, and describe how each item will be fabricated, tested and certified when needed.

The PDR data package shall address design verification, test flow and calibration/test plans.

The PDR data package shall address instrument operations.

The PDR data package shall address parts selection, and qualification.

The PDR data package shall address preliminary Failure Modes Effects Analysis

(FMEA)/Failure Modes, Effects, and Criticality Analysis (FMECA); Fault Tree Analysis; and reliability analysis and results.

The PDR data package shall address parts stress analysis.

The PDR Data Package shall address the list of long lead items, and of items that may become obsolete prior to completion of all flight instruments, identify those items that must be procured prior to CDR, and provide a plan for procuring these items and all parts.

The PDR data package shall address contamination requirements and control plan.

The PDR data package shall address safety hazards identified for flight, range, ground hardware and operations.

The PDR data package shall delineate the status of each document required at PDR as to its acceptability for use as is.

The PDR data package shall address open interface items.

The PDR Data Package shall present all program risks and address their mitigation.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The PDR Data Package shall provide the status of all subcontracts and discuss the preliminary design status of critical assemblies and sub-assemblies.

The PDR Data Package shall present a summary of all breadboard and brassboard testing and present the test results.

The PDR Data Package shall present the development status of sub-assembly engineering units, and available test data.

The PDR Data Package shall address mission assurance to be imposed including parts and materials usage as well and workmanship standards imposed.

The PDR Data Package shall address software assurance process.

The PDR data package shall contain information to cover the Coronagraph ground algorithm design.

The PDR Data Package shall demonstrate that all Coronagraph technologies have achieved a

TRL 6 or higher.

3.18 Critical Design Review (CDR) Data Package

1. CDRL No.: 018

2. Title: CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE

3. Use: To present the Flight Equipment and GSE design and operation and S/C interface aspects, to demonstrate that all related manufacturing documentation, processes and fixtures are in place before hardware manufacture begins, and to demonstrate that the design meets all performance requirements.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The CDR data package shall include responses to action items from previous reviews, including subsystem CDRs.

The CDR data package shall include changes since the last design review.

The CDR Data Package shall address the procurement status of long lead items and Electrical, Electronic, and Electromechanical (EEE) parts.

The CDR Data Package shall address manufacturing flow, and the status of manufacturing and assembly drawings, bill of materials, etc.

The CDR Data Package shall address manufacturing procedures.

The CDR Data Package shall address mission assurance product checkpoints and evaluation criteria.

The CDR data package shall address the Coronagraph ground algorithm design and development.

The CDR Data Package shall address standard applicable in-house processes.

The CDR Data Package shall address special/unique tooling and fixtures.

The CDR Data Package shall address facilities required for manufacturing.

The CDR Data Package shall address personnel resources (time phased).

The CDR Data Package shall address the delivery schedules for flight instruments and GSE.

The CDR Data Package shall provide status of:

a) Performance specification (subsystems and GSE)

b) Block diagram and description of operation (instrument and GSE)

c) Schematic and logic diagrams (including waveforms, and timing)

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

d) Mechanical configuration drawings

e) Test procedures

f) Calibration procedures

g) GSE development

The CDR data package shall address detailed analysis from FMEA/FMECA, fault tree analysis, and reliability analysis.

The CDR data package shall address parts stress analysis.

The CDR Data Package shall address worst-case analyses of:

a) Electrical circuits

b) Tolerance and tolerance sensitivity analysis (including thermal and mechanical considerations)

The CDR Data Package shall address stress analyses using NASTRAN, or compatible tool, with hand stress analysis verification.

The CDR Data Package shall address the structural frequency and other dynamic analyses

(including shock, sine sweep, and random, at a minimum).

The CDR Data Package shall address the thermal analysis.

The CDR Data Package shall address end-to-end system performance and margins.

The CDR Data Package shall address mass, power, data rate, commands, EMI/EMC.

The CDR data package shall include processor resource utilization estimates.

The CDR Data Package shall address test plans (including all environmental and calibration tests).

The CDR Data Package shall address manufacturing considerations.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The CDR Data Package shall address maintainability considerations.

The CDR Data Package shall address materials and processes lists.

The CDR Data Package shall provide a summary of deviations/waivers.

The CDR Data Package shall address contamination control and monitoring considerations.

The CDR Data Package shall address spares program.

The CDR Data Package shall address system safety hazards analyses.

a) Hazards identification matrix

b) Single point failure summaries

c) Risk assessment rationale

The CDR data package shall address open interface items and the status of the IDD.

The CDR Data Package shall present any additional test results from breadboard and brassboard testing.

The CDR Data Package shall present the test data from any engineering model.

The CDR Data Package shall address the status of all program risks and their mitigation.

The CDR Data Package shall address the status of all subcontract design activity and schedule for delivery of flight hardware, and demonstrate that designs are complete and have been adequately reviewed.

3.19 Pre-Environmental Review (PER) Data Package

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

1. CDRL No.: 019

2. Title: PRE-ENVIRONMENTAL REVIEW (PER) DATA PACKAGE

3. Use: Presents the description and results of the Pre-Environmental Test program, and demonstrates readiness for environmental testing.

The PER Data Package shall include status of action items generated at prior reviews.

The PER Data Package shall include analyses and reports required at the review.

The PER Data Package shall include test and integration program descriptions and results.

The PER Data Package shall include Non-Conformance report summaries including status of actions and rationales for closure.

The PER Data Package shall include as-built documentation summary.

The PER Data Package shall include results of the functional and interface tests.

The PER Data Package shall include malfunctions and corrective actions.

The PER Data Package shall include comparison of measured performance with requirements and discussion of the effect of any variance and waivers.

The PER Data Package shall include mission operation constraints.

The PER Data Package shall include contamination avoidance requirements.

The PER Data Package shall include safety requirements.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The PER Data Package shall include list of spares for flight equipment and GSE.

The PER Data Package shall include review of instrument handling procedures.

The PER Data Package shall include interface concerns, problems and solutions.

The PER Data Package shall include orbital operations plans.

The PER Data Package shall include end-item data packages up to this point of the program

(submit a summary of the content prior to review and have package available for inspection at review).

a) As-built configuration list

b) Hardware parts lists

c) Hardware materials and processes lists

d) Test Log Book (including total operating time and cycle records)

e) Open item lists (including reasons for being open)

f) Safety compliance data package

g) Limited life items listings and status

h) Critical parameters trend data

i) Final comprehensive performance test results (pre-environmental test results)

The PER Data Package shall discuss the compatibility of instrument with observatory flight support equipment, ground support equipment and operational ground equipment.

The PER Data Package shall include a description of the planned environmental testing.

The PER Data Package shall address the availability and readiness of facilities and GSE required for environmental testing.

The PER Data Package shall address the readiness of environmental test plans and procedures.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

3.20 Pre-Storage/Pre-Ship Review Data Package

1. CDRL No.: 020

2. Title: PRE-STORAGE/PRE-SHIP REVIEW DATA PACKAGE

3. Use: To evaluate system performance during qualification or acceptance testing, and evaluate readiness to ship from contractor.

The Pre-Storage Review Data Package shall address responses to action items generated at prior reviews.

The Pre-Storage Review Data Package shall address the solutions to all problems encountered during the environmental test and validation program and the solution rationale.

The Pre-Storage Review Data Package shall address any rework/replacement of hardware, regression testing, or test plan changes should be highlighted during the test flow discussions.

The Pre-Storage Review Data Package shall address compliance with the test verification matrix.

The Pre-Storage Review Data Package shall address measured test margins versus design estimates.

The Pre-Storage Review Data Package shall address qualification/acceptance temperature margins.

The Pre-Storage Review Data Package shall address any data that has been trended to identify compliance with specification, indicating a change or drift to the trend.

The Pre-Storage Review Data Package shall address total failure-free operating time of the item.

Check the SWFO CM tool Server at https://swfowc ndc.nasa.gov to verify that this is the correct version prior to use.

The Pre-Storage Review Data Package shall address “could-not-duplicate failures” along with assessment of the problem and the residual risk that may be inherent in the item.

The Pre-Storage Review Data Package shall address project assessment of any residual risk.

The Pre-Storage Review Data Package shall provide an update from CDR on shipping containers, monitoring/transportation/control plans.

The Pre-Storage Review Data Package shall address ground support equipment…