Attachment_03,_GLS-RQMT-001_Gateway_Logistics_Services_Requirements.pdf

Attachment 03

GLS-RQMT-001, GATEWAY LOGISTICS SERVICES

REQUIREMENTS

Revision: BASIC Document No: GLS-RQMT-001

Release Date: August 8, 2019 Page: 2 of 60

Title: GATEWAY LOGISTICS SERVICES REQUIREMENTS

GLS-RQMT-001

BASIC

National Aeronautics and Space Administration

RELEASE DATE: AUGUST 8, 2019

Gateway Logistics Element John F. Kennedy Space Center

GATEWAY LOGISTICS SERVICES REQUIREMENTS

Release Date: August 8, 2019 Page: 3 of 60

REVISION AND HISTORY

Revision No.

Change No.

Description Release

Date

Basic - Basic revision for Gateway Logistics Services contract Request for Proposals

8/8/19

Release Date: August 8, 2019 Page: 4 of 60

TABLE OF CONTENTS

1.0 Introduction

1.1 Scope And Purpose

1.2 Logistics Services Overview

1.3 Logistics Mission Phases and Operations

1.4 Ground Rules And Assumptions

1.5 Change Authority/Responsibility

1.6 Convention and Notation

2.0 Documents

2.1 Applicable Documents

2.2 Reference Documents

2.3 Order of Precedence

3.0 Logistics Requirements

3.01 Overview and Description

3.02 Logistics Services and System Capabilities

L3-GLS-0011 Gateway Logistics Delivery Location

L3-GLS-1002 Pressurized Mass Delivery

L3-GLS-1003 Unpressurized Mass Delivery

L3-GLS-1004 Robotic Arm System Delivery

L3-GLS-1111 Robotic Arm Walk-Off

L3-GLS-1008 Disposal Transportation

L3-GLS-1074 Trash Stowage

L3-GLS-1104 Logistics Module Life

L3-GLS-1005 Uncrewed Operations

L3-GLS-1105 Trash Disposal

L3-GLS-1106 Maximum System Docking Mass

3.03 Autonomy and Docking

L3-GLS-1014 Critical Data Storage

L3-GLS-1023 Logistics Module Flight Software Updates

L3-GLS-1026 Caution and Warning Notifications

L3-GLS-1028 Docked Autonomous Operations

L3-GLS-1125 Gateway to Visiting Vehicle Interface Requirements

L3-GLS-0013 Autonomous Gateway Docking

L3-GLS-1012 Rendezvous, Proximity Operations, and Docking

L3-GLS-0034 RPOD Data Exchange Communication

L3-GLS-1114 RPOD Time-Critical Commands

L3-GLS-1050 Docking System

L3-GLS-1001 Active Docking System

3.04 Habitable Volume

L3-GLS-0025 Habitable Volume Fire Safety Systems

L3-GLS-0032 Habitable Volume for Payload, Cargo, and Trash Transfer Operations

L3-GLS-1056 Habitable Volume Atmosphere Pressure Range

L3-GLS-1057 Habitable Volume Atmosphere Leakage Limits

Release Date: August 8, 2019 Page: 5 of 60

L3-GLS-1103 Habitable Volume Condensation Prevention

L3-GLS-1123 Habitable Volume Environmental Control and Life Support

3.05 Crew Requirements

L3-GLS-1069 Human System Requirements (HSR)

L3-GLS-1095 Crew Displays and Controls Interface

3.06 Payloads and Cargo

L3-GLS-1126 Pressurized Payload & Cargo Environment Temperature

L3-GLS-1127 Pressurized Payload & Cargo Environment Pressure

L3-GLS-1128 Pressurized Payload & Cargo Environment Humidity

L3-GLS-1075 Gateway Inventory Management System (IMS) Interface

L3-GLS-1079 Mission-Specific, Permanently Mounted, Unpressurized Cargo and Payload Services & Interfaces

L3-GLS-1080 Standard Cargo Transfer Bag Stowage System

L3-GLS-1081 Alternate Passive Cargo Stowage System

L3-GLS-1082 Middeck and Double-Middeck Locker Equivalent Cargo and Payload System . 27

L3-GLS-1083 Alternate Mounted Cargo and Payload System

L3-GLS-1086 Unpressurized Cargo and Payload Launch and Transportation Environment ... 28

L3-GLS-1118 EVR-Compatible Unpressurized Cargo and Payload Services & Interfaces

3.07 Docked Operations and Interfaces

L3-GLS-0022 Docked Module Ventilation

L3-GLS-1015 Gateway Control of Logistics

L3-GLS-1016 Redundant Time-Triggered Ethernet

L3-GLS-1027 Data Prioritization

L3-GLS-1033 Docked Data Exchange with Vehicle System Manager

L3-GLS-1036 Remote Capability

L3-GLS-1045 Vestibule Pressurization

L3-GLS-1046 Vestibule De-Pressurization

L3-GLS-1051 Transfer Passageway Diameter

L3-GLS-1066 Crew Hatch Requirements

L3-GLS-1107 Non-Propulsive Venting

3.08 Power

L3-GLS-0005 Power To Payloads

L3-GLS-0021 Power Independence While Docked

L3-GLS-1011 Contingency Docked Power Interface

L3-GLS-1115 Docked Power Quality Specification

L3-GLS-1117 Payload Power Quality Specification

3.09 Communications

L3-GLS-0033 Intermodular Crew Voice Communications

L3-GLS-1021 Gateway Wireless Data Network Coverage

L3-GLS-1035 Logistics Module and Payload Data During Transit

L3-GLS-1100 Critical Event Telemetry

L3-GLS-1124 Payload Commanding

3.10 Extravehicular Robotics Compatibility

L3-GLS-1116 Berthing Capability

L3-GLS-1119 Berthing Grapple Fixture Accommodation

L3-GLS-1120 Berthing Grapple Fixture Interface

L3-GLS-1121 Extravehicular Robotics Base Points for Translation

Release Date: August 8, 2019 Page: 6 of 60

L3-GLS-1122 Extravehicular Robotics Translation Path Redundancy

3.11 Natural and Induced Environments

L3-GLS-0008 Payloads Induced Environment Isolation

L3-GLS-0024 Thermal Independence While Docked

L3-GLS-1010 Natural Space Environment

L3-GLS-1017 Critical Systems Survival at Vacuum

L3-GLS-1040 Uncrewed Temperature Range

L3-GLS-1043 Low Humidity Operation

L3-GLS-1060 Micrometeoroid Debris PNP

L3-GLS-1071 Intravehicular Activity Limit Loads

L3-GLS-1087 Ground Handling and Transportation Environment

L3-GLS-1096 Gateway Docking System Docking Limit Loads

L3-GLS-1098 Maximum Oxygen Concentration Nominal Total Pressure

L3-GLS-1041 Maximum Oxygen Concentration Low Pressure

L3-GLS-1108 Gateway Solar Array and Radiator Wing Maximum Normal Peak Plume Pressures

L3-GLS-1109 Gateway Surfaces Maximum Normal and Shear Plume Pressures

3.12 Safety

L3-GLS-1018 Logistics Module Tolerate Inadvertent Operation Action

L3-GLS-1044 Emergency Equipment Accessibility

L3-GLS-2001 Logistics Module Critical Hazards

L3-GLS-2002 Logistics Module Catastrophic Hazards

L3-GLS-2003 Logistics Module Failure Tolerance Without Emergency Equipment

L3-GLS-2004 Logistics Module Autonomous Operation

L3-GLS-2005 Logistics Module Reliability

L3-GLS-2006 Logistics Module Redundancy Design

L3-GLS-2011 Operational Hazard Controls

L3-GLS-2052 Logistics Module Crew Manual Override

L3-GLS-2053 Logistics Module Inhibit Monitoring

L3-GLS-2057 Logistics Module Deployable End Item Inhibit Monitoring

L3-GLS-2066 Logistics Module Computer Initiated Hazards

L3-GLS-2067 Logistics Module CBCS Safe Initialization

L3-GLS-2068 Logistics Module CBCS Orderly Shutdown

L3-GLS-2069 Logistics Module Safe Operation during Off-Nominal Power

L3-GLS-2070 Logistics Module Overrides by Operators

L3-GLS-2071 Logistics Module Out of Sequence Command Rejection

L3-GLS-2072 Logistics Module Inadvertent Memory Modification

L3-GLS-2073 Logistics Module CBCS Validation of External Inputs

L3-GLS-2074 Logistics Module CBCS Integrity Checks

L3-GLS-2075 Logistics Module CBCS Prerequisite Checks

L3-GLS-2076 Logistics Module Disabling of Arming Commands

L3-GLS-2077 Logistics Module CBCS Two Unique Commands to Deactivate Catastrophic Hazard Control

L3-GLS-2079 Logistics Module Unique Command Messages to Remove or Change State of an Inhibit

L3-GLS-2081 Logistics Module Detection and Safing within Time to Effect

L3-GLS-2082 Logistics Module Manual Safing Data

Release Date: August 8, 2019 Page: 7 of 60

L3-GLS-2113 Logistics Module Electromagnetic Effect Safety Margin when Demonstrated by Test

L3-GLS-2114 Logistics Module Electromagnetic Effect Safety Margin when Calculated by Analysis

L3-GLS-2117 Logistics Module Isolation for Users of Direct Current

L3-GLS-2118 Logistics Module DC Isolation of Isolated Power Sources

L3-GLS-2119 Logistics Module Circuit Conductors DC isolation

L3-GLS-2120 Logistics Module Mechanism State Indication for Hazard Control

L3-GLS-2121 Logistics Module Hatchway Drag-Throughs

L3-GLS-2122 Logistics Module Critical Seals with Major Outer Diameter Less than 0.5 Inches

L3-GLS-2123 Logistics Module Critical Seals with Major Outer Diameter Greater than 0.5 Inches

L3-GLS-2124 Logistics Module Critical Seals with Major Outer Diameter Greater than 6 Inches

L3-GLS-2131 Logistics Module Safe Recovery

L3-GLS-2132 Logistics Module Tolerate Inadvertent Operation Action During Failure

L3-GLS-2133 Logistics Module Controls for Human Error

L3-GLS-2140 Logistics Module Identification of Monitor Loss

L3-GLS-2141 Logistics Module Computer Hazard Controls

L3-GLS-2142 Logistics Module Shatterable Materials

L3-GLS-1151 Unplanned Pressurized Cargo Gas Release

3.13 Materials & Processes, Fluid Standards

L3-GLS-1113 Material Offgassing

L3-GLS-3010 Fluid Standard

L3-GLS-3012 Internal Cleanliness

L3-GLS-3013 External Cleanliness

TBDs AND TBRs

A.1 Scope

A.2 List of TBDs

A.3 List of TBRs

Glossary

Release Date: August 8, 2019 Page: 8 of 60

1.0 INTRODUCTION

1.1 SCOPE AND PURPOSE

The purpose of this document is to present the top-level functional, performance, and interface requirements which define the capabilities needed to accomplish cargo, payload, and element delivery services to the Gateway, located in a lunar Near Rectilinear Halo Orbit (NRHO). This document constitutes the technical requirements to be implemented by the National Aeronautics and Space Administration (NASA) Gateway Logistics Services (GLS) contract.

Section 3.0 of this document contains the technical requirements for the Gateway Logistics Services Contract, which are applicable to every Logistics mission unless otherwise noted.

1.2 LOGISTICS SERVICES OVERVIEW

NASA’s Gateway Program seeks to procure Gateway Logistics Services as a commercially managed, end-to-end service, similar to the approach used in the successful ISS Cargo Resupply Services (CRS) and NASA Launch Services (NLS) contracts.

The commercial Logistics service includes end-to-end cargo and payload delivery and removal services, from integration of NASA-provided cargo and payloads through launch, lunar transit, docked operations, and disposal. The Logistics Module, or LM, is the conceptual resupply space vehicle. It is an independent space system capable of transporting itself and Gateway cargo and payloads from the Earth to locations in an NRHO at the Moon, where it will autonomously rendezvous and dock with Gateway. It provides a crew hatch and a pressurized volume for pressurized cargo and payloads and crew occupation when docked, and external provisions for carrying unpressurized payloads when needed. When the Logistics Module’s transportation and storage services for a Gateway mission have been satisfied, and it has been packed with trash and outfitted with end-of-life mission items by the Gateway crew or robotic capabilities, the LM will autonomously undock and depart the Gateway, and transport itself to a disposal orbit.

Gateway Logistics missions can be categorized according to the GLS Contract Line Item Number (CLIN) structure. CLIN 1 Gateway Logistics Services Missions satisfy these primary objectives:

Delivery and disposal of pressurized and unpressurized cargo and payloads to and from the Gateway

Integrate with and extend Gateway systems to provide a safe, comfortable, and efficiently outfitted working environment for Gateway crew during logistics module entry, unpacking, powered payload operation, and packing for departure tasks.

Critical LM capabilities which enable CLIN 1 objectives are:

The ability of an LM to autonomously rendezvous and dock to the Gateway as a Visiting Vehicle (VV)

The ability to remain docked at the Gateway, without relying on Gateway crew or utilities for power, environmental control, or thermal control, for up to one year.

CLIN 1 missions may be augmented with mission-unique requirements in accordance with subCLIN 103 of the GLS contract RFP. SubCLIN 103 requirements may modify the Logistics Module and mission capabilities to accommodate or augment Gateway Phase 2 capabilities and provide mission-unique services to Gateway.

Release Date: August 8, 2019 Page: 9 of 60

CLIN 2 Specialized Delivery Missions provide for delivery of Gateway Elements to the Gateway. CLIN 2 mission requirements will be developed in a mission-specific requirements set and are not specified herein, with the exception of requirements for the delivery of a Robotic Arm, which has been allocated by the Gateway Program to the Logistics Element for delivery.

1.3 LOGISTICS MISSION PHASES AND OPERATIONS

Logistics missions consist of several distinct phases: pre-launch, launch and ascent, Earth-to-Moon transit, rendezvous, proximity operations, and docking with Gateway (RPOD), docked uncrewed, docked crewed, undocking and departure, and disposal. The pre-launch, launch and ascent, transit, and disposal phases will be managed by the Logistics service provider, with high-risk milestones and mission phase transition approval reserved for NASA Logistics Element management. The RPOD and docked phases operations will be jointly managed between NASA and the provider, to monitor and control the integrated Gateway- LM vehicle and systems as needed to safely execute vehicle and crew operations. A Mission Integration Operations Management Plan (MIOMP) will be jointly developed to describe and document the details of operational integration.

1.4 GROUND RULES AND ASSUMPTIONS

Reserved

1.5 CHANGE AUTHORITY/RESPONSIBILITY

Proposed changes to this document shall be submitted via a Change Request (CR) to the Gateway Program Control Board (GPCB) for consideration and disposition. All such requests will adhere to the Gateway Configuration Management Change Process documented in DSG-PLAN-004.

The appropriate NASA Office of Primary Responsibility identified for this document is the Logistics Element Architecture requirements development team.

1.6 CONVENTION AND NOTATION

Any references to “Level 2” or “L2” in this document refer to items under control or ownership of the Gateway Program Office, located at the NASA Johnson Space Center. The Logistics Element is a Level 3 project element office supporting Gateway, located at the NASA Kennedy Space Center.

The Gateway Program defines its implementation of requirement verbs as follows:

a) “Shall” – Used to indicate a requirement that is binding, which must be implemented and its implementation verified in the design.

b) “Should” – Used to indicate good practice or a goal which is desirable but not mandatory.

c) “May” – Used to indicate permission.

d) “Will” – Used to indicate a statement of fact or declaration of purpose on the part of the government that is reflective of decisions or realities that exist and are to be taken as a given and not open to debate or discussion.

e) “Is” or “Are” – Used to indicate descriptive material.

Release Date: August 8, 2019 Page: 10 of 60

f) “TBD” – Used to indicate items that are not yet known. Will be denoted as <TBD-

XXX>.

g) “TBR” – Used to indicate items that are still under analysis or being refined, and are subject to update/change. Will be denoted as <TBR-XXX>.

Rationales, included for many of the requirements, are intended to provide clarification, justification, purpose, and additional data relating to the origin of a requirement. In the event that there is an inconsistency between a requirement and its rationale, the requirement always takes precedence.

A parent or derived-from requirement may be listed after a Logistics Level 3 requirement.

These relationships have been provided to convey traceability to the parent Level 2 requirement or other source.

Logistics Element-specific terminology used in defining the GLS technical requirements is defined in Appendix B – Glossary.

Release Date: August 8, 2019 Page: 11 of 60

2.0 DOCUMENTS

2.1 APPLICABLE DOCUMENTS

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications that are called out in Section 3.0 requirements. The documents listed in this paragraph are applicable to the extent specified herein.

Document Number Rev Document Title

ASTM–E595

Standard Test Method for Total Mass Loss and Collected Volatile Condensable Materials

CSA-GWY-ID-0001

Initial

Release Gateway Extra-Vehicular Robotics Interface Requirements and Definition Document

DSG-RQMT-001 Draft Gateway Program System Requirements

DSG-RQMT-002 Draft Gateway Human Systems Requirements Volumes 1 and 2

DSG-RQMT-011

Rev A

Draft Gateway Program Hazard Analysis Requirements

DSG-SPEC-CDH-004 Draft Gateway Program Subsystem Specification for Command and Data Handling

DSG-SPEC-COMM-005 Draft Gateway Program Subsystem Specification for COMM

DSG-SPEC-ECLSS-007 Draft Gateway Program Subsystem Specification for ECLSS

DSG-SPEC-HTCH-019 Draft Gateway Program Subsystem Specification for Hatches

DSG-SPEC-MECH-017 Draft Gateway Docking System Specification (GDSS)

DSG-SPEC-PQS-020 Draft Gateway Program Electrical Power Quality Specification Requirements for 120Vdc

DSG-SPEC-PWR-011 Draft Gateway Program Subsystem Specification for Power (PWR)

GP-10031 Draft Gateway to Visiting Vehicle IRD

IEST-STD-CC1246E E Product Cleanliness Levels

MPCV 70156 F

Cross-Program Fluid Procurement and Use Control Specification

SLS-SPEC-159 E Cross-Program Design Specification for Natural Environments

SSP 50833 B

International Space Station Program Cargo Transport Interface Requirements Document

Release Date: August 8, 2019 Page: 12 of 60

2.2 REFERENCE DOCUMENTS

The following documents contain supplemental information to guide the user in the application of this document. These may be called out in Section 3.0 requirement rationales, or other areas of the document.

Document Number Rev Document Title

CSA-GWY-CO-0001

Initial

Release Gateway External Robotics Concept of Operations

CSA-GWY-CD-0001

Initial

Release Gateway External Robotics Concept Description Document

(CDD)

DSG-CONOP-001 Baseline Gateway Program Concept of Operations

DSG-PLAN-009 Draft Integrated Verification & Validation (V&V) Plan

DSG-SPEC-CHI-018 Draft Gateway Program Subsystem Specification for Computer Human Interfaces (CHI)

DSG-SPEC-CHP-010 Draft Gateway Program Subsystem Specification for Crew Health and Performance (CHP)

DSG-SPEC-CS-006 Draft Gateway Program Subsystem Specification for Crew Systems

DSG-SPEC-FSW-014 Draft Gateway Program Subsystem Specification for Software

DSG-SPEC-GNC-009 Draft Gateway Program Subsystem Specification for Guidance Navigation and Control (GNC)

DSG-SPEC-IMG-016 Draft Gateway Program Subsystem Specification for Imagery

DSG-SPEC-IVR-013 Draft Gateway Program Subsystem Specification for Internal Robotics

DSG-SPEC-THR-015 Draft Gateway Program Subsystem Specification for Thermal

DSG-SPEC-VSM-003 Draft Gateway Program Subsystem Specification for Vehicle System Manager (VSM)

IDSS IDD E

International Docking System Standard (IDSS) Interface Definition Document (IDD)

SSP 50808 G

International Space Station to Commercial Orbital Transportation Services (COTS) IRD

SSP 50005 G International Space Station Flight Crew Integration Standard

2.3 ORDER OF PRECEDENCE

In the event of a conflict between the text of this specification and the references cited herein, the text of this specification takes precedence. Nothing in this specification, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

Release Date: August 8, 2019 Page: 13 of 60

3.0 LOGISTICS REQUIREMENTS

This section contains the technical requirements to be implemented by the Logistics service provider's space system, referred to herein as the Logistics Module. All requirements apply to each Logistics mission unless otherwise specified. NASA reserves the right to tailor the requirements for any particular mission by addition, deletion, or modification, consistent with the provisions of the GLS contract.

Requirement verification methods, approaches, detailed verification planning, verification requirements, and a requirements verification & traceability matrix will be provided in the contractor's submittal of GLS contract Data Requirement Description (DRD) GLS-012 Verification & Validation Plan.

3.01 OVERVIEW AND DESCRIPTION

The requirements herein focus on the key performance and interface requirements that are common across all Logistics Missions to the Gateway, unless otherwise noted. As Gateway assembly progresses, new needs or capabilities may be implemented by future Logistics missions. Additional requirements can be established on a per-mission basis as needed via subCLIN 103 options in the GLS contract. The requirements herein are applicable during nominal operations and do not account for maintenance or contingency events unless otherwise specified.

The requirements are written to help a commercial provider execute the service needed by NASA.

Some Gateway system-level specifications are still in development and may be called out in the rationale of requirements for the providers to refer to what may be applicable to their system. The specification requirements are not intended to all be applicable to the Logistics Module, but should still be considered when designing the spacecraft and service.

Release Date: August 8, 2019 Page: 14 of 60

3.02 LOGISTICS SERVICES AND SYSTEM CAPABILITIES

This section contains the top-level Gateway Logistics Service requirements.

L3-GLS-0011 Gateway Logistics Delivery Location

The Logistics services provider shall deliver cargo and payloads to the Gateway, which will be located in a 9:2 lunar synodic resonant southerly Near-Rectilinear Halo Orbit (NRHO).

Rationale: The Earth-Moon system Near-Rectilinear Halo Orbit (NRHO) is the established reference orbit for the Gateway. There are four potential NRHOs where the Gateway may require rendezvous by the Logistics Module. The Gateway primary orbit is the L2 South NRHO, as the reference orbit described in DSG-ADD-005, Gateway Integrated Performance Assessment. The specific location for delivery will be specified by NASA at Authority To Proceed for each mission, but may be modified up until L-X months to launch, as proposed by the contractor.

Derived From/Parent Requirement:

L2-GW-0152 Logistics Resupply

L2-GW-0163 NRHO Orbit

L3-GLS-1002 Pressurized Mass Delivery

The Logistics services provider shall deliver a minimum 3400 kg (7496 lb) pressurized cargo and payloads per mission to the Gateway.

Rationale: The requirement is the minimum estimated mass required for a Gateway Logistics Mission. The capability to deliver mass above the upper limit provides additional capability to the Gateway.

L3-GLS-1003 Unpressurized Mass Delivery

The Logistics services provider shall deliver a minimum 1000 kg (2205 lb) unpressurized cargo and payloads per mission to the Gateway.

Rationale: The minimum specified is the minimum estimated unpressurized mass required for a Gateway Logistics Mission to deliver cargo and payloads to sustain operations during the assembly phase. The delivery of a Robotic Arm may exceed this minimum, and is considered a specialized delivery CLIN 2 mission. The capability to deliver greater than this mass per mission provides additional capability to the Gateway.

L3-GLS-1004 Robotic Arm System Delivery

The Logistics services provider shall deliver a Robotic Arm system with a maximum mass of 2200kg (4850lb) to the Gateway as an unpressurized payload.

Note: This requirement applies to CLIN 2 missions only.

Rationale: A Robotic Arm system is to be delivered to the Gateway via a Logistics mission in Phase 2. The Robotic Arm system elements may be delivered on separate missions depending on Gateway assembly requirements and the GLS provider's system capabilities. Robotic Arm system interface requirements are contained in CSA-GWY-ID-0001, Gateway Extra-Vehicular Robotics Interface Requirements and Definition Document. These requirements define the arm system and Logistics Vehicle functional, logical, and physical interfaces (e.g. power, thermal control, data, software execution, induced environments, release mechanisms, and commanding).

CSA-GWY-CO-0001 Gateway External Robotics Concept of Operations, and CSA-GWY-CD-

Release Date: August 8, 2019 Page: 15 of 60

0001, Gateway External Robotics Concept Description Document (CDD) may also be used as references for Robotic Arm delivery specifications.

L3-GLS-1111 Robotic Arm Walk-Off

The Logistics Vehicle that delivers the Robotic Arm shall support Robotic Arm self-deployment and walk-off onto the Gateway.

Note: This requirement applies to CLIN 2 missions only.

Rationale: The Robotic Arm delivery mission concept requires that the Logistics Vehicle provide the power, data, attach points, attachment fixtures, and computational resources necessary for the arm system to activate and deploy itself from the Logistics Vehicle and onto the Gateway.

CSA-GWY-ID-0001, Gateway Extra-Vehicular Robotics Interface Requirements and Definition Document defines the arm system and Logistics functional, logical, and physical interfaces (e.g.

power, thermal control, data, software execution, induced environments, release mechanisms, and commanding). Documents CSA-GWY-CO-0001 Gateway External Robotics Concept of Operations, CSA-GWY-CD-0001, Gateway External Robotics Concept Description Document (CDD), and CSA-GWY-ID-0001, Gateway Extra-Vehicular Robotics Interface Requirements and Definition Document contains the Robotic Arm system delivery and walk-off requirements.

Derived From/Parent Requirement:

L2-GW-0313 EVR Self-Deployment Support

L3-GLS-1008 Disposal Transportation

The Logistics services provider shall transport the Logistics Module to a government-approved safe and stable end-of-mission disposal orbit or other government-approved disposal location.

Rationale: Because multiple delivery missions are required for assembly and to support crew missions, the Logistics Module needs to be separated and disposed of before the Gateway end of life and disposal. Disposal orbit must comply with the NASA requirements for minimizing orbital debris around the moon and in the vicinity of Earth-moon Lagrange Points. If a Logistics Module will have a secondary mission, beyond the scope of the Logistics Module mission (for NASA or for commercial purposes) the contractor and NASA will determine the approved orbital disposal location that will effectively complete the Logistics Module mission.

L2-GW-0006 Gateway Disposal

L3-GLS-1074 Trash Stowage

The Logistics Module shall provide a storage system, accessible from within the habitable volume, that provides volume, attach points, and restraint systems to store contained Gateway trash and waste for the duration of the LM mission.

Rationale: The Gateway trash management concept intends for trash and waste to be pre-processed for containment before being stored for disposal by the LM. Pre-processing ensures trash and waste is consolidated, secured against leakage, dispersion, and/or odor evolution. The LM will provide waste storage that further ensures trash and waste is stored in a manner such that, over the life of the LM, the stored waste and trash does not negatively affect the habitability of the LM or Gateway atmospheres. LM-stored trash and waste includes crew metabolic waste and expected biological hazardous waste, with appropriate wrappings and/or barriers that is usable by crew and does not allow inadvertent release of trash into the habitable volume. Once

Release Date: August 8, 2019 Page: 16 of 60 properly contained, trash containers will be transferred to the Logistics Module for long term stowage and disposal, when the LM departs the Gateway.

Derived From/Parent Requirement:

L2-GW-0232 Body Waste Management

L2-GW-0236 Trash Accommodation

L2-GW-0237 Management of Biological Hazards

L3-GLS-1104 Logistics Module Life

The Logistics Module shall operate for a minimum of one year while docked to Gateway.

Rationale: Logistics Modules supporting crewed missions are expected to support a Gateway crew flight rate of one mission per year. A one year Logistics Module docked life supports this flight rate, with margin for on-orbit docking and checkout prior to crew arrival, and supports crewed missions of <TBD-007> days.

L2-GW-0003 Uncrewed Operations

L3-GLS-1005 Uncrewed Operations

The Logistics Module shall satisfy docked operational life requirements without preventative or corrective maintenance from Gateway crew.

Rationale: The intent of this requirement is to minimize the use of limited crew time for maintenance or housekeeping tasks. Additionally, the Gateway concept of operations includes extended uncrewed periods during which the Gateway will be monitored and controlled remotely.

Gateway elements should be designed to operate flight systems and maintain pressurized environments without the need for crew intervention.

Some tasks, such as establishing intermodular ventilation (IMV) ducting, require assistance from the crew to complete LM/Gateway integration. The intent of this requirement is for LM systems to be designed to be maintenance-free for the life of the module. Due to the short duration of the crewed phase of Gateway operations, minimizing Gateway and LM maintenance tasks is a critical goal to ensure maximum utilization of Gateway for primary mission and science objectives.

L2-GW-0003 Uncrewed Operations

L3-GLS-1105 Trash Disposal

The Logistics Module shall dispose of at least the same mass of pressurized trash from the Gateway as was delivered on that mission.

Rationale: With respect to the delivered mass, removal of an equivalent mass in the form of trash, waste, or end-of-life Gateway mission items, is a key function of the Gateway Logistics service toward preventing the accumulation of mass/volume in the Gateway stack over its 15-year life. In some cases, volume may be the limiting factor rather than mass. However, the intent is that NASA will maximize both mass and volume for disposal on the logistics module.

L2-GW-0236 Trash Accommodation

Release Date: August 8, 2019 Page: 17 of 60

L3-GLS-1106 Maximum System Docking Mass

Upon first docking to Gateway, the Logistics Module mass, inclusive of cargo and payloads, shall not exceed 14 metric tons (30,865lb).

Note: This requirement does not apply to CLIN 2 missions.

Rationale: An LM upper mass limit of 14 metric tons was used in Gateway Integrated Analysis Cycle 3. A maximum mass constraint for Logistics Modules protects Gateway Guidance, Navigation, and Controls (GNC) and Attitude Control System sizing and development. Specialized delivery missions transporting Gateway elements to Gateway will not be held to this limit;

specialized delivery mission Logistics Vehicle mass limits will be defined in the mission unique requirements set.

Release Date: August 8, 2019 Page: 18 of 60

3.03 AUTONOMY AND DOCKING

Upon arrival in cislunar space and entry into the Gateway Rendezvous Sphere, the Logistics Module will be expected to comply with Gateway visiting vehicle requirements. At the time of publication, these requirements are under development but are expected to generally follow previously established rules and conventions for International Space Station (ISS) rendezvous, proximity operations, and docking (RPOD) of ISS visiting commercial and government vehicles.

In this document, RPOD is frequently used to refer to the phases of flight when the Gateway and the Logistics Module vehicles are operating in space together within the Gateway Rendezvous Sphere, centered on Gateway. RPOD may be assumed by the reader to include not only the approach and docking phases of flight, but also the undocking and departure phases of flight.

Autonomy refers to the ability of the Logistics Module to meet mission requirements with little to no intervention or involvement by crew or ground operators. Due to the extended periods of uncrewed time while the Logistics Module is docked to Gateway, higher degrees of autonomy are expected for Logistics Modules than ISS resupply craft.

L3-GLS-1014 Critical Data Storage

The Logistics Module shall store a minimum of 21 days of critical health and status data.

Rationale: Gateway and Logistics Module mission profiles may include periods of poor or no communications with the ground. During these periods, a store-and-forward method of data management is necessary to prevent the loss of Logistics Module data. Types and quantity of data are to be determined by the Logistics provider and should include vehicle health and control data. Critical payload health and status data may be required.

L3-GLS-1023 Logistics Module Flight Software Updates

The Logistics Module shall perform flight software updates without impacts to Gateway operations.

Rationale: Modern commercial space systems regularly receive software updates while in their operational mission environments. Should the Logistics Module flight or other software components require in-flight updates from the ground, these updates should not prevent or interfere with Gateway operations.

L2-GW-0057 FSW Updates

L3-GLS-1026 Caution and Warning Notifications

The Logistics Module shall detect, report, and annunciate faults for alerts, caution, warning, and emergency events to the crew, ground, or Gateway Vehicle System Manager (VSM).

Rationale: Gateway crew and ground controllers should be informed of any events or conditions originating in Logistics Module systems which indicate off-nominal conditions which could damage the LM or Gateway, or harm the crew. C&W Annunciations may be reported to the Gateway Vehicle Systems Manager (VSM) for annunciation on Gateway computer displays or other visual or audible indicators, including Logistics Module indicators.

L2-GW-0062 Caution & Warning (C&W) Annunciation

Release Date: August 8, 2019 Page: 19 of 60

L3-GLS-1028 Docked Autonomous Operations

The Logistics Module shall meet all habitable volume, payload, interface, and safety requirements independent of ground communications or crew action while docked to the Gateway for up to 21 continuous days.

Rationale: The Gateway will be operated as both a crewed and uncrewed spacecraft, and will experience extensive resupply and communication constraints. The requirement is focused on ensuring continuity of safe operations between the Gateway and the Logistics system during periods of no communication with the ground or presence of crew. This will necessitate the capability for autonomous operations. The time period in this requirement is derived from missions beyond the Earth-Moon system with extended comm outages (e.g. Earth-Mars superior conjunction). To demonstrate these capabilities, the Gateway needs to provide autonomous vehicle control, nominal and off-nominal systems management, and utilization as well as providing essential system capabilities like data storage.

L2-GW-0044 Independent Operations

L3-GLS-1125 Gateway to Visiting Vehicle Interface Requirements

The Logistics Module shall comply with the interface requirements applicable to Logistics Modules as defined in GP-10031, Gateway to Visiting Vehicle Interface Requirements Document (IRD).

Rationale: GP-10031 contains interface requirements which will be applicable to all Gateway Visiting Vehicles, including Logistics Modules, Human Lander Systems, and the Orion spacecraft.

The document will cover functional interfaces between Gateway and VV's during approach/departure, docking/undocking, and mated operations, and will be the only means of communicating interface expectations to a VV. A Logistics Module Annex in GP-10031, Gateway to Visiting Vehicle Interface Requirements Document, will be used to specify those VV interface requirements which will apply to LM.

L3-GLS-0013 Autonomous Gateway Docking

The Logistics Module shall perform autonomous rendezvous, proximity operations, docking, undocking, and departure at any available Gateway radial port.

Rationale: The Gateway Guidance, Navigation & Control (GNC) specification DSG-SPEC-GNC- 009 will define Gateway-to-visiting vehicle RPOD requirements and concept of operations, as tailored for Gateway from the International Rendezvous System Interoperability Standard (IRSIS).

Gateway requires autonomous docking and undocking because the LM is uncrewed, and the Gateway may be uncrewed at the time of the LM arrival and departure.

L2-GW-0008 Crew/Ground Assisted Docking, Undocking, Berthing, and

Unberthing

L2-GW-0152 Logistics Resupply

Release Date: August 8, 2019 Page: 20 of 60

L3-GLS-1012 Rendezvous, Proximity Operations, and Docking Role

During autonomous rendezvous, proximity operations, docking, undocking, and departure phases of flight, the Logistics Module shall be the chaser vehicle.

Rationale: The Gateway rendezvous, proximity operations, and docking concept of operations has established the Gateway as the target vehicle, requiring that any visiting vehicles perform the active "chaser" role.

L3-GLS-1034 RPOD Data Exchange Communication

The Logistics Module shall exchange data and commands with the Gateway via S-band communications during rendezvous, proximity operations, docking, undocking, and departure maneuvers and operations.

Rationale: The Gateway implements the International Communication System Interoperability Standard (ICSIS) for space-to-space comm between Gateway and Visiting Vehicles as specified in DSG-SPEC-COMM-005, Gateway Program Subsystem Specification for Comm.

Gateway communications with visiting vehicles allows for direct data transfer between the visiting vehicle and the Gateway (e.g. commands, telemetry, health and status, GNC data) during rendezvous, proximity operations, docking, and undocking. This same communications link implements Gateway-to visiting vehicle time-critical commands to initiate safety provision maneuvers such as Rendezvous suspend, Rendezvous resume, Collision Avoidance Maneuver, and Abort execute.

L2-GW-0038 Visiting Vehicle Communication

L3-GLS-1114 RPOD Time-Critical Commands

The Logistics Module shall accept, confirm receipt of, and execute commands issued automatically by its onboard systems or by external commands issued by Gateway crew or ground controllers to perform the following during rendezvous, proximity operations, docking, undocking, and departure: Rendezvous suspend, Rendezvous resume, Collision Avoidance Maneuver (CAM).

Rationale: To ensure the safety of Gateway and crew, if present, automatic and crew or ground operator issued abort, hold, and continue functions for Logistics Modules are necessary.

Note on Collision Avoidance Maneuver (CAM): Gateway CAM concept is similar to that of the ISS in that the visiting vehicle should be able to execute a CAM at all times for all RPOD phases.

During a CAM, the visiting vehicle must stop closing (decreasing relative range) and then establish an opening rate (increase relative range). For ISS rendezvous, a CAM would put the vehicle on a 24-hour safe free drift trajectory. A similar safe free-drift trajectory and duration for cislunar and deep space operations at Gateway has not yet been defined.

L2-GW-0199 Autonomous Operation

Release Date: August 8, 2019 Page: 21 of 60

L3-GLS-1050 Docking System

The Logistics Module shall include a docking system compliant with the Gateway Docking System (GDS) requirements for Visiting Vehicles as specified in DSG-SPEC-MECH-017, Gateway Docking System Specification (GDSS).

Rationale: The GDSS is the Gateway Program's implementation of the International Docking System Standard (IDSS). Compatibility of Gateway docking ports and use of common design specifications maximizes Gateway and Visiting Vehicle port assignment flexibility for future expansion and contingency Gateway stack configurations. Logistics Modules carrying pressurized cargo and payloads will dock to radial ports as Visiting Vehicles.

L2-GW-0166 Gateway Standard Docking Port

L3-GLS-1001 Active Docking System

The Logistics Module shall have an active docking system.

Rationale: Gateway radial docking ports are currently baselined as "passive", requiring that all Visiting Vehicles intending to dock to radial ports carry the active half of the docking system.

Release Date: August 8, 2019 Page: 22 of 60

3.04 HABITABLE VOLUME

The habitable volume is the pressurized portion of the Logistics Module where Gateway crew will interact with the LM and its cargo.

L3-GLS-0025 Habitable Volume Fire Safety Systems

The Logistics Module shall implement requirements for fire safety systems within the habitable volume as allocated to the Logistics Module in DSG-SPEC-ECLS-007, Gateway Program Subsystem Specification for ECLSS.

Rationale: Each Gateway habitable element, including the Logistics habitable volume, is to include an independent fire detection, isolation, and suppression system. The ECLS specification contains the Gateway program requirements for implementing fire safety systems on Logistics Modules.

L2-GW-0091 Fire Protection and Prevention

L3-GLS-0032 Habitable Volume for Payload, Cargo, and Trash Transfer Operations

The Logistics Module shall provide a habitable volume for crew payload, cargo, and trash transfer operations.

Rationale: Crew members will perform payload, cargo, and trash transfer operations in a "shirt sleeve" environment, therefore it is necessary to maintain appropriate environmental conditions as part of an integrated Gateway Environmental Control and Life Support (ECLS) system. Mission and volume designers are to carefully analyze volume needs of the crew, crew equipment, storage, trash containment volumes and trash transition plans to ensure they are adequately sized to provide adequate net habitable volume for the crew to effectively and efficiently perform transfer operations. Crew requirements applicable to the LM habitable volume are provided in DSG-RQMT-002 Volume 1, Gateway Human-System Requirements (HSR), and DSG-RQMT-002 Volume 2, Human-System Requirements for Subsystems. Habitable volume requirements for lighting are governed by DSG-SPEC-CHI-018, Gateway Program Subsystem Specification for Computer Human Interfaces (CHI).

Derived From/Parent Requirement:

L2-GW-0206 Shirt Sleeve Environment

L2-GW-0213 Crew Tasks Volumes

L3-GLS-1056 Habitable Volume Atmosphere Pressure Range

Logistics Module systems and components in the habitable volume shall operate in an internal atmosphere pressure range from 65 kPa (9.5 psia) to 105 kPa (15.2 psia) during nominal operations.

Rationale: When crewed with open hatches, the Gateway and Logistics Module atmospheres will be nominally maintained by the Gateway to pressures near Earth sea level 101 kPa (14.7 psi).

When the LM is uncrewed, i.e. during launch, transit, and docked with hatches closed, the LM atmosphere pressure will be controlled by the LM at the discretion of the provider to meet pressurized payload requirements until crew entry requirements take precedence. The full range of pressures specified allows for operational flexibility during crewed and uncrewed periods, including response to contingency scenarios and potential reduction of consumables during uncrewed periods. This function must be performed during crewed and uncrewed periods to protect both crew and vehicle systems. Further specification will be found in DSG-SPEC-ECLS-

Release Date: August 8, 2019 Page: 23 of 60

007, Gateway Program Subsystem Specification for ECLSS. LM habitable volume make-up gas requirements are specified by L3-GLS-3010.

L2-GW-0227 Total Pressure Range

L3-GLS-1057 Habitable Volume Atmosphere Leakage Limits

The Logistics Module shall limit atmosphere leakage to less than 0.01 kg/day.

Rationale: Leakage should be managed to control the amount of consumables needed to maintain a safe habitable environment. If leakage exceeds the allotment, then the pressure control system and stored gases may run out. This is a particular concern during the long duration uncrewed mission phases.

L2-GW-0239 Atmosphere Leakage

L3-GLS-1103 Habitable Volume Condensation Prevention

The Logistics Module shall limit condensation persistence on surfaces within the habitable volume to 1 hour per day.

Rationale: The system is to provide controls and mitigation steps to limit the formation of water condensate on internal surfaces, which has been demonstrated to promote growth of fungi, as this poses a hazard to crew health. Examples of moisture buildup from Mir and ISS missions that resulted in fungal growth include non-insulated cold surfaces and designed operations which moisten surfaces (such as wetting a cloth) without appropriate drying. Condensation on a non-ventilated surface will be difficult to dry.

L3-GLS-1123 Habitable Volume Environmental Control and Life Support

The Logistics Module shall implement requirements for habitable volume environmental control and life support as allocated to the Logistics Module in DSG-SPEC-ECLS-007, Gateway Program Subsystem Specification for ECLSS.

Rationale: The Gateway Program Subsystem Specification for ECLSS defines the specific functionality required of the ECLSS to enable top level capabilities, associated design standards, and module level functional and performance requirements. Requirements allocations to the Logistics Module establish the functions and characteristics required of the LM when docked to the Gateway, to complement and extend the Gateway ECLS, as well as to ensure the safety and health of the crew while they are working in the LM habitable volume. Key functions allocated to the LM include, but are not limited to: air circulation and filtration, atmosphere monitoring and replenishment, condensation control, and control integration with Gateway ECLS.

L2-GW-0249 ECLSS Subsystem Specification

Release Date: August 8, 2019 Page: 24 of 60

3.05 CREW REQUIREMENTS

L3-GLS-1069 Human System Requirements (HSR)

The Logistics Module shall comply with human system requirements applicable to the LM in DSG-RQMT-002, Gateway Human-System Requirements (HSR) Volume 1, Human System Requirements, and Volume 2, Human System Requirements for Subsystems.

Rationale: Providing for the safety, comfort, and basic operational needs of the Gateway crew while they perform work tasks in the Logistics Module is paramount- the human is often the critical factor in the success of Gateway missions. Any activity that involves the human must meet the human factors, habitability, and environmental health requirements in DSG-RQMT-002 HSR Volumes 1 and 2, which are tailored from NASA-STD-3001, Volume 1 and Volume 2, as required by NPR 8705.2C for human rating of space systems.

L2-GW-0119 Human System Requirements (HSR)

L3-GLS-1095 Crew Displays and Controls Interface

The Logistics Module habitable volume shall provide an interface to the Gateway network for crew displays and controls.

Rationale: Crew capability (data/command interfaces) provides monitoring of the Caution and Warning (C&W) as well as nominal and off-nominal control of life support, thermal control, communication, and other system functions necessary for safe operations from any habitable element.

L2-GW-0052 Crew Displays and Controls

Release Date: August 8, 2019 Page: 25 of 60

3.06 PAYLOADS AND CARGO

L3-GLS-1126 Pressurized Payload & Cargo Environment Temperature

When not integrated with Gateway ECLS, the Logistics Module (flight and ground processing) shall provide a temperature environment to the pressurized cargo and payloads in the range of 18.3 deg C to 29.4 deg C (65 deg F to 85 deg F).

Rationale: Requirement defines an acceptable temperature range to be maintained for pressurized cargo and payloads during the ground processing, transit, and docked with closed hatch phases of flight. Some cargo items, such as food or medicine, may require a narrower acceptable range. Mission-specific cargo requirements will be established in the mission-specific payload-to-Logistics Module Interface Requirements Document.

L3-GLS-1127 Pressurized Payload & Cargo Environment Pressure

When not integrated with Gateway ECLS, the Logistics Module (flight and ground processing) shall provide a nominal pressure environment to the pressurized cargo and payloads in the range of 95.8 kPa to 104.8 kPa (13.9 psia to 15.2 psia).

Rationale: Requirement defines an acceptable pressure range to be maintained for pressurized cargo and payloads during the ground processing, transit, and docked with closed hatch phases of flight. Ranges are taken from SSP 50808, International Space Station (ISS) to Commercial Orbital Transportation Services (COTS) Interface Requirements Document (IRD).

L3-GLS-1128 Pressurized Payload & Cargo Environment Humidity

When not integrated with Gateway ECLS, the Logistics Module (flight and ground processing) shall provide a relative humidity environment to the internal cargo in the range of 25 to 75 percent.

Rationale: Requirement defines an acceptable humidity range to be maintained for pressurized cargo and payloads during the ground processing, transit, and docked with closed hatch phases of flight. Ranges are taken from SSP 50808, International Space Station (ISS) to Commercial Orbital Transportation Services (COTS) Interface Requirements Document (IRD).

L3-GLS-1075 Gateway Inventory Management System (IMS) Interface

The Logistics Module shall provide attach points for identification labels with unobstructed access for use by the Gateway Inventory Management System (IMS).

Rationale: The Gateway Inventory Management System will provide inventory identifiers (optical labels or RFID tags) and tracking for crew and Inter-Vehicular Robotics (IVR) systems. Cargo and payloads in the habitable volume of the Logistics Module will have identifiers attached to them that can be scanned by the IMS. The stowage system containers used in the LM (e.g., bags, middeck lockers, drawers or other closed containers) may also require identifiers to be attached to identify the contents of the cargo stowed in those containment devices. IMS may also require identifiers or scanners on permanently-mounted racks or other structures within the LM to provide orientation and location information within the module for the crew or IVR systems or to identify general areas within the LM habitable volume (e.g., separate sections dedicated to food storage or trash storage).

Derived From/Parent Requirement:

L2-GW-0153 Inventory Management

L2-GW-0154 Stowage System

Release Date: August 8, 2019 Page: 26 of 60

L3-GLS-1079 Mission-Specific, Permanently Mounted, Unpressurized Cargo and Payload Services & Interfaces

The Logistics Module shall provide structural support and electrical and data services via interfaces with mission-specific cargo and payloads that are permanently mounted to the exterior of the Logistics Module.

Rationale: Externally-mounted payloads that are not intended for EVR transfer from the Logistics Module or other manipulation/handling by the Gateway EVR System, may be permanently mounted to an exterior site on the unpressurized volume of the Logistics Module, or to an external adapter interface that may include mission-specific physical interfaces for electrical or data connections.