National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
Active, no response deadline listed. Full description on SAM.gov.
Overview
- Posted
- June 20, 2025
- Notice type
- Special Notice
- NAICS
- 541715: Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)
- Agency
- Department of WarIMMEDIATE OFFICE OF THE SECRETARY OF DEFENSE
Notice details
- Office
- DEFENSE INNOVATION UNIT
- Last updated
- Oct 28, 2026
- First published
- Last updated on SAM.gov
Identifiers
- Solicitation number
- HQ0845-24-S-N001
- Notice ID
- dba88354e1af4614b531b38b925ec2a2
Description
Award Overview
No prior contract identified
No prior award matched this notice's agency, NAICS, place of performance and PSC within 18 months. It may be a new requirement.
Contacts
Contracting Officer
Primary Contact
Secondary Contact
Documents
Files (1)
- Download
HQ084524SN001_CAO_amend_0004.pdf
402 KBAdded in Special Notice version 11Posted
Links (1)
- NSIC websitewww.nsic.milPosted
Lifecycle
- 1Version 1Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 2Version 2Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 3Version 3Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 4Version 4Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 5Version 5Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 6Version 6Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 7Version 7Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 8Version 8Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 9Version 9Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 10Version 10Special Notice
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
- 11Version 11Special NoticeCurrent
National Security Innovation Capital (NSIC) - Commercial Acceleration Opportunity (CAO)
Similar Opportunities
Title | Match | Phase | Deadline |
|---|---|---|---|
SPACE SYSTEMS COMMAND (SSC) System Delta 84 (SYD 84/MT) MEDIUM EARTH ORBIT MISSILE WARNING / MISSILE TRACKING EPOCH 3 and EPOCH 4 **UPDATE** 10 November 2026** The Government has updated the RFI Page Count to 50 Pages. Additionally, industry should reach out to our MEOE3IndustryEngagement@groups.af.mil for instructions for classified submittals. **UPDATE** 8 September 2026** The Government has made an update to the Response Date. The Updated Response Date is: 1 December 2026. The Inactive Policy will remain as "15 Days after Response Date." **UPDATE** 21 August 2026** The Government has made available via DoD SAFE transmissions the following documents to interested vendors (in good standing on SAM.GOV) who have contacted the Government POCs in this RFI: (CUI) MEO Epoch 3&4 Industry Day Briefing 07_22_2026 (CUI) Epoch 3&4 Market Research RFI CUI Industry Day Q&A Document 08_20_2026 (CUI) Instructions for the Release of Attachments to MEO Epoch 3&4 Market Research RFI 08_20_2026 Additionally, the Primary Point of Contact (Contracting Officer/Agreements Officer) has been updated, to Capt Kerry Kearschner, USAF. Email: kerry.kearschner@spaceforce.mil. The following companies were added to the list of entities/contractors supporting SSC/SYD 84 and its affiliated government organizations: The Tech7 Company and Galaxia If the respondent disagrees with the release of its RFI response to any of the aforementioned firms, the respondent must clearly state this restriction in the cover letter accompanying the RFI response. **END OF UPDATE** Description SSC requests industry feedback on a Resilient Missile Warning and Tracking (MWT) Medium Earth Orbit (MEO) layer Epochs 3 & 4 (E3&4) production feasibility that will support MWT Full Warfighting Capabilities (FWC). The government is seeking industry feedback to inform the MEO E3&4 acquisition strategy and technical approach. The MEO MWT architecture is being incrementally developed in capability-based deliveries called Epochs. Each Epoch is expected to include at least one competitive award and allows for insertion of new technology and innovative solutions in response to progressive or updated warfighter requirements to ultimately meet Overhead Persistent Infrared (OPIR) capability needs. This RFI requests industry feedback and approaches to support delivering a MEO MWT E3&4 capability. The government encourages capability providers to offer responses for individual or multiple elements of the system architecture: Epochs 3 & 4 Space Vehicles (E3&4 SVs) - delivery, integration, and operations MEO Ground - ground segment with facilities and sites to operate the entire MEO MWT constellation with respect to Command and Control (C2) Digital Engineering Integration in alignment with Government Digital Engineering vision Contract Type The government is intending to use only Firm Fixed Price (FFP) contract type with an Other Transaction Authority (OTA) agreement. Feedback on this approach is welcome. Small Business Consideration The North American Industry Classification System (NAICS) code for this effort is 541715 - Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology). The small business size standard is 1,000 employees. Participation from small and small disadvantaged businesses is encouraged. SSC's Small Business points of contact can be reached at smallbus@spaceforce.mil or by phone at (310) 653-1108. Small Business Opportunities The government would like to encourage small business participation in the performance of this effort and requests insight into how your company would incentivize Small Business participation. Provide an assessment of potential subcontracting opportunities. Do you have any recommendations to increase small business participation under this effort? Is there a more appropriate NAICS code to advertise this effort to maximize competition in industry? Instructions to Responders To receive the full RFI and additional supporting documentation, please send an email to the government POCs with the subject line “MEO Epochs 3 & 4 RFI – (company name)”. Include your organization’s pertinent information below: Submitter's Name and Parent Company Mailing Address/Facility: Street address, city, state, and nine-digit zip code Commercial and Government Entity (CAGE) Code Unique Entity Identification (UEI) Point of Contact (POC) POC Telephone number and email address Prime or Sub Role If Prime, identify how your firm will meet requirements set forth in 10 U.S.C. §4022 (A, B, or C) If sub, identify what capacity your firm will support and potential prime partnership (if known) CUI information can/will only be sent to company POCs listed in the SAM.Gov database. To receive the classified information, please include in the initial contact a SIPR, JWICS or comparable email address where these documents can be sent. Requesting organizations must possess a facility clearance of at least SECRET, which will be verified prior to data release. The government is also willing to physically distribute content to requesting organizations (or divisions/sectors of organizations) without electronic classified means of communication once properly cleared by our security team and proper arrangements are made with our POCs below. Format For Response SSC will endeavor to respond to all requests in the order they are received. All email responses to this RFI must include the subject line “MEO Epochs 3 & 4 RFI – (company name)”. All responses to this RFI should be provided as instructed in the RFI. Contact the POCs identified below for more information. (U) Government Representatives: Mr. Jack Barnett – jack.barnett.5@spaceforce.mil Ms. Lorene Avendaño – lorene.avendano.ctr@spaceforce.mil Mr. Archie Daquioag - archie.daquioag.2.ctr@spaceforce.mil Any information submitted by respondents to this RFI is strictly voluntary. The government encourages interested parties to submit the information requested for the applicable elements listed in the RFI by 31 October 2026 to the government points of contact listed. Please monitor SAM.Gov for further updates. DISCLAIMERS AND NOTES THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes; it does not constitute a Request for (Prototype) Proposal (RPP/RFP) or a promise to issue an RPP/RFP in the future. This request for information does not commit the government to contract for any supply or service whatsoever. Further, the government is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RPP/RFP. The government will acknowledge receipt of all submissions but is under no obligation to provide feedback or integrate respondents’ contributions. All information in response to this RFI marked proprietary will be handled accordingly. The government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with applicable regulations. (U) SSC/SYD 84 and its affiliated government organizations have entered into contracts with the following entities: AirIn Technologies, Inc. Alpha 2, Inc. Alpha Omega Group (AoG) Altus LLC Amentum Services, Inc. (formerly CENTRA) Anduril Astrion Bryce Space & Technology, LLC Booz Allen Hamilton Custom Analysis LLC Emolbi, LLC Exigo ExoAnalytics Full Rev LLC GoLion Company Integrated Enterprise System Engineering Solutions (IESE) John Hopkins University Applied Physics Laboratory (JHU/APL) KBR MMAX, Inc. MTSI Parsons Corporation PL Consulting, Inc. Qualis Corporation SAVI LLC Science Applications International Corporation (SAIC) Sigmatech, Inc. Space Systems Integration, LLC Space Engineering and Acquisition Systems (Space EA Systems) Stellar Solutions Strategic Analysis, Inc. Strategic Engineering Solutions, LLC Tecolote Research TEC Solutions, LLC The Aerospace Corporation The Institute for Defense Analyses (IDA The MITRE Corporation The Stacia Group, LLC QuantiTech Services These companies support the government’s Space Force program office by performing technical reviews, systems engineering and integration analyses, cost estimation, and other advisory services. The government hereby notifies respondents that it will provide all responses to its support contractors for their services to the U.S. Space Force. If the respondent disagrees with the release of its RFI response to any of the aforementioned firms, the respondent must clearly state this restriction in the cover letter accompanying the RFI response. Foreign firms are advised they will not be allowed to participate in this acquisition at the prime contractor level; however, provided they are eligible to do business with the U.S. Government, they may be eligible to participate at the subcontractor level. The research and test data produced under a resultant contract may contain Military Critical Technology List (MCTL) information whose export is restricted by Export Control Act (Title 22, U.S. Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401, et seq.). Request certification and registration from the Defense Logistics Services Center (DLSC), Federal Center, 74 North Washington, Battle Creek, MI 49016-3412 as soon as possible. | - | Market Research | 12/01/2026 |
Section 1: General Information Pursuant to Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO) 15.101(c), this is a Sources Sought Notice/ Request for Information (RFI) only. This notice is issued solely for conducting market research and planning purposes in accordance with RFO Part 10 and RFO Part 5. This announcement is for Market Research only and does not constitute a commitment, promise, or obligation by the Government to issue a Request for Proposal (RFP), Invitation for Bid (IFB), or solicitation of any kind. The Government will not award a contract based on responses to this notice. The Space Force Portfolio Acquisition Executive (SFPAE) for Satellite Communications and Positioning, Navigation and Timing (SATCOM and PNT) is not seeking proposals at this time and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information, bid preparation costs, or administrative expenses incurred in responding to this notice. Acquisition Attribute Program Baseline Details Notice ID / Solicitation Number SSC-GCS-MSS-SSN-2026 Sponsoring Agency / Office United States Space Force (USSF) / Space Systems Command (SSC) / MD31 Product Service Code (PSC) 1677 (Space Vehicle Remote Control Systems) North American Industry Classification (NAICS) 541715 (Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)) Classification & Security Controlled Unclassified Information (CUI) / SECRET Facility Clearance Required Response Date & Time 8 December 2026 at 3:00 PM MST Primary Points of Contact Mr. Daniel Hilger, Procuring Contracting Officer (PCO) Mr. Carl Griffin, Civil Navigation (CNAV) Project Lead Section 2: System Background & Scope of Work 2.1 Background The USSF is actively modernizing the GPS Ground Control Segment (GCS) to deliver enhanced Positioning, Navigation, and Timing (PNT) resilience and operationalize modernized civil and military signals. As part of this effort, USSF seeks to address necessary sustainment and modernization of its global PNT ground receiver network. The legacy ground control segment, the Architecture Evolution Plan (AEP), receives real-time tracking data from a total of 17 global monitor stations, 11 of which are estimated to face obsolescence in late 2028. USSF seeks options to transition to a modernized, sustainable ground segment architecture to maintain AEP's clock and orbit estimation engine (the Kalman Filter). To that end, the Government is requesting interested respondents submit statements of capability (SOCs) describing potential solutions to provide the capabilities described herein. Furthermore, the Space Force requires that any replacement ground receiver infrastructure not merely duplicate legacy capabilities but simultaneously address broader enterprise needs. The replacement architecture must serve as the primary operational enabler for: Civil Navigation (CNAV) Modernization: Providing independent, continuous signal-in-space tracking, integrity monitoring, and safety-of-life assurance for advanced civilian signals (L2C, L5, L1C) to support joint Federal Aviation Administration (FAA) and international civil aviation commitments. Military Navigation (MNAV) & M-Code Operations: Integrating secure, high-fidelity tracking of military M-Code signals to enable robust anti-jam, anti-spoof Navigation Warfare (NAVWAR) operations and Regional Military Protection (RMP). 2.2 Spectrum & Signal Tracking Requirements To demonstrate that the required monitoring capability extends beyond legacy single-frequency L-Band observables, the proposed Monitor Station Service (MSS) must provide simultaneous multi-frequency, multi-code tracking across a growing constellation (up to 63 Space Vehicles). The solution must provide continuous tracking, measurement extraction, and observable processing across the following specific signal tiers: Signal Tier Frequency / Signal Type Capabilities & Processing Requirements Legacy Signals (Baseline Parity) L1 (1575.42 MHz): L1P-codeless L1 C/A, L1P(Y) L2 (1227.60 MHz): L2P(Y) L2P-codless Continuous tracking, legacy LNAV message demodulation, pseudorange/carrier-phase measurement extraction, and legacy telemetry processing for core AEP Kalman Filter orbit/clock estimation continuity. Modernized Civil Signals (CNAV) L5 (1176.45 MHz): Safety-of-Life (SoL), L5I,L5Q L2 (1227.46 MHz): L2C (L2CM,L2CL) L1 (1575.42 MHz): L1C (L1CD,L1CP) CNAV message demodulation, multi-frequency ionospheric delay cancellation, advanced signal quality monitoring (SQM), interference/jamming detection, and civil aviation safety-of-life (SoL) processing standards to support L5 Initial Operational Capability (IOC). Military Signals (Modernized) L1 / L2 M-Code (1575.42 MHz / 1227.46 MHz): Earth Coverage & Regional Military Protection (RMP) Direct M-Code acquisition and tracking, cryptographic channel decoding via NSA-certified security architecture, advanced anti-jam / anti-spoof protections, and Modernized User Equipment (MGUE) warfighter operational support. 2.3 Core Capabilities & Scope of Work The scope of this market research centers on identifying industry capabilities and realistic timelines to deliver an integrated, secure, and safety-certified Monitor Station Service (MSS) that interfaces seamlessly with AEP and external mission partners (FAA, NGA). The Government intends to acquire and take delivery of the software baseline and associated technical data rights to ensure long-term organic C2 baseline control and sustainment within the Government boundary. The Government is seeking responses that demonstrate capability across the following core technical tasks: Integrated Multi-Signal Ingestion: Acquire, process, format, and distribute raw binary and smoothed pseudorange, carrier phase, Accumulated Delta Range (ADR), and Signal Quality Metrics (SQM) across all legacy, CNAV, and MNAV signals listed in Section 2.2. Modular API & Service-Oriented Integration: Expose receiver monitoring and control capabilities through a Modular Open Systems Approach (MOSA) utilizing standardized Application Programming Interfaces (APIs) and messaging layers to decouple data feeds from underlying receiver hardware. Safety-of-Life Signal Assurance: Support rigorous software design assurance standards (certifiable up to Design Assurance Level D / DAL D per RTCA DO-278A / DO-178C) to provide real-time signal deformation detection, Code Carrier Coherence (CCC), and anomalous event alerting. Cryptographic & Boundary Security: Provide NSA-approved cryptographic handling capabilities for military key management, secure unclassified/classified cross-domain boundary routing, and continuous Risk Management Framework (RMF) security control validation in a secure government cloud/on-prem environment (IL5/IL6) to maintain an active DoD Authority to Operate (ATO). Receiver Security Certification (FSET): Provide receiver hardware, software, and firmware capable of achieving or maintaining security certification through the Space Systems Command (SSC) Functional Security Engineering Team (FSET) for deployment across global, unclassified, and collateral Secret monitoring locations, including supporting delta FSET recertification processes for component and cryptographic updates. Section 3: Information Requested from Industry To assist the government in conducting its statutory market research, all respondents are requested to organize their capability statements into the following structured sections: Part A: Corporate Profile Administrative Details: Company Name, Mailing Address, CAGE code, and Unique Entity ID (UEI). Socioeconomic Status: State your business size and any applicable socioeconomic designations under NAICS 541715 (e.g., Small Business, 8(a), HUBZone, SDVOSB, WOSB, etc.). Facility Clearance: Confirm whether your company possesses an active, DOD-approved SECRET Facility Clearance (required for ground segment integration testing and operations). Existing Government Contract Vehicles: List any existing competitive contract vehicles, such as multiple award indefinite delivery indefinite quantity (MAC IDIQ) contracts, under which your company is currently approved to provide similar scope to that described in this notice. Part B: Technical capability Questionnaire Respondents must provide detailed, objective, and verifiable evidence of their capability to execute these requirements. The Government will evaluate vendor capability based on two distinct grading factors: A. Core Competency Alignment: Direct evidence (e.g., past performance references, specific contracts, and operational program details) demonstrating corporate core competencies that directly translate to GPS ground segment development, real-time receiver data processing, or Kalman filter integration. B. Technical Component Maturity: Degree of verified proof that the proposed hardware and/or software components currently exist in a mature state (e.g., Technology Readiness Level 6 or higher). Respondents must show that any necessary modifications or delta-developments can realistically be completed within the program timeframes discussed below in Section 3, Part B(i). Note: Broad technical narratives, marketing descriptions, or unsubstantiated claims of capability without supporting engineering or programmatic evidence will be considered "High Risk." i. Schedule & Programmatic Feasibility: The Government is executing a phased acquisition strategy to mitigate receiver network obsolescence while fully modernizing ground monitoring capabilities. The Government desires an incremental capability delivery and operational acceptance plan structured as follows: Phase 2.1 (Replace Operational P(Y) Data Feed - Target: Late 2028): Development, testing, fielding, and operational acceptance of the critical subset of Legacy Signals referenced in Section 2.2, necessary to replace legacy signal in space tracking feeds prior to earliest planned obsolescence with zero disruption to the AEP Kalman Filter. This effort includes integration of the solution with the currently operational GPS ground system (AEP) in accordance with ICD-GPS-211, in cooperation with the ground system prime contractor. Phase 2.2 (Remaining Core Capabilities - Target: Late 2030): Full development, testing, fielding, and operational acceptance of all remaining core capabilities (including advanced CNAV/MNAV tracking, DO-278A safety assurance, and full NSA cryptographic security certification). This effort should include scope to integrate the solution with AEP. A strict interface specification does not currently exist for this capability, but it is desired to limit integration scope imposed on the AEP system. Phase 2.3 (Additional Capabilities - Target: CY2032 Desired): Incremental delivery of the lower-priority system preferences defined in Section 3.0, Part D (Additional Capabilities). Note if capacity exists to accelerate development of one or some of these earlier, pursuant to evolving military priority (e.g. multi-Global Navigation Satellite System (mGNSS) monitoring). This additional capability is expected to primarily be compatible with a future GPS ground system not yet developed. Open interface standards desired. This scope included for consideration to address transition of the baseline monitoring approach from Phases 2.1-2 from AEP-compliant solution to one compatible with the next-generation system. Describe your programmatic and engineering strategy to deliver these capabilities incrementally, including a phased, notional Integrated Master Schedule (IMS) mapping your mature components to these specific milestones. ii. Rapid Duplication & Continuity under an Urgent Operational Need (UON): Given the operational necessity to modernize ground monitoring capabilities, what is your technical approach to integrate and field an alternative monitor station data stream? Specifically address how you will mitigate risks associated with legacy system integration (AEP) and ensure zero loss of mission continuity for the Kalman Filter. iii. MOSA & Extensible Architecture Design: How will you design the ground monitoring architecture to be inherently extensible, ensuring it can seamlessly support both CNAV (L5 IOC/Full Operational Capability (FOC)) safety-of-life requirements and expanded constellation tracking (up to 63 SVs) without imposing restrictive assumptions or design constraints on future enterprise-level architectural evolution? Describe your approach to utilizing a Modular Open Systems Approach (MOSA) to expose receiver monitoring and control capabilities through standardized Application Programming Interfaces (API), effectively decoupling the data services from the underlying receiver hardware. iv. GPS Multi-Signal Domain Experience Cryptographic Handling & FSET Certification: Describe your technical approach for acquiring, processing, and distributing raw binary observables, smoothed pseudorange, carrier phase, and Signal Quality Metrics (SQM) for the complete GPS signal suite defined in Section 2.2 Detail your technical expertise and proven methodologies for managing NSA-certified cryptographic functions, secure key loading, and anti-spoof/ anti-jam protections associated with M-Code and P(Y)-code operations. Describe your familiarity and track record with obtaining and sustaining receiver security certification through the Space Systems Command (SSC) Functional Security Engineering Team (FSET), including navigating delta FSET evaluation cycles for firmware and hardware obsolescence updates. Describe your company’s capabilities in certifying safety-critical software against RTCA DO-178C/DO-278A standards. Responses should address your approach to meeting various Design Assurance Levels (DALs). v. Accelerated Test & Evaluation (T&E) and DevSecOps Integration: Balancing the need for rapid deployment under an urgent operational need with the statutory T&E requirements, describe your methodology for integrating developmental testing, operational assessments, and cybersecurity authorization concurrently to compress the timeline to formal operational acceptance. Describe your approach to implementing continuous DevSecOps pipeline controls, automated patch testing, and RMF control validation within an IL5/IL6 cloud or hybrid environment to maintain a continuous DoD ATO without disrupting 24/7 space control operations. vi. Transition and Technical Baseline Assumption: Considering that the Government is actively managing ongoing technical baseline and interface definitions under exploratory phases, what is your specific methodology for assuming an active, ongoing development effort? How will you validate pre-existing API definitions, data dictionaries, and interface control documents (ICDs) to prevent schedule degradation? vii. Initial Operational Sustainment & Obsolescence Lifecycle Strategy: Describe your approach to providing initial operational sustainment, Level 1 operational support/ incident triage, depot-level support, and preventive maintenance inspections (PMIs) across globally distributed remote monitoring sites. How will you identify, monitor, and mitigate hardware and software Line Replaceable Unit (LRU) component obsolescence (e.g., FPGAs, time servers, network routing equipment) to ensure continuous system availability (> 98%) through at least CY2035? Part C: Acquisition & Business Strategy i. Cost & Affordability: Provide a high-level, notional Rough Order of Magnitude (ROM) cost estimate for delivering the Monitor Station Service (MSS) capability across development, integration, and initial fielding, and identify your primary cost drivers. ii. Delivery Model & Operational Concept: Describe your proposed delivery model (e.g., software/hardware delivery, managed service, or hybrid) and summarize your operational concept, including nominal day-to-day operations, anomaly alerting, fault recovery, and any data rights constraints. Explicitly detail your technical data rights assertions and confirm your capability to deliver the complete software baseline and interface control definitions to the Government. iv. Government Furnished Property/ Information (GFE/GFI): What specific Government-furnished information, data, equipment , software, or facility access would your company require from the Government to successfully execute this effort? v. Contract Type: What contract type(s) (e.g., Firm-Fixed-Price, Cost-Plus-Incentive-Fee, etc.) would you recommend to best incentivize performance and manage risk? Part D: Additional Capabilities The capabilities outlined below represent secondary system preferences. As outlined in the Schedule and Programmatic Feasibility section, these capabilities are exempt from the core Objective and Threshold timeline constraints. Respondents should address if and how your approach to meeting core requirements would be impacted to satisfy these secondary requirements. Options for future system extensibility to incrementally develop/deliver these capabilities are desired. i. Scalability and Constellation Expansion: Describe the scaling and expansion limits of your proposed receiver architecture. Specifically, detail your system’s capability or planned roadmap to support simultaneous tracking of 64+ Pseudo-Random Noise (PRN) codes across all active GPS frequencies, and how this architecture mitigates signal bottlenecks as the constellation expands. ii. Technical and Infrastructure Optimization: Detail how your proposed architectural design minimizes physical, cyber, and maintenance overhead at globally deployed, remote unmanned sites. Highlight the utilization of innovative techniques, such as Software-Defined Radio (SDR) technologies, remote signal correlation, data compression, and modernized communications infrastructure, to reduce the footprint and complexity of local physical deployments. iii. Dual Concept of Operations (CONOPs): Describe extent your solution can support dual operations (C2 from legacy and next-generation control segments) such that they can support sending data at different data rates to each ground segment. iv. Flexible Signal: Describe extent your solution could support monitoring flexible signal in space waveforms generated by reprogrammable payloads on future planned GPS spacecraft. v. MOSA-enabled monitoring disaggregation: Ingesting data from other sources (e.g. National Oceanic and Atmospheric Administration’s (NOAA) Continuously Operating Reference Stations (CORS), Jet Propulsion Lab’s (JPL) monitoring network, commercial receiver vendor networks, etc.) and support to potential on-orbit distributed Kalman filters (e.g. autonav) to allow expanded and rapid deployment of new monitoring capabilities. vi. Coverage: Capacity to economically expand worldwide monitoring coverage (e.g., resolve pacific gap) to ensure good monitoring station distribution across the latitudes and increase the number of monitoring stations in view of each spacecraft. vii. Multi-GNSS Monitoring: Describe your solution's ability to monitor multi-GNSS signals (including RNSS constellations), determine signal integrity and derive independent navigation data. Section 4: Submission Instructions 4.1 Response Guidelines Technical Approach & Teaming: Submissions should describe the respondent's technical approach and capability to satisfy the integrated scope of work outlined in Section 2. Any proposed teaming arrangements, joint ventures, or partnership structures utilized to meet these requirements must be clearly identified, if applicable. Page Limit: Submissions must not exceed 15 single-sided pages. The Cover Page, Table of Contents, Acronym List, and notional IMS attachment (if provided as a separate 1-page roadmap/diagram) are excluded from this page limitation. Formatting Requirements: Text must be in 12-point Times New Roman font, single-spaced, with margins set at 1 inch on the top, bottom, left, and right of each page. File Format: Responses must be submitted electronically in Adobe PDF format. Due Date: All responses must be received no later than 8 December 2026 at 3:00 PM MST Subject Line: All submission emails must use the subject line: RFI Response: SSC-GCS-MSS-SSN-2026 [Company Name]. 4.2 Proprietary & Sensitive Information The government will safeguard any proprietary information or trade secrets identified in responses to this notice in accordance with the Trade Secrets Act (18 U.S.C. 1905). Respondents are solely responsible for clearly marking and identifying any proprietary, restricted, or sensitive data. Please mark the cover page and individual pages containing such information as: PROPRIETARY - CONTAINS BUSINESS SENSITIVE INFORMATION | - | Market Research | 12/08/2026 |
1. Purpose and Program Background The Space Systems Command’s Space Data Network Backbone (SDN-B) program office is fielding a proliferated, integrated, vendor-diverse space-to-space communications mesh in Low Earth Orbit (LEO) leveraging commercial product baselines from across the industrial base. This mesh forms the critical communications backbone of the Space Data Network (SDN). SDN-B has established the Space Data Network (SDN) Industry Consortium to cultivate a collaborative public-private partnership focused on addressing high-priority technical integration and architectural challenges across the proliferated LEO (pLEO) space-to-space communications mesh. This announcement is an open, one-step call for white papers to serve as market intelligence, informing the Government of the capabilities of the industrial base to meet current and future SDN requirements. Based on this market intelligence, the Government may onboard individual companies into the SDN consortium. 2. Consortium Construct & Terms of Participation Agreement Mechanism: Selected industry members will enter the consortium as Associate Members under a $0-value Other Transaction Agreement (OTA) executed pursuant to 10 U.S.C. § 4022. Scope of Engagement: Consortium members will participate in regular collaborative forums, technical working groups, and architectural interchange meetings chaired by the Government. Activities include technical interoperability assessments, standards formulation, risk reduction discussions, and multi-vendor on-ramp coordination. Agreements & Non-Disclosure: Participating organizations will be required to execute Associate Contractor Agreements (ACAs) and implement Organizational Conflict of Interest (OCI) and proprietary information protection strategies to enable cross-industry and Government information exchange. Nature of Notice: This notice does not constitute a formal Request for Proposals (RFP) or a commitment by the Government to fund any development. Membership does not guarantee future contract awards or delivery orders. 3. Technical Focus Areas Submissions must directly demonstrate how the respondent’s current or planned commercial capabilities, roadmaps, and technologies align with and contribute to the SDN architecture across one or more of the following domains: Proliferated Space Architecture Space Networking & Routing Optical Inter-Satellite Links (OISL) Radio Frequency (RF) Mesh & Communications Payload Hosting & Interface Standardization Ground Architecture & Space-Ground Entry RF Antennas and Receivers Cybersecurity & Cross-Domain Security 4. Eligibility Requirements Ownership: Consortium membership is strictly restricted to U.S.-owned and operated entities. Foreign-owned, foreign-controlled, or foreign-influenced companies are not eligible. Information Handling & Security Clearances: Baseline Minimum: Respondents must possess existing facilities, systems, and personnel infrastructure capable of storing, processing, and transmitting information at a minimum of the Controlled Unclassified Information (CUI) level (in compliance with NIST SP 800-171 / DoD CMMC standards). Higher-Level Capabilities Welcomed: Capabilities to hold and process classified information (e.g., Secret, Top Secret / SCI, and associated Facility Security Clearances (FCL) exceed the minimum threshold. Respondents holding higher clearances and secure facilities should annotate their current safeguarding and facility clearance levels in their cover sheet and white paper for future collaboration planning. SAM Registration: Respondents must possess an active entity registration in SAM.gov under NAICS 541715 prior to submission. 5. Submission Instructions and Format This is a streamlined, single-step process. Respondents shall submit a concise package strictly conforming to the following volume and page constraints: Volume Content Page Limit Format Cover Sheet Administrative details, CAGE, UEI, points of contact (POCs), CUI/Clearance level declaration 1 page PDF White Paper Technical contribution and commercial alignment to SDN 2 pages max PDF Contextual Pitch Deck (Optional) Commercial product background / architecture context Up to 10 content slides (include a cover slide if submitted) PDF or PPTX Page and Document Formatting: Cover Sheet (1 Page): Must include company name, CAGE code, Unique Entity Identifier (UEI), corporate address, confirmation of 100% U.S. ownership, affirmation of CUI processing capability (including notation of any higher facility/personnel clearances held), and designated Technical and Contracting POCs (name, title, phone, email). White Paper (2 Pages Maximum): Must succinctly answer: Consortium Contribution: How the organization can contribute technical expertise, test capabilities, facilities, tools, or data to the consortium. Architecture Alignment: How the organization’s current or planned commercial products, independent research and development (IR&D), and architectures align with the SDN pLEO mesh baseline. Formatting: 8.5 x 11-inch pages, 1-inch margins, minimum 11-point font (tables/graphics no smaller than 9-point). Pages exceeding the 2-page limit will not be reviewed or evaluated. Contextual Pitch Deck (Optional, up to 10 Slides): Respondents may attach an excerpt of up to ten (10) slides from their commercial or government briefing/pitch deck to provide additional visual context on technology readiness or architectural topologies. A single title/cover slide should be included and does not count against the 10-slide limit. 6. Submission Delivery & Inquiries Submissions must be delivered no later than 23 November 2026 at 17:00 Pacific Time (PT). Late submissions will not be reviewed. Submissions may be delivered via either of the following methods: Direct Email: Submit unclassified/non-CUI packages directly via email to all designated Government POCs listed below with the subject line: [SDN Consortium White Paper] - [Company Name]. DoD SAFE Drop-Off (Mandatory for CUI submissions): To transmit CUI or file sizes exceeding email limits, respondents must send an email to all POCs below requesting a DoD SAFE drop-off no later than 3 business days prior to the close date with the subject line: [SDN Consortium DoD SAFE Request] - [Company Name]. Submissions via DoD SAFE must be encrypted. 7. Market Intelligence & Consortium Membership The Government will use this market intelligence to determine the industrial base’s ability to meet current and future SDN-B requirements. As a result of the review of the Government research, the Government may choose to onboard consortium members. The Government reserves the right to invite zero, one, some, or all respondents to join the consortium. The Government makes consortium onboarding decisions based on the following: Applicability & Relevance: Direct technical applicability of the proposed capabilities to the SDN proliferated LEO mesh architecture. Commercial & Technical Maturity: Credibility, maturity, and on-ramp feasibility of the vendor’s commercial offerings or near-term roadmaps. Consortium Value: Ability and willingness of the vendor to actively collaborate, share interface insights, and support multi-vendor standards. 8. Use of Non-Government Advisors Respondents are advised that data submitted in response to this notice may be released to non-Government advisors supporting SSC/SZW under existing advisory and assistance contracts. All non-Government advisors are bound by Non-Disclosure Agreements (NDAs) and organizational conflict of interest terms prohibiting them from engaging in SSC-sponsored commercial competition: ACT-1 AirIn Technologies, Inc. Alpha 2, Inc. Altus LLC Amentum Services, Inc. (formerly CENTRA) ARK Government Solutions Inc. Booz Allen Hamilton Bryce Space & Technology, LLC Custom Analysis LLC Emolbi, LLC Full Rev LLC GoLion Company IDFP Enterprises, Inc. KBR (Trinzic) LinQuest Corporation Massachusetts Institute of Technology, Lincoln Laboratory (MIT/LL) MMAX, Inc. MTSI PL Consulting, Inc. QinetiQ Qualis Corporation SAVI, LLC Science Applications International Corporation (SAIC) Sigmatech, Inc. Space Systems Integration, LLC Space Analysis, Inc. Stellar Solutions Strategic Engineering Solutions, LLC Tecolote TEC Solutions, LLC The Aerospace Corporation The Stacia Group, LLC The MITRE Corporation Zachary Piper Solutions Any objection to the release of information to these non-Government advisors must be submitted in writing to the Agreements Officer within five (5) calendar days of notice publication, identifying the specific advisor and detailed basis for objection. 9. Points of Contact Procuring Contracting / Agreements Officer (PCO/AO): Melanie Gipson Space Systems Command (SSC/SW) Email: melanie.gipson@spaceforce.mil Contracting / Agreements Specialist: Leslie Semerena Space Systems Command (SSC/SW) Email: melanie.gipson@spaceforce.mil Government Program Manager (PM): Maj Foster Davis Space Systems Command (SSC/SW) Email: foster.davis@spaceforce.mil Technical Point of Contact (TPOC): Ryan Colburn Space Systems Command (SSC/SW) Email: ryan.colburn.1.ctr@spaceforce.mil | - | Market Research | 11/23/2026 |
The Space Development Agency (SDA) intends to issue a modification to the sole source, Firm-Fixed-Price (FFP) contract number FA240125C0001 awarded to Space X (CAGE 9ADW9). This modification will enable SpaceX to continue its support of a satellite processing and integration facility to accommodate up to 21 satellites and associated dispenser hardware for the SDA. This facility will support post-transport functional testing as required, satellite mechanical and electrical mates to the dispenser hardware, and integrated payload stack encapsulation. The planned firm-fixed price contract modification is anticipated to be awarded in December 2026. The modification will extend the period of performance for 1 year. The total estimated value of the extension is $15,000,000. This award of this modification will be made under the authority of FAR 6.302-1, Only One Responsible Source and No Other Supplies or Services Will Satisfy Agency Requirements, 10 U.S.C. 3204 (a)(1). This is NOT a request for competitive proposals and is published for informational purposes only. Questions or comments related to this Notice of Intent shall be directed to ussf.pentagon.sda.mesg.sn-26-0002-mbx@mail.mil (phone calls/voicemails will not be accepted and will not receive a response). Please indicate in the subject of your email: Notice of Intent to Sole Source – SDA-SN-27-0002. | - | Special Notice | 10/30/2026 |
In accordance with the FY25 National Defense Authorization Act (NDAA) §874, Establishment of Pilot Program for Access to Shared Classified Commercial Infrastructure, the Department of War Innovation Unit (DIU) would like to expand the number of available Nontraditional Defense Contractors seeking access to, and competing for, classified contracts issued by the Department of War (DoW). This pilot solicitation titled, “Classified Access to Address Critical Technology (CLASS ACT)”, seeks to assist entities with capabilities or technology highly relevant to the DOW to gain facility clearances so that they can bring their innovation to the Department, and help solve classified technical challenges. This solicitation and its accompanying instructions constitute a pilot program under 10 U.S.C. § 4022. DIU anticipates that topic areas, submission and evaluation criteria, and administrative guidelines will undergo active iteration and amendments following initial implementation based on operational insights and participant feedback. Potential offerors should reference amendments to this solicitation for updated guidance and revised solicitation instructions. Amendment 0001 revised paragraph 5.1.d., with the underlined text: "Offerors may receive an offer to enter into an Other Transaction Agreement, a Request for Prototype Proposal (RPP), or a proposed bailment agreement. Being asked to submit a proposal does not guarantee that an offeror will receive an award. DIU reserves the right not to make an award and will not reimburse offerors for costs associated with proposal preparation." | - | Special Notice | Open |
Additional Details
Solicitation Number
HQ0845-24-S-N001
Archive Date
Jun 20, 2028
Office Address
MOUNTAIN VIEW, CA, 94043