Semantically-Aware ISR
Overview
What you need to judge this in 30 seconds
SBIR · Phase: BOTH · Topic DPA26BZ05-DV019 · Solicitation 26.BZ
Effective Intelligence, Surveillance, and Reconnaissance (ISR) in contested theaters depends on the ability to extract and transmit decision-relevant information from sensors under severely constrained communications. Modern multimodal sensor payloads, including electro-optical (EO), infrared (IR), event-camera, low-light, and platform-telemetry streams, produce data volumes orders of magnitude beyond what tactical communications links can carry, particularly when those links are degraded, intermittent, jammed, emission-constrained, or forced to single-digit kilobits per second by electronic warfare. The operational consequence is binary: an ISR platform either delivers mission-relevant evidence to the operator under these conditions, or it provides limited operational value. Small unmanned aircraft systems (sUAS) embody this challenge in its most acute form. Representative Group 1 platforms such as RQ-11B Raven and RQ-20 Puma-class systems carry EO and IR video for dismounted operators with single-digit-watt payload compute budgets. Representative Group 2 platforms such as ScanEagle-class systems provide broader reconnaissance with greater range, endurance, and modular sensors, but remain size, weight, and power (SWaP) constrained. Across both classes, full-motion EO and IR video routinely exceeds available tactical link capacity, particularly when multiple unmanned systems operate simultaneously. Three concurrent technical failure modes define this problem space and rule out incremental approaches: • Mission intent is vague and operator-defined. Operators do not request a single class label. They request answers to compositional, context-dependent tasks such as identifying indicators of hostile staging along a ridgeline, judging whether a gathering is consistent with prior pattern-of-life, or noticing whether access patterns to a structure have changed in the last twenty minutes. There is no fixed object dictionary, and what is mission-relevant in one engagement is clutter in the next. • Regions of interest are not necessarily objects. Mission-relevant regions are frequently not detectable as discrete objects in any single frame. Relevant evidence may be a vehicle stopped where vehicles do not normally stop, a crowd dispersing unusually fast, a heat signature appearing at an unusual time, a person loitering near an asset, or a pattern of vegetation disturbance accumulated over many frames. Object detectors and large vision-language models are weak in this regime because the evidence is distributed across space and time rather than localized in a single frame. • The platform cannot host heavy artificial intelligence. Group 1 payload compute is typically constrained to single-digit watts; Group 2 platforms allow modest growth but remain size, weight, and power constrained. Large vision-language models and conventional deep-learning trackers are not deployable at this power envelope and are additionally fragile under domain shift, adversarial obscuration, and data-poor conditions characteristic of low-density and low-prior threats. This topic seeks a new class of mission-aware semantic communication systems that can approach two orders of magnitude data reduction in mission-suitable ISR scenarios while preserving mission-relevant context and semantic content. The required capability is not video compression, object detection, or target tracking; it is an onboard, real-time, low-power information-processing layer that understands operator intent, reasons over spatial and temporal context, captures behavioral evidence distributed across frames, and emits only the compact semantic packets needed for receiver-side reconstruction. Semantic packets shall combine high-fidelity regions of interest, tracklets, scene-change descriptors, temporal evidence, low-rate background context, confidence, uncertainty, and traceable explanations sufficient for the operator to act on the evidence at substantially lower bandwidth. Phase II prototype…
- Category
- R&D
- Industry
- Needs verification
- Technology
- Needs verification
- Target stage
- Needs verification
- Project duration
- Needs verification
- Estimated preparation
- Needs verification
Funding
Award size and how it is paid
- Award range
- Needs verification
- Currency
- USD
- Total programme budget
- Needs verification
- Support type
- Needs verification
- Co-funding
- Needs verification
- Matching fund
- Needs verification
- Disbursement
- Needs verification
- Note
- -
Eligibility
Can we actually apply?
SBIR/STTR 은 미국 중소기업만 지원할 수 있습니다(Small Business Act 법정 요건). • 계열사를 포함해 상시 종업원 500명 이하 • 미국 시민 또는 영주권자 1인 이상이 50%를 초과해 직접 소유·지배 • 미국 내 사업장을 두고 주로 미국 내에서 사업을 영위할 것 • 수행책임자(PI)의 주된 근무처가 신청 기업일 것 출처: https://www.sbir.gov/faq/eligibility-requirements
- Company age
- Needs verification
- Employees
- 0명 ~ 500명
- Revenue limits
- Needs verification
- Consortium
- Needs verification
Location Requirements
Geography and legal-entity conditions
- Primary country
- 🇺🇸 United States
- Also eligible
- None
- Foreign companies
- No
- Local entity
- Required
- Location condition
- 미국 내 사업장을 두고 미국 시민·영주권자가 50%를 초과해 소유한 중소기업만 신청할 수 있습니다(법정 요건).
Required Documents
Required/optional · issuer · difficulty · validity · cautions
Document requirements were not captured (needs verification). Check the official announcement.
Application Process
How you apply
Application process not captured.
Evaluation
Review process and criteria
Evaluation process not captured.
Timeline
Announcement → intake → review → agreement → execution
Process steps were not captured.
Equity & Financial Terms
Equity, loans and contract conditions
- Equity required
- Needs verification
- Loan
- Non-dilutive grant
- Duplicate funding
- Needs verification
- IP ownership
- Needs verification
- Deliverable ownership
- Needs verification
- Exclusivity
- Needs verification
- Right of first refusal
- Needs verification
- Audit & settlement
- Needs verification
Risk Intelligence
Should we apply at all? — five dimensions plus an overall score (lower is safer)
Chance of failing eligibility, location or legal-entity rules
Co-funding, matching funds, reimbursement and loan exposure
Paperwork load, timeline pressure, reporting and audit duties
Exclusivity, right of first refusal, duplicate-funding limits
How much technical detail you must hand over, and who owns it
- 18Local entity required
You cannot apply without an entity registered in that country.
- 16Overseas applicants not eligible
Only domestically registered companies may apply.
- 10Own contribution not stated· evidence needs verification
R&D and pilot programmes commonly require one. Confirm the ratio.
- 10Required documents not collected· evidence needs verification
The list of required documents was not collected.
- 8Payment timing not stated· evidence needs verification
Advance versus reimbursement makes a large difference to cash flow.
- 7Exclusivity not stated· evidence needs verification
Any exclusivity clause has to be checked.
- 6Award size not stated· evidence needs verification
The announcement does not state how much is available.
- 6Right of first refusal not stated· evidence needs verification
Any right-of-first-refusal clause has to be checked.
- · The list of required documents was not collected — check the announcement for what technical material must be submitted.
- · Whether an NDA can be signed is not stated (needs verification).
- · IP ownership terms are not stated (needs verification).
- · Ownership of the deliverables is not stated (needs verification).
- · Data-rights terms are not stated (needs verification).
- · How submitted material may be reused is not stated (needs verification).
- · Whether an exclusivity clause applies is not stated (needs verification).
- · Whether a right of first refusal applies is not stated (needs verification).
- · The required own-contribution ratio is not stated (needs verification).
- · Whether a matching fund is required is not stated (needs verification).
- · Whether payment is in advance or in arrears is not stated (needs verification).
- · The level of settlement and audit obligation is not stated (needs verification).
- · The award size is not stated (needs verification).
- · The duplicate-support rule is not stated (needs verification).
Generated by local:rules-v1 · 3h ago
IP / Idea Protection
How much of your technology and idea you must disclose
The announcement does not say what has to be submitted, so the disclosure exposure cannot be judged. the scope of the material requested is not stated. The awarding body is U.S. Department of War — DARPA. 8 fields could not be read and must be checked in the announcement and the grant agreement.
- NDA
- Needs verification
- IP ownership
- Needs verification
- Deliverable ownership
- Needs verification
- Data rights
- Needs verification
- Disclosure depth
- Needs verification
- File patent first?
- Not applicable
- Reuse of submissions
- Needs verification
- Publicity obligation
- Needs verification
- Exposure score
- Needs verification
- · The problem your product solves, and the market definition
- · Your value proposition and quantified results (improvement rates, throughput)
- · Anything already public: granted patents, papers, press coverage
- · Team composition, capabilities and a summary of past delivery
- · Architecture-level diagrams at module granularity, without internal implementation
- · Core algorithms: formulae, hyper-parameters and pre-processing rules
- · Raw training data and the details of your collection pipeline
- · Full source code and build or deployment scripts
- · Cost structure and unit-price formulae
- · Named customers, contract terms and pricing
- · How an unfiled invention is actually implemented
- HIGHPoC/공동개발 IP 귀속 조항 확인
공동개발 산출물의 지분·개선발명(improvement) 귀속·배경지식(background IP) 분리 조항을 협약서에서 확인하십시오.
- MEDIUMRequest an NDA
Ask in writing for a mutual NDA before submitting detailed technical material; if it is refused, keep what you submit at summary level.
4 evidence item(s) from the source
- UNKNOWN
No document list was collected, so the exposure of technical material cannot be judged.
Source link - UNKNOWN
No NDA clause could be found.
Source link - UNKNOWN
IP ownership terms could not be found.
Source link - UNKNOWN
Ownership of the deliverables terms could not be found.
Source link
- · The list of required documents was not collected — check the announcement for what technical material must be submitted.
- · Whether an NDA can be signed is not stated (needs verification).
- · IP ownership terms are not stated (needs verification).
- · Ownership of the deliverables is not stated (needs verification).
- · Data-rights terms are not stated (needs verification).
- · How submitted material may be reused is not stated (needs verification).
- · Whether an exclusivity clause applies is not stated (needs verification).
- · Whether a right of first refusal applies is not stated (needs verification).
This assessment is derived from the stored announcement, document and contract fields. Anything the source does not state is marked "needs verification" — it never asserts that your idea will be taken. Generated by local:rules-v1 · 3h ago
AI Analysis
Pros · cons · difficulty · competition · attractiveness
From paperwork and review stages
Heuristic from award size and type
Amount, terms and IP combined
Weighted average of five dimensions
- Needs verification
- − 현지 법인 설립이 필요합니다.
- − 해외 기업은 지원할 수 없습니다.
- ! IP 귀속 조항이 확인되지 않았습니다 (확인 필요).
- ! 중복 수혜 제한 규정을 사전에 확인하십시오.
Similar Programs
Comparable by type, country and technology
- Universal Cell Culture Platform for Rapid Establishment of Species-Agnostic Cell Lines and Autonomous Culture Operations
🇺🇸 United States · R&D program · U.S. Department of War — DARPA
Needs verificationD-34 - Open Architecture Platform for Underwater Vehicles for Rapid Adaptation, Collaborative Sensing, Navigation, and Autonomy
🇺🇸 United States · R&D program · U.S. Department of War — DARPA
Needs verificationD-34 - Commercialization of Ultra-High Payload-to-Weight UAS Subsystems
🇺🇸 United States · R&D program · U.S. Department of War — DARPA
Needs verificationD-34 - Scalable Platform for Enterprise Engineering and Deployment towards Mathematics for the Discovery of Algorithms and Architectures (SPEED DIAL)
🇺🇸 United States · R&D program · U.S. Department of War — DARPA
Needs verificationD-34 - Hoboken - SBIR XL
🇺🇸 United States · R&D program · U.S. Department of War — DARPA
Needs verificationD-34
Source & Provenance
Every value carries its source URL and fetch time
- Official URL
- https://www.dodsbirsttr.mil/topics-app/
- Application URL
- https://www.dodsbirsttr.mil/topics-app/
- Last fetched
- 2026.08.20
- Human review
- Not reviewed — check the official announcement
- First seen
- 2026.08.20
- Data status
- Auto-collected, not reviewed
- AI enrichment
- local:rules-v1 · 3h ago
- PRIMARYSBIR.gov topic — Semantically-Aware ISR
Fetched 2h ago
- HTMLSBIR/STTR 자격요건 (법정)
Fetched 2h ago
- HTML발주 기관 공식 공고
Fetched 2h ago
- · 3h ago — 변경 감지되어 갱신 (3557422a)
- · 4h ago — 최초 수집 (b15881d6)