_NextSTEP-3 APPENDIX E_NEXUS BC Ka-Band Relay BAA_80MSFC26R0006.pdf

National Aeronautics and Space Administration NASA

Space Communications and Navigation (SCaN) Program

300 E ST SW

Washington, D.C. 20546-0001

NextSTEP-3 APPENDIX E: Network

Extension for User Continuity and

Sustainability (NEXUS) Backward-

Compatible Ka-Band Relay

Broad Agency Announcement (BAA)

Broad Agency Announcement No. 80MSFC26R0006

Draft Release: April 9, 2026

Final Original Release: June 4, 2026

Primary Point of Contact: Jennifer George, MSFC/PS50

MSFC-NEXUS@mail.nasa.gov mailto:MSFC-NEXUS@mail.nasa.gov

NextSTEP-3 Appendix E: NEXUS Backward-Compatible Ka-Band Relay

Table of Contents

List of Tables

Acronyms

1 Introduction and Background

1.1 Overview

1.2 General Information for Participants

2 Opportunity Description

2.1 Acquisition Approach and Scope

2.2 Emphasis of Appendix E

2.3 NASA Safety Policy

2.4 Availability of Funds for Award

2.5 Funding Restrictions

2.6 Intellectual Property Developed Under an Award

3 Eligibility and Qualifications

3.1 Eligibility of Offerors

3.2 Mandatory Qualifications and Experience

3.3 Administrative and National Security Policy and Procedures

4 Proposal Submission Information

4.1 Instructions

4.2 Proposal Submissions

4.3 Proposal Format and Contents

4.4 Volume I - Transmittal Letter, Executive Summary, Eligibility Information, and

Mandatory Qualification and Experience

4.5 Volume II - Technical and Management Approach Volume

4.6 Volume III - Price Volume

4.7 Volume IV - Contract Volume

5 Proposal Review Information

5.1 Evaluation

5.2 Selection

5.3 Personnel

5.4 Process for Appeals

6 Award Administration Information

6.1 Award Notices

6.2 Post-Award

7 Solicitation References

8 Solicitation Attachments

List of Tables Table 3.1 Entities Excluded from Participation Table 4.1 Proposal Submission Content Table 4.2 Technical and Management Approach Volume Compliance Matrix Table 4.3 Exceptions and Deviations Table 4.4 Offeror Fill-ins Table 4.5 Plans Table 5.1 Technical and Management Approach Evaluation Points Table 8.1 Solicitation Attachments

Acronyms

Acronym Definition

APMC Agency Program Management Council

ATC Authority To Connect

ATP Authority To Proceed

BAA Broad Agency Announcement

BC Backward-Compatibility / Backward-Compatible

BOE Basis of Estimate

CASQ Commercial Architecture Security Questionnaire

CFR Code of Federal Regulations

CLIN Contract Line Item Number

ConOps Concept of Operations

CSP Communications Services Project

CUI Controlled Unclassified Information

CY Calendar Year

DCAA Defense Contract Audit Agency

DCMA Defense Contract Management Agency

DD Form 254 DoD Contract Security Classification Specification

DPAS Defense Priorities and Allocations System

DPD Data Procurement Document

DRDs Data Requirements Descriptions

DWRP Deviations and Waiver Request Package (DWRP)

EAR Export Administration Regulations

EFSS Enterprise File Sharing and Sync

FAR Federal Acquisition Regulation

FDIR Fault Detection, Isolation, and Recovery

FFP Firm Fixed Price

FFRDC Federally Funded Research and Development Center

FMV Fair Market Value

FY Fiscal Year

GFE Government-Furnished Equipment

GFD Government-Furnished Data

GFP Government-Furnished Property

GPE Governmentwide Point of Entry

GPM Global Precipitation Measurement

GRS GRS Recovery

GSA/ISOO General Services Administration / Information Security

Oversight Office

HSPD-12 Homeland Security Presidential Directive-12

HST Hubble Space Telescope

IMS Integrated Master Schedule

IP Intellectual Property

IR&D Independent Research and Development

Acronym Definition

ISS International Space Station

ITAR International Traffic in Arms Regulations

JPSS Joint Polar Satellite System

JPL Jet Propulsion Laboratory

JV Joint Venture

Ka-band / Ka Ka-band frequency designation

MOU Memorandum of Understanding

MPSR Monthly Program Status Report

NASA National Aeronautics and Space Administration

NEXUS Network Extension for User Continuity and Sustainability

NFS NASA FAR Supplement

NPD NASA Policy Directive

NPG NASA Procedural Guidelines

NPR NASA Procedural Requirements

NSF National Science Foundation

OCI Organizational Conflict of Interest

OFI Offeror Fill-In

POC Point of Contact

Q&A Question and Answer

R&D Research and Development

RF Radio Frequency

RFP Request for Proposals

ROM Rough Order of Magnitude

SCaN Space Communications and Navigation

SSL Space to Space Link

SO Selection Official

SOO Statement of Objectives

SOW Statement of Work

SRD Service Requirements Document

TBD To Be Determined

TDRS Tracking and Data Relay Satellite

TDRSS Tracking and Data Relay Satellite System

TIM(s) Technical Interchange Meeting(s)

TRL Technology Readiness Level

UEI Unique Entity Identifier

V&V Verification and Validation

1 Introduction and Background

1.1 Overview

NASA faces a credible risk of losing critical space-to-ground communications for key on-orbit missions in the Calendar Year (CY) 2029–2031 timeframe due to the aging Tracking and Data

Relay Satellite System (TDRSS) and the lack of currently available backward-compatible commercial alternatives. TDRSS is a critical national asset that enables continuous relay communications for NASA missions with significant operational and scientific importance.

Legacy users that depend on existing TDRS-compatible capabilities cannot transition to new frequency bands or relay architectures without major spacecraft modifications, placing telemetry, tracking, command services, and ultimately mission safety and scientific return, at risk.

Through the Space Communications and Navigation (SCaN) program and SCaN’s

Communications Services Project (CSP), NASA is pursuing a targeted transition strategy that leverages mature commercial space communications capabilities while investing in the development and demonstration of the specific compatibility features needed for legacy TDRS-compatible users. This approach is intended to reduce technical risk, preserve industry flexibility to innovate, and enable the fastest feasible transition to sustained operational relay capability.

Project NEXUS, a CSP subproject, seeks proposed solutions capable of demonstrating the key

Ka-band backward-compatible relay capabilities needed to preserve long-term continuity for legacy Government users.

NEXUS will demonstrate a viable, TDRS-compatible relay capability preserving Government mission assurance, continuity protections, and strategic flexibility consistent with NASA’s operational responsibilities for this communications capability. The Agency’s objective is to demonstrate and mature this capability by leveraging commercial infrastructure, investment, and operational approaches wherever practical, while retaining the Government’s ability to assess and select the most appropriate long-term model for ownership, operations, mission assurance, continuity protection, and service delivery. Results from this demonstration may inform future

Agency decisions regarding sustained relay capability needs, including the appropriate ownership, operational, acquisition, service, and continuity models. This solicitation does not establish or guarantee any specific future follow-on acquisition, ownership model, operational construct, provider, or service arrangement.

To meet NASA’s needs, Offerors must propose a solution that operates in NASA’s heritage

TDRS frequency bands and provides a backward-compatible, waveform-agnostic bent-pipe relay capability without requiring any modifications to current, legacy Government user spacecraft.

While primarily supporting SCaN’s CSP portfolio and near-term relay continuity, the demonstrated capability may also support NASA’s broader cislunar, lunar surface, and exploration objectives by advancing scalable, resilient, and sustainable commercial approaches to space communications needed for increasingly complex missions beyond low Earth orbit. In addition, NEXUS will strengthen the domestic industrial base, mature commercially provided relay capabilities, and demonstrate acquisition and operational approaches applicable to future cislunar, lunar surface, Mars, and exploration communications architectures.

1.2 General Information for Participants

• Agency: National Aeronautics and Space Administration (NASA) George C. Marshall

Space Flight Center (MSFC)

• Responsible Division: Office of Procurement (OP), Science, Technology, and

Engineering Division (PS50)

• Point of Contact: Jennifer George, Contracting Officer MSFC-NEXUS@mail.nasa.gov

• Proposal Submittals: Proposals must be submitted electronically through NASA’s EFSS

Box no later than 10:00 a.m. Central Time (CT), July 7, 2026. Hard copies will not be accepted.

• Proposal Validity: Offers submitted in response to this solicitation must remain in effect until December 31, 2026. However, a different longer validity period may be proposed.

Offers with validity periods expiring before December 31, 2026, risk ineligibility for award if the Government awards without competitive negotiations and the validity period has elapsed prior to award being made.

• Rating: NASA anticipates any resultant contract awarded will receive a Defense

Priorities and Allocations System (DPAS) rating of DO-A7.

• Inquiries: Written questions must be submitted no later than five calendar days after final solicitation posting to SAM.gov. The questions must not contain proprietary or sensitive information. NASA will not provide evaluations, opinions, or recommendations regarding any suggested approaches or concepts. All correspondence must be directed to

Jennifer George, Contracting Officer at msfc-nexus@mail.nasa.gov, with the exception of questions regarding SAM.gov-related issues. SAM.gov-related questions should only be directed to SAM.gov at https://sam.gov/about/contact, not NASA.

• Industry Forum: A pre-solicitation notification was released March 23, 2026, a draft solicitation package was released April 9, 2026, a draft solicitation industry day was conducted April 14, 2026, interested industry vendor visits and one-on-one engagements were conducted April 14, 2026-April 29, 2026, and a final draft solicitation industry day was conducted May 14, 2026. All draft materials continued to be posted on SAM.gov and the NextSTEP website. No further industry forums will be conducted.

• Website for Reference Information: https://sam.gov/, http://nasa.gov/nextstep

This Appendix E solicitation constitutes a BAA as contemplated by FAR Part 35 and NFS Part

1835.

NASA will not issue paper copies of this Appendix. The Appendix and associated Appendix related documents, and other information may be obtained and downloaded from the NextSTEP website or http://www.SAM.gov. Offerors are encouraged to refer regularly to these sites for updates and other information.

Issues with SAM.gov access, questions about navigating the SAM.gov website, or questions about document access in SAM.gov should be directed only to SAM.gov

(https://sam.gov/about/contact).

mailto:MSFC-NEXUS@mail.nasa.gov mailto:msfc-nexus@mail.nasa.gov https://sam.gov/about/contact https://sam.gov/workspace/contract/opp/636a9403af594412ad56b9e04c9402a0/view http://nasa.gov/nextstep http://www.sam.gov/

2 Opportunity Description

2.1 Acquisition Approach and Scope

This solicitation requires Offerors to propose, develop, and conduct an on-orbit demonstration of a focused, end-to-end Ka-band relay capability that supports legacy TDRS-compatible users. The demonstration must address the backward-compatibility, integration, and operational features necessary to show that the proposed capability can transition from demonstration to sustained operational use.

The proposed solution must include the space, ground, network, launch, integration, operations, and service-management elements necessary to demonstrate a credible and traceable path to sustained backward-compatible relay service availability. The proposed approach must also demonstrate how the capability can support operational backward-compatible relay services for a minimum of 15 years.

NASA’s objective is to initiate on-orbit demonstration activities no later than the end of Calendar

Year 2028. The demonstration must provide sufficient technical, operational, schedule, service-assurance, and business evidence to support future sustained-service acquisition decisions and enable incremental sustained service availability beginning in 2029, with full operational service capability attainable by mid-2031.

The demonstration provided under this Appendix E must serve as the first operationally relevant increment of the Offeror’s proposed sustained-service architecture, not a standalone or non-representative demonstration. The demonstration must be technically traceable to the proposed sustained-service architecture and must include a credible path to incremental sustained service availability without requiring fundamental redesign of the demonstrated architecture, user compatibility approach, or service delivery model.

NASA is not prescribing a specific orbital architecture, deployment approach, ownership model, or technical solution. Offerors must propose the architecture and implementation approach they determine best satisfies the NEXUS requirements, provided the proposed solution supports the service needs of legacy TDRS-compatible users without requiring modifications to current, legacy Government user spacecraft. NASA will evaluate proposals based on feasibility, risk, scalability, operational suitability, interoperability, long-term service flexibility, and the ability to meet the stated requirements and demonstration objectives.

For purposes of this solicitation, a commercially provided relay capability means an end-to-end capability in which the Offeror is responsible for providing the space, ground, network, integration, operations, and service-management functions needed to meet NEXUS requirements through commercial capabilities, infrastructure, investment, and operational approaches. This term refers to the manner in which the capability is developed, furnished, operated, and managed by the Offeror, and does not provide or imply commercial access to the NEXUS Ka-band frequencies, which are reserved for Government mission use.

2.2 Emphasis of Appendix E

Appendix E focuses on developing, maturing, integrating, and demonstrating backward-compatible Ka-band relay capabilities needed to support legacy TDRS-compatible users without requiring modifications to current, legacy Government user spacecraft. The NEXUS acquisition is intended to generate the technical, operational, schedule, service-assurance, and business evidence needed to inform future NASA decisions regarding sustained relay capability.

The overall objectives of this acquisition are to:

• Protect continuity for legacy NASA missions operating within defined TDRS Ka-band spectral ranges without requiring modifications to current user spacecraft.

• Demonstrate an operationally viable backward-compatible Ka-band relay capability using a representative implementation of the Offeror’s proposed sustained-service architecture.

• Verify applicable requirements and validate performance, coverage, concurrency, handovers where applicable, scheduling, service activation, data delivery, monitoring, and operational execution through phased development, system integration, and on-orbit demonstration.

• Generate sufficient technical, operational, interoperability, cost, schedule, business, and service-assurance data to inform future NASA decisions regarding sustained relay services.

• Preserve long-term operational flexibility, interoperability, continuity, resiliency, and the potential for a broader multi-user commercial relay ecosystem.

• Demonstrate that the proposed architecture, deployment approach, launch strategy, ground and network integration, operations concept, supply chain, and business model can support transition from demonstration to incremental sustained service availability beginning in 2029 and progression toward full operational capability by mid-2031.

• Achieve service readiness on a timeline that reduces the risk of a legacy service availability gap in the CY 2029–2031 timeframe.

This solicitation does not establish or guarantee any specific future follow-on acquisition, ownership model, operational construct, provider, or service arrangement. NASA may use information generated under this solicitation to inform future sustained-service planning and related acquisition decisions.

NASA intends to award one or more contracts under this solicitation. Each contract will be structured with a base CLIN and two separately priced option CLINs. For purposes of this solicitation, references to “Phase 1,” “Phase 2,” and “Phase 3” correspond respectively to CLIN

1, CLIN 2, and CLIN 3.

• Base CLIN 1 / Phase 1: Concept Maturation and Risk Reduction, 6 months

• Priced Option CLIN 2 / Phase 2: System Integration, Flight Demonstration, and

Capability Verification and Validation, up to 24 months

• Priced Option CLIN 3 / Phase 3: Additional Demonstration, Anomaly Resolution, and

Service Validation, up to 6 months

CLIN 1 / Phase 1: Concept Maturation and Risk Reduction

The purpose of CLIN 1 is to mature the Offeror’s proposed solution into a concept package that defines the proposed end-to-end relay capability, demonstration approach, verification and validation approach, and path to sustained operations. CLIN 1 enables NASA to assess the concept’s technical credibility, execution feasibility, backward compatibility, affordability, transition approach, long-term service sustainability, and overall risk. CLIN 1 milestones, associated DRD deliveries, payment structure, and acceptance criteria are provided in

Attachment F, Payment Milestones and Acceptance Criteria.

CLIN 2 / Phase 2: System Integration, Flight Demonstration, and Capability Verification and Validation

The purpose of CLIN 2 is to integrate, verify, mature, and conduct the initial on-orbit demonstration of the selected service concept as an operationally viable backward-compatible

Ka-band relay capability. CLIN 2 includes final design maturation, integration, test, regulatory and security readiness, launch/deployment as applicable, orbit insertion, checkout, commissioning, Authority to Connect, Government user connection, and completion of a minimum 30-calendar-day on-orbit performance measurement period. CLIN 2 generates the technical, operational, user-integration, and service-assurance evidence needed to inform

NASA’s follow-on sustained-service acquisition planning. CLIN 2 milestones, associated DRD deliveries, payment structure, non-payment milestone expectations, and acceptance criteria are provided in Attachment F, Payment Milestones and Acceptance Criteria.

CLIN 3 / Phase 3: Additional Demonstration, Anomaly Resolution, and Service Validation

The purpose of CLIN 3 is to provide an optional demonstration extension and service-validation phase if NASA determines that additional demonstration, anomaly resolution, retest, extended performance measurement, expanded user interaction, or closeout evidence is needed. CLIN 3 is supplemental to, and not a substitute for, the initial flight demonstration conducted under CLIN

2. CLIN 3 milestones, associated deliverables, payment structure, and acceptance criteria are provided in Attachment F, Payment Milestones and Acceptance Criteria.

At NASA’s discretion, option CLINs may be exercised for one, multiple, or none of the selected

Offerors. The decision to exercise any option rests solely with NASA, and no option is guaranteed.

NASA reserves the right to change its acquisition strategy at any time, including the selection of one, multiple, or none of the proposals received. Subject to the availability of funds, NASA intends to award one or more contracts and requires separate firm-fixed-price pricing, a detailed schedule, and an Offeror-prepared Statement of Work (SOW) for each CLIN. The SOW shall be based on the Government’s Statement of Objectives (SOO) and shall include the Offeror’s proposed technical approach, milestones, deliverables, reviews, and demonstration activities for each CLIN.

Offerors may propose accelerated schedules for completing CLIN objectives, milestones, deliverables, reviews, and demonstration activities. The stated CLIN periods of performance represent maximum planned durations and do not preclude earlier completion when technically and programmatically appropriate.

NASA may, at its discretion, exercise an option CLIN before the end of the preceding CLIN period of performance if the Contractor has satisfactorily completed the applicable objectives, deliverables, reviews, decision criteria, and conditions necessary to proceed. Early completion does not obligate NASA to exercise any option and does not limit NASA’s consideration of technical readiness, risk, funding availability, programmatic need, or overall best value.

2.3 NASA Safety Policy

Safety is NASA’s highest priority. Safety is the freedom from those conditions that can cause death, injury, occupational illness, damage to or loss of equipment or property, or damage to the environment. NASA’s Safety and Mission Assurance requirements are identified in NPR 8715.1, NASA Safety and Health Programs. All research and development conducted under NASA auspices shall conform to these requirements. (NPR 8715.1)

2.4 Availability of Funds for Award

The Government’s ability to make award(s) is contingent upon the availability of funds and the receipt of proposals that NASA determines are acceptable for award under this Appendix E solicitation.

2.5 Funding Restrictions

The following restrictions are applicable to Appendices under this Omnibus:

• The number of awards may change depending on the availability of funds and the receipt of a sufficient number of meritorious proposals.

• Refer to the Proposal Submission Information section for specific price proposal submission requirements.

• Contract awards will be subject to the provisions of the FAR and the NFS as reflected in the Model Contract attachment of this solicitation.

2.6 Intellectual Property Developed Under an Award

This section defines the intellectual property policies applicable to items developed under an award issued pursuant to this Appendix. Consistent with NASA’s objective to advance Ka‑band relay technologies through partnership, award recipients are expected to contribute corporate resources in support of their proposed efforts. Intellectual property rights will be allocated in accordance with applicable Federal requirements and the terms of this solicitation to ensure both commercial incentive and appropriate Government access.

2.6.1 Data Rights

For data related to items, components, or processes developed at private expense by the contractor, the Government will require limited rights (i.e., the right of use [except for manufacture] by subcontractors, the right of use [except for manufacture] by other contractors participating in the same Government program, etc. – see FAR 27.404-2(c)). Generally, the https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=8715&s=1A

Government has unlimited rights in data first produced in the performance of a contract.

However, for co-sponsored research and development activities (i.e., items, components, or processes developed with both the contractor’s funds and the Government’s funds), the

Government will consider taking less than unlimited rights. Such lesser rights will include agreed-to Government purposes (including reprocurement rights) but will exclude rights for commercial purposes which will be retained by the contractor.

For purposes of this solicitation, the term "developed" means that an item, component, or process exists and is workable. Thus, the item or component must have been constructed or the process practiced. Workability is generally established when the item, component, or process has been analyzed or tested sufficiently to demonstrate to reasonable people skilled in the applicable art that there is a high probability that it will operate as intended. Whether, how much, and what type of analysis or testing is required to establish workability depends on the nature of the item, component, or process, and the state of the art. To be considered “developed,” the item, component, or process need not be at the stage where it could be offered for sale or sold on the commercial market, nor must the item, component, or process be actually reduced to practice within the meaning of Title 35 of the United States Code (U.S.C.).

2.6.2 Patent Rights

The Government will have certain statutory rights in an invention that is conceived or first actually reduced to practice under a NASA award (51 U.S.C. § 20135) provided that title to such inventions vests in the United States, except where 35 U.S.C. § 202 provides otherwise for nonprofit organizations or small business firms.

Where 51 U.S.C. § 20135 applies i.e., under an award with a large entity, a recipient may request a waiver to obtain title to inventions made under the award in accordance with 51 U.S.C. §

20135(g) and 14 CFR 1245 Subpart 1.

Such a request may be made in advance of the award or within 30 days thereafter. Even if a waiver request is not made, or denied, a large business recipient may request a waiver on individual inventions made during the course of the award.

NASA normally grants requests for waiver unless the interests of the United States are better served by restricting or eliminating all or part of the rights of an Offeror as set forth in 14 CFR

1245.104(b). Among the most important goals are providing incentives to foster inventiveness and encouraging the reporting of inventions. As noted previously, corporate contributions are required.

For joint inventions, NASA will typically agree, pursuant to a Joint Ownership Agreement, to refrain from exercising its undivided interest in a manner inconsistent with a recipient’s commercial interest.

For all recipients, the patent rights provision in a resulting award will require the disclosure to

NASA of all subject inventions made under the contract. NASA considers the reporting of inventions an important metric that will be used to measure whether new technologies are being developed. Reporting of inventions also protects a recipient’s ownership to such inventions since

NASA has the right to obtain title in unreported inventions.

3 Eligibility and Qualifications

3.1 Eligibility of Offerors

(a) Offerors must be a United States entity to be eligible to participate in this requirement.

Performance of activities under Appendix E requires access to data that is subject to export control regulations. Any entity proposing for a contract under Appendix E must comply with all U.S. export control laws and regulations, including the International

Traffic in Arms Regulations (ITAR), 22 CFR Parts 120 through 130, and the Export

Administration Regulations (EAR), 15 CFR Parts 730 through 774, and must demonstrate the entity’s compliance and process in the performance of the resulting

Appendix E. Violations of these regulations can result in criminal or civil penalties.

(b) Offerors are responsible for ensuring that all employees who will work on this contract are eligible under export control laws, EAR, and ITAR. Therefore, Offerors must confirm that all employees participating in this requirement are U.S. citizens or U.S. permanent residents and continue to ensure U.S. citizenship or permanent U.S. residency as reflected in Attachment H, NEXUS TDRS-BC Model Contract, FAR 52.222-54, Employment

Eligibility Verification.

(c) In accordance with NFS 1852.225-71, Restriction on Funding Activity with China, proposals must not include bilateral participation, collaboration, or coordination with

China or any Chinese-owned company or entity, whether funded or performed under a no-exchange-of-funds arrangement. By submission of a proposal, Offerors are certifying that the proposing organization has read and is in compliance with all the Certifications, Assurances, and Representations, including that proposals must not include bilateral participation, collaboration, or coordination with China or any Chinese-owned company or entity, whether funded or performed under a no-exchange-of-funds arrangement.

(1) NASA is restricted from using appropriated funds to enter into or fund any agreement of any kind to participate, collaborate, or coordinate bilaterally with

China or any Chinese-owned company, at the prime recipient level and at all sub-recipient levels, whether the bilateral involvement is funded or performed under a no-exchange-of-funds arrangement.

(2) Definition: “China or Chinese-owned Company” means the People’s Republic of China, any company owned by the People’s Republic of China, or any company incorporated under the laws of the People’s Republic of China.

(3) By submission of its proposal, the Offeror represents that the Offeror is not

China or a Chinese-owned company, and that the Offeror will not participate, collaborate, or coordinate bilaterally with China or any Chinese-owned company, at the prime recipient level or at any sub-recipient level, whether the bilateral involvement is funded or performed under a no-exchange-of-funds arrangement.

(d) Offerors must ensure information and certifications required in SAM.gov are current at the time of proposal submission to ensure all eligibility requirements are met. Offerors must be registered at SAM.gov at time of proposal submission and at contract award, if selected.

(e) End-to-End Solution: Offerors must describe and demonstrate a complete end-to-end

NEXUS solution that includes the space, ground, network, launch, integration, operations, cybersecurity, service-management, and user-interface elements necessary to meet the requirements stated in the SRD.

(f) Launch Vehicle and Deployment: Offerors must demonstrate a credible launch or deployment path sufficient to support the proposed NEXUS on-orbit demonstration schedule.

(g) Corporate Contributions: Offerors must show a corporate contribution that is directly relevant to the proposed overall effort.

The following entities are excluded from participation in this acquisition due to organizational conflicts of interest (OCI):

Table 3.1 Entities Excluded from Participation

Agile Decision

Sciences

Amentum ASRC Federal CGI Federal

Bastion Technologies Booz Allen Broome Aerospace Ignite Fueling

Innovation, Inc.

Deloitte DigiFlight, Inc. General Dynamics IT Sierra Lobo

N. Otte LLC Peraton, Inc. Resolution LLC TriVector Service

Stellar Solutions Summit Technologies and Solutions

Teltrium Strategic Services

Barrios Technology Victory Solutions KODA Technologies

Columbus

Technologies and

Services Inc.

Auburn University

Applied Research

Institute

3.2 Mandatory Qualifications and Experience

The Offeror must demonstrate that the proposed team, defined as the Prime Offeror and any proposed subcontractors, teaming partners, or joint venture partners whose corporate experience is cited, possesses credible, recent, and relevant corporate experience sufficient to support successful execution of the NEXUS effort. Additional details are in Section 4.4.4.

GoLion https://sam.gov/

3.3 Administrative and National Security Policy and Procedures

Offerors must comply with Homeland Security Presidential Directive 12 (HSPD-12). HSPD-12 applicability will be determined during award negotiations for the selected proposal(s).

NASA does not anticipate that access to classified information will be required for performance under this solicitation. Accordingly, a DD Form 254 is not included with this solicitation. Offerors must propose unclassified solutions that can be fully evaluated using unclassified information.

If an Offeror determines that classified information is necessary to describe or support its proposed solution adequately, the Offeror must clearly identify in the proposal:

• The specific elements requiring classification

• The proposed classification level

• A detailed justification for why an unclassified approach is not feasible

If NASA determines that classified exchanges are necessary during the evaluation process, then

NASA will coordinate with the Offeror to establish appropriate security controls, documentation

(including a DD Form 254, if required), and procedures. Any such exchanges will be conducted in accordance with applicable U.S. Government security policies and procedures. NASA reserves the right to limit, decline, or require unclassified alternatives to any proposed classified engagements or information if NASA, in its sole discretion, deems the classified engagements are not essential to the evaluation of the proposed solution.

4 Proposal Submission Information

4.1 Instructions

Proposals must adhere to the standards outlined in this solicitation. However, noncompliant portions of a proposal (e.g., sections that violate formatting or content requirements) will be identified and will not be evaluated, while the remainder of the proposal will continue to be considered. The Government will not reject an entire proposal solely due to such deficiencies;

instead, the Contracting Officer will notify the Offeror of each identified violation and clarify which portions are ineligible for evaluation. Offerors are responsible for understanding and complying with the solicitation before preparing and submitting proposals.

For purposes of this solicitation, the terms “must” and “shall” are used interchangeably to denote mandatory requirements or obligations. Unless otherwise stated, both terms indicate actions, conditions, or requirements that are required for compliance with this solicitation.

Proposal submission questions will be answered and published in a Question-and-Answer log.

Individual responses will not be provided. NASA will not provide evaluations, opinions, or recommendations regarding any suggested approaches or concepts. This Q&A log will be posted on SAM.gov and the NextSTEP website and will be updated periodically between solicitation release and the proposal due date.

A Prime Offeror must submit only one proposal, representing its best approach and best price for meeting the requirements of this solicitation. An entity that submits as a Prime Offeror may also participate as a subcontractor or team member on another Prime Offeror’s proposal but must not submit more than one proposal as the Prime Offeror.

The proposal must describe a complete end-to-end NEXUS solution. The Offeror must provide a concise summary identifying how the proposed team will provide each required element, including space, ground, network, launch, integration, operations, cybersecurity, service management, and user interface. If any required element is provided by a subcontractor, teammate, partner, or other proposed team member, the Offeror must identify the entity, the role that entity will perform, and how that element is integrated into the overall NEXUS solution.

Proposals that provide only partial or standalone technical capabilities will be determined ineligible and will not be further evaluated.

4.2 Proposal Submissions

Proposals must be submitted electronically through NASA’s Enterprise File Sharing and Sync

Box (EFSS Box). Hard copies will not be accepted.

4.2.1 Electronic Submission of Proposals – Proposal Marking and Delivery Through

NASA’s EFSS Box

The Offeror must submit its proposal electronically via NASA’s Enterprise File Sharing and

Sync (EFSS) Box, a FedRAMP Moderate authorized platform. Offerors must follow the detailed

EFSS Box submission instructions located at:

https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission-

Instructions.pdf

Proposals must be received no later than 10:00 a.m. Central Time on July 7, 2026.

Offerors that have not previously used NASA’s EFSS Box are strongly encouraged to coordinate a test file submission no later than ten (10) calendar days before the proposal due date to allow time to resolve any access or technical issues.

The Offeror is solely responsible for ensuring the complete proposal is successfully uploaded and received by the Government by the deadline. Uploading files through EFSS Box may not be instantaneous. Offerors are strongly encouraged to submit at least 24 hours before the deadline.

NASA is not required to verify receipt before the submission deadline and is not responsible for any transmission or receipt failures.

All proposal files must:

• Be searchable;

• Not contain hidden formulas, hidden tables, or links to data not included in the electronic submission;

• Not be locked or password protected;

• Be free of viruses and malware;

• Not exceed 150 GB per individual file; and

• Be submitted in native electronic format whenever possible.

https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission-Instructions.pdf https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission-Instructions.pdf

Scanned documents are permitted only when necessary, such as signature pages, prior award fee letters, or DCAA/DCMA approval letters.

Files determined by NASA to contain viruses or malware will not be opened or evaluated.

Alternate proposal submission methods are not authorized.

Offerors are encouraged to combine all proposal files into a single .zip file.

File names shall contain only letters, numbers, dashes, single spaces, and the period before the file extension. File names shall not include special characters.

Each file shall be sequentially numbered, clearly labeled with its contents, and include the

Offeror name, solicitation number, volume number, and subcontractor name, if applicable.

Acceptable file name examples include:

Prime Offeror Submissions

1 - Offeror Name - Volume 1

2 - Offeror Name - Volume 1 Attachment 1

Subcontractor Submissions

1 - Offeror Name - Subcontractor Name - Volume 1

2 - Offeror Name - Subcontractor Name - Volume 1 Attachment 1

Subcontractor Submissions

Subcontractors may submit required proposal information separately through EFSS Box. The

Prime Offeror remains responsible for ensuring all subcontractor files are submitted by the proposal deadline and comply with all solicitation instructions.

Post-Submission Actions

Immediately after the complete proposal has been uploaded, the Offeror shall email MSFC-

NEXUS@mail.nasa.gov with a list of all submitted files by filename.

The electronic submission must contain all information required by the solicitation to be considered responsive.

4.3 Proposal Format and Contents

The proposal format and content requirements as outlined in this section below are the same for all volumes. Each of the required volumes of the proposal must be submitted as one searchable, unlocked file. Offerors must comply with the format and page limit requirements described in the table below. Attachments that are not specifically requested must not be submitted and will not be evaluated, if submitted.

Volumes II and III of the proposal must be structured as follows:

• Priced Base CLIN 1, Concept Maturation and Risk Reduction (6 months)

• Priced option CLIN 2, System Integration, Flight Demonstration, and Capability

Verification and Validation (up to 24 months)

• Priced option CLIN 3, Additional Demonstration, Anomaly Resolution and Service

Validation (up to 6 months)

The Offeror’s SOW will be incorporated to accurately reflect and measure the contractor’s performance against the planned solution, deliverables, milestones, and work schedule for each

CLIN, respectively.

The following page limitations are established for each portion of the proposal submitted in response to this solicitation.

Table 4.1 Proposal Submission Content

Proposal Section Page Limit Proposal Subsection Excluded Items, Attachments, &

Pages

Volume I-

Part I:

Transmittal Letter and Executive

Summary

Part II:

Eligibility

Information

Part III:

Mandatory

Qualifications and

Experience

For overview contents, see Section 4.4

• Transmittal Letter

• Executive Summary

• Launch Vehicle and Deployment acceptable evidence as defined in

4.4.3.

Volume II -

Technical and

Management

Approach

80 Pages For volume contents, see Section 4.5

• CASQ Attachment G

• Integrated Master Schedule

• Statement of Work

(provide all after the last numbered page)

Volume III -

Price

No

Page Limit

For volume contents, see Section 4.6

Volume IV –

Contract Volume

No

Page Limit

For volume contents, see Section 4.7

• Infrastructure Validation:

Partnership agreements, facility access documentation, equipment specifications, technology capability documentation

• Organizational Conflicts of Interest

Plan

• Installation-Accountable

Government Property (IAGP) /

Government Furnished Property

(GFP) List

• Data Rights (Assertion Notice, corresponding narratives, and evidence)

• Small Business Plan

(provide all after the last numbered page)

Attachments must not be used to introduce new evaluation-relevant assertions that are not presented in the applicable proposal volume in order to circumvent page limitations.

Submit all proposal volumes in Microsoft Office 2024 or later formats (i.e., Microsoft Word for narrative and Microsoft Excel for the pricing models). Offerors must not convert these volumes to .pdf format. Supplemental documentation provided as part of the non-page limited Price volume (e.g., financial statements, indirect rate letters, audit reports, letters of credit, disclosure statements, pre-award accounting system SF 1408s) may be provided in their native format (e.g., Adobe, .pdf). Offerors must not embed sound or video files into the proposal volumes.

Submit the contents of each volume per section 4.2.1 Electronic Submission of Proposals –

Proposal Marking and Delivery Through NASA’s EFSS Box instructions. Offerors must also ensure that each volume stands alone, provides complete coverage of the topic, and includes responses to each item described in the volume instructions.

Establish a page numbering convention for all volumes except for the Contract volume which must be numbered as provided for in the Model Contract Attachment H.

Provide a table of contents for each volume, with the exception of the Contract volume, for ready reference to sections and other proposal data (e.g., charts, tables, figures, illustrations, screenshots, pictures).

Instructions for page limited volumes:

• All pages must be consecutively numbered, starting with “1” (one) on the first page of each volume.

• Each page, regardless of whether it contains proposal material or left blank, will be counted as a page.

• The standard page size must be 8½” x 11” with at least one-inch margins set on all sides (i.e., Microsoft Word, Layout, Margins, Normal, 1”) and the maximum page size must be 11” x

17.” Page sizes larger than 11” x 17” must not be utilized. Pages larger than 8½” x 11” will count as two pages and be appropriately numbered.

• No material outside of the proposal volumes may be incorporated by reference.

• To minimize redundancy, Offerors may reference another section within that volume only rather than duplicate the information in more than one location. Offerors must maintain logical subject matter flow when utilizing references.

• Font style shall be Times New Roman, and the font size shall be not smaller than 12-point for all text including, but not limited to the documents listed within the “Excluded Items, Attachments, & Pages” column of Table 4-1 above, charts, tables, figures, illustrations, pictures, graphs, or other embedded objects. Any text determined non-compliant will not be evaluated; however, any remaining content will be evaluated. All text shall use normal kerning (i.e., Microsoft Word, Font, Advanced, Scale 100%, Spacing Normal, Position

Normal, Kerning for Fonts unchecked). All lines shall be no less than single spaced.

• Text for all narrative information must be left margin justified (i.e., Microsoft Word, Home, Paragraph, Align Left [Ctrl+L]).

• If a determination is made that any material on any page does not comply with the guidelines related to font, kerning, line spacing, or margins, the material will not be evaluated.

Notification will be provided to the Offeror identifying any non-evaluated material.

• If proposal revisions are requested, separate page limitations will be specified in the

Government's request for that submission.

• Pages submitted in excess of the limitations specified in this provision will not be evaluated by the Government and will be returned to the Offeror.

4.4 Volume I - Transmittal Letter, Executive Summary, Eligibility Information, and

Mandatory Qualification and Experience

4.4.1 Transmittal Letter

(1) A transmittal letter prepared on the Offeror’s letterhead. The letter must include:

(i) The name, address, and telephone number of the Offeror (and electronic address if available)

(ii) A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item

(iii) Names, titles, and telephone number (and electronic addresses if available) of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this solicitation

(iv) Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office

(v) Acknowledgement of receipt of all amendments and identification of all enclosures being transmitted.

(vi)For both the Offeror and any/all subcontractors and/or joint venture (JV) partners, provide the following information:

(i) Name (if "Doing Business As," include primary name)

(ii) Address

(iii) Commercial and Government Entity (CAGE) code

(iv) Unique Entity Identifier (UEI) number (see 2 CFR Part 25)

(v) Socio-economic status

(vi) Estimated/actual subcontract value for each proposed subcontractor at any level (i.e., 1st-tier, 2nd-tier, etc.) (see 13 CFR Subpart 125.6(a)(1)). For indefinite-delivery, indefinite-quantity (IDIQ) acquisitions without a reoccurring requirement (e.g., annual mission), also specify the total anticipated assigned work year equivalents (WYEs) and the resulting percentage of total proposed

WYEs for the first year for each estimated/actual subcontract.

(vii) Microsoft Word version utilized to prepare the proposal

(viii) Results of any internal procurement integrity investigation pertaining to the participation of ex-NASA personnel in proposal preparation activities which could have provided the Offeror with an unfair competitive advantage

(ix) Proposal validity period (see paragraph [c][3] below)

(x) Company acquisitions/mergers/restructure - If the Offeror is involved in an impending or already consummated corporate transaction such as an acquisition, or merger with another company, or restructuring, whether announced publicly or not, the Offeror must provide information to convey any potential impacts of that corporate transaction on its proposal and any subsequent contract that may be awarded. For purposes of this solicitation, a corporate transaction is considered consummated when it has legally closed. Offerors must disclose any such transactions consummated within the 12 months prior to proposal submission, as well as any pending transactions, and describe any potential impacts on contract performance. An impending corporate transaction is one that is reasonably expected to be consummated within 120 days after proposal submission and for which the Offeror has entered into a binding agreement or similar arrangement.

Offerors must disclose such transactions and describe any potential impacts on performance. The following must be addressed:

A. The company’s ability to perform contract requirements as specified in the solicitation

B. The impact to all resources required, including facilities, proposed for this effort

C. The transaction impact to the rates and cost proposed

D. Any impact on how small business will be utilized

E. Any impact on the total compensation plan, if applicable; and

F. Any impact to other aspects of the proposal (e.g., business systems, JV and/or mentor-protégé agreement, organizational conflict of interest plan).

Failure to fully address how the merger, acquisition, or restructuring will affect your proposal may render it ineligible for award under FAR Part 9.1. If such transaction occurs or is initiated after proposal submission, the Offeror must provide notice of the transaction to the point of contact specified in the solicitation.

4.4.2 Executive Summary

The Executive Summary must consist of an overview describing the Offeror’s qualifications, proposed solution, and on-orbit demonstration for an end-to-end Ka-band relay service, including space, ground, launch, integration, and operations elements, that are backward-compatible for a minimum of fifteen years. The Executive Summary must provide an overview of the proposed effort that is suitable for release through a publicly accessible archive should the proposal be selected.

4.4.3 Eligibility Information

The Offeror must provide the eligibility information required by Section 3.1 in Volume I, Part II, Eligibility Information. NASA will determine an Offeror ineligible for award if the Offeror does not demonstrate a complete eligibility package. Therefore, to be eligible for award, the Offeror must document its eligibility to participate in this activity by submitting a signed statement certifying items (a) through (d) of section 3.1 as follows:

(a) All participating entities have applicable DDTC registration, authorization, or other required approval to receive and handle ITAR-controlled data, as applicable.

(b) All participating individuals are U.S. citizens or U.S. permanent residents, and all participating entities are U.S. entities.

(c) All participating entities certify compliance with the China-related restrictions, certifications, assurances, and representations applicable to this solicitation.

(d) The Prime Offeror has verified that its SAM.gov information is current at the time of proposal submission.

In addition to a statement of certification, the following instructions apply to items (e) through

(g) of Section 3.1:

(e) End-to-End Solution: Demonstrate a complete end-to-end NEXUS solution that includes the space, ground, network, launch, integration, operations, cybersecurity, service-management, and user-interface elements necessary to meet the NEXUS requirements stated in the…