Network Extension for User Continuity and Sustainability (NEXUS) Ka-Band Backward-Compatible Relay Broad Agency Announcement (BAA) NextSTEP-3 Appendix E - Final Solicitation

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

Notice type
Solicitation
Solicitation #
SCAN-MSFC-0001
NAICS
541715
PSC
AR12
Posted
June 18, 2026
Response due
July 7, 2026
Place of performance
Huntsville, AL

What this opportunity is

NASA is seeking proposals for the Network Extension for User Continuity and Sustainability (NEXUS) Ka-Band Backward-Compatible Relay under a Broad Agency Announcement. This opportunity falls under NAICS 541715 and is open to all businesses, as there is no set-aside. Interested contractors must have valid ITAR/EAR export clearance to access the technical data included in the solicitation, and they should be prepared to submit proposals by July 7, 2026, as no extensions will be granted for delays in obtaining necessary clearances.

Analysis by Mindy, grounded in the SAM.gov notice.

Description

Network Extension for User Continuity and Sustainability (NEXUS) Statement of Objectives (SOO) 1. PURPOSE The purpose of this Statement of Objectives (SOO) is to define mission objectives, measurable performance outcomes, and constraints that enable industry to propose commercially scalable, technically credible, secure solutions. This SOO establishes what must be achieved through demonstration to validate service readiness and inform transition to sustained commercially provided relay services. NEXUS is intended to validate not only technical compatibility, but also the Offeror’s ability to deliver assured mission support for Government users through reliable service availability, operational continuity, effective prioritization, and a credible path to sustained relay services. The demonstration must also provide NASA with confidence that the proposed approach can scale on a schedule that supports incremental sustained service availability beginning in 2029 and progression toward full operational capability by mid-2031. Terminology Note: For purposes of this SOO, the terms Offeror, Provider, and Vendor refer to the entity submitting a proposal in response to this solicitation. The terms customer vehicle, customer platform, customer control center, user, legacy user, and TDRS user refer, as applicable, to the existing NASA or Government missions, spacecraft, platforms, ground control elements, or user organizations currently supported by TDRS-based relay services. 2. DEMONSTRATION MISSION OBJECTIVES The objectives and outcomes of this demonstration phase are critical to validating a viable solution for long-term commercially provided relay services supporting NASA and other legacy Government missions. The key objectives for the NEXUS on-orbit demonstration include: • Protect continuity of legacy Government missions operating within defined TDRS Ka- band spectral ranges without requiring modification to customer vehicle onboard systems. • Demonstrate an operationally viable on-orbit relay service using a representative implementation of the proposed sustained-service architecture. • Obtain NASA Authority to Connect (ATC) prior to beginning the on-orbit performance measurement period. ATC indicates that the demonstrated NEXUS service is ready for a designated Government user or users to connect to the service. • Complete an initial on-orbit demonstration that includes a minimum 30-calendar-day on-orbit performance measurement period using the proposed backward-compatible Ka- band relay capability. • Execute end-to-end concurrent forward and return relay services, including scheduling, service activation, data delivery, monitoring, and full relay between the customer platform and the Ground Service Interface. • Verify applicable service requirements and validate performance, coverage, concurrency, handovers where applicable, and operational execution through on-orbit demonstration across the required space, ground, network, scheduling, user, and Ground Service Interface elements. -- 1 of 14 -- • Generate sufficient technical, operational, schedule, cost, user-integration, and service-assurance data to inform future Government decisions regarding sustained relay services and NASA’s assessment of long-term assured mission delivery. • Enable service readiness within a timeframe acceptable to maintain legacy service availability. 3. REQUIRED PERFORMANCE OUTCOMES The Offeror must demonstrate compliance with functional and performance outcomes sufficient to validate backward-compatible relay service capability. This SOO establishes NASA’s objectives, required outcomes, and operational context for the NEXUS demonstration. Detailed functional, performance, interface, and verification requirements for the full service are contained in Attachment A.2, NEXUS Service Requirements Document (SRD). Offerors proposed concept must comply with the SRD in its entirety and demonstrate an increment of the concept. In the event of an inconsistency between the SOO and SRD, the SRD will govern technical requirements. The Offeror must deliver verification evidence against applicable requirements and, through an on-orbit demonstration, provide validation of capability that is applicable and scalable to a full backward-compatible Ka-band service. NASA requires sufficient information to evaluate demonstrated performance, service assurance, scalability, operational readiness, and the remaining work needed to transition to sustained service, consistent with applicable data-rights and proprietary information protections. Verification and Validation compliance will be approved by NASA. The Offeror must describe its verification philosophy, including the planned use of analysis, test, inspection, demonstration, heritage data, ground testing, and on-orbit validation. The Offeror must identify how verification limitations, deviations, waivers, or residual verification risks will be documented and submitted for NASA review and approval prior to demonstration execution. The specific requirement areas are summarized in the following subsections. Detailed functional requirements, performance thresholds, and technical parameters are defined in Attachment A.2. Requirement Driver Information: Offerors must propose solutions that meet all stated SRD requirements, which are intended to preserve backward compatibility with current TDRS users. Offerors may identify any SRD requirements that materially affect feasibility, schedule, technical complexity, risk, or pricing, and may provide the requirement number and title, Offeror interpretation, assumptions, supporting rationale, quantified impact, and any proposed alternative value, approach, or implementation concept. Submission of proposed alternatives or requirement impact information does not revise, waive, relax, or trade any SRD requirement or any other solicitation term, condition, evaluation criterion, schedule milestone, or fixed requirement. NASA may use this information to u

Source: SAM.gov, as posted. Verify the current solicitation before responding.

Pursue this opportunity with Mindy

See who holds it now, who else is bidding, and draft your response — grounded in real government data, not generic AI.

View the original notice on SAM.gov ↗

Similar Active Opportunities (NAICS 541715)