DRAFT_Appendix E Solicitation_20260410.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) Project Office:

Tracking and Data Relay Satellites (TDRS) -

Backwards Compatibility (BC) Ka-Band Broad Agency Announcement (BAA)

Broad Agency Announcement No. 80MSFC26R0006

Original Release: April XX 2026 Effective through: June 5, 2026

Primary POC: Jennifer George, MSFC-NEXUS@mail.nasa.gov

NextSTEP-3 Appendix E: NEXUS Ka-Band TDRS-BC

Table of Contents List of Tables

Acronyms

1 Introduction and Background

2 Acquisition Objectives

2.1 Overview

2.2 Objectives

2.3 CLIN / Phase Objectives

3 General Information

3.1 Eligibility

3.2 Response Date

3.3 Administrative and National Policy Requirements

3.4 Industry Forum

3.5 Inquiries

4 Contract Structure

4.1 Work Structure

4.2 CLIN 1: Concept Maturation and Risk Reduction

4.3 CLIN 2: System Integration and Flight Demonstration Readiness

4.4 CLIN 3: On-orbit Demonstration and Service Validation

5 Proposal Submission Information

5.1 General Format Requirements

5.2 Proposal Submission Instructions

6 Proposal Evaluation and Selection Information

6.1 General Evaluation and Selection Methodology

6.2 Proposal Evaluation and Selection

7 Award Administration Information

7.1 Award Provisions

7.2 Award Notices

7.3 Post-Award Progression

8 Other Information

8.1 Corporate Contributions

8.2 Government Engagement

9 Solicitation References

10 Solicitation Attachments

List of Tables Table 5-2 Proposal Submission Content

Acronyms

Acronym Definition APMC Agency Program Management Council BAA Broad Agency Announcement BC Backward Compatibility / Backwards Compatible 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 DD Form 254 DoD Contract Security Classification Specification DRDs Data Requirements Descriptions EAR Export Administration Regulations ESDMD Exploration Systems Development Mission Directorate FAR Federal Acquisition Regulation FDIR Fault Detection, Isolation, and Recovery FFP Firm Fixed Price FFRDC Federally Funded Research and Development Center 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 GTA / GTAs Government Task Agreement(s) HSPD-12 Homeland Security Presidential Directive-12 HST Hubble Space Telescope IMS Integrated Master Schedule IP Intellectual Property ISS International Space Station ITAR International Traffic in Arms Regulations JPSS Joint Polar Satellite System JPL Jet Propulsion Laboratory Ka-band / Ka Ka-band frequency designation M2M Moon to Mars 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

Acronym Definition NPR NASA Procedural Requirements NSF National Science Foundation OCI Organizational Conflict of Interest POC Point of Contact PPQ Past Performance Questionnaire 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 SRD System Requirements Document TDRS Tracking and Data Relay Satellite TDRSS Tracking and Data Relay Satellite System TIMs Technical Interchange Meetings TRL Technology Readiness Level V&V Verification and Validation

1 Introduction and Background NASA faces a credible risk of losing critical space-to-ground communications for key on-orbit missions beginning in the CY2029 to 2031 timeframe due to the aging Tracking and Data Relay Satellite (TDRS) System and the absence of backward-compatible commercial alternatives. The TDRS constellation supports several high-value missions, including the Joint Polar Satellite System (JPSS) and other legacy missions that depend on existing TDRS-compatible capabilities and cannot transition to new frequency bands, or fundamentally different relay architectures, without major spacecraft modifications. Therefore, these missions risk loss of telemetry, tracking, and command services which directly impacts mission safety and scientific return.

NASA, through the Space Communications and Navigation (SCaN) program, and its Commercial Services Project (CSP), is pursuing a targeted transition strategy that leverages mature commercial space communications capabilities to focus NASA’s investment toward the necessary compatibility and integration gaps only. Therefore, project NEXUS, a CSP subproject, is issuing this solicitation to mature only the Ka-band specific backward-compatible relay features, including next-generation Ka-band bent-pipe relay services, without duplicating commercial capabilities already available in the current Earth-orbit communications market.

To meet this need, interested contractors must develop a solution that operates in NASA’s heritage TDRS frequency bands using a transparent, bent-pipe architecture that passes mission communications through the space relay segment without onboard regeneration of user data.

This waveform-agnostic design is necessary to preserve compatibility with legacy TDRS-style links and existing user systems that cannot be modified.

NEXUS intends to reduce technical risk only where targeted development is still required, while preserving industry flexibility and enabling the fastest practical transition to operational commercial relay services in the future. While primarily supporting SCaN’s CSP portfolio, the capability may also benefit other programs such as Exploration Systems Development Mission Directorate (ESDMD)’s Moon to Mars initiative by helping NASA validate a commercial, service-based model for space communications that is more scalable, resilient, and sustainable for long-duration exploration. Although NEXUS is focused on near-term relay continuity, it strengthens the industrial base, matures commercially provided relay services, and demonstrates acquisition and operational approaches that are directly relevant to the communications architecture needed for future lunar and Mars missions.

2 Acquisition Objectives

2.1 Overview

The purpose of this solicitation is for industry to develop and demonstrate on-orbit a targeted end-to-end Ka-band relay service capability within a commercial satellite system architecture, focused specifically on the backward-compatibility and integration features. The capability should include space, ground, launch, integration, operations, and sustainment elements which indicate efficient transition into operational backward compatible services for a minimum of 15 years.

To preserve acquisition flexibility and the opportunity for future competition for operational relay services, NASA intends to award one or more contracts under this Appendix E solicitation.

The acquisition will be conducted in three phases, structured as a base period Contract Line Item Number (CLIN) 0001 for Phase 1, and two separately priced option CLINs for Phases 2 and 3.

For purposes of this solicitation, references to “Phase 1,” “Phase 2,” and “Phase 3” correspond respectively to CLIN 1, CLIN 2, and CLIN 3, and the terms may be used interchangeably as follows:

• Base CLIN 1 (Phase 1): Concept Maturation and Risk Reduction

• Priced Option CLIN 2 (Phase 2): System Integration and Flight Demonstration Readiness

• Priced Option CLIN 3 (Phase 3): On-Orbit Demonstration and Service Validation

NASA intends to progressively reduce the number of contractors through the exercise or non-exercise of options based on performance and progress during each phase. NASA will evaluate contractor performance to determine whether to exercise the option for the next phase. NASA may exercise an option for one, multiple, or none of the contractors. Contractors whose options are not exercised will not continue to subsequent phases.

NASA does not intend to request new proposals for Phases 2 or 3. Offerors will submit technical and pricing information for all three phases as part of their initial proposal. Option exercise decisions will be based on demonstrated performance, Government acceptance of required deliverables, and the criteria set forth in Sections 4.2.1, 4.3.2 and 6.1 of this solicitation.

NASA intends to transition between the base period and any exercised option CLIN without a break in contractor performance. The decision to exercise an option, and thereby authorize performance of the associated phase, rests solely with NASA. No guarantee is made that any option will be exercised.

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 currently intends to award one or more contracts and, later, to exercise options for one, multiple, or none of the contractors. Proposals will include separate firm-fixed-price (FFP) pricing for each optional CLIN.

2.2 Objectives

The objectives of this solicitation are to validate, through phased development and on-orbit demonstration, a viable end-to-end commercial Ka-band relay service solution capable of supporting NASA and other legacy Government missions. This acquisition is intended to focus development and demonstration on the specific backward-compatibility, integration, and operational gaps not yet demonstrated by industry, while enabling the fastest practical transition to sustained operational service. The overall objectives of the NEXUS acquisition are to:

• Protect continuity for legacy NASA missions operating within defined TDRS Ka-band spectral ranges without requiring modification to customer vehicle onboard systems.

• Demonstrate an operationally viable relay capability delivered as a commercial service.

• Verify requirements and validate performance, coverage, multi-user support, and operational execution through phased concept development, system integration, and on-orbit demonstration focused on the specific compatibility and integration features required for legacy mission support.

• Generate sufficient technical, operational, and cost data to inform a follow-on acquisition strategy for sustained relay services, while preserving competition and industry flexibility.

• Achieve service readiness on the timeline required to prevent a gap in legacy service availability and enable the fastest practical transition to operational service.

2.3 CLIN / Phase Objectives

Please note that no additional proposals will be requested for Phase 2 and Phase 3.

2.3.1 CLIN 1 / Phase 1 – Concept Maturation and Risk Reduction (6 months) The objective of CLIN 1 / Phase 1 is to mature the proposed specific backward-compatibility, integration, and verification features required for the end-to-end commercial relay service solution, reduce the key technical and programmatic risks associated with those gaps, refine the system architecture and verification approach, and establish a credible basis for progression into system integration and flight demonstration readiness. Additional details are provided in Section 4.2.

2.3.2 CLIN 2 / Phase 2 – System Integration and Flight Demonstration Readiness (15 months)

The objective of CLIN 2 / Phase 2 is to integrate and test the end-to-end system and complete the readiness activities required to support flight demonstration, including closure of the remaining design and verification gaps associated with backward-compatible relay performance, reduction of residual major risks, execution of integrated system testing, and preparation for on-orbit demonstration of the backwards compatible Ka-Band service capability as defined in Attachment B: SRD. Additional details are provided in Section 4.3.

2.3.3 CLIN 3 / Phase 3 – On-Orbit Demonstration and Service Validation (3 months) The objective of CLIN 3 / Phase 3 is to execute an on-orbit demonstration of the proposed commercial relay service’s backward-compatible relay capability with one or more of NASA’s current customers and to validate, in an operationally relevant environment, that the demonstrated service meets the NEXUS success criteria, satisfies all applicable requirements, and provides a credible basis for transition to sustained operational service. Additional details are provided in Section 4.4.

3 General Information

3.1 Eligibility

Eligible Offerors under this Appendix are United States institutions. Other eligibility information is also included in the NextSTEP-3 Omnibus BAA. 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.

Deloitte, Amentum, Broome Aerospace, Teltrium, Resolution, CGI, Koda, Auburn University Applied Research Institute, Summit Technologies and Solutions, and Stellar Solutions are ineligible to participate in this acquisition due to Organizational Conflict of Interest (OCI).

3.2 Response Date

With the release of this Solicitation, NASA invites qualified U.S. institutions to submit proposals to the NextSTEP-3 Appendix E: Network Extension for User Continuity and Sustainability (NEXUS): Tracking and Data Relay Satellite (TDRS) Backwards Compatibility (BC) Ka-Band Broad Agency Announcement. Interested offerors should review the full BAA requirements and submit complete proposals by 5:00 CT on June 5, 2026, to be considered for contract awards.

Offerors are responsible for monitoring the Contract Opportunities website (SAM.gov) for any calls or amendments to this announcement. Updates will also be posted on the NextSTEP-3 website (NextSTEP-3: Appendix E).

3.3 Administrative and National Policy Requirements

3.3.1 Homeland Security Presidential Directive/ HSPD-12

All Offerors will comply with Homeland Security Presidential Directive/ HSPD-12. HSPD-12 applicability will be determined during negotiation for award for selected proposal(s).

Additionally, award recipient(s) that have individuals working under the award who need access to NASA facilities and/or systems must work with NASA program staff to ensure proper credentialing. Such individuals include U.S. citizens, lawful permanent residents (“green card” holders), and foreign nationals (those who are neither U.S. citizens nor permanent residents).

3.3.2 Security / Classified Information (DD Form 254)

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.

An Offeror will propose solutions that can be fully evaluated using unclassified information to the maximum extent practicable.

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

• The specific elements requiring classification

• The proposed classification level

• A detailed justification for why an unclassified approach is not feasible https://sam.gov/ https://sam.gov/workspace/contract/opp/e33cd0cc61064a6497a55fca8e9b30c6/view https://www.nasa.gov/general/nextstep-3-e-network-extension-for-user-continuity-and-sustainability-nexus-ka-band-backward-compatible-relay-broad

An offeror will not submit any classified information in its proposal unless explicitly authorized by NASA in advance.

If NASA determines that classified exchanges are necessary during the evaluation process, 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 they are not essential to the evaluation of the proposed solution.

3.4 Industry Forum

A pre-solicitation notification was released on March 23, 2026 at NEXUS TDRS-BC SAM.GOV LINK to explain the intent of Appendix E and outline the structure of the acquisition. All materials will continue to be posted on the aforementioned SAM.gov link and the NextSTEP website at NextSTEP-3 E: Network Extension for User Continuity and Sustainability (NEXUS) Ka-Band Backward-Compatible Relay - NASA. Additionally, a final solicitation industry day will be tentatively scheduled on or around May 14, 2026.

3.5 Inquiries

Written questions may be submitted no later than April 21, 2026. The questions will not contain proprietary or sensitive information. NASA will not provide evaluations, opinions, or recommendations regarding any suggested approaches or concepts. All correspondence will be directed to Jennifer George, Contracting Officer at msfc-nexus@mail.nasa.gov.

4 Contract Structure

4.1 Work Structure

The contract will be structured to enable NASA to constantly evaluate contractor performance to make informed progressive downselect decisions. All CLINs will be priced and evaluated at time of initial proposal. NASA will award base CLIN 1 and priced option CLINs two and three. No additional proposals will be requested for subsequent CLINs.

Deliverables will be structured to support Government evaluation of technical viability, operational readiness, and transition planning for potential sustained service activities beyond this acquisition. The demonstration effort is intentionally limited to proving technical and operational viability, not delivering the full operational system. However, an offeror will demonstrate that the proposed architecture can scale and expand from the demonstration configuration into a full operational service system capable of meeting long-term mission needs.

4.2 CLIN 1: Concept Maturation and Risk Reduction

The purpose of CLIN 1 is to mature the Offeror’s proposed solution into a comprehensive package that defines the proposed end-to-end commercial relay service and demonstration approach and enables NASA to assess the concept’s technical credibility, execution feasibility, backward compatibility, affordability, and overall risk prior to progression into CLIN 2.

Activities under CLIN 1 will include:

https://sam.gov/workspace/contract/opp/a9441da4747d470fb7f1cf5e65c1be14/view https://sam.gov/workspace/contract/opp/a9441da4747d470fb7f1cf5e65c1be14/view https://www.nasa.gov/general/nextstep-3-e-network-extension-for-user-continuity-and-sustainability-nexus-ka-band-backward-compatible-relay-broad/ https://www.nasa.gov/general/nextstep-3-e-network-extension-for-user-continuity-and-sustainability-nexus-ka-band-backward-compatible-relay-broad/ mailto:msfc-nexus@mail.nasa.gov

• Refinement of the proposed end-to-end service architecture, including support for backward compatibility and required coverage.

• Maturation of the system design to meet or exceed all applicable performance, functional, and interface requirements.

• Development and maturation of the verification and validation approach for all applicable requirements.

• Identification and reduction of key technical, schedule, integration, regulatory, and cost risks.

• Maturation of the demonstration approach, including how the vendor will meet the success criteria, performance validation methods, and scalability assessment.

• Development of an integrated execution schedule and critical path through demonstration and validation.

• Definition of the approach to resiliency, fault tolerance, and continuity of operations.

• Maturation of the transition-to-service plan and supporting business case including long-term service viability.

• Develop a notional long-term operational service pricing approach, including estimated recurring service pricing, any material non-recurring transition costs, key assumptions, architecture scaling factors, service levels, major cost drivers, and supporting basis-of-estimate.

4.2.1 CLIN 1 Decision Package

No later than 30 calendar days prior to the conclusion of CLIN 1, the Contractor shall submit NEXUS-DRD-012, CLIN 1 Decision Report and Presentation Package, and present a comprehensive CLIN 1 Decision Package to support NASA’s determination on whether to proceed into CLIN 2. NASA reserves the right to request clarifying details or additional information as needed.

The CLIN 1 Decision Report and Presentation Package, along with the required monthly reports, are the only DRD deliverables for CLIN 1. This Decision Package shall provide decision-quality technical, programmatic, schedule, cost, risk, verification, demonstration, and transition information sufficient for NASA to evaluate CLIN 1 progress and decide on continuation into

CLIN 2.

The written report shall be concise and decision-focused and shall not exceed 50 pages, excluding cover pages, table of contents, list of acronyms, and appendices. Appendices may include supporting technical details, data, analyses, and substantiating material, but shall not be used to avoid substantive discussion in the main body.

The Presentation Package shall summarize the key elements of the written report and be suitable for NASA’s CLIN 1 continuation review. The Contractor shall deliver an oral outbrief that presents the Decision Package and responds to NASA questions. The Presentation Package and oral outbrief support NASA’s review and discussion but do not replace the required written report.At a minimum, the Decision Package report, presentation package, and oral outbrief will address the following:

• Updated end-to-end system architecture and design solution

• Detailed requirements compliance and verification plan

• Detailed demonstration and system validation approach

• Concept of Operation Description

• Updated technical, schedule, and cost risk assessment

• Launch services approach and regulatory compliance status

• Security compliance approach and supporting details

• Updated hardware and software technology readiness assessment

• Assembly, integration, and ground test approach

• Updated external interface definitions

• Ground infrastructure definition and approach

• Updated resiliency and fault tolerance approach for continuity of operations

• Updated execution schedule, including critical path definition

• Updated transition-to-service approach

• Intellectual property and data rights approach

• Proposed post-selection engagement plan with NASA

4.3 CLIN 2: System Integration and Flight Demonstration Readiness The purpose of CLIN 2 is to integrate, verify, and mature the selected service concept into a flight demonstration-ready system and to complete the final design, test, regulatory, and pre-flight execution activities necessary to establish demonstration readiness and support progression into CLIN 3. Activities under CLIN 2 will include:

• Completion of design, procurement, assembly, integration, and ground verification activities required to produce a flight-ready demonstration system.

• Execution of long-lead procurements and resolution of supply chain constraints.

• Development and verification of ground system infrastructure and support elements.

• System-level verification of all applicable requirements, including ground testing and RF compatibility testing with legacy TDRS interfaces.

• Significant reduction or elimination of remaining technical, schedule, integration, and regulatory risks.

• Securing of all necessary licensing, regulatory approvals, and launch services required to support the on-orbit demonstration.

• Execution of the integrated schedule and price plan through assembly, integration, and ground testing.

• Finalization of the detailed demonstration approach and full validation plan.

• Finalization of the transition-to-service approach and supporting business case.

• Any updates to all prior activities/deliverables as necessary

4.3.1 CLIN 2 Entry Deliverables (Post Down-Select)

No later than 30 calendar days after CLIN 2 authorization to proceed, or as otherwise specified in the applicable DRDs, the Contractor will deliver the remaining DRDs for baseline.

This delivery will formalize the decision-quality content provided in support of NASA’s Checkpoint #1 continuation decision. Submission of these DRDs in CLIN 2 will not be interpreted as deferring the underlying maturation effort until after the continuation decision.

4.3.2 CLIN 2 Completion/Demonstration Readiness Package

No later than 30 calendar days prior to the conclusion of CLIN 2, the Contractor shall submit NEXUS-DRD-013, CLIN 2 Demonstration Readiness Package, and present a comprehensive Demonstration Readiness Review Package to support NASA’s determination regarding continuation into CLIN 3. NASA reserves the right to request clarifying details or additional information as necessary.

The written report shall be concise and decision-focused. Appendices may contain supporting technical details, data, analyses, and other substantiating material, but shall not be used to avoid providing the required substantive discussion in the main body of the report.

At a minimum, the package will address the following:

• Final end-to-end system architecture and design solution

• Final requirements compliance and verification notices

• Final demonstration and system validation plan

• Updated technical, schedule, and cost risk assessment with mitigation status

• Final launch services approach and regulatory compliance status

• Approved security compliance approach and supporting details

• Final hardware and software technology readiness assessment

• Final external interface definitions

• Final ground infrastructure definition and approach

• Final resiliency and fault tolerance approach for continuity of operations

• Overall execution schedule, including critical path definition, for the on-orbit demonstration

• Final transition-to-service approach and supporting details

• Intellectual property and data rights approach

4.4 CLIN 3: On-orbit Demonstration and Service Validation

The purpose of CLIN 3 is to execute an on-orbit demonstration of the proposed commercial relay service’s backward-compatible relay capability with one or more of NASA’s current customers and to validate, in an operationally relevant environment, that the demonstrated service meets the NEXUS demonstration success criteria, satisfies all applicable requirements, and credibly informs transition planning for a sustained operational service model. Activities under CLIN 3 will include:

• Execution of the approved on-orbit demonstration using the proposed end-to-end service architecture, including applicable space, ground, network, and operations elements.

• Demonstration of backward-compatible relay services with one or more current Government users or representative operational interfaces, as approved by NASA.

• Demonstration of operations sufficient to evaluate service performance against applicable

NEXUS demonstration success criteria, including functional, technical, operational, and interface performance.

• Collection, analysis, and delivery of demonstration data, performance results, and supporting evidence necessary for Government assessment of compliance with applicable requirements and demonstration objectives.

• Validation of the end-to-end verification and validation approach through execution of the demonstration and resolution of identified deficiencies, anomalies, or performance shortfalls.

• Demonstration of the ability to operate the proposed service in a manner that credibly supports transition to a sustained commercial service model.

• Assessment of service scalability, operational viability, and any remaining gaps, risks, or constraints relevant to transition from demonstration to follow-on operational service.

• Delivery of final demonstration reports, validation results, lessons learned, and transition recommendations to inform NASA’s evaluation of operational suitability and future service acquisition planning.

• Delivery of DRDs as defined in Appendix B

5 Proposal Submission Information Proposals received after the due date and time as defined in the notification of this solicitation in SAM.gov are considered late and will not be evaluated.

NASA will not issue paper copies of this Appendix or any documents in conjunction with this Appendix. All information will be posted electronically on http://www.sam.gov. Offerors are encouraged to refer regularly to SAM.gov and the NextSTEP-3 website for updates and other information. All other correspondence must be addressed to the Contracting Officer. The Proposal Package will be sufficiently detailed to enable NASA to evaluate the Offeror’s price, technical understanding, architectural soundness, execution credibility, risk posture, and overall readiness to mature the proposed concept into a successful end-to-end demonstration and viable transition to service.

5.1 General Format Requirements

All proposals must be submitted as a single searchable, unlocked PDF file (unless submitting proposals, which can include MS Word, MS Excel, etc.). Offerors must comply with all format and page limit requirements described herein, as well as any additional attachments. A page is defined as one sheet, 8 ½″ × 11,″ with at least one-inch margins set on all sides (i.e., Microsoft Word, Layout, Margins, Normal, 1”), using not smaller than 12-point type excluding non-substantive text used in charts, figures, illustrations, or other embedded objects (e.g., pictures or screenshots) which shall be not smaller than 10-point type. The metric standard format most closely approximating the described standard 8 ½″ × 11″ size may also be used. Other limitations/instructions are identified as follows.

• Proposals will only be accepted electronically as set forth in Attachment L, Electronic Submission of Proposals – Proposal Marking and Delivery Through NASA’s EFSS Box

(NOV 2024).

• 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 Cost/Price volume (e.g., financial statements, indirect rate letters, audit reports, letters of credit, disclosure statements, pre-award accounting system SF 1408’s) 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 as a separate folder within the single .zip file (see Electronic Submission of Proposals – Proposal Marking and Delivery Through NASA’s EFSS Box). 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 solicitation.

• 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 -o All pages must be consecutively numbered, starting with “1” (one) on the first page of each volume.

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

o The standard page size must be 8½” x 11” 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.

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

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

o Font style shall be Times New Roman and the font size shall be not smaller than 12-point for all text, excluding non-substantive text used in charts, figures, illustrations, or other embedded objects. Non-substantive text refers to text directly related merely to the identification or brief description of a subject and does not require narrative explanation to convey its meaning. Non-substantive text used in charts, figures, illustrations, or other embedded objects must not be smaller than Times New Roman 10-point font. Offerors should exercise caution when inserting charts, figures, illustrations, or other embedded objects to ensure that all text complies with the stated guidelines. This smaller font is intended to facilitate only the limited text normally associated with charts, figures, illustrations, or other embedded objects. The inclusion of narrative text in charts, figures, illustrations, or other embedded objects may be considered non-compliant text. 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.

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

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

5.2 Proposal Submission Instructions

5.2.1 Proposal Submission Format and Content

This section provides the required format and content requirements for proposal submission. All proposals must be organized according to the structure outlined in Table 5-2 below, with page limitations strictly enforced. Proposal attachments are limited to validation documentation only, which means they may contain only supporting evidence that directly validates, substantiates, or provides backup documentation for information already presented in the core proposal sections.

Proposal attachments cannot introduce new evaluation information, narratives, or claims that are not already addressed in the core sections. Offerors should ensure that all required information is complete and clearly presented, as NASA will evaluate proposals based solely on the information provided.

At proposal submission, the Offeror will provide a complete Proposal Package that includes a fair and reasonable price and demonstrates the technical credibility, feasibility, maturity, and executability of its proposed end-to-end NEXUS service solution. The Proposal Package will include preliminary content aligned to the applicable NEXUS Data Requirements Descriptions (DRDs) at the proposal maturity level.

Table 5-1 Proposal Submission Content Proposal Section Page Limitations

Title Page 1 Executive Summary 1 Table of Contents 1 Eligibility Information 1 Technical Volume (Technical Capabilities) 120 Management Volume (Management Capabilities) 35 Intellectual Property (IP) Data Assertions/Corporate Contributions Volume

Price Volume No Limit Completed Model Contract N/A

Proposal Attachments See Below Attachment A – Infrastructure Validation 10 Attachment B – Organizational Conflicts of Interest Plan 10 Attachment C - Corporate Contribution Worksheet N/A Attachment D – Proposed Milestone Acceptance Criteria and Payment Schedule

N/A

Attachment E - GFP List 5 Attachment F - Data Rights (Assertion Notice, corresponding narratives, and evidence)

Attachment G - Integrated Master Schedule 15 Attachment H - Past Performance Questionnaire N/A Attachment I – Commercial Architecture Security Questionnaire

(CASQ)

N/A

Attachment K – Pricing Worksheet N/A

5.2.1.1 Title Page

• NASA Solicitation Number

• Include any Notice of Restriction on Use and Disclosure of Proposal Information

• An optional graphic image may be included

• The Offeror’s name of the proposal

• Date of the proposal submission

• Organization name, address and CAGE Code (including 9-digit ZIP+4 code, if applicable)

• Offeror Point of Contact name, title, e-mail address, and phone number

5.2.1.2 Executive Summary

The Executive Summary consists of an overview describing the overall qualification of an offeror’s 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 should provide an overview of the proposed effort that is suitable for release through a publicly accessible archive should the proposal be selected.

5.2.1.3 Proof of Eligibility

The Offeror will document their eligibility to participate in this activity. Participation is limited to United States of America companies only.

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 their compliance and process in the performance of the resulting Appendix E. Therefore, the Offeror will comply with all U.S. export control laws including Export Administration Regulations (EAR) and International Traffic in Arms Regulations (ITAR). Offerors are responsible for ensuring that all employees who will work on this contract are eligible under export control laws, EAR, and ITAR. Any employee who is not a U.S. citizen or a permanent resident may be restricted from working on this contract if the technology is restricted under export control laws, ITAR, or EAR unless the prior approval of the Department of State or the Department of Commerce is obtained via a technical assistance agreement or an export license. Violations of these regulations can result in criminal or civil penalties.

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.

5.2.1.4 Technical Capability Volume

The Technical Volume will include content aligned to the following technical capability areas, in addition to any other items required by the solicitation.

5.2.1.4.1 System Architecture, Design, and Technical Approach

End-to-End System Architecture Concept

• Describe the proposed end-to-end service architecture, including the space, ground, network, mission operations, and user interface elements, and how those elements work together to deliver the required NEXUS capability, including support for the latency, coverage, and data rate needs of legacy TDRS-compatible users.

Operations Concept and Service Operations Approach

• Describe how the proposed service will be operated (including scheduling data delivery and user interfaces), monitored, controlled, maintained, and supported during demonstration and follow-on service operations, including routine operations, anomaly response, service management, and continuity of service.

Requirements Compliance and Verification Approach

• Describe the approach for meeting all applicable performance, functional, interface, compatibility, operational, and service requirements, including the methods by which compliance will be verified and validated.

Backward Compatibility and Interoperability Approach

• Describe how backward compatibility and interoperability will be achieved and tested with legacy TDRS-compatible Ka-band users without requiring modification to customer vehicle onboard systems, including interfaces, acquisition and tracking considerations, and how compatibility will be demonstrated during testing and on-orbit validation.

Hardware and Software Technology Readiness Initial Assessment

• Describe the maturity of the hardware, software, payload, ground, and network elements required for the proposed solution, including heritage, new development, and any technology maturation needed to support successful execution.

External Interface Definition Concept

• Describe the key external interfaces required to support user integration, service delivery, mission operations, and interoperability, including interface boundaries, assumptions, standards, and the approach for maturing those interfaces.

Ground Infrastructure Concept

• Describe the proposed ground architecture and infrastructure, including ground stations, operations centers, network transport, data routing, mission support systems, and any other enabling elements required to provide the proposed service.

Resiliency and Fault Tolerance Concept for Continuity of Operations

• Describe the approach for ensuring continuity of operations through redundancy, fault detection, fault isolation, recovery, backup operations, graceful degradation, and protection against single-point failures.

5.2.1.4.2 Demonstration, Integration, and Transition

Demonstration and System Validation Concept

• Describe the proposed on-orbit demonstration and system validation concept, including how the demonstration will prove technical performance, backward compatibility, operational utility, and readiness to transition toward sustained service, as well as the proposed success criteria, evaluation metrics, and how the demonstration will reduce continuity risk.

Mission Integration and User Transition Approach

• Describe how Government users will be integrated, how compatibility will be validated, how interfaces will mature, and how users will transition into the demonstrated and follow-on service environment.

Transition to Service and Business Approach

• Describe the approach for transitioning from demonstration to sustained service, including the technical, operational, and commercial business elements needed to support scalability, sustainment, a broader commercial customer base beyond NASA, and long-term service delivery.

Service Performance Monitoring and Reporting Concept

• Describe how service performance, availability, operational health, outages, and other relevant service metrics will be monitored, measured, and reported during demonstration and transition to service.

Security Compliance Approach

• Describe the cybersecurity and system security approach for protecting mission data, command and control functions, networks, interfaces, supply chain elements, and operational environments in accordance with applicable NASA and Federal requirements.

Complete the attached CASQ.

5.2.1.5 Management Volume

The Management Volume will include content aligned to the following management capability areas, in addition to any other items required by the solicitation.

5.2.1.5.1 Small Business Utilization

• Propose meaningful small business utilization by category and percent. The Government is open to any meaningful proposed small business utilization goal the offeror proposes so long as it is supported by the market and meaningfully stimulates the small business community. If selected for award, the small business requirements will be codified as an attachment to the contract.

5.2.1.5.2 Execution Management

Program Management and Teaming Approach

• Describe the proposed program organization, management structure, teammate and subcontractor roles, and how execution will be integrated and managed across the full end-to-end effort.

Definition of Technical, Schedule, and Cost Risks

• Identify and describe the principal technical, integration, supply chain, launch, regulatory, and schedule, risks associated with the proposed solution, including initial mitigation and risk retirement plans.

Supply Chain and Industrial Base Approach

• Describe the key suppliers, long-lead items, industrial base dependencies, and supply chain constraints associated with the proposed solution, including sourcing, production, obsolescence, and supply chain resilience risks.

Overall Execution Schedule with Critical Path Definition

• Describe the integrated execution schedule, including major activities, milestones, dependencies, long-lead items, launch and regulatory dependencies, demonstration milestones, decision points, and the critical path supporting successful execution.

Requirements, Configuration, and Technical Baseline Management Approach

• Describe the approach for managing requirements allocation, interface maturation, design evolution, configuration control, and technical baseline development across the effort.

Past Performance Describe recent and relevant experience in space systems development, satellite communications, or comparable commercial services, and provides evidence of reliable execution, schedule adherence, and overall successful performance on Government or commercial efforts of analogous scope, complexity, and value. The Offeror will use Attachment E: Past Performance Questionnaire (PPQ) for each of their identified references.

5.2.1.5.3 Launch, Regulatory, Security, and Sustainability

Launch Services and Regulatory Compliance Concept

• Describe the launch strategy and launch services concept, as applicable, and the approach for obtaining and maintaining all required regulatory approvals, licenses, authorizations, orbital debris mitigation and compliance actions needed to execute the demonstration and transition to service.

Spectrum Management and Frequency Coordination Approach

• Describe spectrum management and frequency coordination for all aspects other than

SSL Ka-Band (acquired by government) including licensing strategy, domestic and international coordination as applicable, coordination with other operators, interference mitigation, and long-term spectrum sustainability considerations.

5.2.1.6 Intellectual Property (IP) Data Assertions/Corporate Contribution Intellectual Property Concept

• Describe the approach to intellectual property, data rights, software rights, interface documentation, and any anticipated restrictions or assertions that could affect Government insight, integration, validation, sustainment, or future competition.

Corporate Contributions

• Describe any proposed corporate contributions supporting the end-to-end NEXUS service solution, including the purpose, scope, timing, estimated value, source, dependencies, associated risks, and relevance to the proposed technical approach, execution plan, demonstration, and transition to service. Clearly identify and segregate any such contributions from NASA-funded effort. Estimated value of in-kind contributions (e.g., facilities, equipment, or heritage capabilities) will be based on fair market value or other reasonable, supportable methodology.

5.2.1.7 Price Volume

Overall pricing, and Basis-of-Estimate Information

• Describe the pricing approach, including key assumptions, major price drivers, basis-of-estimate rationale, material dependencies, and proposed pricing structure sufficient to support NASA’s assessment of realism, completeness, and affordability.

• Offerors will provide separately proposed price for each CLIN.

• Offerors will assess the value associated with any proposed GTA.

5.2.1.8 Completed Model Contract

A Model Contract is provided in Attachment A of this Appendix. Please be advised that all sections designated with the text [OFI] represent “Offeror Fill-Ins”. Offerors should fill in [OFI]’s and submit as part of the signed model contract with the proposal submittal.

Additionally, sections designated with the text [TBD] stand for “To Be Determined”. Offerors should not fill in the [TBD]’s. NASA will update these after contract award. Offerors may take exception to or have unique interpretations of any model contract clauses. These exceptions and/or unique interpretations will be listed clearly in a Summary of Exceptions with supporting rationale for any and all exceptions taken. Note, taking exception to, or having unique interpretations of any required clauses may have a negative impact on potential selection. NASA does not intend to conduct negotiations.

5.2.1.9 Proposal Attachments

NASA will evaluate proposals based solely on the assertions, claims, and information presented in the proposal sections, using attachments exclusively to verify the accuracy and credibility of those statements and to conduct due diligence on offeror assertions. Offerors are responsible for ensuring that all evaluation-relevant information is clearly presented in the appropriate proposal sections within the specified page limits.