Gateway Logistics Model - NASASpaceFlight.com

Attachment 03 GLS-RQMT-001, GATEWAY LOGISTICS SERVICES

REQUIREMENTS

Revision: Draft Document No: GLS-RQMT-001 Release Date: June 14, 2019 Page: 2 of 63 Title: GATEWAY LOGISTICS SERVICES REQUIREMENTS

NASA and International Partner Internal Use Only • Do Not Distribute

This document may only be released according to the Destination Control Statement on the front cover.

2

GLS-RQMT-001 (DRAFT)

National Aeronautics and Space Administration RELEASE DATE: JUNE 14, 2019

Gateway Logistics Element John F. Kennedy Space Center

GATEWAY LOGISTICS SERVICES REQUIREMENTS

This document contains data within the purview of the U.S. Export Administration Regulations (EAR), 15 CFR 730-774, and is classified as EAR99/NLR. The document may be used only in the International Space Station (ISS) Program to fulfill responsibilities of the Parties or of a Cooperating Agency of an ISS Partner in furtherance of the ISS Intergovernmental Agreement. Re-transfer or disclosure to, or use by, any persons other than citizens of ISS Program International Partner countries, or use for any other purpose, requires prior U.S. Government authorization.




3

REVISION AND HISTORY

Revision No.

Change No. Description Release

Date

Draft N/A Draft GLS requirements document provided with the GLS draft Request For Proposals (RFP)

June 14, 2019




4

TABLE OF CONTENTS

1.0 Introduction ................................................................................................................................. 9 1.1 Scope And Purpose ................................................................................................................ 9 1.2 Overview ................................................................................................................................. 9 1.3 Mission Phases and Operations ........................................................................................... 10 1.4 Ground Rules And Assumptions ........................................................................................... 10 1.5 Change Authority/Responsibility ........................................................................................... 10 1.6 Convention and Notation ....................................................................................................... 10

2.0 Documents ................................................................................................................................ 12 2.1 Applicable Documents .......................................................................................................... 12 2.2 Reference Documents .......................................................................................................... 12 2.3 Order of Precedence ............................................................................................................. 13

3.0 Logistics Requirements ................................................................................................................... 14 L3-GLS-0000 Requirement Title ............................................................................................... 14

3.01 Overview and Description ......................................................................................................... 14 3.02 Logistics Services & System Capabilities ................................................................................. 15

L3-GLS-0011 Gateway Logistics Delivery Location ................................................................. 15 L3-GLS-1002 Pressurized Mass Delivery ................................................................................. 15 L3-GLS-1003 Unpressurized Mass Delivery ............................................................................. 15 L3-GLS-1004 Robotic Arm System Delivery ............................................................................. 16 L3-GLS-1111 Robotic Arm Walk-Off ......................................................................................... 16 L3-GLS-1008 Disposal Transportation ..................................................................................... 16 L3-GLS-1074 Trash Stowage ................................................................................................... 16 L3-GLS-1104 Logistics Module Life .......................................................................................... 17 L3-GLS-1005 Uncrewed Operations ......................................................................................... 17 L3-GLS-1105 Trash Disposal ................................................................................................... 17 L3-GLS-1106 Maximum System Docking Mass ....................................................................... 18

3.03 Autonomy And Docking ............................................................................................................. 19 L3-GLS-0013 Autonomous Gateway Docking .......................................................................... 19 L3-GLS-1114 RPOD Time-Critical Commands ........................................................................ 19 L3-GLS-1001 Active Docking System ....................................................................................... 19 L3-GLS-1012 Rendezvous, Proximity Operations, and Docking Role ..................................... 20 L3-GLS-1023 Logistics Module Flight Software Updates ......................................................... 20 L3-GLS-1028 Docked Autonomous Operations ....................................................................... 20 L3-GLS-1034 RPOD Data Exchange Communication ............................................................. 21 L3-GLS-1050 Docking System ................................................................................................. 21

3.04 Habitable Volume ...................................................................................................................... 22 L3-GLS-0025 Fire Detection, Isolation, and Suppression ........................................................ 22 L3-GLS-0032 Habitable Volume for Payload, Cargo, and Trash Transfer Operations ............ 22 L3-GLS-1042 Habitable Volume Atmosphere Trace Gas Concentrations ............................... 22 L3-GLS-1047 Habitable Volume Atmosphere Remote Evaluation ........................................... 23 L3-GLS-1053 Habitable Volume Atmospheric Leak Detection ................................................. 23 L3-GLS-1055 Habitable Volume Maximum Operating Pressure .............................................. 23




5

L3-GLS-1056 Habitable Volume Atmosphere Pressure Range ............................................... 23 L3-GLS-1057 Habitable Volume Atmosphere Leakage Limits ................................................. 24 L3-GLS-1099 Habitable Volume Particulate Limits .................................................................. 24 L3-GLS-1102 Habitable Volume Atmosphere Circulation ........................................................ 24 L3-GLS-1103 Condensation Prevention ................................................................................... 25

3.05 Crew Accommodations ............................................................................................................. 26 L3-GLS-0034 Crew Safety Equipment Interfaces ..................................................................... 26 L3-GLS-1066 Crew Hatch Requirements ................................................................................. 26 L3-GLS-1069 Human System Requirements (HSR) ................................................................ 26 L3-GLS-1095 Crew Displays and Controls Interface ................................................................ 27

3.06 Payloads And Cargo ................................................................................................................. 28 L3-GLS-1075 Gateway Inventory Management System (IMS) Interface ................................. 28 L3-GLS-1077 Unpressurized Cargo and Payload Power and Command and Data Handling . 28 L3-GLS-1079 Mission-Specific Unpressurized Cargo and Payload Services & Interfaces ...... 28 L3-GLS-1080 Cargo Transfer Bags .......................................................................................... 29 L3-GLS-1081 Mission-Specific Bag Stowage System .............................................................. 29 L3-GLS-1082 Middeck and Double-Middeck Lockers .............................................................. 29 L3-GLS-1083 Mission-Specific Mounted Cargo and Payload System ..................................... 30 L3-GLS-1085 Pressurized Cargo and Payload Late Load Capability ...................................... 30 L3-GLS-1086 Unpressurized Cargo and Payload Launch and Transportation Environment ... 30

3.07 Docked Operations And Interfaces ........................................................................................... 32 L3-GLS-0022 Docked Module Ventilation ................................................................................. 32 L3-GLS-1014 21 Day Data Storage .......................................................................................... 32 L3-GLS-1015 Gateway Control of Logistics .............................................................................. 32 L3-GLS-1016 Redundant Time-Triggered Ethernet ................................................................. 33 L3-GLS-1027 Data Prioritization ............................................................................................... 33 L3-GLS-1033 Docked Data Exchange with Vehicle System Manager ..................................... 33 L3-GLS-1036 Remote Capability .............................................................................................. 34 L3-GLS-1046 Vestibule De-Pressurization ............................................................................... 34 L3-GLS-1051 Transfer Passageway Diameter ......................................................................... 34 L3-GLS-1107 Non-Propulsive Venting ...................................................................................... 34

3.08 Power ........................................................................................................................................ 35 L3-GLS-0005 Power To Payloads ............................................................................................ 35 L3-GLS-0021 Power Independence While Docked .................................................................. 35 L3-GLS-1011 Contingency Docked Power Interface ................................................................ 35

3.09 Communications ....................................................................................................................... 37 L3-GLS-0033 Intermodular Crew Voice Communications ........................................................ 37 L3-GLS-1021 Gateway Wireless Network Coverage ............................................................... 37 L3-GLS-1026 Caution and Warning Notifications ..................................................................... 37 L3-GLS-1031 Visiting Vehicle Phase Spectrum Regulatory Compliance ................................. 38 L3-GLS-1032 Transit Phase Spectrum Regulatory Compliance .............................................. 38 L3-GLS-1035 Logistics Module and Payload Data During Transit ........................................... 38 L3-GLS-1100 Critical Event Telemetry ..................................................................................... 38

3.10 Structure .................................................................................................................................... 40 L3-GLS-1058 Structural Health Monitoring ............................................................................... 40

3.11 Natural & Induced Environments .............................................................................................. 41




6

L3-GLS-0008 Payloads Induced Environment Isolation ........................................................... 41 L3-GLS-0024 Pressurized Payload Environments While Docked ............................................ 41 L3-GLS-1010 Natural Space Environment ............................................................................... 41 L3-GLS-1017 Critical Systems Survival at Vacuum ................................................................. 42 L3-GLS-1040 Uncrewed Temperature Range .......................................................................... 42 L3-GLS-1043 Low Humidity Operation ..................................................................................... 42 L3-GLS-1060 Micrometeoroid Debris PNP ............................................................................... 42 L3-GLS-1071 Intervehicular Activity Limit Loads ...................................................................... 43 L3-GLS-1087 Ground Handling and Transportation Environment............................................ 43 L3-GLS-1094 Minimum Lunar Distance .................................................................................... 43 L3-GLS-1096 Gateway Docking System Docking Limit Loads ................................................. 44 L3-GLS-1098 Maximum Oxygen Concentration Nominal Total Pressure ................................ 45 L3-GLS-1041 Maximum Oxygen Concentration Low Pressure ................................................ 45 L3-GLS-1108 Gateway Solar Array and Radiator Wing Maximum Normal Peak Plume Pressures .................................................................................................................................. 45 L3-GLS-1109 Gateway Surfaces Maximum Normal and Shear Plume Pressures .................. 45

3.12 Safety ........................................................................................................................................ 47 L3-GLS-1018 Logistics Module Tolerate Inadvertent Operation Action ................................... 47 L3-GLS-1044 Emergency Equipment Accessibility .................................................................. 47 L3-GLS-2001 Logistics Module Critical Hazards ...................................................................... 47 L3-GLS-2002 Logistics Module Catastrophic Hazards ............................................................. 47 L3-GLS-2003 Logistics Module Failure Tolerance Without Emergency Equipment................. 48 L3-GLS-2004 Logistics Module Autonomous Operation .......................................................... 48 L3-GLS-2005 Logistics Module Reliability ................................................................................ 48 L3-GLS-2006 Logistics Module Redundancy Design ............................................................... 49 L3-GLS-2009 Hazard Analysis ................................................................................................. 49 L3-GLS-2011 Operational Hazard Controls .............................................................................. 49 L3-GLS-2052 Logistics Module Crew Manual Override ........................................................... 49 L3-GLS-2053 Logistics Module Inhibit Monitoring .................................................................... 49 L3-GLS-2057 Logistics Module Deployable End Item Inhibit Monitoring ................................. 50 L3-GLS-2063 Logistics Module Health and Status Measurement Redundancy ...................... 50 L3-GLS-2066 Logistics Module Computer Initiated Hazards and Controls .............................. 50 L3-GLS-2067 Logistics Module CBCS Safe Initialization ......................................................... 50 L3-GLS-2068 Logistics Module CBCS Orderly Shutdown ........................................................ 50 L3-GLS-2069 Logistics Module Safe Operation during Off-Nominal Power ............................. 50 L3-GLS-2070 Logistics Module Overrides by Operators .......................................................... 51 L3-GLS-2071 Logistics Module Out of Sequence Command Rejection ................................... 51 L3-GLS-2072 Logistics Module Inadvertent Memory Modification ........................................... 51 L3-GLS-2073 Logistics Module CBCS Validation of External Inputs ....................................... 51 L3-GLS-2074 Logistics Module CBCS Integrity Checks ........................................................... 51 L3-GLS-2075 Logistics Module CBCS Prerequisite Checks .................................................... 51 L3-GLS-2076 Logistics Module Disabling of Arming Commands ............................................. 52 L3-GLS-2077 Logistics Module CBCS Two Unique Commands to Deactivate Catastrophic Hazard Control .......................................................................................................................... 52 L3-GLS-2079 Logistics Module Unique Command Messages to Remove or Change State of an Inhibit .................................................................................................................................... 52 L3-GLS-2081 Logistics Module Detection and Safing within Time to Effect ............................ 52




7

L3-GLS-2082 Logistics Module Manual Safing Data ................................................................ 52 L3-GLS-2113 Logistics Module Electromagnetic Effect Safety Margin when Demonstrated by Test ........................................................................................................................................... 53 L3-GLS-2114 Logistics Module Electromagnetic Effect Safety Margin when Calculated by Analysis ..................................................................................................................................... 53 L3-GLS-2117 Logistics Module Isolation for Users of Direct Current ....................................... 53 L3-GLS-2118 Logistics Module DC Isolation of Isolated Power Sources ................................. 53 L3-GLS-2119 Logistics Module Circuit Conductors DC isolation ............................................. 53 L3-GLS-2120 Logistics Module Mechanism State Indication for Hazard Control ..................... 54 L3-GLS-2121 Logistics Module Hatchway Drag-Throughs ...................................................... 54 L3-GLS-2122 Logistics Module Critical Seals with Major Outer Diameter Less than 0.5 Inches .................................................................................................................................................. 54 L3-GLS-2123 Logistics Module Critical Seals with Major Outer Diameter Greater than 0.5 Inches ........................................................................................................................................ 54 L3-GLS-2124 Logistics Module Critical Seals with Major Outer Diameter Greater than 6 Inches .................................................................................................................................................. 54 L3-GLS-2125 Logistics Module Colocation of Tools and Devices for Hatch Operation. .......... 54 L3-GLS-2126 Logistics Module Visual Inspection .................................................................... 55 L3-GLS-2129 Logistics Module Hatch Inadvertent Opening Prevention .................................. 55 L3-GLS-2131 Logistics Module Safe Recovery ........................................................................ 55 L3-GLS-2132 Logistics Module Tolerate Inadvertent Operation Action During Failure ........... 55 L3-GLS-2133 Logistics Module Controls for Human Error ....................................................... 55

3.13 Design & Construction .............................................................................................................. 56 L3-GLS-1113 Material Offgassing ............................................................................................ 56 L3-GLS-3010 Fluid Standard .................................................................................................... 56 L3-GLS-3012 Internal Cleanliness ............................................................................................ 56 L3-GLS-3013 External Cleanliness ........................................................................................... 56

TBDs AND TBRs ........................................................................................................... 58 A.1 Scope ........................................................................................................................................ 58 A.2 List of TBDs ............................................................................................................................... 58 A.3 List of TBRs ............................................................................................................................... 58

Glossary ........................................................................................................................ 60




8

TABLE OF FIGURES No table of figures entries found.




9

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 baseline capabilities needed to accomplish resupply 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.

The scope of the requirements in this document is limited to defining a Logistics service that implements the Gateway mission concept documented in the baseline revision of DSG-CONOP-001 Gateway Concept of Operations, and the draft DSG-RQMT-001 Gateway System Requirements allocated to the Logistics Element contained in DSG-RQMT-001 Gateway System Requirements. Section 3.0 of this document contains the requirements for the Gateway Logistics Services Contract.

1.2 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 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 a southerly NRHO at the Moon. It provides an interior 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 end-of-life mission items by the Gateway crew, the LM will autonomously depart the Gateway and transport itself to a disposal orbit.

Each baseline Gateway Logistics mission has two primary objectives during the Gateway assembly and outfitting phase:

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

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

Critical LM capabilities which enable those objectives are:

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

2. The ability to remain docked at the Gateway, without relying on Gateway crew or utilities for power, environmental control, or thermal control, for a period of up to three years.




10

1.3 MISSION PHASES AND OPERATIONS

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

1.4 GROUND RULES AND ASSUMPTIONS

GR&A1 These requirements do not specifically address Logistics missions flown as co-manifested payloads (CPL) on the Space Launch System (SLS) with Orion. CPL mission-unique requirements will be specified on a per-mission basis via GLS contract mechanisms.

GR&A2 Logistics Modules support Gateway crew presence when docked, but will not provide complete environmental control for crew habitability independent of the Gateway.

GR&A3 A single Logistics Module may support up to two 30-day crew visits within its docked 3-year life.

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.




11

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.




12

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 DSG-RQMT-001 Gateway Systems Requirements DSG-RQMT-002 Gateway Human Systems Requirements Volumes 1 and 2 DSG-RQMT-011 Gateway Program Hazard Analysis Requirements DSG-SPEC-MECH-017 Gateway Docking System Specification (GDSS)

JSC 20584 Spacecraft Maximum Allowable Concentrations for Airborne Contaminants

SSP 50833 International Space Station Program Cargo Transport Interface Requirements Document

DSG-SPEC-PWR-011 Gateway Program Subsystem Specification for Power DSG-SPEC-AV-004 Gateway Program Subsystem Specification for Avionics DSG-SPEC-COMM-005 Gateway Program Subsystem Specification for COMM SLS-SPEC-159 Cross-Program Design Specification for Natural Environments

MPCV 70156 Cross-Program Fluid Procurement and Use Control Specification

IEST-STD-CC1246E Product Cleanliness Levels

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

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 DSG-PLAN-009 Integrated Verification & Validation (V&V) Plan DSG-ADD-001 Gateway Architecture Definition Document DSG-ADD-005 Gateway Integrated Performance Assessment DSG-ANA-001 Gateway Interface Requirements and Functional Allocations DSG-CONOP-001 Gateway Concept of Operations IDSS International Docking System Standard

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

DSG-SPEC-AV-004 Gateway Program Subsystem Specification for Avionics DSG-SPEC-COMM-005 Gateway Program Subsystem Specification for COMM DSG-SPEC-CS-006 Gateway Program Subsystem Specification for Crew Systems DSG-SPEC-ECLSS-007 Gateway Program Subsystem Specification for ECLSS




13

Document Number Rev Document Title DSG-SPEC-HTCH-019 Gateway Program Subsystem Specification for Hatches

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

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

DSG-SPEC-PWR-011 Gateway Program Subsystem Specification for Power

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

DSG-SPEC-FSW-014 Gateway Program Subsystem Specification for Software DSG-SPEC-THR-015 Gateway Program Subsystem Specification for Thermal DSG-SPEC-IMG-016 Gateway Program Subsystem Specification for Imagery

SSP 51075 NASA Docking System Block 2 (DSB2) Interface Definition Document

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

SSP 50005 International Space Station Flight Crew Integration Standard MAPTIS NASA Material Selection Database

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.




14

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.

Requirements are presented in the following format:

L3-GLS-0000 Requirement Title

Requirement Text Rationale: Requirement Rationale

Derived From/Parent Requirement:

Parent-Number-0000 Parent Requirement Title

3.01 OVERVIEW AND DESCRIPTION

The requirements herein focus on the minimum set of key performance and interface requirements that are common across all Logistics Missions to the Gateway, for Phase 1 of the Gateway Program. As Gateway assembly progresses, new needs or capabilities are implemented by sequential Logistics missions. Additional requirements will be established on a per-mission basis as needed. The contract mechanism for the Logistics Service will augment these key performance requirements to cover any mission-specific needs. Some requirements have been removed due to the phase 1 and phase 2 distinctions, and will be addressed as the capability becomes present at the Gateway stack (e.g. Inter-Vehicular Robotics (IVR) and Extravehicular Activity (EVA) requirements). 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.




15

3.02 LOGISTICS SERVICES & 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.


L2-LM-0008 Rendezvous location

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 baseline Gateway Logistics Mission (see GM-3 and GM-6 in DSG-CONOP-001). The capability to deliver mass above the upper limit may provide additional capability to the Gateway. In the event that NASA does not utilize the entire capability of the Logistics service mission, the provider may request to use the remainder of the service mission to meet provider objectives or fly non-NASA cargo & payloads.


L2-LM-0198 Logistics Resupply

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 mass required for a baseline Gateway Logistics Mission (see GM-3 and GM-6 in DSG-CONOP-001) to deliver cargo and payloads to sustain operations during the assembly phase. The delivery of a Robotic Arm may exceed this minimum, and is not considered a baseline mission. The capability to deliver greater than this mass per mission may provide additional capability to the Gateway. In the event that NASA does not utilize the entire capability of the Logistics service mission, the contractor may request to use the remainder of the service mission to meet contractor objectives or fly non-NASA cargo and payloads.


L2-LM-0002 Unpressurized Mass Delivery




16

L3-GLS-1004 Robotic Arm System Delivery

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

Rationale: A Robotic Arm may be delivered as part of one of the Logistics missions to the Gateway. It may be delivered in conjunction with a Logistics Module or it may be delivered as a separate, stand-alone, mission. A Robotic Arm system specification and Interface Requirements Document will be provided which will define the arm and Logistics functional, logical, and physical interfaces (e.g. power, thermal control, data, software execution, induced environments, release mechanisms, and commanding)


L2-LM-0003 External Robotics Delivery

L3-GLS-1111 Robotic Arm Walk-Off

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

Rationale: The Robotic Arm delivery mission concept of operations requires that the arm have the power, data, and computational resources necessary to activate and deploy itself from the Logistics Module (or other system provided by the GLS provider) and onto the Gateway. It is anticipated that these capabilities will augment the baseline logistics mission and will be captured in mission-specific external payload interface documentation such as an IRD or ICD.


L2-LM-0003 External Robotics Delivery

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. 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-LM-0164 LM Disposal

L3-GLS-1074 Trash Stowage

The Logistics Module shall provide a storage system within the habitable volume including 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




17

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 properly contained, trash containers will be transferred to the Logistics Module for long term stowage and disposal, when the LM departs the Gateway.


L2-LM-0024 Trash Accommodation

L2-LM-0220 Metabolic Waste Management

L3-GLS-1104 Logistics Module Life

The Logistics Module shall operate for a minimum of three years while docked to Gateway. Rationale: Logistics missions are expected to support two crewed visits to Gateway per Logistics mission (exclusive of non-cargo missions delivering a Gateway element like the external arm). A three-year Logistics docked life supports a Gateway crew flight rate of one flight per year, includes a Logistics docked time of up to three months prior to crew arrival, and supports a maximum crewed duration of up to 90 <TBD-007> days per mission, with margin.

Requirement Owner:


L2-LM-0112 Uncrewed Operations

L3-GLS-1005 Uncrewed Operations

The Logistics Module shall satisfy docked operational life requirements without support from a Gateway crew.

Rationale: 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. Three continuous years covers the required docked service life of a Logistics mission space element.


L2-LM-0112 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-LM-0024 Trash Accommodation




18

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,865 lb). <TBR-010>

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.




19

3.03 AUTONOMY AND DOCKING

Upon arrival in cislunar space and entry into the 10km radius 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.

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-LM-0011 Autonomous Docking/Berthing

L2-LM-0043 RPOD Sensors

L2-LM-0117 Independent Docking

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): The 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 mission 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.

Requirement Owner:


L2-LM-0011 Autonomous Docking/Berthing

L3-GLS-1001 Active Docking System

The Logistics Module shall have an active docking system.




20

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.


L2-LM-0178 Active Docking Mechanisms

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.


L2-LM-0178 Active Docking Mechanisms

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-LM-0269 FSW Updates

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-LM-0161 Independent Operations




21

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-LM-0211 Comm Subsystem Specification

L2-LM-0272 Data Transport

L3-GLS-1050 Docking System

The Logistics Module docking system shall comply with the Gateway Docking System (GDS) 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.


L2-LM-0282 Standard Docking Port




22

3.04 HABITABLE VOLUME

L3-GLS-0025 Fire Detection, Isolation, and Suppression

The Logistics Module shall detect, isolate, and suppress fires within the habitable volume. Rationale: Each Gateway habitable element, including the Logistics habitable volume, is to include an independent fire detection, isolation, and suppression system.


L2-LM-0252 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. Allocated requirements for the LM habitable volume will be provided in DSG-RQMT-002 Volume 1, Gateway Human-System Requirements (HSR) and DSG-RQMT-002 Volume 2, Gateway Human-System Requirements (HSR) for Subsystem Specifications. Habitable volume requirements for lighting are governed by DSG-SPEC-AV-004, Gateway Program Subsystem Specification for Avionics.


L2-GW-0213 Crew Tasks Volumes

L2-LM-0190 HSR

L2-LM-0191 Spacecraft Lighting

L2-LM-0212 Shirt Sleeve Environment

L2-LM-0214 Environmental Hazards

L2-LM-0215 Crew Tasks Volumes

L3-GLS-1042 Habitable Volume Atmosphere Trace Gas Concentrations

Prior to crew hatch opening, the trace gas concentrations in the Logistics Module habitable volume shall be within the values specified in the following documents, in order of precedence:

1. SMAC JSC 20584

2. Materials and Processes Technical Information System (MAPTIS)

Rationale: Trace gases are added to the atmosphere through normal off-gassing from system surfaces. This requirement ensures a safe environment for crew before hatch opening, and prevents contamination of the Gateway environment. Joint outgassing/contamination with NASA cargo should also be considered. Specific capabilities and limits will be further defined in DSG-SPEC-ECLS-007, Gateway Program Subsystem Specification for ECLSS.


L2-LM-0219 Atmosphere Contamination Removal




23

L3-GLS-1047 Habitable Volume Atmosphere Remote Evaluation

The Logistics Module shall report the conditions of the habitable volume atmosphere gas remotely to verify safe conditions prior to opening the hatch between the habitable volume and the Gateway.

Rationale: Heritage commercial space resupply systems' atmospheres can be sampled and verified safe for humans prior to launch. Due to short launch and transit times, the preflight samples are generally representative of the expected on-orbit environment. Gateway Logistics missions may have lengthy transit times (as long as several weeks) and may be docked at the Gateway for several months prior to first hatch opening and ingress of crew. Given this extended mission time, the ability to evaluate the habitable volume air quality on-orbit, prior to opening the crew hatch, is necessary to protect the Gateway crew from exposure to built-up atmospheric contaminants.

L3-GLS-1053 Habitable Volume Atmospheric Leak Detection

The Logistics Module shall detect habitable volume atmosphere leaks greater than 0.01 kg (0.022 lbm) per day at 101.3 kPa (14.7 psi absolute).

Rationale: Detection of leaks will allow for quick response and repair by the crew, in the event of an atmospheric leak, during crewed periods or autonomously during uncrewed periods.


L2-LM-0173 Atmospheric Leak Detection

L3-GLS-1055 Habitable Volume Maximum Operating Pressure

The Logistics Module habitable volume maximum operating pressure shall be at least 105 kPa (15.2 psid).

Rationale: When crewed, the Gateway will be nominally maintained at pressures near to Earth sea level 101 kPa (14.7 psi). The full range allows for operational flexibility during crewed and uncrewed periods, including response to contingency scenarios and potential reduction of consumables during uncrewed periods. Further specification may be found in DSG-SPEC-ECLS-007, Gateway Program Subsystem Specification for ECLSS.


L2-LM-0247 Minimum MDP

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

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-




24

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


L2-LM-0218 Total Pressure Range

L3-GLS-1057 Habitable Volume Atmosphere Leakage Limits

The LM shall limit atmosphere leakage to less than 0.01 kg/day while docked to the Gateway <TBR-L2-GW-010>.

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 gasses may run out. This is a particular concern during the long duration uncrewed mission phases.


L2-LM-0227 Atmosphere Leakage

L3-GLS-1099 Habitable Volume Particulate Limits

The Logistics Module shall limit the average atmosphere particulate level to 100,000 particles per cubic foot with peak concentrations less than 2 million particles per cubic foot for particles greater than 0.5 microns in size.

Rationale: Particulates are generated by both the crew and the surfaces and items within the habitable volume, and if not controlled, may lead to crew discomfort or injury. This requirement is primarily required during the crewed period, though uncrewed utilization may drive additional capability. Specific requirements will be further defined and allocated to the LM in the ECLS Subsystem Specification.


L2-LM-0219 Atmosphere Contamination Removal

L3-GLS-1102 Habitable Volume Atmosphere Circulation

The Logistics Module shall circulate the habitable volume atmosphere to prevent the formation of oxygen deficient pockets of air while docked to the Gateway, with the crew hatch in the open or closed position.

Rationale: If adequate ventilation is not provided, heat, moisture, and CO2 given off by Crew and equipment will lead to parameters outside the bounds of environmental requirements. Maintaining proper ventilation within the internal atmosphere is necessary to ensure that stagnant pockets do not form, and the temperature, humidity, and atmospheric constituents are maintained within their appropriate ranges inside the LM. If a minimum internal circulation requirement is needed, it must be contained in a Commercial Visiting Vehicle Requirements Document or it may be provided by referencing the applicable requirements in Gateway Level 2 requirements documents.

Requirement Owner:




25

L3-GLS-1103 Condensation Prevention

The Logistics Module shall control the dew point temperature of the atmosphere to be below the internal wall and surface temperatures of the habitable volume.

Rationale: During crewed operations, the dew point will remain within crew comfort levels. During the uncrewed period, the cabin may be very dry with a dew point less than 4C (39F) at lowest allowable temperature. Humidity may be removed purposefully to prevent condensation and microbial growth. The humidity will passively be reduced as the pressure is maintained with dry gasses and no crew is present to replenish atmospheric vapor. Appropriate design of electronics must be included to control electrostatic discharge (ESD) hazards. Design Specifications to minimize risk of ESD may be found in DSG-RQMT-004 and DSG-RQMT-007.

Requirement Owner:


L2-LM-0223 Uncrewed Dry Cabin Atmosphere

Derived/Child Level 3 Requirement(s):





26

3.05 CREW ACCOMMODATIONS

L3-GLS-0034 Crew Safety Equipment Interfaces

The Logistics Module habitable volume shall provide attach points and interfaces to accommodate crew safety equipment (including portable fire extinguishers and emergency breathing apparatus)

Rationale: Gateway safety equipment may be transported to Gateway as cargo, but must be un-packed and stowed in an easily accessible location after initial crew ingress and in support of later logistics activities. DSG-SPEC-ECLSS-007 will provide specific instruction on accommodating the emergency equipment assigned to the module.


L2-LM-0254 Emergency Equipment Accommodation

L3-GLS-1066 Crew Hatch Requirements

The Logistics Module shall have a crew hatch compliant with hatch requirements for crew in DSG-RQMT-002 Vol2, Gateway Human-System Requirements (HSR) for Subsystem Specifications.

Rationale: In addition to the HSR crew hatch requirements, the provider should consider compliance with DSG-SPEC-HTCH-019, Gateway Program Subsystem Specification for Hatches. Hatches are essential structures for vehicle function during transit and when docked to other Gateway modules. Hatch design must address usability not only for efficient operation by crew members but to ensure crew safety during nominal and contingency operations. Hatch operation includes unlatching/opening or closing/latching the hatch. Safety considerations include isolation of the vehicle from other vehicles in an emergency (e.g. depress, fire, toxic spill, etc.). Therefore, hatches should be capable of operation from both sides; operation by one crew member; operation in no more than 60 seconds; operation without the use of tools; manual pressure equalization from the inside and outside of the hatch; providing direct pressure difference measurements on the inside and outside; and enabling visual inspection of the adjacent volume through a closed hatch. To promote usability of hatches, designers should consider providing indications of pressure and temperature to the crew prior to opening a hatch; indication of open or closed status; preventing inadvertent opening prior to complete pressure equalization; and ensuring hatch covers allow for unrestricted flow of traffic.


L2-LM-0216 Hatches

L3-GLS-1069 Human System Requirements (HSR)

The Logistics Module shall comply with human system requirements allocated 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 a mission. Any activity that involves the human must meet the human factors, habitability, and environmental health requirements in DSG-RQMT-002 HSR, which are tailored from NASA-STD-3001, Volume 1 and Volume 2, as required by NPR 8705.2C for human rating of space systems. Requirements specifically allocated to the Logistics Module for implementation will be specified in these volumes.





27

L2-LM-0190 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-LM-0040 Crew Displays and Controls




28

3.06 PAYLOADS AND CARGO

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


L2-LM-0152 Unobstructed Autonomous Inventory Management

L2-LM-0263 Stowage System

L3-GLS-1077 Unpressurized Cargo and Payload Power and Command and Data Handling

For external cargo and payloads that require power or data connections/transmission, the Logistics Module shall provide electrical power and command and data handling capabilities which also meet the electromagnetic emission and susceptibility constraints as specified for unpressurized cargo interfaces in SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document, Sections 3.2.3.4.1, 3.2.3.5 and 3.2.3.6.

Rationale: By providing external power and command and data handling capabilities equivalent to the existing unpressurized cargo interfaces used by ISS, existing external payloads can be accommodated without modification, and new external payload cargo can be developed and transported to the Gateway without modification and recertification.


L2-LM-0113 Utilization Resources

L2-LM-0195 Services to Robotically Compatible External Equipment

L3-GLS-1079 Mission-Specific 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 directly mounted to the exterior of the Logistics Module.

Rationale: Specialized, mission specific, payloads that cannot be transported on a Small Orbital Replacement Unit (SORI) based system, or externally-mounted payloads that are not intended for removal from the Logistics Module, may be directly mounted to an exterior site on the unpressurized volume of the Logistics Module, or to an alternative external adapter interface that may include alternative physical interfaces for electrical or data connections. This requirement is intended to allow the Logistics Module to transport external, unpressurized cargo that use alternate physical interfaces for structural, electrical or data connectors or an alternative attachment/release mechanism other than the SORI-based system. This requirement is also intended to allow the Logistics Module to transport permanently-mounted external cargo, such as




29

pressurized tanks of gases or fuel, which may be transferred to the Gateway through hoses or by other means.



L2-LM-0195 Services to Robotically Compatible External Equipment

L3-GLS-1080 Cargo Transfer Bags

The Logistics Module habitable volume shall provide structural mounting, stowage, and strapping interfaces to transport standard ISS Cargo Transfer Bags (CTB) and Multi-purpose Logistics Module Bags (M-BAG) using the maximum bag dimensions, mass properties and strapping interfaces defined in SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document, Sections 3.1.2.1 and 3.1.2.2.

Rationale: This requirement specifies the standard existing structural and strapping interfaces to the CTB and M-BAG cargo transport systems for ISS. Ground and on-orbit stowage processes are currently in place to support the ISS to ensure CTBs and M-BAGs are packed within current mass property limits. Development of a new cargo transfer bag system would impact ground and flight operations. By providing interfaces that will support the currently approved strapping/stowage concepts, existing bags can be accommodated, packed, stowed and strapped with cargo and payloads for transport to the Gateway without modification and recertification.


L2-LM-0167 Standard Payload Accommodation Interfaces

L3-GLS-1081 Mission-Specific Bag Stowage System

The Logistics Module habitable volume shall provide structural mounting, stowage and strapping interfaces for a NASA-approved mission-specific bag stowage system.

Rationale: An alternate stowage bag and strapping interface design, which meets all other requirements, can be reviewed and approved for use by NASA, depending on the impact to the environments the bags will experience (e.g. loads, random vibration) and depending on the impact to packing and unpacking requirements and processes for ground crews or for crew or IVR systems at the Gateway. This provides flexibility to introduce new bag sizes, types, mass properties and strapping interfaces for transport of cargo and payloads to the Gateway.



L3-GLS-1082 Middeck and Double-Middeck Lockers

The Logistics Module habitable volume shall provide structural, electrical, command and data handling, telemetry and thermal interfaces to transport standard Middeck Locker (MDL) and Double Middeck Locker (Double MDL) cargo and payloads with the interfaces and payload mass properties, orientation constraints, environmental parameters and cleanliness requirements as specified in SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document, Section 3.1.1.

Rationale: By providing structural, power, thermal, data and environmental interfaces that support the standard existing MDL transport requirements for ISS, existing MDLs can be accommodated without modification and new MDLs can be developed for delivery to the Gateway without modification and recertification. Not all MDL or double MDL payloads will require




30

continuous power, data or thermal control during transit and/or during the docked phase of operations onboard the Logistics Module. Standard MDL or double MDL payloads that do not require power during transit can also be flown in stowage systems for unpowered passive transport. Power, data and thermal control for payloads during the disposal phase of the Logistics Mission is expected to be limited.



L3-GLS-1083 Mission-Specific Mounted Cargo and Payload System

The Logistics Module habitable volume shall provide structural, electrical, command and data handling, telemetry and thermal interfaces to transport NASA-approved mission-specific cargo and payloads that are structurally mounted within the habitable volume.

Rationale: Specialized, mission specific, payloads that cannot be transported in a certified passive stowage system, or as a single or double MDL with standard interfaces, may be directly mounted to the Logistics Module, to a plate, or to another structural interface that is directly mounted to the Logistics Module within the habitable volume. This requirement allows the Logistics Module to transport odd-sized or irregularly-shaped hardware that cannot conform to the CTB, M-Bag, or MDL cargo transport requirements. This requirement also allows the Logistics Module to transport hardware that uses alternative interfaces at the Gateway other than the MDL interfaces. This requirement also allows the Logistics Module to transport permanently-mounted cargo or payloads, such as water tanks or pressurized tanks of gases, which may transfer commodities through hoses or by other means to the Gateway.



L3-GLS-1085 Pressurized Cargo and Payload Late Load Capability

When requested by NASA, the provider shall load no less than 10 percent (by mass) of the non-powered cargo, and additionally no less than 4 MDL or MDL-equivalent powered payloads at no less than 7 <TBR-017> days before launch.

Rationale: Changes to the cargo and payload manifest may occur close to the launch date. Additionally, some cargo (e.g., batteries, perishable items, or limited-life science payloads) may require late loading to preserve viability and functionality. Although nominal Logistics Service Missions may take several months to deliver cargo, express services may take less than a week. This requirement is consistent with the late loading of passive cargo to ISS practices, as specified in SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document, and it establishes a minimum late load capacity for powered payloads that is within the nominal late load requirements for powered payloads defined for CRS-2 providers. Very late load capabilities at L-24 hours or less are not anticipated for Logistics Missions that require more than 2 weeks for transit to NRHO.


L2-LM-0144 Late Load Capability

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

From handover to the provider through prelaunch, launch, and transit mission phases, the Logistics services provider shall control the exposure of unpressurized cargo and payloads to the acoustic, shock, pressure decay, thermal and contamination constraints defined in




31

SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document rev. B, Section 3.2.3.8

Rationale: By controlling launch and transportation environmental exposure for unpressurized cargo and payloads to levels equivalent to the existing constraints used by ISS, existing external payload cargo can be accommodated and transported without modification, and new external payload cargo can be developed and transported to the Gateway without modification and recertification.




32

3.07 DOCKED OPERATIONS AND INTERFACES

L3-GLS-0022 Docked Module Ventilation

The Logistics Module shall send filtered forced air to the docked Gateway module when docked to the Gateway when both Gateway and LM hatches are open.

Rationale: Air exchange between the LM and the Gateway will be via a forced air positive-pressure duct interface installed by the crew, with return air via the open hatches between two adjacent modules. Intermodule air exchange duct interfaces will be specified by Gateway-to-Logistics Interface Control Documentation. Gateway ECLS system specifications governing Logistics and Gateway air exchange will be documented in DSG-SPEC-ECLS-007.


L2-LM-0264 Intermodule Ventilation

L3-GLS-1014 21 Day Data Storage

The Logistics Module shall store a minimum of 21 days of LM and hosted payload health and status data.

Rationale: Lunar and Mars Gateway mission profiles may include periods of poor or no communications with the ground for up to 21 days. During these periods, a store-and transmit method of data management is desired to prevent the loss of mission data.


L2-LM-0039 Data Storage

L3-GLS-1015 Gateway Control of Logistics

Logistics Module systems shall respond to command and control instructions from the Gateway while docked.

Rationale: Coordinated control is needed at the Gateway vehicle level. The LM is designed to be self-sufficient, even while docked at the Gateway. However, the LM must maintain the ability to respond to Gateway commands received from Habitation Element Temperature Control System, Pressure Control System, Oxygen Control System, Ventilation System, Fire Safety System, as specified in DSG-SPEC-ECLS-007, Gateway Program Subsystem Specification for ECLS System when required. Additional details are needed to specify the minimum Gateway command and control requirements for the LM, including requirements for payloads, during the docked phase. These may be contained in a Commercial Visiting Vehicle Requirements Document or may be provided by referencing the applicable requirements in Gateway Level 2 requirements documents. A Docked Phase Command and Control System Specification will be defined by the contractor and approved by NASA as part of an overall contractor Logistics Module User's Guide that will be made available for cargo and payloads planning.


L2-LM-0233 GNC Subsystem Specification

L2-LM-0235 Avionics Subsystem Specification

L2-LM-0236 ECLSS Subsystem Specification

L2-LM-0268 Remote Capability




33

L3-GLS-1016 Redundant Time-Triggered Ethernet

The Logistics Module shall interface with Gateway via a Time-Triggered Ethernet (TTE) network, on three planes, in accordance with DSG-SPEC-AV-004, Gateway Program Subsystem Specification for Avionics.

Rationale: Three separate network data interfaces will exist between the Gateway elements to implement TTE fault tolerance. Docking system umbilical Ethernet interfaces will be defined in the Gateway docking system specification and Interface Control Document(s).


L2-LM-0181 TTE Redundancy

L2-LM-0235 Avionics Subsystem Specification

L3-GLS-1027 Data Prioritization

The Logistics Module shall transmit curated system and payload health and status data and events to the Gateway in order of priority.

Rationale: Reduced bandwidth and lack of crew will challenge the situational awareness of ground operators. The Gateway VSM will manage the resource of bandwidth in order to provide the ground controllers with the best possible information. This will involve responding to priorities set by ground, crew, or events on board the Gateway. The curation of data at the Logistics Module will conserve limited processing and network resources.


L2-LM-0273 Data Prioritization

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

The Logistics Module shall exchange data and commands with the Gateway Vehicle System Manager (VSM) while docked.

Rationale: Vehicle System Manager (VSM) will be a system whose function is to manage the overall vehicle. As such, the VSM will need to interface with all modules and all systems. It is important that a common set of requirements exists to describe both the VSM itself as well as the interfaces to the VSM. Compliance with the DSG-SPEC-VSM-003 Gateway Program Subsystem Specification for Vehicle System Manager (VSM) will direct the controllability and compatibility of the Gateway and the VSM. Gateway communications with docked visiting vehicles allows for direct data transfer between the visiting vehicle and the gateway (including commands, telemetry, health & status, GN&C data, etc), thus allowing H&S data from the Logistics system to be viewed by Gateway crew and ground controllers. This extends to payloads as-needed for those that are powered and require data transmission while docked. The Gateway Avionics Subsystem Specification DSG-SPEC-AV-004 will contain requirements for visiting vehicles to participate in the integrated Command and Data Handling Time-Triggered Ethernet system that will be utilized across Gateway to ensure compatibility among all Elements/Modules. The Gateway Program Subsystem Specification for Command and Handling TTE Network will define the specific functionality required of the inter-module network system to enable top level capabilities, associated design standards, and module level functional and performance requirements.


L2-LM-0242 VSM Subsystem Specification





34

L3-GLS-1036 Remote Capability

The Logistics Module shall allow remote monitoring, operation and control of vehicle systems, where:

1. The remote capability is necessary to execute the mission; or

2. The remote capability would prevent a catastrophic event; or

3. The remote capability would prevent an abort.

Rationale: This capability will likely be implemented using a mission control on Earth. There will be long periods of time where a crew is not present on Gateway to monitor, operate, and control the system. If the crew vacates one module of the Gateway or transfers to another vehicle (e.g. Orion, Lunar Lander) as part of the reference mission, there needs to be a capability for humans to monitor the unoccupied Logistics Module. In some of these cases, the crew may be able to perform this function from their new location. In other cases, mission control may perform this function.


L2-LM-0268 Remote Capability

L3-GLS-1046 Vestibule De-Pressurization

The docked Logistics Module shall remotely de-pressurize the docking vestibule volume to space vacuum.

Rationale: The vestibule between the LM and the Gateway must be evacuated before the LM can undock and leave. For robustness, the Gateway ports which receive visiting vehicles will provide a redundant capability.

Requirement Owner:

L3-GLS-1051 Transfer Passageway Diameter

The Logistics Module shall have an 800 mm (31.5 in) minimum diameter transfer passageway between the LM-to-Gateway docking interface.

Rationale: GDS-compliant mechanisms only provide an 800mm diameter passageway for a distance of approximately 1.2 meters when mated. Items to be transferred between Gateway modules need to be sized appropriately.


L2-LM-0172 Transfer Passageway

L3-GLS-1107 Non-Propulsive Venting

Logistics Module venting events shall be non-propulsive when docked to the Gateway. Rationale: Planned venting events (e.g., pressurized volume pressure relief, vestibule venting, or trash system venting) should seek to minimize unbalanced torques or forces which might consume Gateway attitude control system resources. Requirement does not apply when the LM is not docked to Gateway.

Requirement Owner:




35

3.08 POWER

L3-GLS-0005 Power To Payloads

The Logistics Module shall provide no less than 1.8 kW <TBR-001> continuous power to cargo & payloads from the time of handover on the ground, until the time of offloading from the LM to the Gateway.

Rationale: Pressurized and unpressurized Logistics Module cargo and payloads may require power during transit and while docked at the Gateway. These powered payloads may be within the pressurized area, such as a cold stowage system, or in the unpressurized area, such as the Robotic Arm. 1.8 kW is consistent with an Orion Co-Manifested Payload available power budget. A mission Interface Control Document will specify additional detail such as peak power requirements and interfaces required for each powered payload on each Logistics mission.

Requirement Owner:



L3-GLS-0021 Power Independence While Docked

Exclusive of a Robotic Arm, the Logistics Module shall power all LM systems and powered payloads independent of the GW while docked during both crewed and uncrewed periods, including periods of isolation from solar energy of up to 1.5 hrs. <TBR-002>

Rationale: Independence from Gateway systems ensures LM can maintain itself and power necessary systems and payloads while docked. Gateway attitude control will prioritize other systems and elements, such as PPE and Orion (during periods when crew are present). The LM will not be able to rely on Gateway to provide attitude that optimizes LM power generation and the LM will not be able to rely on obtaining power from the Gateway while docked. The 1.5 hours isolation from solar energy is based on a Lunar synodic resonance NRHO which will essentially eliminate the Earth shadow and keep the Lunar eclipses less than 1.5 hours. Preliminary estimates of Robotic Arm power requirements during robotic arm walkoff operations may exceed the 1.8kW continuous payload power requirement, and may require power from Gateway. Power requirements defining Robotic Arm delivery will be addressed on a Gateway Logistics Services mission-unique basis.


L2-LM-0018 Independent Power While Docked

L3-GLS-1011 Contingency Docked Power Interface

The Logistics Module docking system shall have an interface to receive up to <TBD-003> kW of power from the Gateway for contingency purposes, as specified in section 3.2.1.16 Gateway Element Allocation Tables in DSG-SPEC-PWR-011, Gateway Program Subsystem Specification for Power.

Rationale: While the Logistics system is intended to be power independent from Gateway, there may be contingency cases, such as the Robotic Arm mission, where the presence of a power interface, and the ability to accept power from Gateway, would be beneficial. An integrated Modular Power System will be implemented across Gateway to provide power to the Gateway systems, utilization, and visiting vehicles. This interface will be implemented at the docking system umbilical plane.





36

L2-LM-0234 Power Subsystem Specification




37

3.09 COMMUNICATIONS

L3-GLS-0033 Intermodular Crew Voice Communications

The Logistics Module shall extend Gateway voice communication between crew audio devices within the Logistics Module habitable volume.

Rationale: Gateway will implement wireless crew voice comm to enable crew communication throughout Gateway, and for transmission to ground control centers on Earth, visiting vehicles, or ground or space-based lunar systems. To ensure the Gateway wireless communication system performance meets mission requirements, the Logistics Module may include repeaters or interfaces to augment and extend crew wireless voice comm coverage into the LM habitable volume. Gateway implements the International Communication System Interoperability Standard (ICSIS) for wireless communication systems as specified in DSG-SPEC-COMM-005, Gateway Program Subsystem Specification for Comm.


L2-LM-0029 Intermodular Crew Voice Communications

L3-GLS-1021 Gateway Wireless Network Coverage

The Logistics Module shall extend Gateway wireless networks into the habitable volume of the Logistics Module while docked to the Gateway.

Rationale: It is anticipated that multiple mobile devices will be in use within the internal volume of the Logistics Module by crew as well as wireless devices (e.g., computers, tablets, audio, video, sensors) that may be temporarily installed in the Logistics Module. To ensure the Gateway wireless network system performance meets mission requirements, the Logistics Module may include wireless access points or interfaces to augment and extend wireless network coverage into the LM habitable volume. Gateway implements the International Communication System Interoperability Standard (ICSIS) for wireless communication systems as specified in DSG-SPEC-COMM-005, Gateway Program Subsystem Specification for Comm.


L2-LM-0123 Wireless Communication

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

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-LM-0270 C&W Annunciation




38

L3-GLS-1031 Visiting Vehicle Phase Spectrum Regulatory Compliance

The Logistics Module shall comply with spectrum selection/allocation, certification, and usage restriction policies set forth by the National Telecommunications and Information Administration (NTIA) while operating inside the Gateway Rendezvous Sphere

Rationale: Allocations of the spectrum and constraints for its use are governed by national regulations. Allocations of frequency spectrum for U.S. Government systems, including NASA, are managed by the National Telecommunications and Information Administration (NTIA).


L2-LM-0125 Spectrum Regulatory Compliance

L3-GLS-1032 Transit Phase Spectrum Regulatory Compliance

The Logistics Module systems shall comply with spectrum selection/allocation, certification, licensing, and usage restriction policies set forth by the Federal Communications Commission (FCC) for commercial space operations.

Rationale: Allocations of spectrum and constraints for its use are governed by national regulations. US commercial companies' spectrum use is regulated by the Federal Communications Commission (FCC).


L2-LM-0125 Spectrum Regulatory Compliance

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

The Logistics Module shall transmit Logistics Module and payload health & status data to NASA during transit to and from the Gateway.

Rationale: Data and communication are necessary during transit to monitor the status of payloads and to monitor status of the overall Logistics Module system (including commanding, file uploads, GN&C data, health and status telemetry). When not docked with the Gateway, communications are anticipated to be with the provider's earth-based ground systems, with real-time access to downlinked data provided to NASA. Powered cargo or payload mission data transmission requirements will be specified in the associated payload or cargo requirements document or by referencing the applicable requirements in Gateway Level 2 requirements documents. If data up-link is a requirement for some powered payloads onboard the LM then this requirement must be edited to include up-link communications. The data transmission capability will be proposed by the contractor and will be provided in the Transit Phase Data Transmission Systems Specification or equivalent. The Transit Phase Data Transmission Systems Specification will be defined by the contractor and approved by NASA, as part of an overall contractor Logistics Module User's Guide that will be made available for cargo and payloads planning.



L3-GLS-1100 Critical Event Telemetry

The provider shall receive and record Logistics Module and payload telemetry during all critical mission events.

Rationale: In the event of a mission anomaly or loss, the ability to review recorded data up to the event is invaluable in reconstructing events and performing post-anomaly investigations.




39

Requirement Owner:






40

3.10 STRUCTURE

L3-GLS-1058 Structural Health Monitoring

While docked, the Logistics Module shall measure and transmit structural dynamic response data to the Gateway to monitor and characterize Gateway load events.

Rationale: Logistics Module loading events, both planned and un-planned, will occur while docked to the Gateway. The overall dynamic response to these events must be measured and transmitted while the Logistics Module is at the Gateway in order to validate Gateway dynamic models and to assess structural health and adjust operations if needed. This will require sensors on the LM to monitor module response to these events. The specific structural data to be measured/transmitted and the frequency/format of transmission to Gateway will be specified in a Gateway Structural Health Monitoring specification or other Logistics Module to Gateway data interface control documentation.


L2-GW-0190 Structural Health Monitoring System




41

3.11 NATURAL & INDUCED ENVIRONMENTS

L3-GLS-0008 Payloads Induced Environment Isolation

The provider shall provide induced environment isolation for cargo and payloads from time of handover on the ground to time of delivery at the Gateway.

Rationale: Control of environmental parameters, including but not limited to acoustic, vibration, g-loads, thermal, and pressure, is necessary during transit and storage for some payloads to maintain certain conditions, capabilities, and functions of those payloads. The acceptable limits for induced environments are either referenced in applicable level 2 Gateway requirements documents or will be defined in a mission-specific payloads interface requirements document. The provider will maintain an Induced Environment Control Specification for payload isolation systems as needed. The isolation capability within the acceptable limits will be proposed by the provider and will be provided in the Induced Environment Control Specification or equivalent document. The Induced Environment Control Specification will be defined by the contractor and approved by NASA, as part of an overall contractor Logistics Module User's Guide that will be made available for cargo & payloads planning.


L2-LM-0169 Limit Quasi-Steady Accelerations

L2-LM-0170 Limit Vibratory Accelerations

L2-LM-0171 Limit Transient Accelerations

L3-GLS-0024 Pressurized Payload Environments While Docked

The Logistics Module shall meet requirements for pressurized payload temperatures and pressures while docked to the Gateway, independent of the Gateway ECLS or thermal control systems.

Rationale: Independence from Gateway systems ensures LM can maintain its internal pressurized environment for payloads during the docked and uncrewed phase, which may be as long as 3 years. The Gateway will not always provide attitude control that optimizes LM thermal control, and the LM will not be able to rely on thermal control or atmosphere replenishment from the Gateway while docked, if the hatch is closed and any intravehicular ducting is disconnected.


L2-LM-0149 Gateway Thermal Control Systems

L2-LM-0237 Thermal Subsystem Specification

L3-GLS-1010 Natural Space Environment

The Logistics Module shall satisfy all mission requirements for safety and performance during and after exposure to the natural space environments as defined in SLS-SPEC-159 Cross-Program Design Specification for Natural Environments, for up to 3 years of Gateway docked operations.

Rationale: This requirement defines the limits of the effects of the natural space environment at the Gateway for the maximum duration that the LM will reside at the Gateway and ensures that they will be mitigated by the design or the planned operations for that maximum design duration. Additional details are needed. The specification must be referenced in applicable Gateway documents.





42

L2-GW-0176 Natural Space Environments

L3-GLS-1017 Critical Systems Survival at Vacuum

Logistics Module critical systems located with the habitable volume shall operate during and after exposure to vacuum for a duration up to <TBD-GTW-L2-004> hours.

Rationale: Critical avionics and power hardware must be able to survive and operate over a full range of pressure, from standard upper operating design spec pressure through a transition to partial pressures down to zero. This implies that those units need to be conductively cooled and designed for the range of temperature and environment changes (e.g. designed to address corona concerns, humidity changes). Non-critical items such as payloads as well as potential non-critical air cooled electronics are assumed to be powered off during a high-to-low pressure transition.

Requirement Owner:


L2-LM-0210 Critical System Survival At Zero Pressure

L3-GLS-1040 Uncrewed Temperature Range

The Logistics Module pressurized environment systems shall operate in temperatures between 4°C (39°F) and 27°C (81°F). <TBR-018>

Rationale: This requirement establishes the expected Gateway atmosphere temperature range. The low limit is the predicted minimum Gateway internal atmosphere temperature during uncrewed periods. Nominal, crewed operations temperature requirements will be further specified in the Gateway ECLS Subsystem Specification. Payload temperature requirements will be specified in payload ICD or IRD documents.


L2-LM-0222 Temperature Range

L3-GLS-1043 Low Humidity Operation

The Logistics Module shall operate in atmospheric conditions down to 0% <TBR-005> humidity during uncrewed periods.

Rationale: During crewed operations, the dew point will remain within crew comfort levels. During the uncrewed period, the cabin may be very dry with a dew point less than 4C (39F) at lowest allowable temperature. Humidity may be removed purposefully to prevent condensation and microbial growth. The humidity will passively be reduced as the pressure is maintained with dry gasses and no crew is present to replenish atmospheric vapor. Appropriate design of electronics must be included to control electrostatic discharge (ESD) hazards. Design Specifications to minimize risk of ESD may be found in DSG-RQMT-004 and DSG-RQMT-007



L3-GLS-1060 Micrometeoroid Debris PNP

The LM shall have a probability of no penetration (PNP) greater than or equal to 0.99999^(A*Y) <TBR-008>, where: A = total hazardous impact surface area in square




43

meters and Y = exposure time in years for items with the potential to create a catastrophic hazard if impacted or punctured by micrometeoroid debris.

Rationale: This is a Gateway level requirement for micrometeoroid penetration probability and must be confirmed if it can be reduced for the LM. If a commercial visiting vehicle can accept a reduced micrometeoroid penetration probability, then this, or a similar, requirement must be contained in a Commercial Visiting Vehicle Requirements Document or may be provided by referencing the applicable requirement(s) in Gateway Level 2 requirements documents.


L2-LM-0023 Micrometeoroid and Orbital Debris

L3-GLS-1071 Intervehicular Activity Limit Loads

The Logistics Module shall be designed to the limit loads for crew intervehicular activity (IVA) within the Logistics Module while docked, as specified in Table 3.11-2 <TBR-009>.

Rationale: Table 3.11-2 is taken from crew IVA loads in SSP 50005, International Space Station Flight Crew Integration Standard, and SSP 50808, ISS to COTS IRD.

Table 3.11-2 - IVA Induced Loads

Item Induced Loads (N) Directions Fixed and Portable IVA handholds and handrails

1113 N (250 lbf) (ultimate) Any Direction

Nonstructural closures 556 N (125 lbf) (limit) 778 N (175 lbf) (ultimate)

Attach Point for Tether Attachment

1113 N (250 lbf) (ultimate) Any Direction


L2-GW-0291 IVA Limit Loads

L3-GLS-1087 Ground Handling and Transportation Environment

During ground processing and integration prior to launch, the Logistics services provider shall control the exposure of unpressurized cargo and payloads to the loads, temperature, relative humidity and cleanliness constraints defined in SSP 50833, International Space Station Program Cargo Transport Interface Requirements Document rev. B, Section 3.2.3.9

Rationale: By controlling exposure for unpressurized cargo and payloads to the ground handling and transportation environment equivalent to the existing constraints used by ISS, existing external payload cargo can be handled, transported and integrated without modification, and new external payload cargo can be developed for transportation to the Gateway without modification and recertification.

L3-GLS-1094 Minimum Lunar Distance

The LM shall operate in orbit that limits the time during perilune passage below 10,000 km (6214 mi) altitude above the lunar surface to less than 8 consecutive hours.




44

Rationale: This perilune constraint for the Gateway integrated vehicle was chosen by the Gateway Program to minimize orbit maintenance, to define natural environments for thermal and power systems designs, and provide for lunar observation opportunities for utilization. Depending on the NRHO targeted, the minimum altitude can vary. The closest approach will be for a short period of time which can be used to constrain thermal needs. Low Lunar Orbits (LLO) are not planned because Orion cannot reach LLO and Gateway costs and technical challenges are significantly higher for orbit maintenance, power, communications, and thermal constraints.


L2-LM-0118 Minimum Lunar Distance

L3-GLS-1096 Gateway Docking System Docking Limit Loads

The Logistics Module shall limit loads imparted at the docking interface during docking to be within the values in Table 3.11-1.

Rationale: Gateway docking ports are required to be compatible with the IDSS. The limit loads table represents the docking mechanism soft capture system maximum allowable interface loads, as specified in IDSS Table 3.3.1.4-1.

TABLE 3.11-1 LIMIT LOADS FOR VEHICLE DOCKING TO GATEWAY

Load Limiting Value Tension 3900 N (877 lbf) Compression (Static) 3500 N (787 lbf) Compression (Dynamic, up to 0.1sec) 6500 N (1461 lbf) Shear 3200 N (719 lbf) Bending 2800 N-m (2065 lbf-ft) Torsion 1500 N-m (1106 lbf-ft) Notes: 1. Values are design limit loads. 2. Values are defined at the center of the docking mechanism soft capture system (SCS) mating plane. 3. Values are 3σ maxima and are to be applied simultaneously. 4. Shear loads may be applied in any direction in the SCS mating plane. 5. Bending moment may be applied about any axis in the SCS mating plane.


L2-GW-0279 Docking Limit Loads at VV




45

L3-GLS-1098 Maximum Oxygen Concentration Nominal Total Pressure

The Logistics Module shall operate in conditions up to 25.9% oxygen at a nominal pressure of 101.3 kPa (14.7 psia).

Rationale: Enriched oxygen concentrations increase the flammability of materials within that environment. An extensive database of materials flammability data at this operating point is available in the NASA Materials Selection Database for flammability. Oxygen concentration control ranges will be defined in the Gateway ECLS Subsystem Specification.


L2-LM-0246 Maximum Oxygen Concentration Nominal Total Pressure

L3-GLS-1041 Maximum Oxygen Concentration Low Pressure

The Logistics Module shall operate in conditions up to 30% oxygen with nominal operating functions for atmosphere pressures up to 70 kPa (10.2 psia).

Rationale: Elevated oxygen concentrations at lower pressures are needed to sustain human life. An extensive database of materials flammability data at this operating point is available in the NASA Materials Selection Database for flammability. Oxygen concentration control ranges will be defined in the Gateway ECLS Subsystem Specification.


L2-LM-0221 Maximum Oxygen Concentration Low Pressure

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

The provider shall verify by analysis that Logistics Module-generated normal plume pressure impulses imparted upon Gateway solar arrays and radiator wings do not exceed 0.958 N/m² (0.02 pounds per square foot) second (psf-sec) <TBR-L2-GW-040> within any 5 second window and 1.34 N/m² (0.028 psf-sec) <TBR-L2-GW-041> within any 18 second window, during visiting vehicle proximity operations.

Rationale: During proximity operations, thruster plumes from vehicles docking to Gateway will transfer loads to the Gateway structure. It is necessary to limit the loads transfer within the design limits of Gateway modules and deployed appendages, especially solar arrays and radiators. The current limits are based on SSP 50808 Section 3.2.2.6.4.5.2. Verification that the limits are not exceeded will be accomplished through integrated analysis with the Gateway and visiting vehicle teams. Expected values are a function of the Gateway configuration, docking locations, and visiting vehicle thruster size, location, orientation, plume flow field, and jet firing histories for proximity operations.


L2-GW-0294 Normal Peak Plume Pressure

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

The provider shall verify by analysis that Logistics Module-generated normal and shear plume pressure impulses imparted upon Gateway local components and structure other than solar array and radiator wings do not exceed 165 N/m² (3.42 lb/ft²) <TBR-L2-GW-042> and




46

38 N/m² (0.08 lb/ft²) <TBR-L2-GW-043>, respectively, during visiting vehicle proximity operations.

Rationale: During proximity operations, thruster plumes from vehicles docking to Gateway will transfer loads to the Gateway structure. It is necessary to limit the loads transfer within the design limits of Gateway modules and deployed appendages, especially solar arrays and radiators. The current limits are based on SSP 50808 Section 3.2.2.6.4.5.2 and are TBR for Gateway. Verification that the limits are not exceeded will be accomplished through integrated analysis with the Gateway and visiting vehicle teams. Expected values are a function of the Gateway configuration, docking locations, and visiting vehicle thruster size, location, orientation, plume flow field, and jet firing histories for proximity operations.

Requirement Owner:


L2-GW-0295 Normal and Shear Plume Pressures




47

3.12 SAFETY

This section contains the safety technical requirements for the Logistics service. The primary intent of the safety requirements is to protect the flight crew and Gateway. Accordingly, many of the safety requirements are applicable to the phases of the Logistics mission when the Logistics Module is within the Gateway Rendezvous Sphere (which includes rendezvous, proximity operations, docking, docked operations, undocking, and departure). The primary source of these requirements is the draft DSG-RQMT-001, Gateway System Requirements document provided for Logistics Element review per Change Request 0017 in April of 2019. The safety requirements in DSG-RQMT-001 were reviewed for applicability to the Logistics Service and tailored by KSC Logistics Element Safety and Mission Assurance.

L3-GLS-1018 Logistics Module Tolerate Inadvertent Operation Action

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall tolerate an inadvertent command or operator action, as identified by a Hazard Analysis performed in accordance with DSG-RQMT-011, without causing a catastrophic event.

Rationale: This applies to human operators, crew, or automated system commands and operations.


L2-LM-0037 Tolerate Inadvertent Operator Action

L3-GLS-1044 Emergency Equipment Accessibility

The Logistics Module shall allow accessibility to emergency equipment by crew within 15 seconds, <TBR-006> including translation from anywhere in the habitable volume.

Rationale: In the event of a hazardous event such as a rapid cabin decompression, or toxic contamination of the atmosphere due to fire other unscheduled event, the crew must have breathing air to evacuate and isolate themselves from the hazardous environment. This time is driven by the time that an alert is sounded and incapacitation of the crew.


L2-LM-0249 Emergency Equipment Accessibility

L3-GLS-2001 Logistics Module Critical Hazards

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall control critical hazards.

Rationale: Compliance with this requirement may be accomplished at the Logistics Module level, or through a combination of hazard controls at the Logistics Module/Gateway level.


L2-LM-0187 Critical Hazards

L3-GLS-2002 Logistics Module Catastrophic Hazards

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall provide at least single failure tolerance to catastrophic events.




48

Rationale: Compliance with this requirement can be accomplished at the end item level or through a combination of hazard controls at the Module/System levels and end item level. A common way to improve reliability and thus meet safety requirements is to use systems that tolerate failures when complete failure avoidance is not practical. Specific hazard controls and implementation must be derived from an integrated design and safety analysis performed in accordance with DSG-RQMT-011, LM Hazard Analysis Requirements. Additional failure tolerance may be required to meet systems reliability requirements.


L2-LM-0186 Catastrophic Hazards

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

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall provide required failure tolerance capability without the use of emergency equipment and systems.

Rationale: Emergency systems, EVA or emergency operations cannot be used as a leg of failure tolerance as these emergency systems and equipment cannot definitively prevent an initiating event. As a result, the mitigation of catastrophic and critical hazards will implement a fault tolerance strategy without the use of EVA, emergency systems, or emergency operations. However, the use of EVA, emergency systems, and contingency or emergency operations will be considered a CSM to prevent loss of crew in the event all other approved hazard controls have failed.


L2-LM-0185 Failure Tolerance Capability

L3-GLS-2004 Logistics Module Autonomous Operation

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall provide the capability for autonomous operation of system and subsystem functions, which if lost, would result in a catastrophic event.

Rationale: This capability means that the system does not depend on communication with Earth (e.g., mission control) to perform functions that are required for control of catastrophic hazards. While the crew is present, the LM should automate catastrophic hazard controls to minimize the need for crew actions, using crew action only as a last resort where automation is not practical.


L2-LM-0209 Autonomous Operation

L3-GLS-2005 Logistics Module Reliability

The Logistics Module shall have a predicted system hardware reliability of 0.94 per year for its defined mission environment without corrective maintenance in space.

Rationale: Logistics Module reliability includes Logistics Module hardware reliability for all must work and must not work functions during transport, deploy and cis-lunar operations for one year and does not include Launch Vehicle reliability. Logistics Module allocated hardware reliability supports Gateway compliance with program-level Loss of Crew and Loss of Mission requirements. Software was explicitly excluded because there is not a standard methodology for performing software reliability. Loss of a Logistics Module after docking does not impact Gateway loss of crew/loss of mission ( LOC/LOM), but is included in the reliability requirement in order influence the Logistics Module design.




49


L2-LM-0176 LM Reliability

L3-GLS-2006 Logistics Module Redundancy Design

The Logistics Module shall design redundant systems, redundant subsystems, and redundant major elements of subsystems (such as assemblies, panels, power supplies, tanks, controls, and associated interconnecting wiring and fluid lines) to ensure that an unexpected event which damages one is not likely to prevent the other from performing the redundant function.


L2-LM-0208 Protection of Redundant Paths

L3-GLS-2009 Hazard Analysis

The provider shall perform hazard analysis in accordance with DSG-RQMT-011, Gateway Program Hazard Analysis Requirements for Logistics Module operations within the Gateway Rendezvous Sphere, .

Requirement Source:

DSG-RQMT-010 Gateway Safety & Mission Assurance Requirements

L3-GLS-2011 Operational Hazard Controls

Hardware or software requiring crew operation shall include operational hazard controls for safe operation.

Requirement Source:

DSG-RQMT-010 Gateway Safety & Mission Assurance Requirements

L3-GLS-2052 Logistics Module Crew Manual Override

While operating within the Gateway Rendezvous Sphere, the Logistics Module shall provide the capability for the crew to manually override higher-level software control/automation (e.g. automated abort initiation, configuration change, and mode change) when the transition to manual control of the system will not cause a catastrophic event.

Requirement Source:

Draft Gateway Safety Design Requirements

L3-GLS-2053 Logistics Module Inhibit Monitoring

The Logistics Module shall monitor the status of controls and inhibits associated with functions whose inadvertent activation and those functions whose failure to activate when required could have catastrophic results.

Requirement Source:





50

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

Deployable end items shall provide inhibit monitoring during the timeframe a hazard exists. Requirement Source:


L3-GLS-2063 Logistics Module Health and Status Measurement Redundancy

The Logistics Module shall provide redundant health and status measurements of critical systems and subsystems.

Rationale: Note: The requirement for redundant heaters is addressed by fault tolerance for catastrophic hazards.

Requirement Source:


L3-GLS-2066 Logistics Module Computer Initiated Hazards and Controls

No single computer shall be capable of independently initiating a hazard or responsible for sole control of the hazard, under nominal operating conditions.

Requirement Source:


L3-GLS-2067 Logistics Module CBCS Safe Initialization

Logistics Module CBCS shall safely initialize to a known safe state and that no unplanned/spurious signals are generated during initialization and mode transitions.

Requirement Source:


L3-GLS-2068 Logistics Module CBCS Orderly Shutdown

LM CBCS shall perform an orderly shutdown of a function to a predetermined safe state when a termination command has been received or upon detection of a termination condition.

Requirement Source:


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

When the Logistics Module is operating at off-nominal power conditions, any safety-critical systems shall be operable.

Rationale: The LM design should operationally prioritize or design for safety critical systems to fail last or remain operable under off-nominal power conditions.




51

Requirement Source:


L3-GLS-2070 Logistics Module Overrides by Operators

Overrides shall require at least two independent actions by the operator. Requirement Source:


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

Logistics Module shall reject commands received out of sequence if the execution of those commands is hazardous.

Requirement Source:


L3-GLS-2072 Logistics Module Inadvertent Memory Modification

The Logistics Module CBCS shall prevent, detect and recover from inadvertent memory (includes both temporary and long term memory) modification during use.

Requirement Source:


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

While within the Gateway Rendezvous Sphere, the Logistics Module CBCS shall discriminate between valid and invalid inputs from sources external to the CBCS and remain or recover to a known safe state in the event of an invalid external input.

Requirement Source:


L3-GLS-2074 Logistics Module CBCS Integrity Checks

While operating within the Gateway Rendezvous Sphere, the Logistics Module CBCS shall perform integrity checks when data or commands are exchanged across transmission or reception lines and devices.

Requirement Source:


L3-GLS-2075 Logistics Module CBCS Prerequisite Checks

The Logistics Module CBCS shall perform prerequisite checks for the safe execution of hazardous commands.




52

Requirement Source:


L3-GLS-2076 Logistics Module Disabling of Arming Commands

Where two step commanding is required, a Gateway mechanism for disabling the armed command shall be provided.

Rationale: Note: Could be via time-out, a disarm command, or a disarm if the command following the arm is not the fire command.

Requirement Source:


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

Where loss of a function could result in a catastrophic hazard, the Logistics Module CBCS shall provide at least one independent and unique command message to disable each leg of control, and two independent and unique command messages to deactivate the last leg of control.

Requirement Source:


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

Command messages to remove or change the state of inhibits shall be unique for each state and each inhibit.

Requirement Source:


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

The Logistics Module shall provide automated detection and safing for critical and catastrophic hazards within the time to effect of the hazard.

Requirement Source:


L3-GLS-2082 Logistics Module Manual Safing Data

The Logistics Module shall notify the crew or ground operators of the need to perform manual safing and provide the data, necessary and sufficient, for the performance of manual system safing for identified hazards.

Requirement Source:





53

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

Logistics Module Electromagnetic Effect (EME) safety critical circuits shall have 20 dB safety margin for electroexplosive firing circuits and 6 dB safety margin for all other EME safety critical circuits when demonstrated by test.

Requirement Source:


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

Logistics Module EME safety critical circuits shall have 34 dB safety margin for electroexplosive firing circuits and 20 dB safety margin for all other EME safety critical circuits when margin is calculated by analysis.

Requirement Source:


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

Logistics Module systems utilizing direct current power shall be DC isolated from chassis, structure, equipment conditioned power return/reference, and signal returns by a minimum of 1 megohm <TBR-011>.

Requirement Source:


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

Logistics Module isolated power sources shall be DC isolated from chassis, structure, equipment, conditioned power return/reference, and signal circuits by a minimum of 1 megaohm, individually, except at the single point ground.

Requirement Source:


L3-GLS-2119 Logistics Module Circuit Conductors DC isolation

Circuit conductors shall be DC isolated from chassis, structure, and equipment conditioned power return/reference, by a minimum of 1 megohm, individually, when not terminated by the signal circuit's single point ground/reference.

Rationale: Balanced, differential circuits isolated from chassis, structure, and user conditioned power return/reference by a minimum of 6000 ohms complies with this requirement.

Requirement Source:





54

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

The mechanism design shall provide positive indication that the mechanism has achieved its desired state for hazard control.

Requirement Source:


L3-GLS-2121 Logistics Module Hatchway Drag-Throughs

Hatchways shall be clear of drag-throughs. Requirement Source:


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

Critical seals with a major outer diameter less than or equal to 1.27 cm (0.5 inches) shall have a minimum of one seal at the interface.

Requirement Source:


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

Critical seals with a major outer diameter greater than 1.27 cm (0.5 inches) shall have a minimum of two seals at the interface.

Requirement Source:


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

Assemblies containing critical seals with a major outer diameter greater than 15.24 cm (0.5 inches) shall include leak test ports and conductance grooves within the seal interstitial area to accommodate redundant seal verification.

Requirement Source:


L3-GLS-2125 Logistics Module Colocation of Tools and Devices for Hatch Operation.

Tools or devices necessary for hatch operation shall be co-located with the hatch. Requirement Source:




55


L3-GLS-2126 Logistics Module Visual Inspection

The Logistics Module shall provide a window for direct, non-electronic visual observation of the environment on the opposite side of the hatch, when the hatch is closed.

Rationale: A visual inspection of the condition of the Logistics Module interior is desired to assure the interior of the LM is fit for crew entry.


HSR-8027 3.6.1.2.2 Visibility Across the Hatch <TBR-V2>

Requirement Source:


L3-GLS-2129 Logistics Module Hatch Inadvertent Opening Prevention

Hatches shall be designed to prevent inadvertent opening prior to complete pressure equalization.

Requirement Source:


L3-GLS-2131 Logistics Module Safe Recovery

The Logistics Module shall detect, isolate, and safely recover from faults. Rationale:

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

While in the Rendezvous Sphere, LM hazards shall be controlled such that no inadvertent operator action in the presence of a single system failure can result in a catastrophic event.

L3-GLS-2133 Logistics Module Controls for Human Error

The Logistics Module shall implement controls to human error according to the following precedence:

1. Prevent human error in the maintenance, operation, and control of the system.

2. Reduce the likelihood of human error and provide the capability for the human to detect and correct or recover from the error.

3. Design the system to limit the negative effects of errors.


L2-GW-0238 Controls for Human Error




56

3.13 DESIGN & CONSTRUCTION

The following design and construction standards apply to the Logistics Modules and Gateway Logistics Services.

L3-GLS-1113 Material Offgassing

All materials used in hardware which will be exposed to space vacuum shall have low outgassing characteristics as defined by a total mass loss (TML) of < 1.0 percent and a volatile condensable material (VCM) of < 0.1 percent when tested per ASTM–E595, Standard Test Method for Total Mass Loss and Collected Volatile Condensable Materials.

Rationale: Logistics Module offgassing must be limited to prevent the contamination of Gateway or other space system solar arrays, radiators, optical surfaces, sensors, etc. Source is SSP 30426 Space Station External Contamination Control Requirements.

Requirement Owner:

L3-GLS-3010 Fluid Standard

Logistics Module fluids or commodities which are exchanged with Gateway systems or crew shall comply with MPCV 70156, Cross-Program Fluid Procurement and Use Control Specification.

Rationale: A common fluid procurement specification ensures that commodities shared across Gateway/Logistics interfaces are controlled to Gateway specifications.


L2-GW-0298 Fluid Standards

L3-GLS-3012 Internal Cleanliness

The Logistics Module habitable volume interior surfaces and exterior surfaces of flight articles integrated into the habitable volume shall conform to the VC-1-500 cleanliness level prior to final closeout as specified in IEST-STD-CC1246E Product Cleanliness Levels – Applications, Requirements, and Determination, using portable hand held incident lighting, unless a specific hardware item requires a more stringent cleanliness level.

Rationale: The cleanliness level for interior surfaces of the habitable volume is specified to mitigate airborne particulate contamination and promote a safe and comfortable working space for crew upon entry and during routine crewed activities. Levels are similar to SN–C–0005, paragraph 2.4 (Internal). Areas that are inaccessible in the final assembly and that may act as contamination sources while on orbit should be inspected before close out.


L2-GW-0300 Workmanship-Internal Cleanliness

L3-GLS-3013 External Cleanliness

Logistics Module exterior surfaces shall be cleaned to the VC-1-500 cleanliness level prior to final closeout as specified in IEST-STD-CC1246E Product Cleanliness Levels – Applications, Requirements, and Determination, including areas that are inaccessible in the final assembly and that may act as contamination sources while on orbit.




57

Rationale: The cleanliness level for exterior surfaces of the Logistics Module is specified to mitigate on-orbit particle evolution and contamination of Gateway, Orion, and other nearby sensitive system surfaces.


L2-GW-0301 Workmanship-Exterior Cleanliness




58

TBDS AND TBRS

A.1 SCOPE

This appendix lists all items in this document that need to be determined (TBD) and that need to be resolved (TBR).

A.2 LIST OF TBDS

Table A-1—TBDs

TBD Description Closure Date

Trace to Requirement ID & Name

TBD-003 Gateway power system specification, when approved, will define the maximum power that can be used by docked logistics modules.

L3-GLS-1011 Contingency Docked Power Interface

TBD-007 Maximum likely crewed duration of 90 days is notional and has not been refined or validated. Will be closed following input on maximum likely contingency crew duration from Gateway. Level 2.

L3-GLS-1104 Logistics Module Life

A.3 LIST OF TBRS

Table A-2—TBRs

TBR Description Closure Date


TBR-001

1800kW is the current assumption for a baseline logistics mission. Will refine as payload and manifest needs are refined by Level 2

L3-GLS-0005 Power To Payloads

TBR-002

1.5 hours is a preliminary estimate provided by Level 2 and is presumed to be conservative.

L3-GLS-0021 Power Independence While Docked

TBR-003

2200kg is a conservative upper limit for the predicted system mass at this level of development, and has been selected for GLS providers’ consideration. 1600 kg limit at L2 originated as a CPL launch mass limit. Robotic arm mass restrictions are owned by Level 2.

L3-GLS-1004 Robotic Arm System Delivery

TBR-005

0% humidity may be difficult to test/qualify to, so TBR until a realistic lower limit is established by L2 or proposed by GLS vendor.

L3-GLS-1043 Low Humidity Operation

TBR-006

Originates from L2 human/crew systems and safety. See related <TBR-L2-GW-046>.

L3-GLS-1044 Emergency Equipment Accessibility




59

TBR Description Closure Date


TBR-008

Will remove TBD once L2 confirms this PNP value for Logistics/lunar environment.

L3-GLS-1060 Micrometeoroid Debris PNP

TBR-009

Double check that the information is in the SSP 50005 document

L3-GLS-1071 Intervehicular Activity Limit Loads

TBR-010

An LM upper mass limit of 14 metric tons was used in Gateway Integrated Analysis Cycle 3. Will update as new IAC results/assumptions are documented.

L3-GLS-1106 Maximum System Docking Mass

TBR-011

Have Logistics safety & mission assurance confirm 1megohm value

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

TBR-017

7 days is the current late load baseline and is expected to meet most Gateway late load item needs for the first or second flight. Assumes very little to no science on these flights and is primarily a last-minute payload needs accommodation option. Will re-confirm as the phase 1 con ops and manifest mature.

L3-GLS-1085 Pressurized Cargo and Payload Late Load Capability

TBR-018

Lower limit is consistent with Gateway uncrewed lower temps but upper limit has not been confirmed for crewed vs. uncrewed vs. transit pressurized payload requirements.

L3-GLS-1040 Uncrewed Temperature Range

TBR-019

ISS-heritage 400 standard liter volume needs validation by Gateway L2 w.r.t. expected pressure vessels/pressures used as cargo on LM flights.

L3-GLS-1115 Unplanned Pressurized Cargo Gas Release




60

GLOSSARY

Table B-1—Glossary

Term Description

C&W Caution and Warning

CAM Collision Avoidance Maneuver

Cargo The NASA-defined supplies, equipment, spares, and consumables that NASA manifests and provides to the Logistics Service Provider as part of a Logistics mission to deliver to Gateway. Includes NASA-owned systems as well as third-party systems that NASA manifests as part of a Logistics mission managed by the Logistics Element. Typically unpowered, inactive items e.g. soft goods, consumables, or crew items.

Catastrophic Hazard

Any condition which may cause a disabling or fatal personnel injury, or loss of one of the following systems: Gateway, Orion, or Human Landing System elements. For safety failure tolerance considerations, loss of the subject systems is to be limited to those conditions resulting from failures or damage to the systems that render the system unusable for further operations, even with contingency repair or replacement of hardware, or which render the system(s) in a condition which prevents further rendezvous and docking operations.

CBCS Computer-Based Control System

CHP Crew Health and Performance

CO2 Carbon Dioxide

COTS Commercial Orbital Transportation Services

CPL Co-Manifested Payloads

CR Change Request

Critical Hazard Any condition which may cause a non-disabling personnel injury, severe occupational illness; loss of a Gateway element, loss of a Gateway life-sustaining function or emergency system, or involves damage to Orion or a Human Landing System element. For safety failure tolerance considerations, critical hazards include loss of Gateway elements that are not in the critical path for Gateway survival or which can be restored through contingency repair.

Critical Systems (a) Systems which could cause a catastrophic or critical hazard if unable to perform the required functions, as determined by hazard analysis in accordance with DSG-RQMT-011 Gateway Program Hazard Analysis Requirements;

(b) Components with criticality category 1/1R/1S or criticality category 2/2R failure modes as assessed by Failure Modes and Effects Analysis in accordance with DSG-RQMT-011, Gateway Program Failure Modes and Effects/Critical Items List (FMEA/CIL) Requirements.

CRS Cargo Resupply Services

CSM Crew Survival Method

CTB Cargo Transfer Bags

DC Direct Current




61

Term Description

DSB2 Docking System Block 2

ECLS Environmental Control and Life Support

ECLSS Environmental Control and Life Support System

EME Electromagnetic Effect

ESD Electrostatic Discharge

EVA Extravehicular Activity

FCC Federal Communications Commission

Flight This is the sequence of events that takes place between liftoff and landing of a transportation vehicle.

Gateway Logistics Provider (GLP)

Contractor organization that is awarded a contract, managed by the Logistics Element, to provide one or more Logistics Missions to the Gateway as a commercial end-to-end service. Also referred to as "the provider" or "the contractor".

Gateway Logistics Services (GLS)

The name of the commercial contract to provide Logistics services to Gateway.

GDS Gateway Docking System

GDSS Gateway Docking System Specification

GM Gateway Mission

GNC Guidance Navigation and Control

GPCB Gateway Program Control Board

GR&A Ground Rules and Assumptions

H&S Health and Status

Habitability The state of being fit for occupation or dwelling. Meeting occupant needs of health, safety, performance, and satisfaction. (Source: NASA-STD-3001 Vol 2)

Habitable Volume

The volume remaining within a system's volume after accounting for all installed hardware and systems. (Source: NASA-STD-3001 Vol 2). Herein, a general term for the crew-accessible volume of the Logistics module.

Hazard The presence of a potential risk situation caused by an unsafe act or condition.

Hazard Controls "Design or operational features used to reduce the likelihood of occurrence of a hazardous effect. Hazard controls are implemented in the following order of precedence:

a) Elimination of hazards by removal of hazardous sources and operations by appropriate design measures.




62

Term Description

b) Prevention of hazards through the use of safety devices or features.

c) Control of hazards through the use of warning devices.

d) Special procedures, or emergency devices.

e) Minimizing of hazards through a maintainability program and adherence to adequate maintenance and repair schedule(s).

HSR Human System Requirements

ICD Interface Control Document

ICSIS International Communication System Interoperability Standard

IDSS International Docking System Standard

IMS Inventory Management System

IRD Interface Requirement Document

IRSIS International Rendezvous System Interoperability Standard

ISS International Space Station

IVA Inter-Vehicular Activity

IVR Inter-Vehicular Robotics

L2 Level 2, the Gateway Program

LLO Low Lunar Orbit

LOC/LOM Loss of Crew/Loss of Mission

Logistics Element (LE)

The collection of systems, capabilities, organizations, and contracts that implements the Gateway Logistics function. NASA and contractor and international partners, if necessary.

Logistics Module (LM)

A general term used to refer to the Gateway Logistics Provider's space-based system that transports Gateway logistics items to the Gateway. Intended to encompass the elements of the Logistics system which travel to and remain docked to the Gateway; may not apply to any tug, tractor, launch system, or other such elements which do not remain attached to the Gateway or within the Gateway Rendezvous Sphere for the duration of the Logistics mission.

MAPTIS Materials and Processes Technical Information System

M-BAG Multi-Purpose Logistics Module Bag

MDL Mid-Deck Locker

Mission All phases and components for one delivery event from Earth to the Gateway. Includes launch, transit, delivery to Gateway, docked operations at Gateway, and disposal. Includes ground operations.




63

Term Description

MMOD Micrometeoroid and Orbital Debris - Very small, micro-scale debris in the space environment that may cause harm or damage to crew or space systems. In the lunar environment, also referred to as Micrometeoroid(s).

NASA National Aeronautics and Space Administration

NLS NASA Launch Services

NRHO Near Rectilinear Halo Orbit

NTIA National Telecommunications and Information Administration

Payload The NASA-defined science/technology hardware that NASA manifests and provides to the Logistics Service Provider as part of a Logistics Mission to deliver to Gateway. Includes NASA-owned systems as well as third-party systems that NASA manifests as part of a Logistics Mission managed by the Logistics Element. Typically complex, powered, active items, or items which require custom or tailored provisions for mounting or transport.

PNP Probability of No Penetration

PPE Power and Propulsion Element

Rendezvous, Proximity Operations, and Docking (RPOD)

A highly coordinated and controlled set of processes and activities which describe how a visiting vehicle approaches and docks to the Gateway. Also intended to cover the undocking and departure activities which are governed by the same process.

RFID Radio-Frequency Identification

SCS Soft Capture System

SLS Space Launch System

SMAC Spacecraft Maximum Allowable Concentrations

SORI Small Orbital Replacement Unit

TBD To be Determined

TBR To be Resolved

TML Total Mass Loss

TTE Time-Triggered Ethernet

Gateway Logistics Model - NASASpaceFlight.com

Documents

Transcript of Gateway Logistics Model - NASASpaceFlight.com