Low SWaP-C Tactical Awareness Payload for Proliferated, Agile Satellites (TAPPAS) for Space Domain Awareness

SBIR topic from AFWERX, solicitation 26.BX. Closes 2026-10-21 (42 days left).

Component (WERX)
AFWERX
Agency
USAF
Program / Phase
SBIR
Solicitation #
26.BX
Topic #
DAF26BX06-DV511
Status
Pre-release
TPOC Q&A window
Open until 2026-09-23 — sponsors accept direct questions during pre-release.
Pre-release date
2026-09-02
Open date
2026-09-23
Close date
2026-10-21 · 42 days until close · Add to calendar · See all deadlines
Set-aside
NAICS
Pre-release topic brief

Topic brief

This SBIR topic is in pre-release. Use the TPOC Q&A window before proposals open — that is the highest-value intelligence window on DAF26BX06-DV511.

Pre-release focus: Prioritize TPOC Q&A before the open date. Proposals open 2026-09-23.

Who this is for

  • Firms that already have a draft capability narrative ready to adapt
  • Teams that can ask sharp technical questions without revealing proprietary IP
  • Companies tracking a monthly DSIP / WERX release cadence

Capture playbook

  1. Read the full topic text and note must-have vs nice-to-have requirements
  2. Submit clarifying questions to the topic author / TPOC before Q&A closes
  3. Map prior winners in the same component and tech domain (see related awards)
  4. Run a free readiness scorecard and decide go / no-go before open day
  5. Set a deadline alert for 2026-10-21 so you do not miss close

pWin cues

  • Clear alignment between past performance and stated technical objectives
  • Ability to field a prototype on the implied timeline
  • No hard requirement you cannot evidence (facility, clearance, TRL)

Watch-outs

  • Q&A ends when the topic opens — late questions often go unanswered
  • Incumbents from prior topic families may already be drafting
  • Pre-release text can still change; re-read on open day

Peer open topics

Topic brief FAQ

What is pre-release on SBIR/STTR topics?

Pre-release is the window after a topic is announced but before proposals open, when you may contact the topic author/TPOC with questions.

Should I start writing before the topic opens?

Outline and evidence mapping yes; final page-limited drafts wait until the official open text freezes requirements.

How do I track this deadline?

Save the topic on SBIR Signal and set a deadline alert, or use the deadline calendar export.

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

The objective of this Direct to Phase II (D2P2) effort is to provide a production representative article of flight qualifiable hardware to be flown in the GEO space environment. The modern space domain requires a layered sensing architecture to ensure resilience. This D2P2 effort is focused on a critical element of that architecture: a compact, efficient payload that provides persistent, 4 pi steradian awareness of the local space environment for its host vehicle. Occlusion zones are probable and should be minimized based on the satellite design and sensor placement. Multiple phenomenologies are of interest, to include but not limited to, electro-optical, infrared, and radio frequency. To be suitable for integration across a wide range of buses, solutions must be aggressively optimized for low Size, Weight, and Power with affordability in mind. While any available tested technology will be considered, the ideal payload would not exceed 50W of power consumption and 15 Kg of mass. These characteristics are critical for enabling integration onto platforms with stringent resource limitations. The desired capability must establish a "self-awareness bubble" with a range of 200 km (threshold) to 500 km (objective) radius, with the ability to detect a 0.5 (threshold) to 0.2 (objective) meter object with a probability of detection of 0.8 and probability of false alarm of 0.01. The sensor data must feed into advanced on-board analytics to autonomously track nearby objects, to support assessment of intent, distinguishing between debris, unanticipated neutral or friendly objects, and potential threats to enable both autonomous tactical response and intuitive operator visualization. The government’s primary focus is on the speed of delivery for proven technology now. Key challenges to be addressed include: - Autonomous Threat Detection in a Low SWaP-C Package: proactively gathering, processing, and analyzing data to characterize threats using a highly efficient, lightweight payload. - Scalable, Mature, and Manufacturable Solutions: solutions must emphasize high Technology Readiness Level (TRL), Manufacturing Readiness Level (MRL), and scalability for hardware and software. - Efficient Hardware Integration: use common interfaces for power, data, and thermal to ease integration onto platforms. Minimize footprint and be flexible with mounting options. - Efficient Data Integration: Optimizing the payload to provide decision-quality information efficiently, with an architecture that allows for integration with enterprise data systems.

View / apply on DoD DSIP ↗

Score this topic against your capability statement

Loading teaming suggestions…