About this file

This is a Final Solicitation document for a Two Phase Closed Variant Commercial Solutions Opening (CSO) issued by the United States Space Force (USSF) Satellite Communication Augmentation Resource (SCAR) Program Office under the Missile Defense Agency's Nimble Options for Buying Layered Effects (NOBLE) Multiple Authority framework. The SCAR PMO seeks innovative prototype solutions for modern Ground Entry Point (GEP) and Network Operations Center (NOC) capabilities to modernize the USSF Satellite Control Network, providing robust Telemetry, Tracking, and Commanding (TT&C) capabilities across all orbital regimes. The solicitation is designated HQ0860-26-S-C008 and uses NAICS code 541715 with PSC 5985. White Papers are due by 14:00 MDT on October 15, 2026, submitted electronically via DoD SAFE. All communications should be directed to Agreement Specialist Erica Talley (Erica.Talley.2.ctr@spaceforce.mil) and Agreement Officer Lee Mutschler (Lee.Mutschler@spaceforce.mil).

The solicitation addresses three distinct Areas of Interest (AOIs): AOI 01 focuses on Rapid Fielding of Government-Owned and Contractor-Operated Commercial TT&C Capabilities; AOI 02 addresses Exclusive Use Leased Commercial Antenna Capacity on Commercial Sites; and AOI 03 seeks Antenna as a Service (AaaS) solutions utilizing shared global commercial networks. All proposed solutions must achieve Technology Readiness Level (TRL) 7-9 as defined by DoD guidelines, with TRL 8-9 required for AOI 03. Firm-Fixed Price arrangements are highly desired, with pricing models submitted in Microsoft Excel format. Awards will be made as Other Transaction Agreements (OTAs) for prototype projects under 10 U.S.C. § 4022, with the Government reserving the right to award non-competitive follow-on production contracts to successful participants. OTA awards require either significant participation by a non-traditional defense contractor or small business, or the offeror must provide at least one-third of total project cost from non-Federal funds. Phase 2 proposals will only be accepted from offerors invited after Phase 1 White Paper evaluation and must include detailed technical volumes (20 pages maximum for evaluation factors), Statement of Work, pricing documentation, and administrative materials including organizational conflict of interest analysis. Facility Security Clearance at Secret level or higher is required at White Paper submission; offerors must possess an Active DD Form 2345 to access export-controlled CUI documents in the Offeror's Library, which includes the Technical Requirements Document (TRD), Statements of Objectives (SOOs), Use Cases, security implementation guidance, and other baseline documents tailored by AOI.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Two Phase Closed Variant

HQ0860-26-S-C008

United States Space Force (USSF)

Battle Management, Command, Control, Communication and Space Intelligence (BMC3I) Satellite Communication Augmentation Resource (SCAR) Program Office (PMO)

Commercial Solutions Opening (CSO) Two Phase Closed Variant

Solicitation No. HQ0860-26-S-C008

Utilizing the Missile Defense Agency (MDA) Nimble Options for Buying Layered Effects (NOBLE)

BMC3I

Table of Contents

1. Overview6
1.1. Federal Agency Name6
1.2. Program Office:6
1.3. Solicitation Title/No.6
1.4. Solicitation Type6
1.5. Solicitation Period6
1.6. NAICS Code6
1.7. Product Service Code (PSC)6
1.8. Communications and Points of Contact (POC)6
1.9. System for Award Management (SAM)7
1.10. Program Security Requirements7
1.11. Requesting Access to the Offeror’s Library and Distribution of Documents7
1.12. Submission Overview8
2. SCAR PMO Specific Mission, Areas of Interest, and Problem Statements9
2.1. Issuing Organization Mission9
2.2. SCAR PMO Specific Areas of Interest (AOI) and Problem Statements for this Solicitation9
2.2.1. AOI 01: Rapid Fielding of Government Owned and Contractor Operated Commercial TT&C Capabilities9
2.2.2. AOI 02: Exclusive Use Leased Commercial Antenna Capacity on Commercial Sites10
2.2.3. AOI 03: Antenna as a Service (AaaS)11
2.2.4. DoD Technology Readiness Assessment Guidebook (February 2025) Hardware TRL Definitions (Table 1)12
2.2.5. DoD Technology Readiness Assessment Guidebook (February 2025) Software TRL Definitions (Table 2)12
3. NOBLE Framework, Topic Area, and Authority Used for This Solicitation13
3.1. The NOBLE MAA Framework13
3.2. NOBLE MAA Topic Areas for This CSO14
3.3. CSO Statutory Authority and Follow-on Production Authority14
3.4. DoW Policy Alignment15
4. CSO Provisions and Additional Information15
4.1. Data Rights15
4.2. Foreign Participation:15
4.3. Non-Government Advisors15
4.4. Organizational Conflicts of Interest15
4.5. Non-Traditional Defense Contractor (NDC) Status16
4.6. Government Furnished Property (GFP) Availability16
4.7. Definitions16
5. Evaluation and Selection Process18
5.1. General Information18
5.2. Interchanges18
5.3. Evaluation Process18
5.4. Evaluation Factors19
5.4.1. Phase 1 –White Paper Evaluation Factors19
5.4.2. Phase 2 – Proposal Evaluation Factors19
5.5. Technical Ratings20
5.5.1. Recommended21
5.5.2. Selectable21
5.5.3. Not Selectable21
5.6. Offeror Feedback21
6. Phase 1 Submission22
6.1. White Paper Format22
6.2. White Paper Content22
6.2.1. Cover Sheet22
6.2.2. Technical Factor22
6.2.3. Importance to SCAR Program Requirements Factor23
6.2.4. Foreign Ownership, Control, or Influence (FOCI)23
7. Phase 2 Submission24
7.1. Proposal Format24
7.2. Proposal Content24
7.2.1. Cover Sheet24
7.2.2. Technical Volume25
7.2.3. Price Volume32
7.2.4. Administrative Requirements Volume34
8. Organizational Conflict of Interest (OCI) Checklist38
8.1. Contract or Subcontract Identification38
8.2. Magnitude of Work (Your Company Base)39
8.3. Magnitude of Work (Subcontractor Effort)39
8.4. Prime Contractor Information39
8.5. Scope and Regulatory Applicability39
8.6. Detailed Scope of Effort40
8.7. Access to Government Systems40
8.8. Potential Conflict Identification40
8.9. Mitigation Plans40
8.10. Former DoD Personnel Assistance41
9. CSO Offeror’s Library Table of Contents42

Overview Federal Agency Name United States Space Force (USSF) Program Office:

Satellite Communication Augmentation Resource (SCAR) Solicitation Title/No.

SCAR Commercial Solutions Opening (CSO) HQ0860-26-S-C008 Solicitation Type This CSO is a Two Phase Closed Variant. This approach allows for White Paper and proposal submission at the date and time specified in the CSO.

Solicitation Period White Papers must be received no later than 14:00 MDT Thursday, 15 October 2026. After evaluation of White Papers, the Government will issue an invitation to provide a proposal in response to either a Request for Proposal (RFP) or Request for Prototype Proposal (RPP) or a non-selection letter.

NAICS Code 541715 - Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology) Product Service Code (PSC) 5985 Antennas, Waveguides, and Related Equipment Communications and Points of Contact (POC) All communication regarding this solicitation should be UNCLASSIFIED and sent to both the Agreement Specialist Erica Talley at Erica.Talley.2.ctr@spaceforce.mil and Agreement Officer Lee Mutschler at Lee.Mutschler@spaceforce.mil. DO NOT EMAIL CLASSIFIED INFORMATION. Due to the large amount of expected interest in this CSO, and to maintain a written record of questions, these are the only email addresses that will be used for general question communication. The following shall be utilized in the email subject line: (AOI X) SCAR Solicitation No. HQ0860-26-S-C008, where X is replaced with the identified AOI.

Dialogue with any Government representative related to this solicitation shall not constitute a commitment by the Government. Any dialogue that takes place will not be taken into consideration during evaluation of responses to this solicitation. Only Agreements Officers are legally authorized to make commitments on behalf of the Government.

System for Award Management (SAM) Offerors responding to any individual solicitation under this announcement must be registered in the System for Award Management (SAM) at https://www.SAM.gov at time of response and prior to any award. This includes completion of any required representations and certifications.

Program Security Requirements Award(s) resulting from this solicitation will contain a DD Form 254 DoD Contract Security Classification Specification. Any offeror responding to the CSO must possess the minimum clearance required by the DD Form 254 at the time of White Paper submission. Exceptions will only be granted in accordance with federal law.

Requesting Access to the Offeror’s Library and Distribution of Documents This solicitation includes an “Offeror’s Library” (see Section 9) with documents marked as Controlled Unclassified Information (CUI). The documents include CUI Categories Controlled Technical Information (CTI) and Export Controlled (EXPT). In order to access the CUI documents marked EXPT, the Offerors must possess an Active DD Form 2345 Militarily Critical Technical Data Agreement searchable in the Defense Logistics Agency (DLA) Joint Certification Program (JCP) Portal at https://www.dla.mil/logistics-operations/services/joint-certification-program/. Interested offerors must have their Data Custodian email the following information to the Points POCs identified above:

• Company name and official mailing address

• Data Custodian contact information (email and phone number)

• Commercial and Government Entity (CAGE) Code Offerors who do not possess an Active DD2345 will only have access to documents without a CUI EXPT marking. In order to access the CUI documents in the Offeror’s Library, Offerors must have at least a Computer Maturity Model Capability (CMMC) Level II Self-Assessment in Supplier Performance Risk System (SPRS) at https://www.sprs.csd.disa.mil/.

The Offeror’s Library documents will be distributed to the requesting Offeror once the SCAR PMO has verified its Data Custodian and SPRS score as described above. Documents from the Offeror’s Library will be sent to eligible Offerors via the DoD Secure Access File Exchange (SAFE) website https://safe.apps.mil/. DOD SAFE drop off email and passphrase allowing access and pick-up of documents will be provided. Any previous Non-Disclosure Agreement(s) (NDAs) executed under the SCAR Increment 1 Sources Sought will not be considered sufficient to request documents from this solicitation’s Offeror’s Library.

The Government reserves the right to negotiate and/or adjust any of the Offeror Library documents prior to award. The Offeror Library will remain open until the due date for White Papers submission.

Submission Overview

· Submissions received after any due dates specified in the CSO will not be reviewed.

· The Government will not reimburse companies for the costs associated with submissions for any phase.

· Submissions for all phases shall be sent electronically. Hardcopies for any phase will not be accepted.

· Offerors shall appropriately and conspicuously mark each page of the Phase 1 and Phase 2 submissions that contain proprietary information the includes restrictions on disclosure and use of the data.

This CSO is a Two Phase Closed Variant which will be conducted in two phases. Phase 1 is structured to provide the Government with an initial White Paper for solutions while Phase 2 captures proposal submission. The Government reserves the right to invite one, some, all, or none of the Offerors to submit a proposal under Phase 2.

Phase 1: White Paper: Offerors submit a detailed technical white paper describing their innovative solution addressing the specific AOI(s) selected. The PMO will utilize the DoD SAFE website https://safe.apps.mil/ for the submission of Phase 1: White Papers by the date and time specified in this solicitation. Vendors must request a drop off code from the POCs identified above no later than three days before the response deadline. SAFE will no longer allow you to submit your response without a drop off code.

Phase 2: Request for Proposals (RFPs) or Request for Prototype Proposals (RPPs): Offerors selected from Phase1 are invited to submit a full, formal proposal. Phase 2 proposals will only be accepted from Offerors who, upon review of Phase 1 submission, have received a request from the Agreement Officer (AO). The PMO will utilize the DoD SAFE website https://safe.apps.mil/ for the submission of proposals. Vendors must request a drop off code from the POCs identified above no later than three days before the identified response deadline. SAFE will no longer allow you to submit your response without a drop off code.

The Government encourages proposals that span a wide spectrum of possible technical and business solutions in response to this Two Phase Closed CSO. Each AOI identifies a broadly defined individual interest area covering the full range of program requirements. All submissions in response to any AOI will be governed by this Two Phase Closed CSO.

Firm-Fixed Price (FFP) arrangements are highly desired by the PMO and will be maximized. Other fixed-price type arrangements including fixed price incentives may be considered when supported by risk analysis.

Upon favorable evaluation, the Government may choose to award an OTA for Prototype project as deemed appropriate for the transaction. The Agreements Officer will negotiate directly with the Offeror on the terms and conditions of the OTA, including payments, and will execute the OTA on behalf of the Government.

This CSO is focused on the prototype project only. The decision to proceed with a follow-on production award will depend on the successful results of the prototype, the availability of funding, and the approval of a future acquisition strategy. A follow-on production award is not guaranteed.

Awards resulting from this CSO will be made based on the process described in section 5, Evaluation and Selection Process. The Government reserves the right to fund all, some, one, or none of the Phase 2 proposals submitted. All awards are subject to the availability of funds.

All coordination and communication between Offerors and the Government will be conducted as specified in section 1.8, Communications and Points of Contact (POC).

SCAR PMO Specific Mission, Areas of Interest, and Problem Statements Issuing Organization Mission The SCAR program requires complete systems that are Technology Readiness Level (TRL) 7-9 as defined in the Department of Defense (DoD) Technology Readiness Assessment Guidebook (February 2025). (Reference Tables 1 and 2 below). The SCAR Program Management Office (PMO) requires modern Ground Entry Point (GEP) and Network Operations Center (NOC) capabilities to revitalize the United States Space Force's (USSF) Satellite Control system. The SCAR program is responsible for receiving requirements from end users and procuring solutions for fielding modernized antennas to augment the USSF Satellite Control Network (SCN) which comprises the legacy ground antenna architecture. To achieve this, the SCAR program acquisition consists of GEPs and NOC capabilities that can provide robust Telemetry, Tracking, and Commanding (TT&C) to support satellites across all orbital regimes.

SCAR PMO Specific Areas of Interest (AOI) and Problem Statements for this Solicitation Offerors may submit White Papers for any number of Areas of Interest (AOIs); however, each White Paper must address only a single AOI. Proposing to multiple AOIs requires separate submissions. Areas of Interest (AOIs) and their Problem Statements are outlined below.

AOI 01: Rapid Fielding of Government Owned and Contractor Operated Commercial TT&C Capabilities The SCAR PMO is seeking innovative prototype solutions for the rapid , delivery, testing, and operations that consists of GEPs with integration to a contractor furnished NOC system. Prototype solutions must deliver GEPs to Government custody and ownership at designated Government locations with one or more years of Original Equipment Manufacturer (OEM) Contractor Logistics Support (CLS) and operations support. Solutions must be scalable for potential follow-on production and provide a structured path to possible third-party CLS with a goal of transition to Government-run TT&C operations.

Key capabilities include:

· The engineering modification of existing GEP designs

· Fabrication and delivery of the hardware to a Government site

· On-site installation and integration and physical asset transfer to Government custody

· The execution of OEM-led CLS (encompassing preventative/corrective maintenance, supply chain/spares management, configuration control, documentation, and developmental engineering support during both the prototype and operational phases)

· Standardized data delivery interfaces (e.g., Radio Frequency (RF) over Internet Protocol or VMEbus International Trade Association-49 (VITA-49))

· Application Programming Interface (API)-driven tasking interoperable with the Government Antenna Broker, inclusive of contact scheduling and execution

· SCAR system anomaly resolution Solution must be at TRL 7, 8, or 9, offering a clear development-to-production pathway suitable for execution in accordance with section 3.3, and fully compliant with (or possessing a defined plan to meet) federal physical and cybersecurity requirements (e.g., Risk Management Framework [RMF] profiles) for deployment on Government property.

AOI 01 Problem Statement: Government-Owned & Contractor-Operated (GOCO) TT&C Capabilities Under the traditional acquisition model for TT&C capabilities, the Government struggles to rapidly procure and field antennas on Government sites due to bespoke technical solutions, Government-led maintenance, and limited funding. Furthermore, organic Government maintenance organizations lack sufficient personnel, expertise, and rapid engineering reach-back needed to maintain diverse and complex modern systems.

AOI 02: Exclusive Use Leased Commercial Antenna Capacity on Commercial Sites The SCAR PMO is seeking innovative prototype solutions for dedicated, long-term, exclusive Government leases of commercially owned, sited, maintained, and operated satellite TT&C systems.

Key capabilities include:

· Leasing of dedicated satellite TT&C systems (including apertures and NOC)

· Secure physical and logical hosting environments at established commercial ground sites

· Standardized data delivery interfaces (e.g., RF over IP or VITA-49)

· API-driven tasking interoperable with the Government Antenna Broker operations inclusive of contact scheduling and execution

· SCAR system anomaly resolution

· Contractor-managed site selection with Government input

· Contractor-provided hardware maintenance and facility sustainment Solution must be at TRL 7, 8, or 9, implement appropriate security controls to protect Government data streams and system capabilities within the multi-tenant environment, and be readily deployable to support rapid fielding initiatives in accordance with section 3.3. Solutions must demonstrate a robust engineering and production capability and a viable commercial leasing business model.

AOI 02 Problem Statement : Leased Commercial Antenna Capacity Securing dedicated tracking apertures to implement at sites required for robust global coverage often forces the Government to stand up dedicated ground stations with prohibitive schedule impacts and significant costs. This task limits the speed at which the SCAR network can scale geographically to support Government satellite TT&C needs, especially obtaining spectrum licensing in foreign territories.

AOI 03: Antenna as a Service (AaaS) The SCAR PMO is seeking innovative prototype solutions to provide a leased beam service that enables resilient, on-demand, guaranteed level of service for satellite TT&C capabilities. The service should utilize a fully commercial, multi-tenant ground station network that consists of a shared global pool of physical antenna assets. The service can serve multiple independent customers through secure, virtualized logical pathways. This will shift the Government from asset ownership to buying a dynamic, capability-as-a-service model.

Key capabilities include:

· Guaranteed level of service for leased beams for a specified geographic region

· Dynamic, automated scheduling across a globally distributed commercial network

· Logical data isolation techniques to ensure secure concurrent tenant operations on shared hardware

· Standardized data delivery interfaces (e.g., RF over IP or VITA-49)

· API-driven tasking interoperable with the Government Antenna Broker operations inclusive of contact scheduling and execution

· System anomaly resolution

· High-reliability uptime verified by Service Level Agreements (SLAs) Solutions must be a mature, commercial capability (TRL 8–9) operating on existing infrastructure, implement appropriate security controls to protect Government data streams and system capabilities within the multi-tenant environment, and be immediately fieldable in accordance with section 3.3. Solutions must demonstrate proven commercial operational history within a command-and-control model, established global network coverage, technical mechanisms used to prevent cross-tenant data leakage or scheduling conflicts, clear pricing schedules, and a concept for providing a guaranteed level of service (i.e., a fixed number of simultaneously available contacts in a specified region at specified performance).

AOI 03 Problem Statement: Antenna as a Service (AaaS) Space operations demand global, high-frequency satellite passes, yet owning and operating a globally distributed physical network is financially burdensome. Shifting to commercial "shared" networks alleviates the need to establish dozens of Government owned sites or dedicated leases. However, shared networks also introduce cyber risks that must be mitigated such as multi-tenant data leakage, scheduling conflicts, and software interoperability bottlenecks with the Government Antenna Broker.

DoD Technology Readiness Assessment Guidebook (February 2025) Hardware TRL Definitions (Table 1) Solutions for innovative commercial products and technologies proposed for the AOIs above must meet TRL levels 7-9 as defined in the tables below. If a system has been demonstrated to be TRL 7, 8, or 9, but requires a different subsystem or component to meet SCAR requirements, explain the TRL of the new subsystem or component and how it will be integrated into the system.

TRL
Definition
Description
Supporting Information
7
System prototype demonstration in an operational environment.
Prototype near or at planned operational system. Represents a major step up from TRL 6 by requiring demonstration of an actual system prototype in an operational environment (e.g., end-to-end satellite control demonstration).
Results from testing a prototype system in an operational environment.
8
Actual system completed and qualified through test and demonstration.
Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications.
Operational qualification testing results, developmental test & evaluation (DT&E) reports, and system specification compliance matrices.
9
Actual system proven through successful mission operations.
Actual application of the technology in its final form and under mission conditions, such as those encountered in operational tests and evaluation. Examples include using the system under operational mission conditions.
Operational test and evaluation (OT&E) reports, mission logs, sustainment records, and field operational data.

DoD Technology Readiness Assessment Guidebook (February 2025) Software TRL Definitions (Table 2)

TRL
Definition
Description
Supporting Information
7
System prototype demonstration in an operational, high-fidelity environment.
Level at which the program feasibility of a software technology is demonstrated. This level extends to operational environment prototype implementations, where critical technical risk functionality is available for demonstration and a test in which the software technology is well integrated with operational hardware/software systems. Critical technological properties, including cybersecurity, are measured against requirements in an operational environment.
Comparisons between tested environment and operational environment analytically understood. Analysis and test measurements quantifying contribution to system-wide requirements such as throughput, scalability, and reliability. Analysis of human-computer (user environment) began.
8
Actual system completed and mission qualified through test and demonstration in an operational environment.
Level at which a software technology is fully integrated with operational hardware and software systems. Software development documentation is complete. All functionality and cybersecurity measures tested in simulated and operational scenarios. Published documentation and product technology refresh build schedule. Software resource reserve measured and tracked. All severity 1 and severity 2 defects are resolved/confirmed, and a reasonably low level of severity 3 defects remain open.
The software based on the technology is fully integrated with operational hardware/software systems. All software documentation verified. Successful operational experience. Sustaining software engineering support in place. Actual system. Production configuration management reports. Defect resolution system and process is in place for deployed software to address defects discovered in production.
9
Actual system proven through successful mission-proven operational capabilities.
Level at which a software technology is readily repeatable and reusable.
Sustaining software engineering support is in place with steady-state maintenance. Statistical evidence of software reliability, security, and performance under continuous operational deployment. Defect resolution rates and production configuration logs.

NOBLE Framework, Topic Area, and Authority Used for This Solicitation The NOBLE MAA Framework This Two Phase Closed Commercial Solutions Opening (CSO) is a standalone solicitation issued under the overarching Nimble Options for Buying Layered Effects (NOBLE) Multiple Authority (MAA). The NOBLE MAA serves as the foundational, 5-year solicitation vehicle to rapidly acquire and Announcement integrate “layered effects” across the Missile Defense System (MDS). It is a joint, versatile vehicle allowing both the Missile Defense Agency (MDA) and other Department of War (DoW) components to rapidly pursue innovative solutions.

NOBLE MAA Topic Areas for This CSO This CSO seeks proposals that address the following overarching Topic Area excerpted directly from the NOBLE MAA.

Disruptive Technologies: The Missile Defense System shall incorporate mature, disruptive technologies to rapidly field advanced capabilities. This effort prioritizes innovations ready for immediate application or near-term transition, focusing on areas such as AI, directed energy, hypersonic defense, resilient networking, and cybersecurity. This could include novel concepts in the areas of satellite ground Telemetry, Tracking and Commanding (TT&C) capabilities, effectors, high-performance sensor algorithms, space-based tracking phenomenologies and discrimination, space-based off-board sensing concepts for weapons guidance and AI/machine learning (ML) for space/ground applications. These technologies shall enhance the defense system's effectiveness against rapidly evolving threats through enhanced situational awareness, rapid decision-making, and effective response options.

This could also include rapid demonstration and prototype development of disruptive technologies to accelerate the deployment and maintenance of a next-generation defense shield over the United States. This effort, encompassing new system-level capabilities, component concepts, upgrades to existing systems, and novel concepts of operation (CONOPS) across the entire kill chain, will focus on enhancing the Government’s ability to deter and defend against any foreign aerial attack, guaranteeing a secure second-strike capability.

CSO Statutory Authority and Follow-on Production Authority As authorized by the NOBLE MAA, this solicitation utilizes CSO procedures to acquire innovative commercial solutions. This CSO, conducted pursuant to 10 U.S.C. §3458 and DFARS 212.70-(Class Deviation 2026-O0028), serves as the competitive procedure for the initial prototype project selection. The Government intends to maximize the use of Prototype Other Transaction Agreements (OTAs) under 10 U.S.C. § 4022. In accordance with 10 U.S.C. § 4022(f), the Government reserves the right to award a non-competitive follow-on production contract or transaction to the participant(s) in the transaction following the successful completion of a prototype project competitively awarded under an OTA from this solicitation. The Government may award FAR-based firm-fixed price contracts as a result of this solicitation. All innovative commercial products and commercial services acquired under this CSO will be treated as commercial.

Under this Two Phase Closed Variant, the Government may award contracts resulting from proposals received under Phase 2 to acquire innovative products, technologies, or services based on a review of solutions by scientific, technological, or other subject matter expert peers within the SCAR program management office (PMO).

DoW Policy Alignment In accordance with the DoW Secretarial Memorandum dated November 7, 2025, this solicitation executes a “commercial-first” acquisition strategy, prioritizing non-traditional defense contractors and commercially derived innovations to bypass traditional bureaucratic barriers.

CSO Provisions and Additional Information Data Rights The Government intends to acquire only data rights necessary to satisfy agency needs. The specific data rights required will be dependent on the AOI to which Offerors propose solutions. The Offeror’s Library includes Use Cases that describe the anticipated operation of the SCAR system with external systems and actors. Use Cases supplement the SCAR TRD in defining functional requirements for the system. Offerors shall use the Use Cases when proposing data rights to the Government. For any resultant OTAs, the Government will negotiate tailored IP and data rights terms, maximizing the use of Specially Negotiated Licenses consistent commercial market practices. For any resultant FAR-based contracts, the Government will similarly seek to negotiate Specially Negotiated Licenses. However; if the parties cannot reach an agreement, the Government will apply R-DFARS 252.227-7989 and R-DFARS 252.227-7990 as the default positions.

Foreign Participation:

Foreign participation may be considered, but subject to export control restrictions (ITAR/EAR), national security considerations, and disclosure of any foreign ownership, control, or influence (FOCI). The research and test data produced under a resultant contract or agreement may contain information or technology whose export is restricted by the Export Control Act (22, U.S.C. § 2751, et seq.) Export Control Reform Act of 2018 (50 U.S.C. § 4801 et seq.) Request certification and registration from the Defense Logistics Agency (DLA) Joint Certification Program (JCP) Portal at https://www.dla.mil/logistics-operations/services/joint-certification-program/.

Non-Government Advisors In order to review submissions resultant from any phase, CUI PROPIN information may be given to Federally Funded Research and Development Centers (FFRDC), Systems Engineering and Technical Assistance (SETA), Systems Engineering and Integration (SE&I), and/or Advisory and Assistance Services (A&AS) contractors working for the Government. The Non-Government Advisors will have signed a non-disclosure agreement with the Government prior to reviewing submissions. By submission to any phase of this solicitation the offeror accedes to the terms of this provision. Any objection to non-Government advisors reviewing information submitted in response to this solicitation must be included in the Offeror submissions with the appropriate restrictive legends.

Organizational Conflicts of Interest All Offerors shall fill out the Organizational Conflict of Interest (OCI) Mitigation Plan Checklist provided in Section 8 and include a plan if applicable.

Non-Traditional Defense Contractor (NDC) Status For awards executed as OTAs under 10 U.S.C. § 4022, the project requires one of the following: (1) Significant participation by at least one NDC or nonprofit research institution; (2) All significant participants are small businesses or NDCs; or (3) The Offeror provides at least one-third of the total project cost from non-Federal funds. Offerors will be required to indicate their eligibility in their formal Proposal. (See 7.2.4.1 Responsibility) Government Furnished Property (GFP) Availability GFP is not anticipated to be made available under any resulting contract or agreement, but a determination regarding GFP will be made for each individual award.

For FAR-based awards: In accordance with RFO 45.201(b), the contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation, or rehabilitation costs.

For OTA awards: If GFP is ultimately authorized, the specific property list, maintenance responsibilities, and liability risk allocation will be custom negotiated and explicitly documented within the terms of the resulting agreement.

Definitions “Area of Interest” (AOI) means an announcement from this CSO which may result in the award of an OTA or FAR-based contract.

“Commercial Solutions Opening” (CSO) is method for employing the prototyping authority conducted pursuant to 10 U.S.C. §3458.

"Other Transaction for Prototype Projects” refers to the type of OTA that may be awarded as a result of this CSO and associated AOIs. This type of OTA is authorized conducted pursuant to 10 U.S.C. §4022 for prototype projects that are directly relevant to enhancing the mission effectiveness of personnel of the Department of Defense or improving platforms, systems, components, or materials proposed to be acquired or developed by the Department of Defense, or to improvement of platforms, systems, components, or materials in use by the armed forces.

“Prototype Project” can generally be described as a proof of concept, model, or process, including a business process, reverse engineering to address obsolescence, pilot or novel application of commercial technologies for defense purposes, agile development activity, creation, design, development, demonstration of technical or operational utility, or combinations of the foregoing. The quantity should generally be limited to that needed to prove technical or manufacturing feasibility or evaluate military utility.

“Nontraditional Defense Contractor” is defined in 10 U.S.C. § 3014 as an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to 41 U.S.C. § 1502 and the regulations implementing such section.

“Nonprofit Institution” means a nonprofit institution, as defined in 15 U.S.C. § 3703 as an organization owned and operated exclusively for scientific or educational purposes, no part of the net earnings of which inures to the benefit of any private shareholder or individual.

“Small Business” is defined under Section 3 of the Small Business Act (15 U.S.C. 632).

“Innovative” means any technology, process, or method, including research and development (R&D), that is new as of the date of the submission of a proposal, or any application that is new as of the date of the submission of a proposal of a technology, process or method, existing as of such date.

Evaluation and Selection Process General Information This section describes the Evaluation Process, Factors and Technical Ratings used for Phase 1 White Paper selection and Phase 2 proposal evaluation and award.

The Government will review each White Paper and ultimately select the Offeror(s) that have the greatest potential to meet the needs of the SCAR Program technology requirements based on the AOIs and their respective problem statements.

AOIs are written broadly to maximize latitude in creativity when approaching the SCAR PMO technical requirements and to allow for maximum participation from commercial vendors who may not be familiar with submitting proposals to Government solicitations.

Evaluation results for all criteria and factors will be fully supported by narrative findings. The summary for the Price factor will assess the reasonableness of the proposed prices. The Evaluation Team will adhere to the requirements, selection process, and criteria stated in the solicitation during evaluation of proposals.

Relative Importance for Evaluation Factors: Technical and Importance to the SCAR Program Requirements are equal primary evaluation factors. The Technical factor and Importance to the SCAR Program Requirements factor, when combined, are substantially more important than Funds Availability/Price.

Methods of Evaluation that may be used: scientific, technological, or other subject matter expert peers within the program management office (PMO).

Interchanges Interchanges with industry may occur during the evaluation and selection process. All such interchanges with industry will be documented in the contract file. Interchanges with industry may be through email, telephone, or face-to-face/virtual meetings. The Government Evaluation Team will adhere to controls to preserve the integrity of the selection process, as described herein.

Evaluation Process The Government will evaluate submissions in two phases. Phase 1 White Papers will be evaluated on the basis of the merit of the proposed concept in addressing the AOI identified, not against other White Papers submitted in response to the same AOI. All submissions will be evaluated; however, the Government reserves the right to limit the number of Offerors invited to submit a Phase 2 proposal. Progression from one phase to another, and ultimately to award, is at the sole discretion of the Government, subject to review and evaluation results and availability of funds. As such, an Offeror’s White Paper may be evaluated for merit but not invited to submit a Phase 2 proposal. The Government may invite one, some, all, or none of the Offerors to submit a proposal in response to an RFP/RPP.

With regards to Phase 2 proposals, Offerors will be notified that the Government may award all, part, or none of the proposals received. This allows the SCAR PMO the flexibility to specifically negotiate portions of the proposed effort or implement the most innovative aspects of proposals received.

Evaluation Factors Phase 1 –White Paper Evaluation Factors Phase 1 White Papers will be evaluated against the factors as defined below. These factors will be used to identify White Paper submissions that demonstrate sufficient interest and technical merit based on the AOIs and their Problem Statements to justify further consideration. The Government will then determine if Phase 2 Proposals will be requested.

Technical

· The White Paper proposes a solution that is technically feasible, can be executed, and is innovative.

· The White Paper includes a description of the effort that is aligned clearly with the selected AOI.

· The White paper describes the benefits of the proposed approach. The White Paper identifies and substantiates the Technology Readiness Level (TRL) of the proposed solution.

Importance to the SCAR Program Requirement

· The White Paper describes keys system performance specification metrics.

· The White Paper describes a manufacturing capacity and growth plan that clearly identifies the state of the solution, the integration strategy, and the solution approach aligned with the selected AOI.

Outcome Based on the evaluation, Offerors may be:

· Invited to submit a Phase 2 proposal;

· Notified that the White Paper submission is selectable and being held for a future invitation to submit a Phase 2 proposal; or

· Notified that the submission will not be pursued.

Phase 2 – Proposal Evaluation Factors Phase 2 Proposals will then be evaluated against the factors as defined below. These factors will be used to identify Proposal submissions that demonstrate sufficient technical merit based on the AOIs and their Problem Statements to justify an award.

Technical

· The proposed SOW meets the requirements of the SOO, TRD, and addresses the key capabilities identified in the AOI.

· The SOW demonstrates the ability to comply with applicable cybersecurity frameworks.

· The proposed architectural block diagram delivers the key capabilities of the selected AOI

· The proposal includes a realistic schedule that identifies dependencies and incorporates key program milestones identified in the SOO.

Importance to SCAR Program Requirements

· The proposed hardware and software deliverables described in the SOW contribute to mission need and alignment and meet the needs identified in the AOI description.

· The resources needed to execute the proposed solution are achievable and the proposed solution can integrate into existing mission operations with manageable risk while minimizing mission disruption.

· The data rights and IP proposed will satisfy the Government’s minimum data requirements and objectives of the selected AOI.

· The proposed support requirements from the Government are feasible and executable.

Statement of Work (SOW) – The SOW submission is not a separate Factor, but will be evaluated against both the Technical Factor and Importance to SCAR Program Requirements Factor Funds Availability/Price The proposal demonstrates a fair and reasonable price.

Outcome Based on the evaluation, the Government may:

· Select proposals for negotiation leading to award

· Fund all, some, part of, or none of the proposals Technical Ratings Phase 1 White Papers and Phase 2 Proposals will be evaluated against the Government’s factors for technical merit to determine whether a White Paper or Proposal is Recommended, Selectable or Not Selectable as defined below.

Recommended The White Paper or Proposal demonstrates exceptional technical merit, outstanding operational feasibility, or minimal integration risk to the SCAR program. The solution represents a highly mature, logical, or robust approach that fully addresses the AOI and problem statement without requiring significant technical maturation.

These White Paper submissions are recommended for immediate negotiation. These Proposal submissions are recommended for award if sufficient funding is available, and they are normally displaced only by other Recommended proposals.

Selectable The White Paper or Proposal demonstrates satisfactory to strong technical merit or represents a viable approach for addressing AOI and problem statement but requires minor system integration, adaptation, or additional technical maturation for the SCAR Program. It may exhibit minor capability gaps, require engineering-level integration, or demand modest Government-furnished support to achieve full operational capability.

These White Papers or Proposals represent a lower priority than those determined to be Recommended due to potential integration, feasibility, or maturation risks. To ensure a diversity of technical approaches, a Selectable White Paper or Proposal that introduces a highly innovative, disruptive, or unique methodology may be prioritized over a Recommended White Paper or Proposal that utilizes a more conventional, lower-risk approach. Selectable is acceptable if funding is available.

Not Selectable The White Paper or Proposal demonstrates inadequate technical merit, unviable operational feasibility, or unacceptable technical and security risks to the SCAR Program. The White Paper or Proposal fails to address AOI and problem statement, contains critical technical flaws, relies on unproven or highly speculative technologies, or lacks a realistic pathway to achieve system maturation.

These White Papers or Proposals do not represent a sound use of Government resources and will not be considered further.

Offeror Feedback For FAR-based contracts, the Government may provide debriefings in accordance with RFO 52.212-1(l). It will not include a comparison of submissions against a common PWS or SOW as the CSO provides no common PWS or SOW that interested parties must respond to and instead represents opportunity for submission of a variety of innovative commercial items, technologies, and/or services that represent meaningful submissions of diverse scope and price. For OTAs, the Government may provide summary feedback after each phase at the Government’s discretion consistent with OTA authority.

Phase 1 Submission The function of Phase 1 is to receive initial solutions for the respective Areas of Interest (AOIs). Each Offeror shall submit their White Paper submissions under the identified AOI.

White Paper Format The White Paper must be no longer than five pages, 8.5 x 11 inches with one-inch margins, single-spaced, with text in Times New Roman, and no smaller than 12-point font. White Papers must be submitted electronically as a Portable Document Format (PDF). Pages in excess of the page limitation will not be read or reviewed.

White Paper Content The White Paper should provide sufficient information on the technical solution being submitted to allow for review by a technical expert.

Cover Sheet The White Paper shall contain a cover sheet containing the following information. The cover sheet will not count against the page limitation.

· CSO number, AOI number, and AOI name

· Project Title

· Full company name and address

· CAGE code

· Unique Entity ID number

· Business Size Classification (large, small, or other)

· Offeror’s socioeconomic status

· Point of contact, name, title, phone number, and email address

· Current Facilities Clearance Level Technical Factor

· Provide a description of the proposed solution aligned to the selected AOI and explain how the proposed solution is innovative.

· Describe the original thinking, new application of existing technology, or novel concepts, approaches, methods or capabilities that differentiate the solution from other alternatives.

· Substantiate the TRL of the proposed solution. Identify required modifications to previously demonstrated, tested, or fielded systems. Complete the following TRL summary table mapping the proposed solution significant system/subsystem components to the Department of Defense (DoD) Technology Readiness Assessment Guidebook (February 2025) criteria included with the AOIs and Problem Statements.

System/Subsystem Component
Proposed TRL (7, 8, or 9)
Commercial/Operational Demonstration Evidence (e.g., Operating Hours, number of active ground stations, commercial client list, or historical to defense contracts)
Integration Plan (If integrating a new/modified component)

Importance to SCAR Program Requirements Factor

· Provide key system performance specification metrics.

· Describe your current manufacturing capacity and a growth plan showing how capacity could be scaled to provide 100 simultaneous contacts.

Foreign Ownership, Control, or Influence (FOCI) Disclose any FOCI. Do not include corporate or personnel qualifications, past experience or any supplemental information not requested.

Phase 2 Submission Phase 2 proposals will only be accepted from Offerors who, upon review of Phase 1 submission, have received a formal RFP/RPP to submit a full proposal.

Proposal Format Offerors shall submit a concise proposal structured around the following sections with page limitations defined in the table below, 8.5 x 11 inches with one-inch margins, single-spaced, with text in Times New Roman, and no smaller than 12-point font. Use of a 10-point font for tables and picture captions for exhibits is allowable. Graphical representations, block diagrams, and tables are highly encouraged over narrative text.

The Phase 2 Proposal submission shall conform to the following:

PHASE 2 PROPOSAL FORMAT
PAGE LIMITS
ELECTRONIC COPIES

TECHNICAL VOLUME

One (1)

Technical Factor Importance to the SCAR Program Factor 20 for both factors

Statement of Work (SOW)
No Limit

PRICE VOLUME

One (1)

Funds Availability/Price Factor
No Limit
Commercial Sales Data
No Limit
Price Substantiation for Catalog Items
No Limit
Price Substantiation for Non-Catalog Items
No Limit

ADMINISTRATIVE REQUIREMENTS VOLUME

Model OT Submission
Use Provided Model OT Template
Responsibility
No Limit
Small Business
No Limit
Organizational Conflict of Interest
Use Provided Checklist
Space Contractor Responsibility Watchlist (CRWL)
No Limit

Proposal Content The Proposal should provide sufficient information on the technical solution being submitted to allow for review by a technical expert Cover Sheet The following information shall be contained in a cover sheet submitted with the proposal. The cover sheet will not count against the page limitation.

· CSO number, AOI number, and AOI name

· Project Title

· Full company name and address

· CAGE code

· Unique Entity ID number

· Business Size Classification (large, small, or other) and NAICS

· Offeror’s socioeconomic status

· Point of contact, name, title, phone number, and email address

· Current Facility Clearance Level Technical Volume The following describes the technical submission requirements:

Technical Factor

· Provide an architectural block diagram with part numbers for the system that delivers the key capabilities of the selected AOI.

· Propose a one-page schedule in MS Excel, Power Point, or MS Project format illustrating the manufacturing, delivery, testing, integration, and operational phases of your prototype. The schedule should use the provided Integrated Master Plan (IMP) as a source of events and the expected durations for Government activities. to inform events and durations. Clearly identify the logical dependencies and major SCAR milestones (such as Ground Entry Point to Network Operations Center (GEP-NOC) integration, physical asset transition, security boundary testing, or Service Level Agreement (SLA) verification). All milestones must be defined in "Days after Award" (e.g., T+30, T+90). The final negotiated schedule will be incorporated into the resultant award.

Importance to the SCAR Program Requirements Factor

· Provide a simplified Risk and Mitigation Register using the format below to demonstrate low-risk integration and minimize mission disruption.

Identified Risk
Risk Level (L/M/H)
Proposed Proactive Mitigation Strategy
Impact to Existing Operations

· Declare data rights/Intellectual Property (IP) assertions position up front. Complete the table below for all software, hardware designs, and technical data deliverables. Ensure your proposed rights align with the Government's long-term operational goals to satisfy the Government’s minimum data requirements of the selected AOI.

Technical Data/Software Deliverable
Commercial or Proprietary?
Proposed License Rights (e.g., Limited, Government Purpose, SNL)
Alignment with SCAR Long-Term Goals (e.g., path to 3rd-party CLS or Gov operations)

· Itemize all requested Government Furnished Equipment (GFE), Government Furnished Information (GFI), physical facility access, or Government personnel support. If no Government support is required, the Offeror shall explicitly state: "No Government support, GFE, or GFI is required to execute this effort.”

Statement of Work and SOW Drafting Requirements The Offeror shall create a SOW using the SOO correlated to the identified AOI. The SOW will be evaluated against both the Technical Factor and Importance to SCAR Program Requirements Factor. The proposed SOW must meet the following instructions, formatting requirements, and stylistic guidelines:

1.1.1.1.1. Purpose and Applicability

The SOW must be a clear, severable document (provided as a separate MS Word file) outlining the exact tasks, deliverables, and technical objectives the Offeror will perform. Do not include pricing in the SOW.

The proposed SOW will serve as a contractually binding instrument upon award, therefore, it is critical that the SOW is drafted with the highest level of clarity, precision, and professional rigor, adhering strictly to the standards set forth in MIL-HDBK-245E (w/Change 2), Department of Defense Handbook: Preparation of Statement of Work (SOW).

To ensure technical compliancy, Offerors must align their SOW drafting with the principles of performance-based acquisition,…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .