Artemis IV Alternate Communication System

Overview: The National Aeronautics and Space Administration (NASA) is seeking information from U.S. and international commercial providers on support for the Artemis IV mission. NASA is particularly interested in innovative, secondary communications capabilities that can enable robust, high rate data return from the Orion crew vehicle during operations in lunar orbit. This Request for Information (RFI) is issued by NASA’s Artemis Program Office, and aims to identify mature services and user terminals that can augment Orion’s primary communication system. Respondents are invited to submit end-to-end system concepts that could provide continuous, high bandwidth transmission of mission data in the dynamic lunar environment and contribute to the success of crewed space exploration under the Artemis program. RFI Overview: 2.1 The Artemis IV Mission: The Artemis IV mission will launch crew in the Orion spacecraft atop the Space Launch System (SLS) rocket to rendezvous with the Human Landing System (HLS). Once docked crew will transfer from Orion to the lunar lander for transportation to the surface of the Moon. Orion will remain in lunar orbit until HLS returns from the lunar surface and crew transfer back to Orion for return to Earth. The Artemis IV mission profile is still being finalized. For the purposes of responses to this RFI, the following Ground Rules and Assumptions can be considered: • Artemis IV launch no later than March 2028 • Orion will travel to a lunar orbit • Non-Critical (Crit 3) Application 2.2 Service and Integration Expectations: With the Artemis IV mission profile occurring in a lunar orbit, Orion’s primary communication system is challenged to provide a high-rate system capable of streaming live 4k imagery. To meet these demands, a secondary communications system is being evaluated for inclusion in the Artemis IV Orion configuration. It is anticipated that, to meet these requirements, the system must provide near continuous communication with a return link of at least 12 Mbps, while in a lunar orbit. Given the short timeline and availability of hardware, ease of integration into the Orion vehicle is a significant consideration. Performance Objectives: Near continuous communication (goal: > 75%) > 12 Mbps Downlink (goal: 20-50Mbps) > 500 kbps Uplink (Desired to support Class 2 CFDP, not a system requirement) System must provide a broad field of regard or steerable antenna/aperture Orion has many driving attitude constraints so precise vehicle pointing of a fixed antenna/aperture is not available Orion Vehicle Integration: Given the short timeline, ease of integration into the Orion vehicle is a significant consideration. Key design parameters include: Data Interface: Ethernet or WiFi Hardware Control & Telemetry Interface: Ethernet or WiFi Power Interface: 120 VDC (preferred) or 28 VDC, < 150W max (goal) Mass: < 50kg (goal) Max Volume: 32” x 20” x 18” (goal) Implementation Options: Both internally configured and externally mounted implementations will be considered. If the schedule outlined below proves untenable, please provide a revised hardware delivery schedule that can be met. Parameters if externally mounted on Orion Crew Module Adapter Mounted under Service Module (SM) fairing during launch Assumes system is a single assembly, mounted on a plate or pallet No active cooling Engineering Hardware delivery needed by December 2026. Flight Hardware delivery needed by March 2027. Location is not accessible after SM fairing installation during I&T Assume typical launch vehicle and LEO environments Parameters if internally configured by Orion crew Stowed during launch and setup by the crew Multiple separate components can be assumed Assume antenna placed against window, not integrated into spacecraft Flight Hardware delivery needed in fall 2027. Crew cabin can be accessed later in I&T flow than Service Module Assume soft stow launch and pressurized cabin environments Testing: It will be essential to perform Spacecraft (End to End) data flow test prior to launch