Attachment B-418-XO-SCCDRL-0053_V_1_0_final.pdf

Effective Date: September 22, 2023 418-XO-SCCDRL-0053 Responsible Organization: GeoXO Flight Project/Code 418 Baseline 1.0

To verify the correct version of this document, please contact the GeoXO Series Configuration Management Office.

Geostationary Extended Observations (GeoXO)

Spacecraft (SC) Contract Data Requirements List (CDRL)

Signature/Approval Page

Prepared by:

Email approved by:

09/29/2023

John J. Loiacono GeoXO Flight Project, Management Support NASA GSFC, Code 418

Date

Reviewed by:

Electronically approved by:

09/20/2023

Steven W. Bidwell Date GeoXO Flight Project, Mission Systems Engineer

Concurred by:

Electronically approved by:

09/22/2023

Michelle P. Rizzo Date GeoXO Flight Project, Observatory Manager

Approved by:

Electronically approved by Christopher Wheeler for:

09/22/2023

Candace C. Carlisle Date GeoXO Flight Project Manager

/GeoXO Flight Project Spacecraft

SCCDRL

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements List (CDRL)

Version: 1.0 Printed by: rkhoover Printed on: Friday, September 29, 2023

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

Contents

1 1INTRODUCTION

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

1.2 3Applicable Documents

1.3 3Reference Documents

2 4Contract Data Requirements List

3 24Data Item Descriptions

3.1 24Project Management

3.1.1 24PM-01 Project Management Plan

3.1.2 26PM-02 Weekly Status Reports and Telecon Minutes

3.1.3 27PM-03 Risk Management Plan

3.1.4 28PM-04 Configuration Management Plan

3.1.5 29PM-05 Configuration Change Requests, Deviations, and Waivers

3.1.6 30PM-06 Project Management Status Reviews – Technical (PMSR-T), and Business

(PMSR-B)

3.1.7 33PM-07 Spares Plan and List

3.1.8 34PM-08 Digital Image and Video Records

3.1.9 36PM-09 Document Tree

3.1.10 36PM-10 Engineering Development Unit(s) (EDUs) Activities Report

3.1.11 36PM-11 GeoXO Data Books

3.1.12 37PM-12 Early Launch Contingency Plan

3.2 38Resource Management

3.2.1 38RM-01 Earned Value Management (EVM) Plan

3.2.2 39RM-02 Financial Reports

3.2.3 40RM-03 Integrated Program Management Data and Analysis Report (IPMDAR)

3.2.4 50RM-04 Contractor Work Breakdown Structure (CWBS) and CWBS Dictionary

3.2.5 52RM-05 RESERVED

3.2.6 52RM-06 Unit Cost Report

3.2.7 52RM-07 Integrated Baseline Review (IBR) Package

3.3 53System Review

3.3.1 53SR-01 System Requirements Review (SRR) / System Definition Review (SDR)

Data Package

3.3.2 58SR-02 Preliminary Design Review (PDR) Data Package

3.3.3 62SR-03 Critical Design Review (CDR) Data Package

3.3.4 67SR-04 Pre-Environmental Review (PER) Data Package

Project: GeoXO Flight Project Spacecraft Module: SCCDRL Baseline Version: 1.0

Contents ii

3.3.5 70SR-05 Pre-Storage/Pre-Ship Review (PSR) Data Package

3.3.6 72SR-06 Design Modification Review (DMR) Data Package

3.3.7 74SR-07 Component, Subassembly and Subsystem Review Data Packages

3.4 75Systems Engineering

3.4.1 75SE-SPEC-01-x Spacecraft and Satellite Specifications

3.4.1.1 75SE-SPEC-01-1 Satellite Requirements Specification

3.4.1.2 75SE-SPEC-01-2 Spacecraft Detailed Design Specification

3.4.1.3 76SE-SPEC-01-3 Electrical Schematics and Block Diagrams

3.4.1.4 77SE-SPEC-01-4 Fault Management Design Description Document

3.4.1.5 78SE-SPEC-01-5 Drawing Tree

3.4.1.6 78SE-SPEC-01-6 Spacecraft Environmental Verification Specification

3.4.2 79SE-Plans-02-x Spacecraft Plans

3.4.2.1 79SE-PLAN-02-1 Systems Engineering Management Plan

3.4.2.2 82SE-PLAN-02-2 System Performance Verification and Compliance Plan

3.4.2.3 84SE-PLAN-02-3 Contamination Control Plan

3.4.2.4 86SE-PLAN-02-4 Electrostatic Discharge Control Plan

3.4.2.5 86SE-PLAN-02-5 Radiation Effects Control Plan

3.4.2.6 87SE-PLAN-02-6 Electromagnetic Interference (EMI)/ Electromagnetic Compatibility

(EMC) Plan

3.4.2.7 88SE-PLAN-02-7: On-Orbit Electrostatic Discharge Control and Verification Plan

3.4.2.8 89SE-PLAN-02-8 Trend Analysis Plan

3.4.2.9 90SE-PLAN-02-9 Individual Test Plans

3.4.2.10 91SE-PLAN-02-10 Life Test Plan

3.4.2.11 92SE-PLAN-02-11 Engineering Development Unit(s) Development and Test Plan

3.4.3 92SE-RPT-3-x Spacecraft Reports

3.4.3.1 92SE-RPT-03-1 Spacecraft Contamination Model and Report

3.4.3.2 94SE-RPT-03-2 Radiation Shielding and Dose Analysis Report

3.4.3.3 94SE-RPT-03-3: Engineering Analysis Reports (EAR)

3.4.3.4 95SE-RPT-03-4 Trend Reports

3.4.3.5 95SE-RPT-03-5 Test Reports

3.4.3.6 97SE-RPT-03-6 Satellite Level Test Reports

3.4.3.7 100SE-RPT-03-7 Life Test Report(s) for Mechanisms

3.4.3.8 100SE-RPT-03-8 System Performance Verification Reports

3.4.3.9 101SE-RPT-03-9 Spacecraft Assembly and Integration Drawings

3.4.4 101SE-ICD-04-x Spacecraft Interface Control Documents (ICDs)

3.4.4.1 101SE-ICD-04-1 Spacecraft to Instrument ICDs

3.4.4.2 103SE-ICD-04-2 Spacecraft Communications Services ICDs

3.4.4.3 104SE-ICD-04-3 Space to Ground ICD

Contents iii

3.4.5 106SE-INR-05-x Spacecraft Image Navigation and Registration (INR)

3.4.5.1 106SE-INR-05-1 INR Analysis and Test Plan

3.4.5.2 107SE-INR-05-2 INR Analysis and Test Report

3.4.6 108SE-MECH-06-x Spacecraft Mechanical

3.4.6.1 108SE-MECH-06-1 Fields-of-View (FOV) Analysis Report

3.4.6.2 109SE-MECH-06-2 Solid Model

3.4.6.3 110SE-MECH-06-3 Critical Mechanical Clearance List and Model

3.4.6.4 110SE-MECH-06-4 Alignment Plan

3.4.6.5 110SE-MECH-06-5 Alignment Report

3.4.6.6 111SE-MECH-06-6 Stress Analysis Reports

3.4.6.7 112SE-MECH-06-7 Structural and Mechanical Subsystem Performance Analysis

3.4.6.8 113SE-MECH-06-8 Mechanisms Performance Analysis Report

3.4.6.9 114SE-MECH-06-9 Structural Math Models and Report

3.4.6.10 115SE-MECH-06-10 Mass Properties Report

3.4.7 117SE-THER-07-x Spacecraft Thermal

3.4.7.1 117SE-THER-07-1 Detailed and Reduced Integrated Satellite Thermal Model and

3.4.7.2 121SE-THER-07-2 On-orbit Thermal Performance Report

3.4.7.3 122SE-THER-07-3 Thermal Environment for GFP Instruments

3.4.8 124SE-GNC-08-x Spacecraft Guidance, Navigation and Control (GN&C)

3.4.8.1 124SE-GNC-08-1 GN&C Algorithm Document

3.4.8.2 124SE-GNC-08-2 GN&C Models

3.4.9 125SE-CDH-09-x Spacecraft C&DH

3.4.9.1 125SE-CDH-09-1 Communications Security (COMSEC) Security Plan

3.4.10 126SE-COMM-10-x Spacecraft Communications

3.4.10.1 126SE-COMM-10-1 Communications Subsystem Link Performance and Budget Report

3.4.10.2 128SE-COMM-10-2 High Power RF Test and Analysis Report

3.4.10.3 129SE-COMM-10-3 Communications Subsystem Information Required for

International Telecommunication Union (ITU) and National Telecommunications and Information Administration (NTIA) Filings

3.4.10.4 131SE-COMM-10-4 Communications Subsystem Test Data Reports

3.4.11 132SE-POWR-11-x Spacecraft Power

3.4.11.1 132SE-POWR-11-1 Power Subsystem Design and Performance Analyses

3.4.11.2 137SE-POWR-11-2 Battery Specification

3.4.11.3 141SE-POWR-11-3 Battery Design and Performance Analysis Report

3.4.11.4 144SE-POWR-11-4 Battery Cell Acceptance and Cell Qualification Test Plan

3.4.11.5 144SE-POWR-11-5 Battery Acceptance, Qualification, and Life Test Plan

3.4.11.6 145SE-POWR-11-6 Battery Handling, Storage, and Transportation Plan

3.4.11.7 145SE-POWR-11-7 Battery Cell and Battery Test Data & Battery Cell Fabrication Data

Contents iv

3.4.11.8 146SE-POWR-11-8 Solar Panel Qualification and Solar Panel and Array Acceptance Test Plan

3.4.11.9 148SE-POWR-11-9 Power Profile Report

3.4.12 148SE-PROP-12-1-x Spacecraft Propulsion

3.4.12.1 148SE-PROP-12-1 Propulsion Manufacturing Plans

3.4.12.2 149SE-PROP-12-2 Propellant/Pressurant Loading Plan

3.4.12.3 149SE-PROP-12-3 Propulsion Subsystem Analyses and Data Reports

3.4.13 150SE-FPGA-13-x Spacecraft Field Programmable Gate Arrays (FPGAs)

3.4.13.1 150SE-FPGA-13-1 FPGAs Development Plan

3.4.13.2 151SE-FPGA-13-2 FPGAs Design Data Package

3.4.14 152SE-ROBOSERV-14-x Robotic Servicing

3.4.14.1 152SE-ROBOSERV-14-1 Robotic Servicing Assumptions Document

3.5 153Software

3.5.1 153SW-01 Software Management Plan

3.5.2 155SW-02 Software Maintenance Plan

3.5.3 156SW-03 Software Requirements Specification

3.5.4 157SW-04 Software Preliminary Design Review (SWPDR) Data Package

3.5.5 158SW-05 Software Critical Design Review (SWCDR) Data Package

3.5.6 159SW-06 Software Design Document

3.5.7 160SW-07 Software Test Plan

3.5.8 162SW-08 Flight Software Test Procedures

3.5.9 162SW-09 Flight Software Test Readiness Review (SWTRR) Data Package

3.5.10 163SW-10 Flight Software Test Report

3.5.11 164SW-11 Software Acceptance Review (SWAR) Data Package

3.5.12 165SW-12 Software Delivery Package

3.6 166Integration and Test

3.6.1 166I&T-01: Test Data Analysis System (TDAS) Training and Operations Package

3.6.2 167I&T-02 Subsystem Integration and Test (I&T) Plans

3.6.3 168I&T-03 Satellite Integration and Test (I&T) Plan

3.6.4 169I&T-04 Satellite Integration and Test (I&T) Procedures

3.6.5 170I&T-05 Transportation and Handling Plan

3.6.6 171I&T-06 Ground Storage Plan

3.7 172Launch Operations

3.7.1 172LO-01 Satellite Mission Insignia

3.7.2 172LO-02 Satellite Launch Site Integration Plan (LSIP)

3.7.3 174LO-03 Satellite Launch Commit Criteria (SLCC)

3.8 175Mission Operations

3.8.1 175OPS-01 Satellite Telemetry and Command Database

Contents v

3.8.2 176OPS-02 Satellite Telemetry and Command Handbooks

3.8.3 178OPS-03 Spacecraft Operations Handbook (SOH)

3.8.4 184OPS-04 Spacecraft Operations Training Package

3.8.5 185OPS-05 Spacecraft Operations Configurable Items

3.8.6 185OPS-06 Spacecraft Post Launch Test Plan and Procedures

3.8.7 186OPS-07 Spacecraft Post Launch Test Reports

3.8.8 187OPS-08 Spacecraft On-Orbit Anomaly Reports

3.8.9 187OPS-09 Operations Database

3.9 188Simulators

3.9.1 188SIM-01 Operations, Test and Maintenance Manual for the Spacecraft Hardware

Simulator (SHS)

3.9.2 189SIM-02 Operations, Test and Maintenance Manual for the Spacecraft Software

Simulator (S3)

3.9.3 189SIM-03 Spacecraft Simulator to Instrument Simulators Interface Control

Document (ICD)

3.9.4 190SIM-04 Operations, Test and Maintenance Manual for the Spacecraft to

Instrument Interface Simulator (SIIS)

3.10 190Mission Assurance

3.10.1 190System Safety and Mission Assurance

3.10.1.1 190MA 01-1 Mission Assurance Requirements Compliance Matrix

3.10.1.2 191MA 01-2 Suppliers List

3.10.2 191Quality Management System

3.10.2.1 192MA 02-1 Non-Conformance Report: Material Review Board (MRB) and Failure

Review Board (FRB)

3.10.2.2 193MA 02-2 Inputs for Orbital Debris Assessment Report (ODAR) and End of Mission

Plan (EOMP)

3.10.3 193System Safety Deliverables

3.10.3.1 194MA 03-1 System Safety Program Plan

3.10.3.2 195MA 03-2 Safety Requirements Compliance Checklist

3.10.3.3 195MA 03-3 Safety Data Package (SDP)

3.10.3.4 197MA 03-4 Operations Hazard Analysis and Verification Tracking Log

3.10.3.5 198MA 03-5 Hazardous Procedures for Payload I&T and Pre-Launch Processing

3.10.3.6 199MA 03-6 Pre-Mishap Plan and Mishap Reports

3.10.4 201Reliability Deliverables

3.10.4.1 201MA 04-1 Reliability Program Plan

3.10.4.2 201MA 04-2 Failure Modes, Effects, and Criticality Analysis (FMECA) and Critical

Items List (CIL)

3.10.4.3 202MA 04-3 Fault Tree Analysis (FTA) Report

3.10.4.4 203MA 04-4 Parts Stress Analysis Report

3.10.4.5 204MA 04-5 Worst Case Analysis Report

Contents vi

3.10.4.6 204MA 04-6 Reliability Assessments and Predictions

3.10.4.7 205MA 04-7 Limited Life Items List (LLIL)

3.10.5 206Software Assurance Deliverables

3.10.5.1 206MA 05-1 Software Assurance Plan

3.10.6 206Workmanship Deliverables

3.10.6.1 206MA 06-1 Printed Circuit Board (PCB) Procurement Specification

3.10.6.2 208MA 06-2 Printed Circuit Board (PCB) Coupon Evaluation Reports and Lot

Acceptance and Quality Conformance Testing Results for PCBs

3.10.7 209EEE Parts Deliverables

3.10.7.1 209MA 07-1 EEE Parts Control Plan

3.10.7.2 210MA 07-2 Master EEE Parts List

3.10.8 211Materials, Processes and Lubrication Requirements

3.10.8.1 211MA 08-1 Materials and Processes Selection, Control, and Implementation Plan

(MPSCIP)

3.10.8.2 214MA 08-2 Materials Usage Agreement (MUA)

3.10.8.3 214MA 08-3 Materials Identification and Usage List (MIUL)

4 216APPENDIX A: Acronym List

Contents vii

Page 1 of 222 Printed Friday, September 29, 2023

ID

SCCDRL1

SCCDRL2

SCCDRL3

SCCDRL4

Object Number

1.0-1

1.1

1.1.0-1

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

1 INTRODUCTION

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable Data to be provided by the GeoXO Spacecraft (SC) Contractor. “Spacecraft” as referred to in this document applies to SC. Section 1.1 includes definitions and instructions for distribution. Section 2 presents the CDRL item by item with due dates.

Section 3.0 provides the Data Item Descriptions (DIDs), a description of each item and describes use, and Preparation Information.

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 Table in Section 2.

a) DUE DATE:

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

2) CDR, PER, PSR, etc. Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc., respectively.

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

4) As Directed. Per direction by the Contracting Officer (CO).

5) Monthly. Monthly by the 15th of each month or as required or as modified by the CO.

6) Weekly. With weekly status reports by Monday 12 noon ET or as modified by CO.

7) L. Launch Date.

8) DACA. Days after contract award. Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

9) NLT: No Later Than

10) ATP: Authorization to Proceed

b) MATURITY:

1) Preliminary: The first submission of an item. Applies to milestone deliveries. To be completed with available information as of the time of preparation for the due date.

2) Initial: The first submission of an item for deliveries that are periodic – weekly, monthly, etc. To be updated with available information as of the time of preparation for the due date.

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

4) Baseline: The complete thorough submission of an item used as the basis or starting point for the design, procurement, testing, etc.

5) Final: The complete thorough submission of an item including any negotiated changes and other updates. This does not preclude updating later.

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

Page 2 of 222 Printed Friday, September 29, 2023

ID

SCCDRL4

SCCDRL5

SCCDRL6

SCCDRL7

SCCDRL8

SCCDRL9

SCCDRL10

SCCDRL11

SCCDRL12

Object Number

1.1.0-1

1.1.0-2

1.1.0-3

1.1.0-4

1.1.0-5

1.1.0-6

1.1.0-7

1.1.0-8

1.1.0-9

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

Government prior to use and within the time period specified in the "Due Date" column of the Contract Data Requirement List in Section 2 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 Contract Data Requirement List in Section 2 of this document for the purpose of determining current program status, progress, and future planning requirements.

The following requirements terminology is used throughout this document:

a) The use of “shall” designates a requirement that must be met.

b) The use of “will” designates a statement of fact or intention of the

Government.

c) The use of “may” designates that permission has been granted by the

Government.

The Contractor shall transmit items with an “As Generated” due date that are critical to schedule, performance, or interface to GSFC within 48 hours of formal release.

Unless specified otherwise, 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 Contract Data Requirement List in Section 2 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 30 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 the GeoXO portal unless otherwise noted in the Contract Data Requirement List in Section 2 of this document.

Page 3 of 222 Printed Friday, September 29, 2023

ID

SCCDRL13

SCCDRL14

SCCDRL15

SCCDRL16

SCCDRL17

Object Number

1.1.0-10

1.2

1.2.0-1

1.3

1.3.0-1

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

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

a) Text Documents: PDF (searchable) or MSWord.

b) Presentations: PDF (searchable) or PowerPoint.

c) Spreadsheets: Microsoft Excel.

d) Database: Unless specified otherwise, delimited ASCII files accompanied with database schema document defining tables and entries.

e) Schedules: MS Project compatible and PDF.

f) Schematics and Drawings: PDF.

g) Photographs: JPEG or current industry standard.

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

i) System Specifications in DOORS (DPA, DMA updates) and PDF.

1.2 Applicable Documents

The following documents form a part of this specification to the extent specified herein:

Applicable Documents are in each individual Data Item Description (DID).

1.3 Reference Documents

The following documents contain information relating to the work required but which do not constitute requirements:

Reference Documents are in each individual DID.

Page 24 of 222 Printed Friday, September 29, 2023

ID

SCCDRL20

SCCDRL21

SCCDRL22

SCCDRL23

SCCDRL24

SCCDRL25

SCCDRL26

SCCDRL27

SCCDRL28

SCCDRL29

SCCDRL30

SCCDRL31

SCCDRL32

SCCDRL33

Object Number

3.1

3.1.1

3.1.1.0-1

3.1.1.0-2

3.1.1.0-3

3.1.1.0-4

3.1.1.0-5

3.1.1.0-6

3.1.1.0-7

3.1.1.0-8

3.1.1.0-9

3.1.1.0-10

3.1.1.0-11

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

3 Data Item Descriptions

3.1 Project Management

3.1.1 PM-01 Project Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-01

2. Title: Project Management Plan

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

4. Preparation Information:

General:

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

The Project Management Plan shall address interfaces with the Government and with any Government Furnished Property (GFP) suppliers.

The Project 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 Project Management Plan shall describe the concept of the nature of the tasks and related potential problems. Discuss the approach to problem avoidance and/or solution.

The Project Management Plan shall define the technical, schedule and cost control plan and describe management techniques to be employed in minimizing program costs and schedule impacts for all activities, including controls to be exercised over Subcontractors and suppliers.

The Project Management Plan shall describe make/buy strategies, acquisition plans, sparing philosophy, Project dependencies, facility requirements, internal review strategies and plans, significant work elements on critical paths, long-lead items.

The Project Management Plan shall identify how Contractor’s risk management system and processes are integrated into the daily management, decision making, and strategic direction of the Project and how you foresee Government participation in that process.

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

The Project Management Plan shall identify additional definition of spacecraft interfaces and mission design and the need date.

Page 25 of 222 Printed Friday, September 29, 2023

ID

SCCDRL35

SCCDRL36

SCCDRL37

SCCDRL38

SCCDRL39

SCCDRL40

SCCDRL41

SCCDRL42

SCCDRL43

SCCDRL44

SCCDRL45

Object Number

3.1.1.0-12

3.1.1.0-13

3.1.1.0-14

3.1.1.0-15

3.1.1.0-16

3.1.1.0-17

3.1.1.0-18

3.1.1.0-19

3.1.1.0-20

3.1.1.0-21

3.1.1.0-22

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

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

The Project Management Plan shall describe how and where the program will operate during all phases of the contract.

Organization:

The Project Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the Project 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) How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.

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

c) The authority of the Program Manager relative to other ongoing programs and applicable support organizations within the company structure.

d) Discuss the program manager’s control over essential resources and functions necessary to accomplish the work.

The Project Management Plan shall discuss the availability of the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours).

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

Mission Assurance:

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

The Project Management Plan shall state the independence of the system safety/quality assurance functions.

Schedule:

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

Page 26 of 222 Printed Friday, September 29, 2023

ID

SCCDRL46

SCCDRL47

SCCDRL48

SCCDRL49

SCCDRL50

SCCDRL51

SCCDRL52

SCCDRL53

SCCDRL54

SCCDRL55

SCCDRL56

SCCDRL57

SCCDRL58

SCCDRL59

SCCDRL60

Object Number

3.1.1.0-23

3.1.1.0-24

3.1.1.0-25

3.1.1.0-26

3.1.1.0-27

3.1.1.0-28

3.1.1.0-29

3.1.1.0-30

3.1.1.0-31

3.1.2

3.1.2.0-1

3.1.2.0-2

3.1.2.0-3

3.1.2.0-4

3.1.2.0-5

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

The Project Management Plan shall explain/describe the schedule administration/control.

The Project Management Plan shall explain the internal review cycle of the scheduling process.

The Project Management Plan shall explain how subcontract schedules maintained and reported in the master schedule.

The Project Management Plan shall explain how internal audits/reviews ensure that scheduling data reported to the Government accurately reflects the work status.

Knowledge Management:

The Project Management Plan shall describe how lessons learned from spacecraft development, integration, and test will be captured.

The Project Management Plan shall describe how training will be performed to convey lessons learned as they apply to the development, integration, and test of future spacecraft.

The Project Management Plan shall describe how lessons learned will be captured and applied to Subcontractor development of component, subassemblies, and subsystems.

The Project Management Plan shall describe the overall training plan for project personnel.

3.1.2 PM-02 Weekly Status Reports and Telecon Minutes

DATA ITEM DESCRIPTION

1. CDRL No.: PM-02

2. Title: Weekly Status Reports and Telecon Minutes

3. Use: Program status reviews; system, subsystem, and assembly packaging evaluations; and trouble shooting. This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

4. Preparation Information:

The Weekly Status Report shall address the work completed during the week against the work planned.

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

The Weekly Status Report shall contain Program Management (PM), Systems Engineering (SE), engineering disciplines, Integration and Test (I&T), Software (SW), and Mission Assurance (MA) status.

The PM section shall indicate any actual or anticipated slip in schedule, long lead items status, and status on any red risk item.

Page 27 of 222 Printed Friday, September 29, 2023

ID

SCCDRL61

SCCDRL62

SCCDRL63

SCCDRL64

SCCDRL65

SCCDRL66

SCCDRL67

SCCDRL68

SCCDRL69

SCCDRL70

SCCDRL71

SCCDRL72

Object Number

3.1.2.0-6

3.1.2.0-7

3.1.2.0-8

3.1.2.0-9

3.1.2.0-10

3.1.3

3.1.3.0-1

3.1.3.0-2

3.1.3.0-3

3.1.3.0-4

3.1.3.0-5

3.1.3.0-6

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

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

The Weekly Status Report shall contain telecon minutes for the previous week's weekly telecon and all technical meetings.

The Weekly Status Report shall contain Action Item Status and contain telecon minutes from the previous week's weekly telecon.

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/Task Orders.

3.1.3 PM-03 Risk Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-03

2. Title: Risk Management Plan

3. Use: The Risk Management Plan is the basis for identifying and managing all performance, reliability, schedule, cost, and safety risks on the Contractor’s Project. 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.

4. Preparation Information:

The Risk Management Plan shall describe Contractor’s process for Risk Identification, Risk Analysis, Risk Handling and Risk Monitoring.

This Risk Management Plan shall include a process for tracking and reporting risk status and changes.

The Risk Management Plan shall clearly describe:

a) Overview of the risk management process.

b) Organizational responsibilities.

c) Risk identification approach.

d) Risk mitigation planning.

e) Interface of risk management to schedule and financial/cost management.

f) Risk tracking/documentation.

g) Risk management list reporting.

The Risk Management Plan shall include risks associated with hardware and software (e.g., technical challenges, new technology qualification, etc.), COTS items, system safety, performance, cost, and schedule (i.e., programmatic risks).

The Risk Management Plan shall identify which tools and techniques will be used to manage the risks.

Page 28 of 222 Printed Friday, September 29, 2023

ID

SCCDRL73

SCCDRL74

SCCDRL75

SCCDRL76

SCCDRL78

SCCDRL79

SCCDRL80

SCCDRL81

Object Number

3.1.3.0-7

3.1.3.0-8

3.1.3.0-9

3.1.3.0-10

3.1.4

3.1.4.0-1

3.1.4.0-2

3.1.4.0-3

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

The Risk Management Plan shall use the GSFC risk 5x5 definitions as described in the GSFC Risk Matrix Standard Scale Figure.

The Risk Management Plan shall form risk statements in the format as expressed in the following: “Given the [condition], there is a possibility that [consequence] will occur with the result that [outcome].”

Reference Documents:

1. GPR 7120.4D, Risk Management

2. NPR 8000.4C, Agency Risk Management Procedural Requirements

Figure 1: GSFC Risk Matrix Standard Scale (GPR 7120.4D, Table 3)

3.1.4 PM-04 Configuration Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-04

2. Title: Configuration Management Plan

3. Use: Defines the Contractor’s configuration management system

(including policies and procedures) that will be implemented for the configured hardware and documentation.

4. Preparation Information:

The Contractor’s configuration management plan shall be prepared in accordance with the Contractor’s standards.

The Configuration Management Plan shall describe in detail all hardware configuration management processes, methods, and procedures the Contractor intends to use.

Page 29 of 222 Printed Friday, September 29, 2023

ID

SCCDRL82

SCCDRL83

SCCDRL84

SCCDRL85

SCCDRL86

SCCDRL87

SCCDRL88

Object Number

3.1.4.0-4

3.1.4.0-5

3.1.5

3.1.5.0-1

3.1.5.0-2

3.1.5.0-3

3.1.5.0-4

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

The Configuration Management Plan shall describe how the Contractor plans to:

a) Accomplish configuration management,

b) Achieve consistency between product definition, the product’s configuration, and the configuration management records, and

c) Maintain configuration management throughout the applicable phases of the products’ life cycle.

The Configuration Management Plan shall describe the Contractor’s approach, methodology, and application of configuration management principles and practices, including:

a) General product definition and scope.

b) Description of configuration management activities and procedures for each of the following configuration management functions:

1) Configuration planning and management.

2) Configuration identification.

3) Configuration Change management.

4) Configuration status accounting.

5) Configuration verification and audit.

6) Configuration management of digital data.

c) Organization, roles, responsibilities, and resources.

d) Definition of terms.

e) Programmatic and organizational interfaces.

f) Subcontract flow down of configuration management.

3.1.5 PM-05 Configuration Change Requests, Deviations, and

Waivers

DATA ITEM DESCRIPTION

1. CDRL No.: PM-05

2. Title: Configuration Change Requests, Deviations and Waivers

3. Use: To facilitate the orderly processing of engineering change requests to specifications or requirements, changes to plans or procedures, specification deviations, waivers, to appropriate level of review, classification, and approval authority for disposition.

4. Preparation Information:

Consistent with the Contractor’s Configuration Management Plan (CMP), the Contractor shall prepare, and submit Configuration Change Requests (CCR) for Government review.

CCRs shall be either Class I or Class II.

In addition to the change description, the CCR shall contain sufficient information in the form of attachments, drawings, test results, etc., to allow the Government to evaluate the total impact of the proposed change. The Government Contracting Officer may direct the Contractor to prepare CCRs under the “Changes” clause of the contract (52.243-2).

Page 30 of 222 Printed Friday, September 29, 2023

ID

SCCDRL89

SCCDRL90

SCCDRL91

SCCDRL92

SCCDRL93

SCCDRL94

SCCDRL95

SCCDRL96

Object Number

3.1.5.0-5

3.1.5.0-6

3.1.5.0-7

3.1.5.0-8

3.1.6

3.1.6.0-1

3.1.6.0-2

3.1.6.0-3

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

A Class I CCR is a change that:

a) Affects any Government Contract requirement, specification, or interface requirement.

b) Affects schedules of end item deliverables to the Government.

c) Impacts Government Furnished Property.

d) Affects configuration to the extent that changes would be required to prior deliverables in order to maintain specified performance.

e) Creates a new Single Point Failure possibility.

A change may be classified Class II when it does not fall within the definition of a Class I change as given above. Examples of Class II changes are:

a) A change in documentation only (for example, correction of errors, addition or clarifying notes or views).

b) A minor change in hardware (for example, substitution with an approved alternative material) which does not affect any item listed under Class I changes.

c) Drawing changes that do not affect a baseline, interface, etc.

Class II changes normally do not require Government CCB approval unless they are written against Government CM-controlled documents.

Waivers and Deviations are considered CCRs and will follow the CCR approval process.

3.1.6 PM-06 Project Management Status Reviews – Technical

(PMSR-T), and Business (PMSR-B)

DATA ITEM DESCRIPTION

1. CDRL No.: PM-06

2. Title: Project Management Status Reviews – Technical (PMSR-T) and

Business (PMSR-B)

3. Use: To evaluate contract status. These reports will be used to provide an opportunity for face-to-face discussions between the Contractor and the Government regarding Project status, plans, and issues. The Contractor provides a management level review of technical, schedule, financial, and programmatic activities to the Government. These reviews will typically address the topics listed below as required. Addition of special topics will be coordinated between Government and Contractor prior to each meeting.

4. Preparation Information:

The Project Management Status Review (PMSR) shall include all aspects of the contract effort. The final scheduled monthly Project management review will occur the month following the delivery of the last spacecraft under contract.

The PMSR-T data package shall address the following:

a) Program Manager’s Assessment and Program Summary.

b) Current organization chart, including names of individuals fulfilling the roles identified and updates as necessary.

c) Report of Key Technical Parameters and trends for each Technical

Performance Metric (TPM). The list of reported Key Technical

Page 31 of 222 Printed Friday, September 29, 2023

ID

SCCDRL96

Object Number

3.1.6.0-3

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

Parameters will be per mutual agreement with the Government. The parameters presented will be at least to the major component level of the subsystems, e.g., Mechanisms, Power supplies, heaters, cabling, etc. The TPMs for mass and power should include the instrument mass and power within the totals for mass and power. At a minimum, the TPMs (Current Best Estimate (CBE), Maximum Expected Value, Available Resource, and Margin) should be reported against the specification for:

1) Mass (Kg)

2) Operational Peak and Average Power (W)

3) Survival Peak and Average Power (W)

4) Pointing knowledge and control error budgets

5) Average Data Rate (Mbps)

6) Peak Data Rate (Mbps)

7) Memory Utilization

8) CPU Utilization

9) Accuracy of the values and units

10) Status of margins and contingency

d) Technical status for system and subsystem design and development activities, including technology maturity efforts for reaching TRL 6 by PDR, and subcontract technical performance.

e) Design Status (when design work is being accomplished) covering the design activities for the previous month, including: schedule and technical status of development, manufacturing status, qualification and test status, issues and concerns, and Configuration Change status:

1) List of Class I in process and approved changes.

2) List of Class II approved Changes available upon request.

3) Status of engineering products against planned release

f) Summary of Integrated Master Schedule Status, including a brief description of the status of each component, subassembly, or subsystem along with descriptions of any existing or potential problem areas.

g) Critical path and near critical paths explained along with possible workarounds being considered to maintain the schedule. A slack metric with at least 1 month of aging (prior month slack) will be maintained and provided for major hardware developments and activities.

h) Schedule Risk Analysis (SRA) results, including projected delivery date based on SRA.

i) Integration & Test Status such as Test Issues, Test Results, Performance Trends.

j) Verification & Validation status and issues (as required).

k) Mission Assurance status such as summary of MRB actions and status;

summary of FRB actions and status; failure investigations and corrective actions

l) Summary (actions and status) of GIDEP alerts, GIDEP Problem Advisories, and NASA advisories that apply to GeoXO spacecraft

m) Lower Tier Suppliers Status (as required).

n) Problems (problems that are significant in nature, questionable

“significance” should be discussed with and determined by the Observatory Manager or COR) encountered during the reporting period, and anticipated approaches for resolution (including, as appropriate, technical issues, manpower and staffing, supplier, and Subcontractor

Page 32 of 222 Printed Friday, September 29, 2023

ID

SCCDRL96

SCCDRL97

SCCDRL98

Object Number

3.1.6.0-3

3.1.6.0-4

3.1.6.0-5

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL) issues, etc.).

o) Status of open issues and problems from prior reporting periods.

p) Risk Status for top 10 risks, including the status of mitigations plans of each.

q) Schedule and Cost Threats summary based on quantified values of all risks with schedule and cost impacts

r) Status of Master Action Items Database (MAID) action items with focus brought to those actions which are not closing in a timely manner.

s) Identification and status of long-lead purchases/acquisitions planned.

t) Prohibited Materials Compliance Status (as required):

1) GeoXO Product Alert evaluation status.

2) Production Readiness Issues (as required).

u) Significant plans and activities for the following month, including upcoming milestone events depicting critical items of Project status.

v) Contract Status:

1) Summary of current proposals, proposal preparations and expected completion dates.

2) Summary of current Configuration Change Requests (CCRs).

3) Summary of potential future proposals and CCRs, including

Deviations and Waivers.

w) Summary of Task Orders.

1) Status of current task orders and estimated completion dates.

2) Discussion of impediments to timely completion of tasks.

3) Discussion of potential future tasks.

x) CDRL Status Report that includes the following information for each document delivered in accordance with the CDRL or overdue from previous reporting periods:

1) Document Number

2) Document Title

3) Scheduled Due Date

4) Actual Submittal Date

5) Current Status

6) List of documents planned for delivery during the next reporting period, listed by document number, title, and scheduled submittal date.

y) Award Fee (AF) Milestone Status.

1) List of Current AF Milestones with current due date and expected completion dates.

2) Summary of issues that may be hindering the timely completion of each AF milestone.

The PMSR-T presentation material may be in Contractor format.

The PMSR-B data package shall address the following:

a) Program Manager’s Assessment and Program Summary

b) Summary of Integrated Master Schedule Status, including a brief description of the status of each subsystem or subassembly along with descriptions of any existing or potential problem areas.

c) Explanation for the critical path and near critical paths along with possible workarounds being considered to maintain the schedule. A slack metric with at least 1 month of aging (prior month slack) is to be maintained and provided for major hardware developments and

Page 33 of 222 Printed Friday, September 29, 2023

ID

SCCDRL98

SCCDRL99

SCCDRL100

SCCDRL101

SCCDRL102

Object Number

3.1.6.0-5

3.1.6.0-6

3.1.7

3.1.7.0-1

3.1.7.0-2

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL) activities (the Government and Contractor managers will determine which items are to be tracked at least quarterly).

d) A detailed 12-month “rolling-wave” schedule (3 months of actual, plus 9 months of forecast)

e) Metrics summarizing all milestones depicting planned versus actual accomplishments and explanations for variances, e.g., graphic display of planned versus actual cumulative milestone status, xx of 1,000 milestones are behind plan and why, etc.

f) Summary explanation of key EVM parameter performance and trends

g) Metrics by Integrated Product Team (IPT) and Total Project, summarizing Baseline, Forecast and Actual Headcounts where a head equals one equivalent work-month of effort. Include explanation of variance from plan.

h) Review of Management Reserve (MR) Liens or other unfunded risk mitigations including estimated cost and impact

i) Status of action items with focus brought to those actions which are not closing in a timely manner

j) Business issues, including personnel changes

k) Summary of Contract Status:

1) Summary of current contract Funding vs contract cost and Termination Liability requirements

2) Projection of future funding requirements

3) Summary of proposals (Current and in process)

l) Subcontract Management Status

1) Summary of programmatic status of major subcontractors

m) Summary of Task Orders in a tabular format:

1) Task Order number and title

2) Authorized value

3) Period of Performance

4) Actual Cost to date

5) Actual Cost of money to date

6) Estimate at completion

7) Estimated completion Date

8) Total estimated estimate at completion for all closed and open tasks v the total authorized task pool value

9) Status – Open or Closed

10) Discussion of impediments to completing tasks in a timely and cost-effective manner, if applicable

The PMSR-B presentation material may be in Contractor format.

3.1.7 PM-07 Spares Plan and List

DATA ITEM DESCRIPTION

1. CDRL No.: PM-07

2. Title: Spares Plan and List

3. Use: To establish the Contractor’s spares plan and list.

4. Preparation Information:

The Spares Plan and List shall define and justify the Contractor’s position for the spares proposed for the spacecraft.

Page 34 of 222 Printed Friday, September 29, 2023

ID

SCCDRL103

SCCDRL104

SCCDRL106

SCCDRL107

SCCDRL108

SCCDRL109

SCCDRL110

SCCDRL111

SCCDRL112

SCCDRL113

SCCDRL114

SCCDRL115

SCCDRL116

Object Number

3.1.7.0-3

3.1.7.0-4

3.1.7.0-5

3.1.7.0-6

3.1.7.0-7

3.1.8

3.1.8.0-1

3.1.8.0-2

3.1.8.0-3

3.1.8.0-4

3.1.8.0-5

3.1.8.0-6

3.1.8.0-7

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

The Spares Plan and List shall present the schedule and method for obtaining the spares.

The Spares Plan and List shall provide a listing of Spares.

The Spares Plan and List shall consider the judicious definition, procurement, and stock of a set of these critical spares to help minimize potential schedule impact created by hardware failures, by contamination, or by other plausible events or conditions.

The spares may be retained as fully assembled, partially assembled or piece part spares. Since the need to use a spare may be a failure condition in the spacecraft and, depending on the specifics of the fault, the spare itself may need rework or repair, simple substitution of a spare may not be a viable approach. With this consideration in mind, the Contractor shall establish the assembly level of sparing.

In defining the spare parts program, the Contractor shall consider the reliability, handling, and environment conditions of subsystems, components, and parts under consideration for sparing, including the likelihood that these items need to be replaced.

3.1.8 PM-08 Digital Image and Video Records

DATA ITEM DESCRIPTION

1. CDRL No.: PM-08

2. Title: Digital Image and Video Records

3. Use: Program status reviews, system, subsystem, and assembly packaging evaluations and troubleshooting

4. Preparation Information:

The Contractor shall produce closeout photographic documentation of all assemblies during the manufacturing process and of the final integrated configuration "as flown."

The photographs shall be of sufficiently high resolution to reasonably support anomaly resolutions.

The Contractor shall archive photographic documentation of the hardware not posted to the GeoXO portal and make it available to the Government upon request.

The photographs shall include images of major subsystems, assemblies, the full-up system, major test configurations and Ground Support Equipment (GSE) items.

The photographs shall serve as a record of the build-up of major components, subassemblies, and subsystem assemblies, e.g., a typical electronic card, motherboard, electronic subsystem with cover off, etc.

Each Image shall be identified with a label containing the following information: assembly number, serial number, description (e.g., name of the assembly), date of image, and the supplier's company name.

Page 35 of 222 Printed Friday, September 29, 2023

ID

SCCDRL117

SCCDRL118

SCCDRL119

SCCDRL120

SCCDRL121

SCCDRL122

SCCDRL123

Object Number

3.1.8.0-8

3.1.8.0-9

3.1.8.0-10

3.1.8.0-11

3.1.8.0-12

3.1.8.0-13

3.1.8.0-14

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

The subject of the photograph shall appropriately fill the digital frame to allow for effective magnification.

Images shall include pictures of environmental test fixtures, the component, subsystem or spacecraft under test, and any other pictures that would help explain the environmental test setup.

Images shall be of sufficient resolution to:

a) show component placement,

b) show part marking,

c) show details that are covered or obscured at subsequent levels of assembly, and/or any other operation that renders subsequent inspection impractical,

d) permit identification of components, and

e) permit verification of wire routings.

The following events shall be photographed during closeout operations at the S/C contractor's facility, as applicable (pre-shipment), and at launch base:

1. Final closeout at the S/C contractor’s facility prior to shipping:

a. Interior of each area of the satellite prior to final closure.

b. Exterior of the satellite

c. All deployable appendages, including but not limited to hinges, hold-downs, insulation blankets near deployables, and antennas.

d. Exterior of satellite installed in shipping container prior to lid closure, including but not limited to mounting points, purge lines, thermistors, and accelerometers.

2. At the launch base:

a. Exterior of the satellite upon receipt at the Payload Processing

Facility

b. Interior of the satellite prior to final closeout for launch

c. Final stowage condition of all deployables prior to encapsulation into the launch vehicle (LV) fairing.

d. Final condition of all antennas prior to LV encapsulation.

e. Removal sites of all red tag items and installation sites of green tag items prior to LV encapsulation (including but not limited to thruster covers, earth and sun sensors protective covers, and lifting eye bolts)

f. Exterior of the satellite prior to encapsulation

g. Prior to LV fairing door closure on the pad, photographs of the sites of at least any removed purged lines and electrical connections.

Recorded video shall include assembly of the spacecraft of sufficient detail to be used for future assembly training and possible failure investigation.

Recorded video shall include the packaging, handling, and movement of major spacecraft and satellite moves and critical/hazardous operations as agreed with the Government.

The photos and videos shall be organized in a logical manner (i.e., by timeline, subsystem, etc.)

Page 36 of 222 Printed Friday, September 29, 2023

ID

SCCDRL124

SCCDRL125

SCCDRL126

SCCDRL127

SCCDRL128

SCCDRL129

SCCDRL130

SCCDRL131

SCCDRL132

SCCDRL133

SCCDRL134

Object Number

3.1.9

3.1.9.0-1

3.1.9.0-2

3.1.9.0-3

3.1.9.0-4

3.1.9.0-5

3.1.10

3.1.10.0-1

3.1.10.0-2

3.1.11

3.1.11.0-1

418-XO-SCCDRL-0053, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft (SC) Contract Data Requirements

List (CDRL)

3.1.9 PM-09 Document Tree

DATA ITEM DESCRIPTION

1. CDRL No.: PM-09

2. Title: Document Tree

3. Use: For ready reference list of all spacecraft and GSE documents.

4. Preparation Information:

The Document Tree shall list all documents for the spacecraft and for the

GSE.

The Document Tree shall be organized and identified to serve as a ready reference list.

The Document Tree shall identify documents by name and number.

The Document Tree shall include a brief description defining the scope of each document.

3.1.10 PM-10 Engineering Development Unit(s) (EDUs)

Activities Report

DATA ITEM DESCRIPTION

1. CDRL No.: PM-10

2. Title: Engineering Development Unit(s) (EDUs) Activities Report

3. Use: The EDUs Activities Report provides performance assessment to raise confidence in the flight hardware designs and minimize risk to flight hardware development.

4. Preparation Information:

The EDUs Activities Report shall include a comprehensive performance assessment including, but not limited to:

a) Assessment against the objectives of the EDU development(s) over the Program lifecycle

b) Assessment against performance requirements in the F&PS, GIRD, or other interface document(s)

c) Trending of key parameters during the EDU development(s)

d) Risks mitigated

e) Design modifications that…