Attachment G - Statement of Work (SOW).pdf

NextSTEP-2 Appendix P, HLS SLD BAA

Attachment G, Statement of Work

09/16/22

G-1-1

Sustaining Lunar Development (SLD)

Statement of Work (SOW)

G-1-2

Change Log

Version Description of Changes Date

Draft N/A March 31, 2022

RFP September 16, 2022

G-1-3

Table of Contents

Table of Contents

List of Tables and Figures

1.0 Introduction

2.0 Scope

2.1 Definitions

2.2 Roles and Responsibilities

3.0 Contract Documentation

3.1 Applicable Documents

3.2 Reference Documents

4.0 Program Requirements

4.1 Technical Direction

4.2 Data Deliverables

4.2.1 Documentation and Reporting of Work

4.2.2 Data Rights

4.3 Export Controls

4.3.1 International Traffic in Arms Regulation

4.3.2 Export Administration Regulations

4.3.3 Public Release

4.4 Technology Reporting

4.4.1 Technology Reports

4.4.2 Technology Readiness Levels

4.4.3 Final Scientific and Technical Report

4.5 Special Studies and Tasks (CLIN 002)

4.6 Government-Provided Resources

4.6.1 Government-Furnished Property

4.6.2 Integration of Government-Furnished Property

4.6.3 GTA, GFP and other Government Resources Available Working On-site at a NASA Facility

4.6.4 Collaboration

4.6.5 Government-Furnished Information

4.7 Cybersecurity and Project Protection

4.7.1 Contractor Use of NASA Systems

4.7.2 Cybersecurity for Covered Contractor Systems

4.7.3 Information Technology Security Management Plan

4.7.4 Project Protection Plan

4.8 Security Clearances

4.9 Organizational Conflict of Interest (OCI) Plan

4.10 Diversity, Equity, Inclusion, and Accessibility Plan

4.11 Changes, Waivers, and Deviations to Technical Requirements

4.12 Programmatic Deliveries and Reviews

G-1-4

4.12.1 Integrated Master Schedule (IMS) and Schedule Risk Assessment (SRA)

4.12.2 Risk Management

4.12.3 Program Management Reviews

4.12.4 Artemis Tests, Reviews and Technical Interchange Meetings

4.12.5 Artemis Mission Support

4.13 NASA Resident Office

4.14 Public Relations

5.0 HLS Design, Development, Test & Evaluation

5.1 NASA Insight

5.2 Requirements and Interface Development

5.2.1 Requirements Development, Analysis and Management

5.2.2 Technical Standards

5.2.3 Concept of Operations

5.2.4 Docking Adapter

5.2.5 Excess Capability

5.2.6 Trash Disposal

5.3 Interface Definition, Allocation, Verification, and Control

5.3.1 Internal Interface Development

5.3.2 Interface Requirements Document Development

5.3.3 Interface Analysis

5.3.4 Interface Control Document (ICD) Development and Control

5.3.5 Interfaces with NASA On-Site Resources and Government-Furnished Property

5.4 Mission Design and Analysis

5.4.1 Mission Design

5.4.2 Design, Analysis and Trades

5.4.3 Integrated Analysis

5.4.4 Simulators and Emulators

5.5 Assembly, Integration and Test (AI&T)

5.5.1 Assembly, Integration and Test (AI&T) Plan

5.6 Verification, Validation, and Certification

5.6.1 Verification, Validation and Certification Planning

5.6.2 Software Verification and Validation

5.6.3 Verification Closure Notices

5.6.4 Software Independent Verification and Validation (IV&V)

5.7 Launch Vehicle

5.7.1 Launch Vehicle Insight

5.7.2 NASA Launch Vehicle Independent Risk Assessments

5.7.3 Launch Vehicle Mission Integration and Analysis

5.7.4 Launch Site Access

5.8 Safety and Mission Assurance

5.8.1 Safety and Mission Assurance Responsibilities

5.8.2 System Safety

5.8.3 Industrial Safety, Health and Environmental Protection

5.8.4 Reliability and Maintainability

5.8.5 Software Assurance

5.8.6 Quality Assurance

5.8.7 Micrometeoroid Orbital Debris (MMOD) and Orbital Debris Assessment Reports (ODAR)

G-1-5

5.8.8 Anomaly Investigation and Corrective Action

5.8.9 Mishap Preparedness and Reporting

5.8.10 Planetary Protection

5.9 Human Health and Medical

5.9.1 Human Systems Integration Plan

5.9.2 Human Error Analysis and Task Analysis

5.9.3 Human Factors Analysis

5.9.4 Operational Interfaces (CLINs 001 and 003-005)

5.9.5 Toxicological Assessment of Chemicals to be Flown on Manned Spacecraft

5.9.6 Decompression Sickness Protocol and Treatment

5.9.7 Human Systems Best Practices (CLINs 001 and 003-005)

5.9.8 Medical Operations (CLINs 001 and 003-005)

5.9.9 Food (CLINs 001 and 003-005)

5.9.10 Medical Kit Subsystem (CLINs 001 and 003-005)

5.10 Flight Operations and Operations Support

5.10.1 Overview

5.10.2 Mission Planning and Operations Product Development

5.10.3 Integrated Operations Training

5.10.4 Mission Execution

5.10.5 HDL Flight Operations

6.0 SLD Milestone Reviews

6.1 Program Review Plan

6.2 Contractor-Proposed Milestone Reviews

6.3 Government-Mandated Milestone Reviews

6.4 Integrated Lander Reviews

6.4.1 Integrated Lander Certification Baseline Review (CBR), CLIN 001

6.4.2 Integrated Lander Preliminary Design Review (PDR), CLIN 001

6.4.3 Integrated Lander Critical Design Review (CDR), CLIN 003

6.4.4 Uncrewed Flight Test, CLIN 004

6.4.5 Integrated Lander Design Certification Review (DCR), CLIN 004

6.4.6 Integrated Lander Crewed Demonstration Sortie Mission, CLIN 005

6.5 Human-class Delivery Lander (HDL) Reviews

6.5.1 HDL Certification Baseline Review (CBR), CLIN 006

6.5.2 HDL Preliminary Design Review (PDR), CLIN 006

6.5.3 HDL Critical Design Review (CDR), CLIN 007

6.5.4 HDL Design Certification Review (DCR), CLIN 008

Acronyms and Abbreviations

G-1-6

List of Tables and Figures

Table 2.1: SLD CLIN Structure

Table 3.1: Applicable Documents

Table 3.2: Reference Documents

Table 4.1: Government Provided Resource Requirements

Table 5.10.4.4.1: Description of HLS Flight Operations Phases

Table 5.10.4.4.2: HLS Flight Operations Phases and Operational Modes

Table 5.10.5.3.1: Description of HDL Flight Operations Phases

Table 5.10.5.3.2: HDL Flight Operations Phases and Operational Modes

Table 6.3.1a: Integrated Lander Milestone Review-CLIN Applicability Matrix

Table 6.3.1b: HDL Milestone Review-CLIN Applicability Matrix

Table 6.4.1: Integrated Lander CBR Acceptance Criteria and Applicable Products

Table 6.4.2: Integrated Lander PDR Acceptance Criteria and Applicable Products

Table 6.4.3: Integrated Lander CDR Acceptance Criteria and Applicable Products

Table 6.4.4.1: Uncrewed FTRR Acceptance Criteria

Table 6.4.4.4: Uncrewed Flight Test PMAR Acceptance Criteria

Table 6.4.5: Integrated Lander DCR Acceptance Criteria and Applicable Products

Table 6.4.6.1: Crewed Demonstration Mission FRR Acceptance Criteria

Table 6.4.6.5: Crewed Demonstration Mission PMAR Acceptance Criteria

Table 6.5.1: HDL CBR Acceptance Criteria and Applicable Products

Table 6.5.2: HDL PDR Acceptance Criteria and Applicable Products

Table 6.5.3: HDL CDR Acceptance Criteria and Applicable Products

Table 6.5.4: HDL DCR Acceptance Criteria and Applicable Products

G-1-7

1.0 Introduction

The National Aeronautics and Space Administration (NASA) is committed to developing an affordable and sustainable human transportation service capability to explore and perform science on the lunar surface. NASA’s Human Landing System (HLS) Program will provide human and large payload lunar transportation services as part of the sustainable Artemis framework. This includes development of both a crew transportation capability via an HLS

Integrated Lander as well as a large payload transportation capability via a cargo variant of the

Integrated Lander, known as the Human-class Delivery Lander (HDL).

2.0 Scope

This Statement of Work (SOW) encompasses all Design, Development, Test, and Evaluation

(DDT&E) work to be performed to reach certification of a system that demonstrates a sustaining exploration capability to the Moon and beyond. The work to be performed for SLD is provided through the Contract Line-Item Number (CLIN) structure in Table 2.1.

Table 2.1: SLD CLIN Structure

Base CLINs Description Applicable Design

Reference

Mission(s) (DRMs)

001 HLS Integrated Lander Design, Development, Test and Evaluation (DDT&E) through PDR including, but not limited to, the design and development of the

HLS Integrated Lander and coordination and integration with commercial provider launch vehicle contractors. This CLIN concludes 30 days after successful completion of a Preliminary Design

Review (PDR) of the Integrated Lander

DRM-001

DRM-002

002 IDIQ – Special Studies and Tasks includes, but is not limited to, trade studies, risk reduction tasks and other tasks in support of HLS development phases.

Options CLINs Each CLIN is a separate priced option

CLINs 003-005

Description:

Integrated Lander Continued DDT&E including, but not limited to, further maturation of the design, development, and fabrication of the HLS Integrated

Lander, hardware, and execution of system test and evaluation.

003 Integrated Lander DDT&E Through CDR includes further maturation of the design and development of the HLS Integrated Lander hardware, software, and support systems to establish readiness for full-scale

DRM-001

DRM-002

G-1-8 fabrication. This CLIN concludes 30 days after successful completion of CDR.

004 Integrated Lander DDT&E Through DCR includes execution of an uncrewed flight test and supporting reviews, including a Flight Test Readiness Review a

Post-Mission Assessment Review (PMAR) of the flight test. The CLIN concludes 30 days after successful completion of an Integrated Lander Design

Certification Review (DCR), ensuring that the qualification and verifications demonstrate design compliance with Integrated Lander functional and performance requirements.

DRM-001

DRM-002

005 Integrated Lander Through Crewed

Demonstration Sortie Mission consists of execution of a crewed mission to the lunar surface and the return of the crew and science to the Gateway in cislunar orbit. The CLIN includes a Post-Mission Assessment

Review (PMAR) of the crewed mission.

DRM-001

CLINs 006-008

Description:

Human-Class Delivery Lander (HDL) DDT&E including, but not limited to, design and development efforts for Integrated and Offloaded cargo variants of the Integrated Lander, known as Human-class

Delivery Landers (HDLs) for large lunar surface payloads.

006 HDL DDT&E through PDR includes a Certification

Baseline Review (CBR) and concludes 30 days after successful completion of a Preliminary Design

Review (PDR) of the HDL.

DRM-C-001

DRM-C-002

007 HDL DDT&E Through CDR includes further maturation of the design and development of the HDL to demonstrate that the maturity of the design is appropriate to support proceeding with full-scale fabrication, assembly, integration, and test. This

Option concludes 30 days after successful completion of a Critical Design Review (CDR)

DRM-C-001

DRM-C-002

008 HDL DDT&E Through DCR includes completion of a Design Certification Review (DCR) for the HDL, ensuring that the qualification and verifications

DRM-C-001

DRM-C-002

G-1-9 demonstrate design compliance with HDL functional and performance requirements.

This SOW applies to all work to meet NASA requirements and objectives for the HLS as documented in HLS-RQMT-006, HLS Integrated Lander Requirements Document - Sustained

Phase, HLS-RQMT-007, HLS Human-Class Delivery Lander (HDL) Requirements Document -

Sustained Phase, and Interface Requirements Documents (IRDs) as listed in the Applicable

Documents section of each System Requirements Document.

The use of the words “shall”, “will”, “should”, and “may” are defined as follows:

A. Shall – Requirement: “Shall” is used to indicate a requirement, meaning it must be implemented, and its implementation verified.

B. Will – Fact: “Will” is used to indicate a statement of fact, declaration of purpose, or expected occurrence.

C. Should – Expectation: “Should” denotes a statement of best practice or intent.

D. May – Possible: “May” identifies what is allowable.

2.1 Definitions

Except as specified otherwise, the following terms have the following given definitions throughout the entire SOW, but only when capitalized and used in their full-length format (e.g., when the SOW uses the word “element,” it is not referring to a defined term unless the full term is used and it is capitalized, such as “Integrated Lander Element”):

• Human Landing System (HLS): All Integrated Lander Elements, HDL Elements, Contractor Mission Systems, Supporting Spacecraft, and launch vehicles that are designed, developed, and/or utilized by the contractor, its teammates, subcontractors, and/or suppliers in the performance of this contract.

• Human-class Cargo: A Class A or B payload (as defined in NPR 8705.4A, Risk

Classification for NASA Payloads) that requires crew interaction on the lunar surface.

Examples include, but are not limited to, a lunar pressurized rover and lunar surface habitat.

• Human-class Delivery Lander (HDL): A single HDL Element or collection of HDL

Elements that, when integrated: (1) provide transportation for Human-class Cargo from the

Earth to the lunar surface; but (2) do not provide transportation to crew.

• Human-class Delivery Lander (HDL) Element: A spacecraft capable of operating independently of other spacecraft and that is also either: (1) used to transport Human-class

Cargo to the lunar surface during uncrewed missions; or (2) connected to other spacecraft at any time when those spacecraft are used to transport Human-class Cargo to the lunar surface during uncrewed missions.

• Integrated Lander: Any combination of Integrated Lander Elements, including potentially a single Integrated Lander Element, that is used for crew transportation, and is integrated at

G-1-10 any time crew are onboard. Any docking adapter utilized by the contractor during the performance of this contract is considered a part of the Integrated Lander.

• Integrated Lander Element: A spacecraft capable of operating independently of other spacecraft and that is also either: (1) used to transport crew during the performance of crewed missions; or (2) connected at any time to other spacecraft while the other spacecraft is transporting crew during the performance of this contract. Examples of an Integrated

Lander Element may include, but are not limited to, Ascent, Descent, or Transfer elements.

• Mission Systems: The end-to-end terrestrial based hardware and software infrastructure, whether owned or operated by NASA or the contractor, supporting mission operations from the point of Radio Frequency (RF) receipt/transmit at RF communications ground sites, through associated data processing and distribution infrastructure, transport networks, mission control center systems and facilities, interfaces between operations facilities, to the end user display/control systems and support infrastructure. Mission Systems include all associated hardware and software infrastructure supporting crew and flight controller training for operations, including but not limited to simulations, networks, mockups, and interfaces to support infrastructure.

• NASA Mission Systems: Mission Systems provided by NASA.

• Contractor Mission Systems: Mission Systems provided by the contractor.

• Supporting Spacecraft: A spacecraft capable of operating independently of other spacecraft that is required for the contractor to execute its responsibilities pursuant to the terms of this contract, but that is not an Integrated Lander Element, an HDL Element, nor a launch vehicle. Supporting Spacecraft functions could include, but are not limited to, propellant transfer, propellant storage, or orbital maneuvering and transfer.

The comprehensive list of acronyms, abbreviations, and definitions used in the SOW and the

Data Procurement Document 1780 can be found at the end of this document.

2.2 Roles and Responsibilities

The roles and responsibilities of the HLS contractors and the Government will reflect the stated desire to leverage commercial products and processes to the maximum extent practical and will rely on a Government-Industry collaborative approach. To that end, the HLS contractors will be responsible for all activities associated with the design, development, manufacture, test, system verification, system demonstration, and system operation of the HLS with the following primary exceptions:

• The Government will have a shared responsibility for validating that the content of the contractor proposed milestone reviews comply with the applicable acceptance criteria.

• The Government will have a shared responsibility for the HLS Safety and Engineering

Review Panel (HSERP) as described in Section 5.8.2.

• The Government will have responsibility for approving all changes in contract requirements and for approving acceptance of deliverables, as required by corresponding

Data Types.

G-1-11

• The Government will have responsibility for approving verification closures of NASA HLS requirements.

• The Government will have responsibility for Certification of Flight Readiness (CoFR) for the crewed demonstration mission.

• The Government will have responsibility for critical Artemis mission Go/No Go calls during on-orbit crewed and lunar surface operations of the HLS. The Government and contractor will operate in accordance with the primary and shared responsibility for critical mission operational phases for both the Integrated Lander and HDL as shown in Tables

5.10.4.4.2 and 5.10.5.3.2.

• The Government will have responsibility for software Independent Verification and

Validation (IV&V).

3.0 Contract Documentation

3.1 Applicable Documents

The following documents include specifications, standards, and other special publications. The documents listed in this section are applicable to the extent specified herein.

Table 3.1: Applicable Documents

Document No.

Effective

Date Document Title

ACD-52105 Draft Artemis Campaign Development Medical

Operations Requirements Document (MORD)

GP 10031-01 12/2/2021 Gateway to Visiting Vehicle (VV) IRD Annex 1

HLS-PLAN-004, Rev B 45/2022 Human Landing System (HLS) Configuration and

Data Management Plan

HLS-PLAN-011 2/2/2021

Human Landing System (HLS) Program Mishap

Preparedness and Contingency Plan

HLS-RQMT-006, Rev

A+HLS-MD-0011

7/7/2022

HLS Integrated Lander Requirements Document -

Sustained Phase

HLS-RQMT-007, Rev A 6/27/2022 HLS Human-Class Delivery Lander (HDL)

Requirements Document - Sustained Phase

JSC 27472 8/2019

Requirements for Submission of Data Needed for Toxicological Assessment of Chemicals to be Flown on Manned Spacecraft

JSC-35191 2/8/22 Artemis Flight Operations Standards

NASA-STD-8729.1A 6/13/2017

NASA Reliability and Maintainability (R&M)

Standard for Spaceflight and Support Systems

NASA-STD-8739.8A 6/10/2020 Software Assurance and Software Safety Standard

G-1-12

Document No.

Effective

Date Document Title

NPD 8610.7D 3/29/2018

Launch Services Risk Mitigation Policy for NASA-

Owned and/or NASA-Sponsored Payloads/Missions

NPR 7123.1C 2/14/2020

NASA Systems Engineering Processes and

Requirements

NPR 7150.2D 3/8/2022 NASA Software Engineering Requirements

NPR 8000.4B 12/6/2017 Agency Risk Management Procedural Requirements

NPR 8715.24 9/24/2021

Planetary Protection Provisions for Robotic

Extraterrestrial Missions

NPR 8735.2C 3/12/2021

Hardware Quality Assurance Program

Requirements for Programs and Projects

SAE AS9100D 9/20/2016

Quality Management Systems – Requirements for

Aviation, Space and Defense Organizations

3.2 Reference Documents

The following documents contain supplemental information to guide the user in the application of this document.

Table 3.2: Reference Documents

Document No.

Effective

Date Document Title

HLS-CONOP-006, Rev A 6/29/2022 Sustained Phase Human Landing System (HLS)

Concept of Operations

HLS-CONOP-007, Rev A 6/29/2022 Human-Class Delivery Lander (HDL) Concept of

Operations (CONOPS)

HLS-MOA-001, Rev A 4/14/2022

HLS Program FY21 Software Independent

Verification & Validation (IV&V) Project

Execution Plan (IPEP)

HLS-PLAN-003 Rev B 7/23/2021 HLS Safety and Mission Assurance (SMA) Plan

HLS-PLAN-013 Rev B 12/15/2021 HLS Program Planetary Protection Plan

HLS-VV-002, Rev A 7/1/2022 Human Landing System (HLS) Verification

Guidebook

JSC-35194, Rev A 7/25/2022 Mission Training Center Generic Training

Simulation Interface Specification

JSC-35199 7/29/2022 MCC Interface Specification

NASA/SP-2010-3407 Rev 1 6/5/2014 Human Integration Design Handbook

NASA/SP-20210010952 11/2015 NASA Human Systems Integration Handbook

NASA-STD-3001, Volume 1 1/5/2022 NASA Space Flight Human Systems Standard

Crew Health

G-1-13

Document No.

Effective

Date Document Title

NASA-STD-3001, Volume 2 9/9/2019

NASA Space Flight Human Systems Standards

Human Factors, Habitability, and Environmental

Health

NPR 8621.1D 7/6/2020

NASA Procedural Requirements for Mishap and

Close Call Reporting, Investigation and

Recordkeeping.

NPR 8705.4A 4/29/2021 Risk Classification for NASA Payloads

NPR 8715.7B 4/27/2020

Expendable Launch Vehicle Payload Safety

Program

NPR 8735.1D 7/29/2018

Exchange of Problem Data Using NASA

Advisories and the Government-Industry Data

Exchange Program (GIDEP).

4.0 Program Requirements

Unless otherwise specified, the requirements outlined in this section apply to the entirety of the

SLD contract.

4.1 Technical Direction

Performance of the work under this contract is subject to the written technical direction of the

Contracting Officer’s Representative (COR), who shall be specifically appointed by the

Contracting Officer (CO) in writing in accordance with NASA Federal Acquisition Regulations

(FAR) Supplement 1801.602-2. ‘‘Technical direction’’ means a directive to the contractor that approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; and/or furnishes similar instruction to the contractor. Technical direction includes requiring studies and pursuit of certain lines of inquiry regarding matters within the general tasks and requirements of the contract. All Technical direction shall be issued in writing by the COR.

The COR does not have the authority to, and shall not, issue any instruction purporting to be technical direction that—

A. Constitutes an assignment of additional work outside this SOW

B. Constitutes a change as defined in the Changes clause of the contract.

C. Constitutes a basis for any increase or decrease in the total contract price or the time required for contract performance.

D. Changes any of the expressed terms, conditions, or specifications of the contract.

E. Interferes with the contractor’s rights to perform the terms and conditions of the contract.

The contractor shall proceed promptly with the performance of technical direction duly issued by the COR in the manner prescribed by this section of the SOW and within the COR’s authority.

If, in the contractor’s opinion, any instruction or direction by the COR falls within any of the

G-1-14 categories defined in items A through E above, the contractor shall not proceed but shall notify the CO in writing within five (5) working days after receiving it and shall request the CO to act as described in this section of the SOW. Upon receiving this notification, the CO shall either issue an appropriate contract modification within a reasonable time or advise the contractor in writing within 30 days that the instruction or direction is:

A. Rescinded in its entirety; or

B. Within the requirements of the contract and does not constitute a change under the Changes clause of the contract, and that the contractor shall proceed promptly with its performance.

A failure of the contractor and CO to agree that the instruction or direction is within the requirements of the contract and/or does not constitute a change under the Changes clause, or a failure to agree upon the contract action to be taken with respect to the instruction or direction, shall be subject to the Disputes clause of this contract.

Any action(s) taken by the contractor in response to any direction given by any person other than the CO or the COR shall be at the contractor’s risk.

4.2 Data Deliverables

4.2.1 Documentation and Reporting of Work

The contractor shall perform the management functions to ensure accomplishment of all activities described in this SOW including delivery of the data required by this contract. The contractor shall report and document the performance of this work in the SOW and fulfill the requirements of the associated Data Requirements Description (DRD) as outlined in Data

Procurement Document 1780 (Attachment J-02). The contractor shall determine the data restriction that applies to each data deliverable and mark or transmit the data restriction in accordance with section 2.3.3 of the Data Procurement Document (DPD).

4.2.2 Data Rights

The contractor shall determine the data restriction that applies to each data deliverable and mark or transmit the data restriction in accordance with FAR 52.227-14 Rights in Data – General

(Deviation) and Section H clause MARKING REQUIREMENTS FOR TECHNICAL DATA AND

COMPUTER SOFTWARE.

4.3 Export Controls

The contractor shall perform an export control assessment for all data deliverable items shown in the DPD 1780 (Attachment J-02). Due to the additional overhead in storing and handling

International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR) materials, the contractor should only mark data that has been specifically identified under this designation and should not globally mark all data as ITAR and/or EAR by default.

4.3.1 International Traffic in Arms Regulation

If a product is determined to contain information controlled by ITAR Regulations, the following statement shall be included on the product cover page:

G-1-15

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.

4.3.2 Export Administration Regulations

If a product is determined to contain information controlled by EAR and which requires a license or exception prior to export, the following statement shall be included on the product cover page:

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.

4.3.3 Public Release

For Export Control purposes, if a product has been determined by the contractor and the

Government to be suitable for public release, it shall be labeled as such by the contractor.

4.4 Technology Reporting

4.4.1 Technology Reports

The contractor shall provide NASA with technical information concerning any invention, discovery, improvement, or innovation made by the contractor in the performance of work under this contract in accordance with DRD 1780CD-001, Technology Reports.

4.4.2 Technology Readiness Levels

The contractor shall define Technology Readiness Levels (TRLs) and provide a technology maturation plan for critical technologies required to accomplish the mission within context of the contractor’s HLS architecture. The TRLs shall be defined in accordance with Appendix E of

NPR 7123.1, NASA Systems Engineering Processes and Requirements, and shall be delivered in accordance with DRD 1780DE-005, Technology Readiness Levels.

4.4.3 Final Scientific and Technical Report

The contractor shall prepare and submit a Final Scientific and Technical Report summarizing the results of the entire contract effort, including recommendations and conclusions based on the

G-1-16 experience and results obtained, in accordance with DRD 1780MA-006, Final Scientific and

Technical Report.

4.5 Special Studies and Tasks (CLIN 002)

In accordance with the task ordering procedures in this contract, the contractor shall perform special studies and analyses, provide materials, and/or fabricate incidental hardware, as required.

Each task will be initiated by written direction from the NASA CO. These tasks include advance planning and feasibility studies in support of future contemplated missions; development, fabrication, and test of hardware/software to support planning studies or special tests; mission or cargo unique studies; material provision; and implementation of changes required due to changes in requirements.

4.6 Government-Provided Resources

NASA is making a variety of Government-provided resources available to the contractor for use on this contract. Some of these resources are required for use by the contractor during performance, while others are optional. As a general overview, NASA is making the following items available under this contract:

Table 4.1: Government Provided Resource Requirements

Type of

Resource

Listed in

Contract

Special

Agreement

Required

Applicable Property-specific contract clauses

GFP Attachment J-03 Yes for

Optional*

Contractor Use of Government-Furnished

Equipment, Property, or Information

52.245-1, Government Property (ALT 1)

52.245-9, Use and Charges

1852.245-73, Financial Reporting of NASA

Property in the Custody of Contractors

1852.245-75, Property Management Changes

1852.245-76, List of Government Property

Furnished Pursuant to FAR 52.245-1

1852.245-78, Physical Inventory of Capital

Personal Property

NASA On-

Site

Resources*

Attachment J-15 Yes – GTA

Use of Government Resources

1852.245-71, Installation - Accountable

Government Property, if applicable

G-1-17

Type of

Resource

Listed in

Contract

Special

Agreement

Required

Applicable Property-specific contract clauses

1852.245-82, Occupancy Management

Requirements (if contractor will be operating on-site)

* No special agreement is needed for mandatory GFP. All Optional GFP requires an

Optional Government Furnished Property Agreement (OGFPA) form to be submitted and coordinated prior to proposal submittal. New OGFPAs are required for GFP added anew during contract performance, and the terms of all OGFPAs will apply to the GFP that they respectively cover.

* If added anew during contract performance, the cost is the responsibility of the contractor.

4.6.1 Government-Furnished Property

The list of mandatory Government-Furnished Property (GFP) and optional GFP requested by the contractor and agreed to by the Government will be captured in Attachment J-03, Government

Furnished Property (GFP). The contractor will complete an Optional Government Furnished

Property Agreement (OGFPA) for each requested optional GFP. Upon contract award, the

OGFPAs will be subject to formal review and approval by the HLS program manager or designee and CO. Once the final terms and conditions of the provision of the GFP have been finalized by NASA and the contractor (such as delivery date), and any funding has been secured from the appropriate NASA organization if needed, the approved OGFPA will become an attachment to the contract authorizing the contractor to proceed with the OGFPA(s). NASA will also update Attachment J-03 for any GFP furnished to the contractor. NASA has indicated in

Attachment J-03 which GFP items may be consumed during performance (“Consumable

Property” such as depleted resources or material/equipment not planned for reuse after serving its intended purpose). Items not consumed shall be returned to NASA at the end of performance.

The GFP items agreed to upon award are provided to the contractor at no cost and are provided subject to the specific property contract clauses indicated in Table 4.1.

The contractor may inquire at the NASA Centers to determine the availability of any additional

GFP requested during contract performance. The Contractor shall submit an OGFPA through the

COR to document the agreement between NASA and the contractor to potentially provide one or more of these requested items of GFP subject to Contracting Officer approval.

Any items provided to the contractor shall be included in Attachment J-03 prior to delivery of the

GFP. If not consumed during contract performance, the GFP shall be returned to NASA. These items are provided subject to the specific property contract clauses indicated in the table above.

The contractor shall develop and deliver a property plan which describes the contractor’s methods and processes for the identification, control, maintenance, and safeguard of Government property in accordance with DRD 1780LS-001, Government Property Management Plan.

The contractor shall prepare and maintain a report in accordance with DRD 1780LS-002, Annual and Monthly Financial Reporting of National Aeronautics and Space Administration (NASA)

Property in the Custody of Contractors, identifying and listing all equipment, tools, etc., provided

G-1-18 by the Government for use by the contractor in the performance of contracted effort, and for which the contractor has been given physical custody.

The contractor assumes the risk of, and shall be responsible for, any loss of GFP upon its delivery to the contractor as GFP. The contractor is responsible for the cost of replacement or purchase of these items, if needed. These items are provided “as-is.”

4.6.2 Integration of Government-Furnished Property

In accordance with contract H clause CONTRACTOR USE OF GOVERNMENT-FURNISHED

EQUIPMENT, PROPERTY, OR INFORMATION paragraph (g) CONTRACTOR

RESPONSIBILITY, the contractor shall be responsible for the integration of any GFP into their

HLS design.

4.6.3 GTA, GFP and other Government Resources Available Working On-site at a

NASA Facility

In accordance with contract H clause USE OF GOVERNMENT RESOURCES and 1852.245-82

OCCUPANCY MANAGEMENT REQUIREMENTS, the contractor may elect to perform a portion of the work required under this contract using the property, facilities, assets, services, or other specialized resources uniquely available on-site (“on-site resources”) from a NASA Center, Component Facility, or the Jet Propulsion Laboratory (JPL) (any one of which is a “Performing

Organization”). Such proposed requests must be within the scope of the contract and are subject to the availability of those resources and the Performing Organization’s ability and willingness to provide them. The contractor shall limit requests for the use of on-site resources to only those

Performing Organization facilities, services, or other resources that are unique or not otherwise reasonably available commercially. The contractor shall document its planned use of on-site resources through the execution and submission with proposal of one or more Government Task

Agreements (GTAs). During contract performance, the parties may agree to execute additional

GTAs if they mutually determine such agreements are necessary to respond to new or changed circumstances that arise during performance. The contractor is responsible for the cost of any

GTA. During contract performance, the contractor shall formally request GTAs in writing to the

COR identifying the tasks to be performed, facilities required, and the start and end dates for the task agreement. The contractor is responsible for the cost of all GTAs added anew during contract performance (i.e., the GTA was not included in the contract proposal). These on-site resources are provided subject to the specific contract clauses indicated in Table 4.1.

In accordance with FAR 52.245-1(h)(1), the contractor shall be liable for property lost, damaged, destroyed or stolen by the contractor or their employees, contractors, or subcontractors when determined responsible by a NASA Property Survey Board. The official accountable recordkeeping, financial control, and reporting of the property subject to this clause shall be retained by the Government and accomplished within NASA management information systems prescribed by the installation Supply and Equipment Management Officer (SEMO) and Financial

Management Officer.

Contractor use of Government property provided to the contractor under a GTA for use at an off-site location requires advance approval of the CO and notification of the Industrial Property

Officer (IPO).

G-1-19

The contractor shall not bring to the installation for use under this contract any property owned or leased by the contractor, or other property that the contractor is accountable for under any other Government contract, without the CO’s prior written approval.

The contractor shall be responsible for any loss of or damage to Government property because of the contractor’s actions while operating pursuant to a GTA. In accordance with 52.245-1 paragraph (d)(2)(iii), all Government resources used by the contractor while operating pursuant to a GTA are provided “as-is.”

4.6.4 Collaboration

In accordance with contract H clause USE OF GOVERNMENT RESOURCES, the contractor may elect to use the NASA personnel that NASA is making available for use during the performance of this contract. During contract performance, the contractor shall document its collaboration requests in writing to the CO or COR. The contractor shall request specific areas of technical subject matter expertise (e.g., engineering, operations, safety) and the duration and amount of the requested resources, but the contractor shall not request specific Equivalent

Personnel (EPs) by name or title. NASA has the sole authority to determine whether it will provide any portion of the collaboration resources requested by the contractor. During contract performance, NASA reserves the right to unilaterally change its approach to collaboration at any time, including the right to modify the specific EPs offered to the contractor and the amount, type, and/or duration of their support, and including the right to cease collaboration at any time.

At all times during collaboration, the EPs remain employed by, and under the supervisory control of NASA or the NASA support contractor, as appropriate. While collaborative communication between the contractor and provided EPs is expected in furtherance of the EPs’ advisory roles, the contractor shall not direct or supervise the work of EPs. NASA will use reasonable efforts to ensure equitable resources are provided to all HLS contractors, if there is more than one contractor, in support of their respective collaboration approaches but makes no guarantees that identical resources will be provided. Specific resources will be narrowly tailored to a contractor’s unique development approach and associated needs and objectives.

4.6.5 Government-Furnished Information

Government-Furnished information (GFI), such as technical data packages, will be furnished to the contractor for performance of the contract and will not be returned to the Government.

During contract performance, the contractor should inquire at NASA Centers to determine the availability and cost of these items and execute an Optional GFP Agreement (OGFPA) to document the agreement between NASA and the contractor about the provision of GFI. This request should be made in writing to the COR.

4.7 Cybersecurity and Project Protection

The following definitions apply to Section 4.7:

• Covered Contractor Systems means any IT system, OT system, or Mission System that is owned, or operated by or for, the contractor, its subcontractors, or its suppliers; that processes, stores, accesses, or transmits any data and information; as part of the performance of this contract.

G-1-20

• Information Technology (IT) system means: any services, equipment, or interconnected system(s) or subsystem(s) of equipment; either contractor-owned or to which NASA may or will take legal title in accordance with this contract; that are used by the contractor, in the performance of this contract, for the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data and information. An IT system may include computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including cloud computing and help-desk services or other professional services which support any aspect of the life cycle of the equipment or service), and related resources.

• Operational Technology (OT) system means hardware and software that is physically part of, dedicated to, or essential in real time to the performance, monitoring, or control of physical devices and processes. This includes but is not limited to a mission control system or center.

4.7.1 Contractor Use of NASA Systems

For the purposes of effectuating collaboration, GTAs, or similar contractual mechanisms, NASA may grant access to one or more systems that are owned, operated by, or operated on behalf of

NASA (e.g., an internal NASA network at a NASA Center). To the extent that NASA has facility-specific security requirements that apply to these scenarios, before being granted such access, the contractor shall comply with such requirements specified by the applicable NASA

Center and/or facility. At a minimum, all contractor personnel requiring physical or logical access to any such NASA system at any NASA Center and/or facility shall complete NASA’s IT

Security Awareness training prior to being granted physical or logical access and shall repeat this training annually thereafter if the personnel continue to require such access.

4.7.2 Cybersecurity for Covered Contractor Systems

4.7.2.1 System Security Plan (SSP)

In accordance with contract clause NFS 1852.204-76 SECURITY REQUIREMENTS FOR

UNCLASSIFIED INFORMATION TECHNOLOGY RESOURCES and DRD 1780MA-011, the contractor shall deliver a System Security Plan (SSP) to describe its approach to cybersecurity for all Covered Contractor Systems, to ensure that cybersecurity is not only engineered into the design of all Covered Contractor Systems but that cyber compliance is also addressed throughout the lifecycle of Covered Contractor Systems in accordance with applicable Federal laws and

NASA policy.

4.7.2.2 Third Party Audit

To assure NASA that the contractor has achieved the required level of cybersecurity, the contractor shall have a third-party, independent cybersecurity assessment performed on all of its covered contractor systems (including those of its subcontractors) at least once during contract performance, as follows: (1) At any point during contract performance, so long as the audit

G-1-21 occurs after all of the contractor’s covered contractor systems are either operational or otherwise sufficiently mature to undergo a meaningful audit, but No Later Than (NLT) 120 calendar days before the commencement of HLS Flight Operations (as defined in Section 5.10 of this SOW);

and (2) NASA may direct the contractor to get a second audit if, prior to the commencement of

HLS Flight Operations, but after the first audit occurs, the contractor makes, in NASA’s assessment, material changes to its HLS hardware or software. Following the completion of any such audit, the contractor shall provide an audit report authored by the third-party auditor to

NASA as soon as reasonably practicable.

The contractor shall ensure that its proposed timing of the initial third-party audit is clearly reflected in other HLS contract documents as is appropriate, such as but not limited to the contractor’s Integrated Master Schedule (IMS) DRD 1780MA-003.

4.7.2.3 NASA Inspection

In accordance with paragraph (d) of contract clause NFS 1852.204-76, upon request of the

Government, the contractor shall facilitate timely Government access to the contractor’s and subcontractors’ facilities, installations, operations, documentation, databases, and personnel used in performance of the contract to the extent required to carry out a program of Information

Technology (IT) inspection. This inspection may include actions such as vulnerability testing, investigation, and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of NASA Electronic Information or to the function of IT systems operated on behalf of NASA or may be for the purpose of preserving evidence of computer crime. The

Government may use a covered Government support contractor to perform this inspection in whole or in part but will notify the contractor ahead of time if it plans to do so and will ensure that the appropriate measures are put in place to ensure protection of the contractor’s proprietary data that may be accessed during this inspection.

4.7.3 Information Technology Security Management Plan

In accordance with contract clause NFS 1852.204-76 and DRD 1780MA-009, the contractor shall prepare and deliver an Information Technology Security Management Plan (ITSMP).

4.7.4 Project Protection Plan

In accordance with DRD 1780MA-010, the contractor shall prepare and deliver a Project

Protection Plan (PPP).

4.8 Security Clearances

As soon as practicable after contract ATP, the contractor shall have the ability to access Top

Secret/Sensitive Compartmented Information (TS/SCI) information in support of cybersecurity, project protection, and mission execution efforts.

4.9 Organizational Conflict of Interest (OCI) Plan

The contractor shall prepare and deliver an Organizational Conflict of Interest (OCI) Plan in accordance with DRD 1780MA-007.

G-1-22

4.10 Diversity, Equity, Inclusion, and Accessibility Plan

The contractor shall prepare and deliver a Diversity, Equity, Inclusion, and Accessibility (DEIA)

Plan in accordance with DRD 1780MA-012.

4.11 Changes, Waivers, and Deviations to Technical Requirements

The contractor shall prepare and deliver requests to change, waive, or deviate from HLS technical requirements to the COR, who will ensure that the request is entered in the HLS

Change Management System. The requests shall be developed in accordance with HLS-PLAN-

004, Human Landing System (HLS) Configuration and Data Management Plan.

4.12 Programmatic Deliveries and Reviews

4.12.1 Integrated Master Schedule (IMS) and Schedule Risk Assessment (SRA)

The contractor shall prepare and maintain an Integrated Master Schedule (IMS) in accordance with DRD 1780MA-003 that contains the logically networked tasks and milestones by Work

Breakdown Structure (WBS) throughout the DDT&E phase of the contract. In addition to the design, development, manufacture, and test of the Integrated Lander and HDL, the IMS shall include any launch vehicle design modifications, ground systems modifications, design reviews, launch integration reviews and launch readiness reviews.

As defined in DRD 1780MA-003, the contractor shall prepare and deliver a probabilistic

Schedule Risk Assessment (SRA) report to be presented at Government-Mandated Milestone

Reviews, at a minimum, and as directed by NASA per the IMS.

4.12.2 Risk Management

4.12.2.1 Risk Management Plan

The contractor shall implement a risk management process throughout the entire contract lifecycle that is documented in a configuration-controlled HLS Risk Management Plan. The HLS

Risk Management process should identify, analyze, plan, track, and control risks associated with the design, development, fabrication, test, certification, and operation of the HLS beginning with contract award.

Risk management is a continuous process and shall be implemented throughout the life cycle of the contract. The Risk Management Plan shall provide specific information on how the contractor will implement the risk management requirements of NPR 7120.5, NASA Space Flight

Program and Project Management Requirements and NPR 7120.7, NASA Information

Technology Program and Project Management Requirements, by using the risk management procedures specified in NPR 8000.4, Agency Risk Management Procedural Requirements. The contractor shall further describe how risk items will be documented and communicated to the

Government. The approach shall be compatible with the program/project/mission support office’s Risk Management Plan and shall comply with the program/project/mission support organization Work Breakdown Structure (WBS). In addition, lessons learned submittals and search results, risk lists, risk analyses, and risk tracking reports shall be provided throughout the life cycle of the program/project/mission support organization. The contractor shall define risk

G-1-23 management and reporting in accordance with DRDs 1780MA-004, Risk Management Plan and

1780MA-005, Risk Reports.

4.12.2.2 Risk Reports

The contractor shall provide a configuration-controlled risk report that is captured and managed throughout the Integrated Lander and HDL lifecycle that indicates which safety, technical, and schedule risks present threats to mission success, major tests, and certification. This risk report shall identify the appropriate risk approach for handling the risks in accordance with DRD

1780MA-005 and shall be monitored regularly through insight. In accordance with DRD

1780MA-005, the contractor shall submit risk reports monthly throughout performance of the contract. On an annual basis, the contractor shall provide NASA a re-evaluation of each accepted risk as part of the 1780MA-005 delivery.

4.12.3 Program Management Reviews

The contractor shall conduct monthly Program Management Review (PMR) meetings with

NASA at mutually agreed upon locations, which could be virtual, and shall include the submission of review packages. The contractor shall present the following program status, at a minimum:

• IMS and Technical Status, including schedule trends and significant schedule variances

• Risk Management, where the contractor shall provide a risk status indicating which safety, technical, and schedule risks present threats to mission success and certification. The contractor shall include a current detailed explanation of how risks are being addressed along with technical progress status, trends from the prior PMR, accepted or closed risks, and any schedule/resource challenges.

• Current Issues and the strategy for resolution and emerging risks shall be identified, along with supporting detail. Qualitative Risk Assessments (QRAs), Corrective Action Plans, software IV&V findings, and program impacts shall be addressed.

•…