80JSC027R0004 Attachment J-01_CLDC Final SOW.pdf

80JSC027R0004

Commercial Low Earth Orbit (LEO) Destination Contract (CLDC)

Attachment J-01 | Statement of Work (SOW)

ATTACHMENT J-01 STATEMENT OF WORK

National Aeronautics and Space Administration Johnson Space Center

REVISION AND HISTORY

REV DESCRIPTION PUB. DATE

Basic Attachment J-01 (Draft SOW) 07/06/2026

Basic Attachment J-01 (Final SOW) 09/25/2026

TABLE OF CONTENT

REVISION AND HISTORY

TABLE OF CONTENT

STATEMENT OF WORK (SOW)

1.0 INTRODUCTION

1.1 Background

1.2 Scope

1.3 CLDS Requirements and Standards

1.4 Description of Commercial LEO Destination System (CLDS)

1.5 NASA Utilization Capability Needs in LEO

1.6 NASA Usage of Utilization Capabilities

1.7 Increment Definition

1.7.1 Crew Tended Mission

1.7.2 Continuous Crew Mission

1.8 Definitions of Crewmembers

1.8.1 Crewmember Specific Roles

1.9 Payload Specific Roles

1.9.1 Principal Investigator

1.9.2 Payload Developer

1.9.3 Deployable Pressurized Powered Payloads

1.10 Shall, Should, Will Definitions

2.0 CLDC GENERAL REQUIREMENTS

2.1 Program Management

2.1.1 Quarterly Program Review (QPR)

2.2 Milestone Review Process

2.3 Government Insight

2.4 Schedule Management

2.5 Risk Management

2.6 Export Control

2.7 Information Technology (IT)

2.8 Configuration Management

2.9 Reserved

2.10 Systems Engineering and Integration (SE&I)

2.11 Safety and Mission Assurance

2.11.1 Hazard Analysis and System Safety

2.11.2 Software Safety & Assurance

2.11.3 Quality Assurance

2.11.4 Reliability

2.11.5 Orbital Debris, Jettisons, and Deorbit

2.11.6 Mishap Preparedness and Contingency Action Plans

2.11.7 Safety and Health

2.11.8 Integrated Maintenance and Logistics Support

2.12 NASA Access to Partner Facilities and Tools

2.13 Certification

2.14 Mission Integration

2.14.1 Imagery

2.15 Utilization

2.15.1 Payload Users Guide

2.15.2 Utilization Integration Plan

2.15.3 USG Payload and Payload Facility Interface Requirements and Testing

2.15.4 USG Payload and Payload Facility Software and Commands/Telemetry ... 32

2.15.5 USG Payload or Payload Facility Integration and De-Integration

2.15.6 USG Payload or Payload Facility Delay

2.16 Mission Operations

2.16.1 Mission Design and Analysis

2.16.2 Operations Procedures

2.16.3 Timelines

2.16.4 Flight Rules

2.16.5 Operations, Flight and Ground Training

2.16.6 Rules of Operation

2.16.7 Anomaly Resolution

2.16.8 Console Tools

2.16.9 Mission Systems

2.17 Transportation

2.17.1 Transportation Certification

2.17.2 Transportation Mission Integration Services

2.17.3 Government Furnished Transportation and Support Services (GFTSS)

2.17.4 Transportation and Destination Sensitive Data Handling

2.17.5 Launch Vehicle Maturity

2.17.6 Crew Launch & Return

2.17.7 Transportation Redundancy

2.17.8 NASA Provided USG Crew Services

2.18 Human Health, Medical and Performance

2.18.1 Human System Integration

2.18.2 Human-in-the-Loop (HITL) Testing

2.18.3 Human Error Analysis

2.18.4 Medical Operations

2.18.5 Health Stabilization Program

2.18.6 Acoustic Noise Control

2.18.7 Food and Nutrition

2.19 Government Furnished Resources, Property and Services

2.19.1 Use of Government Resources

2.19.2 Government-Furnished Property (GFP) Integration

2.19.3 Government-Furnished Information

2.19.4 USG Furnished Crew Time

2.20 Crew Selection and Mission Evaluation

2.20.1 Minimum Standards

2.20.2 Crew Commander

2.20.3 Mission Medical and Behavioral Health Certification

2.21 Crew Code of Conduct (CCoC)

2.21.1 Authority and Responsibilities of the Commander

2.22 Commercial Activity Coordination

2.23 Communications and Public Affairs

3.0 CLIN STRUCTURE AND DESCRIPTION

3.1 Initial Development (CLIN 1)

3.2 CLDS Development & Certification (CLIN 2)

3.3 Mission Services (CLIN 3)

3.4 Pre-Priced Additional Service (CLIN 4)

3.5 Special Tasks and Studies (CLIN 5)

STATEMENT OF WORK (SOW)

1.0 Introduction

NASA’s strategic goal is to have commercial low-Earth orbit destinations to ensure the continuous presence of United States Government (USG) crew to advance human space exploration, scientific discoveries, and United States economic competitiveness and commercial participation in low-Earth before ISS decommissioning and deorbit at the end of calendar year 2030. To accomplish this strategic goal, NASA is seeking to award multiple Phase 2 FAR-based contracts to one or more U.S. Commercial LEO Destination System contractors for the design, development, manufacture, test, launch, deployment, activation and checkout, and certification of the Commercial LEO Destination System (CLDS) to purchase end-to-end services.

1.1 Background

In 2019, NASA established the Commercial Low Earth Orbit (LEO) Development Program (CLDP) Office at the NASA/Johnson Space Center (JSC) to lead the U.S. commercialization of LEO and to stimulate private sector’s investment in LEO by (a) offering Private Astronaut Missions (PAMs) to/from the International Space Station (ISS) and (b) pursuing multiple commercial LEO destination Phase 1 development agreements. These Phase 1 commercial LEO destination agreements range in scope from the Commercial Destination – International Space Station (CDISS) contract to the Commercial Destination – Free Flyer (CDFF) funded Space Act Agreements (SAA) followed by Collaborations for Commercial Space Capabilities (CCSC-2) unfunded Space Act Agreements (SAAs); all focused on developing United States (U.S.)

Commercial LEO Destination System capabilities that could eventually lead to the availability of U.S. commercially offered end-to-end CLDS services for both commercial and Government customers. The Phase 1 initiatives focused on early maturation of designs for each Phase 1 partner’s CLDS. This effort is a collaboration with U.S. commercial industry partners, International Space Station Program (ISSP) and the Commercial Crew Program (CCP). In June 2026, NASA established the LEO Program Office at the NASA Johnson Space Center (JSC) encompassing the scope previously under the CLDP, CCP and ISSP consolidating the responsibility for all LEO activities including development of future Commercial LEO Destinations and developing the LEO economy.

1.2 Scope

This Statement of Work (SOW) identifies the requirements for the work needed to design, develop, manufacture, test, launch, deploy, demonstrate, certify and provide engineering support of the Commercial LEO Destination System (CLDS) to its intended location in low earth orbit.

In addition, this SOW defines NASA requirements, data deliverables, milestones and rules of engagement for the operational phase of the CLDS where NASA is purchasing CLDS services including crew and cargo transportation.

The CLDS shall support at least a total crew of four (4), including at least two (2) USG Crew for Standard Service Missions. To open the design trade space and encourage innovations and efficiencies in system design solutions, NASA is not dictating a specific destination system architecture and design. Each Contractor must determine the applicable destination system requirements that best serve their target markets and that meet NASA’s utilization needs in LEO as defined in SOW Section 1.5 NASA Utilization Capability Needs in LEO. CLDS Contractors can provide an initial minimum capability consistent with Mission A Capabilities (NASA Category 1 Utilization Needs) with an assembly plan to show how they will meet capabilities consistent with NASA Category 2 Utilization Needs and NASA Category 3 Utilization Needs.

1.3 CLDS Requirements and Standards

Attachment J-03 defines the CLDS Requirements, Standards and Plans the Contractor shall utilize for the performance of this contract.

1.4 Description of Commercial LEO Destination System (CLDS)

The Commercial LEO Destination System (CLDS), as shown in Figure 1.4-1, is the sum of all systems, facilities, and activities required to build, launch, maintain, and operate a human occupied on-orbit station. The CLDS consists of the Crew Transportation System (CTS), Commercial LEO Destination (CLD), and Cargo Transportation System (CaTS). Each of these systems consists of a Ground System (GS), a Mission System (MS), a spacecraft (Destination, Crew Visiting Vehicle (CVV), Cargo Visiting Vehicle (CaVV)), and launch vehicle. While a spacecraft is mated to its launch vehicle, this configuration is defined as the Integrated Stack

(IS).

FIGURE 1.4-1 CLDS COMPONENTS

1.5 NASA Utilization Capability Needs in LEO

NASA’s minimum utilization capabilities requirements and associated quantities are included in Table 1.5-1. Each line item in Table 1.5-1 is intended to be a separate unique service (unless delineated or noted). CLDP-REQ-1130 Requirements and Standards for the CLDP also includes requirements such as, but is not limited to, power, thermal cooling, conditioned stowage, and data to support payload operations.

NASA’s minimum capability requirements are grouped into three (3) categories. Categories 1, 2, and 3 based on NASA’s priorities and desired order of CLDS implementation.

• Category 1 represents NASA’s minimum needs for a 1-month Crew Tended mission capability.

• Category 2 represents NASA’s minimum needs for a 6-month Continuous Crew mission capability.

• Category 3 represents NASA’s minimum needs for a 6-month Standard Service mission capability.

Table 1.5-1 NASA Minimum Capability Requirements

NASA Utilization Capabilities Item Category 1 Category 2 Category 3

DESTINATION CAPABILITIES

Total # of Reconfigurable Locker Locations (MLE) 1

3 20 58

• Heritage or non-Heritage Locker Style Payloads (MLE)

3 12 34

• Minimum # of Rack Equivalent Volume5

0 1 (8 MLE

each)

3 (8 MLE

each)

Deployable Pressurized Powered Payloads

4 8 12

Cargo Transfer Bag Equivalent (CTBE) Stowage

20 45 150

# of locations for Vacuum Resource Access2

0 2 2

# of locations for Vacuum Exhaust Access2

0 3 3

# of locations for gaseous O2 Access2 0 2 2 # of locations for gaseous N2 Access2

(CLDP-STD-1106 Section 3) 0 2 2

Potable/Conditioned Water Access6 Yes Yes Yes On-Orbit Conditioned Stowage (in Liters (L))3 (Total Combined)

20 60 150

• Frozen 20 50 100

• Refrigerated 0 10 50

Workbench (CLDP-STD-1106 Section 3)

0 1 1

Glovebox (CLDP-STD-1106 Section 3)

0 1 1

NASA Utilization Capabilities Item Category 1 Category 2 Category 3

TRANSPORTATION LAUNCH

CAPABILITY 7

Pressurized Delivery - Cargo Transfer Bag Equivalent (CTBE)

14 35 100

Powered Locker Locations4 1 3 4 Conditioned Stowage - Liters 3 (Total Combined)

10 30 70

• Frozen (up to) 10 10 20

• Refrigerated (up to) 5 20 40

• Incubated (up to) 0 5 10

TRANSPORTATION RETURN

CAPABILITY 7

Pressurized Trash Disposal - Cargo Transfer Bag Equivalent (CTBE)

7 18 50

Pressurized Return - Cargo Transfer Bag Equivalent (CTBE)

7 17 50

Powered Locker Locations4 1 3 4 Conditioned Stowage - Liters 3 (Total Combined)

10 30 70

• Frozen (up to) 10 30 60

• Refrigerated (up to) 5 10 20

• Incubated (up to) 0 5 15

References to the CLDP Utilization Standard, CLDP-STD-1106, CLDP Utilization Capabilities Standard provide more detail regarding each of the utilization capabilities.

Notes:

1. The CLDP-STD-1102, CLDP Payload Interface Standard (CPIS) for Heritage Hardware, provides interface requirements for NASA heritage lockers to ensure compatibility with commercial destinations (and transportation vehicles). For Category 1, two (out of three) lockers shall be compatible with NASA heritage lockers. For Category 2, sixteen (out of twenty) shall be compatible with NASA heritage lockers. For Category 3, forty (out of fifty-eight) shall be compatible with NASA heritage lockers.

2. The number of vacuum resources, vacuum exhaust and gaseous nitrogen supply do not include those resources needed by the Glovebox as detailed in CLDP-STD-1106, CLDP Utilization Capabilities Standard. At least one of the vacuum exhaust, gaseous nitrogen, and gaseous oxygen resources shall be co-located in one payload or payload facility rack or CLD location.

3. The intention is that the CLD Provider’s designs are able to meet the total conditioned stowage needs, along with each individual maximum value as provided in the table on a per Increment basis. Frozen, refrigerated, and incubated samples will be managed to not exceed the total requirement per Increment. The Increment baseline will be determined by NASA through the Request for Task Order Proposal (RFTOP). NASA shall be given first right of refusal for any excess conditioned stowage capacity in conditioned stowage assets, to be negotiated through the Request for Task Order Proposal (RFTOP).

4. Powered locker locations (along with required power) are to be provided to NASA in addition to any powered locker locations that are utilized to meet NASA’s conditioned stowage requirements. NASA shall be given first right of refusal for any excess powered locker locations, to be negotiated through the RFTOP.

5. Rack Equivalent Volume equates to four (4) vertical MLE x two (2) horizontal MLE in a contiguous configuration.

6. NASA needs access to onboard water for payloads. This capability could come in many different forms, such as direct plumbing, water bags/drink bags, or potable water dispenser. The desire is to not drive the design, but to use residual water that may be available. Should NASA need amounts that are outside of the residual CLD amounts planned for an increment, NASA can provide their own water, flown in NASA’s allocation/assets.

7. If capabilities listed in in Table 1.5-1 are not available at the quantities listed, NASA may request an equitable adjustment.

1.6 NASA Usage of Utilization Capabilities

NASA’s projected usage for the various utilization capabilities on board the CLDS are as follows and are provided on a best estimate basis.

Table 1.6-1 Utilization Capability Usage Utilization Capability USG Usage Rate (%) Workbench 50 Glovebox 100

1.7 Increment Definition

An Increment is a specific time-period which includes on-orbit utilization, logistics, maintenance, and other CLD system operations. A Crewed Increment begins upon arrival of a Crew to an uncrewed Destination or the day after any crewed vehicle undocks. An increment ends at undocking from the Destination.

1.7.1 Crew Tended Mission

A crew tended mission refers to a mission or destination that is visited intermittently by a crew for a minimum of 1 month rather than being continuously inhabited. The crew arrives, performs operations, maintenance, or utilization activities, and then departs—leaving the destination uncrewed between visits.

1.7.2 Continuous Crew Mission

A continuously crewed mission refers to the Destination that is continuously occupied by USG Crew with no more than a 14 day lapse in Crew presence between crew handovers. Continuous crew capability requires regular crew rotations and resupply so that a continuous human presence is maintained in space.

1.8 Definitions of Crewmembers

Table 1.8-1 defines the types of CLDS Crewmembers that will be selected, trained, and approved to fly in accordance with SOW Section 2.20 Crew Selection and Mission Evaluation.

TABLE 1.8-1 CREWMEMBER DEFINITIONS

Crew Any human on board the space system during the mission that has been trained to monitor, operate, and control parts of, or the whole space system; same as flight crew or crewmember. In some instances, the use of the word Crew can also include Passengers in the context of the entire crew complement.

U.S. Government (USG) Crew

Members of NASA's Astronaut Corps; other US Government personnel; or other NASA-sponsored Crew by NASA for a mission to a Destination.

Non-USG Crew Personnel who are not USG Crew. Can include Passengers, retired USG astronauts working for CLD providers, and Sovereign Astronauts not sponsored by USG

Passenger Any human on board the space system while in flight that has little to no responsibility to perform any mission task for that system. Often qualify as "Space Flight Participants," as defined in 14 C.F.R. § 401.7.

Sovereign Astronauts

An individual, who is acting in their official capacity, has been qualified as an astronaut by their space agency, and is employed as a member of the astronaut corps of the agency

1.8.1 Crewmember Specific Roles

Each Crewmember in Table 1.8-1, Crewmember Definitions will be assigned a role for the mission based on experience and planned activities on-board.

1.8.1.1 Crew Commander

The roles and responsibilities of the Commander are noted in Clause H.23 Authority and Responsibilities of the Destination and Crew Visiting Vehicle (CVV) Commander, Chain-of- Command and Succession On-Orbit; Relationship Between Ground and On-Orbit Management.

In addition to these roles and responsibilities, an awareness and capability to perform the following is part of the role of the Commander.

• Adherence to and a thorough knowledge of the Crew Code of Conduct (CCoC), as defined in SOW Section 2.21 Crew Code of Conduct.

• Responsibility for the safety of the occupants of the Destination and CVV.

• Acknowledgement of final authority to initiate any immediate action deemed necessary for Crew safety.

• Able to assess Crew readiness to execute the mission plan, safety procedures, and emergency responses.

• Capable of delineating their responsibilities and authority as the Commander during emergencies. Note: It is imperative for training to outline specific scenarios demonstrating authority beyond standard Crew safety.

• Proficient in their Commander (CDR) role in response to emergencies and other major failures. Ideally with full Crew so they can consider assigning roles and responsibilities across the Crew.

• Able to safely undock the Crew vehicle without assistance from the ground.

• Understand their authority as the CDR and their role in the chain of command in relationship to the other Crewmembers, USG and non-USG, and the ground Flight Control Team (FCT), Contractor and NASA.

• Able to lead the Crew of the Destination and CVV in major recovery operations assuming a loss of communications with the ground. To include recovering communications, power, and other time critical system failures.

1.8.1.2 Mission Specialist

The role of the Mission Specialist (MS) is that of a Crew member who may perform all daily mission tasks and activities aboard the vehicle and will maintain the vehicle as part of their regular duties as custodian. This person will be an active part of the daily operations, potentially including utilization activities, be fit for daily life on orbit and meet the minimum standards as defined in SOW Section 2.20 Crew Selection and Mission Evaluation. Additional responsibilities may be assigned based on mission specific roles or functions as defined by the Contractor.

1.8.1.3 Passenger

This role, if used, will likely be limited in its participation in on-board activities and would expect to have no decision-making authority during contingency or emergency response. It would be expected that this person(s) would be directed to return to the safe-haven (as specified in CLDP-REQ-1130, Requirement and Standards for the Commercial Low-Earth Orbit

Development Program) and wait until released if an emergency was annunciated. This role would be expected to be one where minimal training was provided and only specifically trained events were planned for the individual. To that end, this person should meet the minimum standards as defined in SOW Section 2.20 Crew Selection and Mission Evaluation. No additional requirements would be required beyond those levied by the Contractor.

1.9 Payload Specific Roles

1.9.1 Principal Investigator

The Principal Investigator (PI) is the person or team responsible for leading the objectives and rationale for a specific utilization activity to be performed onboard the CLDS to accomplish the research sponsor’s goals and objectives.

1.9.2 Payload Developer

The Payload Developer (PD) is an individual or team responsible for designing, building, testing, and deploying scientific instruments, equipment, or other items throughout the payload lifecycle that will be used on the CLDS to achieve specific research sponsor's mission objectives. They work closely with NASA, Contractor(s) and Principal Investigators (PIs) to ensure that payloads meet CLD requirements and that utilization is successfully conducted on-orbit. Additional details related to NASA’s expectations of the Payload Developer can be found in CLDP-PLN- 3017 Utilization Integration Plan.

1.9.3 Deployable Pressurized Powered Payloads

Deployable pressurized powered payloads are internal cabin (pressurized) payloads that do not have to be of the locker form factor and are able to be soft-stowed for transport. Examples include but are not limited to handheld, mounted to a multi-use bracket, or temporarily attached to a workbench or a wall.

1.10 Shall, Should, Will Definitions

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

• Shall –Denotes the imperative.

• Should –Expected course of action or policy that is to be followed unless inappropriate for a particular circumstance.

• Will – To indicate an anticipated future action, event, or result.

• Must – See “shall” per FAR 2.101

2.0 CLDC General Requirements

This Statement of Work (SOW) provides the scope of the work with associated tasks required to manage and lead the CLDS contract performance and work statements.

The Contractor shall design, develop, test, evaluate and certify the CLDS in accordance with the requirements and standards as specified in SOW Section 1.3 CLDS Requirements and Standards and flow down applicable requirements to all subcontractors, vendors, and teaming partners who are performing or supporting contract requirements and deliverables.

The Contractor shall provide the capability to safely support USG Crew continuously and provide end-to-end services, including but not limited to, transportation, habitability, training, operations, utilization, and medical operations. The Contractor shall retain the primary responsibility for meeting and delivering all contract requirements regardless of their subcontract or operational arrangements.

The Contractor shall define and publish the units of measure in all engineering documentation to ensure the proper communication of English or metric units are identified. This will ensure that all communications adhere to the International System of Units (SI) or English standard.

The Contractor shall utilize the English language in all communications both written and spoken including all documents produced by the Contractor, the subcontractors, vendors and teaming partners to fulfill contract deliverables, CLDS Operational products, contract documentation, task orders, and pricing. If Insight data is required that is not in English, the Contractor shall provide English translations, at NASA request.

The Contractor shall obtain and maintain National Security Facility Clearance Level (FCL) per Clause I.12 NFS 1852.240-75 Security Classification Requirements (SEP 2025) (DEVIATION) up to TOP SECRET and as identified in the Task Order requirements, provide SECRET/TOP SECRET security clearances for a limited number of personnel that may need to support functions identified by NASA requiring this level of clearance in accordance with Attachment J- 18 Contract Security Classification Specification (DD254).

NASA is not requiring the Contractor to maintain a Sensitive Compartmented Information Facility (SCIF) but shall have the capability to support conversations over secure communication channels. The Government does not anticipate to need to use S/TS clearance until CLIN 3 at which time the Contractor will have to possess a current National Security Facility Clearance Level (FCL) up to TOP SECRET in order to work on CLIN 3.

2.1 Program Management

The Contractor shall develop, implement, maintain, and operate the CLDS in compliance with DRD CLDC-015 Program Management Plan, as applicable to the Contractor’s program.

The Contractor shall meet all applicable local, national, and international laws and regulations during contract performance.

The Contractor shall be responsible for obtaining and maintaining all applicable licenses, permits and agreements required to deliver the CLDS orbital elements to orbit, perform the end-to-end services, and safely deorbit.

The Contractor shall develop, deliver, and implement the Contractor’s Organizational Conflicts of Interest (OCI) Plan (Attachment J-07) in accordance with DRD CLDC-003 Organizational Conflicts of Interest (OCI) Plan.

The Contractor shall develop, deliver, and implement the Contractor’s Commercialization Plan in accordance with DRD CLDC-002 Commercialization Plan.

The Contractor shall develop, implement, maintain, and operate the CLDS in accordance with DRD CLDC-007 Environmental Compliance Reports and Clause H.38 JSC 52.223-94 JSC Environmental Compliance (FEB 2025), if the contractor is performing work at Johnson Space Center under this contract.

The Contractor shall develop, deliver, implement the Small Business Subcontracting Plan and deliver required reports in accordance with DRD CLDC-008 Small Business Subcontracting Plan and Reports.

The Contractor shall maintain all records created for Government use or created in the course of performing the contract and/or delivered to, or under the legal control of the Government and must be managed in accordance with Federal law, including but not limited to, the Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, as well as NASA records policies (NPD 1440.6, NASA Records Management Program, and NPR 1441.1, NASA Records Management Program Requirements).

The Contractor shall ensure that NASA-owned/Contractor-held records are segregated from contractor-owned records and from non-record materials and report holdings of NASA records.

The Contractor shall immediately notify the Contracting Officer and NASA Records Officer upon discovery of any inadvertent or unauthorized removal, defacing, alteration, or destruction of Federal records. Destruction of Federal Records is EXPRESSLY PROHIBITED unless in accordance with records retention schedules or as directed by the Contracting Officer.

All Contractor employees assigned to this contract who create, work with, or otherwise handle Federal Records are required to complete mandatory NASA- provided records management training. The Contractor shall ensure that training has been completed according to agency policies, including initial training and any required annual or refresher training.

The Contractor shall incorporate the substance of this requirement in all subcontracts under which the subcontractor will create, work with, or otherwise handle Federal Records under this contract, and require written subcontractor acknowledgment of same.

2.1.1 Quarterly Program Review (QPR)

The Contractor shall provide quarterly briefing packages, no later than one month following the designated quarter in review and provide the data specified below no later than two calendar days prior to the meeting. NASA will protect financial data submitted in accordance with the Contractors’ markings, will not distribute publicly, and will limit distribution to need-to-know personnel only.

The Contractor shall also brief updates to DRD CLDC-002 Commercialization Plan quarterly to NASA Program Management. This review can be combined with the QPR or conducted separately.

The quarterly briefing package should include the following contents with details negotiated post-award.

Quarterly Program Review (QPR) Data Contents:

1. Programmatic

a. Provide cost/schedule/technical status against the contract baseline, including milestone payment forecast with explanations and risks.

b. Updates to Key Personnel and Facilities from Clause H.41 NFS 1852.235-71 Essential Personnel and Facilities (AUG 2025) (DEVIATION) and current organization chart.

c. Change Management including list of changes that impact Government requirements or CLDS Certification that were dispositioned over the past quarter and changes currently under evaluation.

d. DRD Submission Status, including summary level of the changes since last QPR.

e. Status of insight team coordination, including new opportunities.

f. Status of Government Task Agreements / Government Collaboration

Agreements (GTAs/GCAs) including overview of any new interfaces, tools, and processes used for establishing effective and efficient insight and collaboration.

g. CLIN 5 Special Tasks and Studies status including overview of work completed since previous QPR and upcoming quarter.

h. Contracts and Agreements status, including progress and future plans for contracts and agreements with subcontractors, vendors, suppliers, and partners with a value over $100M or is supporting scope that is in the critical path. Status shall include a high-level cash flow analysis and future forecast to support adequate funding of subcontractors, vendors, suppliers and partners.

i. Status on Supplier/Sub-contractor technical performance, build quality progress/issues, production challenges, test status/issues, and delivery schedule status.

j. Action Item Closure status from previous PMRs and formal corrective actions, including their closure plan and status.

k. Special topics/other areas as identified by NASA and Contractor during QPR agenda coordination.

2. Schedule

a. Program Plan (major events)

• Show baseline plan vs actual progress, and forecast dates for all major events including Design, Development, Test and Evaluation (DDT&E).

• Show critical and secondary path to readiness for element launch(es) and subsequent offering of services.

• Include drivers of any schedule variances, schedule margin erosion, technical issues, etc. Include recovery plans and estimate closure dates.

• Major upcoming events (next 6 months) including manufacturing and testing events for critical hardware.

3. Certification

a. Summary status of trade studies, including their status, completion or due date, estimated closure date, and closure plan.

b. Status of the CLD design requirements, Verification and Validation.

(V&V) activities, and Verification Closure Notice (VCN) closures with NASA acceptance status.

• Burn down metrics and plans with prior and current period status showing trends.

• Note: Refer to OCE-52, NASA Common Leading Indicators Detailed Reference Guide for recommended trend categories.

c. Test status, including a summary of all development, qualification, acceptance, and integrated system testing schedules and results.

d. Status of Long Lead Parts for current and next quarter including planned vs actual performance of procurement, receipt and acceptance.

e. Updates to Artificial/Super Intelligence (AI/SI) technology in the development or use

4. Mission Integration

a. Mission Service Order Status and Transportation Status.

b. Updated Schedule including Performance to Plan for the increment including transportation.

c. Vehicle Status

• Facility and System status, including payload facilities, system resources, etc Technical performance related to margins, actual versus predicted margin.

• Trends on CLDS System availability and usage (NASA, Commercial, other).

• Anticipated upcoming maintenance needs (including major upgrades and or system replacements).

d. Transportation vehicles status, including mission, Interface Control Documents (ICDs), joint tests, etc.

e. Planned Safety and Capability upgrades.

5. Risk management

a. Summary risk score matrix of top risks as defined in the DRD CLDC- 116 Risk Management Plan.

b. Summary Overview of Top Risks including:

• Risk identification, title, description, potential impacts to the CLDS safety, reliability, technical, cost, or schedule performance, and U.S. Government (USG) Crew and Hardware, Likelihood, and Consequence.

• Risk mitigation plan and status.

c. List of any closed or accepted top risks since last quarter and closure rationale.

6. Safety and Mission Assurance (S&MA):

a. Status of failures, anomalies, nonconformances, waivers/deviations/non-compliances, audits & findings (including Product Assurance Action (PAA) closures and status), corrective actions, mishaps, and other relevant safety metrics;

b. Status of all Government-Industry Data Exchange Program (GIDEP) assessments since last quarter.

c. Supplier surveillance activities completed since last QPR and plans for next quarter.

7. Transportation

a. Integration status, ICD development, and verification

b. Status of joint testing (including with destination provider and with NASA)

c. Development and certification status

2.2 Milestone Review Process

The Contractor shall deliver the applicable DRDs defined in Attachment J-02 Data Requirements Description and the Milestone Review data package at least 30 calendar days in advance of the milestone review dates to allow for review time. For the Certification Baseline Review (CBR) the Contractor may deliver the data 15 calendar days ahead of the milestone review. For every day in delay of the Contractor data submission, NASA reserves the right to delay completion of the milestone a commensurate amount.

A milestone data deliverable pertains to all contract deliverables for certification and missions associated with J-11 Certification Work Plan, J-12 Mission Service Work Plan Template and any RFTOP milestones.

The Contractor shall conduct a checkpoint review 60 calendar days prior to the milestone review to finalize the Joint Implementation Plan (JIP) for each milestone (except for CBR which shall be conducted 30 calendar days prior) to include a draft agenda, list of data to be delivered to show compliance for each entrance and success criteria, logistics information, and confirmation of the availability of key stakeholders.

2.3 Government Insight

Government insight provides NASA an understanding of the Contractor’s CLDC activities and data for the design, development, testing, operation, human rating, and demonstration of their crewed destination in LEO through a collaborative working relationship, participation in the Contractor’s processes, performance of Risk Based Assessments (RBA), working panels and boards, and access to products and data to provide assistance and expertise where needed and provide awareness of developing issues for resolution prior to major milestones.

The Contractor shall develop, deliver, implement, maintain, and operate the CLDS according to an insight approach that meets the intent of CLDP-PLN-3016, Commercial Low-Earth Orbit Development Program Insight Management Plan, and in accordance with Clause H.14 Government Insight and DRD CLDC-104 Insight and Collaboration Implementation Plan.

2.4 Schedule Management

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) per DRD CLDC-001 Integrated Master Schedule (IMS) that contains the logically networked tasks and milestones beginning with contract award to the completion of the contract.

2.5 Risk Management

The Contractor shall develop, implement, deliver, maintain, and operate the CLDS in compliance with a Risk Management Plan submitted in accordance with DRD CLDC-116 Risk Management Plan.

2.6 Export Control

The Contractor shall adhere to export control laws and regulations. The Contractor shall adhere to export control requirements in accordance with NASA Procedural Requirements (NPR) 2190, NASA Export Control Program, NASA Advisory Implementing Instruction (NAII) 2190.1H, NASA Export Control Program Operations Manual in accordance with the DRD CLDC-005 Export Control Plan. The NASA policies and procedures are only applicable when the contractor uses physical and logical NASA assets or engages with NASA personnel, including support contractors.

2.7 Information Technology (IT)

The Contractor shall develop, implement, deliver, maintain, and operate within the Information Technology (IT) Security Plan(s) in accordance with Clause I.1 NFS 1852.240-76, Security Requirements for Unclassified Information Technology Resources (JAN 2026) (DEVIATION) in accordance with DRD CLDC-014 Security Requirements for Unclassified IT Resources

The Contractor shall ensure all IT products and services supporting this contract are approved through the NASA OCIO’s Commercial IT Request (CITR) Application if NASA funds are used to procure IT resources throughout the life of the contract as a direct charge to the contract. This includes, but is not limited to, Federal Information Technology Acquisition Reform Act (FITARA), Supply Chain Risk Management (SCRM), IPv6, and 508 compliance. No purchases of commercial IT products or services should be made prior to coordination and approval by the OCIO if NASA funds are used to procure IT resources throughout the life of the contract as a direct charge to the contract. Contractor shall report purchases in accordance with DRD CLDC- 013 Commercial IT Authorization Report.

The Contractor shall complete Capital Planning and Investment Control (CPIC) Reporting in accordance with DRD CLDC-012 Information Technology (IT) Capital Planning and Investment Control (CPIC).

The Contractor shall provide and comply with the Cyber Supply Chain Risk Management (C- SCRM) Plan in accordance with DRD CLDC-014 Security Requirements for Unclassified IT Resources.

NASA shall own the license(s) or subscriptions for any software or applications purchased and all hardware shall be titled to NASA if NASA funds are used to procure IT resources throughout the life of the contract as a direct charge to the contract.

The Contractor shall ensure that all products, platforms, services, and communications delivered as part of this Statement of Work that are Information and Communication Technology (ICT) or contain ICT, conform to the Revised Section 508 of the Rehabilitation Act Standards, 36 C.F.R.

§ 1194.1 & Apps. A, C & D.

2.8 Configuration Management

The Contractor shall develop, implement and maintain a configuration management approach for CLDS in compliance with Society of Automotive Engineers (SAE) Engineering Information Analysis (EIA) 649-2A Configuration Management Acquisition Requirements for Aeronautics and Space, and SAE AS9100 Quality Management System Requirements for Aviation, Space, and Defense Organizations in accordance with DRD CLDC-006 Configuration Management Plan.

2.9 Reserved

2.10 Systems Engineering and Integration (SE&I)

2.10.1 General SE&I Requirements

The Contractor shall perform the CLDC SE&I technical and management efforts of directing and controlling the integrated engineering effort for the design, development, manufacturing, integration, test, evaluation, verification, validation, certification, and sustaining of the CLDS to satisfy all requirements in accordance with the DRD CLDC-101 Systems

Engineering Management Plan (SEMP).

2.10.2 Requirement Management

The Contactor shall be responsible for developing, implementing, and maintaining a closed-loop requirements management system that ensures the CLDS requirements are traceable to the design and can be verified and validated in accordance with DRD CLDC-101 Systems Engineering Management Plan (SEMP).

Where the evaluation of NASA requirements results in non-compliance or the evaluation of usage of materials results in an elevated risk to the safety of crew, the Contractor may request relief in the form of a variance per the processes defined in CLDP-PLN-2000, Commercial Low- Earth Orbit Destination System (CLDS) Certification Plan. Variance requests to NASA requirements and requests for non-compliance with safety requirements require NASA approval.

2.10.3 Software Management

The Contractor shall develop, manage, implement, test, integrate and maintain, and operate CLDS software throughout the life cycle of the contract in accordance with DRD CLDC-107 Software Management Plan (SMP).

2.10.4 Integrated Performance Analysis and Integrated Test Plan (IPAITP)

If applicable, the Contractor shall conduct multi-element integration and testing for each major configuration change to ensure the successful on-orbit integration with existing and planned CLDS elements in accordance with DRD CLDC-105 Integrated Performance Analysis and Integrated Test Plan (IPAITP). If multi-element integrated testing is not possible, the Contractor should document in DRD CLDC-102 Verification, Validation and Certification Plan (VVCP) how the intent of a multi-element verification and validation is accomplished.

2.10.5 Verification and Validation (V&V)

The Contractor shall develop, implement, deliver, and maintain verification and validation of the CLDS requirements in accordance with DRD CLDC-102 Verification, Validation, and Certification Plan (VVCP).

The Contractor shall deliver to NASA Verification Closure Notices (VCNs) for CLDS requirements in accordance with DRD CLDC-106 Verification Closure Notice (VCN). The Contractor will consider a VCN closed only after NASA approval.

The Contractor shall provide data and support for NASA-conducted Independent Verification and Validation (IV&V), as needed, in compliance with Clause H.14 Government Insight and approval in accordance with DRD CLDC-104 Insight and Collaboration Implementation Plan.

2.10.6 Adjudication of Standards

The Contractor shall develop, implement, maintain, and operate in accordance with DRD CLDC-103 NASA Standards and Specifications Compliance and Tailoring Plan.

Where the evaluation of a NASA defined standard results in the Contractor not adopting the NASA standard, the Contractor may propose an alternative standard or tailoring of the NASA standard in accordance with DRD CLDC-103 NASA Standards and Specifications Compliance and Tailoring Plan subject to NASA’s approval.

NASA has defined an adjudication process for applicable standards and specifications to be implemented as early as possible, potentially upon contract kickoff. NASA will have primary responsibility for adjudication and final approval of each proposed alternate (or tailored) standard. The Contractor with NASA support will develop and present a joint decisional package at a NASA Control Board for a final adjudication decision that shall include the following:

a) Rationale for using the Contractor proposed alternate standard, versus adopting the NASA standard

b) Technical overview of the proposed alternate standard

c) An assessment of past and current efforts to meet the intent of the NASA standard with proposed alternate standards (i.e. heritage usage summary)

d) An assessment of the estimated schedule, technical, and risk impacts associated with implementing the NASA standard as prescribed.

e) Impact(s) if the proposed alternate standard is not used.

f) Associated Verification approach when utilizing the proposed alternate standard.

g) Contractor risk assessment (cost, schedule, technical) of adopting the NASA standard.

h) Documented key areas of disagreement with input from NASA

i) Government risk assessment (cost, schedule, technical) of adopting the

Contractor proposed alternate and/or tailored standard, or variance request

The Contractor shall incorporate NASA Control Board final adjudication decisions in their documentation.

The Contractor should start the adjudication process as early as possible. NASA proposes holding technical coordination meetings shortly after contract award to discuss the alternate standards adjudication process, expectations, and initiate coordination efforts.

NASA expects adjudication to be completed by Preliminary Design Review (PDR) or on an exception basis for certain standards agreed to by NASA and the Contractor to be complete no later than Critical Design Review (CDR). In the event the Contractor proposed alternate standard is not approved by the agreed timeline, the NASA standard shall be applicable.

2.11 Safety and Mission Assurance

The Contractor shall develop, implement, deliver, maintain, and operate in compliance with the Safety and Mission Assurance Plan submitted per DRD CLDC-115 Safety and Mission Assurance (SMA) Plan.

2.11.1 Hazard Analysis and System Safety

The Contractor shall develop and demonstrate a process to identify, control, and verify critical and catastrophic hazards.

The Contractor shall develop, implement, deliver, maintain and operate in compliance with a hazard analysis and system safety plan that provides for NASA joint approval authority at co-chaired safety reviews for critical and catastrophic hazards and meets the intent of CLDP-STD- 3102, Commercial Low-Earth Orbit Development Program (CLDP) Hazard Analysis and Safety Process Standard, in accordance with DRD CLDC-115 Safety and Mission Assurance (SMA) Plan.

The Contractor shall develop, deliver and maintain Safety Data Packages in accordance with DRD CLDC-118 Safety Data Package.

2.11.2 Software Safety & Assurance

The Contractor shall develop, implement, deliver, maintain, and operate in compliance with a software safety and assurance plan that meets the intent of NASA-STD-8739.8B, Software Assurance and Software Safety Standard, Chapter 4 and Appendix A submitted as a component of the Contractor SMA Plan, per DRD CLDC-115 Safety and Mission Assurance (SMA) Plan.

The Contactor shall develop, deliver, maintain, and operate in compliance with a plan for third-party software Independent Verification and Validation (IV&V), in accordance with DRD CLDC-115 Safety and Mission Assurance (SMA) Plan. If the Contractor chooses to request Government IV&V support to meet this requirement, refer to Attachment J-14 Government Task Agreement.

2.11.3 Quality Assurance

The Contractor shall develop, implement, maintain, and operate in compliance with a Quality Assurance (QA) Plan submitted in accordance with DRD CLDC-115 Safety and Mission Assurance (SMA) Plan, for work performed by the Contractor as well as work delegated to subcontractors and suppliers.

2.11.3.1 Supply Chain Quality Surveillance

The Contractor shall develop, implement, and maintain a sub-tier Contractor quality surveillance approach in accordance with DRD CLDC-115 Safety & Mission Assurance (SMA) Plan.

The Contractor shall provide Supply Chain Visibility Reporting of the Contractor’s suppliers and sub-tier suppliers in accordance with DRD CLDC-122 Supply Chain Visibility (SCV) Reporting.

2.11.3.2 Nonconformances

The Contractor shall report emerging and confirmed hardware, manufacturing process, testing, and quality management system Nonconformances (NCs) in accordance with DRD CLDC-121 Nonconformance (NC) Reporting.

The Contractor shall provide operational and technical support in cases of process or product nonconformance that compel NASA to lead a technical investigation to determine the acceptability of a variance with respect to requirements conformity. This support includes submitting and reviewing technical materials used to understand the nonconformance, assess risks to product performance and reliability, and recommend timely, cost-effective corrective actions.

2.11.4 Reliability

The Contractor shall develop, implement, deliver, maintain and operate the CLDS in compliance with a Reliability Plan in accordance with DRD CLDC-115 Safety and Mission Assurance (SMA) Plan.

2.11.5 Orbital Debris, Jettisons, and Deorbit

The Contractor shall assess the risk to the CLDS and Crew resulting from damage or penetration of the CLDS components from Micrometeoroid Orbital Debris (MMOD) during all mission phases in accordance with DRD CLDC-119 Micrometeoroid Orbital Debris (MMOD) Report.

The Contractor shall develop, implement, deliver, maintain and operate the CLDS in compliance with a Jettison Plan in accordance with DRD CLDC-120 Jettison Plan.

The Contractor shall develop, implement, deliver, maintain, and operate the CLDS in compliance with a Destination Disposal Plan in accordance with DRD CLDC-123 Destination Disposal Plan.

2.11.6 Mishap Preparedness and Contingency Action Plans

The Contractor shall develop, implement, deliver, maintain, and operate in compliance with the Mishap Preparedness and Contingency Plan and Clause H.24 Mishap Reporting in the

Mishap Preparedness and Contingency Action Plan in accordance with DRD CLDC-117 Mishap Preparedness and Contingency Plan (MPCP).

2.11.7 Safety and Health

The Contractor shall follow the safety and health requirements of the local NASA Center when on NASA property or at a NASA facility.

2.11.8 Integrated Maintenance and Logistics Support

The Contractor shall develop, implement, deliver, maintain, and operate in compliance with the Integrated Maintenance and Logistics Support Plan and data submitted in accordance with DRD CLDC-133 Integrated Logistics and Maintenance Support.

2.12 NASA Access to Partner Facilities and Tools

The Contractor shall provide safety training, instruction, and certification for all Contractor-operated or Contractor provided integration facilities, launch sites, and landing sites to ensure NASA personnel and other users are aware of applicable hazards and possess adequate knowledge to perform their tasks safely.

The Contractor shall ensure physical and IT security for USG Payloads facilities, Payload data, and NASA personnel in Contractor-operated or provided facilities, control centers, accommodations and launch/landing sites.

The Contractor shall provide personnel sponsored by NASA (referred to in this section 2.12 as NASA personnel) general accommodations and access as follows:

• Provide accommodations and access to Health Stabilization Program facilities for two (2) NASA Flight Surgeons and three (3) USG supporting personnel, with the USG Crew, in accordance with DRD CLDC-113 Health Stabilization Program (HSP) Plan.

• Provide access to Health Stabilization Program facilities for USG Crew Immediate Family Members.

• Facilitate familiarization and Very Important Person (VIP) tours for up to ten (10) people of the Contractor's CVV, CaVV, or Destination control room and facilities no more than once per month.

• Provide one (1) dedicated office and accommodations for NASA Ground Personnel at each primary assembly, integration, destination and transportation location.

• Provide transportation of nine (9) NASA personnel, the USG Crew, plus an additional five (5) NASA personnel per USG Crew from NASA’s Johnson Space Center (JSC) to the launch site in accordance with DRD CLDC-131 Pre-Launch and Post-Landing Operations.

The Contractor shall provide NASA personnel accommodations and access for the transportation CVV flight control room (including during training/simulations) and processing facilities as follows:

• Provide one (1) console in the Crew Transportation flight control room for NASA personnel during launch, landing, phasing,…