Attachment D - Data Procurement Document.pdf

ATTACHMENT D

MARS TELECOMMUNICATIONS NETWORK

DATA PROCUREMENT DOCUMENT

APRIL 28, 2026

RFP NUMBER: 80GSFC26R0011

CONTRACT NUMBER: TBD

MTN Data Procurement Document MTN-MGMT-CDRL-0001, Rev A

Effective Date: 04/28/2026 ii

Check https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

MTN-MGMT-CDRL-0001, Revision A

Mars Telecommunications Network

Mars Telecommunications Network (MTN)

Data Procurement Document

GSFC MTN CMO

April 28, 2026

Released https://ipdtdms.gsfc.nasa.gov/ iii

Change History Log

Revision Effective Date Description of Changes

- 03/19/2026 Initial Release

A Updated DRD-SE-03 (added callout for science payloads)

Updated DRD-SE-09 (added callout for science payloads)

Updated terminology throughout document to use calendar days in all locations instead of working days to be consistent with project contractual documents. DRD revision did not roll if this was the only change.

Updated DRD-SE-04 (added specificity for the minimum ground test unit deliverables)

Updated DRD-SE-15 (per MTN-PCB-0007)

Updated Reference (NFS 1852.240-76) in DRD-PM-07

Updated DRD-PM-01 (per MTN-PCB-0005)

Updated DRD-SE-09 (per MTN-PCB-0005)

Updated DRD-SE-17 (per MTN-PCB-0005)

Updated DRD-SE-18 (per MTN-PCB-0005)

Updated DRD-SE-19 (per MTN-PCB-0005)

Updated DRD-SE-20 (per MTN-PCB-0005)

Updated DRD-SW-02 (per MTN-PCB-0005)

Updated DRD-FO-01 (per MTN-PCB-0005)

Updated DRD-FO-02 (per MTN-PCB-0005)

Added DRD-FO-04 (per MTN-PCB-0005)

Updated DRD-COM-01 (per MTN-PCB-0009)

Updated DRD-COM-02 (per MTN-PCB-0009)

Updated DRD-COM-03 (per MTN-PCB-0009) iv

Table of TBDs/TBRs/TBSs

Action Item

No.

Location Summary Individual/

Organization

Actionee v

Table of Contents

1 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Applicability

1.4 Data Types for Contractual Efforts

2 REFERENCE AND APPLICABLE DOCUMENTS

2.1 Applicable Documents

2.2 Reference Documents

3 LEVERAGING OF CONTRACTOR BEST PRACTICE/INTERNAL DATA

DELIVERABLES

3.1 Electronic Format

3.2 Hardcopy Format

4 DATA REQUIREMENTS LIST

5 DATA REQUIREMENTS DESCRIPTIONS

5.1 Data Requirements Description DRD-PM-01 (Project Management Plan)

5.2 Data Requirements Description DRD-PM-02 (Integrated Master Schedule)

5.3 Data Requirements Description DRD-PM-03 (Management Review Packages)

5.4 Data Requirements Description DRD-PM-04 (Configuration and Data Management Plan)

5.5 Data Requirements Description DRD-PM-05 (Risk Management Plan and Risk

Management Reports)

5.6 Data Requirements Description DRD-PM-06 (Major Review Plans and Documentation)

5.7 Data Requirements Description DRD-PM-07 (Information Technology Security

Management Plan)

5.8 Data Requirements Description DRD-PM-08 (Insight and Oversight Implementation

Plan)

5.9 Data Requirements Description DRD-MD-01 (Mission Design Plan /Concept of

Operations)

5.10 Data Requirements Description DRD-MD-02 (Mission Design Document)

5.11 Data Requirements Description DRD-SE-01 (System Requirements)

5.12 Data Requirements Description DRD-SE-02 (System Specification)

5.13 Data Requirements Description DRD-SE-03 (Interface Control Documents and

Drawings)

5.14 Data Requirements Description DRD-SE-04 (Hardware Deliverable List)

5.15 Data Requirements Description DRD-SE-05 (Acceptance Data Package of Delivered

Hardware)

5.16 Data Requirements Description DRD-SE-06 (Environmental Requirements Document) 40

5.17 Data Requirements Description DRD-SE-07 (Design Data Book)

5.18 Data Requirements Description DRD-SE-08 (Spacecraft Performance and System

Resource Budget Reports)

5.19 Data Requirements Description DRD-SE-09 (Assembly, Integration and Test Plan)

5.20 Data Requirements Description DRD-SE-10 (Verification & Validation Plan) vi

5.21 Data Requirements Description DRD-SE-11 (Test Plans and Procedures)

5.22 Data Requirements Description DRD-SE-12 (Test Reports)

5.23 Data Requirements Description DRD-SE-13 (Verification Closure Notices and

Validation Closure Notices/Requirements Verification Traceability Matrix)

5.24 Data Requirements Description DRD-SE-14 (Drawing and Document Trees)

5.25 Data Requirements Description DRD-SE-15 (Engineering Drawings, Models, and

Associated Lists)

5.26 Data Requirements Description DRD-SE-16 (Design and Construction Standards

Utilized)

5.27 Data Requirements Description DRD-SE-17 (Structural Analysis Reports)

5.28 Data Requirements Description DRD-SE-18 (Thermal Analysis Reports)

5.29 Data Requirements Description DRD-SE-19 (Power Analysis Report and Battery Usage

Assessment)

5.30 Data Requirements Description DRD-SE-20 (Electromagnetic Interference (EMI)

Electromagnetic Compatibility (EMC) Control Plan)

5.31 Data Requirements Description DRD-SE-21 (Worst Case Analysis)

5.32 Data Requirements Description DRD-SW-01 (Software Requirements Specification)... 65

5.33 Data Requirements Description DRD-SW-02 (Master Data Dictionary)

5.34 Data Requirements Description DRD-SW-03 (Software Management and Development

Plan)

5.35 Data Requirements Description DRD-SW-04 (Software Design Description/Version

Description Document)

5.36 Data Requirements Description DRD-SMA-01 (Request for Deviation or Waiver)

5.37 Data Requirements Description DRD-SMA-02 (Safety and Mission Assurance (S&MA)

Plan)

5.38 Data Requirements Description DRD-SMA-03 (Safety Data Package (SDP))

5.39 Data Requirements Description DRD-SMA-04 (Failure Modes and Effects Analysis and

Critical Items List / Single Point Failure)

5.40 Data Requirements Description DRD-SMA-05 (EEE Parts Management Plan)

5.41 Data Requirements Description DRD-SMA-06 (Parts Identification List)

5.42 Data Requirements Description DRD-SMA-07 (Parts Stress/De-Rating Analysis)

5.43 Data Requirements Description DRD-SMA-08 (Radiation Tolerance Report)

5.44 Data Requirements Description DRD-SMA-09 (Nonconformance Processing and

Corrective Action Plan and Nonconformance Reports)

5.45 Data Requirements Description DRD-SMA-10 (Materials Identification and Usage

List/Material Usage Agreement)

5.46 Data Requirements Description DRD-SMA-11 (Planetary Protection Plan)

5.47 Data Requirements Description DRD-SMA-12(Safety Requirements Compliance

Checklist (SRCC))

5.48 Data Requirements Description DRD-COM-01 (Communication System Analysis Report

(DWE))

5.49 Data Requirements Description DRD-COM-02 (Communication System Analysis Report

(UHF Proximity))

5.50 Data Requirements Description DRD-COM-03 (Communication System Analysis Report

(Advanced Proximity)) vii

5.51 Data Requirements Description DRD-COM-04 (Spectrum Management and Compliance

Information)

5.52 Data Requirements Description DRD-FO-01 (Operations Data Book)

5.53 Data Requirements Description DRD-FO-02 (Flight Operations Procedures and

Procedures Data)

5.54 Data Requirements Description DRD-FO-03 (Mission Operations Plans)

5.55 Data Requirements Description DRD-FO-04 (Spacecraft Telemetry Database and Data)

Appendix A Abbreviations and Acronyms viii

List of Tables

Table 1 Data Types Description

1 INTRODUCTION

Consistent with law, the National Aeronautics and Space Administration (NASA) is working toward a high-performance Mars telecommunications orbiter(s), capable of providing assets in and around Mars with robust, continuous communications with Earth.

1.1 Purpose

The purpose of this document is to define the data requirements that shall be delivered to the

Government for the contracted work performed on the Mars Telecommunications Network

(MTN) Project. The document provides descriptions, submission timeline, contents, and formats.

Throughout the project lifecycle, the MTN Project will gather information via technical insight and the data deliverables described herein are one aspect of how NASA MTN will obtain that information. These data deliverables are necessary to ultimately accept hardware fabricated for this project and make risk informed decisions throughout.

1.2 Scope

Subject to the Rights in Data clause, 52.227-14 Rights in Data-General (MAY 2014), this Data

Procurement Document (DPD) sets forth the data requirements in each Data Requirements

Description (DRD) and shall govern that data required by the DPD for the contract. The

Contractor shall furnish data defined by the DRDs listed on the Contract Data Requirements List

(CDRL) by category of data, attached hereto, and made a part of this DPD. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this DPD. In cases where data requirements are covered by a Federal Acquisition

Regulation (FAR) or NASA FAR Supplement (NFS) clause, that clause shall take precedence over the DPD, consistent with clause FAR 52.215-8 Order of Precedence—Uniform Contract

Format (OCT 1997).

1.3 Applicability

This data procurement document is applicable to the contracted work performed on the MTN

Project.

1.4 Data Types for Contractual Efforts

The types of data and their contractually applicable requirements for approval and delivery are:

Type Description

1 NASA reserves a time-limited right to disapprove in writing any versions and interim changes to those versions. The data shall be delivered to NASA for review not less than 30 calendar days prior to its release for use or implementation. The Contractor shall clearly identify the release target date in the “submitted for review” transmittal. If the Contractor has not been notified of any disapproval prior to the release target date, the data shall be considered approved. To be an acceptable delivery, disapproved data shall be revised to remove causes for the disapproval before its release.

2 NASA reserves a time-limited right to disapprove in writing any versions and interim changes to those versions. The data shall be delivered to NASA for review not less than 14 calendar days prior to its release for use or implementation. The Contractor shall clearly identify the release target date in the “submitted for review” transmittal. If the Contractor has not been notified of any disapproval prior to the release target date, the data shall be considered approved. To be an acceptable delivery, disapproved data shall be revised to remove causes for the disapproval before its release.

3 These data shall be delivered by the Contractor as required by the contract and do not require

NASA approval. NASA may submit comments or questions on these documents for clarification or assistance with understanding of the DRD for the Contractor to consider.

However, to be a satisfactory delivery, the data shall satisfy all applicable contractual requirements.

Table 1 Data Types Description

2 REFERENCE AND APPLICABLE DOCUMENTS

2.1 Applicable Documents

Applicable documents are those documents that form a part of this document. These documents carry the same weight as if they were stated within the body of this document.

Document Number Document Title Revision

NASA STD-871927 Implementing Planetary Protection Requirements for

Spaceflight

2.2 Reference Documents

Reference documents are those documents that, though not a part of this document, serve to clarify the intent and contents of this document.

Document Number Document Title Revision

NFS 1852.240-76 Security Requirements for Unclassified Information

Technology Resources

NASA-STD-6016 Standard Materials and Processes Requirements for

Spacecraft

C

NASA-STD-8739.14 NASA Fastener Procurement, Receiving Inspection, and

Storage Practices for NASA Mission Hardware

NASA-STD-8739.8 Software Assurance and Software Safety Standard

NASA-STD 8719.24 NASA Payload Safety Requirements A

MSFC-STD-3029 Guidelines for the Selection of Metallic Materials for Stress

Cracking Resistance in Sodium Chloride Environments

A

MTN-402-REQ-0001 Mars Telecommunications Network (MTN) Objectives and

Requirements Document

NASA STD-871927 Implementing Planetary Protection Requirements for

Spaceflight

NPR 7120.5 NASA Space Flight Program and Project Management

Requirements

F

NPR 7123.1 NASA System Engineering Processes and Requirements D

CCSDS 133.0-B-2 CCSDS Space Packet Protocol

CCSDS 660.0-B-2 CCSDS XML Telemetric and Command Exchange (XTCE)

CCSDS 301.0-B CCSDS Time Code Format

CCSDS 502.0-B CCSDS Orbit Data Messages (OEM/OMM/OPM)

CCSDS 503.0-B CCSDS Tracking Data Message (TDM)

CCSDS 521.0-B CCSDS Mission Operations — Monitor and Control

IETF RFC 8949 Concise Binary Object Representation (CBOR)

IETF RFC 8610 Concise Data Definition Language (CDDL)

3 LEVERAGING OF CONTRACTOR BEST PRACTICE/INTERNAL DATA

DELIVERABLES.

Unless otherwise noted in this or other superseding documents, data products and documentation produced by the offeror through existing internal practices may be used to satisfy any number of data requirements described herein (to the extent practicable) granted that:

1. The supplier clearly communicates traceability to the data deliverables being satisfied by each submission and,

2. The NASA MTN reviewer concurs that the submission adequately satisfies the intent of required deliverable in question.

The DRD will call out any special format requirements if necessary. General format requirements for electronic and hardcopy are as follows. Note that the “pages” field of each DRD entry indicates how many pages are in each DRD description of this DPD; they do not indicate pages associated with submission.

3.1 Electronic Format

DRDs shall be delivered in their native format unless otherwise specified by the DRD or the Contracting

Officer. A preferred format for each delivery item may be specified in the DRD, but the Contractor may utilize an alternative at the discretion of the CO.

Structured data delivered in satisfaction of a DRD is preferred to be in an open-source and standards-compliant format; proprietary file formats are acceptable, but each proprietary format submission shall include:

1. A definition of the application (including version) that produced the file.

2. The native proprietary file itself.

3. A commonly readable representation of the file (e.g. PNG or PDF).

If native file formats are not readable by COTS software and at the discretion of the CO, the Contractor may deliver the application (source code and executable) required in order to read the native format.

In general, files provided in an electronic format shall meet five basic requirements: “human readable”, “machine readable”, “text searchable”, “printable”, and “downloadable” utilizing publicly available COTS software.

3.2 Hardcopy Format

Hardcopy submission of DRDs is necessary only at the discretion of the CO; in general, the Government shall accept electronic delivery of all data products.

4 DATA REQUIREMENTS LIST

Unless otherwise noted, days denote calendar days

P-Preliminary B-Baseline

F-Final ATP-Authority to Proceed

DRD Number DR Title Type Preliminary Design

Phase Detailed

Design Phase

Fabrication, Build, Assembly & Test Phase

Launch Vehicle

Integration & Post- Launch Phase Frequency

DRD-PM-01 Project Management Plan 2 P-60 Days After ATP B-End of Phase

Update Upon Revision

DRD-PM-02 Integrated Master Schedule (IMS) 3 P-30 Days After ATP B-90 Days After ATP

Update Monthly

DRD-PM-03 Management Review Packages 3 Monthly

DRD-PM-04 Configuration and Data Management Plan 3 P-30 Days After ATP B-End of Phase

Update Upon Revision

DRD-PM-05 Risk Management Plan and Risk Management Reports 3 P-60 Days After ATP B-End of Phase

Risk reports Monthly

DRD-PM-06 Major Review Plans and Documentation 3 Plan-30 days before review Documentation-14 days before review

DRD-PM-07 Offeror's IT Security Management Plan 2 B- 6 Months After ATP Update Upon Revision

DRD-PM-08 Insight and Oversight Implementation Plan 2 B-60 Days After ATP Update Upon Revision

DRD-MD-01 Mission Operations Plan/ConOps 1 P-60 Days After ATP B-End of Phase

U U U Updated at Major Milestones

DRD-MD-02 Mission Design Document 2 B-End of Phase U U U Updated at Major Milestones

DRD-SE-01 System Requirements 1 B-End of Phase U U U Updated at Major Milestones

DRD-SE-02 System Specification 2 B-End of Phase U U U Updated at Major Milestones

DRD-SE-03 Interface Control Documents and Drawings (ICDs) 2 B-End of Phase F-End of Phase

DRD-SE-04 Hardware Deliverable List 3 B-60 Days After ATP F-End of Phase

DRD-SE-05 Acceptance Data Package of Delivered Hardware 1 P-30 Days prior to Pre-Ship Review F-30 Days prior to Acceptance Review

DRD-SE-06 Environmental Requirements Document 2 B-End of Phase Update Upon Revision

DRD-SE-07 Design Data Book 2 P-End of Phase U U F-30 Days prior to Acceptance Review

DRD-SE-08 Spacecraft Performance and System Resource Budget Reports 3 B-End of Phase U U F-30 Days prior to Acceptance Review

DRD-SE-09 Assembly, Integration and Test (AI&T) Plan 2 P-End of Phase B-End of Phase

DRD-SE-10 Verification & Validation Plan 2 B-End of Phase U U U Updated at Major Milestones

DRD-SE-11 Test Plans and Procedures 3 B-With Test Readiness Review data Package F-Within 14 Days of Test Completion

DRD-SE-12 Test Reports 3 F-Within 30 Days of Test Completion

DRD-SE-13 Verification Closure Notices and Validation Closure Notices/Requirements Verification Traceability Matrix

2 P-End of Phase U U P-5 days after event (Notices) F-30 days after event(Notices) F-30 days prior to Acceptance Review (Matrix)

DRD-SE-14 Drawing and Document Trees 3 P-End of Phase B-End of Phase Update Upon Revision

DRD-SE-15 Engineering Drawings, Models, and Associated Lists 3 30% 90% F-End of Phase

DRD-SE-16 Design and Construction Standards Utilized 3 B-End of Phase F-End of Phase

DRD-SE-17 Structural Analysis Reports 3 P-End of Phase B-End of Phase F-End of Phase

DRD-SE-18 Thermal Analysis Reports 3 P-End of Phase B-End of Phase F-End of Phase

Unless otherwise noted, days denote calendar days

P-Preliminary B-Baseline

F-Final ATP-Authority to Proceed

DRD Number DR Title Type Preliminary Design

Phase Detailed

Design Phase

Fabrication, Build, Assembly & Test Phase

Launch Vehicle

Integration & Post- Launch Phase Frequency

DRD-SE-19 Power Analysis Report and Battery Usage Assessment 3 P-End of Phase B-End of Phase

DRD-SE-20 Electromagnetic Interference (EMI) Electromagnetic Compatibility (EMC) Control Plan 3 B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SE-21 Worst Case Analysis 3 B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SW-01 Software Requirements Specification (SRS) 3 P-End of Phase B-End of Phase

DRD-SW-02 Master Data Dictionary 3 P-End of Phase B-End of Phase

DRD-SW-03 Software Management and Development Plan 3 P-End of Phase F-End of Phase

DRD-SW-04 Software Design Description/Version Description Document 3 P-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SMA-01 Request for Deviation or Waiver 1

As Needed

DRD-SMA-02 Safety and Mission Assurance (S&MA) Plan 2 P-End of Phase B-End of Phase Update Upon Revision

DRD-SMA-03 System Safety Analysis Report 2 P-End of Phase B-End of Phase F-Within 90 Days of Pre-Ship Review

DRD-SMA-04 Failure Modes and Effects Analysis and Critical Items List / Single Point Failure 2 P-End of Phase B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SMA-05 EEE Parts Management Plan 3 P-End of Phase B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SMA-06 Parts Identification List 3 P-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SMA-07 Parts Stress/De-Rating Analysis 3

DRD-SMA-08 Radiation Tolerance Report 3

DRD-SMA-09 Nonconformance Processing and Corrective Action Plan and Nonconformance Reports 2

Reports as Needed

DRD-SMA-10 Materials Identification and Usage List/Material Usage Agreement 3 P-End of Phase B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-SMA-11 Planetary Protection Plan 2

DRD-SMA-12 Safety Requirements Compliance Checklist (SRCC) 2

DRD-COM-01 Communication System Analysis Report (DWE) 2

DRD-COM-02 Communication System Analysis Report (UHF Prox) 2

DRD-COM-03 Communication System Analysis Report (Advanced Prox) 2

DRD-COM-04 Spectrum Management and Compliance Information 2 P-End of Phase B-End of Phase F-Within 30 Days of Pre-Ship Review

DRD-FO-01 Operations Data Book/User Guide 2 P-End of Phase U U F-30 Days prior to Acceptance Review

DRD-FO-02 Flight Operations Procedures and Procedures Data 2 P-End of Phase B-End of Phase

DRD-FO-03 Mission Operations Plans 2 P-End of Phase B-End of Phase

DRD-FO-04 Spacecraft Telemetry Database and Data 3 P-End of Phase Upon Update/Receipt of Telemetry

5 DATA REQUIREMENTS DESCRIPTIONS

5.1 Data Requirements Description DRD-PM-01 (Project Management Plan)

Program: MTN DRD No.: DRD-PM-01

Data Type: 2 Date Revised: 4/23/2026

Pages: 3

Title: Project Management Plan (PMP)

Description/Use: To describe the overall scope of the project and the implementation approach, including the systems, processes and methods, to provide overall coordination of management activities and plans for accomplishing the Contractor Performance Work Statement (PWS). The PMP also describes the structure and environment within which the contract and subcontract(s) operate.

Initial Submission: Preliminary 60 days after Authority to Proceed (ATP).

Submission Frequency: Baseline version no later than end of Preliminary Design Phase and update as required afterward.

Remarks:

Contents: The PMP shall provide a description of the Contractor’s management concepts, practices, approaches, plans, and schedules necessary for accomplishing (managing and controlling) the tasks described in the contractor PWS. The PMP shall present those management systems to be utilized to define and delegate task assignments and shall define the roles and organizational relationships of the Contractor, Subcontractors, and Government. The PMP shall cover all aspects of contract and subcontract management for the contract. The PMP shall provide information giving the Government insight into staffing, organizational structure, approaches and processes used to manage activities across the contract. The PMP shall describe the methods the contractor will employ to provide Government data accessibility and deliverables.

The PMP shall identify and describe Control Plans that will be used in executing the PWS tasks. Control plans can either be a part of the PMP or separate stand-alone documents referenced in the appropriate part of the PMP.

In addition to the information described above, the PMP shall include, at a minimum, the following items:

1. Descriptions of the management approaches used to accomplish and monitor contractor and subcontractor tasks.

2. Description of roles and responsibilities of the Contractor’s key personnel.

3. Contractor Systems Engineering processes and tools used to implement the technical effort and document the overall technical approach, maintain integrity between NASA and Contractor requirements to the Contractor verification plans, and to transition the products through the lifecycle

(for both Contractor and subcontractor efforts).

4. Management approach to routinely review and address schedule, technical progress, concerns, and issues.

5. Description of major technical and milestone reviews, their purpose, and performance reporting to

NASA in preparation for these reviews.

6. Communication Plan, including but not limited to a description of the overall interaction policy and approach, key interaction milestones, flexibility and adaptability of interactions, the process for continuous improvement and incorporations of lessons learned, and determination and implementation of cause and corrective actions.

7. Approach to interfaces with the Government, other Contractors, and/or other entities that are necessary and pertinent to the accomplishment of contractual tasks, including such things as data, analyses, equipment, software deliverables, schedules, interfaces, and other technical/managerial interactions.

8. Approach to the establishment and management of subcontracts.

9. Description of the Contractor’s acquisition strategy, including make/buy decisions and rationale.

10. Description of facility usage in support of the contract.

11. Performance Assessment Plan including, at a minimum:

a. Definition of performance assessment metrics that will be used to communicate to NASA the progress of the Contractor’s efforts against the project baseline plan.

b. Description of management systems and processes used to implement the plan including the developing, timely gathering, compiling, maintaining, auditing, analyzing, reporting, and providing management review of performance metrics.

c. Description of the Technical Performance Parameters (TPPs) selected for monitoring during the design and development.

12. Schedule performance reporting plans which include schedule reserves.

13. Discuss approach to data rights and intellectual property (IP). Identify any limited data rights or restricted computer software issues, especially in the context of what the various corporate team members will provide. Explain how licensing agreements will be negotiated with vendors and how that data/IP will be treated, specifically identifying any requested special license agreements.

14. Define the Contractor Work Breakdown Structure (CWBS) which is a logical, hierarchical display of the subdivision of all project work to be completed. The CWBS shall include the approved element title and element number. The Contractor will use the CWBS to internally track program schedule and technical performance. The CWBS shall also be used when reporting technical and schedule performance to NASA.

15. Provide a CWBS Dictionary which may be a standalone document or an appendix to this plan. The

CWBS dictionary shall describe and document the work content of every CWBS element and relevant efforts associated with each element (e.g., design, development, and manufacturing). The

CWBS dictionary shall be arranged in the same order as the contract CWBS. The CWBS dictionary shall include the following for each CWBS element:

a. CWBS element title.

b. CWBS element code.

c. CWBS element content description (including quantities, relevant associated work, and contract end items where applicable).

d. CWBS Index.

e. PWS paragraph number.

f. Specification (number and title) associated with the CWBS element (if applicable).

g. Contract line item associated with the CWBS element.

h. Date, revision number, revision authorization and approved changes.

i. Contract Identification Number.

NOTE: It is not intended that this plan duplicate other plans called for in the Data Requirements List. This plan shall summarize the overall project and reference or summarize other plans where appropriate and shall reference Contractor internal procedures where applicable.

Format: Contractor’s format is acceptable.

End of Data Requirements Description DRD-PM-01

5.2 Data Requirements Description DRD-PM-02 (Integrated Master Schedule)

Program: MTN DRD No.: DRD-PM-02

Data Type: 3 Date Revised: Initial Release

Pages: 2

Title: Integrated Master Schedule (IMS)

Description/Use: The IMS is the primary means of communicating project schedule information between the prime Contractor and the Government. The IMS shall use established standard processes, data structures and reporting conventions to plan, manage, and report the work required in the performance of this contract.

Initial Submission: Preliminary 30 days after ATP.

Submission Frequency: Monthly within 7 calendar days after the close of the Contractor’s accounting month. IMS shall be baselined no later than 90 days after ATP.

Contents: The IMS shall include all contractor milestones, activities, and tasks leading to and including all phases through MTN End of Mission (EOM). The IMS shall track and show percentage completion of all tasks. The IMS shall provide the ability to fully identify, analyze, mitigate and control scheduling risks and impacts; accurately identify and analyze critical path activities; clearly show schedule float (margin);

and allow its users to easily measure the progress towards achieving MTN milestones.

Tasks and milestones from subcontractors shall be included with sufficient detail to develop a realistic critical path. Their data shall be consistent, statused monthly, and based on the same cutoff date to enable a realistic critical path.

Along with the IMS monthly deliverables, the Contractor shall provide a narrative description of any significant schedule variances or slips since the last month and the root cause of those slips and options for recovery of that time in the remaining work left on the schedule. The narrative shall also track the status of previously reported variances or slips and the progress made to resolve them. Schedule variances or slips that impact the critical path shall be part of this narrative. Any other variances or slips that are of concern to the Contractor and/or have to potential to impact the critical path in the future should also be reported at the discretion of the Contractor.

Relationships/Dependencies: All discrete tasks/milestones except for the start and end of the contract or for interim receipt and delivery events to/from external entities shall have at least one predecessor and successor.

Schedule Margin: If schedule margin is included in the IMS, it must be as a defined task and clearly labeled as “Schedule Margin” or contingency. The number of schedule margin tasks should be minimal with most of the margin duration placed as the last task before the ending contract event. Other acceptable locations for placing smaller amounts of schedule margin are prior to high level project milestones.

Additionally, at a minimum, the IMS shall be formatted with the largest increment of time being measured in units of months.

Summary Master Schedule: The schedule shall include a top level Gantt chart summary arranged by WBS and that reflects all contract and controlled milestones, major program/project phases (i.e. design, fabrication, integration, assembly, test, etc.) and all end-item deliveries. It shall reflect, either by manual creation or by automated summarization, a vertically integrated rollup of intermediate and detailed schedule data.

Format: IMS shall be provided in Microsoft Project file format.

End of Data Requirements Description DRD-PM-02

5.3 Data Requirements Description DRD-PM-03 (Management Review Packages)

Program: MTN DRD No.: DRD-PM-03

Title: Management Review Packages

Description/Use: To establish activity reporting for the Contractor’s progress and accomplishments. The

Management Review packages support the monthly management reviews of schedule and technical performance between the Contractor and NASA.

Initial Submission: 12 days after the close of the contract month that is subsequent to the month in which the post-award kick-off occurs.

Submission Frequency: Monthly within 5 business days after the close of the Contractor’s accounting month.

Remarks: Management reviews shall be held monthly, face to face management reviews should be held bi-monthly at the Contractor’s facility, Contents: The Management Review data packages support monthly reviews of schedule and technical performance. Metrics that effectively indicate the level of success in the execution of contract requirements and the status of the Contractor’s achievements shall be presented at the review. The Technical

Performance Parameters shall be reported by the Contractor to status their margin growth/loss. All metrics shall be developed and defined by the Contractor with concurrence from the Government. The format provides a standardized approach for review materials.

The monthly Review package shall include, at a minimum:

1. Summary Section

a. Pertinent Performance/Outcome Based metrics

b. Technical Performance Parameters (including margin growth/loss and forecast)

c. Stoplight Status of schedule, and technical performance.

d. Status of risks and opportunities.

e. Cumulative variance explanations (to fiscal year plan) and End-Of- Year trend variance explanations (if threshold criteria exceeded).

f. Performance Work Statement Reconciliation (i.e., Special Projects, etc. that need to be accounted for) (as required)

g. Status of DRDs that are due in the next 90 days

h. Areas of Emphasis Summary

i. Major Contract Milestone Schedule - 90 Day

2. Component Sections (done at major subsystem level):

a. Include all Summary Section items.

b. Accomplishments

c. Pertinent Next Level Performance/Outcome Based metrics (include any other Yellow or

Red metrics)

d. Details of Technical and schedule issues, risks and opportunities

e. Status of document and drawing release/approval as well as engineering change reports.

3. Safety and Mission Assurance General

S&MA Status:

a. Status of significant activities relating to the accomplishments of the PWS S&MA tasks.

Risks to the accomplishment of PWS tasks shall also be identified.

b. S&MA key issues and concerns, including impact, action plan (including any NASA help needed), and projected resolution date.

Detailed content related to S&MA disciplines reliability, EEE parts, quality assurance, materials and processes, system safety, and software assurance:

a. Status of analyses with traceability to assembly/subsystem/system

b. Summary of all activities for that period to include issues/resolutions, analyses results, test results, nonconformances, failures, anomalies, waiver/deviations, audits & findings, mishaps, and quality metrics (including software)

c. Summary of upcoming activities for the next period

d. Status of corrective actions and open items

Format: Contractor’s format is acceptable

End of Data Requirements Description DRD-PM-03

5.4 Data Requirements Description DRD-PM-04 (Configuration and Data Management Plan)

Program: MTN DRD No.: DRD-PM-04

Title: Configuration and Data Management Plan (CDMP)

Description/Use: To describe the Contractor's method for accomplishing the configuration and data management requirements of the contract.

Initial Submission: Preliminary 30 days after ATP.

Submission Frequency: Baseline version no later than end of Preliminary Design Phase and update as required afterward.

Remarks: This DRD may be satisfied by inclusion of required content in DRD-PM-01 PMP submissions. There is no requirement for a separate, stand-alone document.

Contents: NOTE: For this DRD, a Contractor's standard document can be submitted if it meets the intent of the content requirements of this deliverable.

The CDMP shall provide a section that defines the Contractor’s data management approach. The data management section shall include, at a minimum:

1. Relationship of the Contractor’s management, organization and planning to the data management program and the Contractor's other administrative and technical organizations.

2. Configuration Management Planning; Configuration Identification, which includes Interface

Management; Configuration Change Control; Configuration Status Accounting, which includes

Traceability; Configuration Verification and Audits; and Technical Data Management.

a. Configuration status accounting system shall provide information defining the as-designed and as-built configuration of the system and the status of changes to this configuration, provide traceability of changes to controlled products, serve as the basis for communicating accurate and timely status of all Configuration Items, and ensure the delivered documentation accurately describes and represents the associated Configuration Items.

3. Integration of the CM and DM systems across all pertinent project elements such as modeling and simulation, manufacturing, operations, quality, as well as acquisition organizations including customer and vendor Configuration and Data Management (CDM) systems.

4. Specific management policies, practices and work instructions to be used in implementing the data management program include the following elements:

a. Control procedures including management of MTN project directives and change control

b. Storage and retrieval procedures

c. Subcontractor control procedures

d. Special restrictions

e. Government access to data generated during contract performance using an interactive collaborative environment (or equivalent)

f. Preliminary and final data submittal schedules for fulfilling submittal of DRD data in the specified quantities, specific media (electronic, paper, other), and due dates required.

5. Records retention approach.

End of Data Requirements Description DRD-PM-04

5.5 Data Requirements Description DRD-PM-05 (Risk Management Plan and Risk Management

Reports)

Program: MTN DRD No.: DRD-PM-05

Title: Risk Management Plan (RMP) and Risk Management Reports

Description/Use: Provides a baseline document for planning, management, control, and implementation of the Contractor’s risk management.

Initial Submission: Preliminary 60 days after ATP.

Submission Frequency: RMP baseline version no later than end of Preliminary Design Phase and update as required afterward. Risk Reports submitted monthly within 5 business days after the close of the

Contractor’s accounting month.

Remarks: RMP may be satisfied by inclusion of required content in DRD-PM-01PMPsubmissions.

There is no requirement for a separate, stand-alone document.

Contents: NOTE: For the RMP portion of this DRD, a Contractor's standard document can be submitted as long as it meets the intent of the content requirements of this deliverable.

At a minimum, the RMP shall include:

1. Introduction: specify the program/project risk objectives and policy toward risk. Explain the purpose, scope, assumptions, constraints, key ground rules, and policy pertaining to the project risk management process.

2. Overview of Process: provide an overview of the risk management process and information flow;

describe how the risk management process integrates and relates to other project management and system engineering activities. Include general risk mitigation strategies to be employed throughout project life cycle.

3. Organization: show the organization, roles, and responsibilities of program, project, customer, and supplier key personnel with regard to risk management. Document how team members will be trained in the application of risk management methodology.

4. Process Details: provide the risk management process details and related procedures, methods, tools, and metrics. Include here, or in an appendix, the specific methodologies to be used for activities of risk management: identify, analyze, plan, track, control, communicate and document as well as de-scope processes and risk acceptance versus closure criteria. Include the process to be used for continual assessment of the project risk profile. Describe how risk information will be communicated both internally to the project staff and throughout the NASA management chain.

5. Documentation of Risks: specify the format and data elements that will comprise the project risk list (and/or risk database), how configuration control will be applied, and how the list will be used and updated. Explain how team members will be able to access the current risk list at any time.

6. Key System Interfaces: describe the relationship and interfaces of the risk management process to lessons learned reporting, System Safety analyses, reliability/probabilistic risk analyses, schedule, financial and other business reporting systems.

7. Appendix: material that is too detailed or sensitive to be placed in the main body of text may be placed in an appendix or included as reference. Include the appropriate reference in the main body of the text. Appendices may be bound separately, but are considered to be part of the RMP document. Include an alphabetized list of the definitions for abbreviations and acronyms used in this document. Include an alphabetized list of definitions for special terms used in the document, i.e., terms used in a sense that differs from or is more specific than the common usage for such terms. Include a risk attributes scorecard that provides the criteria for establishing likelihood and consequence values of a risk.

At a minimum, the Risk Report shall include:

1. Risk Focus Charts which include:

a. Risk identification number

b. Risk statement

c. Risk context

d. Initial likelihood of occurrence score and rationales consistent with the risk attribute scorecard values established in the RMP

e. Initial consequence of occurrence score with safety, schedule, and technical/performance rationales consistent with the risk attribute scorecard values established in the RMP

f. Risk status

g. Timeframe to begin mitigations

h. Risk approach including mitigation plans (if applicable) and metrics with resulting likelihood and consequence scores consistent with the risk attribute scorecard values established in the RMP

2. Summary of risk mitigation activity and progress including objective evidence of exit criteria accomplishments

3. Applicable schedule for mitigation activity

4. Documentation of contingency planning for risks that could not be successfully mitigated, accepted, or closed

5. Risk attribute scorecard as established in the RMP

6. List of any closed or accepted risks since the last report and rationale for closure or acceptance

7. Consequence based 5x5 risk matrix

8. Risk list including risk trending, risk identification number, approach, and risk title

End of Data Requirements Description DRD-PM-05

5.6 Data Requirements Description DRD-PM-06 (Major Review Plans and Documentation)

Program: MTN DRD No.: DRD-PM-06

Pages: 1

Title: Major Review Plans and Documentation

Description/Use: Provides a baseline document for planning, management, control, and implementation of the Contractor’s risk management.

Initial Submission: See Submission Frequency

Submission Frequency: Plans to be provided 30 days prior to review. Documentation to be provided 14 calendar days before review.

Remarks: Some portions of this deliverable may be satisfied by inclusion of required content in DRD-

PM-01Project Management Plan submissions.

Contents: NOTE: For this DRD, a Contractor's standard document can be submitted as long as it meets the intent of the content requirements of this deliverable.

For each review, the Contractor shall prepare a Review Plan that defines roles and responsibilities, entrance and exit success criteria, what data will be delivered in support of each review (including DRDs), and how comments will be collected, dispositioned and distributed. The review plans should also address verification, qualification, and validation of heritage hardware and software for its intended use on MTN.

For each review, the Contractor shall prepare and submit a review package, presentation material, and the supporting data necessary for the complete understanding and assessment of the review in accordance with the approved Review Plan. In addition to the entrance and success criteria and requirements, required

DRDs will be reviewed

End of Data Requirements Description DRD-PM-06

5.7 Data Requirements Description DRD-PM-07 (Information Technology Security Management

Plan)

Program: MTN DRD No.: DRD-PM-07

Data Type: 2 Date Revised: 4/23/2026

Pages: 3

Title: Information Technology Security Management Plan

Description/Use: To define, document, and implement the security requirements of the Contractor’s

Information Technology (IT) system as well as to delineate the responsibilities and expected behavior of all individuals who access the system. The Information Technology Security Management Plan shall be viewed as documentation of the structured process of planning adequate, cost-effective security protection for the system. This shall ensure the proper security controls are architected into the overall end product for easier potential transition to NASA.

Initial Submission: Within 6 months after ATP.

Submission Frequency: Update as Required

Contents: NOTE: For this DRD, a Contractor's standard document can be submitted as long as it meets the intent of the content requirements of this deliverable.

The Contractor shall implement and maintain a National Institute of Standards & Technology (NIST) Risk

Management Framework-Based IT System Security Plan for all systems provided or operated in performance of this contract as required in clause I.12, NFS 1852.240-76, Security Requirements for

Unclassified Information Technology Resources.

The IT System Security Plan provides an overview of the security requirements of the system and describes the implementation details of the management, operational, and technical security controls in place or planned, and responsibilities and expected behavior of all individuals who access the system.

The IT System Security Plan, at a minimum, shall include the following:

A description of the detailed implementation of the following classes of control:

1. Operational Controls - The security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by people (as opposed to systems).

a. Documentation of operational controls may address the following areas, as applicable to the system, including implementation approach, responsible personnel or roles, execution schedules or frequencies, documentation maintained, and methods for validating effectiveness:

i. Contingency Planning - Backup and recovery procedures, alternate processing arrangements, contingency plan testing

ii. Incident Response - Incident detection, classification, response procedures, reporting and escalation

iii. Maintenance - Scheduled maintenance procedures, maintenance personnel controls, maintenance logging

iv. Physical and Environmental Protection - Physical access controls, visitor management, environmental monitoring

v. Personnel Security - Position screening requirements, access authorization/termination procedures, security responsibilities

vi. Security Awareness and Training - Security awareness programs, role-based training requirements, training records

vii. Media Protection - Media handling, storage, transport, sanitization, and disposal procedures

2. Management Controls - Actions taken to manage the development, maintenance, and use of the system, including system-specific policies, procedures and rules of behavior, individual roles and responsibilities, individual accountability, and personnel security decisions.

a. Documentation of management controls may address the following areas, as applicable to the system, including implementation approach, responsible personnel or roles, execution schedules or frequencies, documentation maintained, and methods for validating effectiveness:

i. Planning - Security and privacy plans, system security plan development and updates, rules of behavior

ii. Risk Assessment - Risk assessment processes, vulnerability identification and analysis, risk determination and mitigation strategies

iii. System and Services Acquisition - System development life cycle management, security requirements in acquisition processes, developer security testing and evaluation

iv. Program Management - Information security program planning, critical infrastructure plans, security program oversight

v. Assessment, Authorization, and Monitoring - Security control assessments, authorization decision processes, continuous monitoring strategies

vi. Supply Chain Risk Management - Supply chain risk assessments, supplier security requirements, provenance tracking

3. Technical Controls - Security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system. The controls can provide automated protection for unauthorized access or misuse, facilitate detection of security violations, and support security requirements for applications and data.

a. Documentation of technical controls may address the following areas, as applicable to the system, including implementation approach, responsible personnel or roles, execution schedules or frequencies, documentation maintained, and methods for validating effectiveness:

i. Access Control - Account management, access enforcement mechanisms, least privilege implementation, remote access controls

ii. Identification and Authentication - User identification and authentication, device authentication, multi-factor authentication

iii. Audit and Accountability - Audit logging, audit record content and generation, audit review and analysis, audit record retention

iv. System and Communications Protection - Boundary protection, cryptographic protections, network segmentation, transmission confidentiality and integrity

v. System and Information Integrity - Flaw remediation, malicious code protection, system monitoring, security alerts and advisories

vi. Configuration Management - Baseline configurations, configuration change control, security impact analysis of changes

End of Data Requirements Description DRD-PM-07

5.8 Data Requirements Description DRD-PM-08 (Insight and Oversight Implementation Plan)

Program: MTN DRD No.: DRD-PM-08

Data Type: 2 Date Revised: Initial Release

Title: Insight and Oversight Implementation Plan

Description/Use: NASA will utilize the Contractor’s Insight Implementation Plan to ensure NASA personnel, and its support services contractors can perform their insight and oversight.

Initial Submission: Baseline within 60 days after ATP

Submission Frequency: Update as Required

Contents: The Contractor’s Insight and Oversight Implementation Plan shall provide a description of the

Offeror’s proposed organizational structure, interfaces, management approach, assignment of key personnel, major subcontractor and supplier teaming arrangements, and approach to communications and coordination with NASA. The Contractor’s Insight and Oversight Implementation Plan shall also describe the accommodations for providing Government personnel and its support services contractor(s) timely and open access necessary to obtain a working-level understanding into all Contractor’s activities leading to hardware delivery and ultimately sustained operations, including the approach to accommodating

Government insight of technical and programmatic performance, including safety and mission assurance while still allowing the Contractor to maintain the efficiencies and effectiveness of their normal commercial processes. These accommodations include design review board membership, facility access, data, and any other information including technical and management processes required to meet contract requirements, milestone acceptance criteria, and to support approval of Type 1 and 2 data deliverables. The

Contractor’s Insight and Oversight Implementation Plan shall identify…