Att J.2-06 - LR-1 Phase 1 ASTO DPD.pdf

PDF 696 KB Posted

Attached to
Space Power and Reactor Capabilities (SPARC) - Final Request for Proposals (RFP)
Solicitation number
80GRC027R0005
Issued by

About this file

This is a Data Procurement Document (DPD) for NASA's Lunar Reactor 1 (LR-1) Phase 1 Task Order, establishing data requirements for preliminary flight system design and Engineering Test Unit (ETU) development through the Preliminary Design Review (PDR). The document, dated November 20, 2026, sets forth the contractor's obligations to prepare, maintain, and deliver technical data in accordance with FAR 52.227-14 Rights in Data-General, with all data classified as Type 1 (requiring NASA written approval before release), Type 2 (NASA has time-limited disapproval rights), or Type 3 (no NASA approval required). Data must be submitted via web-based content management platform in electronic format, primarily Adobe PDF or Microsoft Office formats, with specific identification requirements and data restriction markings for ITAR and EAR-controlled materials.

The CDRL identifies 25 data requirements across project management, systems engineering, safety and mission assurance, software, regulatory compliance, and supply chain disciplines. Key deliverables include the Project Management Plan (baseline at kickoff), Integrated Master Schedule (monthly updates), Flight System and ETU Requirements (baseline at System Requirements Review), Test Plans for ETU (preliminary at ATP+6 months, baseline at Test Readiness Review), Preliminary Flight Design CAD and Models (at PDR), Task Order 1 Final Report (28 days before end of phase), Failure Modes and Effects Analysis/Critical Items List (28 days prior to PDR), Preliminary Hazards Analysis (28 days prior to end of phase), Safety and Mission Assurance Plan (baseline at kickoff), and regulatory engagement and compliance documentation. Additional requirements address software plans and releases, ETU design description and user manual, supply chain assessment, and commercial IT authorization reporting, with submissions spanning from kickoff through phase completion and varying update frequencies from monthly to as-needed basis.

View the file

Other files

Show all 17

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

BASELINE

National Aeronautics and Space Administration

DATE: 2026-11-20

LUNAR REACTOR 1 – PHASE 1 TASK ORDER

(LR-1 P1 TO)

DATA PROCUREMENT DOCUMENT (DPD)

LUNAR REACTOR 1 (LR-1) DEVELOPMENT THROUGH HARDWARE-DRIVEN

PRELIMINARY DESIGN REVIEW (PDR)

Publicly Available: Release to Public Websites Requires Approval of Chief, Office of Primary Responsibility, and approval via the Scientific and Technical Information (STI) process, if applicable

Revision: Baseline SPARC Attachment J.2-06

Release Date: 11/20/26 Page: 2 of 76

Title: LR-1 Phase 1 (P1) Task Order (TO) Data Procurement Document (DPD)

The electronic version is the official approved document.

Verify this is the correct version before use.

REVISION AND HISTORY PAGE

Revision

No.

Description

Release

Date

- Initial Release 11/20/26

Release Date: 11/20/26 Page: 3 of 76

TABLE OF CONTENTS

1. INTRODUCTION

1.1 SCOPE

1.2 DPD DESCRIPTION

1.2.1 General Requirements

1.2.2 Contract Data Requirements List (CDRL)

1.2.3 Data Requirements Descriptions (DRDs)

1.2.4 Document Change Log (DCL)

1.2.5 DPD Maintenance Procedures

1.3 DATA TYPES FOR CONTRACTUAL EFFORTS

2. STATEMENT OF GENERAL REQUIREMENTS

2.1 APPLICABLE/REFERENCE DOCUMENTS

2.2 SUBCONTRACTOR DATA REQUIREMENTS

2.3 DOCUMENT FORMAT

2.4 DATA RESTRICTIONS AND MARKINGS

2.5 TRANSMITTAL

2.6 DOCUMENT IDENTIFICATION

2.7 REFERENCE TO OTHER DOCUMENTS AND DATA DELIVERABLES IN DATA SUBMITTALS.. 8

2.8 MAINTENANCE OF DATA REQUIREMENT DESCRIPTION DOCUMENTS

3. DPD MAINTENANCE PROCEDURES

3.1 NASA-INITIATED CHANGE

3.2 CONTRACTOR-INITIATED CHANGE

3.3 DPD CHANGE PROCEDURES

3.4 DPD REISSUES

4. CONTRACT DATA REQUIREMENTS LIST

5. DATA REQUIREMENT DOCUMENTS

Release Date: 11/20/26 Page: 4 of 76

1. INTRODUCTION

1.1 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.2 DPD Description

This DPD consists of a Document Change Log, an Introduction, a Statement of General

Requirements, DPD maintenance procedures, a CDRL, and the DRDs.

1.2.1 General Requirements

The general requirements, as specified in Section 2 of this DPD, prescribe those requirements applicable to the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRDs.

1.2.2 Contract Data Requirements List (CDRL)

Throughout the performance of the contract, the CDRL provides a listing of the data requirements of the DPD.

1.2.3 Data Requirements Descriptions (DRDs)

Each data requirement listed on the CDRL is given complete definition by a DRD. The

DRD prescribes content, format, and submittal requirements.

1.2.4 Document Change Log (DCL)

The Document Change Log chronologically records all revision actions that pertain to the

DPD.

1.2.5 DPD Maintenance Procedures

Maintenance procedures define the detailed methods to be employed in maintaining the

DPD. Detailed maintenance procedures are specified in Section 3 of this DPD.

Release Date: 11/20/26 Page: 5 of 76

1.3 Data Types for Contractual Efforts

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

Type Description

1 All versions and interim changes that affect the content or intent of those versions of the deliverable require written approval from NASA before formal release for use or implementation.

2 NASA reserves a time-limited right to disapprove in writing any versions and interim changes to those versions. 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.

All DRDs, regardless of data type, that are identified as deliverable as defined in the

CDRL shall be reviewable at the Contractor-Led reviews held at the end of the task order.

2. STATEMENT OF GENERAL REQUIREMENTS

2.1 Applicable/Reference Documents

a. The Contractor shall comply with Applicable Documents to the extent that they are identified and employed in the Contract, Statement of Work (SOW), Data

Requirements Description(s) (DRDs), or other attachment. Unless otherwise stated, the most recent versions of the documents shall be implemented. An Applicable

Documents List is to be maintained by the Contractor.

b. References to documents other than applicable documents in the data requirements of this DPD may sometimes be utilized, and shall be indicated in the DRD. These do not constitute a contractual obligation on the Contractor. They are to be used only as a possible example or to provide related information to assist the Contractor in developing a response to that particular data requirement. Unless otherwise stated, the most recent versions of the documents will be used as reference.

Release Date: 11/20/26 Page: 6 of 76

2.2 Subcontractor Data Requirements

Where a Subcontractor is performing any part of the work related to a Data Requirement, the Contractor shall integrate and provide Subcontractor data into the applicable Data

Requirement. Subcontractor integration is the responsibility of the Prime Contractor.

2.3 Document Format

a. All documents may be formatted using the Contractor’s preferred format except when directed otherwise in the DRD, contract clause, or referenced requirement.

b. All documents, unless otherwise noted within the specific DRD, shall be submitted in electronic format, which accommodates searching, using standard Adobe PDF format or Microsoft Office software (Word, Excel, PowerPoint, and Project).

c. Contractor may consolidate related DRDs, if approved by NASA.

2.4 Data Restrictions and Markings

a. All data produced or delivered under this contract shall be governed by FAR 52.227-

14 Rights in Data-General (MAY 2014), Alts. II & III, as modified by NFS 1852.227-

14 Rights in Data-General (APR 2015). The Contractor shall determine the data restriction that applies to each data deliverable and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The

Contractor shall make a determination for each individual data deliverable item, and shall not apply a default or blanket data restriction marking to all data deliverables

(e.g., “data may be export restricted”). If NASA does not agree with the Contractor applied data restriction, the NASA Contracting Officer shall return the data to the

Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

b. The Contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

1. If data delivered under this contract is subject to the International Traffic in Arms

Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice

This document contains information which falls under the purview of the U.S. Munitions List (USML) as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR §120-130, and is export-controlled. It shall not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license or license exemption is obtained/available from the Directorate of Defense Trade Controls, United States Department of State.

Violations of these regulations are punishable by fine, imprisonment or both.

Release Date: 11/20/26 Page: 7 of 76

2. If data delivered under this contract is subject to the Export Administration

Regulations (EAR), the data shall contain the “EAR Notice” as follows:

2.5 Transmittal

a. Data shall be transmitted to NASA via the web-based content management platform specified in writing by the Contracting Officer or COR prior to the data submission deadline. The electronic files shall be in an unlocked, editable format. Some data may be transmitted by hardcopy if agreed to by the Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data deliverables.

Notification to NASA can be automated via the collaboration tool or by email.

b. Each DRD transmittal package shall include:

1. Transmittal memorandum that specifies the meta-data below for each data transmittal:

a) Contract number

b) Data Requirements Description (DRD) number

c) DRD data type (specified in Item 3 on the DRD)

d) Submission date or milestone being satisfied

e) Document number and revision

f) Document title

g) File names of all files being delivered; multiple files per document must be clearly related to the document

h) Distribution (as defined by the Contracting Officer’s letter)

i) Requested response date

2. Printable electronic files or hardcopy data.

2.6 Document Identification

Type 1, 2 and 3 documents published by the Contractor and submitted in response to the data requirements of this DPD shall be identified within an organized identification numbering system prescribed to NASA by the Contractor and, if applicable, as approved by NASA. This number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The

Export Administration Regulations (EAR) Notice

This document contains information within the purview of the Export Administration Regulations

(EAR), 15 CFR §730-774, and is export-controlled. It may not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable export control official, and/or unless an export license or license exception is obtained/available from the Bureau of Industry and

Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment or both.

Release Date: 11/20/26 Page: 8 of 76 originator and organization names shall be included on the title page. The document number, change legend, and date shall appear on each page of the document. In the front of each document, identify the DPD number and applicable DRD number(s) required for document preparation. Successive issues or revisions of documents shall be identified in the same manner as the basic issue and shall have appropriate change identification.

Drawings are excluded from the marking provisions of this paragraph. All Type 1 documentation, excluding configuration management requirements, shall be marked

“PRELIMINARY PENDING NASA APPROVAL”, and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

2.7 Reference to Other Documents and Data Deliverables in Data Submittals

All referenced documents shall be made readily available to the cognizant NASA organization upon request. The Contractor shall make sure that the references are available to NASA in a manner which does not incur delays in the use of the response document. Reference may be made, within one data submittal, to other data submittals delivered in response to this DPD in those cases where the data required by one DRD may have been delivered by the Contractor in response to another DRD. The reference to previously-submitted data shall include the applicable DRD number, data submittal version date, and location within the referenced document.

2.8 Maintenance of Data Requirement Description Documents

a. Revisions of DRD documentation may be accomplished either by individual page revision or by a complete reissue of the document, with the exception of drawings

(which shall be revised in accordance with contract configuration management requirements).

b. Individual page revisions shall be made as deemed necessary by the Contractor or as directed by the Contracting Officer.

c. A Type 1 or Type 2 document shall be completely reissued when, in the opinion of the Contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the Contracting Officer. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final. Type 3 documents shall be completely reissued at the discretion of the Contractor.

d. Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a technical change is made, unless the accuracy of the document is affected.

Release Date: 11/20/26 Page: 9 of 76

e. Revisions of DRDs shall clearly indicate what content was changed from the previous version of the document.

f. DRD documents shall not be submitted containing pen and ink markups which correct, add to, or change the text, unless schedule problems exist and approval is obtained in writing from the Contracting Officer. Such markups, however, shall not exceed 20 percent of the page content and shall be acceptable provided that the reproduced copies are legible. In addition, hand-drawn schematics, block diagrams, data curves, and similar charts may be used in original reports in lieu of formally prepared art work, as long as legibility of copies is not impaired. Acceptability will be determined by the Contracting Officer.

3. DPD MAINTENANCE PROCEDURES

3.1 NASA-Initiated Change

New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion of the DPD shall be appended. The Contractor shall notify the Contracting Officer in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision to the DPD is appended. In such cases, the Contractor shall submit the requested changes to NASA for approval. See paragraph 3.3 for change procedures.

3.2 Contractor-Initiated Change

Contractor-proposed data requirements or proposed changes to existing requirements shall be submitted to NASA for approval. The document shall be re-issued upon approval.

3.3 DPD Change Procedures

a. Changes to a contractual issue of this DPD shall be identified by NASA on the

Document Change Log.

b. The date of the DPD shall be entered under the “as of” block of the Document

Change Log. The date that was in the “as of” block shall be entered in the

“Superseding” block.

c. The Document Change Log entitled “Incorporated Revisions” shall be changed to indicate the modification number, portions affected, and remarks. All changes to the

DPD/DRDs shall be identified in the “Remarks” column.

d. The Document Change Log entitled “Outstanding Revisions” is changed periodically to indicate outstanding Change Orders and Contracting Officer notification letters.

Release Date: 11/20/26 Page: 10 of 76

3.4 DPD Reissues

a. When conditions warrant, the DPD shall be reissued by NASA for each contract modification that affects the DPD and shall supersede the existing DPD in its entirety.

Reissues shall be issued by contractual direction.

b. All revision dates shall remain in the Date Revised block on all DRDs. The issue symbol, which shall commence with “A” and progress through “Z,” shall be entered in the DRD No. block of the DRD.

Release Date: 11/20/26 Page: 11 of 76

4. CONTRACT DATA REQUIREMENTS LIST

P - Preliminary

ATP - Authority to Proceed

U - Update

B - Baseline

F - Final

Use of “Days” in the DPD refers to calendar days unless stated otherwise

DRD No. DR Title Type Proposal Submission Date Frequency Notes

LR1-PM-001 Project Management Plan 2 - B-at kickoff U-upon revision

LR1-PM-002 Integrated Master Schedule (IMS) 3 - B-at kickoff U-monthly

LR1-PM-003

Project Management Review

Packages 3 - At monthly reviews Monthly

LR1-SE-001

Flight System & ETU

Requirements 1 -

B-at System

Requirements Review

(at 1st quarterly)

Updated upon revision and at major milestones

LR1-SE-002 Test Plans for ETU 2 -

P-ATP +6mo

B-Test Readiness

Review(s)

LR1-SE-003 Test Reports 3 - F-within 30 days of test completion

As often as individual tests are completed

LR1-SE-004

Preliminary Flight Design CAD, Models, and Associated Lists 3 -

F-Preliminary Design

Review

Release Date: 11/20/26 Page: 12 of 76

U - Update

B - Baseline

F - Final

Use of “Days” in the DPD refers to calendar days unless stated otherwise

DRD No. DR Title Type Proposal Submission Date Frequency Notes

LR1-SE-005

ETU Design Description

Document 3 -

F-28 days before End of Phase

LR1-SE-006 ETU CAD and Drawings 3 -

LR1-SE-007 ETU User Manual 3 -

LR1-SE-008 Task Order 1 Final Report 2 -

LR1-SMA-001 Requirement Variance Request 1 -

Within 5 working days of identifying the need for a requirement variance

As needed

LR1-SMA-002 Safety and Mission Assurance Plan 3 - B-at kickoff

LR1-SMA-003

Failure Modes and Effects and

Critical Items List (FMEA/CIL) 2 -

LR1-SMA-004

Preliminary Hazards Analysis

(PHA)

2 -

Release Date: 11/20/26 Page: 13 of 76

U - Update

B - Baseline

F - Final

Use of “Days” in the DPD refers to calendar days unless stated otherwise

DRD No. DR Title Type Proposal Submission Date Frequency Notes

LR1-SW-001 Software Plans 2 - P-60 Days After ATP U-28 days before

End of Phase

LR1-SW-002 Software Release 3 -

LR1-NLAM-001

Plan for Regulatory Engagement and NSPM-20 Compliance 3 - B-at kickoff

U-Preliminary

Design Review

LR1-SC-001 Supply Chain Assessment Report 3 - P-at kickoff F-Preliminary

Design Review

Status included in quarterly PMR charts

LR1-IT-001

Commercial Information

Technology (IT) Authorization

Report

3 - Initial submission within 90 days of ATP

U-monthly

F-End of Phase

Release Date: 11/20/26 Page: 14 of 76

5. DATA REQUIREMENT DOCUMENTS

Release Date: 11/20/26 Page: 15 of 76

DATA REQUIREMENTS DESCRIPTION LR1-PM-001

1. PROGRAM: LR-1 2. DRD NO.: LR1-PM-001

3. DATA TYPE: 2 4. DATE REVISED: 2026-11-20

5. PAGES: 10

6. TITLE: Project Management Plan

7. DESCRIPTION/USE: To describe the overall management approach of the LR-1 Project to execute the contracted scope including plans to address technology maturation, system development and testing, risk management, configuration and data management (CDM), insight/oversight by NASA, defining entrance/success criteria for lifecycle reviews, and subcontractor management. The Project Management Plan (PMP) describes the structure and environment within which the contract and subcontract(s) operate. The PMP will also include the project systems engineering management approach.

Task Order 1 will cover product development including Engineering Test Unit (ETU) testing, flight system design through Preliminary Design Review (PDR), and radiation testing for components/sub-systems to mature technology readiness to proceed towards flight readiness in the design.

8. INITIAL SUBMISSION: Baseline 30 days after Authority to Proceed (ATP), at Kickoff.

9. SUBMISSION FREQUENCY: Update upon revision

10. DATA PREPARATION INFORMATION:

10.1. SCOPE:

The PMP provides the basic planning document which describes the Contractor’s overall plan for performing the contracted scope of work. It details the approach for CDM, risk management, reviews, compliance with NASA insight/oversight, systems engineering management, and subcontractor management.

10.2. APPLICABLE DOCUMENTS:

10.3. CONTENTS:

The PMP shall include at minimum the following sections:

• Project Management

Release Date: 11/20/26 Page: 16 of 76

• Systems Engineering Management

• Configuration and Data Management

• Risk Management

• Insight Implementation

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.

Project Management:

The Project Management section of 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

Statement of Work. 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

SOW. 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 Project Management section shall identify and describe Control Plans that will be used in executing the SOW 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 Project Management Section shall include, at a minimum, the following items:

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

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

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

4. Description of major technical and milestone reviews, their purpose, lifecycle review entrance and success criteria, and performance reporting to NASA in preparation for these reviews.

A. For each review, the Contractor shall prepare a Review Plan that defines roles and responsibilities, entrance and exit success criteria, what data will

Release Date: 11/20/26 Page: 17 of 76 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.

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

C. The Review Board for each review shall include a NASA representative named by the Government.

D. Major technical and milestone reviews to be held are identified in the LR-

1 SOW Section 5.

5. Communication Plan, including but not limited to a description of the overall interaction policy and approach, format of weekly virtual status meetings, method for delivery of agenda and minutes from weekly virtual status meetings, 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.

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

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

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

9. Financial baseline plan.

10. Schedule performance reporting plans (including schedule reserves).

11. Discuss approach to data rights and intellectual property (IP). Identify any limited data rights or restricted computer software issues.

Release Date: 11/20/26 Page: 18 of 76

12. 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 cost, schedule, and technical performance. The CWBS shall also be used when reporting technical and schedule performance to NASA.

13. 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. SOW 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.

J. Budget and reporting number (i.e., Charge Code).

Systems Engineering Management:

The System Engineering Management Plan (SEMP) section of the PMP shall describe the Contractor’s systems engineering management processes and technical products generated including:

1. Systems Engineering approach, processes, and tools used to manage the technical scope, maintain requirements traceability, and transition products through the lifecycle. At a minimum this must describe:

A. The overall project lifecycle.

B. Contractor’s system engineering process, including flow down to subcontracts.

C. Trade study methodology.

D. Scope, approach, methods, and procedures of the system used to implement the management of requirements and verification tracking.

E. Management approach to requirements validation.

Release Date: 11/20/26 Page: 19 of 76

F. Evaluation and decision-making process to be used by the Contractor when resolving technical questions.

G. Contractor’s process for deriving, defining, and allocating project requirements to specifications.

2. Describe the anticipated interactions, roles and responsibilities between the contractor and NASA system engineering teams throughout the technical effort.

3. Describe the approach for sharing information (such as: models, drawings, etc.) between the Government and contractor, including access to contractor owned tools or virtual work environments.

4. Identify and describe the requirement development processes, proposed documentation, and management of the process, including the incorporation of the NASA requirements as well as interfaces to other systems.

5. Describe the tools, methodologies, and approach used to develop and manage to the design solution. Include trade studies processes and documentation.

6. Entrance and success criteria for, at minimum, the System Requirements

Review (SRR), Test Readiness Review(s) (TRR), and Preliminary Design

Review (PDR). The Contractor shall use their standard entrance and success criteria. In the absence of internal criteria, the entrance and success criteria defined in NPR 7123.1 “NASA Systems Engineering Processes and

Requirements” can be used. The SEMP section may define a tailored approach to these reviews. Tailored entrance and success criteria may be a standalone document or an appendix to this plan.

7. Describe the roles and responsibility related to technical authority/accountability. Including the interrelation between Contractor’s technical and business management.

8. Describe the process and philosophy for technical decision making including dissenting opinions and review board processes.

Configuration and Data Management:

The Configuration and Data Management Plan (CDMP) section shall describe approach and methods for implementing configuration management (CM) requirements in compliance with overall project policies, SAE/EIA-649-2 standards, and applicable agency directives. The CDMP section of the PMP must define the overall CM program, at a minimum, by addressing the following core areas:

1. Purpose, Scope, & Documentation

A. Purpose & Applicability: State the objectives, management policies, program phases, and the specific hardware/software Configuration Items

(CIs) covered.

Release Date: 11/20/26 Page: 20 of 76

B. Supplier Context: Identify any assumptions, limitations (e.g., time, resources, risks), and decisional authorities (boards/individuals) specific to the supplier.

C. References: List all applicable documents, standards (e.g., SAE/EIA-649-

2), and related plans (like risk management or sub-tier CMPs).

2. Organization & Milestones

A. Organizational Structure: Graphically illustrate the integration between project and functional organizations, both internal and external.

B. Roles & Responsibilities: Define authority for all CM activities and participating groups, including Configuration Control Boards (CCBs) and any required CM training.

C. CM Phasing: Provide a timeline/schedule for CM implementation, document releases, baselines, and audits tied to major project milestones.

3. Configuration Identification

A. Items & Baselines: List criteria and specific CIs/Computer Software

Configuration Items (CSCIs). Establish Functional, Allocated, and Product baselines.

B. Numbering & Release: Define schemas for assigning unique identifiers

(part/serial numbers, software versions) and the release procedures for

Product Configuration Information (PCI).

4. Configuration Control & Interface Management

A. CCB Operations: Detail the organization, membership, and authority levels for approving/disposing of changes.

B. Change Processing: Define end-to-end procedures for handling Change

Requests, Waivers/Deviations, and Field Engineering Changes.

C. Interfaces: Describe relationships with Interface Working Groups and the

Material Review Board (MRB) nonconformance disposition processes.

5. Configuration Status Accounting

6. Data Collection & Reporting: Explain methods for collecting, processing, and safeguarding CM data.

7. Traceability: Ensure accounting reports track approved PCIs, the status of proposed changes/variances, audit results, and the installation effectivity of changes across all locations.

8. Configuration Verification and Audits

A. Audit Plans: Outline schedules, procedures, and responsibilities for conducting Functional and Physical Configuration Audits, as well as internal CM system audits.

B. Discrepancy Tracking: Define the format for audit reports and methods for tracking and resolving discrepancies.

9. Configuration Data Management & Records

Release Date: 11/20/26 Page: 21 of 76

A. Data Delivery & Storage: Detail how data deliverables (hardcopy or digital) are transmitted, verified, stored, and accessed.

B. Data Protection: Specify strict procedures for protecting, Controlled

Unclassified Information (CUI), export-controlled, and limited-rights data.

C. Acceptance & Records: Describe notification methods for data receipt/acceptance. Identify required CM records, retention schedules, and archival procedures (including Government vs. contractor records custodianship).

The CDMP shall require a current contract Applicable Document List. The

Applicable Documents List will be maintained current and provide, at a minimum, reference to the Document Number, Document Title, Document

Revision/Date, and source of direction to implement the document version (i.e.

Contract, NASA directive, etc.). The Applicable Document List shall be submitted to the Government when updated.

Risk Management:

The purpose of the risk management section is to identify risks early in the project so that appropriate plans can be implemented to reduce the consequences of the risk or likelihood that the risk will occur. A risk refers to anything that can prevent the Contractor from meeting contract objectives. All forms of risk shall be managed including safety, technical (hardware and software), programmatic, supportability, cost, and schedule risks. Cost risks are not required to be reported to NASA. For an undesirable risk or event that has occurred, or occurrence cannot be stopped or directly controlled, the risk will be converted into an issue. Issues shall be presented as part of the risk reporting process.

The Risk Management Plan (RMP) chapter of the PMP shall provide a baseline document for planning, management, control, and implementation of the

Contractor’s risk management process throughout the contract lifecycle and provide Government insight to the Contractor’s risk management approach. The

RMP provides the overall approach, coordination, structure, and environment within which the risk management processes for the contract reside through the contract implementation. The RMP describes the methodologies and processes used to identify, analyze, plan, track, control, communicate and document the risks.

At a minimum, the Risk Management Plan shall include:

Release Date: 11/20/26 Page: 22 of 76

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.

Insight Implementation:

Release Date: 11/20/26 Page: 23 of 76

The Insight Implementation Plan section of the PMP shall 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 the Contractor’s activities leading to a spaceflight demonstration 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

Implementation Plan shall identify instructions or training required to allow for meaningful NASA insight and participation (e.g., facility and safety familiarization).

In addition, the Insight Implementation Plan shall address:

1. Accommodating Government Insight and the following items:

A. The transparency by which the Contractor will provide the Government on-going access into activities and data used for mutually addressing risks and achieving successful milestone acceptance including membership on system level design review boards, approval of Type 1 and 2 data deliverables.

B. The transparency by which the Contractor will provide the Government on-going access to data, both remotely and on-site, in a useable and readable format; and provide the Government the ability to locate and review all data used in performance of this contract, to include technical data, supporting data/information, and administrative and management information with the exception of financial information. Whether the data accessed includes the ability of the Government to download or copy data;

the Contractor’s proposed data restriction legends on accessed data; and mechanisms to ensure that access data is not confused with data delivered under the contract.

C. The timeframe in which the Contractor shall notify the NASA designee of technical meetings, control boards, reviews, demonstrations and tests to permit meaningful Government participation through the entire SOW.

2. Accommodating Government Quality Assurance (GQA) functions. This shall include:

A. The timeliness and ease by which the Contractor will accommodate

NASA and make data available for the Government to perform a

Release Date: 11/20/26 Page: 24 of 76 successful risk based analysis that will facilitate the identification of high risk areas.

B. The timeliness and ease by which the Contractor will accommodate

NASA performing the GQA activities identified by the risk based analysis and make data available to achieve successful GQA activities. GQA refers to the various functions performed by the Government Safety and Mission

Assurance personnel to determine whether a contractor has fulfilled contract obligations pertaining to quality. The term quality, when used within the context of this DRD, refers to compliance with requirements that are levied upon the Contractor, including, but not limited to, safety, technical, item configuration, reliability, and quality management system requirements. GQA functions are planned and conducted on the basis of contract risk, to achieve confidence levels commensurate with the severity of consequences associated with noncompliance and to mitigate circumstances where there is an elevated likelihood of noncompliance.

Audits or surveys are the typical methods used.

3. Resolving concerns and issues identified by NASA and its support services contractor’s insight effort. This shall include:

A. The process to permit timely elevation of issues to NASA.

B. The process of highlighting critical activities of interest (such as changes, decisions, key testing events, critical meetings) to NASA.

4. Accommodating NASA’s insight in the Contractor’s development and successful fulfillment of operational requirements. This shall include:

A. The timeliness and ease by which the Contractor will accommodate

NASA’s insight in the operational activities and make data available to mutually address risks associated with achieving successful demonstrations, tests, completing acceptance milestone review criteria.

B. The process of highlighting critical activities of interest (such as changes, decisions, key events, critical meetings) to NASA.

C. The process to permit timely elevation of issues to NASA.

5. The process of providing the Government insight into all subcontractors and suppliers performing or supporting any critical work associated with this contract.

10.4. FORMAT: Contractor’s format is acceptable.

10.5. MAINTENANCE: Per section 2.8 of the DPD

Release Date: 11/20/26 Page: 25 of 76

DATA REQUIREMENTS DESCRIPTION LR1-PM-002

1. PROGRAM: LR-1 2. DRD NO.: LR1-PM-002

3. DATA TYPE: 3 4. DATE REVISED: 2026-11-20

5. PAGES: 3

6. TITLE: Integrated Master Schedule (IMS)

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

8. INITIAL SUBMISSION: Baseline 30 days after ATP, at kickoff.

9. SUBMISSION FREQUENCY: A fully-statused IMS shall be delivered monthly.

The IMS is a time-phased, integrated, logically linked schedule, and shall capture the activities described in the Project Management Plan, be vertically traceable to the Contractor Work Breakdown Structure and Statement of Work and include the lower-level work necessary to support each of the activities. The IMS will be used to verify attainability of contract objectives and requirements, and to evaluate progress.

To ensure an integrated approach to risk management, the information within the data provided by this IMS DRD shall be integrated with DRD LR-1-PM-001:

Project Management Plan.

The IMS shall include all milestones and discrete activities/tasks from contract award to completion of the contract necessary to perform the entire contract work scope. The IMS shall provide the ability to fully identify, analyze, mitigate, and control scheduling risks and impacts, accurately identify and analyze critical path

Release Date: 11/20/26 Page: 26 of 76 activities, clearly calculate schedule float, and allow its users to easily measure the progress.

Tasks and milestones from subcontractors shall be included with sufficient detail to produce a valid critical path. Their data shall be consistent and statused monthly to the IMS status date.

The IMS shall clearly identify tasks or activities which have a dependency on a

NASA delivery or approval (for example, delivery of a GFE), and the availability of a NASA facility as outlined in a Government Task Agreement, including the need dates. The IMS shall also identify any specific data or models needed from

NASA (for example, GFE models) to complete the work under this contract.

The Contractor shall provide a schedule analysis narrative as part of its monthly

IMS deliverable. The narrative shall include the critical path as well as secondary and tertiary driving paths. The narrative shall address any schedule slips affecting the previous month’s critical path, including root cause for the slip and potential options for schedule recovery. The narrative shall also track the status of previously reported variances or slips and the progress made to resolve them. Any other variances or slips that are of concern to the Contractor and/or have the potential to impact the critical path in the future should also be reported at the discretion of the Contractor.

Schedule Status: The IMS status date shall be updated monthly according to the month of the IMS deliverable, and all activities/tasks shall be statused to the IMS status date. The IMS shall reflect actual progress and maintain accurate start and finish dates for all activities/tasks and milestones. Actual Start and Actual Finish dates shall not be later than the status date, and Forecast Start and Forecast Finish dates shall not be earlier than the status date.

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, and they shall be placed as the last task before a significant milestone, an end-item deliverable, or contract completion.

Release Date: 11/20/26 Page: 27 of 76

Summary Master Schedule: The schedule shall include a top-level Gantt chart summary arranged by WBS and that reflects all contract milestones, LR-1 P1 TO meetings (as defined in Section 5.7 of the Statement of Work), 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.

10.4. FORMAT: IMS shall be provided in Microsoft Project (.mpp) file format.

Release Date: 11/20/26 Page: 28 of 76

DATA REQUIREMENTS DESCRIPTION LR1-PM-003

1. PROGRAM: LR-1 2. DRD NO.: LR1-PM-003

5. PAGES: 2

6. TITLE: Project Management Review Packages

7. DESCRIPTION/USE: To establish activity reporting for the Contractor’s progress and accomplishments. The Project Management Review (PMR) packages support the monthly management performance reviews between the Contractor and NASA at the Contractor’s facility. Face-to-face meetings will at minimum occur quarterly.

8. INITIAL SUBMISSION: DRD shall be delivered 12 days after the close of the contract month that is subsequent to the month in which the post-award kick-off occurs.

9. SUBMISSION FREQUENCY: Monthly

PMR packages provide insight into Contractor performance in executing the contract. The PMR shall address Contractor performance against technical, cost, and schedule objectives with emphasis on risk identification and mitigation. A summary of significant SMA activities shall also be included. Status updates for performance metrics and Technical Performance Parameters (TPPs), developed by the Contractor in accordance with DRD LR1-PM-001, shall be included as part of the PMR package.

10.2. DATA Preparation Information

The monthly review package shall include, at a minimum:

Project Management Summary

1. Accomplishments, Milestone Status, Risk Summary, Top challenges with top level recovery plans and/or decisional solution paths

2. Performance Metrics

3. Contract deliverables and payment milestones

Release Date: 11/20/26 Page: 29 of 76

4. Open actions

Schedule Status

1. Project critical path task summary

2. PDR and ETU development status to milestones

Systems Engineering & Integration Status

1. Flight System requirements development

2. ETU requirements development

3. Summary of requirements changes/waivers/deviations

Risk Management Status

1. Top Project Risks: summary and mitigation

2. Risks to current baselined schedule

i. NASA inputs/decisions requested?

Safety and Mission Assurance Status

1. Summary of significant SMA activities, including but not limited to:

i. a. audits and findings

ii. b. nonconformances and associated review boards

iii. c. quality metrics (e.g. manufacturing process control)

ETU Test Development and Testing Status

1. Subsystem/Test Unit/Test System Design & Development

(Hardware/Software)

2. Test Plans/Reports

3. Procurement & Long Lead Items

4. Test Readiness (Facilities, GSE/ITME, Training, etc.)

Engineering Topics

1. Contractor driven areas of emphasis or concern

Supply Chain Assessment Updates (Quarterly)

1. Status updates per DRD LR1-SC-001

10.4. FORMAT: PMRs shall be delivered as written memos (e.g., a Word document, PDF, or contractor’s preferred written format).

Release Date: 11/20/26 Page: 30 of 76

DATA REQUIREMENTS DESCRIPTION LR1-SE-001

1. PROGRAM: LR-1 2. DRD NO.: LR1-SE-001

3. DATA TYPE: 1 4. DATE REVISED: 2026-11-20

5. PAGES: 4

6. TITLE: Flight System and ETU Requirements

7. DESCRIPTION/USE: The purpose of the Flight System and ETU Requirements deliverable is to define the requirements and verification methods (Analysis, Demonstration, Inspection, Test) for the preliminary LR-1 Flight System and the Engineering Test Unit (ETU). The

Flight System Requirements establish a formal description of functional and performance requirements of the flight hardware. These requirements will form the basis for assessing the adequacy of the LR-1 preliminary design to meet the mission objectives. The ETU

Requirements establish a formal description of the functional and performance requirements of…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .