F-16 Agnostic Rapid Weapons Integration
SBIR topic from AFWERX, solicitation 26.BZ. Open now. Closes 2026-09-23 (14 days left).
- Component (WERX)
- AFWERX
- Agency
- USAF
- Program / Phase
- SBIR
- Solicitation #
- 26.BZ
- Topic #
- DAF26BZ05-DV031
- Status
- Open
- Pre-release date
- 2026-08-05
- Open date
- 2026-08-26
- Close date
- 2026-09-23 · 14 days until close · Add to calendar · See all deadlines
- Set-aside
- —
- NAICS
- —
Topic brief
AFWERX / SpaceWERX-style open topics reward clear dual-use technology and a crisp problem framing. Treat DAF26BZ05-DV031 as a customer-problem essay tied to Air Force / Space Force mission pull — not a generic SBIR dump.
Who this is for
- Dual-use tech firms targeting Air Force or Space Force end users
- Teams that can show commercial traction or dual-use path
- Companies following the monthly DSIP / WERX open-topic cadence
Capture playbook
- Frame the warfighter / operator problem in one paragraph before tech
- Show dual-use or commercial path alongside defense application
- Check peer AFWERX open topics closing the same cycle
- Use the monthly open-topic digest to avoid missing the drop
- Run match + scorecard before allocating proposal bandwidth
pWin cues
- Specific end-user pain and measurable outcome
- Technology maturity appropriate to the phase
- Evidence of speed — AFWERX culture rewards execution
Watch-outs
- Generic dual-use claims without a named mission thread
- Missing the monthly cycle because you only checked SBIR.gov weekly
- Ignoring related open topics that dilute or concentrate competition
Peer open topics
Topic brief FAQ
Where are AFWERX open topics listed?
Live lists are on /afwerx-open-topics and the opportunities feed; monthly digests summarize the open cycle.
How does the monthly DSIP drop work?
DoD SBIR/STTR topics often release on a monthly cadence via DSIP. See the AFWERX DSIP guide on the blog.
Is open topic the same as a traditional SBIR topic?
Open topics are broader problem statements; traditional topics are often more narrowly specified. Read evaluation criteria carefully.
Readiness scorecard Capability match Monthly open-topic digest All topic briefs
Go / No-Go decision pack
One-click pack: competitive field, conversion signal, related awards, and (Pro) a full GO / MAYBE / NO-GO verdict against your capability.
Open scorecard Match my capability
Pro unlocks full Go/No-Go verdicts and named incumbents. Compare plans
Incumbent detector
No adjacent award history found for this topic yet. Use the decision pack and scorecard to build your own go/no-go case, and re-check after the next data refresh.
Description
This effort is focused on a rapid, modular, and scalable weapons integration architecture, developed on the Open Systems Enclave (OSE) system, that can deploy a broader range of munitions in months (vs years) in order to solve a critical interoperability constraint, enhance the relevance of legacy platform; and enable greater agility, lethality, and dominance. This topic primarily addresses the Air National Guard (ANG) & Air Force Reserve Command (AFRC) "Lethality" Modernization Imperative, specifically extending long-range kill chains to maintain offensive advantage. The long-term owner of this capability will be the F-16 program office with PEO Fighters .The Air National Guard (ANG) and Air Reserve Component (AFRC) must be able to integrate new weapons or weapons software updates without the need to code, test, and field entirely new aircraft OFPs requiring two to three years on average. Additionally, ANG and AFRC requires hardware solutions to allow a larger capacity of weapons to be carried to generate the maximum effects on each mission. Successful efforts will result in the development and integration of a hardware/software solution that will be demonstrated on the ANG F-16 aircraft in order to meet the urgent requirement for the integration of an Extended Range Attack Munition (ERAM).This effort will involve development and integration to deliver the architecture for a hardware/software solution that will be demonstrated on the Air National Guard (ANG) F-16 Block 30 aircraft. This effort will not involve the acquisition or integration of munitions, but is instead focused on the rapid integration of munitions and the development of an architecture that will facilitate that capability. This effort will enable the Air National Guard Air Force Reserve Component Test Center (AATC) to meet their urgent requirement for the integration of an Extended Range Attack Munition (ERAM) on the F-16 aircraft then the effort will then focus on additional weapons and aircraft.The long-term plan is to scale the solution to active-duty F-16 aircraft and other OSE platforms. Desired outcomes include the generation of evidence that the proposed solution can be potentially adopted by Active Duty F-16s and other Combat Air Forces (CAF) Open System Enclaves. This topic seeks to advance this technology from a current TRL of 6-7 to a target TRL of 8-9.
Score this topic against your capability statement
Loading teaming suggestions…
Post a teaming need for this topic. Team+ posts go live immediately; free/Pro posts are moderated.
Pro+: starter abstract / approach / work plan / risks — outline only, not a full proposal.
Pro+: paste solicitation text or upload PDF/DOCX to extract SHALL/must requirements.
Turn this topic into a compliance checklist, evaluation criteria, and win themes.