Attachment B - L10 CDRL and DID Rev A.pdf

Attachment No. B

Landsat 10 Contract Data Requirements List (CDRL) and Data Item Descriptions (DID)

RFP 80GSFC26R0015

National Aeronautics and Space Administration Goddard Space Flight Center

Landsat 10 SC CDRL & DID L10-SC-REQ-0029 Revision A ii

Landsat 10 Spacecraft Contract Data Requirements List (CDRL) and Data Item Descriptions (DID)

Signature/Approval Page Prepared by:

Electronic Signature in TDMS Approval Date in TDMS Stephen McKim Date Landsat 10 Deputy Mission System Engineer NASA/GSFC, Code 533

Prepared by:

Michael Pryzby Date Landsat 10 Space Environments Engineer NASA/GSFC, Code 426

Approved by:

Cagatay Aymergen Date Landsat 10 Deputy Project Manager / Acting Observatory Manager

Ross Henry Date Landsat 10 Project Manager

Evan Webb Date Landsat 10 Mission Systems Manager NASA/GSFC, Code 533 iii

CM Foreword This document is a Landsat 10 Project Configuration Management (CM)-controlled document.

Note: Prior to February 2026, the project name was Landsat Next (LNext).

For the purposes of configuration management, the prefixes “LNEXT” and “L10” are completely interchangeable. For example, LNEXT-MGMT-PLAN-0004 is the same as L10-MGMT-PLAN- 0004.

Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the Landsat 10 CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

NASA/Goddard Space Flight Center Landsat 10 Project Office, Code 426 Attention: Configuration Management Office Greenbelt, Maryland 20771 iv

Change History Log v

Table of Contents SIGNATURE/APPROVAL PAGE ................................................................................................ II

CM FOREWORD ..........................................................................................................................III

CHANGE HISTORY LOG .......................................................................................................... IV

TABLE OF CONTENTS ................................................................................................................ V

LIST OF FIGURES ........................................................................................................................ V

LIST OF TABLES ........................................................................................................................ VI

1.0 INTRODUCTION

2.0 DEFINITION OF DUE DATES/MATRUITY, DEFINITION OF CATEGORIES, AND

MAILING DISTRIBUTION INSTRUCTIONS

2.1 Due Dates - Related Definitions

2.1.1 Due Date

2.2 Maturity

2.3 Category

2.4 Media

3.0 LANDSAT 10 CONTRACT DATA REQUIREMENTS LIST

3.1 CDRL Table

3.1.1 Program Management Data

3.1.2 Review Data

3.1.3 Software Data

3.1.4 Integration and Test Data

3.1.5 Systems Engineering Data

3.1.6 Launch Vehicle Data

3.1.7 Simulator Data

3.1.8 Operations Data

3.1.9 Spacecraft Data

3.1.10 Systems Assurance Data

4.0 DESCRIPTION OF REQUIRED DATA

4.1 Program Management Data

4.2 Review Data

4.3 Software Data

4.4 Integration and Test Data

4.5 Systems Engineering Data

4.6 Launch Vehicle Data

4.7 Simulator Data

4.8 Operations Data

4.9 Spacecraft Data

4.10 Systems Assurance Data

List of Figures vi

No table of contents entries found.

List of Tables

No table of contents entries found.

1.0 INTRODUCTION

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable documentation to be provided by the Spacecraft (SC) Contractor. Section 2.0 includes definitions and instructions for mailing and/or distribution. The tables in Sections 3.1.1 through 3.1.10 present the CDRL item by item, with due dates, and media format. Section 4.0 provides the Description of Required Data (DRD) or Data Item Descriptions (DIDs), a description of each item, which describes the use for the deliverable and the required preparation information; except where specifically indicated to the contrary, the formats and drawing standards used may be those normally used by the SC Contractor and by its Subcontractors.

2.0 DEFINITION OF DUE DATES/MATRUITY, DEFINITION OF

CATEGORIES, AND MAILING DISTRIBUTION INSTRUCTIONS

2.1 DUE DATES - RELATED DEFINITIONS

The following definitions apply to the DUE DATE column in the tables in Section 3.1.1 through

3.1.10. Unless otherwise specified, deadlines are in calendar days. Submissions can be made before the due date if the Contractor believes that no changes will be made between the submittal date and the due date.

2.1.1 Due Date

DUE DATE: The contract baseline schedule for delivery of Statement of Work (SOW) CDRL items is shown in the CDRL tables in Sections 3.1.1 through 3.1.10; items in the schedule for delivery are associated with acronyms for the various program reviews that form the contract baseline. Items designated for delivery "As Generated", or "Update As Required (UAR)" are due to be provided to the Government within the timeframe specified in the table or as agreed to by the Government.

Monthly: Submitted on monthly basis L: Launch Date DACA: (Calendar) Days After Contract Award NLT: No Later Than Other entries in the "DUE DATE" column are self-explanatory.

2.2 MATURITY

The following definitions apply to the MATURITY column in the tables in Sections 3.1.1 through 3.1.10.

(1) Initial: The first submission of an item, which will be revised and resubmitted at a later date.

(2) Preliminary: An early submission of an item. To be completed as is practicable at the time of preparation. Preliminary submittals are written with the best available current information and are resubmitted when further information becomes available.

(3) Final: The complete, thorough submission of an item for approval, review, or information that, to the best of the Contractor’s knowledge and intention, does not require further revision or updates. However, this type of submission does not preclude updating if later found to be necessary. Any updates require the same "approval/review" process as was required for the original final submissions.

(4) Baseline, Current: The delivery is written with the best up-to-date information available at the time.

(5) Update: The delivery is revised with the best up-to-date information available at the time.

Other entries in the "MATURITY" column are self-explanatory.

2.3 CATEGORY

The following definitions apply to the CATEGORY column in the tables in Sections 3.1.1 through 3.1.10. If separate approval instructions are not specified for separate submission due date/maturity items, then the listed approval instruction applies to all submissions.

A Approval: CDRL items in this category require approval by the GSFC Contracting Officer’s Representative (COR) or Contracting Officer (CO) prior to use by the Contractor.

Receipt by the Government is due within the time specified in the "Due Date" column in the tables in Sections 3.1.1 through 3.1.10 of this document.

Requirements for re-submission are as specified by the Contracting Officer or Contracting Officer's Representative. In most cases, the Contractor will be required to resubmit the document within 14 calendar days of receiving comments from the Government. If the Contractor has not received a response from GSFC within 45 calendar days of delivery of a CDRL item, the Contractor may proceed as if the document has been approved.

I Information: Data in this category is due to the Government within the time period specified in the “Due Date” column in the tables in Sections 3.1.1 through 3.1.10 for the purpose of determining current program status, progress, and future planning requirements. The Government may submit questions and/or comments pertaining to the deliverables, which the Contractor will provide feedback on either in writing or verbally in meetings. The Contractor is not required to make changes or updates based on Government feedback.

2.4 MEDIA

The Contractor shall deliver all media items in electronic format to a mutually defined web portal that allows external Government and Contractor access unless otherwise noted in the tables in Sections 3.1.1 through 3.1.10.

The Contractor shall notify the CO of electronic submission of the deliverable via email.

The Contractor shall deliver in the following electronic formats unless otherwise approved by the Government:

Text Documents: Portable Document Format (PDF) (searchable) or Microsoft (MS) Word Presentations: PDF (searchable) or MS PowerPoint Spreadsheets: MS Excel

Databases: Delimited American Standard Code for Information Interchange (ASCII) files accompanied with database schema document defining tables and entries

Schedules: PDF (searchable) and MS Project Schematics and Drawings: High-Resolution PDF to be readable Photographs: Joint Photographic Experts Group (JPEG) or current industry standard Video: Any readily available open standard (e.g., Audio Video Interleave (AVI), Movie Picture Experts Group (MPEG))

3.0 LANDSAT 10 CONTRACT DATA REQUIREMENTS LIST

3.1 CDRL TABLE

The tables in Sections 3.1.1 through 3.1.10 comprise the Spacecraft Contract Data Requirements List.

The tables contain the following CDRLs:

Program Management (PM) Reviews (RE) Flight Software (SW) Integration and Test (IT) System Engineering (SE) Launch Vehicle (LV) Simulators (SIM) Spacecraft (SC) Systems Assurance (SA) Operations (OPS)

3.1.1 Program Management Data

CDRL Number CDRL Title Category Due Date and Maturity SOW

Reference L10-PM-01 Monthly Project Status Reviews L10-PM-01: I L10-PM-01: Monthly, materials -5 days before meeting 4.0 and

4.10.1 L10-PM-02 Inputs to Project Protection Plan L10-PM-02-01: I

L10-PM-02-02: I

L10-PM-02-03: I

L10-PM-02-04: I

L10-PM-02-05: I

L10-PM-02-06: I

L10-PM-02-07: I

L10-PM-02-01: Reserved L10-PM-02-02: PPP Inputs, MSRR -15 days, Preliminary L10-PM-02-03: PPP Inputs, MPDR -15 days, Updates L10-PM-02-04: PPP Inputs, MCDR -15 days, Updates L10-PM-02-05: PPP Inputs, MSIR -15 days, Updates L10-PM-02-06: PPP Inputs, FRR -15 days, Updates L10-PM-02-07: PPP Inputs, OAR -15 days, Final

4.10.8

L10-PM-03 Contractor’s Review Plan L10-PM-03-01: I

L10-PM-03-02: I

L10-PM-03-01: DACA +30 days, Draft L10-PM-03-02: SC SRR -14 days, Final

Table 4.10.7.2-1

L10-PM-04 Program Security Plan Supporting Documentation for Landsat 10 Assessment and Authorization and Security Requirements for Unclassified IT Resources

L10-PM-04: A L10-PM-04: DACA +30 days, Final 4.10.8

L10-PM-05 Integrated Master Schedule (IMS) L10-PM-05: I L10-PM-05: Monthly 4.10, 4.10.1, 4.10.2

3.1.2 Review Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference L10-RE-01 Contractor’s Review Materials L10-RE-01-01: I

L10-RE-01-02: I

L10-RE-01-01: Review -7 days, Preliminary L10-RE-01-02: Review +7 days, As-Presented version.

4.10.7

L10-RE-02 Inputs to Mission Level Reviews L10-RE-02-01: I

L10-RE-02-02: I

L10-RE-02-03: I

L10-RE-02-04: I

L10-RE-02-05: I

L10-RE-02-06: I

L10-RE-02-07: I

L10-RE-02-08: I

L10-RE-02-09: I

L10-RE-02-10: I

L10-RE-02-11: I

L10-RE-02-12: I

L10-RE-02-01: MPDR -21 days, Final L10-RE-02-02: MCDR -21 days, Final L10-RE-02-03: MOR -21 days, Final L10-RE-02-04: SIR -21 days, Final L10-RE-02-05: PER -21 days, Final L10-RE-02-06: FOR -21 days, Final L10-RE-02-07: ORR -21 days, Final L10-RE-02-08: PSR -21 days, Final L10-RE-02-09: FRR -21 days, Final L10-RE-02-10: LVRR -21 days, Final L10-RE-02-11: LRR -21 days, Final L10-RE-02-12: PLAR -21 days, Final

4.10.7

L10-RE-03 On-Orbit Acceptance Review

(OAR)

L10-RE-03: A L10-RE-03: OAR -14 days, Final 4.10.7

3.1.3 Software Data

Reference L10-SW-01 Software Management and

Development Plan (SMDP)

L10-SW-01-01: I

L10-SW-01-02: I

L10-SW-01-03: I

L10-SW-01-04: I

L10-SW-01-01: DACA +30 days, Initial L10-SW-01-02: SC SRR -30 days, Baseline L10-SW-01-03: SC PDR -30 days, Update L10-SW-01-04: SC CDR -30 days, Update

4.11.6.3

L10-SW-02 Software Architectural and Detailed Design Description

(SDD)

L10-SW-02-01: I

L10-SW-02-02: I

L10-SW-02-03: I

L10-SW-02-01: SC PDR -30 days, Baseline L10-SW-02-02: SC CDR -30 days, Update L10-SW-02-03: OIRR -30 days, Update

4.11.6.3

L10-SW-03 Software Version Description Document

L10-SW-03: I L10-SW-03: With each Software/patch release, Final 4.11.6.3

L10-SW-04 Software Requirements Specification

L10-SW-04-01: A

L10-SW-04-02: I

L10-SW-04-01: SC PDR -30 days, Initial L10-SW-04-02: SC CDR -30 days, Baseline

4.11.6.3

L10-SW-05 Software Test Plan L10-SW-05-01: I

L10-SW-05-02: A

L10-SW-05-03: I

L10-SW-05-01: SC PDR -30 days, Initial L10-SW-05-02: SC CDR -30 days, Baseline L10-SW-05-03: OIRR, Update

4.11.6.3

L10-SW-06 Software Test Reports (STR) L10-SW-06: I L10-SW-06: OIRR -30 days, Final 4.11.6.3

3.1.4 Integration and Test Data

Reference L10-IT-01 Observatory Integration and Test

Plan

L10-IT-01-01: I

L10-IT-01-02: A

L10-IT-01-03: A

L10-IT-01-01: SC CDR -15 days, Preliminary L10-IT-01-02: OIIRR -30 days, Final L10-IT-01-03: Obs PER -45 days, EMI/EMC, Dynamics, Thermal Vacuum Specific Plan, Final

4.2

L10-IT-02 Observatory Integration and Test Procedures

L10-IT-02-01: I

L10-IT-02-02: A

L10-IT-02-01: Test -60 days, Preliminary L10-IT-02-02: Test -30 days, Final

4.2

L10-IT-03 Observatory and Simulator Test Data Sets

L10-IT-03-01: I

L10-IT-03-02: I

L10-IT-03-01: Test completion event per the Giver/Receiver List +2 days, Preliminary L10-IT-03-02: Test completion event per the Giver/Receiver List +15 days, Final

4.2

L10-IT-04 Observatory Integration and Test Reports

L10-IT-04-01: I

L10-IT-04-02: A

L10-IT-04-01: Test completion +15 days, Preliminary L10-IT-04-02: Test completion +45 days, Final

4.2

L10-IT-05 Spacecraft Comprehensive Performance Test (CPT) and Limited Performance Test (LPT) Plan

L10-IT-05-02: A L10-IT-05-02: SC LPT -90 days, Final 4.1

L10-IT-06 Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) Control Plan

L10-IT-06-01: I

L10-IT-06-02: I

L10-IT-06-01: SC PDR -30 days, Initial L10-IT-06-02: Obs PER -60 days, Final

4.2

3.1.5 Systems Engineering Data

CDRL

Number

CDRL Title Category Due Date and Maturity SOW Reference

L10-SE-01 CCB Summary and Logs, Deviations, and Waivers

L10-SE-01-01: A

L10-SE-01-02: I

L10-SE-01-01: Deviations and Waivers, As generated L10-SE-01-02: CCB Summary and Logs, As generated

4.11.1

L10-SE-02 Micro Meteoroid and Orbital Debris Assessment and End of Mission Plan Inputs

L10-SE-02-01: I

L10-SE-02-02: I

L10-SE-02-03: I

L10-SE-02-04: I

L10-SE-02-05: I

L10-SE-02-01: MPDR -45 days, Preliminary ODAR L10-SE-02-02: MCDR -45 days, Preliminary ODAR L10-SE-02-03: MSIR, ORSAT Model Inputs, Preliminary L10-SE-02-04: MPER, ORSAT Model Inputs, Final L10-SE-02-05: SMSR -60 days, Final ODAR/EOMP

4.11.6.1

L10-SE-03 System Performance Verification Plan and Matrix

L10-SE-03-01: A

L10-SE-03-02: A

L10-SE-03-03: A

L10-SE-03-01: SC PDR -10 days, Preliminary L10-SE-03-02: SC CDR -10 days, Final L10-SE-03-03: OIIRR -15 days, Update

4.11

L10-SE-04 Verification Reports L10-SE-04-01: A L10-SE-04-01: Verification Event +30 days, Final 4.11 L10-SE-05 Fault Management

Description Document

L10-SE-05-01: I

L10-SE-05-02: I

L10-SE-05-03: A

L10-SE-05-01: SC PDR -14 days, Preliminary L10-SE-05-02: SC CDR -14 days, Baseline L10-SE-05-03: FM Test -60 days, Final

4.9.5.2 and 4.11

L10-SE-06 DOORS Compatible Database

L10-SE-06-01: I

L10-SE-06-02: I

L10-SE-06-01: SC SRR -60 days, Preliminary L10-SE-06-02: Monthly, Updates

4.11

L10-SE-07 Observatory Ground Support Equipment Plan

L10-SE-07-01: I

L10-SE-07-02: I

L10-SE-07-03: I

L10-SE-07-04: I

L10-SE-07-01: MPDR -30 days, Preliminary L10-SE-07-02: MCDR -30 days, Baseline L10-SE-07-03: Obs PER -30 days, Updates L10-SE-07-04: PSR -30 days, Final

4.2

L10-SE-08 Observatory & Simulator Acceptance Data Packages

L10-SE-08-01: A

L10-SE-08-02: A

L10-SE-08-03: A

L10-SE-08-04: A

L10-SE-08-05: A

L10-SE-08-06: A

L10-SE-08-01: Observatory Data, PSR -60 days L10-SE-08-02: MOC Site Acceptance Test +15 days, Observatory Operations Simulator L10-SE-08-03: RF Suitcase Acceptance Test +15 days, RF Suitcase L10-SE-08-04: CTSS MOC Site Acceptance Test +15 days, CTSS L10-SE-08-05: SoftSim MOC Site Acceptance Test +15 days, SoftSim L10-SE-08-06: LVIS Acceptance Test +15 days, LVIS

4.1, 4.7, 4.9, 4.10, 4.11

L10-SE-09 Engineering Drawings and Drawing Tree

L10-SE-09-01: I

L10-SE-09-02: I

L10-SE-09-03: I

L10-SE-09-04: I

L10-SE-09-01: SC PDR -30 days, Drawing Tree L10-SE-09-02: SC CDR -30 days, Baseline L10-SE-09-03: As Generated +15 days, As Built, Updates L10-SE-09-04: Launch -30 days, Final

4.11

L10-SE-10 Dynamics Model Validation Plan and Report

L10-SE-10-01: I

L10-SE-10-02: A

L10-SE-10-03: I

L10-SE-10-04: A

L10-SE-10-01: SC PDR -30 days, Initial Plan L10-SE-10-02: SC CDR -30 days, Final Plan L10-SE-10-03: SC CDR +30 days, Initial Report L10-SE-10-04: Post Test CPT +30 days, Final Report

4.11

3.1.6 Launch Vehicle Data

L10-LV-01 Launch Site Ground Operations

Plan

L10-LV-01-01: I

L10-LV-01-02: I

L10-LV-01-03: A

L10-LV-01-01: SC CDR -45 days, Preliminary L10-LV-01-02: OIRR -15 days, Updates L10-LV-01-03: PSR -120 days, Final

4.6

L10-LV-02 Launch Site Test Procedures L10-LV-02-01: I

L10-LV-02-02: A

L10-LV-02-01: PSR -90 days, Preliminary L10-LV-02-02: Obs shipment -30 days, Final

4.6

L10-LV-03 Launch Commit Criteria (LCC) L10-LV-03-01: I

L10-LV-03-02: I

L10-LV-03-03: I

L10-LV-03-01: MOR -90 days, Preliminary L10-LV-03-02: ORR -30 days, Update L10-LV-03-03: FOR -30 days, Final

4.6

3.1.7 Simulator Data

Number

CDRL Title Category Due Date and Maturity SOW Reference

L10-SIM-01 Simulator Verification and Acceptance Test Plan

L10-SIM-01-01: I

L10-SIM-01-02: A

L10-SIM-01-03: I

L10-SIM-01-01: SC PDR -15 days, Preliminary L10-SIM-01-02: Simulator Integration Start -60 days, Final L10-SIM-01-03: Update

4.4

L10-SIM-02 Simulator Acceptance Test Procedures and As-Run Procedure Artifacts

L10-SIM-02-01: I

L10-SIM-02-02: I

L10-SIM-02-03: I

L10-SIM-02-01: Simulator Acceptance Test Start -45 days, Preliminary Test Procedures L10-SIM-02-02: Simulator Acceptance Test Start -14 days, Final Test Procedures L10-SIM-02-03: Sim Acceptance Test Completion +10 days, Test As-Run Procedures & Artifacts

4.4

L10-SIM-03 Simulator's User's Guide and Training Materials

L10-SIM-03-01: I

L10-SIM-03-02: A

L10-SIM-03-03: I

L10-SIM-03-04: I

L10-SIM-03-01: User Guide, Simulator Deliveries -45 days, Preliminary L10-SIM-03-02: User Guide, With Simulator Delivery, Final L10-SIM-03-03: Training Materials, Training Date, Final L10-SIM-03-04: Updates

4.4

L10-SIM-04 Simulator Requirements and Development Plan

L10-SIM-04-01: I

L10-SIM-04-02: A

L10-SIM-04-01: DACA +60 days, Preliminary L10-SIM-04-02: SC SRR -15 days, Final

4.4

3.1.8 Operations Data

Reference L10-OPS-01 Flight Operations Team (FOT)

Training Materials

L10-OPS-01-01: A

L10-OPS-01-02: I

L10-OPS-01-03: I

L10-OPS-01-01: Training Session #1 -60 days, Final L10-OPS-01-02: Training Session #2 -30 days, Updates L10-OPS-01-03: Training Materials, At OAR, Updates

4.7

L10-OPS-02 Mission Readiness, Commissioning and Operations Support Plan

L10-OPS-02-01: I

L10-OPS-02-02: A

L10-OPS-02-03: I

L10-OPS-02-04: I

L10-OPS-02-01: SC PDR +15 days, Preliminary L10-OPS-02-02: SC CDR, Update L10-OPS-02-03: SORT start -30 days, Update L10-OPS-02-04: PSR -90 days, Final

4.7

L10-OPS-03 Space to Operations Interface Documentation

L10-OPS-03-01: I

L10-OPS-03-02: A

L10-OPS-03-03: I

L10-OPS-03-01: SC PDR -30 days, Preliminary L10-OPS-03-02: SC CDR -7 days, Final L10-OPS-03-03: SC CPT, Update

4.7

L10-OPS-04 Operations and Contingency Products and Procedures

L10-OPS-04-01: I

L10-OPS-04-02: I

L10-OPS-04-03: A

L10-OPS-04-04: A

L10-OPS-04-01: Test or Simulation Event -60 days L10-OPS-04-02: SC PDR, Preliminary L10-OPS-04-03: PSR -30 days, Launch Baseline L10-OPS-04-04: OAR, Final

4.7

L10-OPS-05 Spacecraft User's Manual (SUM) L10-OPS-05-01: I

L10-OPS-05-02: I

L10-OPS-05-03: A

L10-OPS-05-04: I

L10-OPS-05-05: I

L10-OPS-05-01: SC CDR -15 days, Preliminary L10-OPS-05-02: SC Bus CPT +60 days, Updates L10-OPS-05-03: First Mission Sim -90 days, Update L10-OPS-05-04: PSR -30 days, Final Pre-launch version L10-OPS-05-05: OAR, Final

4.7

L10-OPS-06 Observatory Command and Telemetry Handbook & Database

L10-OPS-06-01: I

L10-OPS-06-02: I

L10-OPS-06-03: I

L10-OPS-06-04: A

L10-OPS-06-05: I

L10-OPS-06-01: MCDR -90 days, Preliminary L10-OPS-06-02: MCDR +90 days, Update L10-OPS-06-03: SORT start -30 days, Update L10-OPS-06-04: Obs I&T -15 days, Final L10-OPS-06-05: Approx. every 3 months until final On- Orbit acceptance, Updates

4.7

L10-OPS-07 Observatory Flight Rules, Constraints, Restrictions, and Warnings Document

L10-OPS-07-01: I

L10-OPS-07-02: I

L10-OPS-07-03: I

L10-OPS-07-04: A

L10-OPS-07-05: I

L10-OPS-07-01: MCDR, Preliminary L10-OPS-07-02: Obs. I&T start -15 days, Updates L10-OPS-07-03: SORT start -30 days, Updates L10-OPS-07-04: PSR -15 days, Final Pre-Launch Version L10-OPS-07-05: OAR, Final

4.7

L10-OPS-08 Operationally Delivered Tools Documentation and Training

L10-OPS-08: I L10-OPS-08: In conjunction with tool delivery and updates, As Generated

4.7

3.1.9 Spacecraft Data

Number

CDRL Title Category Due Date and Maturity SOW Reference

L10-SC-01 Observatory Thermal Models and Analysis

L10-SC-01-01: I

L10-SC-01-02: I

L10-SC-01-03: I

L10-SC-01-04: I

L10-SC-01-05: I

L10-SC-01-06: I

L10-SC-01-07: I

L10-SC-01-01: MPDR -30 days, Preliminary L10-SC-01-02: MCDR -30 days, Update L10-SC-01-03: Observatory TB/TV -30 days, Update (Test Model) L10-SC-01-04: Observatory TB/TV +60 days, Final (Correlated) L10-SC-01-05: Reduced Launch Model, LRD-24 Months or as specified by Launch Services Provider, Preliminary L10-SC-01-06: Reduced Launch Model, LRD-18 Months or as specified by Launch Services Provider, Updated L10-SC-01-07: As generated, Updates

4.11

L10-SC-02 Mass Properties Report

L10-SC-02-01: I

L10-SC-02-02: I

L10-SC-02-03: I

L10-SC-02-04: I

L10-SC-02-01: MPDR, Preliminary L10-SC-02-02: MCDR, Updates L10-SC-02-03: PER and as Required by Launch Service Provider, Updates L10-SC-02-04: PSR, Final

4.11

L10-SC-03 Observatory Mechanical Models and Analyses

L10-SC-03-01: I

L10-SC-03-02: I

L10-SC-03-03: I

L10-SC-03-04: I

L10-SC-03-05: I

L10-SC-03-06: I

L10-SC-03-07: I

L10-SC-03-08: I

L10-SC-03-09: I

L10-SC-03-10: I

L10-SC-03-11: I

L10-SC-03-12: I

L10-SC-03-13: I

L10-SC-03-14: I

L10-SC-03-15: I

L10-SC-03-16: I

L10-SC-03-17: I

L10-SC-03-18: I

L10-SC-03-19: I

L10-SC-03-20: I

L10-SC-03-21: I

L10-SC-03-01: IMSC FEM and CAD, SC PDR -30 days, Preliminary L10-SC-03-02: IMSC FEM and CAD, SC CDR -30 days, Update L10-SC-03-03: IMSC FEM and CAD, SC PER -30 days, Validated/As-built L10-SC-03-04: Observatory FEM for CLA Cycle 1, L -990 days, Preliminary L10-SC-03-05: Observatory FEM for CLA Cycle 2, L -540 days, Update L10-SC-03-06: Observatory FEM for Verification CLA -300 days, Final L10-SC-03-07: Observatory FEM for mission analysis, SC PDR -30 days, Preliminary L10-SC-03-08: Observatory FEM for mission analysis, SC CDR -30 days, Update L10-SC-03-09: Observatory FEM for mission analysis, OIRR -30 days, Validated L10-SC-03-10: Structural Analysis Report, SC PDR -30 days, Preliminary L10-SC-03-11: Structural Analysis Report, SC CDR -30 days, Update L10-SC-03-12: Structural Analysis Report, OIRR -30 days, Final L10-SC-03-13: Observatory Normal Modes Analysis Report, SC PDR, Preliminary L10-SC-03-14: Observatory Normal Modes Analysis Report, SC CDR, Update L10-SC-03-15: Observatory Normal Modes Analysis Report, OIRR -30 days, Final L10-SC-03-16: Spacecraft Structural Analysis Report, SC PDR +30 days, Preliminary L10-SC-03-17: Spacecraft Structural Analysis Report, SC CDR +30 days, Update L10-SC-03-18: Spacecraft Structural Analysis Report, OIRR -30 days, Final L10-SC-03-19: Observatory CAD model, SC PDR +14 days, Preliminary L10-SC-03-20: Observatory CAD model, SC CDR +14 days, Update L10-SC-03-21: Observatory CAD model, OIRR +14 days, As-Built

Number

CDRL Title Category Due Date and Maturity SOW Reference

L10-SC-04 Attitude Control and Pointing Analyses

L10-SC-04-01: I

L10-SC-04-02: A

L10-SC-04-03: I

L10-SC-04-01: MPDR -30 days, Initial L10-SC-04-02: MCDR -14 days, Update L10-SC-04-03: Observatory PSR, Final

4.11

L10-SC-05 Observatory Level Structural, Thermal, Optical Precision (STOP) analysis

L10-SC-05-01: I

L10-SC-05-02: I

L10-SC-05-03: I

L10-SC-05-01: MPDR -30 days, Initial L10-SC-05-02: MCDR -30 days, Update L10-SC-05-03: PSR -180 days, Final

4.11

L10-SC-06 Observatory Flight Dynamics and Orbital Maintenance Analysis

L10-SC-06-01: I

L10-SC-06-02: I

L10-SC-06-03: I

L10-SC-06-01: MPDR -14 days, Preliminary L10-SC-06-02: MCDR -14 days, Update L10-SC-06-03: Obs PER, Final

4.11

L10-SC-07 Radio Frequency (RF) Link Analysis and Bit Error Rate (BER) Analysis

L10-SC-07-01: I

L10-SC-07-02: I

L10-SC-07-03: I

L10-SC-07-01: MPDR -60 days, Preliminary L10-SC-07-02: MCDR -60 days, Final L10-SC-07-03: RF Compat +60 days, Updates

4.11

L10-SC-08 Observatory Power System Performance Analysis/Energy Balance

L10-SC-08-01: I

L10-SC-08-03: A

L10-SC-08-01: MPDR -14 days, Preliminary L10-SC-08-03: SC CPT +30 days, Final

4.11

L10-SC-09 Command and Data Handling (C&DH) and Electrical Subsystem Performance Analysis

L10-SC-09-01: I

L10-SC-09-02: I

L10-SC-09-01: SC PDR -30 days, Preliminary L10-SC-09-02: SC CDR -30 days, Final

4.11

L10-SC-10 Battery Handling Plan L10-SC-10-01: I

L10-SC-10-02: I

L10-SC-10-03: I

L10-SC-10-01: SC PDR -30 days, Preliminary L10-SC-10-02: PSR -45 days, Final L10-SC-10-03: As generated, Updates

4.11

L10-SC-11 Observatory Storage, Transportation and Handling Plan

L10-SC-11-01: I

L10-SC-11-02: A

L10-SC-11-03: I

L10-SC-11-01: OIRR -60 days, Initial L10-SC-11-02: PSR -90 days, Final L10-SC-11-03: As generated, Updates

4.5

L10-SC-12 Observatory Contamination Analyses

L10-SC-12-01: I

L10-SC-12-02: I

L10-SC-12-03: I

L10-SC-12-04: I

L10-SC-12-05: I

L10-SC-12-06: I

L10-SC-12-07: I

L10-SC-12-08: I

L10-SC-12-01: SC SRR -30 days, Preliminary derivation of contamination requirements from performance allowances & Launch Induced particle redistribution L10-SC-12-02: MPDR -30 days, Preliminary On-orbit outgassing and mass transport, thruster plume impingement/heating L10-SC-12-03: MPDR +60 days, Final derivation of contamination requirements from performance allowances L10-SC-12-04: MCDR +60 days, Final On-orbit outgassing and mass transport and thruster plume impingement/heating

Number

CDRL Title Category Due Date and Maturity SOW Reference

L10-SC-12-05: MCDR +30 days, Update Launch Induced particle redistribution L10-SC-12-06: MPSR -45 days, Final Launch Induced particle redistribution L10-SC-12-07: Launch -660 days, Preliminary Venting analysis L10-SC-12-08: Launch -420 days, Final Venting analysis

L10-SC-13 Observatory Charging Analysis Model

L10-SC-13-01: I

L10-SC-13-02: I

L10-SC-13-03: A

L10-SC-13-01: SC PDR -30 days, Preliminary L10-SC-13-02: SC CDR -30 days, Updates L10-SC-13-03: OIRR -45 days, Final

3.1.10 Systems Assurance Data

L10-SA-01 Supplier List L10-SA-01-01: I

L10-SA-01-02: I

L10-SA-01-03: I

L10-SA-01-01: SC PDR -30 days, Preliminary L10-SA-01-02: SC CDR -30 days, Final L10-SA-01-03: if new suppliers/sub-tier suppliers added, Updates

4.9

L10-SA-02 Safety Requirements Compliance Checklist

L10-SA-02-01: I

L10-SA-02-02: I

L10-SA-02-01: SC SRR -30 days, Preliminary L10-SA-02-02: SC PDR -30 days, Final

4.9

L10-SA-03 Safety Data Package (SDP) L10-SA-03: A L10-SA-03: CDR -60 days, Baseline 4.9 L10-SA-04 Hazard Verification Tracking Log L10-SA-04: A L10-SA-04: PSR -120 days, Initial 4.9 L10-SA-05 Failure Modes, Effects and Criticality

Analysis (FMECA) & Critical Items List (CIL)

L10-SA-05-01: A

L10-SA-05-02: A

L10-SA-05-03: I

L10-SA-05-01: SC PDR -30 days, Preliminary L10-SA-05-02: SC CDR -30 days, Baseline L10-SA-05-03: Each Milestone review up to LRR -30 days, Update

4.9

L10-SA-06 Software Assurance Plan (SAP) L10-SA-06-01: I

L10-SA-06-02: A

L10-SA-06-03: I

L10-SA-06-01: SC SRR -30 days, Preliminary L10-SA-06-02: SC PDR -15 days, Final L10-SA-06-03: SC CDR -30 days, Update

4.9

L10-SA-07 Master Electrical, Electronic, and Electromechanical (EEE) Parts List

L10-SA-07-01: I

L10-SA-07-02: I

L10-SA-07-03: I

L10-SA-07-04: I

L10-SA-07-05: I

L10-SA-07-01: SC SRR -30 days, Initial L10-SA-07-02: SC PDR -30 days, Update L10-SA-07-03: SC CDR -30 days, Update L10-SA-07-04: As Needed, Update L10-SA-07-05: SC EIDP, Final

4.9

L10-SA-08 Materials Identification and Usage List & Materials Usage Agreements

L10-SA-08-01: I

L10-SA-08-02: I

L10-SA-08-01: SC CDR, Initial L10-SA-08-02: SC EIDP, Final

4.9

L10-SA-09 Contamination Control Plan L10-SA-09: I L10-SA-09: SC PDR -30 days, Final 4.9 L10-SA-10 End Item Data Package (EIDP) L10-SA-10-01: A

L10-SA-10-02: A

L10-SA-10-01: OIRR -30 days, Final L10-SA-10-02: Observatory PSR -30 days, Final

4.9

4.0 DESCRIPTION OF REQUIRED DATA

4.1 PROGRAM MANAGEMENT DATA

CDRL No.: L10-PM-01 Title: Monthly Project Status Reviews Reference:

4.0 and 4.10.1 Related Documents:

Use:

To evaluate contract status. These reports and meetings will be used to provide an opportunity for face-to-face discussions between the Contractor and the Government regarding project status, plans and issues.

Preparation Information:

The Contractor shall prepare and deliver the following:

• Monthly accomplishments

• Technical progress status

• Flight Software (FSW) development status and any problem reports

• Requirements verification status

• Technical Performance Metrics summary, status and margins

• Class I changes/waivers status

• Anomaly and/or Material Review Board status and updates, including all non-conformances that affect form, fit and function

• Anomalous facility and hardware cleanliness conditions, if any

• Hardware qualification/acceptance status

• Top Risks and current mitigation status

• Supply chain issues

• Government-Industry Data Exchange (GIDEP) alerts and disposition

• Upcoming milestones and preparation status

• Contract deliverable status

• Organization breakdown structure to discipline level (for first Monthly Project Status Review (MPSR) only)

• Component procurement status, including status of subcontract awards

• Spare hardware status and any changes to nominal sparing plan

• Engineering/impact analyses progress (as applicable)

• Summary of current funding vs. contract cost, termination liability requirements, and projection of future funding requirements

• Security implementation updates/progress, security incident notification, mitigation, and resolution

• Class I and Class II changes

CDRL No.: L10-PM-02 Title: Inputs to Project Protection Plan Reference:

4.10.8 Related Documents:

• Space System Protection Standard, NASA-STD-1006

• NASA Space Security Best Practices Guide, SS BPG

• Department of Defense Contract Security Classification Specification, DD 254

• Landsat 10 Key Management Plan, L10-MGMT-PLAN-0039

• Landsat 10 Project Protection Plan (PPP), L10-SYS-PLAN-0027 Use:

Covers inputs to the Project Protection Plan, which describes how the mission is resilient to threats.

Preparation Information:

The Contractor shall provide inputs to the Landsat 10 Project Protection Plan (PPP), L10-SYS-PLAN-0027, which address the following:

• Saturation and damage thresholds of all on-board spacecraft sensors (Ref. Candidate Protection Strategy

(CPS) CPS-2)

• Threats evaluated in FMECA and other failure analysis and vulnerability results, with recommended mitigations (Ref. CPS-4)

• Backdoor or hardware commands that could adversely affect mission success, with recommended protections against malicious use (Ref. CPS-8)

• Assessment of external partner and internal network interconnections and data flows and protection level of information being processed (Ref. CPS-11)

• Risk assessment of space vehicle interfaces and connections (Ref CPS-13)

• Recommended and implemented details for the following NASA Space Security Best Practices, SS

BPG:

o MI-ARCH-02: Mission Least Privilege Function o MI-DCO-01: Mission Cyber Actor Actions Detection Function o MI-DCO-02: Mission Fault Management Function o MI-MA-01: Mission Recovery Function o MI-MA-02: Cybersecurity-Safe State Function o MI-MALW-01: Mission Malware Protection Function o MI-MALW-02: Mission Software, Programmable Logic Devices, and Firmware Integrity Function o MI-SOFT-02: Software and Hardware Testing Function

CDRL No.: L10-PM-03 Title: Contractor’s Review Plan

Table 4.10.7.2-1 Related Documents:

Use:

To provide the project insight and understanding of Contractor’s review planning, timing and approach.

Preparation Information:

The Contractor shall provide a Review Plan aimed at ensuring systematic evaluations at key project milestones for assessing readiness, identifying risks, and confirming alignment with contract objectives, to include the purpose, timing, objectives, and success criteria for each review.

CDRL No.: L10-PM-04 Title: Program Security Plan Supporting Documentation for Landsat 10 Assessment and Authorization and Security Requirements for Unclassified IT Resources

Reference:

4.10.8 Related Documents:

• NASA Information Security Policy, NPD 2810.1

• Security of Information and Information Systems, NPR 2810.1 Use:

The purpose of the Program Security Plan is to address operational security and Physical, Information/Information Technology (IT), Software, Personnel, and Industrial Security aspects of the program.

To ensure that IT security reporting requirements are met for all IT systems utilized during work associated with this contract and necessary training requirements are fulfilled.

Preparation Information:

The Contractor shall provide a Program Security Plan, to include:

• Describe the approach to identify in a timely and periodic manner, any cyber incidents.

• Describe the process to implement software updates/upgrades/patches and to check for malware prior to load.

• Describe the comprehensive cybersecurity approach to software development and software assurance across the development lifecycle (e.g. signed code, mature configuration management processes, static/dynamic code analysis, complexity checking, pen testing, threat modeling/testing, regular cross check of BOMs, including the use of Independent Verification & Validation or other 3rd party assessors).

• Describe the comprehensive approach to cybersecurity that includes the appropriate security controls for both the corporate infrastructure (including protection of sensitive information such as CUI), any development networks and the system(s) that are to be delivered as the spacecraft.

Distribution: Electronic Submission to the CO, COR, NASA Organization’s Information System Security Officer (ISSO) (i.e., Security Officer). Approval will be provided by the ISSO.

Initial Submission:

• IT Security Plan(s): For Contractor-owned systems, due at the start of phase-in. Initial submission not required for existing, approved plans for Government-owned and Contractor-managed systems.

• Non-Federal System Certification: Prior to any transfer of NASA non-public information to the contractor, the contractor shall provide documentation of the certification of the non-federal system to the security officer of the NASA organization that owns the information (typically the organization responsible for the contract).

• Information on Employees in Sensitive Positions/Assignments Report: At the start of phase-in

• IT Security Point of Contact: At the start of phase-in

• IT Security Awareness Training: Training required prior to access to NASA information and systems

• IT Security Role Based Training: Foundational training is provided prior to performance of assigned role. Initial evidence showing completion due at the end of phase-in.

Submission Frequency:

• IT security Plan(s): As Required

• Non-Federal System Certification: Annually

• Information on Employees in Sensitive Positions/Assignments Report: Annually

• IT Security Point of Contact: As Required

• IT Security Awareness Training: Annual on anniversary date of initial training

• IT Security Role Based Training: Annual on anniversary date of initial training. Evidence of completion due annually.

Format:

Unless otherwise directed, the data requested in this DRD shall be delivered to the Government in soft-copy via an electronic transfer mechanism (e.g., electronic mail, flash drive, or file transfer protocol) in a format readable by a Government device utilizing the standards in Minimum Interoperability Software Suite. NASA-STD-2804, “Minimum Interoperability Software Suite.”

Applicable Documents:

• Basic Safeguarding of Covered Contractor Information Systems, FAR 52.204-21

• Federal Acquisition Supply Chain Security Act Orders-Representation and Disclosures, FAR 52.204–29

• Federal Information Security Modernization Act 2014, FISMA 2014

• Security Requirements for Unclassified IT Resources, NFS 1852.204-76

• Major Breach of Safety or Security, NFS 1852.223-75

• Access to Sensitive Information, NFS 1852.237-72

• Release of Sensitive Information, NFS 1852.237-73

• Review of the Offeror’s Information Technology Systems Supply Chain, NFS 1852.239-73

• Information Technology System Supply Chain Risk Assessment, NFS 1852.239-74

• Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, NIST SP 800-

• Security and Privacy Controls for Information Systems and Organizations, NIST SP 800-53

• NASA Privacy Procedural Requirements, NPR 1382.1

• Information Security Policy, NPD 2810.1

• Security of Information and Information Systems, NPR 2810.1

• Controlled Unclassified Information, NPR 2810.7

• NASA Information Technology Program and Project Management Requirements, NPR 7120.7

• Management of Federal Information Resources, OMB Circular No. A-130 Scope:

All contracts that purchase, lease, network to, or otherwise utilize Government-funded IT (as defined by the Clinger-Cohen Act of 1996 and referenced by OMB Circular A-130) must comply with NASA IT Security Requirements.

Contents: The Federal Information Security Modernization Act (FISMA) and Executive Branch policy require external providers that process, store, or transmit federal information or operate information systems on behalf of the federal government to meet the same security and privacy requirements as federal agencies.

Information System Security Plan:

When the contractor is operating a Federal Information System (FIS) on behalf of NASA or is providing a FIS in the execution of this contract, that system must have an Information System Security Plan in accordance with Security and Privacy Controls for Information Systems and Organizations, NIST SP 800-53, at the revision number required at the issuance of the contract. This plan and supporting documents shall be entered into the NASA cybersecurity system of record pursuant to Authorization to Operate (ATO) requirements set forth in NASA Information Security Policy, NPD 2810.1, and NASA Security of Information and Information Systems, NPR 2810.1. The FIS security plan and ATO must be in place before any system may operate in the NASA environment.

Non-Federal System Security Certification :

When the contractor will receive, process, store or transmit NASA non-public information, especially Controlled Unclassified Information (CUI) including Personally Identifiable Information (PII) on a non-federal system (e.g., the contractor’s corporate system) the system must meet the requirements for data protections detailed in Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, NIST SP 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”

This documentation may take the form of:

a. A third-party review/audit certifying that the non-federal system meets the requirements of Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, NIST SP 800-171 or equivalent standard of information protection, such as the Information security, cybersecurity and privacy protections – Information security management systems – Requirements, ISO/EIC 27001 standard.

b. A certification from another federal agency such as the DOD Cybersecurity Maturity Model Certification (CMMC) Level 2.

Incident Notification:

The contractor shall report immediately upon notification any incident involving NASA information on nonfederal (contractor) systems to SOC@nasa.gov.

IT Security Point Of Contact:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and cybersecurity issues. The point of contact shall have the authority to ensure the immediate notification of the NASA Security Operations Center of any incident involving NASA information.

IT Security Awareness Training:

Contractor employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually. NASA Cybersecurity and Privacy Awareness training is available through the SATERN online system and must be completed prior to access to NASA information and systems. Completion of the training is tracked automatedly by NASA and must recur each year by the anniversary of the initial training as a condition of continued access. Cybersecurity and Privacy training is updated throughout the year as needed, so there is no defined training period.

IT Security Role Based Training:

Contractor employees subject to this contract shall complete NASA’s Foundational IT Security Training in SATERN related to the following role-based functions prior to performing the role:

• IT Security Manager

• Information System Owner (ISO)

• Information Systems Security Officer (ISSO)

• Information System Security Engineer (ISSE) It is highly recommended, but not required, that Contractor employees complete advanced role-based training every other year following completion of the initial training provided by NASA. This training is also provided by NASA but may be fulfilled externally. If fulfilled externally, the Contractor shall provide the “External Role- Based Training Validation Form” to the center CISO. The process for completing this form and receiving credit may be found at: External RBT Validation Form (sharepoint.com).

Informatoin On Employees In Sensitive Position(s)/Assignments Report:

The Information on Employees is Sensitive. IT Security (ITS) Positions/Assignments Report shall provide information annually for personnel screening as required by NPR 2810.1(series), and NPR 1600.1 on position risk.

Remarks:

None Maintenance:

Information System Security Plan(s) shall be kept up to date as changes to the baseline configuration of the system(s) occur.

CDRL No.: L10-PM-05 Title: Integrated Master Schedule (IMS)

4.10, 4.10.1, 4.10.2 Related Documents:

Use:

The purpose of the Integrated Master Schedule (IMS) is to track the spacecraft design, build, and I&T status over contract lifetime with a coherent, integrated scheduling tool.

Preparation Information:

The IMS shall be developed using the Critical Path Method scheduling technique. It will consist of the schedule baseline and the current schedule updated each reporting period. The IMS shall relate actual progress to the baseline and contain the current forecast for the remaining tasks. The IMS shall be delivered in MS Project format.

The IMS will be used to plan, monitor, communicate issues and control all activities, including pertinent resources and facilities necessary to accomplish assigned tasks in compliance with the Landsat 10 Spacecraft Statement of Work, (SC SOW), L10-SC-SOW-0006. The IMS will provide the contractor's time-phased plan, current status, key milestones, schedule reserve, task interdependencies, and major development phases necessary to accomplish the total scope of work.

Schedule will be used to provide management insight into contractor status, potential problem areas and critical path identification which will serve as the basis for evaluating contractor performance. The baseline IMS will be the basis for evaluating the impact of Government-directed changes to the launch date.

4.2 REVIEW DATA

CDRL No.: L10-RE-01 Title: Contractor’s Review Materials Reference:

4.10.7 Related Documents:

• Engineering Peer Reviews, GPR 8700.6 Use:

To provide review materials for design teams and Government to identify potential engineering design and implementation flaws, gain insight and increase the probability of meeting mission requirements and objectives.

Preparation Information:

The Contractor shall provide their review materials to include formal reviews and internal Engineering Peer Reviews. Engineering Peer Reviews, GPR 8700.6 may be used as a guide for Engineering Peer Reviews.

CDRL No.: L10-RE-02 Title: Inputs to Mission Level Reviews

4.10.7 Related Documents:

• Criteria for Flight and Flight Support System Lifecycle Reviews, GSFC-STD-1001 Use:

To capture info to support NASA required and led mission level reviews tied to Key Decision Points (KDPs) within the project development lifecycle.

Preparation Information:

The Contractor shall provide Inputs to Mission Reviews covering information as applicable on spacecraft subsystems, simulators, Ground Support Equipment (GSE), Observatory, testing, and pre- and post-launch operations support, for the Mission-level reviews per Landsat 10 Spacecraft Statement of Work (SC SOW), L10- SC-SOW-0006, Section 4.10.7.1., with the purpose, objectives, and criteria for successful completion of each review as specified in Criteria for Flight Project and Flight Support System Lifecycle Reviews for Flight Elements, GSFC-STD-1001.

CDRL No.: L10-RE-03 Title: On-Orbit Acceptance Review (OAR)

4.10.7 Related Documents:

Use:

Define the required content for the On-Orbit Acceptance Review (OAR) and determine if the Contractor has satisfied all contract requirements sufficient for the Government to take acceptance of the spacecraft/observatory and related systems.

Preparation Information:

The Contractor shall present the following at the OAR:

1. A timeline and summary of all events and commissioning activities following liftoff through the completion of on-orbit performance verification.

2. Comparisons if predicted and indicated performance of the Observatory for each event/activity.

3. Summary of all performance discrepancies, their impact on the mission, and their closure status.

4. Description of any in-flight anomalies, actions taken to resolve/recover and current status.

5. Summary of major changes made to FSW, procedures or other on-board configurations since launch.

6. On-orbit Requirement verification and validation status

7. On-orbit trending data and any recommended changes for trending through End of Life

8. Discussion of open items and deliverable status

4.3 SOFTWARE DATA

CDRL No.: L10-SW-01 Title: Software Management and

Development Plan (SMDP) Reference:

4.11.6.3 Related Documents:

• NASA Software Engineering Handbook, NASA-HDBK-2203 Use:

The Software Development and Management Plan is used to provide insight into, and is a tool for monitoring, the processes to be followed for software development, the methods to be used, and the approach to be followed for each activity. This plan details the system software, project documentation, project schedules, resources requirements and constraints, and general and detailed software development activities.

Preparation Information:

The Contractor shall provide a Software Development and Management Plan to include:

A. Description of the system software, project documentation, project schedules, resources requirements and constraints, software assurance, software metrics, and software development activities.

B. Description of software engineering environment for development, test, operation and maintenance of the software C. Management of software safety, security and privacy D. Secure coding and cybersecurity related design, analysis, risk assessment, and testing activities and policies E. Description of software verification & validation environments, methods, criteria, corrective action and verification F. Discussion of the software life-cycle model, including description of software integration and hardware/software integration processes, software delivery, maintenance, software updates and patching G. Management, development, and testing approach for handling any commercial-off-the-shelf (COTS), Government-off-the-shelf (GOTS), modified-off-the-shelf (MOTS), and reused software. This shall include an analysis of unreachable code for any software associated with space flight operation.

H. Description of software configuration management system I. Plan for and tracking of operational backup software J. Approach for the implementation of modifications to operational software K. Software peer review/inspection process of software work products, including independent review

CDRL No.: L10-SW-02 Title: Software Architectural and Detailed Design Description (SDD)

Reference:

4.11.6.3 Related Documents:

• NASA Software Engineering Handbook, NASA-HDBK-2203 Use:

The Software Design Description is used to understand the design of a Computer Software Configuration Item (CSCI), its architectural design, CSCI-wide design decisions, and the detailed design needed to implement the software.

Preparation Information:

The Contractor shall provide a Software Design Description to include:

A. CSCI architectural design.

B. CSCI decomposition and interrelationship between components:

1. CSCI components:

a. Description of how the software item satisfies the software requirements, including algorithms, data structures, and functional decomposition.

b. Software item Input/Output (I/O) description.

c. Static/architectural relationship of the software units.

d. Concept of execution, including data flow, control flow, and timing.

e. Requirements, design, and code traceability.

f. CSCI's planned utilization of computer hardware resources.

2. Rationale for software item design decisions/trade decisions including assumptions, limitations, safety and reliability related items/concerns or constraints in design documentation. For consistency, ensure that security and safety are included together throughout the document.

3. Interface design.

CDRL No.: L10-SW-03 Title: Software Version Description Document

Reference:

4.11.6.3 Related Documents:

Use:

The software version description document is used to release, track, and control a software version.

Preparation Information:

The Contractor shall provide a software delivery package to include the following information:

A. Full identification of the system and software (e.g., numbers, titles, abbreviations, version numbers, and release numbers).

B. Source files (include any tables, text files, MatLab files, etc. used during auto-code).

C. Software product files (any files needed to install, build, operate, and maintain the software).

D. Executable software…