Attachment H - Data Procurement Document (DPD)_Amendment 2.pdf

H-1

DATA PROCUREMENT DOCUMENT

NO. ISSUE

1780 RFP

Amendment 2

NNM19ZQ001K

CONTRACT/RFP

EXHIBIT NUMBER

H

ATTACHMENT NUMBER

Human Landing System – Sustaining Lunar Development

PROJECT/SYSTEM

Contractor

CONTRACTOR

October 18, 2022

DATE

National Aeronautics and Space Administration

10/18/22

H-2

National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

NO. ISSUE

1780 RFP

INCORPORATED REVISIONS

OUTSTANDING REVISIONS

AS OF:

10-18-22

SUPERSEDING:

PAGE:

AUTHORITY PORTION AFFECTED - PAGE NO./NO.

REMARKS (DPD Revision) INTRO SGR DRL DRD

RFP Amend 2 H-14 Update DRD OP-003 delivery matrix

OP-003 HDL content delivery option made clearer and JSC-35199 interface document reference added

SA-002 Corrected Applicable Documents and the content covered in those documents in sections 15.2 and 15.3: Software Assurance Plan section

SE-001 Clarification to 15.3: g. Verification method level required

SE-005 Clarification of scope for the initial DRD overview content (to include high level Assembly and Integration, along with testing overview)

SW-001 Clarified Scope for what software system plans must be submitted

SW-002 Clarified Scope for what software system plans must be submitted

SW-002 Clarified “conceptual” and “draft” with additional phrase describing expected content

H-3

A subset of DRDs were indicated within the App P: SLD solicitation as Contractor submittals that will be incorporated into the contract at time of award. For those submittals, for each instance during App P: SLD contract performance that the submittal is updated and submitted by the Contractor—and if applicable, approved by NASA—the updated version of the submittal will automatically be incorporated into the contract and shall fully replace and supersede all previous versions of the submittal that may have been incorporated into the contract.

H-4

1.0 INTRODUCTION

1.1 Scope: Subject to clause 52.227-14 Rights in Data – General (Deviated), 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 Data Requirements List (DRL) 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. In accordance with FAR 27.406-3(a), the following DRDs contain technical data to which the clause 52.227-21 - Technical Data Declaration, Revision, and Withholding of Payment--Major Systems applies:

• DRD 1780CM-001, Final Design Data Package

• DRD 1780DE-001, Design Data Book

• DRD 1780DE-002, Integrated System Performance Analysis

• DRD 1780DE-003, Gateway Cross-Program Engineering Models and Data

• DRD 1780DE-004, HDL Integrated Analysis Document

• DRD 1780HS-002, Human Error Analysis (HEA) Reports and Analyses

• DRD 1780HS-004, Human Systems Integration Reports and Analyses

• DRD 1780HS-005, Food System Plan

• DRD 1780HS-006, Medical Kit Subsystem Plan

• DRD 1780LV-001, Launch Vehicle/Spacecraft Interface Control Document (ICD) and Verification

Matrix

• DRD 1780LV-002, Mission Specific Drawings

• DRD 1780LV-003, Launch Vehicle/Spacecraft Integrated Procedures

• DRD 1780LV-004, Performance and Guidance Accuracy Analysis (PGAA)

• DRD 1780MP-001, Orbital Debris Assessment Reports (ODARs) and End of Mission Plan (EOMP)

• DRD 1780OP-001, Flight Software Simulator

• DRD 1780OP-002, Integrated Operations Training

• DRD 1780OP-003, Mission Operations and Mission Systems Plan

• DRD 1780OP-004, Lunar Orbit Checkout Plan

• DRD 1780RM-001, FEMA/CIL

• DRD 1780SA-001, System Safety Assessment Reports

• DRD 1780SA-005, Planetary Protection Data

• DRD 1780SE-001, HLS Integrated Lander System Specification

• DRD 1780SE-002, Verification, Validation, and Certification Plan

• DRD 1780SE-003, Detailed Verification Objectives - Integrated Lander

• DRD 1780SE-004, Verification Closure Notices – Integrated Lander

• DRD 1780SE-005, Assembly, Integration and Test (AIT) Plan

• DRD 1780SE-006, Human Landing System (HLS) GNC Simulator Specification

• DRD 1780SE-007, Avionics Emulator and Acceptance Data Package

• DRD 1780SE-008, HLS Human-class Delivery Lander (HDL) System Specification

• DRD 1780SE-009, Contractor’s Concept of Operations

• DRD 1780SE-010, Detailed Verification Objectives – HLS Human-class Delivery Lander (HDL)

• DRD 1780SE-011, Verification Closure Notices – HLS Human-class Delivery Lander (HDL)

• DRD 1780SE-012, Mission Performance Evaluation Reports and Data

• DRD 1780SW-001, Software Verification, Validation, and Certification Plan

• DRD 1780SW-002, Software Plan (SP)

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

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

1.2.1 General Requirements: The general requirements, as specified in paragraph 2.0 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.

H-5

1.2.2 Data Requirements List (DRL): Throughout the performance of the contract, the DRL provides a listing by data category of the data requirements of the DPD.

1.2.3 Data Requirements Description (DRD)

1.2.3.1 Each data requirement listed on the DRL is given complete definition by a DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements.

1.2.3.2 For the purpose of classification and control, DRDs of this DPD are grouped into the following broad functional data categories:

CATEGORY SYMBOL DESCRIPTION

CD Contractual Data CM Configuration Management DE Design and Development Engineering HS Human System LV Launch Vehicle MA Management MP Materials and Processes OP Mission Operations RM Reliability and Maintainability SA Safety SE Systems Engineering SW Software

1.2.3.3 The symbols representing these data categories form part of the prefix of the DRD identification number. The first numerical characters reflect the DPD number.

1.2.3.4 To facilitate the usage and maintenance of the DPD, the DRDs have been sectionalized in accordance with the above data categories.

1.2.3.5 The DRDs are filed by data category and are in alpha-numeric sequence as listed on the DRL pages that precede the DRDs.

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 paragraph 3.0 of this DPD.

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 issues and interim changes to those issues require written approval from the requiring organization before formal release for use or implementation.

2* NASA reserves a time-limited right to disapprove in writing any issues and interim changes to those issues. The Contractor shall submit the required data to NASA for review not less than 30 calendar days** prior to its release for use. The Contractor shall clearly identify the release target date in the “submitted for review” transmittal***. If the data is unacceptable, NASA will notify the Contractor within 30 calendar days** from the date of submission, regardless of the intended release date***. The Contractor shall resubmit the information for reevaluation if disapproved. The submittal is considered approved if the Contractor does not receive disapproval or an extension request from NASA within 30 calendar days**. NOTE: Approved with Modifications is an alternate to the disapproved option that requires resubmittal of the product and will be used to communicate DRD submittals with the incorporation of Government comments will be approved.

H-6

3 These data shall be delivered by the Contractor as required by the contract and do not require NASA approval. However, to be a satisfactory delivery, the data shall satisfy all applicable contractual requirements and be submitted on time.

4 This type data is produced or used during performance of the contract and retained by the Contractor.

Data shall be delivered only when NASA requests in writing and shall be delivered in accordance with the instructions in the request. The Contractor shall maintain a list of these data products and shall furnish copies of the list to NASA when requested to do so.

5 This type data is incidental to contract performance and retained by the Contractor in those cases where contracting parties have agreed that formal delivery is not required. However, the Contracting Officer or the Contracting Officer’s Representative (COR) shall have access to and can inspect this data at its location in the Contractor’s or subcontractor’s facilities, or in an electronic database accessible to the Government.

* Note: Type 1 and Type 2 data may be placed under NASA configuration management control when designated by NASA. CM control requires the Contractor to submit Type 1 and Type 2 data updates through Engineering Change Proposals (ECPs).

** Note: This time limit may be tailored for individual DRDs to meet the requirements of the procuring activity.

*** Note: If the Contractor does not identify a release target date or if the intended release date is shorter than 30 calendar days from the date of submission, the 30 calendar days review cycle stands (or the tailored Type 2-time limitation for the specific procurement).

2.0 STATEMENT OF GENERAL REQUIREMENTS

2.1 Applicable/Reference Documents: Documents included as applicable documents in this DPD are the issue specified in the Statement of Work and form a part of the DPD to the extent specified herein. Applicable documents listed in Item 15.2 of a DRD are applicable only to the preparation of the deliverable documentation described by that DRD.

References to documents other than applicable documents in the data requirements of this DPD may sometimes be utilized and shall be indicated in 13. Remarks of 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.

2.2 Subcontractor Data Requirements

2.2.1 The Contractor shall specify to subcontractors and vendors, if any, the availability source of all data required for the satisfactory accomplishment of their contracts. The Contractor shall validate these requirements for data products when appropriate; where the requirement concerns other Contractor data, the Contractor shall provide his subcontractor or vendor with the necessary data products. All such requests shall be accomplished under the auspices of the Contractor.

2.2.2 Reference to subcontractor data in the Contractor’s responses is permissible, providing the references are adequate and includes such identification elements as title, number, revision, etc., and a copy of the referenced data is supplied with the response document at time of delivery to NASA.

2.3 Data Distribution, Format, Data Restriction Marking, and Transmittal

2.3.1 Distribution: Distribution of required data products shall be delivered via the Human Landing System (HLS)

Data Delivery System, or as determined by the Contracting Officer. Recipient names and email addresses (if applicable) shall be noted on a separate distribution list to be furnished by the Contracting Officer. Contracting Officer’s letter may include other information pertinent to delivery of data, as required.

2.3.2 Format

H-7

2.3.2.1 Electronic Format: Data products shall be delivered in a native format unless otherwise specified by the DRD or the Contracting Officer. A preferred format is noted for each delivery item specified in the DRD, but the Contractor may utilize an alternative format at the discretion of the COR.

Additional steps necessary for printability are not required for structured data mapped and delivered via method 1 or 2 as defined in 2.3.4.4 below. 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. Definition of the application (including version) that produced the file.

2. The native proprietary file itself.

3. Commonly readable representation of the file (e.g., PNG or PDF).

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

Files delivered via method (3) shall be provided in an electronic format that meets four basic requirements:

“Human-Readable”, “Machine-Readable”, “Printable”, and “Downloadable” (see Attachment J-5, Glossary and Acronym List) utilizing publicly available COTS software.

2.3.2.2 Hardcopy Format: Hardcopy of the DPD is not required unless electronic delivery is not possible or practical.

The Contractor’s transmittal memo shall be delivered in a hardcopy to the Contracting Officer (CO). The DPD shall be emailed to the CO.

2.3.3 Data Restriction Markings

2.3.3.1 Data Restriction Determination and Marking Requirements: 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 clause 52.227-14 Rights in Data – General (Deviated) and contract section H clauses Marking Requirements for Technical Data and Computer Software, and Validation and Challenge Procedures for Technical Data and Computer Software.

2.3.3.2 Data Restriction Categories and Marking Statements: The contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

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:

If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR 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 nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

H-8

Data otherwise delivered under this contract, meaning delivered pursuant to one or more DRDs contained herein, shall comply with the marking requirements contained in clause 52.227-14 Rights in Data – General (Deviated) and contract section H clauses Marking Requirements for Technical Data and Computer Software, and Validation and Challenge Procedures for Technical Data and Computer Software.

Because the contract contains NFS 1852.237-73, a sensitive information legend may be applicable to information (which does not qualify as technical data or computer software) delivered under this contract.

In accordance with the applicable data clause (e.g., FAR 52.227-14(c) or FAR 52.227-20(c)), the contractor may be able to assert copyright in data first produced in the performance of the contract. When claim to copyright is made, the Contractor shall affix the applicable copyright notices of 17 U.S.C. 401 or 402 and acknowledgment of Government sponsorship (including contract number) to the data.

2.3.4 Transmittal

2.3.4.1 Data product deliverables shall be transmitted to NASA electronically or by other mechanism agreed to by the

CO. The Contractor shall notify the CO and the COR of data product delivery by creating a release record in the HLS Data Delivery System (see Appendix A after 3.4.2 - HLS Data Delivery System for access instructions and usage guides).

2.3.4.2 If email is used to transmit data deliverables, the email size shall be 10 Megabytes or less to ensure receipt by the NASA email servers. Encrypted email format shall be used to transmit data which has been judged sensitive by the Contractor (e.g., export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.).

2.3.4.3 Data Transmittal Package: Each data transmittal package shall include:

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

1. Contract number.

2. Data Requirements Description (DRD) number.

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

4. Submission date or milestone being satisfied.

5. Document number and revision.

6. Document title.

7. File names of all files being delivered; file naming convention shall clearly identify the document being delivered.

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

9. Requested response date.

10. Contractor assigned data restriction (export controlled, limited rights data, SBIR, restricted computer software, copyrighted, etc.) if not marked on data.

11. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS 1441.1, NASA

Records Retention Schedules).

b. Electronic data shall be submitted to the appropriate NASA or Contractor site.

2.3.5 Data Product Transmittal Memorandum: Data product deliverables may identify a preferred methodology of delivery for each data item, including the identification of data systems for the tracking and management of specific data products. Regardless of the method of file delivery, a record shall be generated in the HLS Data Delivery System identifying each transmitted package. Delivery into the Government systems shall be performed by:

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 nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/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.

H-9

1. Direct entry, in which the Contractor utilizes the NASA system as the system of record for the data.

2. Batch import, in which files of a predefined schema are provided to the Government for either automated or manual import.

3. File delivery, in which a product is delivered in an archival format (e.g., PDF).

4. An alternate method proposed by the Contractor and approved by the Contracting Office Representative.

2.4 Deleted.

2.5 Contractor’s Internal Data Products: The Contractor’s internal data product shall be used to meet the data requirements of this DPD unless a specific format is required by the applicable DRD.

2.6 Document Identification: Type 1 and 2 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. For all data types, the data product number, change legend, date, and title constitute the minimum identification of the specific data document.

The minimum identification of the specific data product shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization 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 matter 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 and ECPs 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 Data Products/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 data products/documents. 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.

Other data submittals shall accompany a Transmittal Memorandum defined in 2.3.4.3 above.

2.8 Maintenance of Type 1 Data Product Submittals

2.8.1 Revisions of Type 1 data products accomplished either by a targeted Change Request or by a complete reissue of the product identified in accordance with requirements of 2.6 above, with the exception of drawings (which shall be revised in accordance with contract configuration management requirements).

2.8.2 Targeted Type 1 Change Request shall be made as necessary by the Contractor or as directed by the CO. Each targeted change request shall include an explicit listing of all changes in a “to/from” format and identified as a “point release” of the data product revision (e.g., Revision C.1, C.2, etc.). A maximum of 10 (ten) targeted change requests shall be permitted before a complete reissue of the data product. Approved targeted Change Request shall be prepended onto the data product and recorded in the NASA Configuration Management system.

2.8.3 A Type 1 data product shall be completely reissued when, in the opinion of the Contractor and/or NASA, the data product 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 data product shall be brought up to date and shall incorporate targeted Change Request. All revisions shall be recorded in the NASA Configuration Management system. A revision log shall identify complete reissues except for periodic reports and data products that are complete within themselves as final.

H-10

2.8.4 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 data product is affected.

3.0 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 DPD is appended. In such cases, the Contractor shall submit the requested changes to NASA for approval. See paragraph 3.3.1 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.

3.3 DPD Change Procedures

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

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

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

3.4 DPD Reissues

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

3.4.2 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 DPD identification block of each DRD page of the DPD.

H-11

APPENDIX A

HLS DATA DELIVERY SYSTEM

Introduction

The HLS Data Delivery System (DDS) provides a method for delivery of products supplied by the Contractor in satisfac-tion of a DRD and a method for the notification of product completion for products maintained in Contractor systems.

The system is available as part of the NASA HLS SharePoint environment at https://moon2mars.ndc.nasa.gov/HLS/DDS.

At a high level, it allows designated NASA and Contractor personnel to see products being delivered, reviewed, and approved. For Type 1 data deliverables, the DDS will also serve as the method by which Contracting Officer and Contracting Officer Representatives indicate formal acceptance of the deliverable.

Access Instructions for the HLS Data Delivery System

Prerequisites for Access

Moon2Mars (M2M) SharePoint (including the M2M DDS) will be available to Contractors and can be accessed from external (non-NASA) devices via a web-based VPN. Access to the VPN is controlled via a request in the NASA Asset Management System (NAMS) for the “AGCY WebVPN NASA Gateway-NextStep-Moon2Mars Remote Access” asset (https://idmax nasa.gov/nams/asset/254779). Access to this VPN is a prerequisite for access to the DDS from outside the NASA infrastructure.

All Contractor users of the HLS DDS shall have a NASA identity with a Level of Confidence (LoC) of 35. In order to meet this level of confidence, users shall successfully undergo an OPM Tier 1 investigation (low-risk, non-sensitive); at a high level, this requires:

1. Enrollment of the user for a NASA identity.

2. A NASA reciprocity check to determine whether a sufficient background check has already been performed by another agency.

3. If not, an OPM investigation will be performed requiring the Contractor user to complete an investigation questionnaire in e-QIP; after the user has submitted the questionnaire and the Office of Protective Services has released it to OPM for investigation, the user’s Level of Confidence will be increased to 35. At this point, the user can request access to the VPN and access the HLS DDS.

4. Following the OPM investigation, NASA will review the results and increase the LoC of that user identity to 40 if the investigation was favorable. This allows the user to receive full NASA credentials.

Requesting Access to the DDS

Access to information and data products in the HLS DDS is controlled via role-based authentication; only personnel that are identified as being part of an approved group will be permitted to see content associated with that group. In order to join a group, users will create a request in the NASA Asset Management System (NAMS) for the Moon2Mars SharePoint asset https://idmax.nasa.gov/nams/asset/254825. Each Contractor selected under Appendix H will select the contract they support, and approval for that role will be reviewed and approved by the COR for that contract. At the request of the Contractor, the role can be further subdivided into “read only” and “write” to limit which Contractor personnel can deliver content into the DDS. Once the NAMS request has been reviewed and approved, the user will automatically be provisioned into the DDS.

H-12

Usage Guide for the HLS Data Delivery System

The HLS DDS will be used primarily by the Contractor representatives, the Technical Monitors, and the NASA Contracting Officer Representatives to manage data provided to satisfy a DRD. There are no file size restrictions on the DDS; at the COR’s discretion an alternative location may be supplied for complex files such as CAD models.

All Deliveries

When a delivery is ready for submission, a Contractor representative will enter the HLS DDS at https://moon2mars ndc nasa.gov/HLS/DDS and create a new submission. They will attach the data file, provide the following information, and then submit:

● Contract Number

● Data Requirements Description Number

● DRD Data Type

● Document Number

● Document Revision

● Document Title

● Distribution

● Requested Response Date

● Targeted Release Date

● Contractor-Assigned Data Restriction

● NASA Records Retention Schedule (NRRS) number, if applicable

● Location of delivery (if not attached)

This submittal satisfies the requirement for a Data Transmittal Package per Section 2.3.4.3 of the DRD.

Type 1 Deliveries

If the delivery is Type 1, the submission will be placed into a review status. Email notifications will be sent to the distribution. Once the requiring organization has reviewed and approved the product, the COR will place the delivery submission into the “Approved” status and an email notification will be sent to the distribution. Should the requiring organization disapprove the delivery, the record will be placed in the “Disapproved” status and an email notification will be sent to the distribution. The resubmittal of a Type 1 delivery will be a separate submission record.

Type 2 Deliveries

If the delivery is Type 2, the submission will be placed into a review status. Email notifications will be sent to the distribution; a successful submission of the delivery will begin the 30-day review period. Once the 30-day review period has elapsed, the product will automatically be placed into the Approved status. The COR may move the submission into the “Approved” status manually if the review is completed prior to the 30th calendar day. Should the requiring organization disapprove the delivery, the record will be placed in the “Disapproved” status and an email notification will be sent to the distribution. The resubmittal of a Type 2 delivery will be a separate submission record.

Type 3 and 4 Deliveries

If the delivery is Type 3 or 4, the delivery will be placed into the “Delivered” status immediately upon submission. Email notifications will be sent to the distribution.

H-13

DDT&E Phase

DRD Number Data Type Title Proposal CBR PDR CDR DCR FRR Crewed

PMAR

1780CD-001 3 Technology Reports Delivered according to DRD

1780CM-001 2 Final Design Data Package F

(HDL)

F

(IL)

1780DE-001 3 Design Data Book I U B/L

1780DE-002 3 Integrated System Performance Analysis I U B/L X

1780DE-003 2 Gateway Cross-Program Engineering Models and Data

I ATP + 2 Months and 9-month reoccurring

U U U

1780DE-004 1 HDL Integrated Analysis Document

I and

9-month reoccurring

U U U

1780DE-005 3 Technology Readiness Level (TRL) Report I Delivered annually according to DRD

1780HS-001 2 Human Error Analysis (HEA) Plan I B/L U

45 days prior

1780HS-002 3 Human Error Analysis (HEA) Reports and Analyses I

45 days prior U

45 days prior U

1780HS-003 2 Human Systems Integration Plan I U B/L

1780HS-004 3 Human Systems Integration Reports and Analyses I

45 days prior U

45 days prior

1780HS-005 2 Food System Plan I * U B/L U

1780HS-006 2 Medical Kit Subsystem Plan I * U B/L U

1780LS-001 2 Government Property Management Plan I

ATP + 1 Month

1780LS-002 3 GFP in Custody of Contractors Delivered according to DRD

1780LV-001 1

Launch Vehicle/ Spacecraft Interface Control Document

(ICD) and Verification Matrix Delivered according to DRD

1780LV-002 2 Mission Specific Drawings Delivered according to DRD

1780LV-003 2 Launch Vehicle/Spacecraft Integrated Procedures Delivered according to DRD

H-14

Type Title Proposal CBR PDR CDR DCR FRR Crewed

PMAR

1780LV-004 2 Performance and Guidance Accuracy Analysis (PGAA) L-24 months

1780MA-001 2 Insight Implementation Plan I B/L X X

1780MA-002 2 Review Plan I B/L U U U

1780MA-003 3 Integrated Master Schedule I See DRD for detailed delivery schedule

1780MA-004 2 Risk Management Plan I B/L X X X

1780MA-005 3 Risk Reports I Reports are due monthly beginning at ATP

1780MA-006 3 Final Scientific and Technical Report F

1780MA-007 1 Organizational Conflict of Interest (OCI) Plan I

1780MA-008 3 Subcontractor and Geographic Data Collection I @

ATP + 6 Months Delivery annually according to DRD

1780MA-009 1 Information Technology Security Management Plan I @

ATP + 1 Month

1780MA-010 1 Project Protection Plan I @ ATP + 1 Month U U U U

1780MA-011 1 System Security Plan See DRD for detailed delivery schedule

1780MA-012 3 Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan ATP +1 Month Delivered annually according to DRD

1780MP-001 3

Orbital Debris Assessment

Reports (ODARs) and End of Mission Plan (EOMP)

I

6 Months before

CDR;

F

ODAR 45 days prior to FRR

1780OP-001 2 Flight Software Simulator I F

1780OP-002 2 Integrated Operations Training I U B/L Update once per year (as needed) for remainder of contract POP

1780OP-003 2 Mission Operations and Mission Systems Plan I U B/L U U U

1780OP-004 2 Lunar Orbit Checkout Plan I B/L U

1780RM-001 1 FMEA/CIL See DRD for detailed delivery schedule

H-15

Type Title Proposal CBR PDR CDR DCR FRR Crewed

PMAR

1780SA-001 1 System Safety Assessment Report (SSAR)

I Prelim Hazard

List

(PHL)

45 days prior

I Prelim Hazard

Report

(PHR)

45 days prior

Update PHR 30 days prior

B/L HR 45 days prior

U HR 30 days prior

1780SA-002 2 Safety and Mission Assurance (SMA) Plan I B/L

1780SA-003 2 Mishap Preparedness and Contingency Plan (MPCP)

I @

ATP + 4

Months

F

1780SA-004 3 Micrometeoroid Orbital Debris (MMOD) Report

I

Months before

CDR

F 45 days prior to DCR

1780SA-005 3 Planetary Protection Data

Pre-Launch Data

Pre-Launch

Data 120 days prior

1780SE-001 2 HLS Integrated Lander System Specification I B/L U U F

1780SE-002 2 Verification, Validation, and Certification Plan (VVCP) I B/L U U U

1780SE-003 1 Detailed Verification Objectives (DVOs) – Integrated Lander

I (Verification

Methods only) B/L F

1780SE-004 1 Verification Closure Notices (VCNs) – Integrated Lander I F

1780SE-005 2 Assembly, Integration and Test Plan

Overview and Objectives of

Testing Strategy

U B/L U

1780SE-006 3 Human Lander System (HLS) GNC Simulator Specification I B/L

H-16

*If Contractor opted for NASA to provide as GFP, this deliverable is not required.

Abbreviation Maturity Maturity Description I Initial First submittal of the product and is draft maturity; Draft is defined as “documentation of information before it goes under configuration control.”

May be submitted with proposal.

B/L Baseline Upon approval, document is placed under formal NASA configuration control.

U Update Revision driven by increased maturity as required. If document is Baselined, an update will result in a revision letter / number increment.

F Final No planned revision, but update may be driven by design maturing over program lifecycle.

X Current revision is required for the review, but updates are not required. May be updated at the Contractor’s discretion.

Note 1: This table is a quick reference for deliverable submittals; however, it does not capture all required submittals. Refer to the individual DRDs for submittal requirements and schedule.

Note 2: Regardless of maturity level, DRD deliverables provided to the Government must address each requirement within the DRD.

DDT&E Phase

DRD Number Data Type Title Proposal CBR PDR CDR DCR FRR Crewed

PMAR

1780SE-007 3 Avionics Emulator and Acceptance Data Package I F

1780SE-008 2 Human-class Delivery Lander (HDL) System Specification I B/L U U F

1780SE-009 3/2 Contractor’s Concept of Operations

I (Type 3)

U (Type 3)

B/L

PDR

–12 Months (Type 2)

U (Type 2)

X (Type 2)

1780SE-010 1

Detailed Verification Objectives

(DVOs) - HLS Human-class Delivery Lander (HDL)

(Verification Methods only)

B/L F

1780SE-011 1

Verification Closure Notices (VCNs) - HLS Human-class

Delivery Lander (HDL) I B/L

1780SE-012 3 Mission Performance Evaluation Reports and Data See DRD for detailed delivery schedule

1780SW-001 2 Software Verification, Validation, and Certification Plan I U B/L U X

1780SW-002 2 Software Plan (SP) I B/L U U X

H-17

DRD Submission Effectivity

App P: Sustaining Lunar Development (SLD) contract requires DRD content submissions for both the HLS Integrated Lander and the Human-class Delivery Lander (HDL) as applicable (based upon optional HDL CLIN awards and Contractor’s specific architecture). Each DRD has a specific scope that dictates how this information should be submitted.

Individual DRDs indicate which of three methods are appropriate:

1. The most common submission approach of the DRD contents will be in Volumized fashion to distinguish HLS Integrated Lander (Volume 1) versus HDL (Volume 2).

2. Some DRD Scope/Content applies more broadly and can be submitted in a single DRD submission that covers both HLS Integrated Lander and HDL contents.

3. Some DRD Scope/Content applies only to HLS Integrated Lander or HDL.

As Initial, Baselines, Updates, Changes are submitted, Volume submissions must be version controlled and may be submitted together in one file or separately at the Contractor’s choice. DRD content for HLS Integrated Lander and HDL may diverge as designs mature; the Contractor has the flexibility to change DRD delivery from one submission (Vol. 1 & Vol. 2) to two separate volume submissions.

The below language will be in the “REMARKS” section of each DRD with one of the three scenarios designated to that particular DRD submission “assumption.” As mentioned above, the Providers do have flexibility to discuss/justify and modify DRD submissions (two volumes to one volume, or one volume to two volumes, as this “shift” makes sense or as HDL CLIN options are awarded).

Scenario 1: This DRD assumes submission as two DRD Volumes: Volume 1 (HLS Integrated Lander) and Volume 2 (HDL, if awarded) based off the specific DRD scope and content of this DRD. Label each DRD Volume submission accordingly.

Scenario 2: This DRD assumes submission as one DRD submission to cover both HLS Integrated Lander and HDL (if awarded) scope and content. Assumption is that the HLS Integrated Lander and HDL content is virtually the same.

Differences shall be highlighted in the one submission covering both HLS Integrated Lander variants as appropriate.

Scenario 3: This DRD applies only to HLS Integrated Lander [HDL].

*If the Contractor’s DRM DDT&E maturity and milestone reviews for specific DRMs get out of sync for Volume 1 HLS Integrated Lander or Volume 2 HDL, then DRM specific data should be called out as an annex in each DRD Volume based off Contractor’s awarded plan and CLIN structure for reviews.

H-18

DATA REQUIREMENTS DESCRIPTION (DRD)

1. DPD NO.: 1780 ISSUE: RFP 2. DRD NO.: 1780CD-001

3. DATA TYPE: 3 4. DATE REVISED:

5. PAGE: 1/3

6. TITLE: Technology Reports

7. DESCRIPTION/USE: Provides NASA with technical information concerning any invention, discovery, improvement, or innovation made by a Contractor in the performance of work under this contract for the purpose of disseminating this information to obtain increased use and provide NASA with data to review for possible patentable items.

8. OPR: ST22 9. DM: LP40

10. DISTRIBUTION: Per Contracting Officer's letter

11. INITIAL SUBMISSION:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NASA Form 1679): Immediately or within three (3) months of identification of reportable item(s).

Interim NASA New Technology Summary Report (NTSR) Form: Twelve (12) months from the date of the contract.

Final NASA New Technology Summary Report (NTSR) Form: Immediately or within three (3) months after completion of contracted work. Final Payment is contingent upon submission of the Final NTSR.

12. SUBMISSION FREQUENCY:

Technology Reporting Plan: Upon Contracting Officer’s request.

Disclosure of Invention and New Technology (NASA Form 1679): Upon identification of each reportable item.

Interim NASA New Technology Summary Report (NTSR) Form: Every twelve (12) months.

Final NASA New Technology Summary Report (NTSR) Form: Immediately or within three (3) months after completion of contracted work. Final Payment is contingent upon submission of the Final NTSR.

13. REMARKS: Copies of NASA Form 1679 and the NASA New Technology Summary Report (NTSR) Form

(Interim and Final) may be obtained and/or filled out at: https://invention.nasa.gov/. These forms may also be obtained from the New Technology Representative (Sammy.Nabors@nasa.gov). This DRD assumes submission as one DRD submission to cover both HLS Integrated Lander and HDL (if awarded) scope and content.

Assumption is that the HLS Integrated Lander and HDL content is virtually the same. Differences shall be highlighted in the one submission covering both HLS Integrated Lander variants as appropriate.

14. INTERRELATIONSHIP: SOW Paragraph 4.4.1

15. DATA PREPARATION INFORMATION:

15.1 SCOPE: The Technology Reports include technical detail as is necessary to identify and fully describe a

"Reportable Item." Per NFS 1852.227-70, "Reportable Item" means any invention, discovery, improvement, or innovation of the Contractor, whether or not the same is or may be patentable or otherwise protectable under Title 35 of the United States Code, conceived or first actually reduced to practice in the performance of any work under this contract or in the performance of any work that is reimbursable under any clause in this contract providing for reimbursement of costs incurred prior to the effective date of this contract.

15.2 APPLICABLE DOCUMENTS/CLAUSES:

NFS 1852.227-70 New Technology Clause

H-19

DRD Continuation Sheet TITLE: Technology Reports DRD NO.: 1780CD-001

DATA TYPE: 3 PAGE: 2/3

15. DATA PREPARATION INFORMATION (CONTINUED):

15.3 CONTENTS: The Technology Reports consist of:

a. Disclosure of Invention and New Technology (Including Software): In accordance with NFS 1852.227-70

(e)(2), the disclosure to the agency shall be in the form of a written report and shall identify the contract under which the reportable item was made and the inventor(s) or innovator(s). It shall be sufficiently complete in technical detail to convey a clear understanding, to the extent known at the time of the disclosure, of the nature, purpose, operation, and physical, chemical, biological, or electrical characteristics of the reportable item. The disclosure shall also identify any publication, on sale, or public use of any subject invention and whether a manuscript describing such invention has been submitted for publication and, if so, whether it has been accepted for publication at the time of disclosure. In addition, after disclosure to the agency, the Contractor shall promptly notify the agency of the acceptance of any manuscript describing a subject invention for publication or of any on sale or public use planned by the Contractor for such invention.

This reporting requirement may be met by completing NASA Form 1679 (latest revision) in hardcopy or online at: https://invention.nasa.gov/. Use of this form or the online system is preferred; however, if the form is not used the following information should be provided in order to meet the reporting requirement:

1. Descriptive title.

2. Innovator(s) name(s), title(s), phone number(s), and home address(es).

3. Employer when innovation made (name and division).

4. Address (place of performance).

5. Employer status (e.g., Government, college or university, non-profit organization, small business firm, large entity).

6. Origin (e.g., NASA grant number, NASA prime contract number, subcontractor, joint effort, multiple

Contractor contribution, other).

7. NASA Contracting Officer’s Representative (COR).

8. Contractor/grantee New Technology Representative.

9. Brief abstract providing a general description of the innovation:

(a) Description of the problem or objective that motivated the innovation’s development.

(b) Technically complete and easily understandable description of innovation developed to solve or meet the objective.

(c) Unique or novel features of the innovation and the results or benefits of its application.

(d) Speculation regarding potential commercial applications and points of contact (including names of companies producing or using similar products).

10. Additional documentation.

11. Degree of technological significance (e.g., modification of existing technology, substantial advancement in the art, major breakthrough).

12. State of development (e.g., concept only, design, prototype, modification, production model, used in current work).

13. Patent status.

14. Dates or approximate time period during which this innovation was developed.

15. Previous or contemplated publication or public disclosure including dates.

16. Answers to the following questions (for software only):

(a) Using outsiders to beta-test code? If yes, done under beta-test agreement?

(b) Modifications to this software continue by civil servant and/or contractual agreement?

(c) Previously copyrighted (if so, by whom?)?

(d) Were prior versions distributed (if yes, supply NASA or Contractor contract)?

(e) Contains or is based on code owned by a non-federal entity (if yes, has a license for use been obtained?)?

(f) Has the latest version been distributed without restrictions as to use or disclosure for more than one year (if yes, supply date of disclosure)?

17. Name(s) and signature(s) of innovator(s).

H-20

TITLE: Technology Reports DRD NO.: 1780CD-001

DATA TYPE: 3 PAGE: 3/3

15. DATA PREPARATION INFORMATION (CONTINUED):

b. Interim NASA New Technology Summary Report (NTSR): This report shall consist of a listing of reportable items for the reporting period or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts.

Completion of the Interim NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at: https://invention.nasa.gov/ is preferred; however, an alternate format is acceptable provided all required information is provided.

c. Final NASA New Technology Summary Report (NTSR): This report shall consist of a comprehensive list of all reportable items for the contract duration or certification that there are none. This report shall also contain a list of subcontracts containing a patent rights clause or certification that there were no such subcontracts. Completion of the Final NTSR shall satisfy this reporting requirement. Use of the form utilizing the online system at: https://invention.nasa.gov/ is preferred; however, an alternate format is acceptable provided all required information is provided.

d. Subcontracts: The Contractor shall provide copies of subcontracts containing a patent rights clause upon Contracting Officer’s request.

15.4 FORMAT: To report a Disclosure of Invention and New Technology (Including Software) NASA Form 1679

(latest version) may be used or submit the report online at: https://invention.nasa.gov/, or provide sufficient information to meet the reporting requirement.

The interim and final NASA New Technology Summary Reports may use the NTSR Form (Interim or Final whichever is applicable) utilizing the online system at: https://invention nasa.gov/, or provide sufficient information to meet the reporting requirement.

15.5 MAINTENANCE: None required

H-21

1. DPD NO.: 1780 ISSUE: RFP 2. DRD NO.: 1780CM-001

3. DATA TYPE: 2 4. DATE REVISED:

5. PAGE: 1/2

6. TITLE: Final Design Data Package

7. DESCRIPTION/USE: Contractor shall provide final Computer-Aided Design (CAD) models and/or design drawings, system data books, interface control documents/models, flight software and associated lists for the Human Landing System (HLS) Integrated Lander and Human-class Delivery Lander (HDL).

8. OPR: LP10 9. DM: LP01

11. INITIAL SUBMISSION: HDL at Design Certification Review (DCR); Integrated Lander at Post Mission

Assessment Review (PMAR)

12. SUBMISSION FREQUENCY: Single submission for HDL at DCR and for the Integrated Lander at PMAR

13. REMARKS: This DRD assumes submission as two DRD Volumes: Volume 1 (HLS Integrated Lander) and

Volume 2 (HDL, if awarded) based off the specific DRD scope and content of this DRD. Label each DRD Volume submission accordingly.

14. INTERRELATIONSHIP: DRDs 1780LV-001, Launch Vehicle/Spacecraft ICD(s), 1780LV-002, Mission

Specific Drawings, 1780LV-003, Launch Vehicle/Spacecraft Integrated Procedures, 1780SA-001, System Safety Assessment Report (SSAR), 1780SE-001, HLS Integrated Lander System Specifications and 1780SW-002, Software Plan. SOW Paragraphs 6.4.6.5 and 6.5.4

15.1 SCOPE: The Integrated Lander Final Design Data Package provides the HLS Integrated Lander, to include flight software, flight operations, and launch vehicle/spacecraft operations and processing.

15.2 APPLICABLE DOCUMENTS/CLAUSES: None

15.3 CONTENTS: The HLS Integrated Lander Final Design Documentation shall be submitted via distinct Volume

1 (crew) and Volume 2 (cargo) submissions including:

a. CAD models, and associated engineering drawings, to include Interface Drawings:

1. CAD Models shall be sufficient to depict the detailed configuration of all system, subsystem, and component levels and to include ground support equipment (GSE)…