Attachment_01,_GLS_SOW.pdf

Attachment 01

Gateway Logistics Services

Statement of Work (SOW)

Attachment 01: Statement of Work RFP 80KSC019R0002

THIS PAGE IS INTENTIONALLY BLANK

STATEMENT OF WORK

1.0 Introduction

2.0 Scope

3.0 Overall General Mission Requirements

3.1 Vehicle Integration

3.1.1 Launch Vehicle (LV) Preparation and Launch

3.1.2 Gateway Integration Verification Testing

3.1.3 Telemetry Data

3.1.4 Operational Support Services

3.1.5 Cargo Processing Facilities and Services Required at Launch Site

3.1.5.1 Services

3.1.5.2 Facilities

3.1.6 Range Support and Services

3.2 Program Management

3.2.1. Program Management Review

3.2.2. Formal Reviews

3.3. Mission Integration Management

3.4. Mission Analysis

3.5. Mission Operations

3.5.1 Ground Segment Operations

3.5.2 Security Requirements

3.5.3 Technical Imagery

3.5.4 Training and Operational Products for Integrated Mission Operations

3.5.4.1 Mission Flight Procedures

3.5.4.2 Mission Training

3.5.4.3 Mission Simulation Support

3.5.4.4 Real-Time Mission Support

3.6 Risk Management

3.7 Safety and Mission Assurance

3.7.1 Safety Program

3.7.1.1 Safety and Health Plan

3.7.1.2 System Safety Requirements

3.7.1.3 Operations Safety Requirements

3.7.1.4 Cargo and Payload Safety

3.7.1.5 Participation in Safety Working Groups

3.7.1.6 Preservation of the Space and Lunar Environments

3.7.2 Quality Assurance Program

3.7.3 Reliability Program

3.7.4 Probabalistic Risk Assessment (PRA)

3.7.5 Software Assurance Program

3.8 Configuration Management

3.9 Scheduling

3.10 Public Relations

4.0 Gateway Logistics Service (GLS) Missions (CLIN 1)

4.1 Required Capability

4.1.1 Required Capability – Pressurized Cargo Delivery

4.1.2 Required Capability - Pressurized Disposal

4.1.3 Required Capabilitiy - Unpressurized Cargo Delivery and Disposal Mass

4.2 Cargo Integration

4.2.1 Cargo Analysis and Integration

4.2.1.1 Pressurized Cargo Complement Variability

4.2.1.2 Cargo Physical Processing

4.2.1.2.1Pressurized Cargo Turnover

4.2.1.3 Pressurized Cargo Disposal

4.2.2 Unpressurized Cargo Physical Integration

4.3 NASA Insight and Approval for Gateway Logistics Services Missions

4.4 Reviews for Gateway Logistics Services Missions

4.4.1 Common Configuration Integration Reviews

4.4.1.1 Gateway Common Configuration Integration Milestone 1 (Mission Definition and

System Requirements Review (SRR))

4.4.1.2 Gateway Common Configuration Integration Milestone 2 (Preliminary Design Review

(PDR))

4.4.1.3 Gateway Common Configuration Integration Milestone 3 (Critical Design Review

(CDR))

4.4.1.4 Gateway Common Configuration Integration Milestone 4 (System Certification Review

(SCR))

4.4.2 Mission Technical Reviews

4.4.2.1 Vehicle Baseline Review (VBR)

4.4.2.2 Mission Integration Review (MIR)

4.4.2.3 Unpressurized Cargo Integration Review (UCIR), if applicable

4.4.2.4 Pressurized Cargo and Integration Review (PCIR)

4.4.2.5 Flight Readiness Review (FRR)

4.4.2.6 Rendezvous and Docking Readiness Review (RDRR)

4.4.2.7 Post-Delivery Review

4.4.2.8 Undocking Readiness Review (URR)

4.4.2.9 End of Mission Review (EMR)

4.5 Discrepant Hardware

4.6 Equipment Interface Demonstration (EID)

4.7 Data Review for Crew Privacy

5.0 Mission Unique Capabilities (subCLIN 103)

6.0 Specialized Delivery Missions (CLIN 2)

6.1 Required Capability - Specialized Delivery Missions

6.1.1 Delivery Service Vehicles

6.2 Specialized Mission Requirements

6.3 NASA Insight and Approval for Specialized Delivery Missions

6.4 Reviews for Specialized Delivery Missions

6.4.1 Mission Technical Reviews

6.4.1.1 Mission Specific Requirements Review (MSRR)

6.4.1.2 Mission Specific Preliminary Design Review (MSPDR)

6.4.1.3 Mission Specific Critical Design Review (MSCDR)

6.4.1.4 System Acceptance Review (SAR)

6.4.1.5 Pre-Mate Readiness Review

6.4.1.6 Flight Readiness Review (FRR)

6.4.1.7 Launch Readiness Review (LRR)

6.4.1.8 Additional Reviews

6.5 Mission Analyses

6.6 Launch Site Support

6.6.1 Launch Site Payload Integration Support

6.6.2 Contamination and Environmental Control

6.6.3 Operational Support Services

6.7 Specialized Mission S&MA Requirements

6.8 Specialized Mission Task Orders

7.0 Special Tasks and Studies (CLIN 3)

7.1 Evaluation of NASA Mission Requirements

Annexes

A. Gateway EVR System Delivery Requirements

1.0 INTRODUCTION

The Gateway is a part of a strategy to affordably extend human exploration beyond low Earth orbit to the vicinity of the Moon while simultaneously demonstrating technologies and capabilities needed for even more ambitious follow-on human exploration missions to the Lunar surface and beyond. It will be developed via an assembly of elements in cislunar orbit that will provide a platform to conduct a meaningful series of capability demonstrations to enable future exploration efforts as well as utilization. The Gateway will offer power and propulsion capabilities, habitation space, and airlock capability to enable extravehicular activities (EVAs), and logistics modules.

The logistics modules component will be used to provide the Gateway supply services as described in this Statement of Work (SOW). The SOW defines the work to be performed as part of the

Indefinite Delivery/Indefinite Quantity (IDIQ) contract line item. The use of the words shall, will, and should are as defined:

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

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

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

2.0 SCOPE

This Statement of Work (SOW) and all exhibits and documents attached or referenced herein define NASA’s requirements for the Contractor to provide the logistics services to the Gateway and disposal services from the Gateway. The end-to-end service shall include all activities to provide the logistics services including launch site and associated resources, launch vehicle, logistics vehicle and integration of NASA provided cargo, payloads or other Gateway elements, in order to satisfy the requirements of this SOW. It is anticipated that the acquisition will draw on commercial space cargo servicing capabilities and launch vehicle services currently available in the market and under development.

NASA requires the service to provide interior volume for pressurized cargo, consumables, and payloads and external mounting structures for delivery of unpressurized cargo and payloads to the

Gateway (hereinafter referred to as “cargo”). Cargo includes both NASA cargo and NASA-sponsored cargo. Contractor provided non-NASA cargo may also be included per clause 2.2.26, Contractor Objectives on Gateway Logistics Service (GLS) Missions. NASA will provide pressurized cargo to the Contractor including packing materials such as bags and foam, however the Contractor may also accommodate packing of NASA provided pressurized cargo per their unique solutions.

The logistics service includes guidance and navigation, power generation, and propulsion to enable autonomous docking of a logistics module to a docking port on the Gateway via a Gateway

Docking System (GDS) compliant interface. Once docked, the logistics module will be used primarily for cargo stowage, trash stowage, trash disposal, science and utilization and should accommodate crew performing work inside the Logistics Vehicle. In addition, the module will depart the Gateway and perform self-disposal without assistance.

NASA will provide access to detailed design information, as required, for components associated with the Gateway and logistics vehicle interfaces necessary to fulfill this SOW. This includes hardware drawings, acceptance test procedures, test equipment designs and data for the

Contractor’s use in procuring these items. The Contractor shall perform all tasks necessary to ensure safe and reliable cargo integration and transportation to and from the Gateway.

For the initial mission and subsequent missions with vehicle modifications affecting Gateway integration, in-flight demonstrations may be required prior to rendezvous and during integrated operations. The Contractor shall coordinate with NASA to determine the initial flight characteristics which may include additional in-space maneuvers, holds, durations, commands, and/or logistics vehicle health confirmations. JSC 35089, Visiting Vehicle Operations Document can be used as a guide for the type and level of joint-coordination required.

The Government will deliver to the Contractor, for use in connection with and under the terms of this contract, the Government Furnished Property described in clause 2.2.12, NFS 1852.245-76 --

List of Government-Furnished Property Pursuant to FAR 52.245-1, together with such related data and information as the Contractor may request and as may be reasonably required for the intended use of the property (herein referred to as “Government Furnished Property”).

3.0 OVERALL GENERAL MISSION REQUIREMENTS

The purpose of this section is to address requirements that apply to any missions ordered under this contract.

3.1 VEHICLE INTEGRATION

The Contractor shall build, procure, process, integrate and operate the launch and logistics vehicles necessary to provide logistics services to the Gateway. The Contractor shall obtain the support services, permits and licenses necessary to complete the logistics service.

3.1.1 LAUNCH VEHICLE (LV) PREPARATION AND LAUNCH

The Contractor shall:

(a) Perform all launch service preparations and launch site operations necessary to safely and successfully deliver and transfer the cargo to the Gateway.

(b) Generate the required documents and obtain all required safety approvals for the launch service and integrated payload, launch and logistics vehicle system operations including cargo-to-logistics vehicle and logistics vehicle-to-LV system integration and launch operations.

(c) Provide access for at least two NASA personnel to consoles in the Contractor’s launch control center that provide access to vehicle telemetry and voice nets (including countdown and major systems).

(d) Include a logo in accordance with NASA provided artwork in a prominent location. The size and location of the logo and its installation shall be appropriately specified in the relevant interface control documentation.

3.1.2 GATEWAY INTEGRATION VERIFICATION TESTING

The Contractor shall provide all necessary planning, services, personnel, test hardware (e.g.

mockups, simulators, physical interfaces, power, and data), software, and analytical products required to support Joint integration and verification activities between the logistics vehicle and the Gateway. All Joint Gateway integration and verification shall be documented in a Contractor-specific Joint Integration, Verification and Test Plan (JIVTP), to be developed jointly with NASA.

For a general overview of the Joint Gateway integration and verification activities anticipated, see reference document SSP 50964 – Visiting Vehicle ISS Integration Plan, Appendices F & G. Joint verification activities may be utilized when appropriate in DRD GLS-012 Verification and

Validation Plan to verify interface requirements.

3.1.3 TELEMETRY DATA

NASA will utilize telemetry data through all mission phases as part of each GLS mission for determining authority to proceed and mission success. The Contractor shall receive and record the full-rate telemetry data from the initiation of launch countdown through all mission phases for both the launch vehicle and for the logistics vehicle through disposal. The Contractor shall measure and provide launch vehicle and logistics vehicle telemetry and consumable calculations, in electronic format, according to relevant DRDs.

The Contractor shall provide voice and video communications from the launch complex to the designated NASA data center during launch and logistics vehicle operations at the launch complex through Range loss of signal.

The Contractor shall implement the NASA provided console communications configuration for those consoles occupied by the NASA team within the Contractor’s launch control center. The

Contractor shall validate this configuration with the designated NASA data center prior to launch vehicle testing and mission simulations.

3.1.4 OPERATIONAL SUPPORT SERVICES

The Contractor shall provide to NASA personnel safety training, instruction, and certification for all Contractor-operated or provided integration facilities and launch sites to ensure users are aware of facility, launch site, launch vehicle and cargo hazards and have adequate knowledge to carry out their tasks unescorted in a safe manner. The Contractor shall provide access for NASA personnel to the cargo, logistics vehicle, and launch vehicle or storage facilities. The Contractor shall provide security for cargo and personnel as required in cargo-specific or facility-specific documents as provided in each task order.

3.1.5 CARGO PROCESSING FACILITIES AND SERVICES REQUIRED AT LAUNCH

SITE

The Contractor shall provide the following services and facilities at the launch site for final NASA processing of some ORUs, experiment payloads, and other cargo items. This processing will be performed by NASA, NASA representatives, and International Partners in the Contractor provided facilities and includes activities such as post-shipment test and checkout, science sample preparations, final installations/removals, cargo packing, and configuration verifications. Support begins at turnover minus 30 days and continues through cargo turnover to Contractor for Logistics

Vehicle integration.

3.1.5.1 SERVICES

(a) Shipping and receiving support, including off-loading, forklift operation, and delivery to work area

(b) Common consumables such as alcohol, deionized water; bench stock items; and clean-room garments

(c) Contractor pool tools and equipment

(d) Disposal of hazardous waste

3.1.5.2 FACILITIES

(a) High Bay: approximately 1,000 square feet of 300k clean processing space with overhead cranes for processing large cargo items.

(b) Laboratories: three 300k clean science labs including sinks and exhaust vents with approximately 300-500 square feet per lab.

(c) Administrative Space: shared office/desk/cubicle space including access to Wi-Fi, printers, and phones, to accommodate approximately 10 people at any given time and access to conference rooms.

3.1.6 RANGE SUPPORT AND SERVICES

The Contractor shall comply with all applicable Range constraints. The Contractor shall make all launch Range support arrangements for the following: scheduling Range for launch and integrated testing, Range Safety functions, communications and timing, metric coverage, telemetry coverage, camera coverage of launch, and tracking and telemetry station acquisition predictions. The

Contractor shall include all tracking and data recovery support required for their mission requirements. NASA will be the single interface to US Strategic Command on behalf of the

Contractor for all items not related to Range Safety.

The Contractor shall make arrangements for Range-provided services and commodities necessary to support the logistics service.

3.2 PROGRAM MANAGEMENT

For all missions under this contract, the Contractor shall provide program management functions required to deliver the logistics services and satisfy the mission requirements for each NASA mission. The program management function of this contract shall provide NASA insight for all technical and programmatic activities performed under this contract, and shall participate as requested in meetings (e.g., technical interchanges, panels, boards, working groups).

The Contractor shall provide an Integrated Master Schedule (IMS) per DRD GLS-001.

The Contractor shall coordinate all program management functions and issues directly with the

NASA designated representative(s). The NASA Contracting Officer is the only NASA representative authorized to provide formal contract direction.

3.2.1. PROGRAM MANAGEMENT REVIEW

During the contract performance period, the Contractor shall conduct a Program Management

Review (PMR) with NASA at least twice per year formally report on development and production status, ensure schedules support program objectives, review action items, review program schedules, describe extensibility of vehicle capabilities (including the Contractor’s ability to deliver other Elements of Gateway), and discuss any issues. The Contractor shall describe contemplated and implemented changes to the launch and logistics vehicles in sufficient detail for

NASA to determine if the changes constitute a Common GLS Configuration Change. The intent of the PMR is to provide a forum for open dialog between NASA and the Contractor with respect to overall end-to-end contracted missions. NASA will provide status of Agency direction at the reviews. The review location shall alternate between NASA and Contractor facilities unless mutually agreed upon to do otherwise.

3.2.2. FORMAL REVIEWS

The Contractor shall conduct program reviews, design reviews, and readiness reviews, and shall provide for the participation of NASA. The Contractor shall provide minutes and action items resulting from each review to NASA within one week after the review.

Specific detailed formal reviews are included in section 4.4 and section 6.4.

3.3. MISSION INTEGRATION MANAGEMENT

The Contractor shall perform mission integration tasks in accordance with DRD GLS-003, Mission Integration and Operations Management Plan (MIOMP).

The Contractor shall provide Work Plan status and updates at the program reviews, if necessary, when mission schedules change. This work plan shall identify the Contractor’s major milestone events applicable to each mission and provide a corresponding narrative of the work activity necessary to accomplish the major milestone events for each mission.

The Contractor shall perform the following:

(a) Provide a single point of contact with overall mission responsibility for each mission. The single point of contact shall coordinate support from all technical disciplines and management during the integration process.

(b) Provide a focal point to work technical details for unpressurized cargo for each flight

(vehicle layout, FSE, Interface Control Documents (ICDs), analytical products, schedules, etc.)

(c) Provide a focal point to work technical details for pressurized cargo for each flight (cargo layout, powered lockers, unique cargo accommodations, ICDs, analytical products, schedules, etc.)

(d) Conduct mission integration meetings as proposed in DRD GLS-003, Mission Integration and Operations Management Plan (MIOMP) to successfully plan, schedule, and manage mission analyses required to define and verify compatibility of the cargo with the interface requirements and environments.

(e) Track development status of and resolve issues associated with mission specific hardware and software.

(f) Manage the design, development, qualification, testing and integration of mission unique requirements.

3.4. MISSION ANALYSIS

The Contractor shall perform the mission planning and analyses necessary to provide the data for logistics vehicle and Gateway integrated performance. This planning and analysis shall encompass all phases of the mission. The Contractor shall develop and submit the initial DRD GLS-106, Mission Resource Allocation Document (MRAD), for each mission. The Initial MRAD shall contain current analytical data related to: electrical power and energy, command and data requirements, logistics vehicle dynamics and mass properties, docking requirements and robotics requirements (if applicable), logistics vehicle Computer-Aided Design (CAD) models, logistics vehicle structural math model, logistics vehicle thermal model, plume history, thruster firing history, propellant types, and mission specific analysis for unpressurized cargo. The Contractor shall also submit logistics vehicle CAD models for each mission per DRD GLS-107, Engineering

Computer-Aided Design (CAD) Models, and logistics module and integrated assembly mass properties for each mission per DRD GLS-011, Mass Properties Data.

3.5. MISSION OPERATIONS

The Contractor shall perform all functions necessary to provide end-to-end flight control operations for the logistics vehicle including ground segment interfaces, compatibility testing, cargo operating procedures, malfunction procedures, timelines, simulation support, real-time support and crew/back-up crew training.

The Contractor shall participate in technical interchange meetings, working groups, and operational boards and reviews.

3.5.1 GROUND SEGMENT OPERATIONS

The Contractor’s control center shall interface with the NASA Mission Control Center (MCC).

The Contractor shall participate in the development of joint operations products. This will include providing documentation for the ground system specifications and the standard interfaces with the

NASA MCC.

The Contractor’s control center shall provide the necessary systems to control and monitor the logistics vehicle during the free-flight, approach, docked, and disposal mission phases. The

Contractor’s control center shall provide the necessary interfaces to the NASA MCC and other entities the ability to monitor and exchange telemetry as required for mission success and safety.

Contractor ground segment operations shall be consistent with DRD GLS-003, Mission Integration and Operations Management Plan (MIOMP).

3.5.2 SECURITY REQUIREMENTS

Contractor Information Technology (IT) and Operational Technology (OT) systems which store, process, or disseminate NASA information shall comply with NPR 2810.1, as described in DRD

GLS-014, Information Technology (IT) System Security Documents (ITSSDs).

Contractors who have a requirement to access Personal Identity Verification (PIV)-Authenticated

NASA information systems shall obtain the NASA PIV badges and NASA identities as required in clause 2.2.31, Kennedy Space Center Badging Issuance and Identity Verification Process.

3.5.3 TECHNICAL IMAGERY

Photo documentation of logistics vehicle interfaces, pressurized cargo, and unpressurized cargo before, during, and after integration shall be in accordance with DRD GLS-015, Technical Imagery

Plan.

3.5.4 TRAINING AND OPERATIONAL PRODUCTS FOR INTEGRATED MISSION

OPERATIONS

The Contractor shall work with NASA on integrated mission joint flight products and operations.

The overall Mission Operations planning shall be as outlined in DRD GLS-003, Mission

Integration and Operations Management Plan (MIOMP). The Contractor should refer to training and operational product details in JSC 35089, Visiting Vehicle Operations Document, and SSP

50808, paragraph 3.4.5, Training and Operational Products for Integrated Operations. Key areas are defined below.

3.5.4.1 MISSION FLIGHT PROCEDURES

The Contractor shall support and review development of joint flight products. The Contractor specific mission products shall be documented in NASA maintained documentation such as Flight

Rules, Operational Interface Procedures, vehicle and systems manuals, procedures and protocols.

3.5.4.2 MISSION TRAINING

The Contractor shall provide generic and mission specific training, including mission simulations, training models, and mockups to NASA flight and ground crew/back-up crew.

The Contractor, with NASA input and coordination, shall develop a mission specific crew training plan . The Contractor shall provide flight crew/back-up crew and ground personnel training sessions at the provider facility or NASA facility.

3.5.4.3 MISSION SIMULATION SUPPORT

The Contractor shall participate in six to eight joint simulation training events per mission. NASA will conduct the events from the NASA-Johnson Space Center (JSC) training facilities and MCC to perform integrated mission training for each mission.

3.5.4.4 REAL-TIME MISSION SUPPORT

The Contractor shall support real-time mission operations for each Gateway logistics service mission by providing technical expertise and on-console support during integrated operations with

Gateway.

The Contractor shall provide the appropriate level of support and technical expertise to respond to

Mission Action Requests, real-time flight rule changes, and any anomalies or contingencies during integrated operations with Gateway.

The Contractor shall provide support during quiescent phase of the mission to respond to crew or flight controller questions and issues.

NASA will have mission authority and oversight during integrated operations with Gateway.

3.6 RISK MANAGEMENT

The Contractor shall implement a risk management program with techniques that address the identification, analysis, mitigation, and closed-loop tracking of potential impacts to safety, technical performance, cost, and schedule. The Contractor shall develop the criteria, methods, and procedures used for identifying risk items. Delays that result from the Contractor’s business judgment or as a result of the Contractor’s business decisions involving risk are not considered beyond the reasonable control of the Contractor.

The Contractor shall present the status and mitigation plan of all open risk items at program and technical reviews.

The Contractor shall make its risk tracking information systems remotely accessible to select

NASA personnel at NASA Centers. This is to provide insight to current mission risks, including a brief description, subsystems affected, status of ongoing root cause evaluation, mitigation efforts, and how the risk is being evaluated for impacts to upcoming flights.

3.7 SAFETY AND MISSION ASSURANCE

The Contractor shall establish, implement, and maintain comprehensive safety, quality, and reliability programs covering program management, mission integration management, and the design, development, production, test, integration, launch, flight, and mission operations of the logistics vehicle. The Contractor’s Safety and Mission Assurance Programs, Plans, and Analyses shall use DSG-RQMT-010, Gateway Safety and Mission Assurance Requirements, as a guide.

3.7.1 SAFETY PROGRAM

The Contractor shall develop and provide safety documentation, plans, procedures, technical analyses, etc. in accordance with applicable safety requirements of the Gateway and consistent with Federal, State, and Local government requirements at the launch processing site. Launch processing site, FAA, and Range safety required documentation shall be made available to NASA upon request in accordance with DRD GLS-008, Safety Documentation Required by Non-NASA

Entities. When performing work in a NASA-owned facility, the Contractor shall adhere to applicable NASA safety requirements. When requested by NASA, the Contractor shall submit safety documentation (baseline and any changes) to NASA for review/approval in accordance with

DRD GLS-009, Safety Documentation Required for Processing in NASA Provided Facilities.

NASA will review the safety documentation to ensure designs, processes, and operations do not pose an unacceptable risk to NASA personnel/contractors/partners, resources, or mission success.

The Contractor shall report Close Calls and Mishaps to NASA in accordance with DRD GLS-005, Mishap Notification, Investigation and Mishap Preparedness, and Contingency Plan.

3.7.1.1 SAFETY AND HEALTH PLAN

The Contractor shall provide a Safety and Health Plan that will implement safety and health requirements consistent with federal, state, and local government regulations and applicable

Gateway and launch processing site Safety and Health requirements as described in DRD GLS-

004, Safety and Mission Assurance Plan(s). A System Safety plan shall be included as part of the

Safety and Health plan, or as a standalone document.

3.7.1.2 SYSTEM SAFETY REQUIREMENTS

The Contractor shall partner with NASA to tailor DSG-RQMT-011, Gateway Program Hazard

Analysis Requirements, for use relating to the logistics service. This tailoring effort will result in a document that contains a phased safety review process and hazard analysis requirements. The

Contractor shall place the resulting document under configuration control, and NASA shall have approval authority for final tailoring and for any changes.

The Contractor shall comply with the phased safety review process detailed in the tailored DSG-

RQMT-011. The phased safety review process shall be performed for the Initial GLS Mission and

Specialized Missions. The Contractor shall provide a Safety Data Package at each phase in accordance with DRD GLS-006, Safety Data Package (SDP), for NASA to review. For subsequent flights, the Contractor shall update the Safety Data Package to incorporate vehicle and operational changes and participate in the safety review process in accordance with the tailored DSG-RQMT-

011. NASA shall have approval authority of the final Safety Data Package for all missions.

The Contractor shall perform Hazard Analysis for the logistics vehicle within the Gateway

Rendezvous Sphere in accordance with the tailored DSG-RQMT-011. The Contractor shall provide the Hazard Analysis and Hazard Reports as part of safety data package described in DRD

GLS-006, Safety Data Package (SDP). NASA shall have approval authority for all operational hazard controls within the Gateway Rendezvous Sphere. The Contractor shall review program-only causes identified in the Cross Program Integrated Hazard Analysis and document their inclusion and mitigation in the logistics vehicle Hazard Analysis.

The Contractor shall document Failure Modes and Effects Analysis/Critical Items List

(FMEA/CIL) for the logistics vehicle within the Gateway Rendezvous Sphere through disposal and include the data required by DSG-RQMT-012, Gateway Program Failure Modes and Effects

Analysis and Critical Items List (FMEA/CIL) Requirements at a minimum. The Contractor shall provide FMEA/CILs as part of the safety data package described in the DRD GLS-006, Safety

Data Package (SDP). Critical Items shall be subjected to identification and data retrieval requirements, including detailed identification to their origin (e.g. manufacturer, materials, manufacturing date, purchased lot, inspection or test data), specific tests performed, test results, processes utilized, or other pertinent information.

3.7.1.3 OPERATIONS SAFETY REQUIREMENTS

The Contractor shall comply with range safety requirements and processing site requirements.

Contractor items provided to NASA (e.g. training mockups, simulators) shall meet applicable

NASA Center facility and safety requirements.

Prior to any hazardous operation involving NASA property or NASA personnel, the Contractor shall develop a hazardous operating procedure and perform a Test Readiness Review (TRR) or

Operational Readiness Inspection (ORI) prior to performing the operation.

The Contractor shall allow NASA participation in readiness reviews, tests, or operations involving

NASA property or NASA personnel.

When performing critical lifts of NASA hardware, the Contractor shall meet or exceed NASA-

STD-8719.9B, NASA Lifting Standard, Appendix B or a NASA approved equivalent lifting standard. Lifting operations shall be classified as critical when failure/loss of control presents an elevated risk of serious injury or death, loss of one-of-a-kind or high-dollar items, or damage to major facility components whose loss would have serious programmatic impact.

When launching radiological materials, the Contractor shall comply with the requirements of NPR

8715.3D, NASA General Safety Program Requirements, Chapter 6.

3.7.1.4 CARGO AND PAYLOAD SAFETY

The Contractor shall provide an integrated cargo assessment as part of DRD GLS-006, Safety Data

Package (SDP) to ensure that the hazards introduced by cargo and payloads have been adequately controlled. NASA will provide the Contractor with a safety assessment of each cargo bag and payload manifested to support the Contractor’s integrated cargo safety assessment. For co-manifested non-NASA cargo and payloads, the Contractor shall perform a safety assessment in accordance with the tailored DSG-RQMT-011, and shall obtain approval from NASA. Non-NASA cargo and payloads shall also be included in the Contractor’s integrated cargo safety assessment.

3.7.1.5 PARTICIPATION IN SAFETY WORKING GROUPS

The Contractor shall participate in applicable Gateway program level safety working groups and safety reviews (e.g. Gateway and Cargo Safety Reviews, Integrated Hazard Analysis, Failure

Modes and Effects Analysis, Crew Survivability Analysis, and Probabilistic Risk Assessment) as the logistics service safety representative for each mission under this contract.

3.7.1.6 PRESERVATION OF THE SPACE AND LUNAR ENVIRONMENTS

For space vehicles and vehicles/stages that enter the lunar sphere of influence or the vicinity of an

Earth-Moon Lagrange point, the Contractor shall comply with NPR 8715.6B, Procedural

Requirements for Limiting Orbital Debris and Evaluating Meteoroid and Orbital Debris

Environments, in accordance with DRD GLS-007, Orbital Debris Assessment and End of Mission

Disposal Plan. Orbital Debris requirements for space vehicles and vehicles/stages outside the lunar sphere of influence or the vicinity of an Earth-Moon Lagrange point fall under the authority of the

FAA.

The Contractor shall provide to NASA, prior to launch, an inventory of all Contractor-provided biological and organic materials on vehicles destined for the Gateway as described in DRD GLS-

007, Orbital Debris Assessment and End of Mission Disposal Plan.

3.7.2 QUALITY ASSURANCE PROGRAM

The Contractor shall provide a Quality Plan in accordance with DRD GLS-004, Safety and Mission

Assurance Plan(s) that will implement quality requirements consistent with aerospace industry practices.

The Contractor shall maintain a quality management system that is AS9100, Quality Management

Systems – Requirements for Aviation, Space, and Defense Organizations, compliant. The

Contractor shall accommodate NASA participation in Contractor and subcontractor audits and

AS9100 audits. NASA insight will consist of monitoring audits with the Contractor’s auditors and inspectors in order to provide understanding of the Contractor’s quality system and insight of their processes.

The Contractor shall make available to NASA a current Audit Plan and schedule for in-house and contractor audits upon request from NASA. The Contractor shall make available to NASA both the Contractor performed internal Quality Audit Reports and the subcontractor/vendor Quality

Audit Reports as described in DRD GLS-004, Safety and Mission Assurance Plan(s).

The Contractor shall provide insight of Material Review Board (MRB) and failure reporting for all logistics vehicle open and closed nonconformances. The Contractor shall provide read-only quality information to NASA (via remote computer access) wherein such Quality Assurance online information systems exist and to which the Contractor has regular and timely input. An example is an online Problem/Failure Reporting system.

The Contractor shall identify all nonconformances that affect the form, fit, or function of the logistics vehicle to Gateway Interface, including but not limited to: propulsion, mechanical, electrical, software, radio frequency (RF), environmental, and communication/telemetry components.

The Contractor shall make available to NASA an As Built Configuration List (ABCL) of each logistics vehicle for NASA review.

The Contractor and its major subcontractors shall participate in the Government/Industry Data

Exchange Program (GIDEP).

3.7.3 RELIABILITY PROGRAM

The Contractor shall provide a Reliability Plan, as part of DRD GLS-004, Safety and Mission

Assurance Plan(s), that establishes a robust Reliability Program as an integral part of the entire lifecycle. The Contractor’s reliability program and analyses shall facilitate evaluation of the

Contractor and subcontractor’s programs to determine if the logistics service meets quantitative reliability requirements. Overall vehicle reliability predictions shall be provided to NASA as part of the DRD GLS-006, Safety Data Package (SDP) deliveries and shall be incrementally revised to reflect design modifications.

3.7.4 PROBABALISTIC RISK ASSESSMENT (PRA)

The Contractor shall provide technical information in support of the PRA to be performed by the

NASA Gateway Program. In addition to DRD information, the Contractor shall support the

Gateway PRA analyses. This support information shall include (but not be limited to) a detailed description of the logistics vehicle architecture, ConOps (concept of operations), logistics vehicle critical functions, component functions, and functional flow diagrams.

3.7.5 SOFTWARE ASSURANCE PROGRAM

The Contractor shall establish and maintain a Software Safety and Mission Assurance Plan

(SSMAP) as a standalone document or part of other S&MA plans as described in DRD GLS-004, Safety and Mission Assurance Plan(s). The Contractor shall have a Software Quality Management system in accordance with AS9115, Quality Management Systems – Requirements for Aviation, Space and Defense Organizations - Deliverable Software (Supplement to AS9100) and a Software

Assurance Plan in accordance with IEEE 730-2014 Standard for Software Quality Assurance

Processes. Safety Critical Software shall be in accordance with NASA-STD-8719.13C, NASA

Software Safety Standard.

The Contractor shall provide read-only Software Assurance information to NASA (via remote computer access) wherein such online information systems exist and to which the Contractor has regular and timely input in the form of software change requests, problem reports, and corrective actions.

3.8 CONFIGURATION MANAGEMENT

The Contractor shall perform configuration management in accordance with AS9100, Quality

Management System – Requirements for Aviation, Space, and Defense Organizations.

3.9 SCHEDULING

The Contractor shall develop and maintain mission specific schedules that contain an end-to-end cargo and vehicle integration schedule in accordance with DRD GLS-001, Integrated Master

Schedule (IMS).

3.10 PUBLIC RELATIONS

The Contractor shall maximize opportunities to inspire and engage with the public in a partnership with NASA as part of GLS missions operations.

These areas shall include, at a minimum, guest operations, publications, social media, imagery, and educational engagement.

4.0 GATEWAY LOGISTICS SERVICE (GLS) MISSIONS (CLIN 1)

In addition to requirements in section 3.0 the following requirements apply to both Initial and

Standard GLS missions as ordered under CLIN 1.

4.1 REQUIRED CAPABILITY

The Contractor shall provide for the safe integration, transport and stowage of NASA-provided cargo, both pressurized and unpressurized, to the Gateway and disposal of NASA-provided cargo upon departure from the Gateway. The Contractor’s logistics vehicle shall be designed to remain docked to Gateway for one (1) year, with efficient crew access to stowage and payloads but the capability to remain longer than one year should also be considered. The nominal mission docked duration is expected to be six months. . The common launch vehicle configuration shall have one

(1) successful flight prior to the GLS Missions.

4.1.1 REQUIRED CAPABILITY – PRESSURIZED CARGO DELIVERY

4.1.1.1 Contractor shall provide a capability to deliver a minimum of 3,400 kg of pressurized cargo to the Gateway within the overall constraints as defined in GLS-

RQMT-001.

4.1.1.2 Contractor shall provide a usable pressurized volume area for cargo. Useable pressurized cargo volume is defined as the volume which can accommodate

Logistics cargo and payloads types as defined in GLS-RQMT-001.

4.1.1.3 The pressurized volume of the Logistics Vehicle shall accommodate cargo, handed over by NASA, as powered or unpowered payloads in standard hard-mounted single Middeck Lockers (MDLs), double MDLs (or equivalent powered payloads) or as passive cargo, handed over in multiple types of standard soft stowage Cargo

Transfer Bags (CTBs) or alternative passive cargo stowage system as specified in

GLS-RQMT-001.

For reference, the sizes, mass properties, resource interfaces, environmental requirements and strapping/attachment interfaces for the MDL and CTB cargo and payloads are provided in SSP-50833, International Space Station Program Cargo Transport

Interface Requirements Document, and may be used as a guideline. Note, typical

ISS cargo packing density for CTBs is approximately 290 kg/m3. .

4.1.1.4 Contractor shall accommodate alternate interfaces for Gateway cargo and payloads, as specified in GLS-RQMT-001. In order to optimize the cargo delivery service, the Contractor may propose an alternative cargo stowage system to increase packing and Gateway operational efficiency. NASA will provide additional interface requirements when the manifest is delivered for mission specific cargo and payloads that utilize alternative or new interfaces and designs.

4.1.1.5 Cargo Accessibility: The cargo and payloads delivered to the Gateway shall be organized, readily accessible and easy to use by the crew at the Gateway, as specified in GLS-RQMT-001.

4.1.1.6 The Pressurized Volume Area shall allow for the safe translation and mobility of crew to perform expected cargo access, transfer and handling tasks as well as trash stowage tasks as specified in GLS-RQMT-001.

4.1.1.7 The Contractor shall accommodate initial pressurized passive cargo handover at L-

30 days, with the exception of up to 500 kg. The remaining passive cargo will be handed over at no later than the latest time defined in the Cargo hand-over load schedule in the GLS Space System Architecture contract attachment.

4.1.1.8 The Contractor shall accommodate pressurized powered payload handover of at least two and up to six powered double MDL-equivalent payloads, which may be comprised of at least four and up to twelve single MDL-equivalent payloads. The powered payloads will be handed over at the latest time defined in the Cargo hand-over load schedule in the GLS Space System Architecture contract attachment.

4.1.1.9 The Contractor shall provide a controlled environment for pressurized cargo & payloads from the time of handover on the ground, until the time of offloading from the Logistics Vehicle to the Gateway, as specified in GLS-RQMT-001.

4.1.1.10 The Contractor shall provide telemetry data from powered payloads and the capability to command powered payloads after handover, during transit and while docked to the Gateway as specified in GLS-RQMT-001, with minimal periods of interruption.

4.1.2 REQUIRED CAPABILITY - PRESSURIZED DISPOSAL

4.1.2.1 The Logistics Vehicle shall provide a minimum usable pressurized cargo disposal mass and volume that is equivalent or greater to that provided for pressurized mass and volume delivery as specified in GLS-RQMT-001.

4.1.2.2 The Logistics Vehicle shall provide stowage volume, attach points, and restraint systems within the pressurized volume for contained trash as specified in GLS-

RQMT-001.

4.1.2.3 While docked and prior to departure, the pressurized volume of the Logistics

Vehicle designated for trash stowage shall be organized, readily accessible and easy to use by the crew at the Gateway as specified in GLS-RQMT-001.

4.1.2.4 The pressurized volume of the Logistics Vehicle designated for trash stowage shall be kept separated from the cargo and payloads as specified in GLS-RQMT-001 until the cargo or payloads are permanently removed prior to departure.

4.1.2.5 The Pressurized Volume Area shall allow for the safe translation and mobility of crew to perform expected trash stowage tasks as specified in GLS-RQMT-001.

4.1.3 REQUIRED CAPABILITIY - UNPRESSURIZED CARGO DELIVERY AND

DISPOSAL MASS

4.1.3.1 Contractor shall provide a capability to deliver a minimum of 1,000 kg of unpressurized cargo to the Gateway within the overall constraints as defined in

GLS-RQMT-001.

4.1.3.2 The Contractor shall provide disposal of unpressurized cargo, up to a disposal mass that is equivalent or greater to that provided for unpressurized upmass delivery.

4.1.3.3 The Contractor shall provide cargo and payload services and interfaces to transport unpressurized cargo as specified in GLS-RQMT-001.

4.1.3.4 The Contractor shall provide power, telemetry data, and the capability to command unpressurized payloads after hand-over, during transit and while docked to the

Gateway as specified in GLS-RQMT-001, with minimal periods of interruption.

4.1.3.5 The Contractor shall provide a capability to maintain the thermal environment of unpressurized cargo in the range from -50 deg C (-58 deg F) to +50 deg C (+122 deg

F) during transit to the Gateway. Methods to control environment may include attitude control during transit, enclosures or other active or passive means.

4.1.3.6 The Contractor shall provide the necessary services and hardware including Flight

Support Equipment (FSE), if required, to integrate the cargo to the unpressurized volume of the visiting vehicle as specified in GLS-RQMT-001.

4.1.3.7 For payloads that are intended for handling by the Gateway Extravehicular

Robotics (EVR) System the Contractor shall accommodate EVR-compatible inerfaces as specified in GLS-RQMT-001 and CSA-GWY-ID-0001 to allow unpressurized cargo to be robotically manipulated for transfer between the unpressurized volume and Gateway while not requiring Extravehicular Activity

(EVA).

4.1.3.7.1 For Small Orbital Replacement Unit (ORU) Robotic Interface (SORI) based unpressurized cargo, the Contractor shall accommodate the minimum volume and mass for each SORI-based payload or ORU to be transported to Gateway per CSA-GWY-ID-0001.

4.1.3.7.2 For Large ORU Robotic Interface (LORI) based unpressurized cargo, the

Contractor shall:

a. Accommodate a minimum of 210kg (150kg for the payload/ORU and 60kg for the LORI) for each LORI-based payload or ORU to be transported to Gateway.

b. Accommodate a minimum volume of 1200 x 650 x 650 mm

(payload/ORU volume and LORI volume) for each LORI-based payload or ORU to be transported to Gateway.

4.1.3.7.3 The Contractor shall provide a clearance envelope around the unpressurized cargo as per Figure 4.3 in CSA-GWY-ID-0001 that is clear of intrusions such that each payload or ORU can be robotically manipulated when docked to Gateway.

4.1.3.7.4 4.1.3.7.4 The Contractor shall provide a clearance envelope around the unpressurized cargo as per Figure 4.3 in CSA-GWY-ID-0001 that is clear of intrusions such that each payload or ORU can be robotically manipulated when docked to Gateway. The Contractor shall provide the capability to command the release of the SORI/LORI launch latches when docked to Gateway.

4.1.3.8Access shall be provided to unpressurized cargo up to the latest time defined in the

GLS Space System Architecture contract attachment, nominally L-4 days, for final pre-launch cargo preparation, as specified in GLS-RQMT-001.

4.2 CARGO INTEGRATION

The Contractor shall safely integrate NASA cargo into the logistics module and/or unpressurized carriers. NASA will provide packed pressurized cargo to the Contractor. NASA will provide unpressurized cargo without flight support equipment to the Contractor. The Contractor should consider approaches that provide flexibility for assignment, reassignment, packing, and repacking of cargo and payloads by Gateway crew. The Contractor should consider approaches that provide flexibility for post Vehicle Baseline Review (VBR) changes to the unpressurized cargo manifest.

4.2.1 CARGO ANALYSIS AND INTEGRATION

The Contractor shall perform the analysis and integration tasks required to safely integrate pressurized and unpressurized cargo for delivery to and disposal from the Gateway consistent with

DRD GLS-003, Mission Integration and Operations Management Plan (MIOMP) and DRD GLS-

106, Mission Resource Allocation Document (MRAD).

The Contractor shall submit a DRD GLS-103, Vehicle Interface Definition Document (IDD) which will describe the standard interface requirements, capabilities, interfaces, constraints, and environments of the launch and logistics vehicles, as they pertain to pressurized and unpressurized cargo. NASA will use this data to assess the compatibility of NASA cargo with the launch and logistics vehicles.

NASA will provide the Contractor with the preliminary unpressurized cargo complement No Later

Than (NLT) L-24 months and a notional pressurized cargo complement NLT L-13 months (for the first GLS mission only). The Contractor shall perform an assessment of the total cargo complement (NASA-sponsored and Contractor-provided) at the individual cargo item level, assessing resource requirements to validate that vehicle resources are adequate to ensure safe delivery of the cargo complement.

The pressurized cargo complement will define a representative manifest consisting of distribution of standard cargo units and masses consistent with the logistics module capability, the number of powered and unpowered cargo containers, and pressurized cargo or payloads that require special accommodation such as hard mounting. For cargo requiring hard mounting, the associated resource, operational, interface verification, ground processing requirements, and orientation constraints will also be provided at this time.

NASA will provide an updated pressurized cargo launch complement NLT L-5 months. This complement will be more defined in nature, but is still considered preliminary.

At L-6 weeks, NASA will provide the final pressurized cargo launch complement to reflect the as-packed cargo for turnover to the Contractor at L-30 days. At L-2 weeks NASA will update the cargo launch complement to reflect changes to manifest for cargo turned over at the time defined in the GLS Space System Architecture contract attachment.

At each cargo complement delivery time point, NASA will identify cargo items that will have special handling, orientation, and early crew access requirements.

The Contractor shall perform the following:

(a) Analyses of all cargo test and analytical data as it pertains to the physical (structural) and environmental (thermal, acoustics, electromagnetic interference and compatibility

[EMI/C]) interfaces with the logistics vehicle. Structural verification shall be performed using the maximum mass capability for the cargo types as defined in GLS-RQMT-001.

(b) Perform mission specific structural, thermal, and functional assessments (including power and data) to ensure the feasibility of the configuration for each mission.