CSO Call - Group 3 Comms.docx

ASYMMETRIC WARFARE CSO CALL 001

FA8629-26-S-C001

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

Area of Interest: Unmanned Aircraft Systems

This announces Problem Statement Call 002 for Unmanned Aircraft Systems, issued under the Air Force Life Cycle Management Center (AFLCMC) Commercial Solutions Opening (CSO) FA8629-25-S-C001. This is a closed, multi-phase call through which the Government intends to award one or more fixed-price instruments, either as FAR based contract or Other Transactions (OT) for certain prototype projects pursuant to 10 U.S.C § 4022, as appropriate contracts.

This Call is seeking commercial or non-developmental baseline sUAS platforms that are already at a high level of technical readiness and have demonstrated successful flight events. The Government is not seeking and will not fund clean-sheet research and development for the sUAS platform under this announcement; proposals requiring development of a completely new base platform will not be considered.

However, the Government recognizes and intends to fund the necessary integration and developmental efforts required to adapt these mature systems for the required operational environment. Specifically, the Government will fund the integration of the communications relay payload and the developmental engineering required to make the system capable of being launched/dropped from a SOCOM PEO-FW air vehicle. To be considered for award, proposals must demonstrate that the baseline system is currently mature enough to meet the core flight requirements necessary to support these subsequent integration efforts.

The Government intends to execute this effort through a phased down-select process. Vendors selected to advance beyond Phase 2 will be issued distinct Requests for Proposals (RFPs) for integration and prototype development (Phases 3 and 4). These subsequent phases will not be pre-priced; vendors will submit new pricing in response to phase-specific RFPs.

Furthermore, in accordance with applicable prototyping authorities, the Government explicitly reserves the right to award a non-competitive follow-on production contract or transaction (Phase 5) to any vendors that successfully completes the prototype/integration phases. This follow-on production phase may encompass initial Low-Rate Initial Production (LRIP) for test/GFE assets, as well as full-scale production and fielding. The Government may issue a sole-source RFP for this follow-on production phase based on the successful demonstration of the capabilities outlined in this Call.

All proposals will be evaluated on their own technical merit, and the Government reserves the right to select all, some, or none for an award. Interested offerors are responsible for monitoring SAM.gov for all amendments and future announcements related to this call.

Problem Statement Recent conflicts have highlighted the asymmetric impact that small uncrewed aerial systems (sUAS) have on the modern battlefield. The Department of War (DoW) must be able to employ reliable, affordable, and adaptable sUAS platforms at scale in order to maximize operational flexibility for the Joint force.

Typically, Group 2 sUAS lack the payload space and power to enable the edge processing and communications necessary for maintaining a mesh network across a large swarm or for exfiltrating data from a contested environment. The Department of the Air Force (DAF) is seeking commercial or non-developmental baseline sUAS platforms for long-range, single-use, uncrewed air-launched autonomous vehicle carrying a payload that enables communications and data relay amongst a sUAS swarm in a contested area and exfiltrates data from a contested environment via BLOS. The vehicle will be air-launched from a Munitions Adapter Unit (MAU) adapter (Common Weapons Pylon (CWP) / Bomb Release Unit (BRU)) and will have a one-way range of 1000 Km (or endurance of 6 hours) at Max Gross Takeoff Weight.

Minimum UAS System Requirements

1) System Maturity and Phased Demonstration (Mature Technical Readiness Level (TRL) 6): The proposed platform must be a mature TRL 6 prototype with established flight heritage (including successful launch-to-flight transitions) in relevant field conditions outside of a laboratory. The stated entry TRL must reflect the current maturity of the submitted platform configuration and shall not be based on legacy, similar, or sister platforms.

2) Max Gross Weight: 330 lbs or less (with fuel and payload)

3) Range (one way) / Endurance (when launched at Max Gross Weight): 1000 Km or greater / 6 hr or longer

4) Loiter: minimum of 90 min with an objective of 180 min (after above range requirement is met)

5) Payload Capacity: minimum of 35 lbs with an objective of 50 lbs

6) Payload Power: 1000 Watts or more

7) Speed Parameters (at max gross wt, 2k ft MSL):

Loiter: 60 knots/hr or faster Cruise (average speed while achieving max range): 90 knots/hr or faster Dash: 120 knots/hr or faster

8) Delivery: Able to be quickly (within ~4 months of Phase 4 award) engineered for and ready to demonstrate air drop from a CWP / MAU

9) Operational Temps: Systems operable in environments -40° F to 140° F

10) Payload Command & Control: Status, Remote On/Off, Remote System Configuration, Compatible with Vigilant Spirit and Arbitrator

11) Aircraft & Payload Autonomy: Compatible with FANTOM (USG autonomy)

12) Aircraft & Payload, Beyond Line of Sight (BLOS): Proliferated Low Earth Orbit (PLEO) based BLOS

13) Aircraft & Payload, Line of Sight (LOS): Digital Data Link, Scalable Mesh Network, Mobile Ad Hoc Network, LPI/LPD anti-jamming resiliency

14) Third party SW/HW Compatibility: MOSA/OMS - ability to integrate USG provided/directed autonomy, payloads, comms, etc.; physical space layout and common interfaces that enable blue suit payload swap; Containerized critical flight control systems Submission Guidelines This call will be conducted in five phases. Submission instructions for this call supplement the general guidelines outlined in Section 3 of the parent CSO document. Where this document provides specific instructions for a phase, those instructions shall take precedence. The Government will not pay vendors for any submissions, pitches, or proposal preparation costs under this Call, including costs associated with preparing proposals for subsequent phases (phases 3, 4, and 5).

Funding is only authorized upon the official award of a contract or transaction resulting from a phase-specific RFP. The Government reserves the right to make multiple awards, a single award, or no award at all in any phase.

Phase 1 - Solution Briefs: The deadline for submitting Phase 1 Solution Briefs is September 30, 2026. Submissions received after this date may be considered late and may not be reviewed in accordance with (IAW) FAR 52.212-1(c). Interested vendors may submit clarifying questions after the call is posted. The Government will publish responses to submitted questions no later than 10 days prior to the Phase 1 submission deadline.

All materials, including questions and Solution Briefs, must be sent to the Asymmetric Warfare Org Box (Inbox: usafoffensivesmalluas@groups.af.mil).

The Government will not reimburse vendors for any costs associated with preparing or submitting a Solution Brief.

Solution Briefs may be submitted as a 10-page paper or 20-slide briefing, not including title page. Anything exceeding these lengths may not be considered at the discretion of the Government.

In addition to the general content requested in the parent CSO (Executive Summary, Company Viability, ROM Price), all Solution Briefs submitted in response to this Call must specifically provide the following details:

1. Substantiation of Requirement #1 - Technology Concept & Flight Heritage:

a. Provide verifiable evidence to support all claims of flight heritage. This must include, at a minimum:

i. A summary of total cumulative flight hours.

ii. A log detailing the date, duration, and outcome (e.g., successful transition to flight) of the five most recent consecutive launches.

iii. (Optional but encouraged) A brief summary of the test environment (e.g., location, weather) for these flights.

b. Airframe & Propulsion System: A technical description of the airframe, including materials, and the propulsion system (engine manufacturer, fuel/battery type, etc.).

2. Substantiation of Performance Requirements #3, 4, and 5. Provide data, analysis, or telemetry summaries from previous flights that substantiate the claimed Range/Endurance (Req #3), Payload Capacity (Req #4), and Payload Power (Req #5). If performance is based on modeling, identify the specific software used and the extent to which it has been validated against real-world flight data.

3. Substantiation of Requirement #13 - MOSA / Open Architecture Approach:

a. Describe the system’s adherence to Modular Open Systems Approach (MOSA) principles.

b. Interface Declaration: Explicitly declare whether all hardware and software interfaces for payloads and communications are open and non-proprietary. If any interfaces are proprietary, identify them and provide a rationale.

c. Software Containerization: Describe the maturity of the system's ability to run third-party software applications in a containerized environment (e.g., Docker) on the mission computer.

4. Substantiation of Requirement #7- Path to Air-Launch (Phase 4). Provide a notional concept and timeline for how the system would be engineered for air-launch from a CWP / MAU adapter, including any required structural modifications.

In addition to the criteria outlined in Section 3.2 of the parent CSO, Solutions Briefs will be evaluated on the following Call-specific criteria:

1. Credibility of Flight Heritage and System Maturity: The extent to which the vendor substantiates their stated TRL and flight history with verifiable data (e.g., flight logs, telemetry summaries). Solutions with a demonstrated history of successful, consecutive launch-to-flight transitions and significant cumulative flight hours will be rated more favorably.

2. Adherence to Modular Open Systems Approach (MOSA): The degree to which the proposed system demonstrates a commitment to open, non-proprietary hardware and software interfaces. Solutions that explicitly declare open interfaces and a mature approach to software containerization will be rated more favorably than those with proprietary or closed architectures.

3. Feasibility of the Air-Launch Concept: The technical soundness and programmatic realism of the vendor's notional concept for meeting the Phase 4 air-launch requirement. The evaluation will consider whether the proposed engineering path is logical, achievable within the notional timeline, and appropriately addresses key structural and aerodynamic risks.

Note: Vendors may submit multiple solution briefs.

Vendors are responsible for all costs associated with preparing for and submitting a Solution Brief. After the Phase 1 evaluations, vendors will be notified of the outcome. Vendors may be informed of one of the following:

(1) Not Selected: The proposed solution is not of current interest to the Government or does not meet the necessary technical maturity and performance thresholds to proceed.

(2) Selected but Deferred (Capacity Constrained): The proposed solution is of interest and demonstrates technical merit, but the vendor is not currently invited to participate in a Phase 2 Pitch Session due to limited Government evaluation capacity, scheduling constraints, or immediate program priorities. The Government reserves the right to invite the vendor to participate in a Phase 2 Pitch Session at a later date (within 180 days of submission) should scheduling slots become available or program requirements adjust.

(3) Invited to Phase 2 (Pitch Sessions): The vendor's solution is highly meritorious, and the vendor is formally invited to participate in a Phase 2 Pitch Session. The Government will provide supplemental guidance detailing the pitch format, scheduling, and specific evaluation criteria in the formal invitation. Successful execution of the Phase 2 Pitch Session is the required gate to receive an invitation to submit a comprehensive Phase 3 proposal.

Phase 2 - Pitch Sessions (Virtual or In-person): Phase 2 Pitch Sessions are expected to occur between October 19 and October 23, 2026. Following the Phase 2 evaluation, the Government may invite a select number of vendors whose Solution Briefs are deemed meritorious to present their proposed solution. Invitations to participate in Phase 3 are made at the Government's discretion and may be limited. Therefore, a solution may be technically meritorious but not selected for a pitch session.

Vendors are responsible for all costs associated with preparing for and participating in the pitch session. After the Phase 2 evaluations, vendors will be notified of the outcome. Vendors may be informed of one of the following:

(1) Not Selected: The proposed solution is not of current interest to the Government or does not meet the necessary technical maturity and performance thresholds to proceed.

(2) Selected but Deferred (Resource Constrained): The proposed solution is of interest and demonstrates merit, but the vendor is not currently invited to submit a Phase 3 proposal due to limited Government funding or immediate operational priorities. The Government reserves the right to invite the vendor to submit a Phase 3 proposal at a later date if funding becomes available.

(3) Invited to Phase 3 (Request for Prototype Proposal): The vendor’s solution is highly meritorious, and the vendor is formally invited to submit a comprehensive proposal for Phase 3 (Prototype I: Payload Integration & Flight Demonstration). This proposal may result in the award of a FAR-based contract, an Other Transaction Agreement (OTA) for Prototyping under 10 U.S.C. § 4022, or another appropriate acquisition instrument.

Supplemental guidance, in addition to section 3.3 of the parent CSO, for Phase 2 content and evaluation criteria will be provided to vendors chosen to participate in Phase 3. Pitch submissions will be valid for 180 calendar days after the pitch date.

Phase 3 - Prototype I Payload Integration & Flight Demonstration: The vendors that successfully complete both Phase 1 and Phase 2 may be invited to submit a comprehensive Phase 3 proposal. The Phase 3 proposal will include both pricing and a technical proposal sufficient to demonstrate the proposed solution and the vendor’s ability to manufacture the platform at desired quantities (specified in supplemental guidance).

The Government will utilize the Phase 3 period of performance to validate baseline system performance. As a strict performance gate, the platform must successfully demonstrate compliance with UAS Systems Requirements 2 through 6, 11, 12, and 13 at the Phase 3 flight demonstration. Additionally, by the end of Phase 3, the vendor must provide lab-based analysis or environmental testing data to verify the platform is compliant with Requirement #8.

Supplemental guidance for Phase 3 proposal content and evaluation criteria will be provided to the invited vendors.

Evaluation of Phase 3 Proposals and Award:

Based on the evaluation of submitted Phase 3 proposals, the Government will select the most meritorious proposal(s) for a contract award. The Government reserves the right to award Phase 3 contracts to one, some, none, or all eligible vendors. Unsuccessful offerors will be notified that they have not been selected for a Phase 3 award.

Evaluation of Phase 3 Performance:

Upon conclusion of the Phase 3 period of performance, the vendors that received an award and executed the demonstration will be evaluated on their performance and informed of one of the following outcomes:

(1) Not Selected to Advance: The vendor did not successfully meet the technical milestones or performance criteria of the Phase 3 prototype effort and will not advance further in the down-select process.

(2) Successful but Deferred: The vendor successfully met the Phase 3 prototype criteria but is not currently invited to submit a Phase 4 proposal due to limited Government funding or shifting operational priorities. The Government reserves the right to invite the vendor to Phase 4 at a later date.

(3) Invited to Phase 4 (Request for Prototype Proposal): The vendor successfully demonstrated the required Phase 3 capabilities and is formally invited to submit a proposal for Phase 4 (Prototype II: Air-Launch Demonstration).

Phase 4 - Prototype II Air Launch/Drop Demonstration: The vendors that successfully complete Phase 3 may be invited to submit a Phase 4 proposal. The Phase 4 proposal will include both pricing and a technical proposal sufficient to demonstrate the proposed solution and the vendors’ ability to manufacture the platform at desired quantities (to be specified in supplemental guidance).

The Government will utilize the Phase 4 period of performance to validate the system's air-launch capabilities. As a strict performance gate, the platform must successfully demonstrate a clean air-launch-to-flight transition, continued compliance with UAS Systems Requirements 2 through 6 and 11, and successful demonstration of Requirements 12 and 13. Further information regarding the demonstration and evaluation of UAS Systems Requirements 9 and 10 will be provided in supplemental guidance, contingent upon the availability of Government Furnished Equipment (GFE).

Evaluation of Phase 4 Proposals and Award:

Based on the evaluation of submitted Phase 4 proposals, the Government will select the most meritorious proposal(s) for a contract award. The Government reserves the right to award Phase 4 contracts to one, some, none, or all eligible vendors. Unsuccessful offerors will be notified that they have not been selected for a Phase 4 award.

Evaluation of Phase 4 Performance (Air-Launch Demonstration):

Upon conclusion of the Phase 4 performance period, the vendors will be informed of one of the following outcomes:

(1) Not Selected to Advance: The vendor did not successfully meet the technical milestones or performance criteria of the Phase 4 prototype effort and will not advance to the production phase.

(2) Successful but Deferred: The vendor successfully met the Phase 4 prototype criteria but is not currently invited to a Phase 5 production award due to limited Government funding or shifting operational priorities. The Government reserves the right to award a follow-on production contract at a later date.

(3) Selected for Phase 5 (Follow-on Production): The vendor successfully demonstrated all required Phase 4 capabilities. In accordance with 10 U.S.C. § 4022(f), the Government reserves the right, but is under no obligation, to award a non-competitive follow-on production contract or transaction for activities including formal host-platform(s) integration support, production of integration and/or test assets, Low-Rate Initial Production (LRIP), and/or Full-Rate Production/Fielding. Any future Phase 5 award is strictly subject to the successful completion of Phase 4, the availability of Government funding, and continued Government need. The specific quantities and scope of Phase 5 will be defined in the resulting production award.

Phase 5 - Follow-on Production: Test and Operational Assets: The vendors that successfully complete Phase 4 may be invited to submit a Phase 5 proposal. The Phase 5 proposal will include both pricing and a technical proposal for activities including formal host-platform(s) integration support, production of integration and/or test assets, Low-Rate Initial Production (LRIP), and/or Full-Rate Production/Fielding. Additional requirements beyond those listed in this Call will be provided via supplemental guidance to the vendors selected to participate in Phase 5.

The Government will provide the date and time for Phase 5 submissions in the invitation to submit a proposal. Detailed proposal preparation and submission instructions are provided in Section 3.4 of the parent CSO, and additional, phase-specific proposal instructions will be provided in the supplemental guidance.

The vendors that submit an acceptable Phase 5 proposal will be eligible for award consideration. However, the Government reserves the right, but is under no obligation, to award one or more non-competitive follow-on production contracts or transactions—in accordance with 10 U.S.C. § 4022(f) or other applicable authorities—for the activities outlined above. Any future Phase 5 award is strictly subject to the availability of Government funding and continued operational need. The specific quantities, terms, and scope of Phase 5 will be defined in the resulting production award(s).

Eligibility This call under CSO FA8629-25-S-C001 is open to both U.S. and international vendors. Any company selected for an award that does not possess a Commercial and Government Entity (CAGE) code or Dunn and Bradstreet (DUNS) number will be required by the Department of Defense (DoD) to register in the System for Award Management (SAM.gov). Prospective companies are strongly encouraged to initiate the SAM registration process as early as possible to avoid potential delays.

Contact Any questions regarding this Area of Interest or Problem Statement Call may be directed to the following POCs:

· Org Box: usafoffensivesmalluas@groups.af.mil

· Attn/Cc: Mr. Jesse Cooley, Contracting Officer, jesse.cooley.1@us.af.mil Captain Veronica Hindelang, Contract Specialist, veronica.hindelang.1@us.af.mil Mr. Aaron Snyder, Program Manager, aaron.snyder.4@us.af.mil

Additional Considerations We strongly recommend all Phase 1 proposals be formatted as presentations, no more than 20 slides in length. Solution Briefings should provide, at a minimum, the specific substantiating data requested in the "Phase 1 - Solution Briefs" section above.

In addition to those requirements, briefings should use this section to detail the following:

· Air-Launch Employment Concept: Describe the concept of operations for the air-launch of this system. Address how the system will safely separate from a CWP / MAU adapter, start its engine, and autonomously navigate to its initial loiter point.

· Communications Payload Integration: While the Government will fund payload integration in Phase 3, describe the system's payload bay architecture. Detail the available volume, mounting provisions, and power/data interfaces that make it suitable for a 35 lb communications relay payload.

· GFE Software Compatibility (Reqs #9 & #10): Describe the system's software architecture and the pathway to integration with the specified Government C2 and autonomy frameworks (Vigilant Spirit, Arbitrator, FANTOM).

· Production Scalability: Describe the plan for production scalability to meet potential Low-Rate and Full-Rate Production quantities. Address reliance on specialized tooling, supply chain for critical components, and potential manufacturing locations.

DDIL Operations: We expect solutions to operate in Denied, Degraded, Intermittent, and Limited (DDIL) environments. The UAS must be able to execute its primary loiter and waypoint navigation mission without continuous communication from an operator. Given its role as a communications relay for a sUAS swarm, solutions that provide multiple resilient pathways for two-way communications are desired. Solution Briefings shall describe the platform's ability to maintain autonomous flight, hold station, and execute pre-planned recovery/termination protocols in GPS- and communications-denied environments.

Mission Planning Software: Solution Briefings must discuss the mission planning software that will be utilized with the submitted platform. Mission planning software should be intuitive and capable of generating flight plans compatible with the air-launch drop profile. Vendors should highlight any current or planned integration with the USG-provided C2 systems referenced in Requirement #9 (e.g., Vigilant Spirit, Arbitrator).

Hardware/Software Integration: In alignment with UAS Requirement #13, the solution will be assessed for its adherence to a Modular Open Systems Approach (MOSA). Solutions must utilize open hardware and software interfaces that allow for the seamless integration of USG-provided or directed autonomy (e.g., FANTOM), communications, and third-party payloads. The platform's physical space layout and common interfaces should enable "blue suit" payload swaps on the flight line. Furthermore, critical flight control software systems should be containerized to isolate them from mission payload software. Proprietary data bus interfaces, closed message formatting, or hardware that require restrictive vendor-specific licensing are highly discouraged and must be explicitly identified in the Solution Brief.

Data Rights Assertions: The Solution Brief will identify any Intellectual Property (IP) involved in the effort and the associated restrictions on the Government’s use of that IP. The Government strongly prefers Government Purpose Rights (GPR) for interfaces necessary for payload integration.

Security Requirements: The base effort (Phases 1 and 2) for this call is unclassified. However, Phase 3 awards, subsequent air-launch demonstrations (Phase 4), and production efforts (Phase 5) may require access to classified information up to the SECRET level. Should classified access be required, a DD Form 254, Contract Security Classification Specification, will be issued, and the successful offeror must possess a valid Facility Clearance (FCL) and have personnel with appropriate Personnel Clearances (PCL) at the time of award. Offerors who do not currently meet these requirements may still submit a Solution Brief but must be eligible to obtain the necessary clearances prior to Phase 3 award.

Affordability & Target Pricing: Given the single-use, attritable nature of this mission profile, unit cost is a critical evaluation factor. Vendors can be expected to discuss trade space, component selection, and design choices through the lens of affordability, with the explicit aim of minimizing future production bottlenecks and driving down unit costs at scale.

The Government's target Average Procurement Unit Cost (APUC) for the baseline platform (excluding payload costs) at mature production quantities is $250,000 per unit. Solutions that provide a credible manufacturing pathway to achieve or under-run this target cost while meeting the core performance requirements will be viewed highly favorably.

Regulatory Requirements and Teaming Considerations All proposed solutions must comply with the most current U.S. laws and Department of Defense (DoD) policies regarding the procurement and operation of Unmanned Aircraft Systems (UAS). Offerors are responsible for ensuring their entire supply chain, including all critical components, is compliant. Key governing authorities include, but are not limited to:

National Defense Authorization Act (NDAA) Prohibitions on Certain UAS: All solutions must comply with the prohibitions on the procurement and use of certain foreign-made UAS and their critical components, as specified in Section 805 of the FY2024 NDAA and all related preceding and subsequent legislation. Solutions on the Defense Innovation Unit (DIU) "Blue UAS" Cleared List are preferred, though not required. Vendors must be prepared to provide a full bill of materials and certify supply chain compliance upon request.

Cybersecurity Risk Management Framework (RMF): The proposed system, including the air vehicle and ground control station, must be capable of meeting a cybersecurity evaluation in accordance with DoD Instruction 8510.01, DoDI 8500.01, and other relevant directives. The successful offeror will be required to achieve and maintain an Authority to Operate (ATO) on DoD networks prior to operational fielding.