DAF SBIR DAF26BZ06-DV037: Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons

Quick Answer

DAF26BZ06-DV037 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force has a high priority requirement for much lower-cost long-range air-launched prompt strike weapons that operate in the very high supersonic flight regime, and this topic funds the seeker that goes in them. The objective is a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting radar, passive direction-finding, and line-of-sight datalink modes. Low unit production cost and high-volume manufacturability are stated as key goals. Awards are up to $2,000,000 for up to 24 months, with a 35 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Two things about this topic are unusual enough that they belong in the first paragraph. First, venture capital, hedge fund, and private equity majority-owned small businesses are not eligible under this announcement. That is the opposite of the rule in the DAF Release 6 CSO topics, and it disqualifies a meaningful share of the defense hardware startup market. Second, the Phase II deliverable is a design, not hardware. The offeror will design and model a prototype to Critical Design Review level. Physical prototype build, laboratory testing, hardware-in-the-loop testing, and flight experiment integration all happen in Phase III with Air Force Research Laboratory 6.3 funding.

Topic At a Glance

Topic number: DAF26BZ06-DV037

Title: Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons

Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Direct to Phase II

Solicitation instrument: BAA, not a CSO. This is a separate solicitation from the DAF 2026 SBIR CSO Release 6 topics, with different rules

Program type: Direct to Phase II (D2P2)

Award maximum value: $2,000,000

Award maximum duration: 24 months

Technical volume page limit: 35 pages or slides

OUSD (R&E) Critical Technology Area: Scaled Hypersonics (SHY)

Component Technology Priority Area: Integrated Sensing and Cyber

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Venture capital, hedge fund, private equity majority ownership: not eligible under this announcement

Phase II end state: Critical Design Review level design and model, not built hardware

Production cost targets: $50,000 threshold, $30,000 objective, per flight unit at volume production

Physical envelope: must fit within a 6 inch interior diameter cylinder

Interface standard: WOSA Seeker Domain interface specification

Named Phase III transition targets: AFLCMC/EB and other Department of Defense users

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: seeker, seekers, AESA, multifunction RF, radar, software-defined RF

Note on the deadline time. The DAF instructions direct firms to the DoW FY26 SBIR BAA for the proposal submission deadline date and time rather than restating it. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP topic posting and do not plan around an end-of-day deadline.

Read This First: Venture Capital Ownership Is Disqualifying Here

The DAF Release 6 BAA instructions state that small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are not eligible to submit applications or receive awards for DAF topics.

That single sentence deserves more attention than anything else in this document.

Because this provision is not uniform across the DAF Release 6 component instructions, here is where it stands across all seven documents.

Not eligible: the SBIR BAA Direct to Phase II instructions covering topic DV037; the STTR BAA Direct to Phase II instructions covering topic DV008; and the STTR BAA Phase I instructions covering topics NV006 and NV007.

Eligible: the SBIR BAA Phase I instructions covering topics NV034 through NV036; the SBIR CSO Direct to Phase II instructions; the SBIR CSO Phase I instructions; and the STTR CSO Phase I instructions.

Every Commercial Solutions Opening document permits venture-backed firms. Three of the four Broad Agency Announcement documents exclude them, the SBIR BAA Phase I instructions being the exception. The DAF has not explained the variation. What matters practically is that the exclusion appears in the document governing this topic, so treat it as operative. Verify your status against 13 CFR 121.702 and the definition in the instructions, and raise it with the DAF SBIR/STTR One Help Desk during the open period rather than assuming it resolves in your favor.

BAA Versus CSO: Why This Document Is Not the Same as the Other DAF Release 6 Instructions

The DAF issued Release 6 topics under two different solicitation instruments. The topics numbered with BX, including the five Direct to Phase II topics and the one Phase I topic, sit under the 2026 SBIR Commercial Solutions Opening. This topic, numbered BZ, sits under the 2026 SBIR Broad Agency Announcement.

The two sets of component instructions are largely parallel in structure, and much of the language is identical, but they are separate documents governing separate solicitations. The differences that matter are these.

Venture capital, hedge fund, and private equity majority-owned firms are ineligible under this document. Across DAF Release 6, all three CSO documents permit such firms and three of the four BAA documents exclude them, the SBIR BAA Phase I instructions being the exception. So the provision tracks the specific document, with a strong BAA lean, rather than the instrument cleanly.

Evaluation criteria are not restated in the BAA component instructions. The CSO instructions spell out Criteria A, B, and C in descending order of importance. This BAA document says only that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how you will be scored, and no summary of the CSO criteria is a substitute.

The address change notification uses a different subject line: "FY26 SBIR BAA Address Change" rather than the CSO version.

References throughout point to the FY26 SBIR BAA rather than the CSO for cover sheet instructions, proprietary information marking, technical data rights, and protest procedures.

The performance of work language in this document reads differently, and appears to contain an error, which the next section addresses.

The Performance of Work Problem, and How to Handle It

The BAA component instructions contain three statements about how much work you must perform yourself. Read together they do not cleanly agree, and one of them appears to be a drafting error.

Under Performance of Work Requirements and Location of Work, the document states that for Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit.

That sentence says Phase I, inside a Direct to Phase II instruction document where no Phase I awards are made. The parallel CSO Direct to Phase II instructions say Phase II and set the floor at one-third. The DAF Phase I instructions elsewhere in Release 6 say Phase I and set it at two-thirds. So the most likely reading is that the Phase I paragraph was carried into the Direct to Phase II document by mistake.

Under Consultants and Subcontractors, the document states that in accordance with the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer, and that such requests can only be made upon proposal submission.

Under the Cost Volume subcontracts discussion, the document states that the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price, unless otherwise approved in writing by the Contracting Officer.

The conservative course, and the one we would recommend, is to plan on performing at least two-thirds of the research or analytical effort in house and keeping all consultant, facility lease, and subcontract costs combined below one-half of the total contract price. That satisfies every reading of the document as written, including the strictest one. On a seeker design program that often means resisting the temptation to subcontract large portions of the RF front end or the digital back end design.

If your teaming structure cannot meet two-thirds, the document provides a process, and you have to use it twice. Requests for Performance of Work deviations must be made prior to submission during the topic open period, and again as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove the applicant proceeding with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award. Because the pre-submission request has to happen inside the four week open window, this is a first-week action, not a last-week one. It is also the natural moment to ask the One Help Desk which threshold actually governs.

All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking that approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission.

What the Air Force Is Actually Looking For

The requirement behind the topic

The Department of the Air Force has a high priority requirement for much lower-cost long-range air-launched prompt strike weapons that operate in the very high supersonic flight regime. Toward that requirement, the objective of this topic is to develop a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting RF modes including radar, passive direction-finding, and line-of-sight datalinks. Low unit production cost and high-volume manufacturability are key goals of this topic.

The problem statement is economic before it is technical. Current multifunction radar systems for use onboard various types of small airborne platforms are prohibitively expensive to procure at scale, and the Air Force says this is especially true for systems engineered for use in demanding regimes at peak velocity greater than Mach 3 but under Mach 5. Note that the topic labels that velocity band "high subsonic," which is inconsistent with the stated Mach numbers and with the objective's own description of a very high supersonic flight regime. Read the Mach 3 to Mach 5 figures as the governing statement of the environment.

Because affordability at volume is the point, a proposal that delivers exquisite RF performance without a manufacturing and cost story has missed the topic. Conversely, cost reduction that sacrifices the performance floor also fails, because Phase II requires meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system.

The technical approach the Air Force expects

The effort will leverage recent advancements in RF technology, high-temperature materials science, and associated manufacturing to design a complete multi-function Ku-band RF system to a Critical Design Review level of maturity.

Those three enabling areas are named deliberately and each maps to a different part of the problem. RF technology advancement points toward highly integrated, software-defined architectures, which the topic references reinforce by citing two papers on RF system-on-chip based multi-role sensors. High-temperature materials science addresses the thermal environment of sustained Mach 3 to Mach 5 flight, which is what separates this from a subsonic small-platform radar. Associated manufacturing is the volume production story that the cost targets demand.

The hard requirements

Four requirements are stated explicitly and should be treated as pass or fail gates in your proposal.

Physical envelope. The system must fit within a 6 inch interior diameter cylinder, whether conformally mounted or forward mounted. The Phase II description repeats this, adding that the offeror's design will size and package the front end and back-end RF electronics to fit within that envelope. The fact that both conformal and forward mounting are named means aperture architecture is a real design choice you should address rather than assume.

Interface standard. The design must conform to the WOSA Seeker Domain interface specification. Open systems architecture conformance is a stated requirement, not an option, and it constrains how you partition the system. If you have not worked to that specification before, understanding it is a prerequisite to writing a credible proposal.

Modes. The system must incorporate imaging radar modes, passive direction-finding modes, and height of burst fuze sensing modes. Combined with the objective's mention of line-of-sight datalinks, that is four distinct functions sharing one aperture and back end. Multi-function here means genuinely multi-function.

Maturity. The Phase II output is a design at Critical Design Review level of maturity.

The cost targets, which are the center of the topic

Phase II places emphasis on lowering the flight-unit production cost at volume production to a threshold of $50,000 and an objective of $30,000, while meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system.

Those numbers are the heart of this topic and they are aggressive for a Ku-band multifunction seeker with imaging radar, passive direction finding, datalink, and fuze sensing packaged for a Mach 3 to Mach 5 environment. Your proposal needs a defensible cost model at volume, not a prototype bill of materials. Address component integration and part count reduction, wafer-scale or highly integrated RF and digital solutions, aperture manufacturing approach, thermal management approach and its cost, test and calibration cost per unit which is frequently underestimated in phased array production, and the volume assumptions your model depends on.

Be explicit about the volume at which you hit the threshold and objective. A cost model that only closes at a hundred thousand units per year and a model that closes at two thousand are very different propositions, and the evaluator will want to know which one you are describing.

What Phase II actually produces

For this Direct to Phase II topic, the offeror will design and model a prototype for Critical Design Review level, a complete Ku-band multi-function radar system.

Read that carefully. The verbs are design and model. This is a design maturation program culminating in CDR-level documentation and modeling, plus a cost and manufacturability case. It is not a hardware build program, and a proposal that promises fabricated and tested hardware within the $2,000,000 and 24 month envelope is misreading the topic and inviting doubt about whether you understood it.

That framing also tells you where your effort belongs: modeling and simulation fidelity, design analysis, packaging and thermal analysis, WOSA conformance documentation, producibility analysis, and the cost model. Existing hardware you can point to is feasibility evidence, not a Phase II deliverable.

Phase III

Following successful completion of the Phase II objectives and the culmination of a CDR-level system design, the Air Force Research Laboratory and its transition partner will use 6.3 funding to implement a prototype of the radar system designed in Phase II, perform laboratory, hardware-in-the-loop, and field testing, and then integrate it into a 6.3 flight experiment for further technology maturation. TRL and MRL gaps will be identified and addressed in order to transition the system to AFLCMC/EB and other Department of Defense users.

This is one of the more concrete Phase III descriptions in the Release 6 portfolio, and it is worth using. The government has told you that AFRL and a transition partner will fund the build with 6.3 dollars, that the test sequence is laboratory then hardware-in-the-loop then field then flight experiment, and that the eventual customer is AFLCMC/EB. Both TRL and MRL gaps are named, which reinforces that manufacturing readiness is being assessed alongside technical readiness. Your Relationship with Future R/R&D Efforts section should track this sequence and identify the specific TRL and MRL gaps your Phase II design will leave, along with how Phase III closes them.

The cited references

The topic cites two papers, both about RF system-on-chip based sensors: "ARESTOR: A Multi-role RF Sensor based on the Xilinx RFSoC" by Nial Peters, Colin Horne, and Matthew Ritchie, IEEE Xplore, 2 June 2022; and "Prototyping a Radar Sensor based on a Xilinx RFSoC Device for Detect-And-Avoid onboard Small UAV" by Valentine Wasik, L. Casadebaig, Benjamin Gabard, and Benjamin Gigleux, 2023 20th European Radar Conference.

Both references point in the same direction, toward a software-defined, highly integrated RF system-on-chip approach as the affordability enabler, which is also consistent with the software-defined RF keyword. Read them. Citing and engaging with the government's own references, including where you think a different approach is better, is a cheap and effective way to signal that you did the work.

The Feasibility Requirement

Direct to Phase II means you must document that you already completed the Phase I equivalent work outside the SBIR program. The DAF will not consider your proposal if you fail to demonstrate technical merit and feasibility have been established, or if you fail to demonstrate the feasibility effort was substantially performed by the applicant or the principal investigator. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

What this topic requires specifically

For this Direct to Phase II topic, the offeror must have previously demonstrated Phase I-type feasibility by demonstrating the successful system design, modeling, and hardware specifications of a multifunction radar system for use in an embedded system application. The feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system.

Three elements sit inside that requirement. Successful system design, modeling, and hardware specifications, meaning documented design work and modeling results plus specifications at the hardware level. A multifunction radar system, so a single-function radar heritage is a weaker fit and you should say how it extends. For use in an embedded system application, meaning integrated into a constrained platform rather than a benchtop or standalone instrument.

Plus a fourth element that is a deliverable rather than a heritage claim: the feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system. That is forward-looking. You need to put a baseline concept for the Ku-band seeker into your feasibility documentation, not only evidence of past work.

The general D2P2 rules

Applicants must demonstrate completion of research and development through means other than the SBIR and STTR programs to establish the feasibility of the proposed Phase II effort based on the criteria outlined in the topic description.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists specifically for companies that matured technology outside the SBIR pipeline.

Feasibility efforts detailed must have been substantially performed by the applicant or the principal investigator.

If technology in the feasibility documentation is subject to intellectual property rights, the applicant must provide IP rights assertions, and applicants shall provide a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research. The document points to the FY26 SBIR BAA for technical data rights information.

One helpful mechanical detail this BAA states more clearly than the parallel CSO document: feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. That means your design heritage, modeling results, hardware specifications, and baseline conceptual design can be documented at whatever length the evidence requires without eating into your 35 page technical volume. Use that.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material, which will not be evaluated.

Funding Allowance and Cost Structure

Award ceiling

Up to $2,000,000 across up to 24 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The instructions also note that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

Note the difference between the two dollar figures in this topic. The $2,000,000 is the design contract. The $50,000 threshold and $30,000 objective are per-unit flight hardware production costs at volume that your design must achieve. Do not conflate them.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards. In accordance with the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

A significant procedural note: if no exceptions are taken to an applicant's proposal, the Government may award a contract without exchanges. Therefore the applicant's initial proposal should contain the applicant's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen exchanges later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The DAF will provide up to $50,000 per Phase II award, in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal. Applicants may elect to use 50 percent of this TABA allocation, meaning $25,000, on a first SBIR Phase II award and 50 percent, meaning $25,000, on a sequential SBIR Phase II award.

Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases.

For this topic, development of manufacturing plans is the standout. High-volume manufacturability is a stated key goal, the cost targets are aggressive, and Phase III explicitly names MRL gaps alongside TRL gaps. TABA support for manufacturing planning is directly on point.

Those activities can be undertaken in furtherance of the following purposes: making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

Requests for TABA funding creditable to a TABA provider must include the following information or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider, including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.

If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed, including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.

A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.

Cost volume expectations

A detailed cost proposal must be submitted, and cost proposal information will be treated as proprietary. Proposed costs must be provided by both individual cost element and contractor fiscal year in sufficient detail to determine the basis for estimates, as well as the purpose, necessity, and reasonableness of each. This information will expedite award if the proposal is selected. Cost proposal attachments do not count toward proposal page limitations.

Direct labor. Identify key personnel by name, if possible, and labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a design and modeling program, this will be nearly the entire budget, so it deserves the most care. RF engineers, digital designers, packaging and thermal engineers, and producibility analysts should be visible as named individuals or clearly defined categories with hours that match the task structure.

Direct cost materials. Costs for materials, parts, and supplies must be justified and supported. Provide an itemized list of types, quantities, prices, and where appropriate purpose. If computer or software purchases are planned, detailed information such as manufacturer, price quotes, proposed use, and support for the need will be required. On this topic, electromagnetic simulation, circuit and system modeling, and thermal analysis licenses are likely the significant items, and they need quotes and justification.

Other direct costs. This includes specialized services such as machining or milling, special test and analysis, and costs for temporary use or lease of specialized facilities and equipment. Provide usage hours expected, rates, and sources, as well as a brief discussion concerning the purpose and justification. Proposals including leased hardware must include an adequate lease versus purchase rationale. Anechoic chamber or near-field range time, if any is planned for design validation, belongs here.

Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an applicant would otherwise possess in the normal course of business. These may include such items as innovative instrumentation or automatic test equipment.

Subcontracts. Subcontract costs must be supported with copies of subcontract agreements. Agreement documents must adequately describe the work to be performed and cost bases. The agreement document should include a statement of work, assigned personnel, hours and rates, materials if any, and proposed travel if any. A letter from a subcontractor agreeing to perform a task or tasks at a fixed price is not considered sufficient. The proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price, unless otherwise approved in writing by the Contracting Officer. The prime contractor must accomplish price analysis, including reasonableness, of the proposed subcontractor costs. If based on comparison with prior efforts, identify the basis upon which the prior prices were determined reasonable. If price analysis techniques are inadequate or the FAR requires subcontractor cost or pricing data submission, provide a cost analysis, which includes but is not limited to consideration of materials, labor, travel, other direct costs, and proposed profit rates.

Consultants. For each consultant, provide a separate agreement letter briefly stating the service to be provided, hours required, and hourly rate, as well as a short, concise resume.

Travel. Each effort should include, at a minimum, a kickoff or interim meeting. Travel costs must be justified as required for the effort. Include destinations, number of trips, number of travelers per trip, airfare, per diem, lodging, and ground transportation. Per diem and lodging rates may be found in the Joint Travel Regulation, Volume 2. On a program that culminates in a Critical Design Review, budget for the design review itself and for interim technical interchange meetings with AFRL, since Phase III depends on AFRL picking the design up.

Indirect costs. Indicate proposed rates' bases, for example budgeted or actual rates per fiscal year. The proposal should identify the specific rates used and allocation bases to which they are applied. Do not propose composite rates; proposed rates and applications per fiscal year throughout the anticipated performance period are required.

Non-SBIR governmental or private investment is allowed. However, it is not required, nor will it be a proposal evaluation factor.

Export Control, Which Is Central on a Seeker Topic

The technology within this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including export of sensitive technical data, and the EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by the foreign nationals in accordance with section 3.5 of the Announcement. Offerors are advised that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

A weapon seeker is about as clearly ITAR-controlled as a technology gets, so treat this as a hard staffing constraint rather than a disclosure exercise. In the technical volume, identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for those individuals, in addition to technical resumes, provide countries of origin, type of visas or work permits held, and identify the tasks they are anticipated to perform.

Foreign nationals, also known as foreign persons, means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR BAA and disclose this information regardless of whether the topic is subject to ITAR restrictions.

When the topic area is subject to export control, these individuals, if permitted to participate, are limited to work in the public domain. Further, tasks assigned must not be capable of assimilation into an understanding of the project's overall objectives. This prevents foreign citizens from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations in order to verify foreign citizens' eligibility to perform on a contract awarded under this BAA.

The following will apply to all projects with military or dual-use applications developing beyond fundamental research, meaning basic and applied research ordinarily published and shared broadly within the scientific community. The Contractor shall comply with all U.S. export control laws and regulations, including ITAR 22 CFR Parts 120 through 130 and the EAR 15 CFR Parts 730 through 799, in the performance of this contract. In the absence of available license exemptions or exceptions, the Contractor shall be responsible for obtaining the appropriate licenses or other approvals, if required, for exports of, including deemed exports of, hardware, technical data, and software, or for the provision of technical assistance. The Contractor shall be responsible for obtaining export licenses, if required, before utilizing foreign persons in the performance of this contract, including instances where the work is to be performed on-site at any Government installation, whether in or outside the United States, where the foreign person will have access to export-controlled technologies including technical data or software. The Contractor shall be responsible for all regulatory record keeping requirements associated with the use of licenses and license exemptions or exceptions. The Contractor shall be responsible for ensuring that these provisions apply to its subcontractors.

If you are asserting export-controlled status, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission must be included in Volume 5. The form, instructions, and FAQs are available at the United States and Canada Joint Certification Program website. DD Form 2345 approval will be required if the proposal is selected for award.

Proposal Structure: The Seven Volumes

Formatting

Proposals should be direct, concise, and informative. Type shall be no smaller than 11-point on standard 8.5 by 11 paper, with one-inch margins and pages consecutively numbered. Applicants are discouraged from including promotional and non-programmatic items. If included, such material will count toward the page limit.

The technical volume limit for this topic is 35 pages or slides, per the topic index. Pages or slides in excess of this number will not be considered during evaluations. The preferred submission format is Portable Document Format. Graphics must be distinguishable in black and white, which matters for a topic where you will want to show antenna patterns, block diagrams, and packaging layouts. Virus-check all submissions.

The complete proposal must be submitted electronically through DSIP. Ensure the complete technical volume and additional cost volume information is included in this sole submission.

Fraud, Waste, and Abuse training must be completed prior to proposal submission. When training is complete and certified, DSIP will indicate completion of the Volume 6 requirement, and the proposal cannot be submitted until the training is complete. The DAF recommends completing submission early, as site traffic is heavy prior to solicitation close, causing system lag, and states plainly not to wait until the last minute. The DAF will not be responsible for proposals not completely submitted prior to the deadline due to system inaccessibility unless advised by DoW, and will not accept alternative means of submission outside of DSIP.

Also note the criminal warning the instructions include: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released. On a seeker topic, be deliberate about what goes in the abstract, since it will become public.

If a proposal submitted in response to this BAA is substantially the same as another proposal submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, the applicant must so indicate on the Cover Sheet.

Volume 2, Technical Volume

The technical proposal includes all items listed below in the order provided.

Table of contents, located immediately after the Cover Sheet.

Glossary of acronyms and abbreviations used in the proposal.

Milestone identification, including a program schedule with all key milestones identified.

Identification and significance of the problem or opportunity, briefly referencing the specific technical problem or opportunity to be pursued under this effort.

Phase II technical objectives, detailing the specific objectives of the Phase II work and describing the technical approach and methods to be used in meeting these objectives, including an assessment of the potential commercial application for each objective.

Work plan. The work plan shall be a separate and distinct part of the proposal package, using a page break to divide it from the technical proposal, and begins on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility. Do not include proprietary information, because in the event of proposal selection the work plan will be incorporated into the resulting contract by reference. The recommended format is 1.0 Objective, providing a brief overview of the specialty area explaining the purpose and expected outcome; 2.0 Scope, providing a concise description of the work to be accomplished including the technology area to be investigated, goals, and major milestones, with task development and deliverables as the key elements meaning the anticipated end result or the effort's product, and consistent with the information in section 4.0; 3.0 Background, in which the applicant shall identify appropriate specifications, standards, and other documents applicable to the effort, including information or explanation for and constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task and Technical Requirements, in which detailed individual task descriptions must be developed in an orderly progression with sufficient detail to establish overall program requirements and goals, with the work effort segregated into major tasks identified in separately numbered paragraphs. Each numbered major task should delineate the work to be performed by subtask. The work plan must contain every task to be accomplished in definite, realistic, and clearly stated terms. Use "shall" whenever the work plan expresses a binding provision, "should" or "may" to express a declaration or purpose, and "will" when no contractor requirement is involved.

Section 3.0 Background deserves attention on this topic, since the WOSA Seeker Domain interface specification is exactly the kind of applicable specification the instructions are asking you to identify. Name it, and name any other standards your design conforms to.

Deliverables. Include a section clearly describing the specific sample or prototype hardware and software to be delivered, as well as data deliverables, schedules, and quantities. Be aware of the possible requirement for unique item identification in accordance with DFARS 252.211-7003, Item Identification and Valuation, for hardware. If hardware or software will be developed but not delivered, provide an explanation. On this topic that explanation matters, because the Phase II output is a design and model rather than built hardware, so be clear about what physical artifacts, if any, exist and why.

At a minimum, the following reports will be required under all Phase II contracts. Scientific and Technical Reports, noting that rights in technical data including software developed under the terms of any contract resulting from a SBIR Announcement generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the SBIR/STTR contract for a period of 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page will be a single-page project summary identifying the work's purpose, providing a brief description of the effort accomplished, and listing potential result applications; the summary may be published by DoW and therefore must not contain any proprietary or classified information, while the remainder of the report should contain details of project objectives met, work completed, results obtained, and technical feasibility estimates. Status reports are due quarterly at a minimum. The Air Force may require additional reporting documentation including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project will result in partial or total development and delivery of hardware, and updates to the commercialization results.

Given that this program produces a CDR-level design, the engineering drawings item and the 20 year data rights provision together deserve a conversation with counsel before you decide what design detail to generate under the award.

Related work. Describe significant activities directly related to the proposed effort, including any previous programs conducted by the principal investigator, proposing firm, consultants, or others, and their application to the proposed project. Describe how these activities interface with the proposed project and discuss any planned coordination with outside sources. Also list any applicant-identified subject matter experts, regardless of affiliation, providing comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related to the proposed effort but similar, providing a short description, the client for which the work was performed including an individual to be contacted and phone number, and the date of completion.

Commercialization potential. The DoW requires a commercialization plan be submitted with the Phase II proposal, specifically addressing what the first planned product to incorporate the proposed technology is, who the probable customers are and what the estimated market size is, how much money is needed to bring the technology to market and how it will be raised, whether the firm has the necessary marketing expertise and if not how the firm will compensate, and who the probable competitors are and what price or quality advantage is anticipated by the firm. The commercialization strategy plan should briefly describe the commercialization potential for the proposed project's anticipated results as well as plans to exploit it. Commercial potential is evidenced by the existence of private sector or non-SBIR/STTR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and the presence of other indicators of commercial technology potential including the firm's commercialization strategy.

If awarded a D2P2, the awardee will be required to update periodically the commercialization results of the project via SBA. These updates will be required at completion of the effort and subsequently when the contractor submits a new SBIR/STTR proposal to DoW. Firms not submitting a new proposal to DoW will be requested to provide updates annually after the D2P2 completion. Note that the Commercialization Plan and the Company Commercialization Report are distinct documents; the CCR comprises Volume 4.

The commercialization question is harder on this topic than on most, because a Ku-band prompt strike seeker has limited non-defense application. The honest framing is that the primary market is defense volume production, that the named Phase III path runs through AFRL to AFLCMC/EB and other DoD users, and that the underlying software-defined multifunction RF architecture and low-cost manufacturing approach have adjacent applications. Do not manufacture an implausible commercial market. Build the case on volume defense demand plus genuine architecture-level spillover.

Relationship with future R/R&D efforts. State the anticipated results of the proposed approach, specifically addressing plans for Phase III, if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III R/R&D effort, if planned. The topic gives you the Phase III sequence, so track it.

Key personnel. In the technical volume, identify all key personnel involved in the project. Include information directly related to education, experience, and citizenship. A technical resume for the Principal Investigator, including publications if any, must also be included. Concise technical resumes for subcontractors and consultants, if any, are also useful. The Principal Investigator's primary employment must be with the small business concern at the time of award and during the entire period of performance. Primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager can be designated to a proposal at any given time.

Facilities and equipment. Describe instrumentation and physical facilities necessary and available to carry out the D2P2 effort. Justify equipment to be purchased, with detail in the cost proposal. State whether proposed performance locations meet environmental laws and regulations of federal, state, and local governments for, but not limited to, airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors. Private companies, consultants, or universities may be involved in the project. All should be described in detail and included in the cost proposal. In accordance with the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm, unless otherwise approved in writing by the Contracting Officer, and these requests can only be made upon proposal submission. Signed copies of all consultant or subcontractor letters of intent must be attached to the proposal. These letters should briefly state the contribution or expertise being provided. Include statements of work and detailed cost proposals, and information regarding consultant or subcontractor unique qualifications. Subcontract copies and supporting documents do not count against the Phase II page limit. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support of similar proposals or awards. While it is permissible, with proper notification, to submit identical proposals or proposals containing a significant amount of essentially equivalent work for consideration under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort. Any potential for this situation must be disclosed to the solicitation agencies before award. Provide the name and address of the federal agencies or DoW components to which proposals were or will be submitted or from which an award is expected or has been received, the proposal submission or award dates, the proposal title, the PI's name and title for each proposal submitted or award received, the solicitation titles, numbers, and dates under which the proposal was or will be submitted or under which an award is expected or has been received, the contract number if an award was received, and the applicable topics for each SBIR proposal submitted or award received. If this section does not apply, state in the proposal, "No prior, current, or pending support for proposed work."

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the DoW FY26 SBIR BAA for full details on this requirement. Information contained in the CCR will not be considered by the DAF during proposal evaluations. Complete it for compliance and do not treat it as a scoring opportunity.

Volume 5, Supporting Documents

The following documents may be required if applicable to your proposal. DD Form 2345, which applies to this export-controlled topic. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 BAA. Technical Data Rights Assertions, if asserting data rights restrictions. On a seeker design program built on proprietary RF architecture, this last item is how you draw the line between your background intellectual property and what you develop under the award.

Feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. Its requirements are described above.

The detailed TABA request, if you are requesting TABA, also belongs in Volume 5.

Volume 6, Fraud, Waste, and Abuse Training

Fraud, Waste and Abuse training material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the Disclosures of Foreign Affiliations or Relationships to Foreign Countries webform in Volume 7 of the DSIP proposal submission. The webform will not be accepted as a PDF supporting document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW Program BAA.

How Your Proposal Will Be Evaluated

The criteria are in the BAA, not in this document

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel. Throughout evaluation, selection, and award, confidential proposal and evaluation information will be protected to the greatest extent possible. D2P2 proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

The component instructions then state that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0.

That is the whole of it. Unlike the DAF Release 6 CSO instructions, which restate Criteria A, B, and C with their relative importance, this BAA document does not reproduce the evaluation criteria. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how your proposal will be scored, and you should not assume the CSO criteria carry over. This is the single most important research task before you start writing, because the criteria determine your proposal's structure and emphasis.

The DAF adds that it is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic, that multiple procurements are planned and anticipated as a result of the topic, that each proposal is considered a separate procurement and will be evaluated on its own merit, and that the Government may award all, some, or none of the proposals.

Foreign risk evaluation

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of Defense, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures the DAF will use include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

For an RF hardware company, patent analysis and the semiconductor supply chain both deserve a look before you propose. RF system-on-chip devices, gallium nitride and gallium arsenide processes, packaging, and passive components frequently trace to suppliers with entries on one or more of the denial lists below, and the topic's own references point toward commercial RFSoC parts.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the small business concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.

If the DAF denies an award under 15 U.S.C. 638(g)(16) or 638(o)(20), or upon determining that the concern has a security risk described in that paragraph, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv).

Support contractors

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors. These support contractors may include, but are not limited to, APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the DAF SBIR/STTR Contracting Officer with concerns about any of these contractors.

Status, feedback, and protests

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions, since separate notifications are provided for each proposal.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for proposal status before that time.

Refer to the FY26 SBIR BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(b) and FAR 52.233-3, protests after award should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer and to the individual procuring contracting officer listed on your firm's selection notification.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. Settle eligibility first, because nothing else matters if you fail it. If venture capital, hedge fund, or private equity funds hold majority ownership in part, resolve your status against the definition and raise it with the DAF SBIR/STTR One Help Desk. Read Section 6.0 of the DoW FY26 SBIR BAA, since the evaluation criteria are there and not in the component instructions. Obtain and study the WOSA Seeker Domain interface specification. Read the two cited RFSoC papers. Assemble your feasibility documentation: system design, modeling, and hardware specifications for a multifunction radar in an embedded application, substantially performed by your firm or your PI, with no SBIR or STTR lineage. Draft the baseline conceptual design for the Ku-band seeker, which the feasibility demonstration must also describe. Build the volume production cost model that reaches $50,000 threshold and $30,000 objective, and identify the volume assumption it rests on. Audit your semiconductor and component supply chain against the eight denial lists. Resolve export control staffing, since foreign nationals may be restricted from performing on this topic, and start DD Form 2345 if you do not hold one. Check your work distribution against the two-thirds figure and, if you cannot meet it, file the pre-submission Performance of Work deviation request in the first week of the open period. Complete Volume 6 training and verify SAM and DSIP alignment.

September 23 through October 3. Draft Volume 2 in the required order against the 35 page limit. Structure the technical approach around the four hard requirements: the 6 inch interior diameter envelope with conformal or forward mounting addressed, WOSA Seeker Domain conformance, the imaging radar, passive direction-finding, and height of burst fuze sensing modes plus line-of-sight datalink, and CDR-level maturity. Build the milestone schedule early, since the TABA task milestone list must track to your milestone payment schedule. Write the work plan as a separate page-broken document in contract language with no proprietary content, naming the WOSA specification in section 3.0 Background.

October 4 through October 12. Build the cost volume by individual cost element and contractor fiscal year. Get quotes for simulation and modeling software licenses. Collect signed letters of intent, statements of work, and detailed cost proposals from every consultant and subcontractor, remembering that a letter agreeing to a fixed price is not sufficient. Verify all outside costs sit below one-half of the total contract price. Write the detailed TABA request into Volume 5 if requesting TABA, and consider manufacturing plan development given the volume production emphasis.

October 13 through October 16. Finalize the Volume 5 package, which for this topic carries real weight: feasibility documentation with no page limit, DD Form 2345, Technical Data Rights Assertions, and the TABA request. Complete the Volume 7 webform and the Volume 4 CCR. Run a compliance pass: 35 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics distinguishable in black and white, virus-checked PDF, no marketing material, no proprietary information in the technical abstract or the work plan.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BZ06-DV037?

‍ ‍

DAF26BZ06-DV037 is a Department of the Air Force SBIR Direct to Phase II topic titled "Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting radar, passive direction-finding, and line-of-sight datalink modes, for long-range air-launched prompt strike weapons operating in the very high supersonic flight regime.

‍ ‍

Are venture capital backed companies eligible for this topic?

‍ ‍

No. The Direct to Phase II instructions governing this topic state that small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are not eligible to submit applications or receive awards for DAF topics. If your ownership structure is near this line, verify your status and raise it with the DAF SBIR/STTR One Help Desk during the open period.

‍ ‍

Why does the eligibility rule differ from the other DAF Release 6 topics?

‍ ‍

Because it varies by document. Three DAF Release 6 documents exclude venture-backed firms: this one, the STTR BAA Direct to Phase II instructions, and the STTR BAA Phase I instructions. Four permit them: the SBIR BAA Phase I instructions and all three CSO documents. Every CSO document permits them and three of four BAA documents exclude them, so there is a strong BAA pattern with one exception. Since the exclusion appears in three independently issued documents, a deliberate restriction is more plausible than a typographical error, though the DAF has not explained it. Do not carry an eligibility conclusion from one document to another in either direction.

‍ ‍

Does the BAA versus CSO distinction determine eligibility?

‍ ‍

Almost, but not cleanly. All three CSO documents permit venture-backed firms and three of the four BAA documents exclude them, but the SBIR BAA Phase I instructions permit them, which breaks a purely instrument-level rule. Check the specific component instruction document that governs the topic you are pursuing rather than reasoning from the instrument.

‍ ‍

How much funding is available under DAF26BZ06-DV037?

‍ ‍

Up to $2,000,000 for a period of performance up to 24 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition to that ceiling.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct firms to the DoW FY26 SBIR BAA for the exact submission time, which is ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting rather than assuming an end-of-day deadline.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

What does Phase II actually deliver?

‍ ‍

A design, not hardware. For this Direct to Phase II topic the offeror will design and model a prototype for Critical Design Review level, a complete Ku-band multi-function radar system. Physical prototype implementation, laboratory testing, hardware-in-the-loop testing, field testing, and flight experiment integration all occur in Phase III with Air Force Research Laboratory 6.3 funding. A proposal promising fabricated and tested hardware inside the $2,000,000 and 24 month envelope has misread the topic.

‍ ‍

What are the production cost targets?

‍ ‍

The Phase II emphasis is on lowering the flight-unit production cost at volume production to a threshold of $50,000 and an objective of $30,000, while meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system. These are per-unit hardware costs at volume, entirely separate from the $2,000,000 design award. State the volume assumption your cost model depends on.

‍ ‍

What is the physical envelope requirement?

‍ ‍

The system must fit within a 6 inch interior diameter cylinder, whether conformally mounted or forward mounted. The Phase II description adds that the design will size and package the front end and back-end RF electronics to fit within that envelope. Because both conformal and forward mounting are named, aperture architecture is a design choice worth addressing explicitly.

‍ ‍

What interface standard must the design conform to?

‍ ‍

The WOSA Seeker Domain interface specification. This is a stated key technical requirement, so obtain and study the specification before writing, and name it among the applicable specifications in section 3.0 Background of your work plan.

‍ ‍

What modes must the system support?

‍ ‍

The topic names imaging radar modes, passive direction-finding modes, and height of burst fuze sensing modes as key technical requirements, and the objective adds line-of-sight datalinks to the RF modes supported. That is four distinct functions sharing one aperture and back end.

‍ ‍

What flight regime does this seeker operate in?

‍ ‍

The objective describes a very high supersonic flight regime, and the description specifies peak velocity greater than Mach 3 but under Mach 5. Note that the description labels that band "high subsonic," which is inconsistent with the Mach numbers stated and with the objective's own wording, so treat the Mach 3 to Mach 5 figures as governing.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This is a Direct to Phase II topic. Applicants must provide documentation satisfying the Phase I feasibility requirement to be included in the Phase II proposal, demonstrating completion of research and development through means other than the SBIR and STTR programs.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

The offeror must have previously demonstrated Phase I-type feasibility by demonstrating the successful system design, modeling, and hardware specifications of a multifunction radar system for use in an embedded system application. The feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system. So you need both documented heritage and a forward-looking baseline concept.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility efforts detailed must have been substantially performed by the applicant or the principal investigator.

‍ ‍

Does feasibility documentation count against my page limit?

‍ ‍

No. The instructions state that feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. Use that room for your design heritage, modeling results, hardware specifications, and baseline conceptual design rather than compressing them into the technical volume.

‍ ‍

How long can my technical volume be?

‍ ‍

35 pages or slides, per the topic index. Pages or slides in excess of this number will not be considered during evaluations. Type must be no smaller than 11-point on standard 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Cost proposal attachments, subcontract copies and supporting documents, and feasibility documentation do not count toward the limit.

‍ ‍

How will my proposal be evaluated?

‍ ‍

The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how you will be scored, and you should not assume the Criteria A, B, and C structure from the DAF CSO instructions carries over. This is the first research task before writing.

‍ ‍

How much of the work must my company perform?

‍ ‍

The document states three overlapping figures. Under Performance of Work Requirements it says a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit, though that paragraph refers to Phase I inside a Direct to Phase II document and appears to be a drafting artifact. Under Consultants and Subcontractors it says a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. And the subcontracts cost guidance caps all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements at one-half of the total contract price. Planning to perform at least two-thirds in house and keeping all outside costs below one-half of contract price satisfies every reading. If you cannot, file a Performance of Work deviation request during the open period and again with your proposal, and ask the One Help Desk which threshold governs.

‍ ‍

How do I request a performance of work deviation?

‍ ‍

Requests must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove the applicant proceeding with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award. Because the pre-submission request must happen inside the four week open window, treat it as a first-week action.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for them. The topic advises that foreign nationals proposed to perform may be restricted due to the technical data under U.S. export control laws. A certified DD Form 2345, or evidence of application submission, belongs in Volume 5, and approval will be required if selected for award.

‍ ‍

Can foreign nationals work on this project?

‍ ‍

Only in limited ways, if at all. Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which the instructions note prevents foreign citizens from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations to verify eligibility. On a weapon seeker topic, treat this as a hard staffing constraint.

‍ ‍

Who owns the design data I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. Because this program produces a CDR-level design and the Air Force may require engineering drawings as additional reporting, review the data rights provision with counsel before deciding what design detail to generate under the award, and use Technical Data Rights Assertions in Volume 5 to protect background intellectual property.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state that information contained in the CCR will not be considered by the DAF during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award, in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, and splittable as $25,000 on a first SBIR Phase II award and $25,000 on a sequential one. Development of manufacturing plans is an eligible activity and is directly relevant here given the high-volume manufacturability goal and the MRL gaps named in Phase III. The detailed request must be in Volume 5, including provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests that only specify a value in Volume 3 will not be considered.

‍ ‍

What happens in Phase III?

‍ ‍

Following successful completion of the Phase II objectives and the culmination of a CDR-level system design, AFRL and its transition partner will use 6.3 funding to implement a prototype of the radar system designed in Phase II, perform laboratory, hardware-in-the-loop, and field testing, and then integrate it into a 6.3 flight experiment for further technology maturation. TRL and MRL gaps will be identified and addressed in order to transition the system to AFLCMC/EB and other Department of Defense users.

‍ ‍

What is the commercial market for this technology?

‍ ‍

It is limited, and honesty serves you better than invention here. A Ku-band prompt strike weapon seeker has a primarily defense market, and the topic gives you a concrete Phase III path through AFRL to AFLCMC/EB and other DoD users. Build the commercialization case on volume defense demand plus genuine architecture-level spillover from the software-defined multifunction RF approach and the low-cost manufacturing methods, rather than on an implausible commercial application.

‍ ‍

What references does the topic cite?

‍ ‍

Two papers on RF system-on-chip based sensors: "ARESTOR: A Multi-role RF Sensor based on the Xilinx RFSoC" by Nial Peters, Colin Horne, and Matthew Ritchie, IEEE Xplore, 2 June 2022; and "Prototyping a Radar Sensor based on a Xilinx RFSoC Device for Detect-And-Avoid onboard Small UAV" by Valentine Wasik, L. Casadebaig, Benjamin Gabard, and Benjamin Gigleux, 2023 20th European Radar Conference. Both point toward a software-defined, highly integrated RFSoC approach as the affordability enabler.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal submitted.

‍ ‍

Will I be able to negotiate after submitting?

‍ ‍

Possibly not. If no exceptions are taken to your proposal, the Government may award a contract without exchanges, so your initial proposal should contain your best terms from a cost or price and technical standpoint. The Government reserves the right to reopen exchanges later if the Contracting Officer determines it necessary.

‍ ‍

Who do I contact with questions?

‍ ‍

For general information related to the DAF SBIR/STTR program and proposal preparation instructions, contact the DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us. The DAF encourages applicants to request clarifying information as early as possible, since delays in such requests constrain its ability to provide satisfactory resolution to applicant concerns. For questions regarding the DSIP electronic submission system, contact the DoW SBIR/STTR Help Desk at dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. If your company mail or email addresses or points of contact change after proposal submission, provide the information to the DAF SBIR/STTR One Help Desk with the subject line "FY26 SBIR BAA Address Change."

‍ ‍

Positioning Advice for Companies Considering This Topic

‍ ‍

Check eligibility before anything else. Majority ownership in part by multiple venture capital operating companies, hedge funds, or private equity funds is disqualifying under this announcement. That is an unusual gate in modern defense SBIR, and it removes a large fraction of the companies that would otherwise be natural bidders. If you clear it, you are competing in a thinner field than the technology would suggest, which is worth knowing.

‍ ‍

Read BAA Section 6.0 first. The evaluation criteria are not in the component instructions. Writing a proposal without them is guessing at what matters, and the criteria should shape your section emphasis and your milestone framing.

‍ ‍

Lead with cost and manufacturability, not RF performance. The topic says low unit production cost and high-volume manufacturability are key goals, sets a $50,000 threshold and $30,000 objective, and identifies MRL gaps alongside TRL gaps in Phase III. Performance is the constraint you must satisfy, and cost is the variable you are being asked to move. Structure the proposal accordingly, with a defensible volume cost model rather than a prototype bill of materials.

‍ ‍

State your volume assumption explicitly. A cost target is meaningless without the production rate behind it. Give the number, justify it against plausible program quantities, and show cost sensitivity if the rate is lower.

‍ ‍

Respect the design-only scope. Design and model to CDR is what Phase II buys. Overpromising fabricated hardware reads as either a misreading of the topic or an unrealistic plan, and cost realism concerns follow either way. Put the build in Phase III where the government put it.

‍ ‍

Take WOSA conformance seriously as an architecture driver. An open interface specification changes how you partition front end, back end, and processing. Show that you understand it rather than asserting conformance in a sentence.

‍ ‍

Address the thermal problem directly. High-temperature materials science is one of three named enabling areas, and Mach 3 to Mach 5 sustained flight is the reason. Radome, aperture, and electronics thermal management is where a design that works subsonically fails here, and it interacts with the cost target because exotic thermal solutions are expensive.

‍ ‍

Engage the cited references. Both point toward RFSoC-class integration. If that is your approach, say how you go beyond the referenced work. If you have a better path, say why, and be specific. Either is stronger than ignoring them.

‍ ‍

Make the four modes share hardware credibly. Imaging radar, passive direction finding, height of burst fuze sensing, and line-of-sight datalink from one aperture and back end is the multi-function claim. Explain the time and frequency resource sharing, the calibration approach, and where the modes conflict.

‍ ‍

Build the feasibility package properly, and use the page relief. Feasibility documentation lives in Volume 5 and is not page limited. System design, modeling, and hardware specifications for a multifunction radar in an embedded application, plus the baseline conceptual design, can be documented thoroughly without spending technical volume pages.

‍ ‍

Audit the semiconductor supply chain early. The denial criteria name eight lists, and RF and digital component sourcing touches them more often than teams expect. A mandatory denial after selection is an expensive way to learn this.

‍ ‍

Plan for two-thirds in house. Given the ambiguity in the document, plan to the strictest figure and keep all outside costs below half the contract price. If your approach depends on a large subcontracted element, file the deviation request in the first week of the open period rather than discovering the problem at submission.

DAF SBIR DAF26BZ06-NV036: Flightline Radio Network

Quick Answer

DAF26BZ06-NV036 is a Department of the Air Force SBIR Phase I topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force wants a secure, adaptable, interoperable private cellular network for the flight line at Edwards Air Force Base, built on 5G and Open Radio Access Network architecture, to support aircraft maintenance, logistics, and test and evaluation operations. Awards are up to $250,000 for a period of performance up to 6 months, with a 20 page or slide technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Two features make this the most accessible topic in the release for a commercial company. First, it is a named-site problem: Edwards AFB, its existing infrastructure, its flight line, and the 412th Maintenance Group as an eventual transition partner. That specificity means the winning proposal will be the one that understands the site, not just the technology. Second, the technology itself is commercial. 5G Open RAN, private cellular, and augmented reality maintenance support all exist in industry today, and the topic starts the technology at Technology Readiness Level 4. This is an adaptation and integration problem, not a research problem, and the Phase I deliverable is a feasibility study with initial design and a preliminary prototype proof-of-concept.

Topic At a Glance

Topic number: DAF26BZ06-NV036

Title: Flightline Radio Network

Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Phase I Proposal Submission Instructions

Program type: Phase I

Award maximum value: $250,000

Award maximum duration: 6 months

Technical volume page limit: 20 pages or slides

OUSD (R&E) Critical Technology Area: Quantum and Battlefield Information Dominance (Q-BID)

Component Technology Priority Areas: Integrated Network System-of-Systems; Sustainment and Logistics; FutureG

Projected CMMC level requirement: Level 2 (Self)

Export control status: no topic-level ITAR or EAR restriction paragraph appears on this topic, unlike NV034 in the same release. General disclosure obligations still apply

Site: Edwards Air Force Base flight line

Technology readiness at project start: TRL 4

Phase I success criterion: the topic states achieving TRL 3 to 4

Target at end of Phase II: TRL 6, with the topic also stating a targeted advancement to TRL 6 to 7 by end of Phase II

Phase III target: TRL 7

Named transition partners: the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding

Program alignment: Advanced Battle Management System (ABMS)

Minimum work performed in house: two-thirds of the research or analytical effort

Subcontract and consultant cap: one-third of total contract price, profit excluded

Technical and Business Assistance: up to $6,500 per Phase I award

Type size: no smaller than 10-point

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: 5G, private cellular, flight line, aircraft maintenance, secure communications, predictive maintenance, augmented reality, Edwards AFB, logistics

Note on the deadline time. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the proposal submission deadline date and time. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP posting rather than assuming end of day.

What the Air Force Is Actually Looking For

The operational problem at Edwards

Flight line operations at Edwards Air Force Base face increasing demands for more efficient, secure, and real-time communication systems to enhance aircraft maintenance, logistics, and operational performance. The Air Force is direct about why current arrangements fall short: current communication solutions are limited by outdated infrastructure, lack of interoperability, and insufficient data transmission capabilities.

There is a distinct opportunity to leverage advanced cellular network technologies, particularly 5G and Open Radio Access Network architectures, to address these limitations and modernize the flight line environment.

Note that Edwards is a test and evaluation base, which shapes the requirement. The objective states that the effort aims to support advanced test and evaluation activities, promoting a high-performance communication environment that meets the stringent demands of a modern Air Force Base. A flight line at a test wing generates instrumentation data, telemetry, and rapidly changing configurations in a way that an operational fighter wing does not, and the Range Commanders Council IRIG 106 telemetry standards reference in the topic reinforces that this environment has its own data conventions.

The objective

The objective is to explore and develop innovative technologies leveraging cellular network infrastructure, particularly Open RAN architectures, to enhance communication capabilities on the flight line at Edwards AFB. The goal is to establish a secure, adaptable, and interoperable cellular network that facilitates superior aircraft maintenance, logistics, and operational efficiency.

This research and development initiative will focus on feasibility studies, system design, and foundational prototyping, ensuring flexibility for future adaptation and integration into subsequent phases based on Phase I outcomes and insights.

That last sentence tells you the shape of the Phase I effort. Feasibility studies, system design, and foundational prototyping, with deliberate flexibility rather than a locked architecture.

The use cases the Air Force names

The topic is specific about what the network is for, and each named use case is a place your proposal should say something concrete.

Ground crew coordination. The project will focus on enhancing ground crew coordination, which is the baseline voice and data communication problem.

Real-time aircraft health monitoring. Enabling real-time aircraft health monitoring, which implies on-aircraft or on-equipment data collection moving over the network while the aircraft is on the ground.

Predictive maintenance. Supporting predictive maintenance to reduce aircraft downtime and enhance mission readiness. This is the value argument, since downtime is the cost the Air Force is trying to reduce.

Augmented reality maintenance support. Augmented reality applications will be integrated to provide maintenance personnel with real-time guidance, schematics, and remote support, further optimizing maintenance tasks. Note the specificity: guidance, schematics, and remote support. AR is named as an integrated application, not an aspiration, which means bandwidth and latency budgets for AR belong in your design.

Improved data sharing and operational efficiency. The aim is a secure, adaptable, and interoperable network that improves real-time communication, data sharing, and operational efficiency at Edwards AFB.

The technical direction

From a technical standpoint, the initiative will employ a 5G Open RAN architecture, offering increased flexibility, interoperability, and security while minimizing vendor lock-in and lowering costs.

Vendor lock-in avoidance and cost reduction are named as reasons for Open RAN, which is worth registering. The Air Force is not asking for Open RAN because it is fashionable; it is asking because a disaggregated, multi-vendor architecture is the procurement outcome it wants. A proposal built on a single-vendor proprietary stack answers a different question.

The modular design of this network will allow it to accommodate evolving test requirements and future upgrades, ensuring a scalable and cost-effective solution.

The network will integrate seamlessly with Edwards AFB's existing infrastructure and employ efficient frequency allocation through spectrum sharing mechanisms.

Those last two clauses are the hard parts, and they are the ones a commercial cellular vendor is most likely to underestimate. Integration with existing base infrastructure means engaging with what is already there rather than overlaying a greenfield network. Spectrum sharing at a Department of Defense test range is a genuinely constrained problem, involving federal spectrum allocations, range operations, and coordination that has no commercial analogue.

Interference with aircraft systems is a named requirement

The detailed Phase I description states that the effort will outline network architecture, components, deployment strategy, and address potential interference with aircraft systems.

This deserves emphasis because it is where a commercial telecom proposal most often fails to persuade a flight test audience. Radiating RF energy near aircraft, in a flight test environment, next to instrumentation and telemetry systems, raises electromagnetic interference and electromagnetic environmental effects questions that must be addressed on their own terms. Phase II reinforces this, stating that testing will evaluate performance and ensure compatibility with aircraft systems. If your proposal treats interference as a footnote, a reviewer from the test community will notice.

Phase I

The topic describes Phase I twice, and the two descriptions are complementary rather than contradictory.

The summary version: conduct feasibility studies and initial system design. This includes analyzing current flight line communication requirements, exploring Open RAN components, and developing foundational prototypes. Deliverables will include a comprehensive feasibility report, initial design schematics, and a preliminary prototype proof-of-concept.

The detailed version: Phase I will assess the feasibility of an Open RAN network for flight line use at Edwards AFB. It will outline network architecture, components, deployment strategy, and address potential interference with aircraft systems. Deliverables include security analysis, use cases, and integration plans. Success includes achieving TRL 3 to 4, demonstrating proof-of-concept through a preliminary prototype and feasibility report.

Combined, your Phase I deliverable list is: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, documented use cases, and integration plans. That is six named items in six months, and every one of them is a document or a bench-level demonstration rather than a fielded system. Scope accordingly.

Note a small inconsistency in the source. The topic states the anticipated TRL at the start of the project is TRL 4, but then says Phase I success includes achieving TRL 3 to 4. Starting at 4 and succeeding by reaching 3 to 4 does not quite parse. The most sensible reading is that commercial Open RAN technology generally sits at TRL 4 or higher, while the specific flight line application at Edwards is what needs to be brought to TRL 3 to 4. Frame your maturity claims in terms of the application rather than the underlying technology, and describe what you will actually demonstrate.

Phase II

Phase II will develop and test a prototype Open RAN network at Edwards AFB. The system will include base stations, network components, user equipment, and specialized sensors. Testing will evaluate performance and ensure compatibility with aircraft systems, assessing coverage, bandwidth, latency, security, and operational impact. The system must integrate with Edwards AFB's infrastructure and achieve TRL 6, demonstrating a functional prototype in an operational setting.

The summary version adds that Phase II involves developing and refining the prototype based on Phase I insights, implementation of pilot deployments and rigorous testing to validate system performance and security, with deliverables including a full-scale prototype, detailed test results, and an integration plan for transitioning the technology to operational use at Edwards AFB.

Five assessment dimensions are named for Phase II: coverage, bandwidth, latency, security, and operational impact. Your Phase I design work should establish predicted values or targets against those five, because that is the framework your own Phase II will be measured on. Note also that specialized sensors appear in the Phase II system description, which connects back to the real-time aircraft health monitoring use case.

The topic also notes a targeted advancement to TRL 6 to 7 by the end of Phase II in one place and TRL 6 in another. Planning toward TRL 6, a functional prototype in an operational setting, satisfies both.

Phase III and the transition path

Phase III involves scaling the Open RAN cellular network at Edwards AFB to enhance flight line operations, targeting TRL 7. Military applications include real-time maintenance data and improved logistics coordination. Commercial use spans complex logistics in aerospace sectors. Transition efforts will engage the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding.

This is among the most concrete transition descriptions in the DAF Release 6 portfolio. You are given the using organization, the 412th MXG at Edwards, the major command, AFMC, and two named funding sources, the Air Force Sustainment Center and AFLCMC. Reference all of them in your future research and development discussion.

The topic also states that successful completion is expected to significantly advance the Department of Defense's technological state by providing a robust, future-proof communication solution tailored to the unique demands of flight line operations, and that this development aligns with modernization priorities such as Integrated Network System-of-Systems and Sustainment and Logistics, ultimately contributing to the operationally focused Advanced Battle Management System.

The ABMS connection is worth using carefully. It elevates a base infrastructure project into a recognized Air Force modernization line, and the topic makes the link itself so you are not stretching.

The cited references

Four references, all standards and industry documents rather than research papers, which reinforces that this is an integration topic.

3rd Generation Partnership Project, 3GPP, the mobile broadband standard.

Range Commanders Council IRIG 106, the 106 Telemetry Standards, via the Public RCC TRMC website.

O-RAN Alliance, O-RAN Use Cases and Deployment Scenarios.

Next Generation Mobile Networks Alliance, Open RAN White Paper.

The IRIG 106 citation is the one that distinguishes this topic from a generic private cellular opportunity. It is the telemetry standard family used at test ranges, and its presence signals that the flight line environment at Edwards carries range instrumentation conventions your network has to coexist with. A proposal that cites 3GPP and O-RAN but ignores IRIG 106 has read half the reference list.

Funding Allowance and Cost Structure

Award ceiling and realistic scoping

Up to $250,000 across up to 6 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The instructions add that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

Six months and $250,000 supports a serious requirements analysis, an architecture and deployment design, a security analysis, an integration plan, and a laboratory or small-scale proof-of-concept. It does not support standing up a network at Edwards, and the topic does not ask you to. Deployment at the base is Phase II.

Contract type

The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts. Awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system, since if the company intends to continue work with the Department of War an approved accounting system allows competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts. For a commercial telecom company new to defense work, that is worth acting on early, because DCAA accounting system approval takes time.

If no exceptions are taken to an offeror's proposal, the Government may award a contract without negotiations. Therefore the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen negotiations later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The DAF will provide up to $6,500 per Phase I award, in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal.

This BAA Phase I document carries the full detailed TABA request requirements. Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases. Those activities can be undertaken in furtherance of making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

Cybersecurity assistance and development of regulations are the two most relevant here. Cybersecurity because a security analysis is a named Phase I deliverable and CMMC Level 2 self-assessment is the projected requirement. Development of regulations because spectrum coordination at a federal test range is a regulatory problem as much as a technical one.

Requests for TABA funding creditable to a TABA provider must include the following or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.

If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.

A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.

Cost volume requirements

Cost information should be provided by completing the Cost Volume in DSIP and including the Cost Volume Itemized Listing. The cost volume detail must be adequate to enable Air Force personnel to determine the purpose, necessity, and reasonableness of each cost element. The DSIP Cost Volume and Itemized Cost Volume Information will not count against the specified page limit, and the itemized listing may also be submitted in Volume 5 under the "Other" dropdown option.

Direct cost materials. Justify costs for materials, parts, and supplies with an itemized list containing types, quantities, prices, and where appropriate purpose. Material costs may include raw materials, parts, subassemblies, components, and manufacturing supplies. On this topic, radio units, servers or edge compute for the RAN Intelligent Controller and core, test user equipment, and AR headsets belong here.

Other direct costs. This includes but is not limited to specialized services such as machining, milling, special testing or analysis, and costs incurred in temporarily using specialized equipment. Proposals including leased hardware must include an adequate lease versus purchase justification. Anechoic or shielded chamber time for interference characterization, spectrum analysis equipment rental, and commercial software or licensing may sit here, and the lease versus purchase rationale is likely to be relevant given how much cellular test equipment is normally rented.

Direct labor. Identify key personnel by name, if possible, or by labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a study and design Phase I, this is most of the budget. RF and network engineers, security engineers, and someone credible on flight line or maintenance operations should all be visible.

Travel. Travel costs must relate to project needs. Break out travel costs by trip, number of travelers, airfare, per diem, lodging, and similar. The number of trips required, as well as the destination and purpose of each, should be reflected. The instructions recommend budgeting at least one trip to the Air Force location managing the contract.

On this topic that recommendation is more than a formality. The entire proposition is a network at a specific base, and a requirements analysis of the Edwards flight line performed entirely from a distance is weaker than one informed by a site visit. Budget the travel and say what you will do there.

Subcontracts. Involvement of university or other consultants in the project's planning or research stages may be appropriate. If so, describe in detail and include information in the Cost Volume. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded from the calculation, unless otherwise approved in writing by the Contracting Officer. The SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. Support subcontract costs with copies of executed agreements that adequately describe the work to be performed, and at a minimum include a Statement of Work with a corresponding detailed Cost Volume for each planned subcontract.

Open RAN is by design a multi-vendor architecture, which creates a specific tension with this cap. One-third of $250,000 is roughly $83,000 for all consultant fees, facility lease and usage fees, and subcontract or purchase agreements combined. If your architecture requires radio units, a core, and a controller from three different vendors, the purchase agreements alone can approach that. Model it early, and consider whether Phase I needs procured hardware at all or whether a design plus a software-based or emulated proof-of-concept satisfies the deliverable.

Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an offeror would otherwise possess in the normal course of business, and may include items such as innovative instrumentation or automatic test equipment.

Consultants. Provide a separate agreement letter for each consultant, briefly stating what service or assistance will be provided, the number of hours required, and the hourly rate. A consultant with flight line maintenance or range spectrum experience is a strong addition to this proposal, and this is how you document them.

Performance of work requirements

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit.

Occasionally the DAF will consider deviations from this performance of work requirement. Requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove requesting applicants to proceed with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award.

All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States. The awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking this approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission.

This last point deserves attention on a telecom topic. Cellular network software development is frequently distributed internationally, and offshore engineering teams are common in the industry. All research and development work under this award must be performed in the United States absent specific written approval sought with the initial proposal.

Supply Chain, Which Is a Live Issue for Cellular Equipment

Nothing in this topic is more likely to disqualify an otherwise strong bidder than equipment sourcing. The foreign risk denial criteria name eight lists, and cellular network equipment intersects several of them directly. The Section 889 Prohibition List, the FCC List of Equipment and Services, the Entity List, and the Military End User List all include telecommunications equipment suppliers.

Radio units, baseband hardware, transport equipment, and even components inside otherwise domestic products are the exposure. Open RAN's multi-vendor premise increases the number of suppliers you have to clear rather than decreasing it. Audit your intended bill of materials against those lists before you propose, and be prepared to name your suppliers.

Note also that the projected CMMC level requirement for this topic is Level 2 with self-assessment, and that a security analysis is a named Phase I deliverable. A company proposing to build a secure network for a flight line should expect its own security posture to be relevant, and cybersecurity practices is the first item on the foreign risk assessment list.

Personnel Disclosure and Export Control

This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same Phase I release. Your general obligations still apply.

The Volume 2 Key Personnel requirements apply to every topic in this release. Identify in the Technical Volume all key personnel who will be involved in this project, including information on directly related education, experience, and citizenship. A technical resume of the principal investigator, including a list of publications if any, must be included, and only one principal investigator or project manager can be designated to a proposal at any given time. Concise technical resumes for subcontractors and consultants are also useful.

Identify all U.S. permanent residents to be involved in the project as direct employees, subcontractors, or consultants. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants. For all non-U.S. citizens, in addition to technical resumes, provide countries of origin, the type of visa or work permit under which they are performing, and an explanation of their anticipated level of involvement on this project, as appropriate. Additional information may be requested during negotiations in order to verify the foreign citizen's eligibility to participate on a contract issued as a result of this announcement.

Do not upload information such as Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying identity documents.

If you are asserting export-controlled status for your own technology, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission is a Volume 5 document, and approval will be required if selected for award.

Proposal Structure: The Seven Volumes

Formatting, and what does not count against the page limit

The Technical Volume should include all graphics and attachments but should not include the Cover Sheet, which is completed separately as Volume 1. Ensure that all graphics are distinguishable in black and white, which matters here because network architecture diagrams and coverage maps often rely on color.

The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. This differs from the DAF Direct to Phase II instructions, which require 11-point.

The Phase I Technical Volume page and slide limits identified for the topics do not include the Cover Sheet, the Cost Volume, or the Cost Volume Itemized Listing. Only the Technical Volume and any enclosures or attachments count toward the page limit. The documents required for upload into Volume 5 under "Other" do not count toward the specified limits. In the interest of equity, pages or slides in excess of the stated limits will not be reviewed.

The limit for this topic is 20 pages or slides. A slide-format volume is acceptable and suits architecture diagrams, coverage analysis, and deployment layouts well.

Fraud, Waste and Abuse training must be completed prior to proposal submission, and DSIP will indicate completion of the Volume 6 requirement once the training is complete and certified. Note the criminal warning the instructions carry: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released. Be careful here about anything describing base infrastructure or vulnerabilities.

Volume 2, Technical Volume

The Phase I technical volume shall contain the required elements below. These instructions supplement the FY26 SBIR BAA, and in addition to the requirements found in the BAA, applicants are required to provide the following information in Volume 2.

Key personnel, as described above.

Phase I Statement of Work outline. The DAF uses the work plan outline as the initial draft of the Phase I Statement of Work. Therefore, do not include proprietary information in the work plan outline. To do so will necessitate a request for revision, if selected, and may delay award.

Include a work plan outline in the following format. Scope, listing the effort's major requirements and specifications. Task Outline, providing a brief outline of the work to be accomplished during the Phase I effort. Milestone Schedule. Deliverables. Progress reports. Final report with SF 298.

Your Deliverables entry should reflect the six items the topic names across its two Phase I descriptions: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, use cases, and integration plans.

The SF 298 is the Report Documentation Page that accompanies a technical report. It is named in the required outline, so plan for it.

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the FY26 SBIR BAA for full details. Information contained in the CCR will not be considered by the Air Force during proposal evaluations.

Volume 5, Supporting Documents

The following documents may be required if applicable to your proposal. DD Form 2345, for proposals submitted under export-controlled topics. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the FY26 SBIR BAA. Technical Data Rights Assertions, if asserting data rights restrictions.

For a commercial telecom company, Technical Data Rights Assertions matter because your existing software, orchestration, and network management intellectual property predates this award. This is the mechanism for keeping that boundary clear.

The detailed TABA request, if you are requesting TABA, also goes in Volume 5. Documents uploaded into Volume 5 under "Other" do not count toward the page limit, and the Cost Volume Itemized Listing may also be submitted there.

Volume 6, Fraud, Waste, and Abuse Training

Material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the webform in Volume 7 of the DSIP proposal submission. The disclosures will not be accepted as a PDF Supporting Document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW SBIR Program BAA.

How Your Proposal Will Be Evaluated

The criteria live in the BAA

Proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. The DAF is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals.

This BAA document does not reproduce the evaluation criteria, unlike the DAF Release 6 CSO Phase I instructions which restate Criteria A, B, and C. Read the criteria in the DoW FY26 SBIR BAA before writing, and do not assume the CSO criteria carry over.

Foreign risk evaluation

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of War, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.

If an award is denied on these grounds, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv).

Of all the topics in this release, this is the one where the eight lists bite hardest, because telecommunications equipment is the explicit subject of several of them.

Venture capital, hedge fund, and private equity ownership

Small business concerns that are owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

Worth stating plainly because the DAF Release 6 BAA Direct to Phase II instructions say the opposite for that document's topic. Within the same BAA cycle, the Phase I instructions permit venture-backed firms and the Direct to Phase II instructions do not. The Phase I instructions govern this topic, so venture-backed private cellular companies are eligible here. Verify eligibility per document rather than assuming a cycle-wide rule.

Support contractors, status, feedback, and protests

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors, which may include but are not limited to TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space and Missiles Centers may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the AF SBIR/STTR Contracting Officer with concerns regarding the use of support contractors.

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions.

The Air Force anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the BAA Contracting Officer for proposal status before that time.

Refer to the DoW SBIR Program BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(a) and FAR 52.233-2, protests should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer. The DAF uses its best efforts to resolve concerns raised by interested parties at the contracting officer level through open and frank discussions, and for agency protests the DAF provides for inexpensive, informal, procedurally simple, and expeditious resolution of protests.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

How Phase II works

DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the conclusion of the period of performance. This decision will be based on the awardee's technical progress, as determined by a DAF Technical Point of Contact review using the Phase II review criteria.

Phase II is the demonstration of the technology found feasible in Phase I. Only Phase I awardees are eligible to submit a Phase II proposal. All Phase I awardees will be sent a notification with the Phase II proposal submittal date and detailed preparation instructions. If the physical or email addresses or firm points of contact have changed since submission of the Phase I proposal, correct information shall be sent to the DAF SBIR/STTR One Help Desk. Phase II dollar values, performance periods, and proposal content will be specified in the Phase II request for proposal. Only one Phase II proposal may be submitted for each Phase I award.

The DAF reserves the right to modify the Phase II submission requirements, and should the requirements change, all Phase I awardees will be notified. The DAF also reserves the right to change any administrative procedures that will improve management of the DAF SBIR/STTR Program at any time.

Because Phase II involves deploying at Edwards and the request can come during Phase I performance, building the relationship with the base during Phase I is directly instrumental rather than merely helpful.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 6 months from award

A working backward plan

Before September 23. Read the evaluation criteria in the DoW FY26 SBIR BAA, since they are not in the component instructions. Read the four cited references, including IRIG 106, which is the one most likely to be unfamiliar to a commercial cellular team. Learn what you can about the Edwards flight line environment and the 412th Maintenance Group. Audit your intended equipment bill of materials against the eight denial lists, which on a telecom topic is the highest-risk diligence item. Identify a consultant with flight line maintenance or range spectrum experience if you do not have that inside. Work out your spectrum approach and the electromagnetic interference story. Model the one-third outside cost cap against any hardware procurement, and decide whether Phase I needs purchased equipment at all. Inventory background intellectual property for Technical Data Rights Assertions. Complete Volume 6 training and verify SAM and DSIP alignment. Send clarifying questions to the DAF SBIR/STTR One Help Desk, which encourages early inquiries.

September 23 through October 3. Draft the technical volume against the 20 page limit, organized around the six named Phase I deliverables. Give the network architecture, components, and deployment strategy real specificity, address interference with aircraft systems on its own terms, and write the security analysis as an actual analysis rather than a compliance statement. Set targets for the five Phase II assessment dimensions: coverage, bandwidth, latency, security, and operational impact. Write the work plan outline separately with no proprietary content, since it becomes the Statement of Work. Build the milestone schedule early since the TABA task list must track to it.

October 4 through October 12. Build the cost volume and itemized listing, neither of which counts against the page limit. Itemize radios, compute, test user equipment, and AR hardware if you are procuring any. Include the recommended trip to the Air Force location managing the contract with a stated purpose. Get separate agreement letters from each consultant and executed agreements with statements of work and detailed cost volumes for each planned subcontract, and check the one-third cap including purchase agreements. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5 with Technical Data Rights Assertions and any applicable DD Form 2345, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 10-point minimum type, one-inch margins, graphics distinguishable in black and white, no PII uploaded to DSIP, no proprietary content in the technical abstract or the work plan outline.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BZ06-NV036?

‍ ‍

DAF26BZ06-NV036 is a Department of the Air Force SBIR Phase I topic titled "Flightline Radio Network," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks innovative technologies leveraging cellular network infrastructure, particularly 5G Open Radio Access Network architectures, to establish a secure, adaptable, and interoperable network on the flight line at Edwards Air Force Base supporting aircraft maintenance, logistics, and operational efficiency.

‍ ‍

How much funding is available under DAF26BZ06-NV036?

‍ ‍

Up to $250,000 for a period of performance up to 6 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $6,500 in Technical and Business Assistance is available per Phase I award, in addition to the per-topic total.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

Is this topic tied to a specific base?

‍ ‍

Yes. The flight line at Edwards Air Force Base is named throughout, the network must integrate with Edwards AFB's existing infrastructure, Phase II deploys and tests there, and Phase III scales there. The 412th Maintenance Group at Edwards is named as a transition partner. Site understanding is a differentiator, not a detail.

‍ ‍

What are the use cases?

‍ ‍

Ground crew coordination, real-time aircraft health monitoring, predictive maintenance to reduce aircraft downtime and enhance mission readiness, and augmented reality applications providing maintenance personnel with real-time guidance, schematics, and remote support. The broader aim is improved real-time communication, data sharing, and operational efficiency.

‍ ‍

Why Open RAN specifically?

‍ ‍

The topic states that a 5G Open RAN architecture offers increased flexibility, interoperability, and security while minimizing vendor lock-in and lowering costs, and that its modular design will accommodate evolving test requirements and future upgrades. Vendor lock-in avoidance and cost reduction are stated procurement goals, so a single-vendor proprietary stack is answering a different question.

‍ ‍

What does Phase I deliver?

‍ ‍

Across the topic's two Phase I descriptions, six items are named: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, use cases, and integration plans. Phase I will also outline network architecture, components, and deployment strategy, and address potential interference with aircraft systems.

‍ ‍

What technology readiness level applies?

‍ ‍

The topic states the anticipated TRL at project start is TRL 4, and that Phase I success includes achieving TRL 3 to 4. Those do not quite reconcile, and the sensible reading is that commercial Open RAN technology sits at TRL 4 or above while the specific flight line application at Edwards is what must be matured to TRL 3 to 4. Frame maturity claims around the application rather than the underlying technology.

‍ ‍

Do I need to address interference with aircraft systems?

‍ ‍

Yes, explicitly. Phase I is required to address potential interference with aircraft systems, and Phase II testing must ensure compatibility with aircraft systems. Radiating RF near aircraft in a flight test environment raises electromagnetic interference and environmental effects questions, and a proposal that treats this as a footnote will not persuade a test community reviewer.

‍ ‍

What about spectrum?

‍ ‍

The topic states the network will employ efficient frequency allocation through spectrum sharing mechanisms. Spectrum at a Department of Defense test range involves federal allocations, range operations, and coordination that has no direct commercial analogue, so treat it as a substantive design problem rather than an assumption.

‍ ‍

What happens in Phase II?

‍ ‍

Develop and test a prototype Open RAN network at Edwards AFB, including base stations, network components, user equipment, and specialized sensors. Testing evaluates performance and ensures compatibility with aircraft systems, assessing coverage, bandwidth, latency, security, and operational impact. The system must integrate with Edwards AFB's infrastructure and achieve TRL 6, demonstrating a functional prototype in an operational setting. Deliverables include a full-scale prototype, detailed test results, and an integration plan for transitioning to operational use.

‍ ‍

What happens in Phase III?

‍ ‍

Scaling the Open RAN cellular network at Edwards AFB, targeting TRL 7. Military applications include real-time maintenance data and improved logistics coordination, and commercial use spans complex logistics in aerospace sectors. Transition efforts will engage the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding.

‍ ‍

How does this connect to larger Air Force programs?

‍ ‍

The topic states the development aligns with modernization priorities such as Integrated Network System-of-Systems and Sustainment and Logistics, ultimately contributing to the operationally focused Advanced Battle Management System. Because the topic makes that link itself, you can reference ABMS without overreaching.

‍ ‍

What references should I read?

‍ ‍

Four are cited: 3GPP, the mobile broadband standard; Range Commanders Council IRIG 106 telemetry standards; the O-RAN Alliance's O-RAN Use Cases and Deployment Scenarios; and the NGMN Alliance Open RAN White Paper. IRIG 106 is the one that distinguishes this from a generic private cellular opportunity, since it governs range telemetry conventions your network must coexist with.

‍ ‍

How long can my technical volume be?

‍ ‍

20 pages or slides. The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. The Cover Sheet, Cost Volume, and Cost Volume Itemized Listing do not count toward the limit; only the Technical Volume and any enclosures or attachments do. Documents uploaded into Volume 5 under "Other" do not count either. Pages or slides in excess of the stated limit will not be reviewed.

‍ ‍

What is my biggest disqualification risk?

‍ ‍

Equipment supply chain. The foreign risk denial criteria name eight lists, including the Section 889 Prohibition List, the FCC List of Equipment and Services, the Entity List, and the Military End User List, all of which reach telecommunications equipment. Open RAN's multi-vendor premise increases the number of suppliers you must clear. Audit your bill of materials before you propose.

‍ ‍

How much of the work must my company perform?

‍ ‍

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility lease or usage fees, and other subcontract or purchase agreements together may not exceed one-third of the total contract price or cost with profit excluded, unless the Contracting Officer approves otherwise in writing. On a $250,000 award that is roughly $83,000 for all outside costs combined.

‍ ‍

Does the one-third cap include equipment purchases?

‍ ‍

The cap as written covers consultant fees, facility lease or usage fees, and other subcontract or purchase agreements. Because Open RAN is multi-vendor by design, purchased radios, core software, and controllers can approach that figure quickly. Consider whether Phase I requires procured hardware at all, or whether a design plus a software-based or emulated proof-of-concept satisfies the deliverable.

‍ ‍

Can my offshore engineering team work on this?

‍ ‍

Not without specific approval. All research and development work must be performed in the United States. The DAF may approve a particular portion performed or obtained outside the United States only based on a rare and unique circumstance, with written approval from the awarding Funding Agreement officer, and the request must accompany the initial proposal submission. This is a real constraint in an industry where distributed development is common.

‍ ‍

Is this topic export controlled?

‍ ‍

This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same release. General disclosure obligations still apply, including identifying all U.S. permanent residents and all non-U.S. citizens involved with countries of origin, visa or work permit type, and anticipated level of involvement.

‍ ‍

What identity information should I not upload?

‍ ‍

Do not upload Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying documents.

‍ ‍

How will my proposal be evaluated?

‍ ‍

The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. Read those criteria before writing, and do not assume the Criteria A, B, and C structure from the DAF CSO instructions carries over.

‍ ‍

Are venture capital backed companies eligible?

‍ ‍

Yes, for this topic. The BAA Phase I instructions state that firms owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible for DAF topics. The DAF Release 6 BAA Direct to Phase II instructions state the opposite for that document's topic, so verify per document.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state information contained in the CCR will not be considered by the Air Force during proposal evaluations.

‍ ‍

Why does the work plan outline matter so much?

‍ ‍

Because the DAF uses it as the initial draft of the Phase I Statement of Work. The instructions direct you not to include proprietary information in it, warning that doing so will necessitate a request for revision if selected and may delay award.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $6,500 per Phase I award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. This BAA document carries the full detailed request requirements: provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, with the task milestone list tracking to your milestone payment schedule. The detailed request must be in Volume 5, and requests specifying only a value in Volume 3 will not be considered. Cybersecurity assistance and development of regulations are the most relevant eligible activities here.

‍ ‍

Should I budget travel to Edwards?

‍ ‍

The instructions recommend budgeting at least one trip to the Air Force location managing the contract, and on this topic that is substantive rather than administrative. A requirements analysis of a specific flight line performed entirely remotely is weaker than one informed by a site visit. Budget it and say what you will do there.

‍ ‍

How do I get to Phase II?

‍ ‍

DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the period of performance concludes, based on the awardee's technical progress as determined by a DAF Technical Point of Contact review. Only Phase I awardees are eligible, and only one Phase II proposal may be submitted for each Phase I award.

‍ ‍

When will I hear about selection?

‍ ‍

The Air Force anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email.

‍ ‍

Who do I contact with questions?

‍ ‍

The AF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the DoW FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR BAA Address Change."

‍ ‍

Positioning Advice for Companies Considering This Topic

‍ ‍

Win on site knowledge, not on cellular expertise. Many companies can build a private 5G network. Far fewer understand a flight line at a test wing, where instrumentation, telemetry, rapidly changing aircraft configurations, and range spectrum coordination all intersect. Demonstrating that you understand Edwards specifically is the strongest differentiator available on this topic.

‍ ‍

Get someone with flight line credibility on the team. A consultant with maintenance operations or range spectrum experience changes how the proposal reads to a reviewer from the test community, and the cost volume has a documented path for consultants. This is a high-return, low-cost addition.

‍ ‍

Treat interference with aircraft systems as a first-class technical section. It is a named Phase I requirement and a named Phase II test criterion. Address emissions, coexistence with aircraft avionics and instrumentation, and your test approach. This is where a commercial telecom proposal most often loses a defense flight test audience.

‍ ‍

Read and cite IRIG 106. It is the reference in the list least likely to be familiar and the one that signals whether you understand the environment. Range telemetry conventions are part of your interoperability problem.

‍ ‍

Write the security analysis as analysis. It is a named deliverable, CMMC Level 2 self-assessment is the projected requirement, and cybersecurity practices leads the foreign risk assessment list. A threat model for a base flight line network, covering the RAN, the core, the user equipment, and the AR endpoints, is worth real pages.

‍ ‍

Audit your bill of materials before anything else. On a cellular topic, the eight denial lists are the most likely cause of a mandatory denial. Section 889, the FCC covered list, the Entity List, and the Military End User List all touch telecom equipment. Know your suppliers and their component sources.

‍ ‍

Solve the one-third cap problem structurally. Open RAN means multiple vendors, and purchase agreements count against the same cap as subcontracts. Decide early whether your Phase I proof-of-concept can be software-based or emulated, since that keeps procurement out of a tight cost envelope and leaves room for the analysis the topic actually asks for.

‍ ‍

Set targets against the five Phase II dimensions now. Coverage, bandwidth, latency, security, and operational impact are the Phase II assessment criteria. Establishing predicted values in Phase I gives the government a measurement framework and gives you a defensible basis for the Phase II request.

‍ ‍

Make the downtime argument quantitative. Predictive maintenance reducing aircraft downtime is the value proposition. Even a rough model of sortie availability or maintenance cycle time improvement is more persuasive than a description of the technology.

‍ ‍

Use the named transition path in full. The 412th Maintenance Group, Air Force Materiel Command, the Air Force Sustainment Center, AFLCMC, and ABMS are all named in the topic. Very few SBIR topics hand you the using organization, the command, the funding sources, and the program alignment. Put all of them in your future research and development section.

‍ ‍

Build the commercial case on aerospace logistics. The topic names complex logistics in aerospace sectors as the commercial application. Commercial MRO facilities, airport ramp operations, and manufacturing plants have the same problem structure, which makes the dual-use argument straightforward rather than strained.

DAF SBIR DAF26BZ06-NV035: Quantum Memory for Secure Communication

Quick Answer

DAF26BZ06-NV035 is a Department of the Air Force SBIR Phase I topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force wants advanced quantum memory systems that enable secure communication within quantum networks, with the specific aim of building quantum repeaters that extend the range of Quantum Key Distribution. The problem being solved is stated plainly: current QKD systems are limited by signal loss over long distances, which prevents widespread implementation. Quantum memory is the component that makes a repeater possible, and a repeater is what breaks the distance limit. Awards are up to $250,000 for a period of performance up to 6 months, with a 20 page or slide technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

The maturity framing is the most important thing to understand before you write. The topic states that at project start the technology is at Technology Readiness Level 2, focusing on application concept formulation, and that Phase I success means demonstrating TRL 3 by drafting a feasibility report and a detailed architecture plan for a Phase II prototype of a lab-based test bench capable of end-to-end quantum information transport. That is a design and analysis deliverable, not a working repeater. Six months and $250,000 buys a scientific approach, a conceptual design, a feasibility report, and an architecture plan, with laboratory validation activity where you can achieve it.

Topic At a Glance

Topic number: DAF26BZ06-NV035

Title: Quantum Memory for Secure Communication

Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Phase I Proposal Submission Instructions

Program type: Phase I

Award maximum value: $250,000

Award maximum duration: 6 months

Technical volume page limit: 20 pages or slides

OUSD (R&E) Critical Technology Area: Quantum and Battlefield Information Dominance (Q-BID)

Component Technology Priority Areas: Integrated Sensing and Cyber; Integrated Network System-of-Systems; Quantum Science; Emerging Threat Reduction; Sustainment and Logistics

Projected CMMC level requirement: Level 2 (Self)

Export control status: no topic-level ITAR or EAR restriction paragraph appears on this topic, unlike NV034 in the same release. General disclosure obligations still apply

Technology readiness at project start: TRL 2, application concept formulation

Phase I success criterion: demonstrate TRL 3

Target at end of Phase II: the topic states TRL 5 in one place and TRL 4 to 6 in another

Phase III target: TRL 7

Minimum work performed in house: two-thirds of the research or analytical effort

Subcontract and consultant cap: one-third of total contract price, profit excluded

Technical and Business Assistance: up to $6,500 per Phase I award

Type size: no smaller than 10-point

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: quantum memory, quantum key distribution, secure communication, quantum networks, photonic qubits, quantum repeaters, long-range communication, cybersecurity, TRL 2-5, quantum science, AFWERX, strategic communications, emerging threats

Note on the deadline time. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the proposal submission deadline date and time. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP posting rather than assuming end of day.

What the Air Force Is Actually Looking For

The threat and the gap

The topic opens with the strategic motivation. The rapid advancement of quantum computing poses a significant challenge to traditional encryption methods, potentially compromising the security of digital communications. Quantum Key Distribution provides a solution by using quantum properties to generate secure encryption keys.

Then the limitation. Current QKD systems are limited by signal loss over long distances, preventing widespread implementation. This project seeks to address that limitation by developing advanced quantum memory systems, or quantum repeaters, designed to extend the range and fidelity of quantum signals. These repeaters will enable efficient Quantum Key Distribution over long distances, thereby enhancing secure communications for the Air Force's digital infrastructure.

That framing sets your problem statement. You are not being asked to improve QKD key rates at existing distances. You are being asked to attack the distance limit itself, and quantum memory is the enabling component.

The objective

The objective is to develop and demonstrate advanced quantum memory systems essential for enabling secure communication within quantum networks. The primary goal is to enhance the storage and transmission capabilities of photonic qubits, ensuring high coherence and minimal loss over extended distances. This will facilitate the creation of scalable quantum repeater systems that significantly improve the efficiency and robustness of Quantum Key Distribution.

By focusing on the foundational aspects of quantum memory hardware, the effort aims to address critical challenges in quantum communication, providing a reliable solution that can be adapted and expanded upon in subsequent phases. The results from this phase will establish a solid technical foundation, allowing for iterative improvement and seamless integration with existing and future quantum entanglement sources and networks.

Two phrases deserve attention. "Foundational aspects of quantum memory hardware" tells you the Air Force expects hardware-oriented work rather than protocol or software analysis. And "seamless integration with existing and future quantum entanglement sources and networks" tells you that interoperability with entanglement sources is part of the design problem, not an afterthought, which the Phase II description reinforces.

The primary goal is restated as developing and demonstrating advanced quantum memory systems capable of high coherence and minimal loss, essential for reliable communication within quantum networks.

The Phase I tasks

The topic describes Phase I twice, at different levels of specificity, and the two descriptions should be read together rather than treated as alternatives.

The first description says the required efforts will commence with foundational research and development of quantum memory hardware. In Phase I, the tasks will involve designing quantum memory materials, developing quantum repeater prototypes, and validating their performance through controlled laboratory experiments. Key activities will include designing and fabricating quantum memory materials aimed at reducing signal decoherence and data loss; developing prototypes capable of storing and transmitting photonic qubits; and conducting laboratory tests to validate the prototypes' performance against defined metrics such as coherence, loss, and noise.

The second, later description is more specific about what Phase I is assessed on. Phase I will assess the feasibility of using quantum memory hardware to enhance Quantum Key Distribution by requiring proposals to detail the scientific approach, develop a conceptual design for a functional quantum memory prototype showcasing its capabilities and potential advantages in both lab and simulated environments. Demonstrate Technology Readiness Level 3 by drafting a feasibility report and a detailed architecture plan for a Phase II prototype of a lab-based test bench capable of end-to-end quantum information transport.

The tension between those two passages is real and worth handling deliberately in your proposal. The first mentions fabricating materials and developing prototypes with laboratory validation. The second sets the assessed deliverable at a feasibility report plus an architecture plan, at TRL 3. Six months and $250,000 will not support meaningful materials fabrication and prototype development from scratch, so the sensible reading is that the assessed Phase I output is the feasibility report, the scientific approach, the conceptual design, and the architecture plan, with whatever laboratory validation you can credibly perform on material or apparatus you already have.

The strongest proposals will be explicit about this. State what design and analysis you will deliver, state what laboratory work you will actually perform in six months and on what existing capability, and do not promise fabrication and validation cycles the schedule cannot hold. Cost realism sits inside the evaluation, and an overpromised quantum hardware schedule is not credible.

The three named Phase I key activities

Use these as structure. Designing and fabricating quantum memory materials aimed at reducing signal decoherence and data loss. Developing prototypes capable of storing and transmitting photonic qubits. Conducting laboratory tests to validate the prototypes' performance against defined metrics, with coherence, loss, and noise given as the examples.

Coherence, loss, and noise is your metric triple. Whatever your memory approach, atomic ensemble, rare-earth doped crystal, solid-state defect center, or another, give predicted values against those three and say how you will measure them.

Minimum deliverables

Minimum deliverables for this project include detailed technical reports, functional quantum memory prototypes, performance evaluation data, and an integration roadmap detailing steps for transition into operational use.

Note that this list is framed as deliverables for the project rather than for Phase I specifically, which is consistent with the functional prototype appearing in the Phase II description. For Phase I, the assessed items are the feasibility report and the architecture plan at TRL 3, with the integration roadmap being a natural Phase I product as well since it is analysis rather than hardware.

The advanced quantum repeater systems developed through this SBIR initiative will significantly enhance the Department of Defense's capabilities in secure communications, positioning the Air Force at the forefront of quantum-secured information transfer.

Phase II

Phase II will focus on developing a prototype quantum repeater and memory system, validating functionality in relevant environments, and achieving TRL 4 to 6. This involves building scalable prototypes, integrating with entangled pair transmission equipment, and rigorous lab testing to meet metrics such as coherence, loss, and security. Successful outcomes will demonstrate transition readiness for development and deployment.

The main Phase II activities are named as enhancing quantum memory systems for increased coherence fidelity and extended transmission distances; integrating prototypes with existing entanglement sources and quantum communication networks; testing the quantum memory systems in simulated and real-world environments to ensure robustness and reliability; and evaluating performance through rigorous data collection and analysis to meet predefined security and operational metrics.

Note the TRL inconsistency in the source. Earlier the topic states that by the end of Phase II the target is to reach TRL 5, demonstrating the integrated system in a relevant environment. The Phase II paragraph states achieving TRL 4 to 6. Those are not the same claim. The safe course is to plan toward TRL 5 in a relevant environment, which satisfies both statements, and to describe your maturity claims in terms of what you will actually demonstrate rather than leaning on a TRL number alone.

Note also that integration with entangled pair transmission equipment and with existing entanglement sources appears in both the objective and the Phase II activities. Your Phase I architecture plan should address the interfaces to an entanglement source, since that is where the Air Force has signaled the system boundary sits.

Phase III

In Phase III, the quantum memory technology will achieve TRL 7, transitioning into secure Department of Defense communication networks and commercial QKD applications. Expected efforts include finalizing integration, extensive testing, obtaining necessary certifications, and establishing production capability. Potential Air Force customers include network and cybersecurity divisions. This addresses critical needs for secure, long-range communication solutions.

Two useful details for your commercialization section. The named Air Force customers are network and cybersecurity divisions, which gives you a concrete internal buyer to reference. And commercial QKD applications are named alongside the defense path, which supports a dual-use case built on financial, utility, and government network security markets rather than an invented one.

The reference list

The topic carries an unusually long reference list, fifteen items, spanning the foundational and the applied. Kimble's "The quantum internet" in Nature 2008. Gisin and Thew, "Quantum communication," Nature Photonics 2007. Afzelius, Simon, de Riedmatten and Gisin on multimode quantum memory based on atomic frequency combs, Physical Review A 2009. Ladd et al, "Quantum computers," Nature 2010. Bussieres et al on prospective applications of optical quantum memories, Journal of Modern Optics 2013. Van Meter, Devitt and Itoh on architecture-dependent execution time of Shor's algorithm, Physical Review A 2007. Bennett and Brassard's 1984 public key distribution and coin tossing paper, listed twice, once in the Proceedings of the IEEE International Conference on Computers, Systems and Signal Processing and once as the BB84 Protocol citation in Theoretical Computer Science with the note that this is the original QKD protocol. Knill, Laflamme and Milburn on efficient quantum computation with linear optics, Nature 2001. A 2020 Journal of Research of the National Institute of Standards and Technology paper on optical quantum memory and its applications in quantum communication systems. The Quantum Economic Development Consortium. The National Quantum Initiative at quantum.gov. Scarani et al on the security of practical quantum key distribution, Reviews of Modern Physics 2009. Pirandola et al on quantum cryptography, Nature Reviews Physics 2020. And Lucamarini, Yuan, Dynes and Shields on overcoming the rate-distance limit of quantum key distribution without quantum repeaters, Nature 2018.

That last reference is the interesting one, and worth engaging with directly. It describes twin-field QKD, an approach that extends range without quantum repeaters. Its presence in a quantum memory topic's reference list means the Air Force is aware of the repeaterless alternative. A proposal that explains why a memory-based repeater is worth pursuing given that alternative, in terms of ultimate scaling, network topology, or entanglement distribution capability beyond key exchange, is answering a question the reference list implicitly asks. Ignoring it is a missed opportunity.

The inclusion of Afzelius on atomic frequency comb multimode memory and the NIST optical quantum memory review also suggests the government's frame of reference for candidate approaches. The Shor's algorithm and linear optics computation references, by contrast, are context for the threat and for the broader quantum landscape rather than steers on approach.

Funding Allowance and Cost Structure

Award ceiling and realistic scoping

Up to $250,000 across up to 6 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The instructions add that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

For a TRL 2 to TRL 3 quantum hardware effort, six months and $250,000 is a study with supporting laboratory work, not a build. The proposals that read as credible will scope accordingly and will be specific about what existing capability they bring, since nothing meaningful in quantum memory hardware gets built from zero in two quarters.

Contract type

The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts. Awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system, since if the company intends to continue work with the Department of War an approved accounting system allows competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts.

If no exceptions are taken to an offeror's proposal, the Government may award a contract without negotiations. Therefore the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen negotiations later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The DAF will provide up to $6,500 per Phase I award, in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal.

This BAA Phase I document carries the full detailed TABA request requirements. Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases. Those activities can be undertaken in furtherance of making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

Requests for TABA funding creditable to a TABA provider must include the following or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.

If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.

A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.

For a quantum company, access to a network of scientists and engineers and intellectual property protections are the natural fits. Market validation is also worth considering given that the topic names both Air Force network and cybersecurity divisions and commercial QKD as destinations.

Cost volume requirements

Cost information should be provided by completing the Cost Volume in DSIP and including the Cost Volume Itemized Listing. The cost volume detail must be adequate to enable Air Force personnel to determine the purpose, necessity, and reasonableness of each cost element. The DSIP Cost Volume and Itemized Cost Volume Information will not count against the specified page limit, and the itemized listing may also be submitted in Volume 5 under the "Other" dropdown option.

Direct cost materials. Justify costs for materials, parts, and supplies with an itemized list containing types, quantities, prices, and where appropriate purpose. Material costs may include raw materials, parts, subassemblies, components, and manufacturing supplies. On this topic, crystals or other memory media, single photon detectors, lasers, cryogenic consumables, and optics belong here with quantities and prices.

Other direct costs. This includes but is not limited to specialized services such as machining, milling, special testing or analysis, and costs incurred in temporarily using specialized equipment. Proposals including leased hardware must include an adequate lease versus purchase justification. Cryostat time, characterization services, and specialized measurement may sit here.

Direct labor. Identify key personnel by name, if possible, or by labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a study-weighted Phase I this will be most of the budget, and the credibility of your named quantum scientists matters.

Travel. Travel costs must relate to project needs. Break out travel costs by trip, number of travelers, airfare, per diem, lodging, and similar. The number of trips required, as well as the destination and purpose of each, should be reflected. The instructions recommend budgeting at least one trip to the Air Force location managing the contract.

Subcontracts. Involvement of university or other consultants in the project's planning or research stages may be appropriate. If so, describe in detail and include information in the Cost Volume. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded from the calculation, unless otherwise approved in writing by the Contracting Officer. The SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. Support subcontract costs with copies of executed agreements that adequately describe the work to be performed, and at a minimum include a Statement of Work with a corresponding detailed Cost Volume for each planned subcontract.

This cap is the practical constraint for quantum memory work, because the field is heavily university-based. One-third of $250,000 is roughly $83,000 for all consultant fees, facility lease and usage fees, and subcontracts combined. If your approach depends on a university group's cryogenic facility and their graduate students, model the arithmetic before you commit, and note that facility usage fees count against the same cap as the subcontract itself.

Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an offeror would otherwise possess in the normal course of business, and may include items such as innovative instrumentation or automatic test equipment.

Consultants. Provide a separate agreement letter for each consultant, briefly stating what service or assistance will be provided, the number of hours required, and the hourly rate.

Performance of work requirements

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit.

Occasionally the DAF will consider deviations from this performance of work requirement. Requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove requesting applicants to proceed with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award.

Because quantum memory expertise concentrates in academic groups, this requirement will bind on a number of otherwise strong teams. If your plan is university-centric, either restructure so that two-thirds of the research or analytical effort sits inside the company, or file the pre-submission deviation request in the first week of the open period, since it must occur inside the four week window.

All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States. The awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking this approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission. Quantum research collaborations are frequently international, so if any collaborator sits abroad, address it.

Export Control, Foreign Nationals, and Personnel Disclosure

This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same Phase I release. That absence does not eliminate your obligations.

The Volume 2 Key Personnel requirements apply to every topic in this release. Identify in the Technical Volume all key personnel who will be involved in this project, including information on directly related education, experience, and citizenship. A technical resume of the principal investigator, including a list of publications if any, must be included, and only one principal investigator or project manager can be designated to a proposal at any given time. Concise technical resumes for subcontractors and consultants are also useful.

Identify all U.S. permanent residents to be involved in the project as direct employees, subcontractors, or consultants. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants. For all non-U.S. citizens, in addition to technical resumes, provide countries of origin, the type of visa or work permit under which they are performing, and an explanation of their anticipated level of involvement on this project, as appropriate. Additional information may be requested during negotiations in order to verify the foreign citizen's eligibility to participate on a contract issued as a result of this announcement.

One instruction is easy to get wrong: do not upload information such as Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying identity documents.

Quantum research groups are among the most internationally staffed in physical science, so build your key personnel section with this in mind. Note also that the foreign risk evaluation described below explicitly assesses foreign affiliations of covered individuals with entities in foreign countries of concern, including research institutions, which is directly relevant where your team members hold or held academic appointments abroad.

If you are asserting export-controlled status for your own technology, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission is a Volume 5 document, and approval will be required if the proposal is selected for award.

Proposal Structure: The Seven Volumes

Formatting, and what does not count against the page limit

The Technical Volume should include all graphics and attachments but should not include the Cover Sheet, which is completed separately as Volume 1. Ensure that all graphics are distinguishable in black and white.

The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. This differs from the DAF Direct to Phase II instructions, which require 11-point, so do not carry formatting assumptions across documents.

The Phase I Technical Volume page and slide limits identified for the topics do not include the Cover Sheet, the Cost Volume, or the Cost Volume Itemized Listing. Only the Technical Volume and any enclosures or attachments count toward the page limit. The documents required for upload into Volume 5 under "Other" do not count toward the specified limits. In the interest of equity, pages or slides in excess of the stated limits will not be reviewed.

The limit for this topic is 20 pages or slides. Because the limit is expressed as pages or slides, a slide-format technical volume is acceptable.

Twenty pages is workable here if you resist the urge to write a quantum communication tutorial. The evaluators do not need the background, and the fifteen-item reference list tells you they have it. Spend the pages on your specific memory approach, your predicted coherence, loss, and noise, your architecture plan, and your integration path.

Fraud, Waste and Abuse training must be completed prior to proposal submission, and DSIP will indicate completion of the Volume 6 requirement once the training is complete and certified. Note the criminal warning the instructions carry: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released.

Volume 2, Technical Volume

The Phase I technical volume shall contain the required elements below. These instructions supplement the FY26 SBIR BAA, and in addition to the requirements found in the BAA, applicants are required to provide the following information in Volume 2.

Key personnel, as described above.

Phase I Statement of Work outline. The DAF uses the work plan outline as the initial draft of the Phase I Statement of Work. Therefore, do not include proprietary information in the work plan outline. To do so will necessitate a request for revision, if selected, and may delay award.

That instruction matters. Your work plan outline becomes the contract's statement of work, so proprietary content there either ends up in a contract document or triggers a revision cycle that delays award. Keep the detailed physics in the technical volume body and keep the outline at the task and deliverable level.

Include a work plan outline in the following format. Scope, listing the effort's major requirements and specifications. Task Outline, providing a brief outline of the work to be accomplished during the Phase I effort. Milestone Schedule. Deliverables. Progress reports. Final report with SF 298.

The SF 298 is the Report Documentation Page that accompanies a technical report. It is named in the required outline, so plan for it rather than discovering it at closeout.

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the FY26 SBIR BAA for full details. Information contained in the CCR will not be considered by the Air Force during proposal evaluations.

Volume 5, Supporting Documents

The following documents may be required if applicable to your proposal. DD Form 2345, for proposals submitted under export-controlled topics. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the FY26 SBIR BAA. Technical Data Rights Assertions, if asserting data rights restrictions.

Technical Data Rights Assertions deserve attention on a quantum topic where your memory material, your protocol implementation, or your control approach may be background intellectual property developed with private or prior non-federal funding.

The detailed TABA request, if you are requesting TABA, also goes in Volume 5. Documents uploaded into Volume 5 under "Other" do not count toward the page limit, and the Cost Volume Itemized Listing may also be submitted there.

Volume 6, Fraud, Waste, and Abuse Training

Material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the webform in Volume 7 of the DSIP proposal submission. The disclosures will not be accepted as a PDF Supporting Document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW SBIR Program BAA.

How Your Proposal Will Be Evaluated

The criteria live in the BAA

Proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. The DAF is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals.

This BAA document does not reproduce the evaluation criteria, unlike the DAF Release 6 CSO Phase I instructions which restate Criteria A, B, and C with their relative importance. Read the criteria in the DoW FY26 SBIR BAA before you begin writing, and do not assume the CSO criteria carry over.

Foreign risk evaluation

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of War, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

Employee analysis and foreign affiliations warrant particular attention on this topic. Quantum information science is a globally connected field, and academic affiliations abroad are common among exactly the people you would want as key personnel. Know your team's affiliation history before you propose.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.

If an award is denied on these grounds, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv). Note that the malign foreign talent recruitment program provision and the foreign research institution affiliation provision are both mandatory denials, not discretionary judgments.

Venture capital, hedge fund, and private equity ownership

Small business concerns that are owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

This is worth stating plainly because the DAF Release 6 BAA Direct to Phase II instructions say the opposite for that document's topic. Within the same BAA cycle, the Phase I instructions permit venture-backed firms and the Direct to Phase II instructions do not. The Phase I instructions govern this topic, so venture-backed quantum companies are eligible here. Check eligibility per document rather than assuming a cycle-wide rule, and consider raising the discrepancy with the DAF SBIR/STTR One Help Desk if you are pursuing both.

Support contractors, status, feedback, and protests

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors, which may include but are not limited to TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space and Missiles Centers may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the AF SBIR/STTR Contracting Officer with concerns regarding the use of support contractors.

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions.

The Air Force anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the BAA Contracting Officer for proposal status before that time.

Refer to the DoW SBIR Program BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(a) and FAR 52.233-2, protests should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer. The DAF uses its best efforts to resolve concerns raised by interested parties at the contracting officer level through open and frank discussions, and for agency protests the DAF provides for inexpensive, informal, procedurally simple, and expeditious resolution of protests.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

How Phase II works

DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the conclusion of the period of performance. This decision will be based on the awardee's technical progress, as determined by a DAF Technical Point of Contact review using the Phase II review criteria.

Phase II is the demonstration of the technology found feasible in Phase I. Only Phase I awardees are eligible to submit a Phase II proposal. All Phase I awardees will be sent a notification with the Phase II proposal submittal date and detailed preparation instructions. If the physical or email addresses or firm points of contact have changed since submission of the Phase I proposal, correct information shall be sent to the DAF SBIR/STTR One Help Desk. Phase II dollar values, performance periods, and proposal content will be specified in the Phase II request for proposal. Only one Phase II proposal may be submitted for each Phase I award.

The DAF reserves the right to modify the Phase II submission requirements, and should the requirements change, all Phase I awardees will be notified. The DAF also reserves the right to change any administrative procedures that will improve management of the DAF SBIR/STTR Program at any time.

Because the Phase II request can arrive while Phase I is still running and is based on demonstrated technical progress, producing real results early rather than holding everything for the final report is worth planning for on a six month award.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 6 months from award

A working backward plan

Before September 23. Read the evaluation criteria in the DoW FY26 SBIR BAA, since they are not in the component instructions. Work through the reference list, particularly the Lucamarini paper on overcoming the rate-distance limit without repeaters, and form your argument for why a memory-based repeater is the right investment anyway. Settle your memory approach and the predicted coherence, loss, and noise figures. Decide honestly what laboratory work six months supports on capability you already have. Model the two-thirds in-house requirement and the one-third outside cost cap against any university involvement, and if it does not close, file the pre-submission Performance of Work deviation request in the first week of the open period. Map your team's foreign affiliations and any international collaborations. Inventory background intellectual property for Technical Data Rights Assertions. Complete Volume 6 training and verify SAM and DSIP alignment. Send clarifying questions to the DAF SBIR/STTR One Help Desk, which encourages early inquiries, and consider asking about the TRL 5 versus TRL 4 to 6 inconsistency in the Phase II language.

September 23 through October 3. Draft the technical volume against the 20 page limit. Lead with your scientific approach and the conceptual design, then the coherence, loss, and noise projections, then the architecture plan for the Phase II lab-based test bench capable of end-to-end quantum information transport, then the integration path to entanglement sources. Skip the tutorial. Write the work plan outline separately, keeping proprietary detail out of it since it becomes the Statement of Work. Build the milestone schedule early since the TABA task list must track to it.

October 4 through October 12. Build the cost volume and itemized listing, neither of which counts against the page limit. Itemize memory media, detectors, lasers, cryogenic consumables, and optics. Check the one-third cap, remembering that facility usage fees count against it alongside subcontracts. Get separate agreement letters from each consultant and executed agreements with statements of work and detailed cost volumes for each planned subcontract. Budget at least one trip to the Air Force location managing the contract. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5 with Technical Data Rights Assertions and any applicable DD Form 2345, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 10-point minimum type, one-inch margins, graphics distinguishable in black and white, no PII uploaded to DSIP, no proprietary content in the technical abstract or the work plan outline.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BZ06-NV035?

‍ ‍

DAF26BZ06-NV035 is a Department of the Air Force SBIR Phase I topic titled "Quantum Memory for Secure Communication," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks advanced quantum memory systems that enable secure communication within quantum networks, specifically to build quantum repeaters that extend the range and fidelity of Quantum Key Distribution.

‍ ‍

How much funding is available under DAF26BZ06-NV035?

‍ ‍

Up to $250,000 for a period of performance up to 6 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $6,500 in Technical and Business Assistance is available per Phase I award, in addition to the per-topic total.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

What problem is this topic solving?

‍ ‍

Signal loss over long distances in Quantum Key Distribution systems, which the topic says prevents widespread implementation. Quantum memory enables quantum repeaters, and repeaters extend the range and fidelity of quantum signals so that QKD works over long distances.

‍ ‍

What technology readiness level does Phase I target?

‍ ‍

The technology is at TRL 2 at project start, focusing on application concept formulation. Phase I success is demonstrating TRL 3 by drafting a feasibility report and a detailed architecture plan for a Phase II prototype of a lab-based test bench capable of end-to-end quantum information transport.

‍ ‍

What is the actual Phase I deliverable?

‍ ‍

The assessed output is a feasibility report plus a detailed architecture plan at TRL 3, supported by a detailed scientific approach and a conceptual design for a functional quantum memory prototype showing its capabilities and potential advantages in both lab and simulated environments. The topic also describes designing quantum memory materials, developing prototypes, and conducting laboratory validation, but six months and $250,000 will not support meaningful fabrication from scratch, so the credible plan pairs the design and analysis deliverables with whatever laboratory work you can perform on existing capability.

‍ ‍

Why do the two Phase I descriptions differ?

‍ ‍

The topic describes Phase I twice. One passage lists designing and fabricating quantum memory materials, developing prototypes, and laboratory validation. The other sets the assessed criterion at a feasibility report and architecture plan demonstrating TRL 3. Read them together, be explicit in your proposal about which activities you will actually perform in six months, and do not promise fabrication and validation cycles your schedule cannot hold.

‍ ‍

What metrics should I address?

‍ ‍

Coherence, loss, and noise are named as the defined metrics for laboratory validation in Phase I. Phase II adds security to that list. Give predicted values for coherence, loss, and noise for your approach and say how you will measure each.

‍ ‍

What are the minimum deliverables?

‍ ‍

The topic lists detailed technical reports, functional quantum memory prototypes, performance evaluation data, and an integration roadmap detailing steps for transition into operational use. Note this is framed as deliverables for the project rather than for Phase I alone, consistent with the functional prototype appearing in the Phase II description.

‍ ‍

What happens in Phase II?

‍ ‍

Developing a prototype quantum repeater and memory system, validating functionality in relevant environments, and achieving TRL 4 to 6. That involves building scalable prototypes, integrating with entangled pair transmission equipment, and rigorous lab testing against coherence, loss, and security metrics. Named activities include enhancing coherence fidelity and extended transmission distances, integrating with existing entanglement sources and quantum communication networks, testing in simulated and real-world environments, and rigorous data collection against predefined security and operational metrics.

‍ ‍

Is the Phase II TRL target 5 or 4 to 6?

‍ ‍

The topic says both in different places. Earlier it states that by the end of Phase II the target is to reach TRL 5, demonstrating the integrated system in a relevant environment. The Phase II paragraph states achieving TRL 4 to 6. Planning toward TRL 5 in a relevant environment satisfies both statements. Describe maturity in terms of what you will demonstrate rather than relying on a TRL number alone, and consider asking the One Help Desk during the open period.

‍ ‍

What happens in Phase III?

‍ ‍

The quantum memory technology will achieve TRL 7, transitioning into secure Department of Defense communication networks and commercial QKD applications. Expected efforts include finalizing integration, extensive testing, obtaining necessary certifications, and establishing production capability. Potential Air Force customers include network and cybersecurity divisions.

‍ ‍

Does this topic care about integration with entanglement sources?

‍ ‍

Yes, and it says so twice. The objective mentions seamless integration with existing and future quantum entanglement sources and networks, and the Phase II activities name integrating prototypes with existing entanglement sources and quantum communication networks and with entangled pair transmission equipment. Your Phase I architecture plan should address those interfaces.

‍ ‍

The reference list includes a paper on QKD without quantum repeaters. Should I address that?

‍ ‍

Yes. The Lucamarini, Yuan, Dynes and Shields 2018 Nature paper on overcoming the rate-distance limit of quantum key distribution without quantum repeaters describes an approach that extends range without memory-based repeaters. Its presence in a quantum memory topic's reference list means the government is aware of the alternative. A proposal that explains why a memory-based repeater is worth pursuing anyway, on grounds of ultimate scaling, network topology, or entanglement distribution beyond key exchange, is answering a question the reference list implicitly poses.

‍ ‍

Is this topic export controlled?

‍ ‍

This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same release. Your general disclosure obligations still apply, including identifying all U.S. permanent residents and all non-U.S. citizens involved with countries of origin, visa or work permit type, and anticipated level of involvement. If you are asserting export-controlled status for your own technology, DD Form 2345 is a Volume 5 document.

‍ ‍

What identity information should I not upload?

‍ ‍

Do not upload Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, meaning countries of origin, visa or work permit type, and level of involvement, not the underlying documents.

‍ ‍

How long can my technical volume be?

‍ ‍

20 pages or slides. The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. The Cover Sheet, Cost Volume, and Cost Volume Itemized Listing do not count toward the limit; only the Technical Volume and any enclosures or attachments do. Documents uploaded into Volume 5 under "Other" do not count either. Pages or slides in excess of the stated limit will not be reviewed.

‍ ‍

How much of the work must my company perform?

‍ ‍

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility lease or usage fees, and other subcontract or purchase agreements together may not exceed one-third of the total contract price or cost with profit excluded, unless the Contracting Officer approves otherwise in writing. On a $250,000 award that is roughly $83,000 for all outside costs combined.

‍ ‍

My approach depends on a university lab. Is that a problem?

‍ ‍

Potentially, and it is the constraint most likely to bind on this topic since quantum memory expertise concentrates in academic groups. Note that facility usage fees count against the same one-third cap as the subcontract itself. Either restructure so two-thirds of the research or analytical effort sits inside the company, or file a Performance of Work deviation request, which must be made prior to submission during the topic open period and again as part of the initial proposal submission.

‍ ‍

How will my proposal be evaluated?

‍ ‍

The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. Read those criteria in the DoW FY26 SBIR BAA before writing, and do not assume the Criteria A, B, and C structure from the DAF CSO instructions applies.

‍ ‍

Are venture capital backed companies eligible?

‍ ‍

Yes, for this topic. The BAA Phase I instructions state that firms owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible for DAF topics. Note that the DAF Release 6 BAA Direct to Phase II instructions state the opposite for that document's topic, so verify eligibility per document rather than per cycle.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state information contained in the CCR will not be considered by the Air Force during proposal evaluations.

‍ ‍

Why does the work plan outline matter so much?

‍ ‍

Because the DAF uses it as the initial draft of the Phase I Statement of Work. The instructions direct you not to include proprietary information in it, warning that doing so will necessitate a request for revision if selected and may delay award. Keep the detailed physics in the technical volume body.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $6,500 per Phase I award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. This BAA document carries the full detailed request requirements: provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, with the task milestone list tracking to your milestone payment schedule. The detailed request must be in Volume 5, and requests specifying only a value in Volume 3 will not be considered.

‍ ‍

How do I get to Phase II?

‍ ‍

DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the period of performance concludes, based on the awardee's technical progress as determined by a DAF Technical Point of Contact review. Only Phase I awardees are eligible, all Phase I awardees receive a notification with the submittal date and detailed instructions, and only one Phase II proposal may be submitted for each Phase I award.

‍ ‍

When will I hear about selection?

‍ ‍

The Air Force anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email.

‍ ‍

Who do I contact with questions?

‍ ‍

The AF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the DoW FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR BAA Address Change."

‍ ‍

Positioning Advice for Companies Considering This Topic

‍ ‍

Scope to what six months and TRL 3 actually mean. The single most common way to lose this topic will be promising a working quantum memory prototype. The assessed deliverable is a feasibility report and an architecture plan. Write a proposal that delivers those excellently, plus laboratory results on capability you already possess, and be explicit that this is the plan rather than leaving the evaluator to wonder whether you understand the constraint.

‍ ‍

Name your memory modality and defend it. Atomic ensemble, rare-earth doped crystal, solid-state defect center, or another approach, the choice drives everything about coherence time, bandwidth, wavelength compatibility, and operating temperature. Say which and why, with numbers.

‍ ‍

Give the coherence, loss, and noise triple explicitly. Those three are named as the defined metrics. A table with predicted values, measurement methods, and which you consider highest risk earns its space.

‍ ‍

Address the telecom wavelength question. QKD infrastructure lives in the telecom bands. If your memory operates elsewhere, the frequency conversion problem and its loss penalty is part of your architecture, and a proposal that omits it looks incomplete to anyone who works in this field.

‍ ‍

Engage the repeaterless alternative. The reference list includes the twin-field QKD paper. Explain why memory-based repeaters remain the right long-term investment, whether on scaling, on network topology, or on the entanglement distribution capability that key exchange alone does not provide.

‍ ‍

Build the architecture plan as a real deliverable. The Phase I criterion names a detailed architecture plan for a Phase II prototype of a lab-based test bench capable of end-to-end quantum information transport. That phrase is a specification. Show the test bench: sources, memory, channel, detection, synchronization, and the measurements that establish end-to-end transport.

‍ ‍

Design for the entanglement source interface. Integration with existing and future entanglement sources appears in both the objective and Phase II. Treat the source as an external interface with defined requirements rather than as something to be figured out later.

‍ ‍

Solve the university dependency problem before you write. Two-thirds of the research or analytical effort in house, and all outside costs including facility usage fees under one-third of contract price, is the requirement most likely to disqualify an otherwise strong academic-adjacent team. Either restructure or file the deviation request in the first week of the open period.

‍ ‍

Know your team's foreign affiliations. Foreign affiliation with a research institution in a country of concern is a mandatory denial, not a discretionary judgment, and quantum information science is an unusually international field. This is a diligence item, not a paperwork item.

‍ ‍

Use the named Phase III customers. Air Force network and cybersecurity divisions are named as potential customers, and commercial QKD applications are named alongside them. That gives you both a defense buyer to reference and a credible commercial market in financial, utility, and government network security, without having to invent one.

‍ ‍

Do not write the tutorial. Fifteen references tell you the evaluators know the field. Spend all twenty pages on your approach, your numbers, and your plan.

DAF SBIR DAF26BZ06-NV034: Low Noise and Low-SWaP High-Repetition Rate Mode-Locked Lasers for High-Speed Photonics

Quick Answer

DAF26BZ06-NV034 is a Department of the Air Force SBIR Phase I topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force wants a compact, low size, weight, and power mode-locked laser operating in the near-infrared to short-wave infrared at repetition rates between 6 and 12 GHz. The reason is a specific gap in the market: the Air Force states that a commercially available stabilized low-noise laser in the 6 to 12 GHz range is currently lacking, and it needs one as a low-noise bridge between the optical and microwave domains. Awards are up to $250,000 for a period of performance up to 6 months, with a 20 page or slide technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Phase I is a proof-of-concept and feasibility effort at breadboard level, and the Air Force is explicit that supporting electronics can use benchtop solutions at this stage. It is also explicit about something else that shapes your cost volume: no government materials, equipment, data, or facilities will be provided. Everything you need, you bring or buy.

Topic At a Glance

Topic number: DAF26BZ06-NV034

Title: Low Noise and Low-SWaP High-Repetition Rate Mode-Locked Lasers for High-Speed Photonics

Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Phase I Proposal Submission Instructions

Program type: Phase I

Award maximum value: $250,000

Award maximum duration: 6 months

Technical volume page limit: 20 pages or slides

OUSD (R&E) Critical Technology Area: Quantum and Battlefield Dominance (Q-BID)

Component Technology Priority Areas: Integrated Sensing and Cyber; Microelectronics; Advanced Materials

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Government-furnished property: none. No government materials, equipment, data, or facilities will be provided

Minimum work performed in house: two-thirds of the research or analytical effort

Subcontract and consultant cap: one-third of total contract price, profit excluded

Technical and Business Assistance: up to $6,500 per Phase I award

Type size: no smaller than 10-point

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords, as listed in the topic: CO2 mode-locked lasers, frequency combs, semiconductor lasers, infrared, InP, GaSb, MOCVD, MBE

Note on the deadline time. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the proposal submission deadline date and time rather than restating it. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP topic posting and do not plan around an end-of-day deadline.

Note on the keyword list. The topic's keyword list opens with CO2 mode-locked lasers, which sits oddly against a topic body entirely concerned with mode-locked semiconductor lasers in the near-infrared and short-wave infrared, and against the InP, GaSb, MOCVD, and MBE keywords that follow. Read the topic body as governing and treat that first keyword as likely carried over from elsewhere.

The Requirements, Stated Plainly

These are the numbers your proposal will be measured against. Address each one explicitly.

Repetition rate: between 6 and 12 GHz.

Average power: 50 mW or greater.

Pulse width: a picosecond or less.

Spectral range: near-infrared to short-wave infrared, with the O-band and C-band called out for compatibility with photonic integrated circuits and commercial off-the-shelf components.

Pumping: optically or electrically pumped, your choice.

Stabilization: the repetition rate must be stabilized with custom or commercial off-the-shelf electronics.

Noise and stability: low relative intensity noise and long-term power stability.

SWaP: the overall size, weight, and power of the laser itself and the necessary electronics must be minimized, with differentiating goals highlighted across Phase I, Phase II, and Phase III.

The last item is worth reading carefully. The Air Force is asking you to identify what your SWaP differentiators are at each phase, which means your proposal should say what you will demonstrate about SWaP in Phase I at breadboard level, what changes in Phase II when the electronics become modular, and what the packaged Phase III article looks like. A proposal that treats SWaP as a Phase III concern has not answered the question.

What the Air Force Is Actually Looking For

Why semiconductor mode-locking, and why this frequency band

The technical argument in the topic is specific and worth following closely, because your proposal needs to engage with it rather than restate it.

Mode-locked semiconductor lasers can support high repetition rates up to 100 GHz due to high gain and fast gain recovery, unlike fiber lasers or doped dielectric gain medium lasers. That is the reason the Air Force is pointed at semiconductor gain media rather than fiber or crystal.

Harmonic mode-locking or pulse interleaving can be used to increase the repetition rate into the 4 to 10 GHz range, but the Air Force states that each of these techniques lacks a pure microwave signal. This is the crux of the topic. You can get to the right repetition rate by those routes, but you do not get a clean microwave tone out of it, and the clean tone is the point.

High repetition rate semiconductor lasers can provide the low-noise microwave signal due to the fundamental mode-locking that can be achieved in the gigahertz range with a semiconductor saturable absorber mirror. Fundamental mode-locking, as opposed to harmonic mode-locking or interleaving, is what delivers spectral purity.

That offers a compact, efficient, low-noise, high-speed option for connecting the optical and microwave domain, enabling integration with photonic integrated circuits or commercial off-the-shelf components.

And then the market statement: currently a commercially available stabilized low-noise laser in the 6 to 12 GHz range is lacking.

So the topic is not asking for an incremental improvement to an existing product line. It is asking you to fill a stated hole in the commercial supply, using fundamental mode-locking in a semiconductor gain medium, in a form factor and noise regime that makes it useful as a microwave source.

The approach the Air Force points toward

The topic describes a promising approach in enough detail that it functions as a technical steer. A technique enabling a two-element cavity design for high-repetition rate lasers has been demonstrated in the first two cited references.

By including the semiconductor saturable absorber with a dielectric output coupler, the overall cavity length can be made shorter for high repetition rates without complex gain structures and without high curvature cavity optics. Shorter cavity means higher repetition rate, and the two-element approach gets there without the complications that usually accompany it.

In the near-infrared this was demonstrated on a curved output coupler with a bonded quantum well saturable absorber, resulting in a hybrid SESAM, achieving pulse widths of about 400 femtoseconds at repetition rates from 2.8 to 8 GHz.

In the visible spectrum a similar technique was applied with a flat dielectric mirror, constructing what was coined as a membrane saturable absorber mirror, or MESAM. Because the output coupler and saturable absorber were independent, the repetition rate remained low but still achieved picosecond pulses.

Integrating these elements via direct membrane bonding of the saturable absorber allows higher repetition rates, and has been demonstrated for high-power applications in the third cited reference.

It is envisioned that this approach, or other proposed solutions, can be extended throughout the near-infrared and into the short-wave infrared, particularly in the O-band and C-band for compatibility with photonic integrated circuits and commercial off-the-shelf components.

Two things follow for your proposal. First, the phrase "or other proposed solutions" leaves the door open, so you are not obligated to pursue direct membrane bonding of a saturable absorber. Second, if you propose something else, you should engage with why the referenced route is insufficient or why yours is better, because the Air Force has told you what it considers promising. Silence on that point reads as unfamiliarity.

Phase I

Develop a proof-of-concept for the necessary components and conduct a feasibility study to demonstrate a breadboard 6 to 12 GHz mode-locked laser with picosecond or shorter pulse widths.

Component development is to include the semiconductor gain medium, the saturable absorber or other mode-locking element, and the necessary fabrication steps for the components.

Potential metrics include average power, pulse energy, pulse width, long-term power stability, spectral bandwidth, repetition rate tuning, and relative intensity noise.

Supporting electronics can utilize benchtop solutions.

Read those four paragraphs together and the Phase I scope becomes clear. You are building components and a breadboard, not a product. Gain medium, mode-locking element, and the fabrication process for both are named as in-scope component development, which means epitaxial growth and processing work belongs in the plan. The metric list gives you your data table. And the permission to use benchtop supporting electronics removes an entire category of work from Phase I, which matters a great deal in a six month, $250,000 effort. Do not spend Phase I money miniaturizing drive electronics.

Note also the phrase "repetition rate tuning" in the metric list. Tunability is not in the hard requirements but appears as a potential metric, so characterizing your tuning range is a way to add value without scope creep.

Phase II

Conduct research to transition the validated Phase I design into prototypes for two fiber-coupled brassboards with full stabilization and low-noise, low-SWaP implementation of the near-infrared to short-wave infrared mode-locked laser. Aside from an external DC power supply, all electronics should be modular with the ability to integrate in Phase III.

Three concrete details there. Two units, not one. Fiber-coupled, which is a packaging and alignment problem distinct from the laser physics. And full stabilization with modular electronics, meaning the benchtop permission from Phase I expires. Your Phase I proposal should show that you know where the Phase II electronics work sits even though you are not doing it yet, because the Air Force asked for SWaP differentiating goals across all three phases.

Phase III

Develop a fully packaged low-noise, high-repetition rate mode-locked laser operating in the near-infrared to short-wave infrared spectral range, suitable for system integration and commercial sales.

The commercial framing is explicit here, and it is unusually favorable. The Air Force has already told you that a stabilized low-noise laser in this band is not commercially available, which is your market statement handed to you. Photonic integrated circuit integration, microwave photonics, optical frequency comb applications, high-speed analog-to-digital conversion, and precision timing distribution are all natural adjacent markets for a clean 6 to 12 GHz optical pulse source.

The cited references

Three papers, all worth reading before you write.

Gibson, R., et al, "Hybrid SESAMs for high-repetition rate mode-locked VECSELs," SPIE Proceedings, VECSELs XII, Volume 12404, p. 1240407, 2023.

Cutuk, A., Grossmann, M., Jetter, M. and Michler, P., "Membrane saturable absorber mirror (MESAM) in a red-emitting VECSEL for the generation of stable ultrashort pulses," Optics Express, 31(4), pp. 6796-6804, 2023.

Diebold, A., et al, "Optimized SESAMs for kilowatt-level ultrafast lasers," Optics Express, 24(10), pp. 10512-10526, 2016.

The reference set points toward vertical external cavity surface emitting laser architectures with engineered saturable absorbers. Combined with the InP, GaSb, MOCVD, and MBE keywords, the picture is of a topic aimed at companies with semiconductor epitaxy and processing capability rather than at systems integrators buying components.

Funding Allowance and Cost Structure

Award ceiling and what six months buys

Up to $250,000 across up to 6 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The instructions add that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

Six months is the tighter constraint for this particular topic, because semiconductor epitaxy has an irreducible cycle time. If your plan requires a growth run, characterization, a design iteration, and a second growth run, be honest about whether that fits and say how you have de-risked it. Proposals that assume a first-pass success on novel epitaxy invite skepticism. Existing wafers, existing material, or a partner with ready capacity are all ways to make the schedule credible, subject to the work-performance limits below.

No government-furnished anything

The topic states plainly that no government materials, equipment, data, or facilities will be provided. That has two consequences. Your cost volume has to carry every wafer, every characterization tool hour, and every piece of test equipment you need. And you cannot propose a plan that depends on access to an Air Force Research Laboratory facility or on government-furnished material.

Contract type

The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts. Awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system, since if the company intends to continue work with the Department of War an approved accounting system allows competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts.

If no exceptions are taken to an offeror's proposal, the Government may award a contract without negotiations. Therefore the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen negotiations later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The DAF will provide up to $6,500 per Phase I award, and this total is in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal.

Note that this BAA Phase I document carries the full detailed TABA request requirements, which the DAF CSO Phase I instructions did not. Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases. Those activities can be undertaken in furtherance of making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

Requests for TABA funding creditable to a TABA provider must include the following information or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.

If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.

A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.

For a photonics company, intellectual property protections and market validation are the obvious candidates. Given that the Air Force has stated the commercial gap explicitly, market validation work that quantifies that gap has value beyond the proposal.

Cost volume requirements

Cost information should be provided by completing the Cost Volume in DSIP and including the Cost Volume Itemized Listing. The cost volume detail must be adequate to enable Air Force personnel to determine the purpose, necessity, and reasonableness of each cost element. The DSIP Cost Volume and Itemized Cost Volume Information will not count against the specified page limit, and the itemized listing may also be submitted in Volume 5 under the "Other" dropdown option.

Direct cost materials. Justify costs for materials, parts, and supplies with an itemized list containing types, quantities, prices, and where appropriate purpose. Material costs may include such items as raw materials, parts, subassemblies, components, and manufacturing supplies. On this topic, substrates, epitaxial material, dielectric coatings, and optics belong here with quantities and prices.

Other direct costs. This category includes but is not limited to specialized services such as machining, milling, special testing or analysis, and costs incurred in temporarily using specialized equipment. Proposals including leased hardware must include an adequate lease versus purchase justification. Outside epitaxial growth runs, if structured as a service rather than a subcontract, and specialized characterization such as noise measurement or autocorrelation may sit here. Be deliberate about whether a growth run is a service, a subcontract, or a purchase, since the classification affects your one-third cap arithmetic.

Direct labor. Identify key personnel by name, if possible, or by labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable.

Travel. Travel costs must relate to project needs. Break out travel costs by trip, number of travelers, airfare, per diem, lodging, and similar. The number of trips required, as well as the destination and purpose of each, should be reflected. The instructions recommend budgeting at least one trip to the Air Force location managing the contract.

Subcontracts. Involvement of university or other consultants in the project's planning or research stages may be appropriate. If so, describe in detail and include information in the Cost Volume. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded from the calculation, unless otherwise approved in writing by the Contracting Officer. The SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. Support subcontract costs with copies of executed agreements that adequately describe the work to be performed, and at a minimum include a Statement of Work with a corresponding detailed Cost Volume for each planned subcontract.

On a $250,000 award, one-third is roughly $83,000 for all consultant fees, facility lease and usage fees, and subcontract or purchase agreements combined. For a topic that may require outside epitaxy or outside fabrication, that is a real constraint. Model it before you settle on your approach.

Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an offeror would otherwise possess in the normal course of business, and may include items such as innovative instrumentation or automatic test equipment.

Consultants. Provide a separate agreement letter for each consultant, briefly stating what service or assistance will be provided, the number of hours required, and the hourly rate.

Performance of work requirements

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit.

Occasionally the DAF will consider deviations from this performance of work requirement. Requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove requesting applicants to proceed with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award.

For a semiconductor laser topic this is the constraint most likely to bind. If your plan sends epitaxy to a foundry or fabrication to a university cleanroom, run the numbers early. Two-thirds of the research or analytical effort performed by you, plus all outside costs under one-third of contract price, is a tight envelope for a materials-heavy effort. If you cannot meet it, file the pre-submission deviation request in the first week of the open period, since it must happen inside the four week window.

All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States. The awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking this approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission. Compound semiconductor epitaxy and processing capacity is globally distributed, so if any part of your supply chain is offshore, address it.

Export Control and Foreign Nationals

The technology within this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including export of sensitive technical data, and the EAR 15 CFR Parts 730-774, which controls dual use items.

Of the three topics in this Phase I release, this is the only one carrying a topic-level export control restriction. NV035 and NV036 do not include this paragraph. That does not remove the general disclosure obligations from those topics, but it does mean this topic specifically flags export-controlled technical data.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by the foreign nationals in accordance with section 3.5 of the Announcement. Offerors are advised that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

The Volume 2 Key Personnel requirements reinforce this. You must identify all U.S. permanent residents to be involved in the project as direct employees, subcontractors, or consultants, and identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants. For all non-U.S. citizens, in addition to technical resumes, provide countries of origin, the type of visa or work permit under which they are performing, and an explanation of their anticipated level of involvement on this project, as appropriate. Additional information may be requested during negotiations in order to verify the foreign citizen's eligibility to participate on a contract issued as a result of this announcement.

One instruction here is easy to get wrong and worth calling out. The topic states plainly: do not upload information such as Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying identity documents.

Photonics and compound semiconductor groups are frequently internationally staffed, so resolve who can work on what before you build your key personnel section.

If you are asserting export-controlled status, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission must be included in Volume 5. The form, instructions, and FAQs are available at the United States and Canada Joint Certification Program website. DD Form 2345 approval will be required if the proposal is selected for award.

Proposal Structure: The Seven Volumes

Formatting, and what does not count against the page limit

The Technical Volume should include all graphics and attachments but should not include the Cover Sheet, which is completed separately as Volume 1. Ensure that all graphics are distinguishable in black and white, which matters on a topic where you will want to show spectra, autocorrelation traces, and noise plots.

The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. Note that this differs from the DAF Direct to Phase II instructions, which require 11-point.

The Phase I Technical Volume page and slide limits identified for the topics do not include the Cover Sheet, the Cost Volume, or the Cost Volume Itemized Listing. Only the Technical Volume and any enclosures or attachments count toward the page limit. The documents required for upload into Volume 5 under "Other" do not count toward the specified limits. In the interest of equity, pages or slides in excess of the stated limits will not be reviewed.

The limit for this topic is 20 pages or slides, per the topic index. Because the limit is expressed as pages or slides, a slide-format technical volume is acceptable, and many hardware teams find slides more efficient for conveying device structure and measured data within a tight limit.

Fraud, Waste and Abuse training must be completed prior to proposal submission, and DSIP will indicate completion of the Volume 6 requirement once the training is complete and certified.

Note the criminal warning the instructions carry: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released. On a topic where your device structure may be your core intellectual property, be deliberate about abstract content.

Volume 2, Technical Volume

The Phase I technical volume shall contain the required elements below. These instructions supplement the FY26 SBIR BAA, and in addition to the requirements found in the BAA, applicants are required to provide the following information in Volume 2.

Key personnel. Identify in the Technical Volume all key personnel who will be involved in this project, including information on directly related education, experience, and citizenship. A technical resume of the principal investigator, including a list of publications if any, must be included. Only one principal investigator or project manager can be designated to a proposal at any given time. Concise technical resumes for subcontractors and consultants, if any, are also useful. Identify all U.S. permanent residents to be involved in the project as direct employees, subcontractors, or consultants. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for all non-U.S. citizens, in addition to technical resumes, provide countries of origin, the type of visa or work permit under which they are performing, and an explanation of their anticipated level of involvement on this project, as appropriate. Do not upload Permanent Resident Cards, birth certificates, Social Security Numbers, or other PII to DSIP.

Phase I Statement of Work outline. The DAF uses the work plan outline as the initial draft of the Phase I Statement of Work. Therefore, do not include proprietary information in the work plan outline. To do so will necessitate a request for revision, if selected, and may delay award.

That is a meaningful instruction. Your work plan outline becomes the contract's statement of work, so anything proprietary in it either gets published in a contract document or triggers a revision cycle that delays your award. Write the technical detail in the body of the technical volume and keep the work plan outline at the task and deliverable level.

Include a work plan outline in the following format. Scope, listing the effort's major requirements and specifications. Task Outline, providing a brief outline of the work to be accomplished during the Phase I effort. Milestone Schedule. Deliverables. Progress reports. Final report with SF 298.

The SF 298 is the Report Documentation Page that accompanies a technical report. Naming it in the required outline means your final report needs it, so plan for it rather than discovering it at closeout.

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the FY26 SBIR BAA for full details on this requirement. Information contained in the CCR will not be considered by the Air Force during proposal evaluations. Complete it for compliance and do not treat it as a scoring opportunity.

Volume 5, Supporting Documents

The following documents may be required if applicable to your proposal. DD Form 2345, which applies to this export-controlled topic. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the FY26 SBIR BAA. Technical Data Rights Assertions, if asserting data rights restrictions.

On a semiconductor laser topic, Technical Data Rights Assertions deserve real attention. Your epitaxial structure, your saturable absorber design, and your bonding process are likely background intellectual property developed with private investment, and this is the mechanism for distinguishing them from what you develop under the award.

The detailed TABA request, if you are requesting TABA, also goes in Volume 5. Note that documents required for upload into Volume 5 under "Other" do not count toward the page limit, and the Cost Volume Itemized Listing may also be submitted there.

Volume 6, Fraud, Waste, and Abuse Training

Material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the webform in Volume 7 of the DSIP proposal submission. The disclosures will not be accepted as a PDF Supporting Document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW SBIR Program BAA.

How Your Proposal Will Be Evaluated

The criteria are in the BAA, not in this document

Proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. The DAF is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Any per-award or per-topic funding caps are budgetary estimates only, and more or less funding may become available. Funding decisions are made with complete disregard to the other awards under the same topic.

That is all this document says about criteria. Unlike the DAF Release 6 CSO Phase I instructions, which restate Criteria A, B, and C with their relative importance, this BAA document does not reproduce them. You must read the evaluation criteria in the DoW FY26 SBIR BAA to know how your proposal will be scored, and you should not assume the CSO criteria carry over. Do this before you start writing, because the criteria determine your emphasis.

Foreign risk evaluation

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of War, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

Patent analysis and technology licensing arrangements both deserve attention on this topic. Compound semiconductor laser intellectual property is internationally dense, and licensing or cross-licensing relationships are common. Map yours before you propose.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.

If the DAF denies an award under 15 U.S.C. 638(g)(16) or 638(o)(20), or upon determining the concern has a security risk described in that paragraph, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv).

For a compound semiconductor effort, audit your substrate, epitaxy, and optics supply chain against those eight lists before you propose. Substrate and coating supply in particular has significant offshore concentration.

Venture capital, hedge fund, and private equity ownership

Small business concerns that are owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

This is worth stating explicitly because the DAF Release 6 BAA Direct to Phase II instructions say the opposite, stating that such firms are not eligible. Within the same BAA cycle, the Phase I instructions permit venture-backed firms and the Direct to Phase II instructions do not. The Phase I instructions govern this topic, so venture-backed applicants are eligible here. If you are also considering the Direct to Phase II topic in this cycle, read that document's eligibility language separately and consider raising the discrepancy with the DAF SBIR/STTR One Help Desk during the open period.

Support contractors, status, feedback, and protests

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors. These support contractors may include, but are not limited to, TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space and Missiles Centers may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the AF SBIR/STTR Contracting Officer with concerns regarding the use of support contractors.

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions, since separate notifications are provided for each proposal.

The Air Force anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the BAA Contracting Officer for proposal status before that time.

Refer to the DoW SBIR Program BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(a) and FAR 52.233-2, protests should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer. The DAF uses its best efforts to resolve concerns raised by interested parties at the contracting officer level through open and frank discussions, and for agency protests the DAF provides for inexpensive, informal, procedurally simple, and expeditious resolution of protests.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

How Phase II works

DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the conclusion of the period of performance. This decision will be based on the awardee's technical progress, as determined by a DAF Technical Point of Contact review using the Phase II review criteria.

Phase II is the demonstration of the technology found feasible in Phase I. Only Phase I awardees are eligible to submit a Phase II proposal. All Phase I awardees will be sent a notification with the Phase II proposal submittal date and detailed Phase II proposal preparation instructions. If the physical or email addresses or firm points of contact have changed since submission of the Phase I proposal, correct information shall be sent to the DAF SBIR/STTR One Help Desk. Phase II dollar values, performance periods, and proposal content will be specified in the Phase II request for proposal. All proposals must be submitted electronically via DSIP by the date indicated in the Phase II proposal instructions, and only one Phase II proposal may be submitted for each Phase I award.

The DAF reserves the right to modify the Phase II submission requirements, and should the requirements change, all Phase I awardees will be notified. The DAF also reserves the right to change any administrative procedures that will improve management of the DAF SBIR/STTR Program at any time.

Because the Phase II request can come while Phase I performance is still ongoing and is based on demonstrated technical progress, front-loading real measured results rather than saving everything for the final report is strategically sensible on a six month award.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 6 months from award

Phase II: requested by DAF organizations based on technical progress, during or after Phase I performance, with one Phase II proposal permitted per Phase I award

A working backward plan

Before September 23. Read the evaluation criteria in the DoW FY26 SBIR BAA, since they are not in the component instructions. Read the three cited papers. Settle your device architecture and decide whether you are pursuing the referenced two-element cavity and membrane-bonded saturable absorber route or something else, and if something else, work out your argument for why. Inventory what material and wafers you already have, because six months plus no government-furnished material makes existing inventory valuable. Model your one-third outside cost cap and two-thirds in-house work requirement against your epitaxy and fabrication plan, and if it does not close, file the pre-submission Performance of Work deviation request in the first week of the open period. Resolve export control staffing questions and start DD Form 2345 if you do not hold one. Inventory background intellectual property for Technical Data Rights Assertions. Audit substrate, epitaxy, and optics supply against the eight denial lists. Complete Volume 6 training and verify SAM and DSIP alignment. Send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries.

September 23 through October 3. Draft the technical volume against the 20 page limit, with the device design, the fabrication plan, and the measurement plan against the named metrics as the core. Write the work plan outline separately and keep proprietary detail out of it, since it becomes the Phase I Statement of Work. Build the milestone schedule early, since the TABA task milestone list must track to your milestone payment schedule.

October 4 through October 12. Build the cost volume and itemized listing, neither of which counts against the page limit. Itemize substrates, epitaxial material, coatings, and optics with prices. Classify growth runs and outside fabrication correctly as service, subcontract, or purchase and check the one-third cap. Get separate agreement letters from each consultant and executed agreements with statements of work and detailed cost volumes for each planned subcontract. Include at least one trip to the Air Force location managing the contract. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5 with DD Form 2345 and Technical Data Rights Assertions, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 10-point minimum type, one-inch margins, graphics distinguishable in black and white, no PII uploaded to DSIP, no proprietary content in the technical abstract or the work plan outline.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BZ06-NV034?

‍ ‍

DAF26BZ06-NV034 is a Department of the Air Force SBIR Phase I topic titled "Low Noise and Low-SWaP High-Repetition Rate Mode-Locked Lasers for High-Speed Photonics," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks compact low-SWaP optically or electrically pumped mode-locked lasers in the near-infrared to short-wave infrared capable of operating at repetition rates between 6 and 12 GHz.

‍ ‍

How much funding is available under DAF26BZ06-NV034?

‍ ‍

Up to $250,000 for a period of performance up to 6 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $6,500 in Technical and Business Assistance is available per Phase I award, in addition to the per-topic total.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the exact submission time, which is ordinarily 12:00 p.m. Eastern on the close date. Confirm the time on the live DSIP topic posting rather than assuming an end-of-day deadline.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

What are the laser performance requirements?

‍ ‍

Repetition rate between 6 and 12 GHz, average power of 50 mW or greater, pulse width of a picosecond or less, operation in the near-infrared to short-wave infrared with the O-band and C-band called out for PIC and COTS compatibility, optical or electrical pumping, repetition rate stabilized with custom or COTS electronics, low relative intensity noise, and long-term power stability. Overall SWaP of the laser and its necessary electronics must be minimized, with differentiating goals highlighted across Phase I, II, and III.

‍ ‍

Why does the Air Force want 6 to 12 GHz specifically?

‍ ‍

Because it says a commercially available stabilized low-noise laser in the 6 to 12 GHz range is currently lacking. The band matters because fundamental mode-locking in a semiconductor gain medium at those rates produces a low-noise microwave signal, whereas harmonic mode-locking or pulse interleaving can reach comparable rates but, as the topic puts it, lack a pure microwave signal.

‍ ‍

Why semiconductor gain media rather than fiber or crystal lasers?

‍ ‍

The topic states that mode-locked semiconductor lasers can support high repetition rates up to 100 GHz due to high gain and fast gain recovery, unlike fiber lasers or doped dielectric gain medium lasers. The InP, GaSb, MOCVD, and MBE keywords reinforce that this topic is aimed at companies with semiconductor epitaxy and processing capability.

‍ ‍

What technical approach does the Air Force suggest?

‍ ‍

A two-element cavity design in which the semiconductor saturable absorber is combined with a dielectric output coupler, allowing a shorter overall cavity for high repetition rates without complex gain structures and without high curvature cavity optics. The topic describes near-infrared demonstrations using a curved output coupler with a bonded quantum well saturable absorber forming a hybrid SESAM, achieving roughly 400 femtosecond pulses at 2.8 to 8 GHz, and a visible-spectrum membrane saturable absorber mirror approach. It notes that integrating these elements via direct membrane bonding of the saturable absorber allows higher repetition rates.

‍ ‍

Do I have to use the suggested approach?

‍ ‍

No. The topic says this approach "or other proposed solutions" can be extended throughout the near-infrared and into the short-wave infrared. If you propose an alternative, engage with why the referenced route is insufficient or why yours is better, since the Air Force has stated what it considers promising.

‍ ‍

What does Phase I actually deliver?

‍ ‍

A proof-of-concept for the necessary components plus a feasibility study demonstrating a breadboard 6 to 12 GHz mode-locked laser with picosecond or shorter pulse widths. Component development is to include the semiconductor gain medium, the saturable absorber or other mode-locking element, and the necessary fabrication steps for the components.

‍ ‍

What metrics should I characterize in Phase I?

‍ ‍

The topic names average power, pulse energy, pulse width, long-term power stability, spectral bandwidth, repetition rate tuning, and relative intensity noise as potential metrics. Use them as your data table.

‍ ‍

Do I need to miniaturize the drive electronics in Phase I?

‍ ‍

No. The topic states that supporting electronics can utilize benchtop solutions in Phase I. That permission removes a substantial body of work from a six month effort, so do not spend Phase I funding on electronics miniaturization. The modular, stabilized electronics requirement arrives in Phase II.

‍ ‍

Will the government provide any materials, equipment, or facilities?

‍ ‍

No. The topic states plainly that no government materials, equipment, data, or facilities will be provided. Your cost volume must carry every wafer, tool hour, and instrument you need, and you cannot propose a plan that depends on access to a government facility.

‍ ‍

What happens in Phase II?

‍ ‍

Research to transition the validated Phase I design into prototypes for two fiber-coupled brassboards with full stabilization and low-noise, low-SWaP implementation of the near-infrared to short-wave infrared mode-locked laser. Aside from an external DC power supply, all electronics should be modular with the ability to integrate in Phase III. Note that it is two units, they are fiber-coupled, and the benchtop electronics permission expires.

‍ ‍

What happens in Phase III?

‍ ‍

Develop a fully packaged low-noise, high-repetition rate mode-locked laser operating in the near-infrared to short-wave infrared spectral range, suitable for system integration and commercial sales.

‍ ‍

How long can my technical volume be?

‍ ‍

20 pages or slides, per the topic index. The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. Note that the Cover Sheet, Cost Volume, and Cost Volume Itemized Listing do not count toward the limit, only the Technical Volume and any enclosures or attachments do, and documents uploaded into Volume 5 under "Other" do not count either. Pages or slides in excess of the stated limit will not be reviewed.

‍ ‍

Is 10-point type correct, or is it 11-point?

‍ ‍

For this BAA Phase I release it is 10-point minimum. The DAF Direct to Phase II instructions require 11-point, so do not carry the formatting assumption across documents.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. Of the three topics in this Phase I release, this is the only one carrying a topic-level export control restriction. You must disclose any proposed use of foreign nationals with countries of origin, visa or work permit type, and the statement of work tasks intended for them, and the topic advises that foreign nationals proposed to perform may be restricted due to the technical data involved.

‍ ‍

What identity information should I not upload?

‍ ‍

Do not upload Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information the instructions request, meaning countries of origin, visa or work permit type, and level of involvement, not the underlying identity documents.

‍ ‍

How much of the work must my company perform?

‍ ‍

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit. Separately, the proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded, unless the Contracting Officer approves otherwise in writing. On a $250,000 award that is roughly $83,000 for all outside costs combined.

‍ ‍

What if I need an outside foundry for epitaxy or fabrication?

‍ ‍

Run the arithmetic first, because this is the constraint most likely to bind on a materials-heavy topic. If it does not close, the DAF will occasionally consider deviations, but requests must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. Since the pre-submission request must happen inside the four week open window, treat it as a first-week action.

‍ ‍

How will my proposal be evaluated?

‍ ‍

The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. You must read the criteria in the DoW FY26 SBIR BAA, and you should not assume the Criteria A, B, and C structure from the DAF CSO instructions carries over.

‍ ‍

Are venture capital backed companies eligible?

‍ ‍

Yes, for this topic. The BAA Phase I instructions state that small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics. Note that the DAF Release 6 BAA Direct to Phase II instructions state the opposite for that document's topics, so check eligibility per document rather than per cycle.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state that information contained in the CCR will not be considered by the Air Force during proposal evaluations.

‍ ‍

Why does the work plan outline matter so much?

‍ ‍

Because the DAF uses it as the initial draft of the Phase I Statement of Work. The instructions direct you not to include proprietary information in the work plan outline, warning that doing so will necessitate a request for revision if selected and may delay award. Keep technical detail in the technical volume body and keep the outline at the task and deliverable level.

‍ ‍

What is the SF 298?

‍ ‍

The Report Documentation Page, a standard form that accompanies a technical report. It is named in the required work plan outline format as part of the final report deliverable, so plan for it.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $6,500 per Phase I award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. Unlike the DAF CSO Phase I instructions, this BAA document carries the full detailed request requirements: provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, with the task milestone list tracking to your milestone payment schedule. The detailed request must be in Volume 5, and requests that only specify a value in Volume 3 will not be considered.

‍ ‍

How do I get to Phase II?

‍ ‍

You do not apply on a calendar. DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the period of performance concludes, based on the awardee's technical progress as determined by a DAF Technical Point of Contact review. Only Phase I awardees are eligible, all Phase I awardees receive a notification with the submittal date and detailed instructions, and only one Phase II proposal may be submitted for each Phase I award.

‍ ‍

When will I hear about selection?

‍ ‍

The Air Force anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal.

‍ ‍

Who do I contact with questions?

‍ ‍

For general information related to the AF SBIR/STTR program and proposal preparation instructions, contact the AF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us. The DAF encourages applicants to request clarifying information as early as possible, since delays in such requests constrain its ability to provide satisfactory resolution. For questions regarding the DSIP electronic submission system, contact the DoW SBIR/STTR Help Desk at dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the DoW FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. If your company mail or email addresses or points of contact change after submission, notify the One Help Desk with the subject line "FY26 SBIR BAA Address Change."

‍ ‍

Positioning Advice for Companies Considering This Topic

‍ ‍

Know whether you are the intended applicant. The reference set, the InP and GaSb keywords, and the MOCVD and MBE keywords together describe a company with semiconductor epitaxy and device processing capability, not a systems integrator assembling purchased components. Phase I explicitly includes component development covering the gain medium, the mode-locking element, and the fabrication steps. If you would be buying all of that, the two-thirds in-house requirement and the one-third outside cost cap will be hard to satisfy.

‍ ‍

Read the three papers and position against them. The Air Force described a specific promising approach in unusual detail. Engaging with it, including disagreeing with it for stated reasons, is the clearest way to show technical command of the topic. Ignoring it is the clearest way to look unfamiliar.

‍ ‍

Make the pure microwave signal argument central. The distinguishing claim in this topic is that fundamental mode-locking gives a clean microwave tone where harmonic mode-locking and pulse interleaving do not. Your proposal should make that argument in your own device's terms, with phase noise or relative intensity noise projections, rather than treating repetition rate as the only figure of merit.

‍ ‍

Take the free pass on electronics. Benchtop supporting electronics are explicitly permitted in Phase I. Spend the six months on the laser.

‍ ‍

Plan the schedule around growth cycle time. Six months and no government-furnished material is a real constraint on any plan that needs multiple epitaxy iterations. Say what material you already have, what the growth and processing turnaround is, and what your fallback is if the first structure underperforms.

‍ ‍

Address SWaP at all three phases. The requirement asks for differentiating goals highlighted in Phase I, Phase II, and Phase III. Give three answers, not one.

‍ ‍

Answer the metric list directly. Average power, pulse energy, pulse width, long-term power stability, spectral bandwidth, repetition rate tuning, and relative intensity noise. A compact table of predicted values with measurement methods, plus which of them you consider at risk, does a lot of work in 20 pages.

‍ ‍

Keep the work plan outline clean. It becomes the Statement of Work. Proprietary content there triggers a revision request that delays award, and the instructions say so explicitly.

‍ ‍

Assert your data rights. Epitaxial structure, absorber design, and bonding process are likely your background intellectual property. Technical Data Rights Assertions in Volume 5 is how you keep that boundary clear, and Volume 5 documents do not count against your page limit.

‍ ‍

Use the commercial gap the Air Force handed you. A stated absence of a commercially available stabilized low-noise laser in the 6 to 12 GHz range is a market claim you can cite rather than argue. Microwave photonics, frequency comb applications, high-speed conversion, and precision timing are the adjacent markets, and Phase III explicitly contemplates commercial sales.

DAF SBIR DAF26BZ06-DV037: Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons

Quick Answer

DAF26BZ06-DV037 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force has a high priority requirement for much lower-cost long-range air-launched prompt strike weapons that operate in the very high supersonic flight regime, and this topic funds the seeker that goes in them. The objective is a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting radar, passive direction-finding, and line-of-sight datalink modes. Low unit production cost and high-volume manufacturability are stated as key goals. Awards are up to $2,000,000 for up to 24 months, with a 35 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Two things about this topic are unusual enough that they belong in the first paragraph. First, venture capital, hedge fund, and private equity majority-owned small businesses are not eligible under this announcement. That is the opposite of the rule in the DAF Release 6 CSO topics, and it disqualifies a meaningful share of the defense hardware startup market. Second, the Phase II deliverable is a design, not hardware. The offeror will design and model a prototype to Critical Design Review level. Physical prototype build, laboratory testing, hardware-in-the-loop testing, and flight experiment integration all happen in Phase III with Air Force Research Laboratory 6.3 funding.

Topic At a Glance

Topic number: DAF26BZ06-DV037

Title: Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons

Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Direct to Phase II

Solicitation instrument: BAA, not a CSO. This is a separate solicitation from the DAF 2026 SBIR CSO Release 6 topics, with different rules

Program type: Direct to Phase II (D2P2)

Award maximum value: $2,000,000

Award maximum duration: 24 months

Technical volume page limit: 35 pages or slides

OUSD (R&E) Critical Technology Area: Scaled Hypersonics (SHY)

Component Technology Priority Area: Integrated Sensing and Cyber

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Venture capital, hedge fund, private equity majority ownership: not eligible under this announcement

Phase II end state: Critical Design Review level design and model, not built hardware

Production cost targets: $50,000 threshold, $30,000 objective, per flight unit at volume production

Physical envelope: must fit within a 6 inch interior diameter cylinder

Interface standard: WOSA Seeker Domain interface specification

Named Phase III transition targets: AFLCMC/EB and other Department of Defense users

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: seeker, seekers, AESA, multifunction RF, radar, software-defined RF

Note on the deadline time. The DAF instructions direct firms to the DoW FY26 SBIR BAA for the proposal submission deadline date and time rather than restating it. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP topic posting and do not plan around an end-of-day deadline.

Read This First: Venture Capital Ownership Is Disqualifying Here

The DAF Release 6 BAA instructions state that small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are not eligible to submit applications or receive awards for DAF topics.

That single sentence deserves more attention than anything else in this document, because it is the reverse of what the DAF Release 6 CSO instructions say. The CSO documents covering the other Release 6 DAF topics state that such firms are eligible. This BAA says they are not.

Practically, that means a defense hardware company with majority ownership spread across multiple venture funds, which describes a large share of the companies actually capable of designing a Ku-band multifunction seeker, cannot compete for this topic. If you are in that position, verify your status against the definition before you invest proposal effort. The rule concerns majority ownership in part by multiple VCOCs, hedge funds, or private equity funds, so the analysis turns on your specific cap table rather than on whether you have taken venture money at all.

Two pieces of advice follow. If your ownership structure is anywhere near this line, raise it with the DAF SBIR/STTR One Help Desk during the open period, since the DAF explicitly encourages early clarifying questions and warns that late ones constrain its ability to respond. And if you are reading this page alongside our pages on the DAF Release 6 CSO topics, do not carry the eligibility conclusion from one to the other. They are different solicitations.

BAA Versus CSO: Why This Document Is Not the Same as the Other DAF Release 6 Instructions

The DAF issued Release 6 topics under two different solicitation instruments. The topics numbered with BX, including the five Direct to Phase II topics and the one Phase I topic, sit under the 2026 SBIR Commercial Solutions Opening. This topic, numbered BZ, sits under the 2026 SBIR Broad Agency Announcement.

The two sets of component instructions are largely parallel in structure, and much of the language is identical, but they are separate documents governing separate solicitations. The differences that matter are these.

Venture capital, hedge fund, and private equity majority-owned firms are ineligible under the BAA and eligible under the CSO. This is the consequential one.

Evaluation criteria are not restated in the BAA component instructions. The CSO instructions spell out Criteria A, B, and C in descending order of importance. This BAA document says only that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how you will be scored, and no summary of the CSO criteria is a substitute.

The address change notification uses a different subject line: "FY26 SBIR BAA Address Change" rather than the CSO version.

References throughout point to the FY26 SBIR BAA rather than the CSO for cover sheet instructions, proprietary information marking, technical data rights, and protest procedures.

The performance of work language in this document reads differently, and appears to contain an error, which the next section addresses.

The Performance of Work Problem, and How to Handle It

The BAA component instructions contain three statements about how much work you must perform yourself. Read together they do not cleanly agree, and one of them appears to be a drafting error.

Under Performance of Work Requirements and Location of Work, the document states that for Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit.

That sentence says Phase I, inside a Direct to Phase II instruction document where no Phase I awards are made. The parallel CSO Direct to Phase II instructions say Phase II and set the floor at one-third. The DAF Phase I instructions elsewhere in Release 6 say Phase I and set it at two-thirds. So the most likely reading is that the Phase I paragraph was carried into the Direct to Phase II document by mistake.

Under Consultants and Subcontractors, the document states that in accordance with the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer, and that such requests can only be made upon proposal submission.

Under the Cost Volume subcontracts discussion, the document states that the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price, unless otherwise approved in writing by the Contracting Officer.

The conservative course, and the one we would recommend, is to plan on performing at least two-thirds of the research or analytical effort in house and keeping all consultant, facility lease, and subcontract costs combined below one-half of the total contract price. That satisfies every reading of the document as written, including the strictest one. On a seeker design program that often means resisting the temptation to subcontract large portions of the RF front end or the digital back end design.

If your teaming structure cannot meet two-thirds, the document provides a process, and you have to use it twice. Requests for Performance of Work deviations must be made prior to submission during the topic open period, and again as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove the applicant proceeding with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award. Because the pre-submission request has to happen inside the four week open window, this is a first-week action, not a last-week one. It is also the natural moment to ask the One Help Desk which threshold actually governs.

All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking that approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission.

What the Air Force Is Actually Looking For

The requirement behind the topic

The Department of the Air Force has a high priority requirement for much lower-cost long-range air-launched prompt strike weapons that operate in the very high supersonic flight regime. Toward that requirement, the objective of this topic is to develop a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting RF modes including radar, passive direction-finding, and line-of-sight datalinks. Low unit production cost and high-volume manufacturability are key goals of this topic.

The problem statement is economic before it is technical. Current multifunction radar systems for use onboard various types of small airborne platforms are prohibitively expensive to procure at scale, and the Air Force says this is especially true for systems engineered for use in demanding regimes at peak velocity greater than Mach 3 but under Mach 5. Note that the topic labels that velocity band "high subsonic," which is inconsistent with the stated Mach numbers and with the objective's own description of a very high supersonic flight regime. Read the Mach 3 to Mach 5 figures as the governing statement of the environment.

Because affordability at volume is the point, a proposal that delivers exquisite RF performance without a manufacturing and cost story has missed the topic. Conversely, cost reduction that sacrifices the performance floor also fails, because Phase II requires meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system.

The technical approach the Air Force expects

The effort will leverage recent advancements in RF technology, high-temperature materials science, and associated manufacturing to design a complete multi-function Ku-band RF system to a Critical Design Review level of maturity.

Those three enabling areas are named deliberately and each maps to a different part of the problem. RF technology advancement points toward highly integrated, software-defined architectures, which the topic references reinforce by citing two papers on RF system-on-chip based multi-role sensors. High-temperature materials science addresses the thermal environment of sustained Mach 3 to Mach 5 flight, which is what separates this from a subsonic small-platform radar. Associated manufacturing is the volume production story that the cost targets demand.

The hard requirements

Four requirements are stated explicitly and should be treated as pass or fail gates in your proposal.

Physical envelope. The system must fit within a 6 inch interior diameter cylinder, whether conformally mounted or forward mounted. The Phase II description repeats this, adding that the offeror's design will size and package the front end and back-end RF electronics to fit within that envelope. The fact that both conformal and forward mounting are named means aperture architecture is a real design choice you should address rather than assume.

Interface standard. The design must conform to the WOSA Seeker Domain interface specification. Open systems architecture conformance is a stated requirement, not an option, and it constrains how you partition the system. If you have not worked to that specification before, understanding it is a prerequisite to writing a credible proposal.

Modes. The system must incorporate imaging radar modes, passive direction-finding modes, and height of burst fuze sensing modes. Combined with the objective's mention of line-of-sight datalinks, that is four distinct functions sharing one aperture and back end. Multi-function here means genuinely multi-function.

Maturity. The Phase II output is a design at Critical Design Review level of maturity.

The cost targets, which are the center of the topic

Phase II places emphasis on lowering the flight-unit production cost at volume production to a threshold of $50,000 and an objective of $30,000, while meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system.

Those numbers are the heart of this topic and they are aggressive for a Ku-band multifunction seeker with imaging radar, passive direction finding, datalink, and fuze sensing packaged for a Mach 3 to Mach 5 environment. Your proposal needs a defensible cost model at volume, not a prototype bill of materials. Address component integration and part count reduction, wafer-scale or highly integrated RF and digital solutions, aperture manufacturing approach, thermal management approach and its cost, test and calibration cost per unit which is frequently underestimated in phased array production, and the volume assumptions your model depends on.

Be explicit about the volume at which you hit the threshold and objective. A cost model that only closes at a hundred thousand units per year and a model that closes at two thousand are very different propositions, and the evaluator will want to know which one you are describing.

What Phase II actually produces

For this Direct to Phase II topic, the offeror will design and model a prototype for Critical Design Review level, a complete Ku-band multi-function radar system.

Read that carefully. The verbs are design and model. This is a design maturation program culminating in CDR-level documentation and modeling, plus a cost and manufacturability case. It is not a hardware build program, and a proposal that promises fabricated and tested hardware within the $2,000,000 and 24 month envelope is misreading the topic and inviting doubt about whether you understood it.

That framing also tells you where your effort belongs: modeling and simulation fidelity, design analysis, packaging and thermal analysis, WOSA conformance documentation, producibility analysis, and the cost model. Existing hardware you can point to is feasibility evidence, not a Phase II deliverable.

Phase III

Following successful completion of the Phase II objectives and the culmination of a CDR-level system design, the Air Force Research Laboratory and its transition partner will use 6.3 funding to implement a prototype of the radar system designed in Phase II, perform laboratory, hardware-in-the-loop, and field testing, and then integrate it into a 6.3 flight experiment for further technology maturation. TRL and MRL gaps will be identified and addressed in order to transition the system to AFLCMC/EB and other Department of Defense users.

This is one of the more concrete Phase III descriptions in the Release 6 portfolio, and it is worth using. The government has told you that AFRL and a transition partner will fund the build with 6.3 dollars, that the test sequence is laboratory then hardware-in-the-loop then field then flight experiment, and that the eventual customer is AFLCMC/EB. Both TRL and MRL gaps are named, which reinforces that manufacturing readiness is being assessed alongside technical readiness. Your Relationship with Future R/R&D Efforts section should track this sequence and identify the specific TRL and MRL gaps your Phase II design will leave, along with how Phase III closes them.

The cited references

The topic cites two papers, both about RF system-on-chip based sensors: "ARESTOR: A Multi-role RF Sensor based on the Xilinx RFSoC" by Nial Peters, Colin Horne, and Matthew Ritchie, IEEE Xplore, 2 June 2022; and "Prototyping a Radar Sensor based on a Xilinx RFSoC Device for Detect-And-Avoid onboard Small UAV" by Valentine Wasik, L. Casadebaig, Benjamin Gabard, and Benjamin Gigleux, 2023 20th European Radar Conference.

Both references point in the same direction, toward a software-defined, highly integrated RF system-on-chip approach as the affordability enabler, which is also consistent with the software-defined RF keyword. Read them. Citing and engaging with the government's own references, including where you think a different approach is better, is a cheap and effective way to signal that you did the work.

The Feasibility Requirement

Direct to Phase II means you must document that you already completed the Phase I equivalent work outside the SBIR program. The DAF will not consider your proposal if you fail to demonstrate technical merit and feasibility have been established, or if you fail to demonstrate the feasibility effort was substantially performed by the applicant or the principal investigator. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

What this topic requires specifically

For this Direct to Phase II topic, the offeror must have previously demonstrated Phase I-type feasibility by demonstrating the successful system design, modeling, and hardware specifications of a multifunction radar system for use in an embedded system application. The feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system.

Three elements sit inside that requirement. Successful system design, modeling, and hardware specifications, meaning documented design work and modeling results plus specifications at the hardware level. A multifunction radar system, so a single-function radar heritage is a weaker fit and you should say how it extends. For use in an embedded system application, meaning integrated into a constrained platform rather than a benchtop or standalone instrument.

Plus a fourth element that is a deliverable rather than a heritage claim: the feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system. That is forward-looking. You need to put a baseline concept for the Ku-band seeker into your feasibility documentation, not only evidence of past work.

The general D2P2 rules

Applicants must demonstrate completion of research and development through means other than the SBIR and STTR programs to establish the feasibility of the proposed Phase II effort based on the criteria outlined in the topic description.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists specifically for companies that matured technology outside the SBIR pipeline.

Feasibility efforts detailed must have been substantially performed by the applicant or the principal investigator.

If technology in the feasibility documentation is subject to intellectual property rights, the applicant must provide IP rights assertions, and applicants shall provide a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research. The document points to the FY26 SBIR BAA for technical data rights information.

One helpful mechanical detail this BAA states more clearly than the parallel CSO document: feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. That means your design heritage, modeling results, hardware specifications, and baseline conceptual design can be documented at whatever length the evidence requires without eating into your 35 page technical volume. Use that.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material, which will not be evaluated.

Funding Allowance and Cost Structure

Award ceiling

Up to $2,000,000 across up to 24 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The instructions also note that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

Note the difference between the two dollar figures in this topic. The $2,000,000 is the design contract. The $50,000 threshold and $30,000 objective are per-unit flight hardware production costs at volume that your design must achieve. Do not conflate them.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards. In accordance with the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

A significant procedural note: if no exceptions are taken to an applicant's proposal, the Government may award a contract without exchanges. Therefore the applicant's initial proposal should contain the applicant's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen exchanges later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The DAF will provide up to $50,000 per Phase II award, in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal. Applicants may elect to use 50 percent of this TABA allocation, meaning $25,000, on a first SBIR Phase II award and 50 percent, meaning $25,000, on a sequential SBIR Phase II award.

Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases.

For this topic, development of manufacturing plans is the standout. High-volume manufacturability is a stated key goal, the cost targets are aggressive, and Phase III explicitly names MRL gaps alongside TRL gaps. TABA support for manufacturing planning is directly on point.

Those activities can be undertaken in furtherance of the following purposes: making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

Requests for TABA funding creditable to a TABA provider must include the following information or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider, including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.

If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed, including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.

A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.

Cost volume expectations

A detailed cost proposal must be submitted, and cost proposal information will be treated as proprietary. Proposed costs must be provided by both individual cost element and contractor fiscal year in sufficient detail to determine the basis for estimates, as well as the purpose, necessity, and reasonableness of each. This information will expedite award if the proposal is selected. Cost proposal attachments do not count toward proposal page limitations.

Direct labor. Identify key personnel by name, if possible, and labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a design and modeling program, this will be nearly the entire budget, so it deserves the most care. RF engineers, digital designers, packaging and thermal engineers, and producibility analysts should be visible as named individuals or clearly defined categories with hours that match the task structure.

Direct cost materials. Costs for materials, parts, and supplies must be justified and supported. Provide an itemized list of types, quantities, prices, and where appropriate purpose. If computer or software purchases are planned, detailed information such as manufacturer, price quotes, proposed use, and support for the need will be required. On this topic, electromagnetic simulation, circuit and system modeling, and thermal analysis licenses are likely the significant items, and they need quotes and justification.

Other direct costs. This includes specialized services such as machining or milling, special test and analysis, and costs for temporary use or lease of specialized facilities and equipment. Provide usage hours expected, rates, and sources, as well as a brief discussion concerning the purpose and justification. Proposals including leased hardware must include an adequate lease versus purchase rationale. Anechoic chamber or near-field range time, if any is planned for design validation, belongs here.

Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an applicant would otherwise possess in the normal course of business. These may include such items as innovative instrumentation or automatic test equipment.

Subcontracts. Subcontract costs must be supported with copies of subcontract agreements. Agreement documents must adequately describe the work to be performed and cost bases. The agreement document should include a statement of work, assigned personnel, hours and rates, materials if any, and proposed travel if any. A letter from a subcontractor agreeing to perform a task or tasks at a fixed price is not considered sufficient. The proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price, unless otherwise approved in writing by the Contracting Officer. The prime contractor must accomplish price analysis, including reasonableness, of the proposed subcontractor costs. If based on comparison with prior efforts, identify the basis upon which the prior prices were determined reasonable. If price analysis techniques are inadequate or the FAR requires subcontractor cost or pricing data submission, provide a cost analysis, which includes but is not limited to consideration of materials, labor, travel, other direct costs, and proposed profit rates.

Consultants. For each consultant, provide a separate agreement letter briefly stating the service to be provided, hours required, and hourly rate, as well as a short, concise resume.

Travel. Each effort should include, at a minimum, a kickoff or interim meeting. Travel costs must be justified as required for the effort. Include destinations, number of trips, number of travelers per trip, airfare, per diem, lodging, and ground transportation. Per diem and lodging rates may be found in the Joint Travel Regulation, Volume 2. On a program that culminates in a Critical Design Review, budget for the design review itself and for interim technical interchange meetings with AFRL, since Phase III depends on AFRL picking the design up.

Indirect costs. Indicate proposed rates' bases, for example budgeted or actual rates per fiscal year. The proposal should identify the specific rates used and allocation bases to which they are applied. Do not propose composite rates; proposed rates and applications per fiscal year throughout the anticipated performance period are required.

Non-SBIR governmental or private investment is allowed. However, it is not required, nor will it be a proposal evaluation factor.

Export Control, Which Is Central on a Seeker Topic

The technology within this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including export of sensitive technical data, and the EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by the foreign nationals in accordance with section 3.5 of the Announcement. Offerors are advised that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

A weapon seeker is about as clearly ITAR-controlled as a technology gets, so treat this as a hard staffing constraint rather than a disclosure exercise. In the technical volume, identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for those individuals, in addition to technical resumes, provide countries of origin, type of visas or work permits held, and identify the tasks they are anticipated to perform.

Foreign nationals, also known as foreign persons, means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR BAA and disclose this information regardless of whether the topic is subject to ITAR restrictions.

When the topic area is subject to export control, these individuals, if permitted to participate, are limited to work in the public domain. Further, tasks assigned must not be capable of assimilation into an understanding of the project's overall objectives. This prevents foreign citizens from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations in order to verify foreign citizens' eligibility to perform on a contract awarded under this BAA.

The following will apply to all projects with military or dual-use applications developing beyond fundamental research, meaning basic and applied research ordinarily published and shared broadly within the scientific community. The Contractor shall comply with all U.S. export control laws and regulations, including ITAR 22 CFR Parts 120 through 130 and the EAR 15 CFR Parts 730 through 799, in the performance of this contract. In the absence of available license exemptions or exceptions, the Contractor shall be responsible for obtaining the appropriate licenses or other approvals, if required, for exports of, including deemed exports of, hardware, technical data, and software, or for the provision of technical assistance. The Contractor shall be responsible for obtaining export licenses, if required, before utilizing foreign persons in the performance of this contract, including instances where the work is to be performed on-site at any Government installation, whether in or outside the United States, where the foreign person will have access to export-controlled technologies including technical data or software. The Contractor shall be responsible for all regulatory record keeping requirements associated with the use of licenses and license exemptions or exceptions. The Contractor shall be responsible for ensuring that these provisions apply to its subcontractors.

If you are asserting export-controlled status, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission must be included in Volume 5. The form, instructions, and FAQs are available at the United States and Canada Joint Certification Program website. DD Form 2345 approval will be required if the proposal is selected for award.

Proposal Structure: The Seven Volumes

Formatting

Proposals should be direct, concise, and informative. Type shall be no smaller than 11-point on standard 8.5 by 11 paper, with one-inch margins and pages consecutively numbered. Applicants are discouraged from including promotional and non-programmatic items. If included, such material will count toward the page limit.

The technical volume limit for this topic is 35 pages or slides, per the topic index. Pages or slides in excess of this number will not be considered during evaluations. The preferred submission format is Portable Document Format. Graphics must be distinguishable in black and white, which matters for a topic where you will want to show antenna patterns, block diagrams, and packaging layouts. Virus-check all submissions.

The complete proposal must be submitted electronically through DSIP. Ensure the complete technical volume and additional cost volume information is included in this sole submission.

Fraud, Waste, and Abuse training must be completed prior to proposal submission. When training is complete and certified, DSIP will indicate completion of the Volume 6 requirement, and the proposal cannot be submitted until the training is complete. The DAF recommends completing submission early, as site traffic is heavy prior to solicitation close, causing system lag, and states plainly not to wait until the last minute. The DAF will not be responsible for proposals not completely submitted prior to the deadline due to system inaccessibility unless advised by DoW, and will not accept alternative means of submission outside of DSIP.

Also note the criminal warning the instructions include: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released. On a seeker topic, be deliberate about what goes in the abstract, since it will become public.

If a proposal submitted in response to this BAA is substantially the same as another proposal submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, the applicant must so indicate on the Cover Sheet.

Volume 2, Technical Volume

The technical proposal includes all items listed below in the order provided.

Table of contents, located immediately after the Cover Sheet.

Glossary of acronyms and abbreviations used in the proposal.

Milestone identification, including a program schedule with all key milestones identified.

Identification and significance of the problem or opportunity, briefly referencing the specific technical problem or opportunity to be pursued under this effort.

Phase II technical objectives, detailing the specific objectives of the Phase II work and describing the technical approach and methods to be used in meeting these objectives, including an assessment of the potential commercial application for each objective.

Work plan. The work plan shall be a separate and distinct part of the proposal package, using a page break to divide it from the technical proposal, and begins on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility. Do not include proprietary information, because in the event of proposal selection the work plan will be incorporated into the resulting contract by reference. The recommended format is 1.0 Objective, providing a brief overview of the specialty area explaining the purpose and expected outcome; 2.0 Scope, providing a concise description of the work to be accomplished including the technology area to be investigated, goals, and major milestones, with task development and deliverables as the key elements meaning the anticipated end result or the effort's product, and consistent with the information in section 4.0; 3.0 Background, in which the applicant shall identify appropriate specifications, standards, and other documents applicable to the effort, including information or explanation for and constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task and Technical Requirements, in which detailed individual task descriptions must be developed in an orderly progression with sufficient detail to establish overall program requirements and goals, with the work effort segregated into major tasks identified in separately numbered paragraphs. Each numbered major task should delineate the work to be performed by subtask. The work plan must contain every task to be accomplished in definite, realistic, and clearly stated terms. Use "shall" whenever the work plan expresses a binding provision, "should" or "may" to express a declaration or purpose, and "will" when no contractor requirement is involved.

Section 3.0 Background deserves attention on this topic, since the WOSA Seeker Domain interface specification is exactly the kind of applicable specification the instructions are asking you to identify. Name it, and name any other standards your design conforms to.

Deliverables. Include a section clearly describing the specific sample or prototype hardware and software to be delivered, as well as data deliverables, schedules, and quantities. Be aware of the possible requirement for unique item identification in accordance with DFARS 252.211-7003, Item Identification and Valuation, for hardware. If hardware or software will be developed but not delivered, provide an explanation. On this topic that explanation matters, because the Phase II output is a design and model rather than built hardware, so be clear about what physical artifacts, if any, exist and why.

At a minimum, the following reports will be required under all Phase II contracts. Scientific and Technical Reports, noting that rights in technical data including software developed under the terms of any contract resulting from a SBIR Announcement generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the SBIR/STTR contract for a period of 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page will be a single-page project summary identifying the work's purpose, providing a brief description of the effort accomplished, and listing potential result applications; the summary may be published by DoW and therefore must not contain any proprietary or classified information, while the remainder of the report should contain details of project objectives met, work completed, results obtained, and technical feasibility estimates. Status reports are due quarterly at a minimum. The Air Force may require additional reporting documentation including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project will result in partial or total development and delivery of hardware, and updates to the commercialization results.

Given that this program produces a CDR-level design, the engineering drawings item and the 20 year data rights provision together deserve a conversation with counsel before you decide what design detail to generate under the award.

Related work. Describe significant activities directly related to the proposed effort, including any previous programs conducted by the principal investigator, proposing firm, consultants, or others, and their application to the proposed project. Describe how these activities interface with the proposed project and discuss any planned coordination with outside sources. Also list any applicant-identified subject matter experts, regardless of affiliation, providing comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related to the proposed effort but similar, providing a short description, the client for which the work was performed including an individual to be contacted and phone number, and the date of completion.

Commercialization potential. The DoW requires a commercialization plan be submitted with the Phase II proposal, specifically addressing what the first planned product to incorporate the proposed technology is, who the probable customers are and what the estimated market size is, how much money is needed to bring the technology to market and how it will be raised, whether the firm has the necessary marketing expertise and if not how the firm will compensate, and who the probable competitors are and what price or quality advantage is anticipated by the firm. The commercialization strategy plan should briefly describe the commercialization potential for the proposed project's anticipated results as well as plans to exploit it. Commercial potential is evidenced by the existence of private sector or non-SBIR/STTR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and the presence of other indicators of commercial technology potential including the firm's commercialization strategy.

If awarded a D2P2, the awardee will be required to update periodically the commercialization results of the project via SBA. These updates will be required at completion of the effort and subsequently when the contractor submits a new SBIR/STTR proposal to DoW. Firms not submitting a new proposal to DoW will be requested to provide updates annually after the D2P2 completion. Note that the Commercialization Plan and the Company Commercialization Report are distinct documents; the CCR comprises Volume 4.

The commercialization question is harder on this topic than on most, because a Ku-band prompt strike seeker has limited non-defense application. The honest framing is that the primary market is defense volume production, that the named Phase III path runs through AFRL to AFLCMC/EB and other DoD users, and that the underlying software-defined multifunction RF architecture and low-cost manufacturing approach have adjacent applications. Do not manufacture an implausible commercial market. Build the case on volume defense demand plus genuine architecture-level spillover.

Relationship with future R/R&D efforts. State the anticipated results of the proposed approach, specifically addressing plans for Phase III, if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III R/R&D effort, if planned. The topic gives you the Phase III sequence, so track it.

Key personnel. In the technical volume, identify all key personnel involved in the project. Include information directly related to education, experience, and citizenship. A technical resume for the Principal Investigator, including publications if any, must also be included. Concise technical resumes for subcontractors and consultants, if any, are also useful. The Principal Investigator's primary employment must be with the small business concern at the time of award and during the entire period of performance. Primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager can be designated to a proposal at any given time.

Facilities and equipment. Describe instrumentation and physical facilities necessary and available to carry out the D2P2 effort. Justify equipment to be purchased, with detail in the cost proposal. State whether proposed performance locations meet environmental laws and regulations of federal, state, and local governments for, but not limited to, airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors. Private companies, consultants, or universities may be involved in the project. All should be described in detail and included in the cost proposal. In accordance with the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm, unless otherwise approved in writing by the Contracting Officer, and these requests can only be made upon proposal submission. Signed copies of all consultant or subcontractor letters of intent must be attached to the proposal. These letters should briefly state the contribution or expertise being provided. Include statements of work and detailed cost proposals, and information regarding consultant or subcontractor unique qualifications. Subcontract copies and supporting documents do not count against the Phase II page limit. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support of similar proposals or awards. While it is permissible, with proper notification, to submit identical proposals or proposals containing a significant amount of essentially equivalent work for consideration under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort. Any potential for this situation must be disclosed to the solicitation agencies before award. Provide the name and address of the federal agencies or DoW components to which proposals were or will be submitted or from which an award is expected or has been received, the proposal submission or award dates, the proposal title, the PI's name and title for each proposal submitted or award received, the solicitation titles, numbers, and dates under which the proposal was or will be submitted or under which an award is expected or has been received, the contract number if an award was received, and the applicable topics for each SBIR proposal submitted or award received. If this section does not apply, state in the proposal, "No prior, current, or pending support for proposed work."

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the DoW FY26 SBIR BAA for full details on this requirement. Information contained in the CCR will not be considered by the DAF during proposal evaluations. Complete it for compliance and do not treat it as a scoring opportunity.

Volume 5, Supporting Documents

The following documents may be required if applicable to your proposal. DD Form 2345, which applies to this export-controlled topic. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 BAA. Technical Data Rights Assertions, if asserting data rights restrictions. On a seeker design program built on proprietary RF architecture, this last item is how you draw the line between your background intellectual property and what you develop under the award.

Feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. Its requirements are described above.

The detailed TABA request, if you are requesting TABA, also belongs in Volume 5.

Volume 6, Fraud, Waste, and Abuse Training

Fraud, Waste and Abuse training material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the Disclosures of Foreign Affiliations or Relationships to Foreign Countries webform in Volume 7 of the DSIP proposal submission. The webform will not be accepted as a PDF supporting document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW Program BAA.

How Your Proposal Will Be Evaluated

The criteria are in the BAA, not in this document

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel. Throughout evaluation, selection, and award, confidential proposal and evaluation information will be protected to the greatest extent possible. D2P2 proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

The component instructions then state that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0.

That is the whole of it. Unlike the DAF Release 6 CSO instructions, which restate Criteria A, B, and C with their relative importance, this BAA document does not reproduce the evaluation criteria. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how your proposal will be scored, and you should not assume the CSO criteria carry over. This is the single most important research task before you start writing, because the criteria determine your proposal's structure and emphasis.

The DAF adds that it is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic, that multiple procurements are planned and anticipated as a result of the topic, that each proposal is considered a separate procurement and will be evaluated on its own merit, and that the Government may award all, some, or none of the proposals.

Foreign risk evaluation

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of Defense, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures the DAF will use include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

For an RF hardware company, patent analysis and the semiconductor supply chain both deserve a look before you propose. RF system-on-chip devices, gallium nitride and gallium arsenide processes, packaging, and passive components frequently trace to suppliers with entries on one or more of the denial lists below, and the topic's own references point toward commercial RFSoC parts.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the small business concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.

If the DAF denies an award under 15 U.S.C. 638(g)(16) or 638(o)(20), or upon determining that the concern has a security risk described in that paragraph, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv).

Support contractors

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors. These support contractors may include, but are not limited to, APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the DAF SBIR/STTR Contracting Officer with concerns about any of these contractors.

Status, feedback, and protests

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions, since separate notifications are provided for each proposal.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for proposal status before that time.

Refer to the FY26 SBIR BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(b) and FAR 52.233-3, protests after award should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer and to the individual procuring contracting officer listed on your firm's selection notification.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. Settle eligibility first, because nothing else matters if you fail it. If venture capital, hedge fund, or private equity funds hold majority ownership in part, resolve your status against the definition and raise it with the DAF SBIR/STTR One Help Desk. Read Section 6.0 of the DoW FY26 SBIR BAA, since the evaluation criteria are there and not in the component instructions. Obtain and study the WOSA Seeker Domain interface specification. Read the two cited RFSoC papers. Assemble your feasibility documentation: system design, modeling, and hardware specifications for a multifunction radar in an embedded application, substantially performed by your firm or your PI, with no SBIR or STTR lineage. Draft the baseline conceptual design for the Ku-band seeker, which the feasibility demonstration must also describe. Build the volume production cost model that reaches $50,000 threshold and $30,000 objective, and identify the volume assumption it rests on. Audit your semiconductor and component supply chain against the eight denial lists. Resolve export control staffing, since foreign nationals may be restricted from performing on this topic, and start DD Form 2345 if you do not hold one. Check your work distribution against the two-thirds figure and, if you cannot meet it, file the pre-submission Performance of Work deviation request in the first week of the open period. Complete Volume 6 training and verify SAM and DSIP alignment.

September 23 through October 3. Draft Volume 2 in the required order against the 35 page limit. Structure the technical approach around the four hard requirements: the 6 inch interior diameter envelope with conformal or forward mounting addressed, WOSA Seeker Domain conformance, the imaging radar, passive direction-finding, and height of burst fuze sensing modes plus line-of-sight datalink, and CDR-level maturity. Build the milestone schedule early, since the TABA task milestone list must track to your milestone payment schedule. Write the work plan as a separate page-broken document in contract language with no proprietary content, naming the WOSA specification in section 3.0 Background.

October 4 through October 12. Build the cost volume by individual cost element and contractor fiscal year. Get quotes for simulation and modeling software licenses. Collect signed letters of intent, statements of work, and detailed cost proposals from every consultant and subcontractor, remembering that a letter agreeing to a fixed price is not sufficient. Verify all outside costs sit below one-half of the total contract price. Write the detailed TABA request into Volume 5 if requesting TABA, and consider manufacturing plan development given the volume production emphasis.

October 13 through October 16. Finalize the Volume 5 package, which for this topic carries real weight: feasibility documentation with no page limit, DD Form 2345, Technical Data Rights Assertions, and the TABA request. Complete the Volume 7 webform and the Volume 4 CCR. Run a compliance pass: 35 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics distinguishable in black and white, virus-checked PDF, no marketing material, no proprietary information in the technical abstract or the work plan.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BZ06-DV037?

‍ ‍

DAF26BZ06-DV037 is a Department of the Air Force SBIR Direct to Phase II topic titled "Low-Cost Multi-Function Ku-Band RF System for Prompt Strike Weapons," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks a Ku-band multi-function RF seeker system that can be manufactured at scale, supporting radar, passive direction-finding, and line-of-sight datalink modes, for long-range air-launched prompt strike weapons operating in the very high supersonic flight regime.

‍ ‍

Are venture capital backed companies eligible for this topic?

‍ ‍

No. The DAF Release 6 BAA instructions state that small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are not eligible to submit applications or receive awards for DAF topics. This is the opposite of the rule in the DAF Release 6 CSO instructions, which cover the BX-numbered topics and state that such firms are eligible. If your ownership structure is near this line, verify your status and raise it with the DAF SBIR/STTR One Help Desk during the open period.

‍ ‍

Why does the eligibility rule differ from the other DAF Release 6 topics?

‍ ‍

Because they are different solicitations. The BX-numbered Release 6 topics sit under the 2026 SBIR Commercial Solutions Opening, and this BZ-numbered topic sits under the 2026 SBIR Broad Agency Announcement. The two sets of component instructions are largely parallel but govern separate solicitations, and the venture capital ownership provision reads opposite ways in the two documents. Do not carry an eligibility conclusion from one to the other.

‍ ‍

How much funding is available under DAF26BZ06-DV037?

‍ ‍

Up to $2,000,000 for a period of performance up to 24 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition to that ceiling.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct firms to the DoW FY26 SBIR BAA for the exact submission time, which is ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting rather than assuming an end-of-day deadline.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

What does Phase II actually deliver?

‍ ‍

A design, not hardware. For this Direct to Phase II topic the offeror will design and model a prototype for Critical Design Review level, a complete Ku-band multi-function radar system. Physical prototype implementation, laboratory testing, hardware-in-the-loop testing, field testing, and flight experiment integration all occur in Phase III with Air Force Research Laboratory 6.3 funding. A proposal promising fabricated and tested hardware inside the $2,000,000 and 24 month envelope has misread the topic.

‍ ‍

What are the production cost targets?

‍ ‍

The Phase II emphasis is on lowering the flight-unit production cost at volume production to a threshold of $50,000 and an objective of $30,000, while meeting or exceeding the RF performance metrics of a contemporary, similarly-sized multifunction radar system. These are per-unit hardware costs at volume, entirely separate from the $2,000,000 design award. State the volume assumption your cost model depends on.

‍ ‍

What is the physical envelope requirement?

‍ ‍

The system must fit within a 6 inch interior diameter cylinder, whether conformally mounted or forward mounted. The Phase II description adds that the design will size and package the front end and back-end RF electronics to fit within that envelope. Because both conformal and forward mounting are named, aperture architecture is a design choice worth addressing explicitly.

‍ ‍

What interface standard must the design conform to?

‍ ‍

The WOSA Seeker Domain interface specification. This is a stated key technical requirement, so obtain and study the specification before writing, and name it among the applicable specifications in section 3.0 Background of your work plan.

‍ ‍

What modes must the system support?

‍ ‍

The topic names imaging radar modes, passive direction-finding modes, and height of burst fuze sensing modes as key technical requirements, and the objective adds line-of-sight datalinks to the RF modes supported. That is four distinct functions sharing one aperture and back end.

‍ ‍

What flight regime does this seeker operate in?

‍ ‍

The objective describes a very high supersonic flight regime, and the description specifies peak velocity greater than Mach 3 but under Mach 5. Note that the description labels that band "high subsonic," which is inconsistent with the Mach numbers stated and with the objective's own wording, so treat the Mach 3 to Mach 5 figures as governing.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This is a Direct to Phase II topic. Applicants must provide documentation satisfying the Phase I feasibility requirement to be included in the Phase II proposal, demonstrating completion of research and development through means other than the SBIR and STTR programs.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

The offeror must have previously demonstrated Phase I-type feasibility by demonstrating the successful system design, modeling, and hardware specifications of a multifunction radar system for use in an embedded system application. The feasibility demonstration shall also describe a baseline conceptual design for the proposed multifunction radar system. So you need both documented heritage and a forward-looking baseline concept.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility efforts detailed must have been substantially performed by the applicant or the principal investigator.

‍ ‍

Does feasibility documentation count against my page limit?

‍ ‍

No. The instructions state that feasibility documentation is required for all proposal submissions, is contained within Volume 5, and is not subject to page limitations. Use that room for your design heritage, modeling results, hardware specifications, and baseline conceptual design rather than compressing them into the technical volume.

‍ ‍

How long can my technical volume be?

‍ ‍

35 pages or slides, per the topic index. Pages or slides in excess of this number will not be considered during evaluations. Type must be no smaller than 11-point on standard 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Cost proposal attachments, subcontract copies and supporting documents, and feasibility documentation do not count toward the limit.

‍ ‍

How will my proposal be evaluated?

‍ ‍

The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria outlined in the FY26 SBIR BAA Section 6.0. You must read Section 6.0 of the DoW FY26 SBIR BAA to know how you will be scored, and you should not assume the Criteria A, B, and C structure from the DAF CSO instructions carries over. This is the first research task before writing.

‍ ‍

How much of the work must my company perform?

‍ ‍

The document states three overlapping figures. Under Performance of Work Requirements it says a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit, though that paragraph refers to Phase I inside a Direct to Phase II document and appears to be a drafting artifact. Under Consultants and Subcontractors it says a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. And the subcontracts cost guidance caps all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements at one-half of the total contract price. Planning to perform at least two-thirds in house and keeping all outside costs below one-half of contract price satisfies every reading. If you cannot, file a Performance of Work deviation request during the open period and again with your proposal, and ask the One Help Desk which threshold governs.

‍ ‍

How do I request a performance of work deviation?

‍ ‍

Requests must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove the applicant proceeding with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award. Because the pre-submission request must happen inside the four week open window, treat it as a first-week action.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for them. The topic advises that foreign nationals proposed to perform may be restricted due to the technical data under U.S. export control laws. A certified DD Form 2345, or evidence of application submission, belongs in Volume 5, and approval will be required if selected for award.

‍ ‍

Can foreign nationals work on this project?

‍ ‍

Only in limited ways, if at all. Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which the instructions note prevents foreign citizens from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations to verify eligibility. On a weapon seeker topic, treat this as a hard staffing constraint.

‍ ‍

Who owns the design data I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. Because this program produces a CDR-level design and the Air Force may require engineering drawings as additional reporting, review the data rights provision with counsel before deciding what design detail to generate under the award, and use Technical Data Rights Assertions in Volume 5 to protect background intellectual property.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state that information contained in the CCR will not be considered by the DAF during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award, in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, and splittable as $25,000 on a first SBIR Phase II award and $25,000 on a sequential one. Development of manufacturing plans is an eligible activity and is directly relevant here given the high-volume manufacturability goal and the MRL gaps named in Phase III. The detailed request must be in Volume 5, including provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests that only specify a value in Volume 3 will not be considered.

‍ ‍

What happens in Phase III?

‍ ‍

Following successful completion of the Phase II objectives and the culmination of a CDR-level system design, AFRL and its transition partner will use 6.3 funding to implement a prototype of the radar system designed in Phase II, perform laboratory, hardware-in-the-loop, and field testing, and then integrate it into a 6.3 flight experiment for further technology maturation. TRL and MRL gaps will be identified and addressed in order to transition the system to AFLCMC/EB and other Department of Defense users.

‍ ‍

What is the commercial market for this technology?

‍ ‍

It is limited, and honesty serves you better than invention here. A Ku-band prompt strike weapon seeker has a primarily defense market, and the topic gives you a concrete Phase III path through AFRL to AFLCMC/EB and other DoD users. Build the commercialization case on volume defense demand plus genuine architecture-level spillover from the software-defined multifunction RF approach and the low-cost manufacturing methods, rather than on an implausible commercial application.

‍ ‍

What references does the topic cite?

‍ ‍

Two papers on RF system-on-chip based sensors: "ARESTOR: A Multi-role RF Sensor based on the Xilinx RFSoC" by Nial Peters, Colin Horne, and Matthew Ritchie, IEEE Xplore, 2 June 2022; and "Prototyping a Radar Sensor based on a Xilinx RFSoC Device for Detect-And-Avoid onboard Small UAV" by Valentine Wasik, L. Casadebaig, Benjamin Gabard, and Benjamin Gigleux, 2023 20th European Radar Conference. Both point toward a software-defined, highly integrated RFSoC approach as the affordability enabler.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal submitted.

‍ ‍

Will I be able to negotiate after submitting?

‍ ‍

Possibly not. If no exceptions are taken to your proposal, the Government may award a contract without exchanges, so your initial proposal should contain your best terms from a cost or price and technical standpoint. The Government reserves the right to reopen exchanges later if the Contracting Officer determines it necessary.

‍ ‍

Who do I contact with questions?

‍ ‍

For general information related to the DAF SBIR/STTR program and proposal preparation instructions, contact the DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us. The DAF encourages applicants to request clarifying information as early as possible, since delays in such requests constrain its ability to provide satisfactory resolution to applicant concerns. For questions regarding the DSIP electronic submission system, contact the DoW SBIR/STTR Help Desk at dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. If your company mail or email addresses or points of contact change after proposal submission, provide the information to the DAF SBIR/STTR One Help Desk with the subject line "FY26 SBIR BAA Address Change."

‍ ‍

Positioning Advice for Companies Considering This Topic

‍ ‍

Check eligibility before anything else. Majority ownership in part by multiple venture capital operating companies, hedge funds, or private equity funds is disqualifying under this announcement. That is an unusual gate in modern defense SBIR, and it removes a large fraction of the companies that would otherwise be natural bidders. If you clear it, you are competing in a thinner field than the technology would suggest, which is worth knowing.

‍ ‍

Read BAA Section 6.0 first. The evaluation criteria are not in the component instructions. Writing a proposal without them is guessing at what matters, and the criteria should shape your section emphasis and your milestone framing.

‍ ‍

Lead with cost and manufacturability, not RF performance. The topic says low unit production cost and high-volume manufacturability are key goals, sets a $50,000 threshold and $30,000 objective, and identifies MRL gaps alongside TRL gaps in Phase III. Performance is the constraint you must satisfy, and cost is the variable you are being asked to move. Structure the proposal accordingly, with a defensible volume cost model rather than a prototype bill of materials.

‍ ‍

State your volume assumption explicitly. A cost target is meaningless without the production rate behind it. Give the number, justify it against plausible program quantities, and show cost sensitivity if the rate is lower.

‍ ‍

Respect the design-only scope. Design and model to CDR is what Phase II buys. Overpromising fabricated hardware reads as either a misreading of the topic or an unrealistic plan, and cost realism concerns follow either way. Put the build in Phase III where the government put it.

‍ ‍

Take WOSA conformance seriously as an architecture driver. An open interface specification changes how you partition front end, back end, and processing. Show that you understand it rather than asserting conformance in a sentence.

‍ ‍

Address the thermal problem directly. High-temperature materials science is one of three named enabling areas, and Mach 3 to Mach 5 sustained flight is the reason. Radome, aperture, and electronics thermal management is where a design that works subsonically fails here, and it interacts with the cost target because exotic thermal solutions are expensive.

‍ ‍

Engage the cited references. Both point toward RFSoC-class integration. If that is your approach, say how you go beyond the referenced work. If you have a better path, say why, and be specific. Either is stronger than ignoring them.

‍ ‍

Make the four modes share hardware credibly. Imaging radar, passive direction finding, height of burst fuze sensing, and line-of-sight datalink from one aperture and back end is the multi-function claim. Explain the time and frequency resource sharing, the calibration approach, and where the modes conflict.

‍ ‍

Build the feasibility package properly, and use the page relief. Feasibility documentation lives in Volume 5 and is not page limited. System design, modeling, and hardware specifications for a multifunction radar in an embedded application, plus the baseline conceptual design, can be documented thoroughly without spending technical volume pages.

‍ ‍

Audit the semiconductor supply chain early. The denial criteria name eight lists, and RF and digital component sourcing touches them more often than teams expect. A mandatory denial after selection is an expensive way to learn this.

‍ ‍

Plan for two-thirds in house. Given the ambiguity in the document, plan to the strictest figure and keep all outside costs below half the contract price. If your approach depends on a large subcontracted element, file the deviation request in the first week of the open period rather than discovering the problem at submission.

DAF SBIR DAF26BX06-NV510: AI/ML for Next Generation of Missile Detection, Warning, Tracking, and Reporting

Quick Answer

DAF26BX06-NV510 is a Department of the Air Force SBIR Phase I topic under the DAF FY26 SBIR Commercial Solutions Opening, Release 6. SpaceWERX, working with Space Systems Command's Space Sensing System Delta 84 and the OPIR Tap Lab, wants to assess whether artificial intelligence and machine learning can improve multi-sensor fusion, missile tracking precision, and real-time situational awareness across a multi-orbit satellite framework spanning geosynchronous, medium, and low Earth orbit. Awards are up to $150,000 for a period of performance up to 3 months, with a 30 page or slide technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Three months and $150,000 tells you exactly what this is. It is not a build. The Air Force says Phase I deliverables are expected to focus on a feasibility study detailing United States Space Force concept of operations and technical viability, plus analytical findings, and that the research plan can include modeling, simulation, literature review, or trade studies. Algorithm prototypes or simulation results are welcome as applicable. What the Air Force actually wants out of Phase I is stated plainly: to onboard and coordinate emergent solutions into the OPIR Tap Lab and create a shared understanding of the Missile Warning and Tracking mission area problem set. Read that as an invitation to become a known quantity inside a specific government lab, with a small award as the entry ticket.

Topic At a Glance

Topic number: DAF26BX06-NV510

Title: AI/ML for Next Generation of Missile Detection, Warning, Tracking, and Reporting

Solicitation: Department of the Air Force FY26 SBIR Commercial Solutions Opening (CSO), Release 6, Phase I Proposal Submission Instructions

Program type: Phase I

Award maximum value: $150,000

Award maximum duration: 3 months

Technical volume page limit: 30 pages or slides

Sponsoring organizations: SpaceWERX, in partnership with Space Systems Command's Space Sensing System Delta 84 and the OPIR Tap Lab

Component Technology Priority Area: Space Technology

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Required proposal template: Space FY26 SBIR Phase I Proposal Template, from the DSIP supporting documents page

Minimum work performed in house: two-thirds of the research or analytical effort

Technical and Business Assistance: up to $6,500 per Phase I award

Named Phase III transition pipeline: the Space Modernization Initiative program within Space Systems Command's Space Sensing portfolio

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: SpaceWERX, space platforms, space sensing, Overhead Persistent Infrared, OPIR, data fusion, AI/ML, OODA, mission assurance

Note on the deadline time. The DAF instructions direct offerors to the DoW FY26 SBIR CSO for the proposal submission deadline date and time rather than restating it. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP topic posting and do not plan around an end-of-day deadline.

How Phase I Differs From the Direct to Phase II Release

If you have read the DAF Release 6 Direct to Phase II instructions, several rules here are different. Getting these wrong is an avoidable way to lose.

You must use the government template. All applicants must complete their Volume 2 Technical Volume proposal submission using the template provided at the DSIP supporting documents page, titled "Space FY26 SBIR Phase I Proposal Template." This is a stated requirement, not a suggestion, and it has no counterpart in the D2P2 instructions. Download it first and build inside it. Note also that the Phase I instructions do not restate the type size, margin, and page numbering rules that appear in the D2P2 instructions, which is consistent with the template governing format. Follow the template.

Two-thirds of the work must be yours. For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit. The D2P2 instructions set that floor at one-third, so this is a substantially tighter constraint. If your plan leans on a university partner or an outside data science firm, check the arithmetic before you commit.

The subcontract cap is one-third, not one-half. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, and profit is not included in that calculation. The instructions add that the SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. On a $150,000 award, one-third is roughly $50,000 for all outside costs combined.

TABA is $6,500, not $50,000. The DAF will provide up to $6,500 for each Phase I award. The Phase I instructions state that simply, without the detailed Volume 5 provider documentation requirements that the D2P2 instructions impose. If you intend to use it, ask the One Help Desk what documentation this cycle expects rather than assuming either the simple or the detailed process applies.

There is no Phase I feasibility eligibility gate. Direct to Phase II proposals get disqualified if prior feasibility documentation does not establish technical merit. Phase I has no such screen, and the Volume 5 list here carries only three conditional documents. The feasibility study in this topic is a Phase I deliverable, not an admission requirement. That makes this topic accessible to a company that has never held a SBIR award.

The protest citations differ. Protests here are prescribed under FAR 33.106(a) and FAR 52.233-2, versus FAR 33.106(b) and FAR 52.233-3 in the D2P2 instructions.

The support contractor list differs. The Phase I list names TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). The FFRDC evaluators named are MITRE and Aerospace Corporations working under contract to provide technical support to Air Force Life Cycle Management Center and Space and Missiles Centers.

What the Space Force Is Actually Looking For

The mission problem

The topic addresses a critical need within the U.S. Space Force's Missile Warning, Tracking, and Response mission by advancing the application of artificial intelligence and machine learning to improve multi-sensor fusion, missile tracking precision, and real-time situational awareness within a multi-orbit satellite framework covering GEO, MEO, and LEO.

The Air Force is specific about what is currently hard. Current technologies face challenges in fusing large volumes of disparate data across multiple sensing modalities, tackling latency in data processing, and accurately tracking increasingly sophisticated threats such as hypersonic and maneuverable missile systems.

Three distinct problems sit inside that sentence. Heterogeneous data fusion at volume. Latency. And targets that do not behave like ballistic objects. A proposal that addresses only one should say which one and why that is the highest-value place to start.

The Phase I objective

The objective of this Phase I effort is to evaluate the feasibility of applying innovative data processing techniques, including AI and ML methodologies, to address the evolving challenges in missile detection, warning, tracking, and reporting.

The primary goal of the research and development initiative is to advance data fusion, sensor integration, and real-time processing methods that enhance the accuracy, responsiveness, and reliability of satellite-based missile warning systems. That includes addressing data interoperability from multi-orbit GEO, MEO, and LEO satellite constellations, optimizing on-orbit and ground-based processing frameworks, and improving data quality from diverse sensing modalities across legacy and future Overhead Persistent Infrared space architectures.

Specifically, the effort will focus on researching and developing state-of-the-art algorithms and processing techniques that support rapid and precise multi-sensor fusion, robust target identification, and accurate real-time 3D tracking of traditional, hypersonic, and maneuverable missile threats. By leveraging novel techniques in data association, sensor fusion, and edge processing, the solution will aim to mitigate limitations presented by diverse sensor resolutions, data cadences, and observational geometries. The project will also investigate methods to increase computational efficiency for onboard satellite processing and consider robustness against noise in highly dynamic operational environments.

Four technical themes are worth pulling out of that because they are where a credible Phase I can differentiate. Data association across sensors with different resolutions, cadences, and observational geometries, which is the genuinely hard part of multi-orbit fusion. Real-time 3D tracking of maneuvering and hypersonic targets, where classical filters degrade. Computational efficiency sufficient for onboard satellite processing, meaning your algorithm has to survive a flight processor. And robustness against noise in highly dynamic environments.

The desired future state, in the Air Force's own words

Phase I will assess the feasibility of AI and ML driven multi-sensor fusion techniques for real-time advanced missile detection, warning, and tracking across multi-orbit satellite systems and data architectures. The desired future state of this effort is a network-aware, autonomous constellation spanning multiple orbital regimes where ground "migrates" with space via edge fusion that compresses timelines for the joint fight without loss of quality or confidence.

That sentence is the vision statement to write toward. Ground migrating with space via edge fusion means moving processing that today happens in ground stations onto the constellation itself. Compressing timelines without loss of quality or confidence is the constraint: faster is only valuable if the answer is still trustworthy, which is why explainability appears later in the topic.

What Phase I is actually for

The goal of this Phase I effort is to onboard and coordinate emergent solutions into the OPIR Tap Lab and create a shared understanding of the problem set of the Missile Warning and Tracking mission area. Successful Phase I efforts from this topic will target capability testing within the OPIR Tap Lab, with the goal of advancing capability and de-risking follow-on capability development in subsequent phases.

Proposed solutions should include a feasibility study and algorithm prototypes or simulation results as applicable, as well as a clear path to integration and testing within the OPIR Tap Lab.

The OPIR Tap Lab is named in the topic references at boulderlab.org. Understanding what it is, how outside companies engage with it, and what integration there requires is probably the highest-return hour of research you can spend before writing. Your clear path to integration and testing is an explicit proposal requirement, and it cannot be written credibly from the outside.

The four focused topic areas

The topic states that focused topic areas can include any part of the following, which is permissive language. You may address one, several, or elements across them.

Edge Fusion and Autonomy. AI and ML solutions for on-orbit track fusion, autonomous constellation tasking, and event-driven scheduling across proliferated MEO and LEO architectures in contested environments.

Multi-Source Integration. Capabilities that fuse OPIR, electro-optical, radar, signals intelligence, and commercial sensor data to improve detection, tracking, typing, and characterization, with scalable software architectures and ML-driven sensor calibration.

Observe, Orient, Decide, Act Loop Collapse and Mission Assurance. Solutions that accelerate the sensor-to-decision-maker kill chain with sufficient confidence and explainability to assure mission-critical decisions. These can include but are not limited to dynamic user control of automation covering command and control, operator overload, and scalable operations, plus orchestration, edge computing, AI trade-space exploration, and authoritative knowledge access.

New sources and methods for Missile Warning that are outside of the current missile warning operational paradigm tactics, techniques, and procedures.

That fourth area is unusual and deserves attention. It is an explicit invitation to propose something that does not fit current TTPs. Most SBIR topics reward alignment with existing practice. This one carves out space for an approach the mission area has not tried. If your technology is genuinely orthogonal to how missile warning is done today, that is the area to claim, and the topic gives you cover for it.

Note also the phrase "sufficient confidence and explainability to assure mission-critical decisions" in the third area. For an AI proposal in a nuclear-adjacent warning mission, explainability is not a feature request, it is the precondition for the capability being usable at all. Address it directly.

The Feasibility Study and CONOPS Requirements

This is the most prescriptive part of the topic, and it is where your Phase I deliverable is defined. The Air Force tells you what a feasibility study is and what it must contain.

What the feasibility study must do

A feasibility study is an assessment of the practicality of developing and implementing a new technology within a given concept. The study aims to objectively and rationally uncover the strengths and weaknesses of the new technology, the feasibility of successful development of the technology, and the viability of the success of implementation of the technology in the proposed CONOPS.

The study should do four things.

Identify the benefits of the new technology within the CONOPS over existing solutions, or the lack thereof. Note the parenthetical. The Air Force is asking you to be honest where no existing solution exists, rather than manufacturing a comparison.

Identify the risks, uncertainties and unknowns, and issues of the proposed CONOPS with mitigation and closure measures. Both mitigation and closure, meaning how a given uncertainty gets resolved, not just managed.

Identify the critical technology elements of the new technology. Critical technology elements, or CTEs, is deliberate systems engineering vocabulary. Use it.

Provide data to support the feasibility of technology development of each CTE, to include literature research supporting technical viability or historical usage, trade studies identifying existing technologies, current developments, and feasible development pathways, analysis demonstrating technical solutions, and heritage usage of similar technology with identified differences in operations or environment for the proposed CONOPS.

That last item is the workload of the award. Per critical technology element, you owe literature research, trade studies, analysis, and a heritage comparison that names how your environment differs. Three months is enough time for that only if you scope the CTE list tightly. Identify four or five critical technology elements, not fifteen.

What the CONOPS must do

The Concept of Operations should clearly communicate how the technology is intended to support a military mission within a defined system. The main purpose of the CONOPS is to facilitate a common understanding of a future system to help develop operational and system-level requirements. CONOPS should be written at the system level first and then expanded on how the technology functions enable successful military operations.

That ordering instruction is specific and easy to get backwards. System level first, then how your technology's functions enable the mission. A CONOPS that starts from your algorithm and works outward is written in the wrong direction. Start with the missile warning system and the operational sequence, then place your contribution inside it.

Phase I deliverables are expected to focus on a feasibility study detailing USSF CONOPS and technical viability, as well as analytical findings. The Air Force also notes that a Phase II transition concept may be outlined, so a forward-looking section is welcome but is not the deliverable.

Phase II and Phase III

Phase II

Phase II aims to build off the work completed in Phase I after successfully demonstrating capability for operational use within the OPIR Tap Lab or similar environments that demonstrate integrating advanced AI and ML for real-time multi-sensor fusion and missile tracking from OPIR systems.

Activities include system development, integration, and testing in operationally relevant environments to verify performance metrics such as accuracy, latency, resilience, and coverage. Phase II will mature the feasible concepts identified in Phase I into a deployable, testable prototype, and will include design refinement, system development, and operationally relevant testing focused on delivering a measurable improvement in AI and ML techniques to detect or accurately fuse any source detecting these threats, either on the ground in the traditional processing ground stations or on board via edge processing.

The four named performance metrics, accuracy, latency, resilience, and coverage, are worth building your Phase I analytical findings around. If your feasibility study produces baseline estimates against those four, you have handed the government the measurement framework for your own Phase II.

The pathway is stated explicitly: successful Phase I efforts establish technical feasibility and transition the validated proof-of-concept into the OPIR Tap Lab or a similar testbed, and Phase II efforts continue development of technologies coming out of the OPIR Tap Lab. By using that operationally relevant environment, the work progresses to system development, integration, and testing, which de-risks follow-on capability development. The ultimate goal of the pathway is to mature the feasible concepts into a deployable, testable working prototype delivering a measurable improvement in techniques for multi-sensor fusion and missile detection, warning, tracking and reporting.

How Phase II gets requested, which matters for planning

The Phase I instructions describe a Phase II process that is not applicant-initiated on a fixed calendar. DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the conclusion of the period of performance. The decision is based on the awardee's technical progress, as determined by a DAF Technical Point of Contact review using the Phase II review criteria.

Only Phase I awardees are eligible to submit a Phase II proposal. All Phase I awardees will be sent a notification with the Phase II proposal submittal date and detailed preparation instructions. Phase II dollar values, performance periods, and proposal content will be specified in the Phase II request for proposal. Only one Phase II proposal may be submitted for each Phase I award. If your physical or email addresses or firm points of contact have changed since Phase I submission, send corrected information to the DAF SBIR/STTR One Help Desk.

Two practical consequences. First, because the request can come while Phase I performance is still ongoing, and because it is based on demonstrated technical progress, front-loading real analytical results rather than saving them for the final report is strategically sensible on a three month award. Second, the DAF reserves the right to modify Phase II submission requirements and will notify all Phase I awardees if requirements change.

The instructions also note that the DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts, but awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system. If the company intends to continue work with the Department of War, an approved accounting system will allow competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts. That is worth acting on early if you expect a defense business, since DCAA accounting system approval is not a quick process.

Phase III

Potential Phase III efforts will pursue transition of the capability to operational use through non-SBIR/STTR funding streams, aiming for a Technology Readiness Level of 6 or 7 and demonstrating functionality in relevant environments.

A key transition pipeline for this capability is the Space Modernization Initiative program within Space Systems Command's Space Sensing portfolio. Successful efforts in potential Phase III efforts will involve full integration into OPIR operational data workflows and fielding the capability at scale to provide recurring operational value and reduce warfighter risk by expanding OPIR sensing capabilities.

A named transition pipeline is a gift in a SBIR topic, because it answers the question every proposal has to answer about what happens after the money runs out. Reference the Space Modernization Initiative and Space Systems Command's Space Sensing portfolio explicitly in your commercialization and future R&D discussion.

The topic cites the GAO Technology Readiness Assessment Guide as a reference, at gao.gov/assets/gao-20-48g.pdf. Since the Phase III target is stated as TRL 6 or 7, use GAO's definitions rather than an informal scale when you make maturity claims.

Funding Allowance and Cost Structure

Award ceiling and what it buys

Up to $150,000 across up to 3 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The DAF adds, in the evaluation section, that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.

Be realistic about what three months and $150,000 supports. Roughly speaking this is a small team for a quarter. That is enough for a rigorous feasibility study with a bounded CTE list, a literature and trade study foundation, some simulation work against representative data, and an integration plan for the OPIR Tap Lab. It is not enough for a demonstration against real OPIR data on a flight-representative processor. Propose the former convincingly rather than the latter aspirationally, because cost realism is assessed inside the most important evaluation criterion.

Contract type

The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts.

The instructions add a significant procedural note: if no exceptions are taken to an offeror's proposal, the Government may award a contract without negotiations. Therefore the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen negotiations later if the Contracting Officer determines doing so to be necessary.

Technical and Business Assistance

The Small Business Innovation and Economic Security Act Section 7 mandates agencies to offer TABA, and the DAF will provide up to $6,500 for each Phase I award.

The Phase I instructions state this in a single sentence, without the detailed provider documentation requirements the D2P2 instructions impose. Because the two documents in the same release treat TABA differently, and because TABA requests are commonly denied on documentation grounds, ask the DAF SBIR/STTR One Help Desk during the open period what Phase I TABA documentation this cycle requires and where it goes.

Cost volume requirements

Cost information should be provided by completing the Cost Volume in DSIP and including the Cost Volume Itemized Listing. The cost volume detail must be adequate to enable Air Force personnel to determine the purpose, necessity, and reasonableness of each cost element.

A helpful mechanical point: the DSIP Cost Volume and Itemized Cost Volume Information will not count against the specified page limit. The itemized listing also may be submitted in Volume 5 under the "Other" dropdown option.

The seven categories the instructions name:

Direct cost materials. Justify costs for materials, parts, and supplies with an itemized list containing types, quantities, prices, and where appropriate purpose. Material costs may include raw materials, parts, subassemblies, components, and manufacturing supplies.

Other direct costs. Includes but is not limited to specialized services such as machining, milling, special testing or analysis, and costs incurred in temporarily using specialized equipment. Proposals including leased hardware must include an adequate lease versus purchase justification. Compute time, if you are running significant simulation or model training, belongs here with justification.

Direct labor. Identify key personnel by name if possible, or by labor category if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a study award this will be nearly the whole budget, so it deserves the most care.

Travel. Travel costs must relate to project needs. Break out travel costs by trip, number of travelers, airfare, per diem, lodging, and similar. The number of trips required, as well as the destination and purpose of each, should be reflected. The instructions recommend budgeting at least one trip to the Air Force location managing the contract. On this topic, that recommendation reads as an opportunity: a trip to engage the OPIR Tap Lab supports the integration path the topic asks you to define.

Subcontracts. Involvement of university or other consultants in the project's planning or research stages may be appropriate. If so, describe in detail and include information in the Cost Volume. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, and profit is not included in the calculation, unless otherwise approved in writing by the Contracting Officer. The SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. Support subcontract costs with copies of executed agreements that adequately describe the work to be performed, and at a minimum include a Statement of Work with a corresponding detailed Cost Volume for each planned subcontract.

Special tooling, special test equipment, and material. Inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an offeror would otherwise possess in the normal course of business, and may include items such as innovative instrumentation or automatic test equipment.

Consultants. Provide a separate agreement letter for each consultant. The letter should briefly state what service or assistance will be provided, the number of hours required, and the hourly rate.

Where work must be performed

All research and research and development work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States. The awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking this approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission.

Performance of work deviations

Occasionally the DAF will consider deviations from the performance of work requirement. Requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove requesting applicants to proceed with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award.

Given the two-thirds in-house requirement on Phase I, this process is more likely to be relevant here than on a D2P2 topic. If a university collaborator is central to your approach, start the deviation request early in the open period.

Export Control and Foreign Nationals

The technology within this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including export of sensitive technical data, and the EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by the foreign nationals in accordance with section 3.5 of the Announcement. Offerors are advised that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

Missile warning is among the more sensitive mission areas in the portfolio, so treat this as a real constraint rather than a disclosure formality. AI and ML teams are frequently internationally staffed, and resolving who can work on what should happen before you write your key personnel section, not after selection. If you are asserting export-controlled status, a certified DD Form 2345 Militarily Critical Technical Data Agreement, or evidence of application submission, is a Volume 5 document, and DD Form 2345 approval will be required if the proposal is selected for award. The form, instructions, and FAQs are at the United States and Canada Joint Certification Program website.

Proposal Structure: The Seven Volumes

Complete proposals must include Volume 1 Cover Sheet, Volume 2 Technical Volume, Volume 3 Cost Volume, Volume 4 Company Commercialization Report, Volume 5 Supporting Documents, Volume 6 Fraud, Waste, and Abuse Training, and Volume 7 Disclosures of Foreign Affiliations or Relationships to Foreign Countries.

Volume 1, Cover Sheet

Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.

The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released, so keep sensitive algorithmic detail out of both.

Volume 2, Technical Volume

All applicants must complete their Volume 2 Technical Volume proposal submission using the template provided at the DSIP supporting documents page, titled "Space FY26 SBIR Phase I Proposal Template."

Include a work plan outline in the following format:

Scope. List the effort's major requirements and specifications.

Task Outline. Provide a brief outline of the work to be accomplished during the Phase I effort.

Milestone Schedule.

Deliverables.

Progress reports.

Final report with SF 298.

Two notes. First, the required work plan outline here is much lighter than the D2P2 work plan, which demanded a separately paginated contract-language document with numbered task hierarchies. Phase I asks for an outline. Do not over-build it, but do include every named element, since omissions in a prescribed format are the cheapest kind of avoidable finding.

Second, the SF 298 is the Report Documentation Page, a standard form that accompanies a technical report. Naming it in the deliverables list means your final report needs it, so account for that rather than discovering it at closeout.

The technical volume page limit for this topic is 30 pages or slides, from the topic index. Note that the limit is expressed as pages or slides, so a slide-format submission is acceptable within whatever structure the template provides. Thirty pages is generous relative to the size of the award, which means the constraint on this proposal is analytical substance rather than space. Use the room for the feasibility study structure, the CTE analysis, and the CONOPS.

Volume 3, Cost Volume

Covered above. Remember that the DSIP Cost Volume and Itemized Cost Volume Information do not count against the page limit, and the itemized listing may also be submitted in Volume 5 under the "Other" dropdown.

Volume 4, Company Commercialization Report

Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. The instructions state that information contained in the CCR will not be considered by the Air Force during proposal evaluations. Complete it for compliance and do not treat it as a scoring opportunity. This matches the D2P2 instructions and differs from Army SBIR practice, where the CCR is considered.

Volume 5, Supporting Documents

Three documents may be required if applicable to your proposal.

DD Form 2345. For proposals submitted under export-controlled topics, either ITAR or EAR, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission must be included. This topic is export controlled, so this applies. DD Form 2345 approval will be required if the proposal is selected for award.

Verification of Eligibility of Small Business Joint Ventures, which is Attachment 3 to the FY26 SBIR CSO.

Technical Data Rights Assertions, if asserting data rights restrictions. For an AI and ML company whose core asset is existing models, code, and training pipelines built with private investment, this is the mechanism for protecting that background intellectual property. Do not skip it because the award is small.

Note what is absent. There is no Phase I feasibility documentation requirement in Volume 5, because Phase I is where feasibility gets established rather than where it must be proven in advance.

Volume 6, Fraud, Waste, and Abuse Training

Fraud, Waste and Abuse training material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission. Complete this before you need it, since it gates submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the Disclosures of Foreign Affiliations or Relationships to Foreign Countries webform in Volume 7 of the DSIP proposal submission. The form will not be accepted as a PDF supporting document in Volume 5, and previous versions of the form must not be uploaded to Volume 5. For additional details, refer to the DoW SBIR Program CSO.

How Your Proposal Will Be Evaluated

The criteria

Proposals will be evaluated for overall merit in accordance with the criteria below in descending order of importance. The DAF is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic. Multiple procurements are planned and anticipated, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals.

Criteria A, most important. The soundness, technical merit, and innovation of the proposed approach and its incremental progress toward topic or subtopic solution, and the qualifications of the proposed principal and key investigators, supporting staff, and consultants. This includes whether the proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the unique methods of performance and materials described in the technical proposal.

Criteria B, second. The degree of mission impact and the urgency of the identified need. The specificity of the defense requirement addressed. The adequacy of the proposed effort in fulfilling the research topic or subtopic solution.

Criteria C, third. The potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

Three observations. Cost realism sits inside Criteria A, so on a three month award the proposal that promises too much is penalized on the top criterion, not on price. The phrase "incremental progress toward topic or subtopic solution" rewards a clearly bounded step, which fits a feasibility study well, so do not apologize for the modest scope. And qualifications of key personnel are inside the top criterion, which on an AI and ML topic means the credibility of your technical team relative to sensor fusion and tracking, not just to machine learning generally.

Due diligence and foreign risk

15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of War, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.

The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures the DAF will use include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.

The DAF will assess using a risk-based approach as appropriate: cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks, and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the small business concern to an entity, including any affiliates of the entity, or individual on any of eight named lists: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; and the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.

The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified, or has a security risk the DAF determines warrants a denial.

If the DAF denies an award under 15 U.S.C. 638(g)(16) or 638(o)(20), or upon determining the concern has a security risk described in that paragraph, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same notification approach applies to denials under 15 U.S.C. 638(vv).

For an AI and ML company, three items on that list deserve a look before you propose. Cybersecurity practices, which leads the list and connects to the CMMC Level 2 self-assessment projection for this topic. Patent analysis, since machine learning patent portfolios often have international co-assignees or co-inventors. And employee analysis together with foreign affiliations, which in this field frequently means academic affiliations abroad.

Ownership and support contractors

Small business concerns that are owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF Topics.

Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors. These support contractors may include, but are not limited to, TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to Air Force Life Cycle Management Center and Space and Missiles Centers may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the Air Force SBIR/STTR Contracting Officer, Daniel J. Brewer, with concerns regarding the use of support contractors.

Status, feedback, and protests

The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.

Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions, since separate notifications are provided for each proposal.

The Air Force anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the CSO Contracting Officer for proposal status before that time.

Refer to the DoW SBIR Program CSO for procedures to protest the Announcement. As further prescribed in FAR 33.106(a) and FAR 52.233-2, protests should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer. The DAF uses its best efforts to resolve concerns raised by interested parties at the contracting officer level through open and frank discussions, and for agency protests the DAF provides for inexpensive, informal, procedurally simple, and expeditious resolution of protests.

All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 3 months from award

Phase II: requested by DAF organizations based on technical progress, either during Phase I performance or any time after it concludes, with only Phase I awardees eligible and one Phase II proposal permitted per Phase I award

A working backward plan

Before September 23. Download the Space FY26 SBIR Phase I Proposal Template from the DSIP supporting documents page and read it before you write anything, because it dictates your structure. Research the OPIR Tap Lab, since a clear path to integration and testing there is an explicit proposal requirement. Decide which of the four focused topic areas you are claiming. Draft your critical technology element list and keep it short enough for three months of real analysis. Resolve export control staffing questions and start DD Form 2345 if you do not hold one. Inventory your background intellectual property so you can assert data rights properly. Check your work distribution against the two-thirds in-house requirement, and if a university collaborator is central, start the Performance of Work deviation request now, since it must be made during the open period as well as with the proposal. Complete Volume 6 training, verify SAM registration and DSIP account alignment, and send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries and warns that late ones constrain its ability to respond. Ask about Phase I TABA documentation while you are there.

September 23 through October 3. Build the technical volume inside the template. Write the CONOPS at the system level first, then expand into how your technology's functions enable the mission, following the topic's stated ordering. Structure the feasibility study around the four required elements: benefits over existing solutions or the lack thereof, risks and unknowns with mitigation and closure measures, critical technology elements, and supporting data per CTE covering literature research, trade studies, analysis, and heritage usage with identified differences.

October 4 through October 12. Complete the work plan outline with all six named elements: scope, task outline, milestone schedule, deliverables, progress reports, and final report with SF 298. Build the cost volume and itemized listing, remembering neither counts against the page limit. Include at least one trip to the Air Force location managing the contract, which the instructions recommend and which on this topic supports your OPIR Tap Lab engagement. Get separate agreement letters from each consultant and executed agreements with statements of work and detailed cost volumes for each planned subcontract. Verify all outside costs stay under one-third of the contract price with profit excluded.

October 13 through October 16. Assemble Volume 5 with DD Form 2345 and Technical Data Rights Assertions, complete the Volume 7 webform, finish the Volume 4 CCR, and run a compliance pass against the template and the 30 page or slide limit. Confirm no proprietary or classified content in the technical abstract, which will be publicly released if you are selected.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-NV510?

‍ ‍

DAF26BX06-NV510 is a Department of the Air Force SBIR Phase I topic titled "AI/ML for Next Generation of Missile Detection, Warning, Tracking, and Reporting," released under the DAF FY26 SBIR Commercial Solutions Opening, Release 6. SpaceWERX, in partnership with Space Systems Command's Space Sensing System Delta 84 and the OPIR Tap Lab, seeks to evaluate the feasibility of applying AI and ML data processing to multi-sensor fusion, missile tracking, and real-time situational awareness across GEO, MEO, and LEO satellite architectures.

‍ ‍

How much funding is available under DAF26BX06-NV510?

‍ ‍

Up to $150,000 for a period of performance up to 3 months. Proposals in excess of that amount or that duration will not be considered for evaluation or award. Up to $6,500 in Technical and Business Assistance is available for each Phase I award.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct offerors to the DoW FY26 SBIR CSO for the exact submission time, which is ordinarily 12:00 p.m. Eastern on the close date. Confirm the time on the live DSIP topic posting rather than assuming end of day.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

Do I have to use a specific proposal template?

‍ ‍

Yes. All applicants must complete their Volume 2 Technical Volume submission using the template provided at the DSIP supporting documents page, titled "Space FY26 SBIR Phase I Proposal Template." Download it before you start writing. This requirement has no counterpart in the DAF Direct to Phase II instructions.

‍ ‍

How long can my technical volume be?

‍ ‍

30 pages or slides, per the topic index. Pages or slides in excess of that number will not be considered during evaluations. The DSIP Cost Volume and Itemized Cost Volume Information do not count against the limit.

‍ ‍

What is the work plan outline format?

‍ ‍

Six named elements: Scope, listing the effort's major requirements and specifications; Task Outline, a brief outline of the work to be accomplished during Phase I; Milestone Schedule; Deliverables; Progress reports; and Final report with SF 298.

‍ ‍

What is the SF 298?

‍ ‍

The Report Documentation Page, a standard form that accompanies a technical report. It is named in the required work plan outline as part of the final report deliverable, so plan for it rather than discovering it at closeout.

‍ ‍

How much of the work must my company perform?

‍ ‍

For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit. Note this is substantially tighter than the one-third floor in the DAF Direct to Phase II instructions.

‍ ‍

What is the cap on subcontracts and consultants?

‍ ‍

The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded from the calculation, unless otherwise approved in writing by the Contracting Officer. On a $150,000 award that is roughly $50,000 for all outside costs combined. The Direct to Phase II cap is one-half, so do not carry that assumption over.

‍ ‍

Can I get a waiver on the performance of work requirement?

‍ ‍

Occasionally the DAF will consider deviations. Requests must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. For requests before submission, the DAF will approve or disapprove the applicant proceeding with DSIP submission, then reconsider upon proposal receipt for the resultant award. The DAF will not consider these requests prior to proposal submission opening.

‍ ‍

What does the feasibility study have to contain?

‍ ‍

Four things. Identify the benefits of the new technology within the CONOPS over existing solutions, or the lack thereof. Identify the risks, uncertainties and unknowns, and issues of the proposed CONOPS with mitigation and closure measures. Identify the critical technology elements of the new technology. And provide data supporting the feasibility of technology development of each CTE, including literature research supporting technical viability or historical usage, trade studies identifying existing technologies, current developments, and feasible development pathways, analysis demonstrating technical solutions, and heritage usage of similar technology with identified differences in operations or environment for the proposed CONOPS.

‍ ‍

How should I write the CONOPS?

‍ ‍

At the system level first, then expanded on how the technology functions enable successful military operations. That ordering is specified in the topic. The CONOPS should clearly communicate how the technology is intended to support a military mission within a defined system, and its main purpose is to facilitate a common understanding of a future system to help develop operational and system-level requirements.

‍ ‍

What are the focused topic areas?

‍ ‍

Four, and the topic says focused areas can include any part of them. Edge Fusion and Autonomy, covering AI and ML for on-orbit track fusion, autonomous constellation tasking, and event-driven scheduling across proliferated MEO and LEO architectures in contested environments. Multi-Source Integration, fusing OPIR, EO, radar, SIGINT, and commercial sensor data to improve detection, tracking, typing, and characterization with scalable software architectures and ML-driven sensor calibration. OODA Loop Collapse and Mission Assurance, accelerating the sensor-to-decision-maker kill chain with sufficient confidence and explainability to assure mission-critical decisions. And new sources and methods for Missile Warning outside the current missile warning operational paradigm tactics, techniques, and procedures.

‍ ‍

What if my approach does not fit current missile warning practice?

‍ ‍

The fourth focused topic area explicitly invites new sources and methods outside the current missile warning operational paradigm TTPs. That is unusual in a SBIR topic and gives cover for a genuinely orthogonal approach. Claim that area and say why the current paradigm limits the outcome.

‍ ‍

What is the OPIR Tap Lab and why does it matter?

‍ ‍

The OPIR Tap Lab is a government lab named as the destination for Phase I work, referenced in the topic at boulderlab.org. The stated Phase I goal is to onboard and coordinate emergent solutions into the OPIR Tap Lab and create a shared understanding of the Missile Warning and Tracking mission area problem set. Successful Phase I efforts will target capability testing there. Proposed solutions must include a clear path to integration and testing within the OPIR Tap Lab, which makes understanding how the lab engages outside companies essential before you write.

‍ ‍

What are the Phase I deliverables?

‍ ‍

Phase I deliverables are expected to focus on a feasibility study detailing USSF CONOPS and technical viability, as well as analytical findings. Proposed solutions should include a feasibility study and algorithm prototypes or simulation results as applicable, plus a clear path to integration and testing within the OPIR Tap Lab. A Phase II transition concept may be outlined. The research plan can include modeling, simulation, literature review, or trade studies.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for them. The topic advises that foreign nationals proposed to perform may be restricted due to the technical data involved. A certified DD Form 2345, or evidence of application submission, belongs in Volume 5, and approval will be required if selected for award.

‍ ‍

How is my proposal evaluated?

‍ ‍

Under three criteria in descending order of importance. Criteria A, most important, covers soundness, technical merit, and innovation of the proposed approach, its incremental progress toward topic or subtopic solution, the qualifications of the principal and key investigators, supporting staff, and consultants, and whether proposed cost elements are realistic, reflect a clear understanding of the requirements, and are consistent with the methods and materials in the technical proposal. Criteria B covers degree of mission impact, urgency of the identified need, specificity of the defense requirement, and adequacy of the effort. Criteria C covers commercial application potential.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state information contained in the CCR will not be considered by the Air Force during proposal evaluations.

‍ ‍

Do I need prior SBIR experience or existing feasibility documentation?

‍ ‍

No. Unlike the Direct to Phase II topics in this release, Phase I has no feasibility eligibility gate and Volume 5 carries only three conditional documents. The feasibility study here is a Phase I deliverable, not an admission requirement, which makes this topic accessible to a company that has never held a SBIR award.

‍ ‍

How do I get to Phase II?

‍ ‍

You do not apply on a calendar. DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the period of performance concludes, based on the awardee's technical progress as determined by a DAF Technical Point of Contact review. Only Phase I awardees are eligible. All Phase I awardees will be sent a notification with the Phase II submittal date and detailed preparation instructions, and Phase II dollar values, performance periods, and proposal content will be specified in that request. Only one Phase II proposal may be submitted for each Phase I award.

‍ ‍

Since Phase II can be requested during Phase I, should I change how I schedule the work?

‍ ‍

It is worth considering. Because a Phase II request can arrive while Phase I performance is still ongoing and is based on demonstrated technical progress, producing real analytical results early rather than holding everything for the final report gives a reviewing Technical Point of Contact something to act on. On a three month award that argues for front-loading substance.

‍ ‍

What contract type should I expect?

‍ ‍

The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts. Awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system, since if the company intends to continue work with the Department of War an approved accounting system allows competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts.

‍ ‍

Will I be able to negotiate after submitting?

‍ ‍

Possibly not. If no exceptions are taken to your proposal, the Government may award a contract without negotiations, so your initial proposal should contain your best terms from a cost or price and technical standpoint. The Government reserves the right to reopen negotiations later if the Contracting Officer determines it necessary.

‍ ‍

How do I protect my existing AI models and code?

‍ ‍

Technical Data Rights Assertions is a listed Volume 5 document if you are asserting data rights restrictions. For a company whose core asset is models, code, and training pipelines developed with private investment, this is the mechanism for distinguishing background intellectual property from what you develop under the award. Do not skip it because the award is small.

‍ ‍

What is TABA on this topic and how do I request it?

‍ ‍

The DAF will provide up to $6,500 for each Phase I award. The Phase I instructions state this in one sentence without the detailed provider documentation requirements the Direct to Phase II instructions impose. Because the two documents in the same release treat TABA differently, ask the DAF SBIR/STTR One Help Desk during the open period what Phase I TABA documentation this cycle requires and where it belongs.

‍ ‍

What happens in Phase III?

‍ ‍

Potential Phase III efforts will pursue transition to operational use through non-SBIR/STTR funding streams, aiming for TRL 6 or 7 and demonstrating functionality in relevant environments. A key transition pipeline is the Space Modernization Initiative program within Space Systems Command's Space Sensing portfolio. Successful Phase III efforts will involve full integration into OPIR operational data workflows and fielding the capability at scale to provide recurring operational value and reduce warfighter risk by expanding OPIR sensing capabilities.

‍ ‍

Are venture-backed companies eligible?

‍ ‍

Yes. Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

‍ ‍

When will I hear about selection?

‍ ‍

The Air Force anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal submitted.

‍ ‍

Will I get feedback if not selected?

‍ ‍

Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

‍ ‍

Who do I contact with questions?

‍ ‍

For general information related to the AF SBIR/STTR program and proposal preparation instructions, contact the AF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us. The DAF encourages applicants to request clarifying information as early as possible, since delays in such requests constrain the DAF's ability to provide satisfactory resolution to applicant concerns. For questions regarding the DSIP electronic submission system, contact the DoW SBIR/STTR Help Desk at dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the DoW FY26 SBIR CSO. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. If your company mail or email addresses or points of contact change after proposal submission, provide the information to the AF SBIR/STTR One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Understand what you are buying with this proposal. At $150,000 over three months, the award itself is not the prize. The prize is being onboarded into the OPIR Tap Lab and becoming part of the shared understanding of the Missile Warning and Tracking problem set, with a named Phase III pipeline in the Space Modernization Initiative behind it. Write the proposal as an entry into a relationship, and be explicit about the integration path, because that is what the topic asks for and what the government is actually buying.

‍ ‍

Do the OPIR Tap Lab homework before you write. A clear path to integration and testing within the lab is a stated proposal requirement. What data is available there, what interfaces exist, how outside algorithms get evaluated, and what the onboarding process involves are all things you should know before drafting. A generic statement that you would like to integrate is not a path.

‍ ‍

Scope the critical technology element list tightly. Per CTE you owe literature research, trade studies, analysis demonstrating technical solutions, and heritage usage with identified differences. Three months buys that for a handful of elements, not for a dozen. Four or five well-analyzed CTEs will read as rigorous; fifteen thin ones will read as unserious and will hurt you on cost realism inside the top criterion.

‍ ‍

Write the CONOPS in the order the topic specifies. System level first, then how your technology's functions enable successful military operations. Most AI companies naturally write outward from the algorithm. This topic asks for the reverse, and following the instruction is free points.

‍ ‍

Make explainability a first-class part of the approach. The OODA loop area asks for sufficient confidence and explainability to assure mission-critical decisions. In a warning mission, an unexplainable output is unusable regardless of accuracy. Treat confidence quantification and explainability as design requirements, not as a paragraph near the end.

‍ ‍

Address the hard fusion problem specifically. Diverse sensor resolutions, data cadences, and observational geometries is where multi-orbit fusion actually breaks. Naming that problem precisely and describing your data association approach against it is the fastest way to signal that you understand the mission rather than the buzzwords.

‍ ‍

Take onboard processing seriously. The topic asks about computational efficiency for onboard satellite processing. An algorithm that only works on a ground cluster answers half the question, because the desired future state is ground migrating with space via edge fusion. State your compute budget assumptions.

‍ ‍

Consider claiming the fourth focused area if it fits. New sources and methods outside current missile warning TTPs is an explicit invitation to be different. Few topics offer that, and if your approach genuinely does not fit today's paradigm, that framing turns a weakness into responsiveness.

‍ ‍

Check the two-thirds rule against your team plan early. Phase I requires you to perform two-thirds of the research or analytical effort in house, and all outside costs to stay under one-third of contract price. AI and ML proposals often lean on academic collaborators. If yours does, either restructure or start the Performance of Work deviation request during the open period, since it must be made before submission as well as with the proposal.

‍ ‍

Assert your data rights. Your models and pipelines predate this award. Technical Data Rights Assertions in Volume 5 is how you keep that boundary clear, and a small Phase I is exactly the situation where companies neglect it and regret it later.

‍ ‍

Budget the trip. The instructions recommend at least one trip to the Air Force location managing the contract. On a topic built around integration into a specific lab, that trip is substantive rather than administrative. Put it in the cost volume with a stated purpose.

DAF SBIR DAF26BX06-DV513: Autonomous On Orbit Logistics and Sustainment Architecture

Quick Answer

DAF26BX06-DV513 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. The Space Force wants prototype-ready technologies that enable a complete on-orbit logistics enterprise: autonomous resupply, refueling, repair, recovery, and reconstitution of United States space assets across Low Earth Orbit, Medium Earth Orbit, Geosynchronous Orbit, and cislunar space. The stated goal is a logistics architecture that mirrors the resilience and flexibility of terrestrial sustainment systems while adapting to the unique constraints of orbital mechanics. Awards are up to $1,000,000 for up to 12 months, with a 15 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

This is the smallest award, the shortest period of performance, and the tightest page limit in the release, which tells you something about how to scope a proposal. A twelve month, one million dollar effort is not going to build a servicing vehicle. It is going to prototype one clearly bounded piece of the logistics enterprise and demonstrate it. The topic accommodates that by offering six focus areas and requiring you to address at least one, plus two alternative architectural framings you may choose between. Precision of scope is the whole game here.

Topic At a Glance

Topic number: DAF26BX06-DV513

Title: Autonomous On Orbit Logistics and Sustainment Architecture

Solicitation: Department of the Air Force 2026 SBIR Commercial Solutions Opening (CSO), Release 6, Direct to Phase II

Program type: Direct to Phase II (D2P2), no Phase I awards will be made for this topic

Award maximum value: $1,000,000, the smallest in this release

Award maximum duration: 12 months, the shortest in this release

Technical volume page limit: 15 pages or slides, the tightest in this release

Component Technology Priority Area: Sustainment and Logistics

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Orbital regimes in scope: Low Earth Orbit, Medium Earth Orbit, Geosynchronous Orbit, and cislunar space

Focus areas: six, and D2P2 proposals must address at least one

Architectural frameworks offered: two, Systems of Systems or Logistics Function, and you must identify which you are using

Named sponsor reference: Space Access PAE is identified as seeking prototype-ready propellant technologies

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: on-orbit sustainment, space logistics, orbital refueling, propellant transfer, in-space servicing, rendezvous and proximity operations, sustained maneuver, space mobility, depot architecture, spacecraft resilience, cislunar logistics, SDP 4-0

Note on the deadline time. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the submission deadline date and time. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting rather than assuming end of day.

What the Space Force Is Actually Trying to Change

The problem with how satellites are built today

Space systems today are designed for single use and lack the ability to be maintained, repaired, or resupplied once deployed. The Space Force is direct about the consequences: this design philosophy limits maneuverability, reduces resilience, and forces operators to conserve resources.

That last consequence is the operational one. A satellite with finite propellant and no prospect of resupply is a satellite whose operators ration maneuver. If maneuver warfare is emerging in the space domain, as the topic asserts, then rationing maneuver is a losing posture.

What the Space Force says it requires is a logistics backbone that provides freedom of action, operational reach, and prolonged endurance, supporting rapid reconstitution, autonomous servicing, multi orbit distribution, and predictive sustainment.

What the topic is asking for

The On Orbit Space Logistics Challenge seeks mature technologies that can transition directly into prototype development. These technologies must support a future in which satellites are serviced, refueled, repaired, repositioned, and recovered as part of routine operations.

The D2P2 effort will focus on autonomous operations, multi orbit integration, servicing demonstrations, depot interactions, and logistics health monitoring. The performer must demonstrate how their technology contributes to a resilient logistics architecture capable of supporting sustained operations in contested environments.

The topic encourages solutions that integrate with broader Space Force concepts such as sustained space maneuver, dynamic space operations, and contested logistics. The performer must show how their technology supports mission continuity, reduces reconstitution burden, and enhances the survivability of critical space assets.

Those three outcomes, mission continuity, reduced reconstitution burden, and enhanced survivability, are the value statement the Space Force wants you to make. Whatever you propose, tie it back to at least one of them explicitly.

The Two Architectural Frameworks: Pick One and Say Which

This is an unusual and helpful structural feature of the topic. Offerors may structure their approach using one of two acceptable architectural frameworks. Both are valid for early exploration and concept development, and both support the broader goal of building a resilient on orbit logistics enterprise. Offerors should select the approach that best aligns with their proposed technology, their integration pathway, and the operational problem they intend to solve.

Critically, the topic states that the proposer must clearly identify which approach they are using and explain why it is appropriate for their concept. That is a compliance requirement, not a suggestion. Name your framework early in the proposal.

Systems of Systems approach

A Systems of Systems approach views the on orbit logistics enterprise as a collection of interconnected subsystems that work together to deliver sustained combat power. This perspective recognizes that no single technology can solve the logistics challenge alone. Instead, multiple systems must interact across orbital regimes, mission timelines, and operational conditions.

Under this approach, the proposer describes how their technology fits within a larger architecture that includes depots, warehouses, orbital transfer vehicles, servicing vehicles, drop ships, and health monitoring systems. The feasibility study should explain how the proposed system interacts with other systems, how it contributes to distribution loops, and how it supports the overall sustainment mission.

This approach is well suited to technologies that enable integration, coordination, or interoperability across multiple nodes. It encourages proposers to think about interfaces, standards, autonomy, and mission sequencing, and supports early identification of dependencies, constraints, and opportunities for modularity. It is particularly useful for technologies that enable routing, servicing, depot operations, or multi orbit logistics planning.

Logistics Function approach

A Logistics Function approach focuses on the specific logistics activity that the proposed technology enables. Instead of describing the entire architecture, the proposer concentrates on the function their system performs. Examples given include refueling, repair, recovery, resupply, warehousing, and health monitoring.

Under this approach, the feasibility study explains how the proposed technology improves the performance of a particular logistics function. The proposer describes the operational need, the current limitations, and the functional improvements their solution provides.

This approach is well suited to technologies that perform a discrete logistics task, such as propellant transfer, component replacement, autonomous inspection, or orbital resupply. It encourages proposers to think about efficiency, reliability, throughput, and mission impact, and supports early demonstration of measurable improvements in sustainment operations.

Choosing between them

The topic's own guidance: a Systems of Systems approach is appropriate when the technology interacts with multiple nodes or contributes to enterprise level coordination. A Logistics Function approach is appropriate when the technology performs a specific task that can be evaluated independently.

For a twelve month, one million dollar effort, the Logistics Function approach will fit most applicants better, because it lets you scope a bounded, demonstrable improvement and measure it. The Systems of Systems approach suits companies whose product is fundamentally about interfaces, standards, routing, or coordination, where the value only appears in the interactions.

The Six Phase II Focus Areas

The On Orbit Logistics Challenge includes several technical focus areas, and D2P2 proposals must address at least one. Expanded descriptions are provided in the topic to guide prototype development and ensure alignment with Space Force needs.

Propellant Management

Propellant management is described as essential to sustained maneuver, servicing, and logistics operations in space. A resilient on-orbit logistics enterprise requires the ability to store, transfer, meter, monitor, and manage propellant across multiple orbital regimes. Relevant propellant classes may include cryogenic propellants, storable chemical propellants, electric propulsion propellants, pressurants, and emerging multi-mode propulsion consumables.

The topic names Space Access PAE as seeking prototype-ready technologies that improve the availability, transferability, storability, quality assurance, and operational utility of propellant within an on-orbit logistics architecture. Proposed solutions should demonstrate how they support safe, reliable, and precise autonomous fueling operations and how they integrate with depots, orbital transfer vehicles, servicing systems, and client spacecraft.

D2P2 prototypes should demonstrate one or more of the following: autonomous propellant transfer methods, standardized or interoperable refueling interfaces, depot integration, propellant distribution operations, propellant quality monitoring, or technologies that improve the military utility and affordability of on-orbit refueling and maneuver sustainment.

Desired capabilities include autonomous propellant transfer and refueling operations; propellant quality monitoring, conditioning, and conversion; quick-connect, standardized, or interoperable mechanical and fluid interfaces; precision metering and custody tracking during storage and transfer; zero-gravity transfer, docking, grappling, and fluid handling; foreign object debris inspection, contamination control, and quality assurance; compatibility with depot operations, orbital transfer vehicles, and client spacecraft; and secondary utility such as cargo rideshare or optical inspection where relevant.

Enabling technologies named include pressurant recycling and management; propellant storage and sustainment technologies including boil-off mitigation; servicer and depot refueling interfaces; size-appropriate zero-gravity transfer systems; multi-mode propellant and propulsion support systems; in-space propellant extraction, processing, or conversion; sensors and diagnostics for propellant condition monitoring; and autonomous control systems for fueling safety, sequencing, and anomaly response.

Proposals in this focus area should clearly address four things as appropriate. Supply chain and sourcing: describe the relevant propellant supply chain, including industrial availability, production sources, expected throughput, and any dependence on terrestrial or in-space sources, addressing where applicable the potential role of in-situ resource utilization including extraction or processing from lunar, asteroid, or other space-based resources. Transfer and storage: describe how the propellant will be stored, transferred, and sustained over time, including expected storage duration, boil-off or loss characteristics where applicable, zero-boil-off or loss-mitigation approaches if relevant, and the method by which the solution supports interoperability across multiple systems or platforms, identifying whether you use existing interfaces, are designed to conform to emerging government or industry standards, or require a new interface approach. Metering, quality control, and custody: describe how the system meters propellant and maintains propellant quality during storage, transfer, and delivery, including approaches for contamination control, foreign object debris mitigation, quality monitoring, and assurance of propellant condition while under your custody, and explain how propellant is received from an upstream source, managed during transport or storage, and delivered to the next node in the logistics chain such as a depot, distribution vehicle, or end-user spacecraft. Value chain role and integration: identify the specific portion of the in-space propellant value chain being addressed, which may include production, extraction, transportation, storage, quality management, metering, distribution, or propulsion-system support for mobility restoration or reuse, and describe the broader military-relevant system or architecture to which the proposed intellectual property or capability contributes, such as reusable launch systems, reusable orbital transfer vehicles, depots, distribution fleets, or propulsion maintenance support systems. Economics and military utility: describe how the technology improves the cost, availability, responsiveness, or operational effectiveness of propellant delivery and use in space, which may include reduction in delivered cost per kilogram, improved availability at key orbital nodes such as GEO, increased maneuver endurance, greater operational reach, improved flexibility, or enhanced ability of space assets to generate mission effects.

Orbital Transfer Vehicles

Orbital Transfer Vehicles are described as the workhorses of the logistics enterprise. They move supplies, tow damaged satellites, reposition assets, and deliver benchstock. An OTV must be capable of multi stop routing, autonomous navigation, and precision maneuvering, must operate across multiple orbital regimes, and must support both planned and reactive logistics operations.

D2P2 prototypes must demonstrate modular chassis designs, autonomous navigation, precision propulsion control, and multi stop routing. The prototype must show how the OTV supports distribution loops and interacts with depots and satellites. The performer must demonstrate how the OTV maintains safety during autonomous rendezvous and proximity operations.

Desired capabilities include refuelability, reusability, inter and intra-domain mobility, interfacing with multiple systems including depots, clients, and launch vehicles, ability to handle and grapple supplies, long-duration mission survivability including radiation, spacecraft anomaly diagnosis, high delta-V performance, and standardized storage and containerization.

Enabling technologies named include reconfigurability and interoperability with specific mechanical, refueling, or electrical interfaces; autonomous rendezvous, proximity operations, and docking with on-orbit navigation and prioritization; different OTV classes or tiers by thrust and fuel type; modularity for component upgrades; radiation-hardened compute; encryption and security; cryogenics and boil-off management; fuel-on-orbit capability; containerization as a terrestrial analogy; foreign object debris mitigation and verification; center of gravity management and stability control for coupled loads; specific impulse efficiency improvements; multi-mode propulsion; and robotic manipulation.

Network Mechanics

Network Mechanics encompasses the integrated system of interfaces, connectors, docking systems, and the underlying orbital dynamics and operational standards that enable logistics systems to interact reliably and efficiently across the space domain. A robust logistics enterprise requires not only common physical interfaces for vehicles to dock, depots to exchange materials, and servicing systems to manipulate payloads, but also sophisticated orbital planning, navigation, and coordination mechanisms to manage the movement and interaction of these assets.

D2P2 prototypes must demonstrate standardized connectors, docking operations, autonomous rendezvous safety protocols, and interface modularity. Crucially, prototypes must also show how they leverage advanced orbital mechanics principles for efficient trajectory optimization, collision avoidance, and synchronized operations within a dynamic network of space assets. The prototype must show how the technology improves interoperability and reduces complexity across the logistics enterprise, while ensuring safe and fuel-efficient orbital maneuvers. The performer must demonstrate how the system supports modularity and reduces the number of unique form factors in orbit, integrated with intelligent orbital management.

Desired capabilities include logistics management, power beaming, or robotics supported by analytical tools for variables like client count and propellant needed; debris detection; training missions or war-gaming; hybrid propulsion coordination across the network, or the ability to troubleshoot anomalies; RPOD or cargo handling including space tugs and recycle center refurbishment; servicing frequency, routing, and autonomy that adapt to changing demand and reduce latency in high-demand areas; asset protection, security, and access control; autonomous orbital trajectory optimization for multi-asset coordination and fuel efficiency; real-time collision avoidance and dynamic re-routing for networked assets; precise orbital synchronization and station-keeping for distributed logistics nodes; and multi-body orbital mechanics solutions for cislunar and beyond-GEO operations.

Enabling technologies named include refueling interfaces or power beaming; functional network nodes or a control plane; novel propulsion integration for network coordination; AI-leveraged decision support or ontology development; sensors for troubleshooting or debris detection; advanced astrodynamics modeling and simulation for complex orbital scenarios; autonomous navigation and guidance algorithms for precise orbital maneuvers; distributed computing architectures for real-time orbital state estimation and prediction; Space Domain Awareness integration for enhanced orbital safety and operational planning; inter-satellite communication networks for synchronized orbital operations; and optimization algorithms for minimizing delta-V and transit times across the logistics network.

Orbital Warehousing

Warehouses and depots serve as storage and distribution nodes. They must hold propellant, spare parts, tools, consumables, and modular components. They must support autonomous material handling, inventory management, and asset visibility. They must operate in multiple orbital regimes and support both routine and emergency operations.

D2P2 prototypes must demonstrate depot construction concepts, inventory management systems, autonomous material handling, and environmental control. The prototype must show how depots support OTV operations, maintain asset visibility, and reduce logistics complexity, with no reliance on a unique interface for supply delivery, free-flying containers for diverse assets, and data on commercial capabilities. The performer must demonstrate how the depot maintains reliability and throughput during autonomous operations.

Desired capabilities include more autonomy, modularization, and system resilience; sizeable warehouses with self-healing support systems; ability to deliver parts across different orbits, with an economy and in-house operations that scale; warehouse resupply processes; secure, tamper-resistant tracking such as blockchain; super heavy lift or in-space assembly; and versatile, adaptable infrastructure supporting mission integration and intermodal transportation.

Enabling technologies named include space pallets and standards for space operations and interfaces; power beaming; visibility of inventory and speed of delivery; retractability and rapid, repeatable rendezvous and proximity operations; employing and testing new technology in the domain including autonomous robotic manipulation; no reliance on a unique interface for supply delivery; free-flying containers for diverse assets; and data on commercial capabilities.

Reuse, Repair, Refuel, and Recovery

This focus area addresses modular component replacement, robotic repair, autonomous triage, and towing of damaged satellites. Servicing vehicles must be able to diagnose faults, perform repairs, and support operational tempo. Recovery operations must support both planned maintenance and emergency response.

D2P2 prototypes must demonstrate how servicing vehicles diagnose faults, perform repairs, and support operational tempo. The prototype must show how repair operations reduce reconstitution burden and increase endurance. The performer must demonstrate how the system maintains precision and reliability during autonomous repair operations.

Desired capabilities include line- and orbital-replaceable units that are mindful of mass and are non-life-limiting components; serviceable systems and capabilities; adaptable software and distributed compute; ground digital twin and autonomy; all satellites prepared for servicing; in-space assembly and maintenance; and precision robotic manipulation.

Enabling technologies named include standard fluid, docking, power, data, and thermal interfaces; power, propulsion, and payload components such as valves and tanks; optical communications, gimbal-less, or robo-taxis with edge compute; gauges, metering, and active sensing such as LiDAR; fault-tolerant autonomous RPO; multi-degree-of-freedom robotic arms and servicing depots, with a second set of eyes software for Space Domain Awareness and RPO.

Logistics Health Monitoring

Health monitoring provides predictive insight for sustainment. Satellites must report their health status, depots must track inventory, and OTVs must monitor their systems. A logistics enterprise requires digital twins, autonomous anomaly detection, and fleet level dashboards that provide real time visibility.

D2P2 prototypes must demonstrate sensors, edge computing, digital twins, anomaly detection, and fleet level dashboards. The prototype must show how health data informs logistics planning and supports autonomous decision making. The performer must demonstrate how the system maintains accuracy and reliability during health monitoring operations.

Desired capabilities include environmentally controlled warehousing and hosting; rapid autonomous decision support including predictive tools for long-term planning and fault onset; communication and data sharing from stored goods with onboard health monitoring; balancing or cross-distribution of supplies; robotic manipulation and inspection; modular reconstitution and cross-domain autonomy; and decision-making systems that account for commercial versus government ownership with clear delegation of authority across ground, space, or hybrid systems.

Enabling technologies named include novel materials for monitorable components; advanced analytics, AI, and digital twin technology for health monitoring; data fusion across sensor data, maintenance logs, and digital twins with serialized pedigree and historical tracking; data norms and standardization for interoperability; docking and capture mechanisms that do not require high precision, or ejection seat designs for modular self-monitoring components; decentralized or cross-vendor data sharing and servicing modularity; and user interfaces for human or autonomous decision-making supported by advanced modeling and simulation.

Which focus area fits you

Of the six, Logistics Health Monitoring and Network Mechanics are the most software-accessible, and are plausible for a twelve month, one million dollar effort by a company whose product is analytics, digital twins, autonomy software, or astrodynamics tooling. Propellant Management is the most explicitly sponsored, with Space Access PAE named, and also the most demanding in terms of the questions the topic asks you to answer. Orbital Transfer Vehicles, Orbital Warehousing, and Reuse, Repair, Refuel, and Recovery are hardware-heavy and require you to scope a single demonstrable subsystem rather than a vehicle.

Given the award size, the realistic play in the hardware focus areas is a component, an interface, a mechanism, or a subsystem demonstration, not a spacecraft.

The Feasibility Requirement, Spelled Out in Six Parts

Direct to Phase II means you must document that you already completed the Phase I equivalent work outside the SBIR program. The DAF disqualifies proposals where the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit, and applies that screen before evaluating technical merit.

This topic is the most explicit in the release about what that documentation must contain. It states that the performer must demonstrate that Phase I equivalent work has already been completed, including feasibility studies, stakeholder engagement, technical validation, and early integration planning, and that the Phase II effort will build upon this foundation to produce a prototype that demonstrates operational relevance, autonomous capability, and a clear pathway to transition into Space Force sustainment operations.

Then it lists six required elements under Phase I Equivalent Work Requirements. Offerors must provide documentation demonstrating completion of Phase I equivalent work, and that documentation must be thorough, detailed, and clearly aligned with Space Force operational needs. Use these six as literal section headings in your Volume 5 feasibility package.

Stakeholder engagement. The performer must show that they have engaged with Space Force operators, program offices, mission owners, or acquisition stakeholders. This engagement must demonstrate that the proposed technology addresses a real operational need and has a clear customer within the U.S. Space Force.

Feasibility study. The feasibility study must demonstrate technical merit, operational relevance, and mission fit. It must show that the proposed technology can operate in the space environment, integrate with existing systems, and support logistics operations across multiple orbital regimes. The study must include analysis of technical risks, operational constraints, and integration challenges.

Integration pathway. The performer must describe how the technology will integrate into Space Force logistics operations. This includes interfaces, standards, autonomy requirements, mission sequencing, and coordination with other logistics systems. The integration pathway must show how the technology contributes to a broader sustainment architecture.

Regulatory considerations. The performer must identify regulatory considerations such as ITAR, EAR, licensing, and safety requirements. The documentation must show how the performer plans to comply with these regulations during Phase II and Phase III.

Commercial dual use potential. The performer must demonstrate how the technology can be used by commercial customers such as GEO operators, satellite manufacturers, or insurance providers. This dual use potential supports long term sustainability and transition.

Phase II prototype plan. The performer must provide a clear and actionable plan for Phase II prototype development. This plan must include technical milestones, integration activities, testing requirements, and demonstration objectives.

Note that only two of those six are about technology. Four are about customers, integration, regulation, and commercial demand. That is the real bar. A company with excellent hardware and no documented Space Force stakeholder engagement does not meet this requirement, and the four week open period is not enough time to manufacture it.

The general D2P2 rules

The feasibility work must have been substantially performed by the applicant or the principal investigator.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists for companies that matured technology outside the SBIR pipeline.

If technology in the feasibility documentation is subject to intellectual property rights, provide IP rights assertions, plus a short summary for each item asserted with less than unlimited rights describing the nature of the restriction and the intellectual property intended for use in the proposed research.

Feasibility documentation can be included as part of Volume 5 and is required of all proposal submissions.

Phase III

Phase III will transition the technology to operational use. Expected activities include TRL maturation to operational readiness, commercial adoption across GEO, LEO, and cislunar markets, government approvals and certifications, integration with the Space Force logistics enterprise, transition planning and stakeholder engagement, and identification of additional Department of the Air Force customers. The performer must demonstrate how the technology supports long term sustainment and commercial viability.

The reference the Air Force cites is U.S. Space Force, Space Training and Readiness Command, Space Doctrine Publication 4-0: Sustainment. If you are writing for this topic, read that document. It is the doctrinal basis for the language in the topic, and using its vocabulary is the cheapest available alignment signal.

Funding Allowance and Cost Structure

Award ceiling and the scoping problem

Up to $1,000,000 across up to 12 months. The topic index warns that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

Twelve months is the binding constraint more than the dollar figure. Space hardware schedules do not compress easily, and a proposal that promises a hardware prototype, integration, testing, and a demonstration in twelve months invites skepticism. Because cost realism sits inside the most important evaluation criterion, an implausible schedule is a technical credibility problem. Scope to what twelve months can actually deliver, name it precisely, and let the ambition live in the Phase III narrative.

The DAF also notes that per-award and per-topic funding caps are budgetary estimates only, more or less funding may become available, multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none. Funding decisions are made with complete disregard to the other awards under the same topic.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards, and per the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

Technical and Business Assistance

Up to $50,000 per Phase II award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. Applicants may elect to use $25,000 on a first SBIR Phase II award and $25,000 on a sequential SBIR Phase II award.

On a one million dollar award, $50,000 of additional assistance is proportionally the largest TABA opportunity in this release, which is worth noticing. TABA can only fund the activities in 15 U.S.C. 638(q)(1)(A) through (E): access to a network of scientists and engineers, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature through online databases. For this topic, development of regulations is directly relevant given the regulatory considerations requirement covering ITAR, EAR, licensing, and safety, and market validation supports the commercial dual use potential requirement.

The detailed request must appear in Volume 5, including provider name, point of contact with email and phone, an explanation of the provider's unique qualifications, the tasks the provider will perform including purpose and objective, and total provider cost with hours and labor rates. Average or blended rates are acceptable. The task milestone list must track to the milestone payment schedule otherwise provided by the applicant. Requests that only specify a request value in the Volume 3 Cost Proposal will not be considered.

If using TABA to hire new staff, augment staff, or direct staff into training activities, provide names and positions, the business need to be filled or training to be provided, the number of employees to be hired, augmented, or directed to participate, their qualifications or the detailed need for training, the tasks to be performed with both a description of the activity and the purpose it serves, and total staff or training cost with hours and labor rates.

Cost volume expectations

A detailed cost proposal by individual cost element and by contractor fiscal year, in sufficient detail to determine the basis for estimates and the purpose, necessity, and reasonableness of each. Cost proposal attachments do not count toward page limits, and cost proposal information will be treated as proprietary.

Direct labor: identify key personnel by name where possible, labor category otherwise, with direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual, which the Contracting Officer needs in order to determine whether hours, fringe rates, and hourly rates are fair and reasonable.

Direct cost materials: an itemized list of types, quantities, prices, and where appropriate purpose. For planned computer or software purchases, detailed information such as manufacturer, price quotes, proposed use, and support for the need will be required. On a hardware focus area, long-lead components with quotes belong here.

Other direct costs: specialized services such as machining or milling, special test and analysis, and costs for temporary use or lease of specialized facilities or equipment, with usage hours expected, rates, sources, and a brief discussion of purpose and justification. Proposals including leased hardware must include an adequate lease versus purchase rationale. Thermal vacuum, vibration, or robotics testbed access lives here.

Special tooling, special test equipment, and material: inclusion is carefully reviewed relative to need and appropriateness to the work proposed. Purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort, and should not be of a type an applicant would otherwise possess in the normal course of business.

Subcontracts: must be supported with copies of subcontract agreements adequately describing the work to be performed and cost bases, including a statement of work, assigned personnel, hours and rates, materials, and proposed travel. A letter from a subcontractor agreeing to perform a task or tasks at a fixed price is expressly not considered sufficient. The prime must accomplish price analysis including reasonableness of proposed subcontractor costs, identify the basis where prior efforts are used for comparison, and provide cost analysis where price analysis techniques are inadequate or the FAR requires cost or pricing data.

Consultants: for each consultant, provide a separate agreement letter briefly stating the service to be provided, hours required, and hourly rate, plus a short concise resume.

Travel: each effort should include at a minimum a kickoff or interim meeting, with travel costs justified as required for the effort, including destinations, number of trips, number of travelers per trip, airfare, per diem, lodging, and ground transportation, against the Joint Travel Regulation.

Indirect costs: indicate proposed rate bases, identify the specific rates used and allocation bases to which they are applied, and provide proposed rates and applications per fiscal year throughout the anticipated performance period. Do not propose composite rates.

Non-SBIR governmental or private investment is allowed but not required, and will not be a proposal evaluation factor.

If no exceptions are taken to your proposal, the Government may award a contract without exchanges, so your initial proposal should contain your best terms from a cost, price, and technical standpoint.

Work performance requirements

The instructions state two thresholds that do not obviously align. The Consultants and Subcontractors section requires, per the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer. The Performance of Work Requirements section states that for Phase II a minimum of one-third of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit. Separately, the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price unless approved in writing by the Contracting Officer.

On a one million dollar hardware effort, that one-half cap is roughly $500,000 for all outside costs combined, which is easy to exceed if you are buying components and leasing testbeds. Model this before you finalize your approach. Planning to perform at least half the R/R&D in house and keeping all outside costs below half the contract price satisfies every reading.

If your structure cannot meet that, requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission. Given the ambiguity between the two stated thresholds, raise it with the DAF SBIR/STTR One Help Desk early in the open period.

Where work must be performed

All R/R&D must be performed in the United States by the small business and its team members. Based on rare and unique circumstances the DAF may approve a particular portion of the work to be performed or obtained outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking that approval must request it with the initial proposal submission.

Export Control and Foreign Nationals

The technology in this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including sensitive technical data, and EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by those individuals. The topic advises that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

A foreign national means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR CSO and disclose regardless of whether the topic is subject to ITAR restrictions.

Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations to verify eligibility.

For projects with military or dual-use applications developing beyond fundamental research, the contractor must comply with all U.S. export control laws, is responsible for obtaining appropriate licenses or other approvals including for deemed exports of hardware, technical data, and software, must obtain export licenses before utilizing foreign persons including where work is performed on-site at any Government installation whether inside or outside the United States, is responsible for all regulatory record keeping associated with the use of licenses and license exemptions or exceptions, and must ensure these provisions apply to its subcontractors.

If asserting export-controlled status, a certified DD Form 2345 Militarily Critical Technical Data Agreement, or evidence of application submission, belongs in Volume 5, and DD Form 2345 approval will be required if the proposal is selected for award.

Note the useful overlap: the feasibility requirement's regulatory considerations element already asks you to identify ITAR, EAR, licensing, and safety requirements and describe your compliance plan for Phase II and Phase III. Write that analysis once and use it in both places.

Proposal Structure: The Seven Volumes

Formatting, and the 15 page problem

Type no smaller than 11-point on standard 8.5 by 11 paper, one-inch margins, pages consecutively numbered. This differs from Army SBIR instructions, which allow 10-point.

The technical volume limit is 15 pages or slides, the tightest in this release. Pages in excess will not be considered by the Government in evaluations. Because the limit is expressed as pages or slides, a slide-format volume is acceptable, and on a 15 page budget many teams find slides more information-dense.

Fifteen pages must cover the required Volume 2 element list, your chosen architectural framework and why, your chosen focus area and technical approach, a milestone schedule, a commercialization plan, key personnel, facilities, and prior support. There is no room for scene-setting. Two things help. First, push everything permitted into the volumes that do not count: cost proposal attachments, subcontract copies, and supporting documents do not count toward the page limit, and feasibility documentation goes in Volume 5. Second, do not restate the topic back to the Government. Evaluators wrote it.

Proposals should be direct, concise, and informative. Applicants are discouraged from including promotional and non-programmatic items, and if included such material counts toward the page limit. Marketing material will not be evaluated. Preferred format is PDF, graphics must be distinguishable in black and white, and all submissions must be virus-checked.

Volume 6 Fraud, Waste, and Abuse training must be completed before proposal submission, and DSIP will not allow submission until it is complete and certified. The DAF recommends completing submission early because site traffic is heavy prior to solicitation close and causes system lag, will not be responsible for proposals not completely submitted before the deadline due to system inaccessibility unless advised by DoW, and will not accept alternative means of submission outside DSIP.

Volume 1, Cover Sheet

Per DSIP instructions. The technical abstract should include a brief description of program objectives, a description of the effort, anticipated benefits, commercial applications, and a list of keywords and terms. The abstract of each successful proposal goes to the Office of the Secretary of War for publication and must not contain proprietary or classified information. If selected for funding, the technical abstract and discussion of anticipated benefits will be publicly released.

Volume 2, Technical Volume

Required items in the order provided: table of contents immediately after the cover sheet; glossary of acronyms and abbreviations; milestone identification with a program schedule showing all key milestones; identification and significance of the problem or opportunity; Phase II technical objectives with the technical approach and methods and an assessment of potential commercial application for each objective; work plan; deliverables; related work; commercialization potential; relationship with future R/R&D efforts; key personnel; facilities and equipment; consultants and subcontractors; and prior, current, or pending support of similar proposals or awards.

The work plan is a separate and distinct part of the proposal package, divided from the technical proposal by a page break and begun on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility, and must not contain proprietary information, because if the proposal is selected the work plan will be incorporated into the resulting contract by reference. Recommended format is 1.0 Objective, a brief overview of the specialty area explaining purpose and expected outcome; 2.0 Scope, concisely describing the work to be accomplished including the technology area to be investigated, goals, and major milestones, with task development and deliverables as key elements meaning the anticipated end result or the effort's product, consistent with section 4.0; 3.0 Background, identifying appropriate specifications, standards, and other documents applicable to the effort, including explanation for or constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task and Technical Requirements, with detailed individual task descriptions developed in orderly progression with sufficient detail to establish overall program requirements and goals, work segregated into major tasks and identified in separately numbered paragraphs, each numbered major task delineating work by subtask. The work plan must contain every task to be accomplished in definite, realistic, and clearly stated terms. Use "shall" whenever the work plan expresses a binding provision, "should" or "may" to express a declaration or purpose, and "will" when no contractor requirement is involved.

Deliverables must include a section clearly describing the specific sample or prototype hardware and software to be delivered, as well as data deliverables, schedules, and quantities. Be aware of the possible requirement for unique item identification in accordance with DFARS 252.211-7003, Item Identification and Valuation, for hardware. If hardware or software will be developed but not delivered, provide an explanation. At a minimum, all Phase II contracts require Scientific and Technical Reports. Rights in technical data including software developed under the terms of any contract resulting from a SBIR Announcement generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the SBIR/STTR contract for a period of 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page will be a single-page project summary identifying the work's purpose, providing a brief description of the effort accomplished, and listing potential result applications, which may be published by DoW and therefore must not contain any proprietary or classified information; the remainder should contain details of project objectives met, work completed, results obtained, and technical feasibility estimates. Status reports are due quarterly at a minimum. The Air Force may require additional reporting documentation including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project will result in partial or total development and delivery of hardware, and updates to the commercialization results.

Related work must describe significant activities directly related to the proposed effort, including any previous programs conducted by the principal investigator, proposing firm, consultants, or others, and their application to the proposed project, describe how these activities interface with the proposed project, and discuss any planned coordination with outside sources. Also list any applicant-identified subject matter experts regardless of affiliation, providing comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related to the proposed effort but similar, providing a short description, the client for which the work was performed including an individual to be contacted and phone number, and the date of completion.

Commercialization potential requires a commercialization plan submitted with the Phase II proposal, specifically addressing what the first planned product to incorporate the proposed technology is, who the probable customers are and what the estimated market size is, how much money is needed to bring the technology to market and how it will be raised, whether the firm has the necessary marketing expertise and if not how the firm will compensate, and who the probable competitors are and what price or quality advantage is anticipated by the firm. The commercialization strategy plan should briefly describe the commercialization potential for the project's anticipated results as well as plans to exploit it. Commercial potential is evidenced by the existence of private sector or non-SBIR/STTR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and the presence of other indicators of commercial technology potential including the firm's commercialization strategy. If awarded a D2P2, the awardee will be required to update periodically the commercialization results of the project via SBA, at completion of the effort and subsequently when submitting a new SBIR/STTR proposal to DoW, with firms not submitting a new proposal requested to provide updates annually after the D2P2 completion. The Commercialization Plan and the Company Commercialization Report are distinct documents.

Note the useful overlap again: the feasibility requirement's commercial dual use potential element names GEO operators, satellite manufacturers, and insurance providers as example commercial customers. Those are strong candidates for the probable customers question in the commercialization plan.

Relationship with future R/R&D efforts must state the anticipated results of the proposed approach, specifically addressing plans for Phase III if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III R/R&D effort if planned. The topic's own Phase III list gives you the structure: TRL maturation to operational readiness, commercial adoption across GEO, LEO, and cislunar markets, government approvals and certifications, integration with the Space Force logistics enterprise, transition planning and stakeholder engagement, and identification of additional DAF customers.

Key personnel must identify all key personnel involved in the project with information directly related to education, experience, and citizenship, and include a technical resume for the principal investigator with publications if any. Concise technical resumes for subcontractors and consultants are also useful. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for those individuals, in addition to technical resumes, provide countries of origin, type of visas or work permits held, and identify the tasks they are anticipated to perform. The principal investigator's primary employment must be with the small business concern at the time of award and during the entire period of performance, where primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager can be designated to a proposal at any given time.

Facilities and equipment must describe instrumentation and physical facilities necessary and available to carry out the D2P2 effort, justify equipment to be purchased with detail in the cost proposal, and state whether proposed performance locations meet environmental laws and regulations of federal, state, and local governments for, but not limited to, airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors: private companies, consultants, or universities may be involved in the project, and all should be described in detail and included in the cost proposal. Signed copies of all consultant or subcontractor letters of intent must be attached to the proposal, briefly stating the contribution or expertise being provided, with statements of work and detailed cost proposals, and information regarding consultant or subcontractor unique qualifications. Subcontract copies and supporting documents do not count against the Phase II page limit. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support of similar proposals or awards: while it is permissible with proper notification to submit identical proposals or proposals containing a significant amount of essentially equivalent work for consideration under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort, and any potential for that situation must be disclosed to the solicitation agencies before award. If a proposal submitted in response to this CSO is substantially the same as another submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, the applicant must indicate so on the cover sheet and provide the name and address of the federal agencies or DoW components to which proposals were or will be submitted or from which an award is expected or has been received, the proposal submission or award dates, the proposal title, the PI's name and title for each proposal submitted or award received, the solicitation titles, numbers, and dates, the contract number if an award was received, and the applicable topics for each SBIR proposal submitted or award received. If this section does not apply, state so in the proposal and certify on the cover sheet, "No prior, current, or pending support for proposed work."

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Completion of the CCR in DSIP is required. The DAF states that information contained in the CCR will not be considered by the DAF during proposal evaluations, which differs from Army SBIR practice. Complete it for compliance.

Volume 5, Supporting Documents

May be required if applicable: DD Form 2345, which applies to this export-controlled topic, with the form, instructions, and FAQs at the United States and Canada Joint Certification Program website; Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 CSO; and Technical Data Rights Assertions if asserting data rights restrictions.

Required of all submissions: feasibility documentation. D2P2 proposals require a comprehensive, detailed effort description and should demonstrate sufficient technical progress or problem-solving results to warrant more extensive RDT&E. Developing technologies with commercial and military potential is described as extremely important, and the DAF is particularly seeking proposals emphasizing technologies' dual-use applications and commercialization. The applicant must provide information enabling the agency to make the 15 U.S.C. 638(cc) determination of scientific and technical feasibility and merit. Feasibility efforts detailed must have been substantially performed by the applicant or the PI. If technology in the feasibility documentation is subject to intellectual property rights, the applicant must provide IP rights assertions and a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material, which will not be evaluated.

Volume 6, Fraud, Waste, and Abuse Training

Complete once per year, before submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Complete the webform in Volume 7 of the DSIP proposal submission. It will not be accepted as a PDF supporting document in Volume 5, and do not upload any previous versions of this form to Volume 5.

How Your Proposal Will Be Evaluated

The criteria for this topic

DV513 is evaluated under the criteria set covering DV026, DV511, DV512, and DV513, in descending order of importance.

Criteria A, most important: the soundness, technical merit, and innovation of the proposed approach and its incremental progress toward topic or subtopic solution, and the qualifications of the proposed principal and key investigators, supporting staff, and consultants. This includes whether the proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the unique methods of performance and materials described in the technical proposal.

Two features of this criterion matter especially on this topic. First, incremental progress toward topic or subtopic solution rewards a bounded, well-defined step rather than an overreach. With six focus areas designated as subtopics, name yours and frame your progress against it. Second, cost realism inside the top criterion is where an implausible twelve month hardware schedule gets penalized. If your work plan promises fabrication, integration, and demonstration in twelve months, your cost volume and milestone schedule have to make that arithmetic work.

Criteria B, second: the degree of mission impact and the urgency of the identified need, the specificity of the defense requirement addressed, and the adequacy of the proposed effort in fulfilling the research topic or subtopic solution.

Criteria C, third: the potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

General evaluation process

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel, with confidential proposal and evaluation information protected to the greatest extent possible. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

Selections are based on a determination of the overall technical value of each proposal and an evaluation of the cost volume for selection of the proposals most advantageous to the Government. Where technical evaluations are essentially equal in merit, cost or price will be considered in determining successful applicants. All evaluation criteria other than cost or price, when combined, are significantly more important than cost or price. The DAF is seeking varying technical and scientific approaches and varying and new technologies responsive to the problem statements and areas of interest in the topic, multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none of the proposals.

Foreign risk evaluation

The DAF will evaluate all small business concerns submitting under this release on whether the concern presents a security risk, using the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947, federal law enforcement, and other counterintelligence capabilities of the United States Government.

The risk-based assessment covers cybersecurity practices, patent analysis, employee analysis, foreign ownership of the concern including financial ties and obligations covering surety, equity, and debt obligations of the concern and its employees to a foreign country, foreign person, or foreign entity, foreign affiliations of a covered individual, owner, or other key personnel with an entity in a foreign country of concern, investment relationships of the concern with an individual or entity in a foreign country of concern, technology licensing agreements or joint ventures including joint venture like agreements with an individual or entity in a foreign country of concern, and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

Two of those items deserve particular attention on this topic. Patent analysis matters because in-space servicing and propellant transfer are patent-dense areas with significant international activity. Technology licensing agreements and joint ventures matter because commercial space companies frequently have international partners, launch agreements, and cross-licensing arrangements. Map yours before you propose.

The DAF also assesses proposals using open-source analysis and analytical tools for nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examines any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, it will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.

Awards must be denied under 15 U.S.C. 638(g)(16) or 638(o)(20) where the DAF determines the concern has an owner or covered individual party to a malign foreign talent recruitment program; a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; an owner or covered individual with a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or a security risk connecting the concern, including any affiliates, to an entity or individual on the UFLPA Entity List maintained by the Department of Homeland Security, the Non-SDN Chinese Military-Industrial Complex Companies List maintained by Treasury's Office of Foreign Assets Control, the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019, the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021, the Military End User List maintained by Commerce's Bureau of Industry and Security, the Entity List maintained by BIS, the FCC List of Equipment and Services, or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection. The DAF also will not make an award where the concern has a security risk with a primary source that is classified or a security risk the DAF determines warrants a denial.

Applicants must disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7, and must provide a written statement of any substantial changes to the foreign disclosure form to the awarding agency within 30 days of any changes while on a project for the DAF.

Where an award is denied on these grounds, the DAF will as appropriate and in a manner that does not compromise security provide a notification advising the small business of the determination, the basis for it, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle.

Ownership, support contractors, status, and protests

Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics. This matters on this topic, since in-space servicing and logistics is a venture-funded sector.

Proposals may be handled for administrative purposes only by support contractors, which may include APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to Air Force Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the DAF SBIR/STTR Contracting Officer with concerns about any of these contractors.

The principal investigator and Corporate Official indicated on the proposal cover sheet will be notified by email regarding proposal selection or non-selection. Small businesses receive a notification for each proposal submitted, so read each notification carefully and note the proposal number and topic number referenced. Automated feedback will be provided for proposals designated Not Selected, and additional feedback may be provided at the sole discretion of the DAF. Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic, and each organization operates within its own schedule for proposal evaluation and selection, so update and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions, since separate notifications are provided for each proposal.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for proposal status before that time. Protests after award should be submitted, as further prescribed in FAR 33.106(b) and FAR 52.233-3, to the Air Force SBIR/STTR Contracting Officer and to the individual procuring contracting officer listed on the firm's selection notification. All final reports will be submitted to the awarding DAF organization in accordance with contract instructions, and companies will not submit final reports directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 12 months from award

A working backward plan

Before September 23. The gating item is your stakeholder engagement documentation. The feasibility requirement demands evidence that you have engaged Space Force operators, program offices, mission owners, or acquisition stakeholders, and that the engagement shows a real operational need and a clear customer within the U.S. Space Force. Pull together records of those conversations now. Read Space Doctrine Publication 4-0 Sustainment, which the topic cites, and adopt its vocabulary. Choose your architectural framework and your focus area. Map your patents, international licensing arrangements, and joint ventures against the foreign risk criteria. Assemble the regulatory analysis covering ITAR, EAR, licensing, and safety, which serves both the feasibility requirement and your export control posture. Confirm which team members are U.S. persons. Start DD Form 2345 if you do not hold one. Complete Volume 6 training, verify SAM and DSIP alignment, and send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries.

September 23 through October 2. Draft Volume 2 against the 15 page limit, which will take multiple compression passes. State your architectural framework and why it fits, and your focus area, in the opening page. Build a twelve month milestone schedule you can actually defend, since the TABA task milestone list must track to your milestone payment schedule and cost realism sits in the top evaluation criterion.

October 3 through October 10. Assemble the Volume 5 feasibility package under the six required headings: stakeholder engagement, feasibility study, integration pathway, regulatory considerations, commercial dual use potential, and Phase II prototype plan. This is the document that gets you past the disqualification screen, and it does not count against your 15 pages, so give it the room it deserves.

October 11 through October 16. Build the cost volume by element and fiscal year. Collect signed letters of intent, statements of work, and detailed cost proposals from every consultant and subcontractor, remembering that a letter agreeing to a fixed price is not sufficient. Check that all outside costs stay under half the contract price, which on a one million dollar award is a tighter constraint than it sounds. Complete the Volume 7 webform and the Volume 4 CCR. Run compliance: 15 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics legible in black and white, virus-checked PDF, no marketing material, and no proprietary content in the technical abstract or the work plan.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-DV513?

‍ ‍

DAF26BX06-DV513 is a Department of the Air Force SBIR Direct to Phase II topic titled "Autonomous On Orbit Logistics and Sustainment Architecture," released under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. It seeks prototype-ready technologies enabling a complete on-orbit logistics enterprise supporting autonomous resupply, refuel, repair, recovery, and reconstitution of U.S. space assets across LEO, MEO, GEO, and cislunar space.

‍ ‍

How much funding is available under DAF26BX06-DV513?

‍ ‍

Up to $1,000,000 for a period of performance up to 12 months, the smallest ceiling and shortest duration in this release. Proposals exceeding either limit will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

How should I scope a twelve month, one million dollar space logistics effort?

‍ ‍

Narrowly and precisely. Twelve months is the binding constraint, and space hardware schedules do not compress. In the hardware focus areas the realistic scope is a component, interface, mechanism, or subsystem demonstration, not a vehicle. Because cost realism sits inside the most important evaluation criterion, an implausible schedule reads as a technical credibility problem. Put the ambition in the Phase III narrative and keep the Phase II scope defensible.

‍ ‍

What are the two architectural frameworks and do I have to pick one?

‍ ‍

Yes, and the topic requires you to clearly identify which you are using and explain why it is appropriate for your concept. A Systems of Systems approach views the enterprise as interconnected subsystems and suits technologies enabling integration, coordination, or interoperability across multiple nodes, including routing, servicing, depot operations, or multi orbit logistics planning. A Logistics Function approach focuses on the specific logistics activity your technology enables, such as refueling, repair, recovery, resupply, warehousing, or health monitoring, and suits technologies performing a discrete task that can be evaluated independently.

‍ ‍

Which framework should I choose?

‍ ‍

The topic says Systems of Systems is appropriate when your technology interacts with multiple nodes or contributes to enterprise level coordination, and Logistics Function is appropriate when your technology performs a specific task that can be evaluated independently. For a twelve month effort, the Logistics Function approach will fit most applicants better because it lets you scope and measure a bounded improvement.

‍ ‍

What are the six focus areas?

‍ ‍

Propellant Management, Orbital Transfer Vehicles, Network Mechanics, Orbital Warehousing, Reuse Repair Refuel and Recovery, and Logistics Health Monitoring. D2P2 proposals must address at least one.

‍ ‍

Which focus area fits my company?

‍ ‍

Logistics Health Monitoring and Network Mechanics are the most software-accessible and most plausible for a twelve month effort by an analytics, digital twin, autonomy, or astrodynamics software company. Propellant Management is the most explicitly sponsored, with Space Access PAE named as seeking prototype-ready propellant technologies, and also asks the most detailed questions of proposers. Orbital Transfer Vehicles, Orbital Warehousing, and Reuse Repair Refuel and Recovery are hardware-heavy and require scoping to a single demonstrable subsystem.

‍ ‍

What does the Propellant Management focus area require me to address?

‍ ‍

Five areas as appropriate: supply chain and sourcing including industrial availability, production sources, expected throughput, dependence on terrestrial or in-space sources, and where applicable in-situ resource utilization; transfer and storage including storage duration, boil-off or loss characteristics, loss-mitigation approaches, and interoperability across systems with a statement of whether you use existing interfaces, conform to emerging standards, or require a new interface; metering, quality control, and custody including contamination control, foreign object debris mitigation, quality monitoring, and how propellant moves from upstream source through your custody to the next node; value chain role and integration identifying the specific portion of the in-space propellant value chain addressed and the broader military-relevant architecture your capability contributes to; and economics and military utility including delivered cost per kilogram, availability at nodes such as GEO, maneuver endurance, operational reach, flexibility, or enhanced ability to generate mission effects.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This topic is intended for technology proven ready to move directly into Phase II, and Phase I awards will not be made.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

Six elements, and the documentation must be thorough, detailed, and clearly aligned with Space Force operational needs. Stakeholder engagement showing you have engaged Space Force operators, program offices, mission owners, or acquisition stakeholders and that the technology addresses a real operational need with a clear customer within the U.S. Space Force. A feasibility study demonstrating technical merit, operational relevance, and mission fit, showing the technology can operate in the space environment, integrate with existing systems, and support logistics operations across multiple orbital regimes, including analysis of technical risks, operational constraints, and integration challenges. An integration pathway describing interfaces, standards, autonomy requirements, mission sequencing, and coordination with other logistics systems. Regulatory considerations identifying ITAR, EAR, licensing, and safety requirements and your compliance plan for Phase II and Phase III. Commercial dual use potential showing use by commercial customers such as GEO operators, satellite manufacturers, or insurance providers. And a Phase II prototype plan with technical milestones, integration activities, testing requirements, and demonstration objectives.

‍ ‍

What is the hardest part of the feasibility requirement?

‍ ‍

The stakeholder engagement element. Only two of the six required elements are about technology, and four are about customers, integration, regulation, and commercial demand. A company with excellent hardware and no documented Space Force stakeholder engagement does not meet this requirement, and four weeks is not enough time to create that record.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility effort must have been substantially performed by the applicant or the principal investigator.

‍ ‍

How long can my technical volume be?

‍ ‍

15 pages or slides, the tightest limit in this release. Pages in excess will not be considered during evaluations. Type must be no smaller than 11-point on 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Cost proposal attachments, subcontract copies, and supporting documents do not count toward the limit, and feasibility documentation goes in Volume 5, so use those volumes for detail.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. You must disclose any proposed foreign nationals with countries of origin, visa or work permit type, and the statement of work tasks intended for them, and the topic advises those individuals may be restricted from performing. A certified DD Form 2345, or evidence of application, belongs in Volume 5, and approval will be required if selected for award.

‍ ‍

How is my proposal evaluated?

‍ ‍

Under three criteria in descending order of importance. Criteria A, most important, covers soundness, technical merit, and innovation of the approach, incremental progress toward the topic or subtopic solution, the qualifications of key personnel, and whether proposed cost elements are realistic and consistent with the technical proposal. Criteria B covers degree of mission impact, urgency of the identified need, specificity of the defense requirement, and adequacy of the effort. Criteria C covers commercial application potential. All criteria other than cost or price, combined, are significantly more important than cost or price.

‍ ‍

How much of the work must my company perform?

‍ ‍

The instructions state two thresholds. The Consultants and Subcontractors section requires at least 50 percent of the R/R&D be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. The Performance of Work Requirements section states at least one-third of the Phase II research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility leases, and other subcontract or purchase agreements together may not exceed one-half of the total contract price without written Contracting Officer approval, which on a one million dollar award is roughly $500,000 for all outside costs combined. Model this before finalizing your approach. Deviation requests must be made twice, prior to submission during the open period and again with the initial proposal.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 is required, but the DAF states information contained in the CCR will not be considered during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, splittable as $25,000 on a first SBIR Phase II and $25,000 on a sequential one. On a one million dollar award this is proportionally the largest TABA opportunity in the release. Development of regulations and market validation are eligible activities that map directly to the regulatory considerations and commercial dual use elements of the feasibility requirement. The detailed request must be in Volume 5 with provider name, point of contact, unique qualifications, tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests specifying only a value in Volume 3 will not be considered.

‍ ‍

Who owns the data and software I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data.

‍ ‍

What happens in Phase III?

‍ ‍

Phase III will transition the technology to operational use. Expected activities include TRL maturation to operational readiness, commercial adoption across GEO, LEO, and cislunar markets, government approvals and certifications, integration with the Space Force logistics enterprise, transition planning and stakeholder engagement, and identification of additional Department of the Air Force customers. The performer must demonstrate how the technology supports long term sustainment and commercial viability.

‍ ‍

What doctrine should I read before writing?

‍ ‍

Space Doctrine Publication 4-0, Sustainment, published by U.S. Space Force Space Training and Readiness Command, which is the reference the topic cites. It is the doctrinal basis for the topic's language, and using its vocabulary is the cheapest alignment signal available to you.

‍ ‍

Are venture-backed companies eligible?

‍ ‍

Yes. Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates all proposals evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The principal investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal submitted.

‍ ‍

Who do I contact with questions?

‍ ‍

The DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Scope to twelve months honestly. This is the most common way a good company loses this topic. The logistics enterprise the Space Force describes is a decade-long build, and you are being funded for one year. Name one bounded deliverable, show it is achievable, and describe the enterprise contribution around it rather than promising the enterprise.

‍ ‍

State your framework and focus area on page one. The topic requires you to identify which architectural approach you are using and explain why. Doing that immediately signals that you read the topic carefully, and with only 15 pages, ambiguity about scope is expensive.

‍ ‍

Build the Volume 5 feasibility package around the six named headings. Stakeholder engagement, feasibility study, integration pathway, regulatory considerations, commercial dual use potential, Phase II prototype plan. Mirroring the topic's own structure makes the disqualification screen easy to pass and does not consume your page limit.

‍ ‍

Treat stakeholder engagement as the real gate. Space Force operators, program offices, mission owners, or acquisition stakeholders, with evidence the technology addresses a real operational need and has a clear customer. That is not something a proposal can assert its way past.

‍ ‍

Read and quote SDP 4-0. The topic cites Space Doctrine Publication 4-0 Sustainment as its only reference. Sustained space maneuver, dynamic space operations, and contested logistics are the operating concepts the topic names. Alignment scores, and alignment here is largely vocabulary plus a genuine understanding of the doctrine.

‍ ‍

Answer the interoperability question directly. Across several focus areas the topic asks whether you use existing interfaces, are designed to conform to emerging government or industry standards, or require a new interface approach. That is a live and consequential question in in-space servicing, and a clear answer with reasoning beats an evasive one.

‍ ‍

Do the economics. The Propellant Management focus area explicitly asks about delivered cost per kilogram, availability at orbital nodes, maneuver endurance, and operational reach. Even outside that focus area, quantified sustainment economics distinguish a serious proposal from a technology description.

‍ ‍

Model the subcontract cap early. Half of one million dollars for all consultant fees, facility leases, and subcontracts combined is restrictive for hardware. If your plan involves buying a lot or leasing testbeds, check the arithmetic before you commit to the approach.

‍ ‍

Map your international entanglements. Patent analysis and technology licensing agreements or joint ventures with entities in countries of concern are both named in the foreign risk assessment. Commercial space companies commonly have international launch, licensing, and partnership arrangements. Know yours and be ready to describe them.

‍ ‍

Use GEO operators, satellite manufacturers, and insurers as your commercial customers. The topic names them in the feasibility requirement, which means the Space Force already accepts them as credible. Your commercialization plan's probable customers question has a ready answer.

DAF SBIR DAF26BX06-DV512: Cyberspace Warfare for Space

Quick Answer

DAF26BX06-DV512 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. SpaceWERX, working with Cyberspace Warfare professionals in the U.S. Space Force, is looking for solutions that defend space systems from adversarial attack through the cyber domain. The topic is organized into eight distinct focus areas, and proposals need to address one or more of them, not all eight. Awards are up to $2,000,000 for up to 24 months, with a 20 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

The eight focus areas are genuinely different businesses: data ingestion, software supply chain vetting, on-orbit cyber defense running on a satellite, a cyber range for training space operators, data parsing and normalization, AI threat detection, supply chain risk analytics, and a portable field kit. A company with a mature product in any one of them has a credible path here, which makes this the broadest topic in the release and probably the most accessible to commercial cybersecurity firms that have never worked with the Space Force.

Topic At a Glance

Topic number: DAF26BX06-DV512

Title: Cyberspace Warfare for Space

Solicitation: Department of the Air Force 2026 SBIR Commercial Solutions Opening (CSO), Release 6, Direct to Phase II

Sponsoring organization: SpaceWERX, in partnership with Cyberspace Warfare professionals within the U.S. Space Force

Program type: Direct to Phase II (D2P2), no Phase I awards will be made for this topic

Award maximum value: $2,000,000

Award maximum duration: 24 months

Technical volume page limit: 20 pages or slides

Component Technology Priority Area: Space Technology

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Focus areas: eight, and proposals should address one or more

Target maturity for Phase III transition: TRL 6 or 7

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: SpaceWERX, on-orbit cyber defense, space vehicles, autonomous cyber response, real-time monitoring, defensive cyber warfare, artificial intelligence, machine learning, threat simulation

Note on the deadline time. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the proposal submission deadline date and time. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting rather than assuming end of day.

What the Space Force Is Actually Trying to Build

The strategic framing

The Space Force's defensive cyber operations mission is focused on rapid integration of capabilities into the Defensive Cyber Warfare pipeline, referred to throughout as DCW, to address the unique and complex cybersecurity requirements of space systems. The stated aims are to enable scaling of current DCW systems for widespread protection and to improve Space Force operational readiness.

The Space Force describes the change it wants in terms worth quoting closely, because they tell you what language to use. Modernizing Defensive Cyber Warfare for Space requires shifting from fragmented, reactive security to a cohesive, intelligence-driven posture that spans from the commercial supply chain to the orbital edge.

That phrase, from the commercial supply chain to the orbital edge, is the organizing idea behind the eight focus areas. Two of them are supply chain problems, three are data and analytics problems on the ground, one is a training environment, one runs on the satellite itself, and one goes in a case to a forward location.

The initiative is described as seeking to build a unified defense ecosystem where AI-enhanced vetting ensures the integrity of hardware and software long before deployment. Once operational, agile data architectures will seamlessly normalize complex telemetry across hybrid networks, fueling advanced machine learning engines to autonomously detect and intercept threats in real time. The focus areas should optimize the existing IT environment to minimize cost and maximize efficiency. By extending lightweight, resilient safeguards directly onto spacecraft and disconnected ground infrastructure, and validating them through hyper-realistic, immersive training environments, the initiative aims to equip cyber operators with a decisive, end-to-end advantage against advanced adversaries.

The desired outcome, stated at the top, is to produce capabilities that advance the domain of defensive cyber warfare operations in eight different focus areas, each presenting a unique opportunity for industry. This initiative supports the Space Force's broader strategy to generate, present, sustain, and improve Cyberspace Warfare forces for the Joint Force.

The eight focus areas

Proposals should address one or more of the following. Pick the one where you have real product maturity and feasibility evidence, and say so clearly and early in your proposal.

Focus Area 1: Lightweight and Cloud-Agnostic Data Ingest. To support future-ready data operations for DCW systems, the team wants best value, lightweight, efficient data ingestion at the edge or at the hub. The named problem is the significant infrastructure overhead associated with traditional data capture methods. Solutions should deploy with minimal impact to existing systems, providing high-throughput data capture without demanding extensive hardware or complex configurations. The goal is to pull critical data into analytics platforms so that on-premises monitoring capabilities are both effective and sustainable. In parallel, the effort is interested in cloud data ingestion, with Cloud Service Provider agnostic approaches offering flexible and scalable ingestion independent of cloud provider solutions, including exploring technologies such as virtual TAPs. The ultimate objective is a cohesive data ingest solution independent of the underlying infrastructure, whether on-premises, in a single cloud, or across a multi-cloud landscape.

Focus Area 2: Defensive Cyber Warfare Systems, Proactive Software Assurance and Malware Detection. To safeguard DCW systems against an increasingly compromised global software supply chain, the team wants advanced capabilities for deep inspection and security vetting of third-party software packages. The initiative is twofold, addressing both Free and Open-Source Software and non-approved Commercial Off-the-Shelf products, with the goal of proactively identifying and mitigating threats before they enter critical operational environments. Solutions should thoroughly evaluate FOSS packages to produce a comprehensive Software Bill of Materials and detailed risk analysis, automatically alerting operators to embedded malware, hidden back-doors, and vulnerabilities corresponding to the OWASP Top 10. A key feature will be the ability to trace software origin and development lineage, providing critical intelligence on contributions from foreign nationals or known adversaries. A similar vetting mechanism is desired for COTS software not currently on an Approved Product List, leveraging techniques such as binary analysis, SBOM generation, or other advanced methods to produce a thorough risk assessment covering both specific security vulnerabilities and broader digital supply chain risks. These detection mechanisms would provide the greatest value if implemented for validation onboard or integrated prior to space system deployment.

Focus Area 3: On-Orbit Space Vehicle Cyber Defense and Monitoring. The team wants an advanced on-orbit detection and response capability for Space Vehicles that directly reduces or negates the impact of cyber-attacks on critical space systems. The primary objective is to deploy a persistent monitoring solution directly onto the Space Vehicle that can identify and, in approved instances, autonomously respond to malicious activity in real time. This onboard capability should integrate seamlessly with existing ground-based DCW systems so all telemetry and alert data are relayed to terrestrial monitoring centers. Solutions should monitor a wide spectrum of the Space Vehicle's internal functions, including detecting unauthorized software, firmware, or critical configuration changes; monitoring traffic on essential, non-redundant components such as the 1553 Bus and SpaceWire; and identifying anomalous behavior such as irregular commands or malware uploads. The system should be sensitive to threat indicators targeting the vehicle's core subsystems, including triggers related to power manipulation, system timing interference, or unauthorized payload function commands. Upon detecting an approved event, the system should execute a direct response on the Space Vehicle and transmit comprehensive logs to the ground segment for analysis. Given the highly restrictive nature of space platforms, solutions should be engineered with minimal size, weight, and power impact, and software-based solutions that impose a negligible resource footprint on the host vehicle are strongly preferred. Offerors should be aware that development and testing will likely be conducted using high-fidelity environments such as a FlatSat or realistic simulations.

Focus Area 4: Immersive Space Cyber Test Environment. The team wants a comprehensive and immersive test and purple teaming platform designed to prepare cyber operators for the unique challenges of defending space systems against advanced cyber threats. The objective is a realistic, hands-on environment where operators develop and hone skills in detecting and responding to attacks targeting space assets and their supporting infrastructure, described as instrumental in building a proficient and mission-ready cyber defense workforce. The proposed solution should include two core high-fidelity components: a simulated space asset, which could be a physical FlatSat or a sophisticated digital twin, and a corresponding simulated ground system. The ground simulation should realistically model all essential elements, including the ground control segment, remote tracking stations, and antenna systems. A critical requirement is full integration of the government-furnished DCW tool suite, allowing operators to train with the actual systems they will use in live missions. The training platform should also come equipped with a robust curriculum of realistic, scenario-based cyber-attacks serving as the foundation for training exercises, simulating credible threats including direct cyber-attacks against the space vehicle's onboard systems, attacks targeting the ground control systems, and threats aimed at compromising the communication and access links between the space and ground segments.

Focus Area 5: Adaptive Data Parsers and Transformation Engine. The team wants a universal parser or data transformation mechanism capable of ingesting and normalizing a wide array of data types into a single standardized format for seamless integration into DCW analytics systems. The stated problem is that developing dedicated parsers for each data source is time consuming, labor intensive, and creates significant code maintenance challenges. The needed solution handles a wide range of data types used in analytics, including space specific protocols, proprietary logs from various network devices, proprietary data types produced by cyber tools, and non-standard formats from numerous intelligence threat feeds. It should minimize code maintenance when new Security Information and Event Management systems or data structures are introduced, and support incorporation of new data formats without requiring major code revisions. By transforming disparate data into a common, queryable format, the solution will significantly enhance analytical capabilities and provide a comprehensive, correlated view of the battlespace, described as essential for creating a unified and consistent data pipeline fundamental to effective security monitoring, threat hunting, and incident response.

Focus Area 6: AI-Driven Cyber Threat Detection. In response to emerging adversarial tactics, the team recognizes that traditional signature-based detection methods are no longer sufficient to provide a decisive advantage, and wants to augment DCW systems with an advanced, behavior-based threat detection capability. The solution should leverage artificial intelligence, machine learning, or advanced heuristics to establish a baseline of normal activity and proactively identify anomalies indicative of a compromise. Required elements include anomaly detection across multi-domain data sources such as network, host, user, and space specific telemetry; automated threat hunting correlating disparate indicators to reveal hidden patterns; predictive analytics identifying potential attack vectors before they are exploited; and natural language processing that automatically analyzes and correlates intelligence from multiple threat feeds. AI and ML capabilities should be trained in an operational-like environment to reduce noise and optimize detection, and should operate effectively in bandwidth constrained or contested environments common to space operations. Automated triage and prioritization of alerts is needed to reduce analyst fatigue and speed response times, along with AI assisted incident response recommendations informed by historical attack patterns and mission context.

Focus Area 7: AI-Driven Digital Supply Chain Illumination and Risk Management. The team wants a comprehensive digital supply chain risk management capability to safeguard the flow of software and hardware from vendors and suppliers. Proposed solutions should leverage artificial intelligence and advanced analytical tools to provide deep, multi-tier visibility and proactive risk identification across the entire supplier ecosystem. The capability should continuously monitor and analyze a wide range of data sources to deliver real-time intelligence on potential disruptions, including detecting cybersecurity risks such as data breaches or attacks within a supplier's network, as well as broader supplier and operational risks including material shortages, production delays, financial instability, or legal and labor issues. The system should use AI to identify and alert on emerging threats that could impact the ecosystem, protecting against both immediate cyber threats and long-term operational disruptions. By creating a unified view of the supply chain and automating vulnerability detection, this capability enables a move from a reactive to a predictive and resilient posture, ensuring the integrity and continuity of DCW systems.

Focus Area 8: Portable Edge Cyber Defense Kit. The team wants a lightweight, portable, plug-and-play fly-away kit for cyber threat detection, investigation, and response at remote and forward-deployed locations. As operations increasingly extend into austere environments, the Space Force wants a self-contained capability that functions effectively with limited or nonexistent network connectivity, addressing the challenge of robust cyber defense in disconnected, intermittent, and low-bandwidth settings where reliance on centralized security infrastructure is not feasible. The kit should empower operators to conduct local threat hunting and initial remediation, ensuring security of critical assets at the tactical edge. It should be engineered with a minimal physical footprint for portability and ease of deployment, and should possess onboard processing and analytical power to autonomously detect and investigate threats without real-time reach-back. A critical requirement is sufficient internal storage to collect and securely hold logs, forensic data, and other mission-critical artifacts for extended periods, and that stored data must be easily transferable so operators can push it to central analysis platforms for deeper post-mission analysis upon returning to a connected environment. The kit should provide an intuitive interface enabling an operator to effectively manage incidents and secure networks in the field, bridging the gap between disconnected operations and enterprise-level situational awareness.

Which focus area fits you

A short guide to self-selection. If you build data pipeline or observability infrastructure, look at Focus Areas 1 and 5. If you do SBOM generation, binary analysis, or software composition analysis, Focus Area 2, and if you do supplier risk intelligence, Focus Area 7. If you build embedded security or runtime monitoring for constrained systems, Focus Area 3, which is the most space-specific and most technically distinctive of the eight. If you build cyber ranges, digital twins, or training platforms, Focus Area 4. If you build behavioral detection, UEBA, or AI security analytics, Focus Area 6. If you build deployable forensic or incident response appliances, Focus Area 8.

The two focus areas with the highest barrier to entry, and therefore the least competition, are 3 and 4, because both require genuine space system knowledge. Focus Area 3 asks for monitoring on a 1553 Bus and SpaceWire in a minimal SWaP footprint, tested against a FlatSat. Focus Area 4 requires integration of a government-furnished DCW tool suite into your range. The other six are closer to adaptations of commercial cybersecurity products, which makes them more accessible and probably more crowded.

The Feasibility Requirement

Direct to Phase II means you must document that you already completed the Phase I equivalent work outside the SBIR program. The DAF disqualifies proposals where the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit, and applies that screen before evaluating technical merit.

What this topic requires, in three specific parts

The topic states it is intended for technology proven ready to move directly into Phase II, that Phase I awards will not be made, and that the applicant must provide detail and documentation in the D2P2 proposal demonstrating accomplishment of a Phase I type effort including a feasibility study. That includes determining, insofar as possible, the scientific and technical merit and feasibility of ideas appearing to have commercial potential. The applicant must have validated the product-mission fit between the proposed solution and a potential U.S. Air Force or Space Force stakeholder, and should have defined a clear, immediately actionable plan with the proposed solution and the DAF customer and end-user.

Then the topic lists three things the feasibility study should have. These are unusually explicit and you should mirror them as headings.

First, clearly identified the potential stakeholders of the adapted solution for solving the USAF or USSF needs.

Second, described the pathway to integrating with DAF operations, to include how the applicant plans to accomplish core technology development, navigate applicable regulatory processes, and integrate with other relevant systems or processes.

Third, described if and how the solution can be used by other Department of Defense or Governmental customers.

Notice that all three are about customers, integration pathways, and regulatory navigation rather than about technical performance. For a commercial cybersecurity company, that is the real bar on this topic. Your product probably works. What the Space Force is checking is whether you have identified who inside the USSF would use it, whether you understand the accreditation and integration path, and whether you can articulate broader government demand. If you have not had those conversations, that is the gap, and four weeks is not much time to close it.

The general D2P2 rules

The feasibility work must have been substantially performed by the applicant or the principal investigator.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists for companies that matured technology outside the SBIR pipeline.

If technology in the feasibility documentation is subject to intellectual property rights, provide IP rights assertions, plus a short summary for each item asserted with less than unlimited rights describing the nature of the restriction and the intellectual property intended for use in the proposed research.

Feasibility documentation can be included as part of Volume 5 and is required of all proposal submissions.

Phase II and Phase III Expectations

Phase II: proposed solutions should develop and demonstrate innovative technologies to support operations as part of the Space Force's cyberspace warfare for space operations. Solutions should address one or more of the eight focus areas.

Phase III: potential Phase III efforts will pursue transition of the capability to operational use through non-SBIR/STTR funding streams, aiming for a Technology Readiness Level of 6 or 7 and demonstrating functionality in relevant environments. Phase II efforts that demonstrate technical maturity, integration feasibility, and mission alignment may be selected for continued development and deployment into operational environments.

During Phase III, performers may be expected to advance system readiness, demonstrate operational capability, enable cross-service application, and pursue dual-use commercialization. Phase III work may be performed with non-SBIR/STTR funding and can include further government-sponsored prototyping, operational transition activities, or commercialization via strategic partners in the defense and aerospace sectors.

The reference the Air Force cites for this topic is the GAO Technology Readiness Assessment Guide, at gao.gov/assets/gao-20-48g.pdf. That is a meaningful hint. If you are going to make TRL claims, and the Phase III target is stated as TRL 6 or 7, use the GAO guide's definitions rather than your own informal scale, and cite it.

Funding Allowance and Cost Structure

Award ceiling

Up to $2,000,000 across up to 24 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The DAF also notes that per-award and per-topic funding caps are budgetary estimates only, more or less funding may become available, multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none. Funding decisions are made with complete disregard to the other awards under the same topic.

Because this topic has eight focus areas and the Government may award multiple times, do not assume you are competing against every other proposal. You are most directly competing against other proposals in your focus area, though the topic does not commit to distributing awards across focus areas.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards, and per the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

Technical and Business Assistance

Up to $50,000 per Phase II award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. Applicants may elect to use $25,000 on a first SBIR Phase II award and $25,000 on a sequential SBIR Phase II award.

TABA can only fund the activities in 15 U.S.C. 638(q)(1)(A) through (E): access to a network of scientists and engineers, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature through online databases. Those activities must serve one of these purposes: making better technical decisions, solving technical problems arising during the project, minimizing technical risks, developing and commercializing new commercial products and processes including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.

The detailed request must appear in Volume 5, including provider name, point of contact with email and phone, an explanation of the provider's unique qualifications, the tasks the provider will perform including purpose and objective, and total provider cost with hours and labor rates. Average or blended rates are acceptable. The task milestone list must track to the milestone payment schedule otherwise provided by the applicant. Requests that only specify a request value in the Volume 3 Cost Proposal will not be considered.

If using TABA to hire new staff, augment staff, or direct staff into training, provide names and positions, the business need to be filled or training to be provided, the number of employees to be hired, augmented, or directed into training, their qualifications or the detailed need for training, the tasks to be performed with a description of the activity and the purpose it serves, and total staff or training cost with hours and labor rates.

Cost volume expectations

A detailed cost proposal by individual cost element and by contractor fiscal year, in sufficient detail to determine the basis for estimates and the purpose, necessity, and reasonableness of each. Cost proposal attachments do not count toward page limits, and cost proposal information will be treated as proprietary.

Direct labor: key personnel by name where possible, labor category otherwise, with direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual, which the Contracting Officer needs to determine whether hours, fringe rates, and hourly rates are fair and reasonable. For a software-heavy proposal this will be the dominant cost element and deserves the most care.

Direct cost materials: an itemized list of types, quantities, prices, and where appropriate purpose. For planned computer or software purchases, detailed information such as manufacturer, price quotes, proposed use, and support for the need will be required. Cloud infrastructure, commercial software licenses, and development hardware belong here.

Other direct costs: specialized services such as machining or milling, special test and analysis, and costs for temporary use or lease of specialized facilities or equipment, with usage hours, rates, sources, and justification. Leased hardware requires a lease versus purchase rationale. FlatSat access or cyber range infrastructure, depending on your focus area, may live here.

Special tooling, special test equipment, and material: carefully reviewed relative to need and appropriateness, must in the Contracting Officer's opinion be advantageous to the Government and relate directly to the effort, and should not be of a type an applicant would otherwise possess in the normal course of business.

Subcontracts: supported with copies of subcontract agreements adequately describing the work and cost bases, including a statement of work, assigned personnel, hours and rates, materials, and proposed travel. A letter from a subcontractor agreeing to perform a task at a fixed price is expressly not sufficient. The prime must accomplish price analysis including reasonableness, identifying the basis where prior efforts are used for comparison, and provide cost analysis where price analysis techniques are inadequate or the FAR requires cost or pricing data.

Consultants: a separate agreement letter for each, stating the service, hours required, and hourly rate, plus a short concise resume.

Travel: each effort should include at a minimum a kickoff or interim meeting, with destinations, trips, travelers, airfare, per diem, lodging, and ground transportation justified against the Joint Travel Regulation.

Indirect costs: indicate proposed rate bases, identify specific rates and allocation bases, and provide rates and applications per fiscal year across the anticipated performance period. Do not propose composite rates.

Non-SBIR governmental or private investment is allowed but not required and will not be a proposal evaluation factor.

If no exceptions are taken to your proposal, the Government may award a contract without exchanges, so your initial proposal should contain your best terms from a cost, price, and technical standpoint.

Work performance requirements

The instructions state two thresholds that do not obviously align. The Consultants and Subcontractors section requires, per the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer. The Performance of Work Requirements section states that for Phase II a minimum of one-third of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit. Separately, the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price unless approved in writing by the Contracting Officer.

Planning to perform at least half the R/R&D in house and keeping all outside costs below half the contract price satisfies every reading. This is usually easier on a software topic than a hardware one, but watch cloud and licensing costs if you are treating them as purchases. If you cannot meet the thresholds, requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission. Given the ambiguity between the two stated thresholds, raise it with the DAF SBIR/STTR One Help Desk early.

Where work must be performed

All R/R&D must be performed in the United States by the small business and its team members. Based on rare and unique circumstances the DAF may approve a particular portion of the work to be performed or obtained outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Requests must accompany the initial proposal submission.

This deserves particular attention on a cybersecurity topic. Distributed engineering teams and offshore development are common in commercial software, and this requirement rules that out for the funded work absent specific written approval.

Export Control and Foreign Nationals

The technology in this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including sensitive technical data, and EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by those individuals. The topic advises that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

A foreign national means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR CSO and disclose regardless of whether the topic is subject to ITAR.

Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations to verify eligibility.

For projects with military or dual-use applications developing beyond fundamental research, the contractor must comply with all U.S. export control laws, is responsible for obtaining appropriate licenses or approvals including for deemed exports of hardware, technical data, and software, must obtain export licenses before using foreign persons including where work is performed on-site at any Government installation whether inside or outside the United States, is responsible for regulatory record keeping associated with the use of licenses and exemptions, and must ensure these provisions apply to its subcontractors.

If asserting export-controlled status, a certified DD Form 2345, or evidence of application submission, belongs in Volume 5, and DD Form 2345 approval will be required if the proposal is selected for award.

There is a notable interaction with Focus Area 2. That focus area asks for the ability to trace software origin and development lineage, providing critical intelligence on contributions from foreign nationals or known adversaries. If you are proposing that capability, your own team composition and development practices are fair territory for scrutiny. Be prepared for that consistency check.

Proposal Structure: The Seven Volumes

Formatting

Type no smaller than 11-point on standard 8.5 by 11 paper, one-inch margins, pages consecutively numbered. This differs from Army SBIR instructions, which allow 10-point.

The technical volume limit is 20 pages or slides, and pages in excess will not be considered by the Government in evaluations. Because the limit is expressed as pages or slides, a slide-format volume is acceptable.

Twenty pages is tight for a topic with this much surface area. The strategic implication is to be decisive about scope: name your focus area or areas in the first paragraph, and do not spend pages surveying the other seven. A proposal that gestures at breadth across all eight focus areas will read as unfocused and will run out of room to substantiate anything.

Proposals should be direct, concise, and informative. Applicants are discouraged from including promotional and non-programmatic items, and if included that material counts toward the page limit. Marketing material will not be evaluated. Preferred format is PDF, graphics must be distinguishable in black and white, and all submissions must be virus-checked.

Volume 6 Fraud, Waste, and Abuse training must be completed before submission, and DSIP will not allow submission until it is complete and certified. The DAF recommends completing submission early because site traffic is heavy prior to close and causes system lag, will not be responsible for proposals not completely submitted before the deadline due to system inaccessibility unless advised by DoW, and will not accept submission outside DSIP.

Volume 1, Cover Sheet

Per DSIP instructions. The technical abstract should include a brief description of program objectives, a description of the effort, anticipated benefits, commercial applications, and a list of keywords and terms. The abstract of each successful proposal goes to the Office of the Secretary of War for publication and must not contain proprietary or classified information. If selected for funding, the technical abstract and discussion of anticipated benefits will be publicly released. For a cybersecurity topic, take care that your abstract does not disclose detection methods or architecture detail you consider protected.

Volume 2, Technical Volume

Required items in the order provided: table of contents immediately after the cover sheet; glossary of acronyms and abbreviations; milestone identification with a program schedule showing all key milestones; identification and significance of the problem or opportunity; Phase II technical objectives with technical approach and methods and an assessment of potential commercial application for each objective; work plan; deliverables; related work; commercialization potential; relationship with future R/R&D efforts; key personnel; facilities and equipment; consultants and subcontractors; and prior, current, or pending support of similar proposals or awards.

The work plan is a separate and distinct part of the proposal package, divided from the technical proposal by a page break and begun on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility, and must not contain proprietary information, because if the proposal is selected the work plan will be incorporated into the resulting contract by reference. Recommended format is 1.0 Objective, a brief overview of the specialty area explaining purpose and expected outcome; 2.0 Scope, concisely describing the work including technology area, goals, and major milestones, with task development and deliverables as key elements, consistent with section 4.0; 3.0 Background, identifying appropriate specifications, standards, and other documents applicable to the effort, constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task and Technical Requirements, with detailed individual task descriptions developed in orderly progression with sufficient detail to establish overall program requirements and goals, work segregated into major tasks in separately numbered paragraphs, each major task delineated by subtask. The work plan must contain every task to be accomplished in definite, realistic, and clearly stated terms. Use "shall" for binding provisions, "should" or "may" to express a declaration or purpose, and "will" when no contractor requirement is involved.

Deliverables must clearly describe the specific sample or prototype hardware and software to be delivered, plus data deliverables, schedules, and quantities. Be aware of the possible unique item identification requirement under DFARS 252.211-7003 for hardware, which matters if you are proposing Focus Area 8's fly-away kit or Focus Area 4's physical FlatSat. If hardware or software will be developed but not delivered, provide an explanation. At minimum all Phase II contracts require Scientific and Technical Reports. Rights in technical data including software developed under a SBIR contract generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the contract for a period of 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page is a single-page project summary identifying the work's purpose, briefly describing the effort accomplished, and listing potential result applications, which may be published by DoW and therefore must not contain proprietary or classified information. Status reports are due quarterly at a minimum. The Air Force may require additional reporting including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project results in partial or total development and delivery of hardware, and updates to commercialization results.

For a software company, the 20 year SBIR data rights provision is the single most commercially significant clause in this document. Read it with counsel before you decide what code you are willing to develop under this award.

Related work must describe significant activities directly related to the proposed effort, including previous programs conducted by the principal investigator, proposing firm, consultants, or others, and their application to the proposed project, describe how these activities interface with the proposed project, and discuss planned coordination with outside sources. List any applicant-identified subject matter experts regardless of affiliation, providing comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related but similar, with a short description, the client for which the work was performed including an individual to be contacted and phone number, and the date of completion.

Commercialization potential requires a commercialization plan addressing what the first planned product to incorporate the proposed technology is, who the probable customers are and the estimated market size, how much money is needed to bring the technology to market and how it will be raised, whether the firm has the necessary marketing expertise and if not how it will compensate, and who the probable competitors are and what price or quality advantage is anticipated. Commercial potential is evidenced by the existence of private sector or non-SBIR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and other indicators of commercial technology potential including the firm's commercialization strategy. If awarded, the awardee must periodically update commercialization results via SBA. The Commercialization Plan and the Company Commercialization Report are distinct documents.

Relationship with future R/R&D efforts must state the anticipated results of the proposed approach, specifically addressing plans for Phase III if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III effort if planned. Given that the topic states a Phase III target of TRL 6 or 7 and cites the GAO Technology Readiness Assessment Guide, use GAO TRL definitions here.

Key personnel must identify all key personnel with information directly related to education, experience, and citizenship, and include a technical resume for the principal investigator with publications. Concise technical resumes for subcontractors and consultants are also useful. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for those individuals provide countries of origin, type of visa or work permit held, and identify the tasks they are anticipated to perform. The principal investigator's primary employment must be with the small business concern at the time of award and during the entire period of performance, where primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager may be designated per proposal.

Facilities and equipment must describe instrumentation and physical facilities necessary and available to carry out the effort, justify equipment to be purchased with detail in the cost proposal, and state whether proposed performance locations meet federal, state, and local environmental laws and regulations for airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors: private companies, consultants, or universities may be involved and all should be described in detail and included in the cost proposal. Signed copies of all consultant or subcontractor letters of intent must be attached, briefly stating the contribution or expertise being provided, with statements of work, detailed cost proposals, and information regarding unique qualifications. Subcontract copies and supporting documents do not count against the Phase II page limit, which is a useful relief valve on a 20 page topic. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support: while it is permissible with proper notification to submit identical proposals or proposals containing a significant amount of essentially equivalent work for consideration under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort, and any potential for that situation must be disclosed to the solicitation agencies before award. If your proposal is substantially the same as another submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, indicate so on the cover sheet and provide the agency names and addresses, submission or award dates, proposal titles, PI names and titles, solicitation titles, numbers and dates, contract numbers if awarded, and the applicable topics for each. If the section does not apply, state so in the proposal and certify on the cover sheet, "No prior, current, or pending support for proposed work."

This section matters more than usual on this topic, because a commercial cybersecurity company with a mature product may well have submitted similar material to other agencies. Disclose fully.

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Required in DSIP. The DAF states that information contained in the CCR will not be considered during proposal evaluations, unlike Army SBIR practice. Complete it for compliance.

Volume 5, Supporting Documents

May be required if applicable: DD Form 2345, which applies to this export-controlled topic; Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 CSO; and Technical Data Rights Assertions if asserting data rights restrictions. That last one deserves attention here. A commercial cybersecurity product built on years of private investment almost certainly carries background IP you want to protect, and asserting those restrictions properly is how you do it.

Required of all submissions: feasibility documentation as described above, including IP rights assertions with a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material, which will not be evaluated.

Volume 6, Fraud, Waste, and Abuse Training

Complete once per year, before submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Complete the webform in Volume 7 of the DSIP submission. It will not be accepted as a PDF supporting document in Volume 5, and do not upload previous versions of the form to Volume 5.

How Your Proposal Will Be Evaluated

The criteria for this topic

DV512 is evaluated under the criteria set covering DV026, DV511, DV512, and DV513, in descending order of importance.

Criteria A, most important: the soundness, technical merit, and innovation of the proposed approach and its incremental progress toward topic or subtopic solution, and the qualifications of the proposed principal and key investigators, supporting staff, and consultants. This includes whether the proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the unique methods of performance and materials described in the technical proposal.

Note the phrase "toward topic or subtopic solution." With eight focus areas, the subtopic language is doing work: you are being assessed on progress toward the focus area you selected, so name it explicitly and frame your progress against it.

Criteria B, second: the degree of mission impact and the urgency of the identified need, the specificity of the defense requirement addressed, and the adequacy of the proposed effort in fulfilling the research topic or subtopic solution.

Criteria C, third: the potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

For a commercial cybersecurity firm, the counterintuitive lesson is that Criteria C, where you are probably strongest, is the least important of the three. Your commercial traction is useful evidence but it does not carry the proposal. The weight sits on technical merit against a specific Space Force focus area and on mission urgency, which means your proposal needs to be written in the Space Force's language rather than repurposed from commercial marketing.

General evaluation process

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel, with confidential proposal and evaluation information protected to the greatest extent possible. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

Selections are based on a determination of the overall technical value of each proposal and an evaluation of the cost volume for selection of the proposals most advantageous to the Government. Where technical evaluations are essentially equal in merit, cost or price will be considered in determining successful applicants. All evaluation criteria other than cost or price, when combined, are significantly more important than cost or price. The DAF is seeking varying technical and scientific approaches and varying and new technologies responsive to the problem statements and areas of interest in the topic, multiple procurements are planned and anticipated, each proposal is considered a separate procurement evaluated on its own merit, and the Government may award all, some, or none of the proposals.

Foreign risk evaluation

The DAF will evaluate all small business concerns submitting under this release on whether they present a security risk, using the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947, federal law enforcement, and other counterintelligence capabilities of the United States Government.

The risk-based assessment covers cybersecurity practices, patent analysis, employee analysis, foreign ownership including financial ties and obligations covering surety, equity, and debt obligations of the concern and its employees to a foreign country, person, or entity, foreign affiliations of a covered individual, owner, or other key personnel with an entity in a foreign country of concern, investment relationships with an individual or entity in a foreign country of concern, technology licensing agreements or joint ventures including joint venture like agreements with an individual or entity in a foreign country of concern, and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

Cybersecurity practices lead that list, and on this topic in particular the assessment of your own security posture carries obvious weight. A company proposing to defend Space Force systems should expect its own practices to be examined closely.

The DAF also assesses proposals using open-source analysis and analytical tools for nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examines any relationship of the concern to any entity or individual on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses security risks, it may either create a plan to mitigate them or decide not to select the proposal based upon a totality of the review.

Awards must be denied under 15 U.S.C. 638(g)(16) or 638(o)(20) where the concern has an owner or covered individual party to a malign foreign talent recruitment program; a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; an owner or covered individual with a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or a security risk connecting the concern, including any affiliates, to an entity or individual on the UFLPA Entity List maintained by the Department of Homeland Security, the Non-SDN Chinese Military-Industrial Complex Companies List maintained by Treasury's Office of Foreign Assets Control, the Section 889 Prohibition List, the Section 1260H list of Chinese Military Companies, the Military End User List maintained by Commerce's Bureau of Industry and Security, the Entity List maintained by BIS, the FCC List of Equipment and Services, or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection. Awards are also denied where the concern has a security risk with a primary source that is classified, or a security risk the DAF determines warrants denial.

Applicants must disclose under penalty of perjury the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7, and must provide a written statement of any substantial changes to the foreign disclosure form to the awarding agency within 30 days of any changes while on a project for the DAF.

If an award is denied on these grounds, the DAF will as appropriate and in a manner that does not compromise security provide notification advising the small business of the determination, the basis for it, and a statement that denial does not prohibit eligibility for an award in a subsequent award cycle.

Ownership, support contractors, status, and protests

Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics. This is relevant on a cybersecurity topic, where venture funding is the norm.

Proposals may be handled for administrative purposes only by support contractors, which may include APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. Only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporation working under contract to provide technical support to Air Force Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the DAF SBIR/STTR Contracting Officer with concerns about any of these contractors.

The principal investigator and Corporate Official indicated on the cover sheet will be notified by email regarding selection or non-selection, with a separate notification for each proposal submitted. Read each notification carefully and note the proposal number and topic number referenced. Automated feedback is provided for proposals designated Not Selected, and additional feedback may be provided at the sole discretion of the DAF. Proposals are received and evaluated by different organizations, handled by topic, each operating on its own schedule, so notification timeframes vary.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for proposal status before that time. Protests after award should be submitted, as prescribed in FAR 33.106(b) and FAR 52.233-3, to the Air Force SBIR/STTR Contracting Officer and to the individual procuring contracting officer listed on the firm's selection notification. Final reports go to the awarding DAF organization per contract instructions, not directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. Choose your focus area. That decision governs everything else, and it should be driven by where you have deployed product and documented results. Assemble the feasibility package around the three named elements: identified USAF or USSF stakeholders for your adapted solution, the pathway to integrating with DAF operations including core technology development, regulatory navigation, and integration with other systems, and whether and how other DoD or governmental customers could use it. Determine your export control posture and confirm which team members are U.S. persons under the stated definition. Review your own cybersecurity practices, since they are the first item on the foreign risk assessment list. Inventory your background IP so you can assert data rights properly. Complete Volume 6 training, verify SAM and DSIP alignment, and send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries.

September 23 through October 3. Draft Volume 2 against the 20 page limit. Name your focus area in the opening paragraph. Build the milestone schedule early, since the TABA task milestone list must track to your milestone payment schedule. If you are proposing Focus Area 3 or 4, address FlatSat or simulation environment access explicitly, and for Focus Area 4 address integration of the government-furnished DCW tool suite.

October 4 through October 12. Build the cost volume by element and by fiscal year, with individual named labor rates, cloud and license costs itemized, and indirect rates per fiscal year with no composite rates. Collect signed letters of intent, statements of work, and detailed cost proposals from every consultant and subcontractor, remembering that a letter agreeing to a fixed price is not sufficient. Check your work-performance percentages against the thresholds and the one-half outside cost cap. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5 including Technical Data Rights Assertions and DD Form 2345, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics legible in black and white, virus-checked PDF, no marketing material, and no proprietary content in the technical abstract or the work plan.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-DV512?

‍ ‍

DAF26BX06-DV512 is a Department of the Air Force SBIR Direct to Phase II topic titled "Cyberspace Warfare for Space," released under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. SpaceWERX, partnering with Cyberspace Warfare professionals in the U.S. Space Force, seeks next generation capabilities to defend space systems from adversarial attack through the cyber domain, organized into eight focus areas.

‍ ‍

How much funding is available under DAF26BX06-DV512?

‍ ‍

Up to $2,000,000 for a period of performance up to 24 months. Proposals exceeding either limit will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition to that ceiling.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

Do I have to address all eight focus areas?

‍ ‍

No. Proposals should address one or more of the eight focus areas. Choose the area where you have genuine product maturity and documented feasibility evidence, name it explicitly in your proposal, and resist the temptation to claim breadth across all eight. With a 20 page limit, a diffuse proposal cannot substantiate anything.

‍ ‍

What are the eight focus areas?

‍ ‍

Lightweight and cloud-agnostic data ingest; defensive cyber warfare systems with proactive software assurance and malware detection; on-orbit space vehicle cyber defense and monitoring; an immersive space cyber test environment; adaptive data parsers and a transformation engine; AI-driven cyber threat detection; AI-driven digital supply chain illumination and risk management; and a portable edge cyber defense kit.

‍ ‍

Which focus area is the best fit for my company?

‍ ‍

Data pipeline and observability companies should look at Focus Areas 1 and 5. SBOM, binary analysis, and software composition analysis companies at Focus Area 2, and supplier risk intelligence at Focus Area 7. Embedded security and runtime monitoring for constrained systems at Focus Area 3. Cyber ranges, digital twins, and training platforms at Focus Area 4. Behavioral detection and AI security analytics at Focus Area 6. Deployable forensic and incident response appliances at Focus Area 8.

‍ ‍

Which focus areas have the least competition?

‍ ‍

Focus Areas 3 and 4 carry the highest barrier to entry because both require real space system knowledge. Focus Area 3 requires monitoring a 1553 Bus and SpaceWire in a minimal SWaP footprint with FlatSat or simulation-based testing. Focus Area 4 requires integrating a government-furnished DCW tool suite into your training platform. The other six are closer to adaptations of commercial cybersecurity products and are likely more crowded.

‍ ‍

What does Focus Area 3 require technically?

‍ ‍

A persistent monitoring solution deployed directly onto the Space Vehicle that identifies and, in approved instances, autonomously responds to malicious activity in real time, integrating with existing ground-based DCW systems so all telemetry and alerts reach terrestrial monitoring centers. Monitoring must cover unauthorized software, firmware, or critical configuration changes, traffic on essential non-redundant components such as the 1553 Bus and SpaceWire, and anomalous behavior including irregular commands or malware uploads, with sensitivity to indicators targeting core subsystems such as power manipulation, system timing interference, or unauthorized payload function commands. Minimal size, weight, and power impact is required, and software-based solutions with a negligible resource footprint are strongly preferred. Development and testing will likely use high-fidelity environments such as a FlatSat or realistic simulations.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This topic is intended for technology proven ready to move directly into Phase II, and Phase I awards will not be made.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

Detail and documentation demonstrating accomplishment of a Phase I type effort including a feasibility study, plus validated product-mission fit between your solution and a potential USAF or USSF stakeholder and a clear, immediately actionable plan with the DAF customer and end-user. The feasibility study should have clearly identified the potential stakeholders of the adapted solution for solving USAF or USSF needs, described the pathway to integrating with DAF operations including core technology development, applicable regulatory processes, and integration with other relevant systems or processes, and described if and how the solution can be used by other DoD or governmental customers.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility effort must have been substantially performed by the applicant or the principal investigator.

‍ ‍

How long can my technical volume be?

‍ ‍

20 pages or slides. Pages in excess will not be considered during evaluations. Type must be no smaller than 11-point on 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Subcontract copies, supporting documents, and cost proposal attachments do not count toward the limit.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. You must disclose any proposed foreign nationals with countries of origin, visa or work permit type, and the statement of work tasks intended for them, and the topic advises those individuals may be restricted from performing. A certified DD Form 2345, or evidence of application, belongs in Volume 5, and approval will be required if selected for award.

‍ ‍

Can my offshore development team work on this?

‍ ‍

No, absent specific written approval. All R/R&D must be performed in the United States by the small business and its team members. The DAF may approve a particular portion of work performed or obtained outside the United States only based on rare and unique circumstances, with written approval from the awarding Funding Agreement officer for each specific condition, and the request must accompany the initial proposal submission.

‍ ‍

How is my proposal evaluated?

‍ ‍

Under three criteria in descending order of importance. Criteria A, most important, covers soundness, technical merit, and innovation of the approach, incremental progress toward the topic or subtopic solution, the qualifications of key personnel, and whether proposed cost elements are realistic and consistent with the technical proposal. Criteria B covers degree of mission impact, urgency of the identified need, specificity of the defense requirement, and adequacy of the effort. Criteria C covers commercial application potential. All criteria other than cost or price, combined, are significantly more important than cost or price.

‍ ‍

My company has strong commercial traction. Does that carry the proposal?

‍ ‍

Not by itself. Commercialization is Criteria C, the least important of the three. Technical merit against the specific focus area you selected and mission urgency carry the weight, which means the proposal has to be written in the Space Force's terms rather than repurposed from commercial materials.

‍ ‍

Who owns the software I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. For a software company, this is the most commercially significant clause in the instructions and warrants review with counsel before you decide what to develop under the award.

‍ ‍

How do I protect my existing intellectual property?

‍ ‍

Technical Data Rights Assertions are listed as a Volume 5 document if you are asserting data rights restrictions. Separately, if technology in your feasibility documentation is subject to IP rights, you must provide IP rights assertions plus a short summary for each item asserted with less than unlimited rights, describing the nature of the restriction and the intellectual property intended for use in the proposed research.

‍ ‍

How much of the work must my company perform?

‍ ‍

The instructions state two thresholds. The Consultants and Subcontractors section requires at least 50 percent of the R/R&D be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. The Performance of Work Requirements section states at least one-third of the Phase II research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility leases, and other subcontract or purchase agreements together may not exceed one-half of the total contract price without written Contracting Officer approval. Performing at least half in house satisfies every reading. Deviation requests must be made twice, prior to submission during the open period and again with the initial proposal.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 is required, but the DAF states information contained in the CCR will not be considered during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, splittable as $25,000 on a first SBIR Phase II and $25,000 on a sequential one. Cybersecurity assistance and intellectual property protections are both eligible activities. The detailed request must be in Volume 5 with provider name, point of contact, unique qualifications, tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests specifying only a value in Volume 3 will not be considered.

‍ ‍

What happens in Phase III?

‍ ‍

Phase III pursues transition to operational use through non-SBIR/STTR funding streams, aiming for TRL 6 or 7 and demonstrating functionality in relevant environments. Phase II efforts demonstrating technical maturity, integration feasibility, and mission alignment may be selected for continued development and deployment. Performers may be expected to advance system readiness, demonstrate operational capability, enable cross-service application, and pursue dual-use commercialization. Phase III work may include further government-sponsored prototyping, operational transition activities, or commercialization via strategic partners in the defense and aerospace sectors.

‍ ‍

Are venture-backed companies eligible?

‍ ‍

Yes. Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates all proposals evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The principal investigator and Corporate Official on the cover sheet are notified by email, with a separate notification per proposal.

‍ ‍

Who do I contact with questions?

‍ ‍

The DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Pick one focus area and commit. This is the single most consequential decision on this topic. Twenty pages does not permit a survey. Name the focus area in your first paragraph, structure the proposal around it, and let your feasibility evidence be about that area specifically.

‍ ‍

Translate your product into Space Force language. A commercial SIEM connector becomes lightweight, cloud-agnostic data ingest for DCW systems at the edge or hub. A software composition analysis tool becomes proactive software assurance for FOSS and non-APL COTS with SBOM generation and development lineage tracing. Use the topic's own vocabulary, including DCW, FlatSat, purple teaming, orbital edge, and Approved Product List. Evaluators read for alignment, and the topic hands you the words.

‍ ‍

Close the stakeholder gap before you write. The feasibility requirement is fundamentally about customers and integration pathways, not technical performance. Identified USSF stakeholders, an integration pathway that accounts for regulatory processes, and articulated demand from other government customers are the three things the topic asks you to have already established. This is where a strong commercial product with no Space Force relationship will fail.

‍ ‍

Address the space-specific constraint in your focus area. Every focus area has one. Bandwidth constrained and contested environments in Focus Area 6. Space specific protocols in Focus Area 5. Minimal SWaP and 1553 and SpaceWire in Focus Area 3. Disconnected, intermittent, and low-bandwidth settings in Focus Area 8. A proposal that ignores the space-specific twist reads as a generic commercial pitch.

‍ ‍

Get your own security posture in order. Cybersecurity practices is the first item on the foreign risk assessment list, and CMMC Level 2 self-assessment is the projected requirement. A firm proposing to defend space systems will be judged on its own house.

‍ ‍

Read the data rights clause before you decide what to build. Twenty years of Government SBIR data rights in everything developed or generated under the contract, followed by Government purpose rights, is a significant commitment for a software company whose core asset is code. Structure the work so what you contribute as background IP is properly asserted and what you develop under the award is what you intend to give those rights in.

‍ ‍

Use the GAO TRL guide. The topic cites it and states a Phase III target of TRL 6 or 7. Using GAO definitions rather than an informal scale makes your maturity claims checkable, which supports Criteria A.

‍ ‍

Make cost realism match the work plan. Cost realism sits inside the top-weighted criterion. For a software effort, that mostly means credible labor: named people, real rates, hours that match the tasks. Understaffing a 24 month program to look cheap will read as a misunderstanding of the requirements.

‍ ‍

Disclose equivalent submissions honestly. A mature commercial product often means similar proposals elsewhere. The instructions permit that with proper notification but make it unlawful to enter into contracts requiring essentially equivalent effort. Full disclosure protects the award.

DAF SBIR DAF26BX06-DV511: Low SWaP-C Tactical Awareness Payload for Proliferated, Agile Satellites (TAPPAS) for Space Domain Awareness

Quick Answer

DAF26BX06-DV511 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. The Space Force wants a compact, low size, weight, power, and cost sensor payload that gives a host satellite persistent 4 pi steradian awareness of its own local space environment in geosynchronous orbit. Think of it as a self-awareness bubble: the satellite sees what is around it, tracks nearby objects autonomously, and assesses whether they are debris, unremarkable neutral objects, friendly, or a potential threat. The deliverable at the end of Phase II is a production representative article of flight qualifiable hardware. Awards are up to $3,000,000 for up to 24 months, with a 20 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

This is the largest award ceiling in the release and also the most hardware-committed. The government states plainly that its primary focus is on the speed of delivery for proven technology now. That framing should shape everything about your proposal: this is a manufacturing and qualification topic more than a research topic, and a proposal that reads as exploratory will lose to one that reads as production ready.

Topic At a Glance

Topic number: DAF26BX06-DV511

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

Solicitation: Department of the Air Force 2026 SBIR Commercial Solutions Opening (CSO), Release 6, Direct to Phase II

Program type: Direct to Phase II (D2P2), no Phase I awards will be made for this topic

Award maximum value: $3,000,000, the highest in this release

Award maximum duration: 24 months

Technical volume page limit: 20 pages or slides

Component Technology Priority Area: Space Technology

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Target orbit environment: Geosynchronous, the GEO belt

Expected maturity at Phase II completion: approximately TRL 6, a system or prototype demonstrated in a relevant environment

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: surveillance, space based surveillance, proliferation, constellation, resident space object, space domain awareness, geostationary orbit, GEO belt, visual magnitude, electro optical, infrared, radio frequency, free flyer, GEO SDA, low size weight and power, own-ship awareness, local area sensor

Note on the deadline time. The DAF instructions point applicants to the DoW FY26 SBIR CSO for the submission deadline date and time. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting rather than assuming end of day.

The Performance Requirements, Stated Plainly

These are the numbers your proposal will be measured against. State your position on each one explicitly.

Field of regard: persistent 4 pi steradian awareness of the local space environment for the host vehicle. Occlusion zones are probable and should be minimized based on satellite design and sensor placement.

Power: the ideal payload would not exceed 50 watts of power consumption.

Mass: the ideal payload would not exceed 15 kilograms.

Self-awareness bubble range: 200 kilometers as the threshold, 500 kilometers as the objective radius.

Detection sensitivity: ability to detect a 0.5 meter object as the threshold, down to 0.2 meter as the objective.

Detection confidence: probability of detection of 0.8 and probability of false alarm of 0.01.

Phenomenologies of interest: multiple, including but not limited to electro-optical, infrared, and radio frequency.

Bus compatibility: 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.

The topic softens the SWaP figures with the phrase "while any available tested technology will be considered," and calls the 50 watt and 15 kilogram figures ideal rather than absolute. Do not read that as permission to ignore them. Read it as an invitation to propose something proven that comes close, and to justify any excess against the platform integration argument the topic makes, which is that these characteristics are critical for enabling integration onto platforms with stringent resource limitations.

What the Space Force Is Actually Looking For

The operational logic

The modern space domain requires a layered sensing architecture to ensure resilience. This topic targets one element of that architecture: a compact, efficient payload that gives its host vehicle persistent local awareness.

The Space Force draws an explicit analogy to other warfighting domains. Following the traditions of air, maritime, and ground combat architectures, proliferated tactical sensors and their on-board assessment technology must become part of any combat system baseline. In plain terms, combat aircraft and ships carry their own sensors for self-protection as a matter of course, and satellites do not yet. This topic is about closing that gap.

The dual purpose is stated clearly. The effort targets the combination of in-space sensing and sense-making, with the goal of enabling both self-protection, through the organic ability to detect, track, and characterize immediate threats to support threat response, and contribution to shared awareness of the tactical space picture across the domain. So the payload serves the host vehicle and the broader Space Domain Awareness enterprise at the same time.

The payload capability is described as a critical enabler for mission resilience and ultimately space superiority, through greater autonomy, decision-agility, and survivability in contested space warfighting environments.

Beyond detection: the sense-making requirement

This is where the topic asks for more than a sensor. 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.

Four elements in that sentence deserve individual attention in your proposal. On-board analytics, meaning processing at the edge rather than downlinking raw data. Autonomous tracking. Object classification into debris, neutral or friendly, and potential threat categories, which is a characterization problem, not just a detection problem. And output that supports both machine action and human understanding.

A proposal that delivers excellent detection with no on-board sense-making has answered half the topic.

The four named key challenges

The topic lists four challenges to be addressed. Use them as an organizing structure, because they map to what the evaluators are looking for.

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, Manufacturing Readiness Level, and scalability for hardware and software. Note the explicit inclusion of Manufacturing Readiness Level. MRL is rarely called out in SBIR topics and its presence here reinforces the production orientation. Address your MRL directly.

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: optimize the payload to provide decision-quality information efficiently, with an architecture that allows for integration with enterprise data systems.

Phase II activities and success criteria

The successful completion of Phase II should be production of a production representative article, or PRA, that can be space qualified and meets the SWaP and performance requirements.

Four Phase II activities are named. Prototype fabrication and assembly: fabricate or procure necessary components to fabricate and test a PRA. Firmware and software development: develop and integrate firmware and software necessary to support processing of sensor data and provide output that can be ingested by the bus for autonomous operation, with necessary data formatted for further exploitation on the ground. Environmental and performance testing: conduct a comprehensive test campaign to validate payload performance and survivability, expected to include thermal-vacuum cycling representative of the GEO thermal environment, random vibration testing to assess launch survivability, and electromagnetic interference testing to ensure no harm to other space vehicle subsystems. Laboratory-based performance demonstration: conduct performance testing in a laboratory environment to validate key performance parameters.

Successful completion is determined by demonstration of three things: demonstrated performance of the unit, successful completion of space environmental testing covering TVAC, random vibration, and EMI, and demonstrated data output format.

Phase II deliverables

Five primary deliverables are listed. A Production Representative Article. Performance and environmental test data and reports, described as an End Item Data Package. A reliability analysis. A preliminary Interface Control Document. And ground software for commanding the sensor payload and processing telemetry and mission data.

Read that list against your 24 month schedule and $3,000,000 ceiling. Hardware fabrication, a full environmental test campaign at GEO-representative conditions, an ICD, a reliability analysis, and ground software is a substantial program. The proposals that win will show a credible schedule with test facility access identified, not an optimistic one.

Phase III

Phase III activities, funded through non-SBIR/STTR government contracts or other appropriate funding mechanisms, are intended to support continued maturation, qualification, and operational integration. The focus would be advancing the payload toward flight-qualified configurations suitable for incorporation into operational Space Domain Awareness mission architectures.

Potential Phase III activities include qualification of the payload design for space flight, refinement for manufacturability and scalability, integration support with host spacecraft platforms, and preparation for operational testing and evaluation. Where appropriate, Phase III may also support Low-Rate Initial Production planning and execution, subject to government priorities and funding availability.

On the maturity ladder: upon successful completion of Phase II the payload is expected to achieve approximately TRL 6, a system or prototype demonstrated in a relevant environment. Phase III efforts may mature the technology to TRL 8 through flight qualification and system-level testing, and ultimately to TRL 9 upon successful on-orbit deployment and operational use.

The topic notes that the full scope of potential Phase III efforts is defined in 15 U.S.C. 638 and the SBA SBIR/STTR Policy Directive Section 4(c), and that per Section 4(b)(2) of the Policy Directive the Government may, at its discretion, include Phase III procedures in its Phase II Funding Agreement. That last point is worth flagging to your counsel: a Phase III provision inside the Phase II agreement is a meaningful commercial advantage if it materializes.

The Feasibility Requirement

Direct to Phase II means you must document that you already did the Phase I equivalent work outside the SBIR program. The DAF disqualifies proposals where the Phase I equivalency documentation does not establish feasibility and technical merit, and applies that screen before evaluating technical merit.

What this topic requires

The topic states it is intended for technology proven ready to move directly into Phase II, and that Phase I awards will not be made. The applicant is required to provide detail and documentation in the D2P2 proposal demonstrating accomplishment of a Phase I type effort, including a feasibility study. That includes determining, insofar as possible, the scientific and technical merit and feasibility of ideas appearing to have commercial potential.

Then two specific requirements that are easy to under-deliver on. The applicant must have validated the product-mission fit between the proposed solution and a potential Air Force or Space Force stakeholder. And the applicant should have defined a clear, immediately actionable plan with the proposed solution and the DAF customer and end-user.

Notice what those two sentences require. Not just that your sensor works, but that you have engaged with a specific Air Force or Space Force stakeholder and validated that your solution fits their mission, and that you and that customer have a plan you could act on now. That is a business development requirement embedded in a technical feasibility requirement, and it cannot be manufactured in the four weeks the topic is open. If you have not had those conversations, that is the gap to close first.

The general D2P2 rules

The feasibility work must have been substantially performed by the applicant or the principal investigator.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists for companies that matured technology outside the SBIR pipeline.

If technology in the feasibility documentation is subject to intellectual property rights, provide IP rights assertions, plus a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research.

Feasibility documentation can be included as part of Volume 5 and is listed as required of all proposal submissions.

For a hardware topic like this one, useful feasibility evidence includes prior flight heritage of the sensor or its components, environmental test reports from non-SBIR work, breadboard or engineering unit performance data against the detection thresholds, and documented stakeholder engagement establishing the product-mission fit.

Funding Allowance and Cost Structure

Award ceiling

Up to $3,000,000 across up to 24 months. The topic index warns that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The DAF also notes that per-award and per-topic funding caps are budgetary estimates only, more or less funding may become available, multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none. Funding decisions are made with complete disregard to other awards under the same topic.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards, and per the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

A firm-fixed-price hardware program with a full environmental qualification campaign carries real cost risk. Build your estimate with that in mind, since the Government may award without exchanges if it takes no exceptions to your proposal, meaning your initial submission should carry your best terms rather than an opening position.

Technical and Business Assistance

Up to $50,000 per Phase II award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. Applicants may elect to use $25,000 on a first SBIR Phase II award and $25,000 on a sequential SBIR Phase II award.

TABA can only fund the activities in 15 U.S.C. 638(q)(1)(A) through (E): access to a network of scientists and engineers, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature through online databases. For this topic, development of manufacturing plans deserves a serious look, given the explicit Manufacturing Readiness Level emphasis and the Phase III scalability and Low-Rate Initial Production framing.

The detailed request must appear in Volume 5, including provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks the provider will perform including purpose and objective, and total provider cost with hours and labor rates. Average or blended rates are acceptable. The task milestone list must track to the milestone payment schedule otherwise provided by the applicant. Requests that only specify a value in the Volume 3 Cost Proposal will not be considered.

Cost volume expectations

A detailed cost proposal by individual cost element and by contractor fiscal year, in sufficient detail to determine the basis for estimates and the purpose, necessity, and reasonableness of each. Cost proposal attachments do not count toward page limits, and cost proposal information will be treated as proprietary.

For a hardware program, several cost volume elements carry unusual weight here.

Direct cost materials: an itemized list of types, quantities, prices, and where appropriate purpose. For planned computer or software purchases, detailed information such as manufacturer, price quotes, proposed use, and support for the need will be required. Long-lead space-qualified parts belong here with quotes.

Other direct costs: specialized services such as machining or milling, special test and analysis, and costs for temporary use or lease of specialized facilities or equipment, with usage hours expected, rates, sources, and a brief discussion of purpose and justification. Thermal-vacuum chamber time, vibration table time, and EMI chamber access all live in this category. Proposals including leased hardware must include an adequate lease versus purchase rationale.

Special tooling, special test equipment, and material: inclusion will be carefully reviewed relative to need and appropriateness to the work. Purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort, and should not be of a type an applicant would otherwise possess in the normal course of business. These may include innovative instrumentation or automatic test equipment.

Subcontracts: must be supported with copies of subcontract agreements adequately describing the work and cost bases, including a statement of work, assigned personnel, hours and rates, materials, and proposed travel. A letter from a subcontractor agreeing to perform a task at a fixed price is expressly not considered sufficient. The prime must accomplish price analysis including reasonableness of proposed subcontractor costs, and provide cost analysis where price analysis techniques are inadequate or the FAR requires cost or pricing data.

Consultants: a separate agreement letter for each, stating the service, hours required, and hourly rate, plus a short concise resume.

Travel: each effort should include at a minimum a kickoff or interim meeting, justified with destinations, trips, travelers, airfare, per diem, lodging, and ground transportation against the Joint Travel Regulation.

Indirect costs: indicate proposed rate bases, identify specific rates and allocation bases, and provide rates and applications per fiscal year across the anticipated performance period. Do not propose composite rates.

Non-SBIR governmental or private investment is allowed but not required and will not be a proposal evaluation factor.

Work performance requirements

The instructions state two thresholds that do not obviously align. The Consultants and Subcontractors section requires, per the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer. The Performance of Work Requirements section states that for Phase II a minimum of one-third of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit. Separately, the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price unless approved in writing by the Contracting Officer.

This is a live problem for space hardware specifically. If you are buying detector assemblies, procuring space-qualified components, and leasing TVAC and vibration facilities, those costs accumulate against the one-half cap quickly. Model your cost distribution early. Planning to perform at least half the R/R&D in house and keeping all outside costs below half the contract price satisfies every reading.

If you cannot meet it, requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission. Given the ambiguity between the stated thresholds, raise it with the DAF SBIR/STTR One Help Desk early in the open period.

Where work must be performed

All R/R&D must be performed in the United States by the small business and its team members. Based on rare and unique circumstances the DAF may approve a particular portion of the work to be performed or obtained outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Requests must accompany the initial proposal submission.

Export Control, Which Is Explicit on This Topic

The technology in this topic is restricted under ITAR 22 CFR Parts 120-130, which controls the export and import of defense-related material and services including export of sensitive technical data, and the EAR 15 CFR Parts 730-774, which controls dual use items.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit possessed, and the statement of work tasks intended for accomplishment by those individuals. The topic advises that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

A foreign national means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR CSO and disclose regardless of whether the topic is subject to ITAR.

Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which the instructions note prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer.

For projects with military or dual-use applications developing beyond fundamental research, the contractor must comply with all U.S. export control laws, is responsible for obtaining appropriate licenses or approvals including for deemed exports of hardware, technical data, and software, must obtain export licenses before using foreign persons including where work is performed on-site at any Government installation whether inside or outside the United States, is responsible for regulatory record keeping associated with licenses and exemptions, and must ensure these provisions apply to its subcontractors.

If asserting export-controlled status, a certified DD Form 2345 Militarily Critical Technical Data Agreement, or evidence of application submission, belongs in Volume 5, and DD Form 2345 approval will be required if the proposal is selected for award.

Space sensing companies frequently employ non-U.S. persons in engineering roles. Resolve who can work on what before you build your key personnel section.

Proposal Structure: The Seven Volumes

Formatting, with a note about the tighter page limit

Type no smaller than 11-point on standard 8.5 by 11 paper, one-inch margins, pages consecutively numbered. This differs from Army SBIR instructions, which allow 10-point.

The technical volume limit for this topic is 20 pages or slides, notably tighter than the 35 pages allowed for the two air-domain topics in the same release. Pages in excess will not be considered by the Government in evaluations. That constraint matters here because the topic asks for a great deal: performance against seven or eight numeric requirements, four named challenges, four Phase II activities, five deliverables, environmental test planning, and a commercialization plan. Ruthless economy is required. Push resumes, subcontract documents, and cost detail into the volumes where they do not count against the limit.

Proposals should be direct, concise, and informative. Applicants are discouraged from including promotional and non-programmatic items, and if included, such material counts toward the page limit. Marketing material will not be evaluated.

Preferred submission format is PDF, graphics must be distinguishable in black and white, and all submissions must be virus-checked. Note that "pages or slides" means a slide-format technical volume is acceptable, which many hardware teams find more efficient for conveying design and test information within a tight limit.

Volume 6 Fraud, Waste, and Abuse training must be completed before submission, and DSIP will not allow submission until it is complete and certified. The DAF recommends completing submission early because site traffic is heavy prior to close and causes system lag, will not be responsible for proposals not completely submitted before the deadline due to system inaccessibility unless advised by DoW, and will not accept submission outside DSIP.

Volume 1, Cover Sheet

Per DSIP instructions. The technical abstract should include a brief description of program objectives, a description of the effort, anticipated benefits, commercial applications, and a list of keywords and terms. The abstract of each successful proposal goes to the Office of the Secretary of War for publication and must not contain proprietary or classified information. If selected for funding, the technical abstract and discussion of anticipated benefits will be publicly released, so keep sensitive design detail out of it.

Volume 2, Technical Volume

Required items in the order provided: table of contents immediately after the cover sheet; glossary of acronyms and abbreviations; milestone identification with a program schedule showing all key milestones; identification and significance of the problem or opportunity; Phase II technical objectives with technical approach and methods and an assessment of potential commercial application for each objective; work plan; deliverables; related work; commercialization potential; relationship with future R/R&D efforts; key personnel; facilities and equipment; consultants and subcontractors; and prior, current, or pending support of similar proposals or awards.

The work plan is a separate and distinct part of the package, divided from the technical proposal by a page break and begun on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility, and must not contain proprietary information, because if the proposal is selected the work plan will be incorporated into the resulting contract by reference. Recommended format is 1.0 Objective, a brief overview of the specialty area explaining purpose and expected outcome; 2.0 Scope, a concise description of the work including technology area, goals, and major milestones, with task development and deliverables as key elements, consistent with section 4.0; 3.0 Background, identifying applicable specifications, standards, and other documents, constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task and Technical Requirements, with detailed individual task descriptions in orderly progression, sufficient detail to establish overall program requirements and goals, work segregated into major tasks in separately numbered paragraphs, each delineated by subtask. Every task must appear in definite, realistic, clearly stated terms. Use "shall" for binding provisions, "should" or "may" for a declaration or purpose, and "will" where no contractor requirement is involved.

For this topic, the work plan is where your environmental test campaign, PRA fabrication sequence, and deliverable production get expressed contractually. Because it becomes part of the contract by reference, be deliberate about which statements you make binding with "shall."

Deliverables must clearly describe the specific sample or prototype hardware and software to be delivered, plus data deliverables, schedules, and quantities. Be aware of the possible requirement for unique item identification under DFARS 252.211-7003, Item Identification and Valuation, for hardware, which is directly relevant to a Production Representative Article. If hardware or software will be developed but not delivered, provide an explanation. At minimum all Phase II contracts require Scientific and Technical Reports. Rights in technical data including software developed under a SBIR contract generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page is a single-page project summary identifying purpose, briefly describing the effort accomplished, and listing potential result applications, which may be published by DoW and therefore must contain no proprietary or classified information. Status reports are due quarterly at a minimum. The Air Force may require additional reporting including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project results in partial or total development and delivery of hardware, and updates to commercialization results.

Related work must describe significant directly related activities including previous programs conducted by the principal investigator, proposing firm, consultants, or others, their application to the proposed project, how they interface with it, and planned coordination with outside sources. List any applicant-identified subject matter experts regardless of affiliation with comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related but similar, with a short description, the client including an individual to be contacted and phone number, and the date of completion.

Commercialization potential requires a commercialization plan with the Phase II proposal addressing the first planned product to incorporate the technology, probable customers and estimated market size, how much money is needed to bring the technology to market and how it will be raised, whether the firm has necessary marketing expertise and how it will compensate if not, and probable competitors with the anticipated price or quality advantage. Commercial potential is evidenced by the existence of private sector or non-SBIR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and other indicators of commercial technology potential including the firm's commercialization strategy. If awarded, the awardee must periodically update commercialization results via SBA, at completion of the effort and when submitting a new SBIR/STTR proposal to DoW, with annual updates requested from firms not submitting new proposals. The Commercialization Plan and the Company Commercialization Report are distinct documents.

Relationship with future R/R&D efforts must state the anticipated results of the proposed approach, specifically addressing plans for Phase III if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III effort if planned. Given how specific this topic is about the TRL 6 to TRL 8 to TRL 9 path and Low-Rate Initial Production, this section should track that language.

Key personnel must identify all key personnel with information directly related to education, experience, and citizenship, and include a technical resume for the principal investigator with publications. Concise technical resumes for subcontractors and consultants are also useful. Identify all non-U.S. citizens expected to be involved as direct employees, subcontractors, or consultants, and for those individuals provide countries of origin, type of visa or work permit held, and the tasks they are anticipated to perform. The principal investigator's primary employment must be with the small business at the time of award and during the entire period of performance, where primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager may be designated per proposal.

Facilities and equipment must describe instrumentation and physical facilities necessary and available to carry out the effort, justify equipment to be purchased with detail in the cost proposal, and state whether proposed performance locations meet federal, state, and local environmental laws and regulations for airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials. For this topic, identify your access to TVAC, vibration, and EMI test facilities here, whether owned or contracted.

Consultants and subcontractors: private companies, consultants, or universities may be involved, all should be described in detail and included in the cost proposal, and signed copies of all consultant or subcontractor letters of intent must be attached, briefly stating the contribution or expertise being provided, with statements of work, detailed cost proposals, and information regarding unique qualifications. Subcontract copies and supporting documents do not count against the page limit, which is a meaningful relief valve on a 20 page topic. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support: while it is permissible with proper notification to submit identical proposals or proposals containing a significant amount of essentially equivalent work under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort, and any potential for that must be disclosed to the solicitation agencies before award. If substantially the same as another proposal submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, indicate so on the cover sheet and provide agency names and addresses, submission or award dates, proposal titles, PI names and titles, solicitation titles, numbers and dates, contract numbers if awarded, and applicable topics. If the section does not apply, state so in the proposal and certify on the cover sheet, "No prior, current, or pending support for proposed work."

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Required in DSIP. The DAF states that information contained in the CCR will not be considered during proposal evaluations, which differs from Army SBIR practice. Complete it for compliance.

Volume 5, Supporting Documents

May be required if applicable: DD Form 2345, which applies to this export-controlled topic; Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 CSO; and Technical Data Rights Assertions if asserting data rights restrictions.

Required of all submissions: feasibility documentation as described above, including IP rights assertions with a short summary for each item asserted with less than unlimited rights.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material.

Volume 6, Fraud, Waste, and Abuse Training

Complete once per year, before submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Complete the webform in Volume 7 of the DSIP submission. It will not be accepted as a PDF supporting document in Volume 5, and previous versions of the form must not be uploaded to Volume 5.

How Your Proposal Will Be Evaluated

The criteria for this topic

DV511 is evaluated under the criteria set covering DV026, DV511, DV512, and DV513, in descending order of importance.

Criteria A, most important: the soundness, technical merit, and innovation of the proposed approach and its incremental progress toward topic or subtopic solution, and the qualifications of the proposed principal and key investigators, supporting staff, and consultants. This includes whether the proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the unique methods of performance and materials described in the technical proposal.

Criteria B, second: the degree of mission impact and the urgency of the identified need, the specificity of the defense requirement addressed, and the adequacy of the proposed effort in fulfilling the research topic or subtopic solution.

Criteria C, third: the potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

Two implications for a hardware proposal. First, cost realism lives inside the top-weighted criterion, and on a firm-fixed-price hardware program with a qualification test campaign, an unrealistic cost estimate is a technical credibility problem, not just a pricing problem. If your work plan promises TVAC, random vibration, and EMI testing, your cost volume must show facility access, hours, and rates that make that plausible. Second, "incremental progress toward topic solution" rewards showing where you start and where you land. Anchor your current maturity honestly and show the delta.

General evaluation process

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel, with confidential proposal and evaluation information protected to the greatest extent possible. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

Selections are based on a determination of the overall technical value of each proposal and an evaluation of the cost volume for selection of the proposals most advantageous to the Government. Where technical evaluations are essentially equal in merit, cost or price will be considered. All evaluation criteria other than cost or price, when combined, are significantly more important than cost or price. The DAF is seeking varying technical and scientific approaches and varying and new technologies responsive to the problem statements and areas of interest, multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none.

Foreign risk evaluation

The DAF will evaluate all small business concerns submitting under this release on whether they present a security risk, using the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947, federal law enforcement, and other counterintelligence capabilities of the United States Government.

The risk-based assessment covers cybersecurity practices, patent analysis, employee analysis, foreign ownership including financial ties and obligations covering surety, equity, and debt obligations of the concern and its employees to a foreign country, person, or entity, foreign affiliations of a covered individual, owner, or other key personnel with an entity in a foreign country of concern, investment relationships with an individual or entity in a foreign country of concern, technology licensing agreements or joint ventures including joint venture like agreements with an individual or entity in a foreign country of concern, and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern. The DAF also assesses proposals using open-source analysis and analytical tools for nondisclosures of information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examines any relationship of the concern to any entity or individual on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses security risks, it may either create a mitigation plan or decide not to select the proposal based on a totality of the review.

Awards must be denied under 15 U.S.C. 638(g)(16) or 638(o)(20) where the concern has an owner or covered individual party to a malign foreign talent recruitment program; a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; an owner or covered individual with a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or a security risk connecting the concern, including any affiliates, to an entity or individual on the UFLPA Entity List maintained by DHS, the Non-SDN Chinese Military-Industrial Complex Companies List maintained by Treasury's Office of Foreign Assets Control, the Section 889 Prohibition List, the Section 1260H list of Chinese Military Companies, the Military End User List maintained by Commerce's Bureau of Industry and Security, the Entity List maintained by BIS, the FCC List of Equipment and Services, or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection. Awards are also denied where the concern has a security risk with a primary source that is classified, or a security risk the DAF determines warrants denial.

Applicants must disclose under penalty of perjury the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7, and must provide a written statement of any substantial changes to the foreign disclosure form to the awarding agency within 30 days while on a DAF project.

For space hardware, the parts supply chain is the exposure. Detectors, focal plane assemblies, radiation-tolerant compute, and passive components frequently trace to suppliers with entries on one or more of those lists. Audit the bill of materials against them before you propose.

Ownership, support contractors, status, and protests

Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics. That matters on this topic in particular, since venture-funded space companies are the natural applicant pool.

Proposals may be handled for administrative purposes only by support contractors, which may include APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. Only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporation working under contract to provide technical support to Air Force Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Concerns about any of these contractors go to the DAF SBIR/STTR Contracting Officer.

The principal investigator and Corporate Official indicated on the cover sheet will be notified by email regarding selection or non-selection, with a separate notification for each proposal submitted. Automated feedback is provided for proposals designated Not Selected, and additional feedback may be provided at the sole discretion of the DAF. Proposals are received and evaluated by different organizations, handled by topic, each operating on its own schedule, so notification timeframes vary.

The DAF anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for status before that time. Protests after award should be submitted, as prescribed in FAR 33.106(b) and FAR 52.233-3, to the Air Force SBIR/STTR Contracting Officer and to the individual procuring contracting officer listed on the firm's selection notification. Final reports go to the awarding DAF organization per contract instructions, not directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. The hardest items here are not writing tasks. Confirm your stakeholder validation: you need a documented product-mission fit with an Air Force or Space Force stakeholder and an immediately actionable plan with that customer. Secure written commitments or at least confirmed availability for TVAC, random vibration, and EMI test facility access within your schedule window, because the cost volume needs rates and hours. Get quotes for long-lead space-qualified parts. Audit your bill of materials against the foreign entity denial lists. Resolve export control staffing questions, since the topic warns foreign nationals may be restricted. Start DD Form 2345 if you do not hold one. Complete Volume 6 training, verify SAM and DSIP alignment, and send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries.

September 23 through October 3. Draft Volume 2 against the 20 page limit, which will require several passes to compress. Build a compact requirements response covering 4 pi steradian coverage and occlusion minimization, 50 watts, 15 kilograms, 200 to 500 kilometer bubble, 0.5 to 0.2 meter detection, probability of detection 0.8 and false alarm 0.01, phenomenologies, TRL and MRL, and common power, data, and thermal interfaces. Consider a slide-format volume, which the page or slide limit permits and which suits hardware and test content.

October 4 through October 12. Build the cost volume by element and fiscal year, with materials quotes, test facility usage hours and rates, special test equipment justification, and indirect rates per fiscal year with no composite rates. Collect signed letters of intent, statements of work, and detailed cost proposals from every subcontractor and consultant, since a letter agreeing to a fixed price is not sufficient. Check the one-half subcontract and purchase agreement cap and your R/R&D percentage. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics legible in black and white, virus-checked PDF, no marketing material, no proprietary content in the technical abstract or the work plan.

October 17 through October 19. Submit and certify in DSIP.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-DV511?

‍ ‍

DAF26BX06-DV511 is a Department of the Air Force SBIR Direct to Phase II topic titled "Low SWaP-C Tactical Awareness Payload for Proliferated, Agile Satellites (TAPPAS) for Space Domain Awareness," released under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. It seeks a compact sensor payload providing a host satellite persistent 4 pi steradian awareness of its local space environment in the GEO belt, with on-board analytics that autonomously track and characterize nearby objects.

‍ ‍

How much funding is available under DAF26BX06-DV511?

‍ ‍

Up to $3,000,000 for a period of performance up to 24 months, the largest ceiling in this release. Proposals exceeding either limit will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions point to the DoW FY26 SBIR CSO for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

What are the size, weight, and power targets?

‍ ‍

The ideal payload would not exceed 50 watts of power consumption and 15 kilograms of mass. The topic frames these as ideal rather than absolute, noting any available tested technology will be considered, but states these characteristics are critical for enabling integration onto platforms with stringent resource limitations. If you exceed them, justify it against the integration argument.

‍ ‍

What detection performance is required?

‍ ‍

A self-awareness bubble with a range of 200 kilometers threshold to 500 kilometers objective radius, the ability to detect a 0.5 meter object at threshold and 0.2 meter at objective, with a probability of detection of 0.8 and a probability of false alarm of 0.01. Coverage is persistent 4 pi steradian, with occlusion zones minimized through satellite design and sensor placement.

‍ ‍

What sensing phenomenologies are of interest?

‍ ‍

Multiple, including but not limited to electro-optical, infrared, and radio frequency.

‍ ‍

Is this only a sensor, or does it need onboard processing?

‍ ‍

It needs onboard processing. The sensor data must feed advanced on-board analytics that autonomously track nearby objects and support assessment of intent, distinguishing between debris, unanticipated neutral or friendly objects, and potential threats, enabling both autonomous tactical response and intuitive operator visualization. A detection-only proposal answers half the topic.

‍ ‍

What is the Phase II deliverable?

‍ ‍

Successful Phase II completion should produce a Production Representative Article that can be space qualified and meets the SWaP and performance requirements. The five primary deliverables are the PRA, performance and environmental test data and reports as an End Item Data Package, a reliability analysis, a preliminary Interface Control Document, and ground software for commanding the payload and processing telemetry and mission data.

‍ ‍

What environmental testing is expected?

‍ ‍

A comprehensive test campaign validating payload performance and survivability, expected to include thermal-vacuum cycling representative of the GEO thermal environment, random vibration testing to assess launch survivability, and electromagnetic interference testing to ensure no harm to other space vehicle subsystems. Successful completion is determined in part by successful completion of that space environmental testing.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This topic is intended for technology proven ready to move directly into Phase II, and Phase I awards will not be made.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

Detail and documentation demonstrating accomplishment of a Phase I type effort including a feasibility study, determining insofar as possible the scientific and technical merit and feasibility of ideas appearing to have commercial potential. Critically, you must have validated the product-mission fit between your proposed solution and a potential Air Force or Space Force stakeholder, and should have defined a clear, immediately actionable plan with the proposed solution and the DAF customer and end-user.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility effort must have been substantially performed by the applicant or the principal investigator.

‍ ‍

How long can my technical volume be?

‍ ‍

20 pages or slides for this topic, tighter than the 35 pages allowed for the two air-domain topics in the same release. Pages in excess will not be considered during evaluations. Type must be no smaller than 11-point on 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Note that subcontract copies, supporting documents, and cost proposal attachments do not count toward the limit.

‍ ‍

Can I submit slides instead of a written document?

‍ ‍

The limit is expressed as pages or slides, so a slide-format technical volume is acceptable. Many hardware teams find slides more efficient for conveying design and test content within a tight limit.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. You must disclose any proposed foreign nationals with countries of origin, visa or work permit type, and assigned statement of work tasks, and the topic advises those individuals may be restricted from performing due to the technical data involved. A certified DD Form 2345, or evidence of application, belongs in Volume 5, and approval will be required if selected.

‍ ‍

How is my proposal evaluated?

‍ ‍

Under three criteria in descending order of importance. Criteria A, most important, covers soundness, technical merit, and innovation of the approach, incremental progress toward a solution, the qualifications of key personnel, and whether proposed cost elements are realistic and consistent with the technical proposal. Criteria B covers degree of mission impact, urgency of the identified need, specificity of the defense requirement, and adequacy of the effort. Criteria C covers commercial application potential. All criteria other than cost or price, combined, are significantly more important than cost or price.

‍ ‍

Does Manufacturing Readiness Level matter?

‍ ‍

Yes, and unusually so. One of the four named key challenges is scalable, mature, and manufacturable solutions, which explicitly requires emphasis on high Technology Readiness Level, Manufacturing Readiness Level, and scalability for hardware and software. MRL is rarely called out in SBIR topics, and its presence signals a production orientation. Address your MRL directly.

‍ ‍

How much of the work must my company perform?

‍ ‍

The instructions state two thresholds. The Consultants and Subcontractors section requires at least 50 percent of the R/R&D be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. The Performance of Work Requirements section states at least one-third of the Phase II research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements together may not exceed one-half of the total contract price without written Contracting Officer approval. That last cap is a real constraint on space hardware programs that buy components and lease test facilities. Performing at least half the R/R&D in house satisfies every reading; deviation requests must be made twice, prior to submission during the open period and again with the initial proposal.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 is required, but the DAF states information contained in the CCR will not be considered during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, splittable as $25,000 on a first SBIR Phase II and $25,000 on a sequential one. The detailed request must be in Volume 5 with provider name, point of contact, unique qualifications, tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests specifying only a value in Volume 3 will not be considered. Development of manufacturing plans is an eligible activity worth considering on this topic.

‍ ‍

Who owns the data and software I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years from contract award, after which the Government has Government purpose rights to the SBIR data.

‍ ‍

What happens in Phase III?

‍ ‍

Phase III, funded through non-SBIR/STTR government contracts or other appropriate mechanisms, supports continued maturation, qualification, and operational integration, advancing the payload toward flight-qualified configurations for operational Space Domain Awareness mission architectures. Potential activities include space flight qualification of the design, refinement for manufacturability and scalability, integration support with host spacecraft platforms, preparation for operational testing and evaluation, and where appropriate Low-Rate Initial Production planning and execution subject to government priorities and funding. The Government may, at its discretion, include Phase III procedures in the Phase II Funding Agreement per SBA Policy Directive Section 4(b)(2).

‍ ‍

What technology readiness level is expected?

‍ ‍

Upon successful completion of Phase II the payload is expected to achieve approximately TRL 6, a system or prototype demonstrated in a relevant environment. Phase III may mature it to TRL 8 through flight qualification and system-level testing, and ultimately TRL 9 upon successful on-orbit deployment and operational use.

‍ ‍

Are venture-backed companies eligible?

‍ ‍

Yes. Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates all proposals evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The principal investigator and Corporate Official on the cover sheet are notified by email.

‍ ‍

Who do I contact with questions?

‍ ‍

The DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Read "speed of delivery for proven technology now" as the governing sentence. The government wrote that its primary focus is speed of delivery for proven technology. That is a direct instruction about what wins. Existing hardware with test heritage, an established supply chain, and a manufacturing path beats a better architecture that needs to be invented.

‍ ‍

Answer the numbers in a compact traceability section. With eight or so quantitative requirements and only 20 pages, a tight requirements response near the front of the volume earns its space. Meet, exceed, or path to meet with the risk named, for each one.

‍ ‍

Do not neglect the sense-making half. Many sensor companies will propose excellent detection and treat the on-board analytics as a software afterthought. The topic asks for autonomous tracking, characterization into debris, neutral or friendly, and potential threat, and output serving both autonomous response and operator visualization. That is a distinguishing opportunity.

‍ ‍

Put Manufacturing Readiness Level in writing. It is named as a key challenge alongside TRL. Give your MRL, justify it, and describe the production scaling path. Very few competitors will do this well.

‍ ‍

Prove your test facility access with specifics. TVAC at GEO-representative conditions, random vibration, and EMI within 24 months is a scheduling problem before it is a technical one. Named facilities, confirmed availability, and rates in the cost volume make the schedule believable and directly support the cost realism element inside Criteria A.

‍ ‍

Close the stakeholder validation gap now, not in the proposal. The feasibility requirement demands validated product-mission fit with an Air Force or Space Force stakeholder and an immediately actionable plan with that customer. If you have not had those conversations, that is the binding constraint on your eligibility, and the open period is short.

‍ ‍

Model the subcontract cap before you finalize the architecture. Buying focal planes, procuring space-qualified parts, and leasing test chambers can push your outside costs past one-half of the contract price. Discovering that after you have committed to a design is expensive.

‍ ‍

Audit the supply chain against the eight denial lists. Space electronics bills of materials touch them more often than teams expect, and a denial under 15 U.S.C. 638(g)(16) or 638(o)(20) is mandatory, not discretionary.

‍ ‍

Build the commercialization case on the commercial GEO market. Criteria C is third in importance but should not be thin. Commercial GEO operators, satellite manufacturers who would embed the payload as a baseline subsystem, and insurers with an interest in collision and proximity risk are all natural buyers for local space awareness, and the topic's own framing of proliferated tactical sensors as part of any combat system baseline generalizes cleanly to commercial fleets.

DAF SBIR DAF26BX06-DP027: OPEN Topic, Proliferated Low-Altitude Detection for Counter-sUAS

Quick Answer

DAF26BX06-DP027 is a Department of the Air Force SBIR Direct to Phase II open topic under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. The Air Force is trying to solve what it calls the "sneaky drone" problem: detecting, tracking, and identifying small, low-altitude, terrain-masked, and radio-frequency-silent Group 1 through 3 unmanned aircraft around permanent bases. The wanted solution is a low-cost network of perimeter sensor nodes that can spot a drone that is not emitting anything, fuse all sensor data at a node into a single track, and integrate with the Medusa command and control system. Awards are up to $2,000,000 for up to 24 months, with a 35 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.

Three features make this topic unusual and worth understanding before you write. First, it carries hard numeric performance thresholds, including a full-rate production cost target of less than $100,000 for the system, which is a stringent constraint that will disqualify many otherwise capable sensor architectures. Second, because it is an open topic, a small business concern may submit only one proposal to it, and if you submit more than one, only the most recent certified proposal is evaluated while all prior ones are marked nonresponsive. Third, it uses a different evaluation rubric than the other topics in this release, one where Defense Need carries equal weight with Technical Approach.

Topic At a Glance

Topic number: DAF26BX06-DP027

Title: OPEN, Proliferated Low-Altitude Detection for C-sUAS

Solicitation: Department of the Air Force 2026 SBIR Commercial Solutions Opening (CSO), Release 6, Direct to Phase II

Program type: Direct to Phase II (D2P2) open topic, no Phase I awards, Phase I proposals will be rejected

Award maximum value: $2,000,000

Award maximum duration: 24 months

Technical volume page limit: 35 pages or slides

OUSD (R&E) Critical Technology Area: Quantum and Battlefield Information Dominance (Q-BID)

Component Technology Priority Areas: Trusted AI and Autonomy; Integrated Sensing and Cyber

Projected CMMC level requirement: Level 2 (Self)

Proposals allowed per company: one, because this is an open topic

Transition customers named: AFLCMC/ES and the JIATF-401 counter-UAS marketplace

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: sensor network, sensors, acoustic, optical, radio frequency, C-sUAS, sneaky drone, RF-silent dark drone, base defense

Note on the deadline time. The DAF instructions point applicants to the DoW FY26 SBIR CSO for the submission deadline date and time rather than restating it. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Verify the exact time on the live DSIP posting and do not plan around an end-of-day deadline.

What Makes This an Open Topic, and Why It Matters

The DAF states that this release contains an open topic, and under section 7 of the SBIR and STTR Extension Act of 2022, innovation open topic activities are meant to increase the transition of commercial technology to the Department of War, expand the small business nontraditional industrial base, increase commercialization derived from DoW investments, and expand the ability for qualifying small businesses to propose technology solutions that meet DoW needs.

The practical difference the DAF draws is this: unlike conventional topics, which specify the desired technical objective and output, open topics can use generalized mission requirements or specific technology areas to adapt commercial products or solutions to close capability gaps, improve performance, or provide technological advancements in existing capabilities.

In practice DP027 sits somewhere in between. It is labeled OPEN, and it invites adaptation of commercial sensing products, but it also carries very specific numeric requirements. Read it as an invitation to bring a commercial sensor product to a defined base defense problem, not as an invitation to propose whatever you like.

The rule that follows from open-topic status is strict and mechanical. A small business concern may only submit one proposal to each open topic. If more than one proposal from a single concern is received for a single open topic, only the most recent proposal to be certified and submitted prior to the submission deadline will receive an evaluation. All prior proposals submitted by that concern for the same open topic will be marked nonresponsive and will not receive an evaluation.

If your company has more than one candidate architecture, you must choose before you submit. And if you submit early and then decide to submit a revised version, understand that the earlier one is simply discarded rather than considered as an alternative.

What the Air Force Is Actually Looking For

The problem statement

Small drones that do not emit radio frequency energy are hard to find. Most fielded counter-UAS detection depends on picking up the control link or video downlink. A drone flying a preprogrammed route with its radios off, hugging terrain at low altitude, defeats that approach. The Air Force calls this the sneaky drone problem, and this topic is aimed squarely at it.

The DAF describes this as a focused open topic seeking counter-small-UAS detection options for transition into the USAF and USSF, specifically supporting AFLCMC/ES and the JIATF-401 marketplace. The effort seeks low-cost detection and recognition sensors configured as a perimeter network for early warning of low-flying drones.

The hard performance requirements

These numbers are the specification. Treat them as pass or fail gates in your proposal, and state explicitly where you meet or exceed each.

Detection altitude band: the system must detect targets from 1 meter up to 300 meters as the threshold, and 500 meters as the objective, off the ground.

Per-node horizontal detection range: individual sensor nodes must detect targets at a horizontal range of at least 100 meters.

Aggregate coverage: the nodes must integrate to create at least 10 kilometers of combined linear boundary coverage.

Full-rate production cost: the final system must cost less than $100,000 at full-rate production.

Target class: Group 1 through 3 UAS.

Operating conditions: the sensors must work in cluttered environments and recognize non-RF-emitting "dark" drones, meaning the system must distinguish a drone from something that is not a drone.

Data fusion: the system must integrate data from all sensors at a node into a single track, providing at least the target's heading along with the absolute location of the detecting node.

Control: the system must feature remote node control and be fully controllable via external API commands.

C2 integration: the system must be able to integrate into the Medusa C2 system or other Air Force directed C2.

The constraint that is deliberately relaxed

This is important and easy to miss. Solutions are strictly for permanent base defense applications. Therefore, strict size and weight limitations do not apply, and systems can rely on direct or off-grid permanent power.

That is a meaningful design freedom. If your sensor concept was previously ruled out because it was too heavy, too large, or too power-hungry for a tactical or mobile application, this topic removes that objection. Do not compress your architecture to hit SWaP targets that this topic does not impose. Do use that freedom to hit the detection performance and cost requirements instead.

Phase II deliverable

Deliver a field-ready, production-representative, low-cost, scalable network of sensors prototype capable of recognizing Group 1 through 3 drone targets up to altitudes of 300 meters threshold and 500 meters objective. The system must recognize non-RF-emitting targets both day and night. It must integrate with the Medusa C2 system or other Air Force directed C2.

Environmental and hardening requirements for Phase II are specific. The hardware must be ruggedized for real-world environmental conditions, demonstrating an ingress protection of at least IP65, operability in ambient relative humidity up to 95 percent non-condensing, and temperature tolerances from minus 32 degrees Celsius to 55 degrees Celsius. The system must include anti-tamper features for critical components and be capable of receiving an ATO or IATO.

Proposals should include development, demonstration, and test and evaluation of the proposed solution prototype.

The ATO requirement deserves attention. Receiving an Authority to Operate or Interim Authority to Operate is a cybersecurity accreditation process, not a technical performance milestone, and it takes time and documentation discipline. Address your plan for it explicitly rather than asserting capability.

Phase III and commercial applications

Phase III is transition to AFLCMC/ES and the JIATF-401 counter-UAS marketplace for base defense. Named commercial dual-use applications are airport security, critical infrastructure protection, and border patrol.

The references the Air Force cites reinforce the airport and infrastructure framing: a March 2024 GAO report on federal efforts to address unauthorized drone flights near airports, the Department of Defense Counter-Small Unmanned Aircraft Systems Strategy, the summary of the 2024 National Defense Authorization Act, and the June 2025 statement for the record by General Michael Kurilla, then Commander of U.S. Central Command, before the Senate Committee on Armed Services on the posture of U.S. Central Command.

The Feasibility Requirement

Direct to Phase II means you must already have done the Phase I equivalent work, outside the SBIR program, and be able to document it. The DAF will disqualify proposals where the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit, and it applies that screen before evaluating technical merit.

What this topic specifically requires

The topic states that the Government requires the applicant to have accomplished a Phase I type effort accomplished outside of the SBIR program through other means. To demonstrate feasibility, the applicant must have developed and validated a working prototype that has been tested in a simulated or non-operational relevant environment.

Then it gets specific about what the prototype must have shown. The applicant must demonstrate that their system is capable of detecting and tracking non-RF emitting Group 1 through 3 UAS at low altitudes while outputting basic track and sensor node location data.

That is a tight, checkable claim. Your feasibility documentation needs to show three things: detection and tracking of non-emitting targets, in the Group 1 to 3 class, at low altitude, with track output plus node location. Test data against cooperative RF-emitting targets does not satisfy this. Detection without tracking does not satisfy it. Tracking without location output does not satisfy it.

The general D2P2 rules that also apply

The feasibility work must have been substantially performed by the applicant or the principal investigator. Work performed by someone else does not qualify.

Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. This authority exists for companies that matured technology outside the SBIR pipeline.

If technology in your feasibility documentation is subject to intellectual property rights, you must provide IP rights assertions, plus a short summary for each item asserted with less than unlimited rights describing the nature of the restriction and the intellectual property intended for use in the proposed research.

Feasibility documentation can be included as part of Volume 5, and is listed as required of all proposal submissions.

Funding Allowance and Cost Structure

Award ceiling

Up to $2,000,000 across up to 24 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

The DAF also notes in the evaluation section that per-award and per-topic funding caps are budgetary estimates only, that more or less funding may become available, and that multiple procurements are planned with each proposal treated as a separate procurement evaluated on its own merit. The Government may award all, some, or none of the proposals, and funding decisions are made with complete disregard to other awards under the same topic.

The $100,000 production cost target is a design requirement, not a budget line

Do not confuse the two dollar figures in this topic. The $2,000,000 is what the Government may pay you to develop the prototype. The under $100,000 figure is what the resulting system must cost at full-rate production. That second number is a technical requirement that shapes your entire sensor selection and architecture.

Because this is a network of nodes covering at least 10 kilometers of linear boundary, the cost engineering question is what a node can cost and how many you need. A proposal that does not address unit cost, node count, and the path to the sub-$100,000 system cost has left a central requirement unanswered. Show the bill of materials logic at production volume, not at prototype volume.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards. In accordance with the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

Technical and Business Assistance

The DAF will provide up to $50,000 per Phase II award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. Applicants may elect to use $25,000 on a first SBIR Phase II award and $25,000 on a sequential SBIR Phase II award.

TABA can only fund the activities in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature through online databases. For this topic, cybersecurity assistance and development of manufacturing plans are worth considering given the ATO requirement and the production cost target.

The detailed request must appear in Volume 5 Supporting Documents and must include the provider name, point of contact with email and phone, an explanation of the provider's unique qualifications, the tasks the provider will perform including purpose and objective, and total provider cost with hours and labor rates. Average or blended rates are acceptable. The task milestone list must track to the milestone payment schedule otherwise provided by the applicant. TABA requests that only specify a request value in the Volume 3 Cost Proposal will not be considered.

If using TABA to hire or augment staff or fund training, provide names and positions, the business need or training to be provided, the number of employees involved, their qualifications or the detailed training need, and total staff or training cost with hours and labor rates.

Cost volume expectations

A detailed cost proposal broken out by individual cost element and by contractor fiscal year, in sufficient detail to determine the basis for estimates and the purpose, necessity, and reasonableness of each. Cost proposal attachments do not count toward page limits, and cost proposal information will be treated as proprietary.

Direct labor requires key personnel by name where possible, labor category otherwise, with direct labor hours, labor overhead or fringe, and actual hourly rates for each individual. Direct cost materials require an itemized list of types, quantities, prices, and purpose, and for planned computer or software purchases, manufacturer, price quotes, proposed use, and support for the need. Other direct costs cover specialized services such as machining or milling, special test and analysis, and temporary use or lease of specialized facilities or equipment, with usage hours, rates, sources, and justification, and leased hardware needs a lease versus purchase rationale. Special tooling and special test equipment must be advantageous to the Government in the Contracting Officer's opinion, relate directly to the effort, and not be items an applicant would ordinarily possess in the normal course of business.

Subcontract costs must be supported with copies of subcontract agreements adequately describing the work and cost bases, including a statement of work, assigned personnel, hours and rates, materials, and proposed travel. A letter from a subcontractor agreeing to perform at a fixed price is expressly not sufficient. The prime must accomplish price analysis including reasonableness of proposed subcontractor costs, and provide cost analysis where price analysis techniques are inadequate or the FAR requires cost or pricing data.

Consultants require a separate agreement letter each, stating the service, hours required, and hourly rate, plus a short resume. Travel should include at a minimum a kickoff or interim meeting, justified against the Joint Travel Regulation. Indirect costs require proposed rate bases, the specific rates and allocation bases, and rates and applications per fiscal year across the anticipated performance period, with no composite rates.

Non-SBIR governmental or private investment is allowed but not required and will not be a proposal evaluation factor.

If no exceptions are taken to your proposal, the Government may award without exchanges, so your initial proposal should contain your best terms from a cost, price, and technical standpoint.

Work performance requirements

The instructions contain two statements that do not obviously align. The Consultants and Subcontractors section states that per the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer. The Performance of Work Requirements section states that for Phase II, a minimum of one-third of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit. Separately, the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements may not exceed one-half of the total contract price unless approved in writing by the Contracting Officer.

Planning to perform at least half the R/R&D in house and keeping all outside costs below half the contract price satisfies every reading. If your teaming structure cannot, requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission. Given the ambiguity between the two stated thresholds, raise it with the DAF SBIR/STTR One Help Desk early.

This is a live concern for sensor topics specifically, because a network combining acoustic, optical, and RF modalities often means buying subsystems from multiple suppliers. Watch the subcontract and purchase agreement total against the one-half cap.

Where work must be performed

All R/R&D must be performed in the United States by the small business and its team members. Based on rare and unique circumstances, the DAF may approve a particular portion of the work to be performed or obtained outside the United States, with written approval from the awarding Funding Agreement officer for each specific condition. Requests must be made with the initial proposal submission.

Foreign Nationals and Export Control

Unlike three of the other topics in this release, DP027 does not carry a topic-level ITAR and EAR restriction notice. That does not remove your disclosure obligations.

All applicants proposing to use foreign nationals must follow the FY26 SBIR CSO and disclose this information regardless of whether the topic is subject to ITAR restrictions. In the technical volume, identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants, and for those individuals provide, in addition to technical resumes, countries of origin, the type of visa or work permit held, and the tasks they are anticipated to perform.

A foreign national means any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b.

Where a topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives, which prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer. Additional information may be requested during negotiations to verify eligibility.

For all projects with military or dual-use applications developing beyond fundamental research, the contractor must comply with all U.S. export control laws including ITAR 22 CFR Parts 120 through 130 and EAR 15 CFR Parts 730 through 799, is responsible for obtaining appropriate licenses or approvals including for deemed exports of hardware, technical data, and software, must obtain export licenses before using foreign persons including where work is performed on-site at a Government installation, is responsible for regulatory record keeping, and must ensure these provisions apply to its subcontractors.

Counter-UAS sensing is a domain where export control questions arise readily, so form a view on your own classification early rather than assuming the absence of a topic-level notice settles it. If you are asserting export-controlled status, a certified DD Form 2345 or evidence of application submission goes in Volume 5.

Proposal Structure: The Seven Volumes

Formatting

Type no smaller than 11-point on standard 8.5 by 11 paper, one-inch margins, pages consecutively numbered. This differs from Army SBIR instructions, which allow 10-point, so do not reuse an Army-formatted volume without adjusting.

Proposals should be direct, concise, and informative. Applicants are discouraged from including promotional and non-programmatic items, and if included, that material counts toward the page limit. Marketing material will not be evaluated.

Technical volume limit for this topic is 35 pages or slides, and pages in excess will not be considered by the Government in evaluations. Preferred format is PDF, graphics must be distinguishable in black and white, and all submissions must be virus-checked.

Volume 6 Fraud, Waste, and Abuse training must be completed before submission, and DSIP will not permit submission until it is complete and certified. The DAF recommends completing submission early because site traffic is heavy before close and causes system lag. The DAF will not be responsible for proposals not completely submitted before the deadline due to system inaccessibility unless advised by DoW, and will not accept submission outside DSIP.

Volume 1, Cover Sheet

Completed per DSIP instructions. The technical abstract should include a brief description of program objectives, a description of the effort, anticipated benefits, commercial applications of the proposed research, and a list of keywords and terms. The abstract of each successful proposal goes to the Office of the Secretary of War for publication and must not contain proprietary or classified information. If selected for funding, the technical abstract and discussion of anticipated benefits will be publicly released.

If your proposal is substantially the same as one submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, you must indicate that on the cover sheet. If the prior support section does not apply, certify on the cover sheet, "No prior, current, or pending support for proposed work."

Volume 2, Technical Volume

Required items in the order provided: table of contents immediately after the cover sheet; glossary of acronyms and abbreviations; milestone identification with a program schedule showing all key milestones; identification and significance of the problem or opportunity; Phase II technical objectives with the technical approach and methods and an assessment of potential commercial application for each objective; work plan; deliverables; related work; commercialization potential; relationship with future R/R&D efforts; key personnel; facilities and equipment; consultants and subcontractors; and prior, current, or pending support of similar proposals or awards.

The work plan is a separate and distinct part of the package, divided from the technical proposal by a page break and beginning on a new page. It must summarize technical methodology and task description in broad enough detail to provide contractual flexibility, and must not contain proprietary information, because if the proposal is selected the work plan is incorporated into the resulting contract by reference. The recommended format is 1.0 Objective, 2.0 Scope, 3.0 Background, and 4.0 Task and Technical Requirements. Section 2.0 should concisely describe the work including technology area, goals, and major milestones, with task development and deliverables as the key elements, consistent with section 4.0. Section 3.0 should identify applicable specifications, standards, and other documents, constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective. Section 4.0 requires detailed individual task descriptions in orderly progression with sufficient detail to establish overall program requirements and goals, segregated into major tasks in separately numbered paragraphs, each delineated by subtask. Every task to be accomplished must appear in definite, realistic, clearly stated terms. Use "shall" for binding provisions, "should" or "may" for a declaration or purpose, and "will" where no contractor requirement is involved.

Deliverables must clearly describe the specific sample or prototype hardware and software to be delivered, plus data deliverables, schedules, and quantities, with awareness of the possible unique item identification requirement under DFARS 252.211-7003 for hardware. If hardware or software will be developed but not delivered, explain why. Rights in technical data including software developed under a SBIR contract generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights. The Final Report's first page is a single-page project summary identifying purpose, briefly describing the effort accomplished, and listing potential result applications, which may be published by DoW and therefore must contain no proprietary or classified information. Status reports are due quarterly at a minimum. The Air Force may require additional reporting including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis where hardware is developed and delivered, and updates to commercialization results.

Related work must describe significant directly related activities including previous programs by the principal investigator, proposing firm, consultants, or others, how they interface with the proposed project, and planned coordination with outside sources, plus any applicant-identified subject matter experts regardless of affiliation with comments on the applicant's knowledge of the state of the art. Describe similar but not directly related previous work with a short description, the client including an individual to contact and phone number, and the date of completion.

Commercialization potential requires a commercialization plan addressing the first planned product to incorporate the technology, the probable customers and estimated market size, how much money is needed to bring the technology to market and how it will be raised, whether the firm has necessary marketing expertise and how it will compensate if not, and the probable competitors and the anticipated price or quality advantage. Commercial potential is evidenced by private sector or non-SBIR governmental funding sources demonstrating commitment to Phase II efforts and results, Phase III follow-on commitments for the research subject, and other indicators including the firm's commercialization strategy. If awarded, the awardee must periodically update commercialization results via SBA. The Commercialization Plan and the Company Commercialization Report are distinct documents.

Key personnel must identify all key personnel with information directly related to education, experience, and citizenship, and include a technical resume for the principal investigator with publications. The principal investigator's primary employment must be with the small business at the time of award and during the entire period of performance, where primary employment means more than one-half of the PI's time is spent in the small business's employ, precluding full-time employment with another entity. Only one principal investigator or project manager may be designated per proposal.

Facilities and equipment must describe instrumentation and physical facilities necessary and available, justify equipment to be purchased with detail in the cost proposal, and state whether proposed performance locations meet federal, state, and local environmental laws and regulations for airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors: private companies, consultants, or universities may be involved, all should be described in detail and included in the cost proposal, and signed copies of all consultant or subcontractor letters of intent must be attached, briefly stating the contribution or expertise provided, with statements of work, detailed cost proposals, and information on unique qualifications. Subcontract copies and supporting documents do not count against the page limit. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support: while it is permissible with proper notification to submit identical proposals or proposals containing a significant amount of essentially equivalent work under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort, and any potential for that must be disclosed before award. Provide the federal agency or DoW component names and addresses, submission or award dates, proposal titles, PI names and titles, solicitation titles, numbers and dates, contract numbers if awarded, and applicable topics for each.

Volume 3, Cost Volume

Covered above.

Volume 4, Company Commercialization Report

Required in DSIP. Note the DAF states that information contained in the CCR will not be considered during proposal evaluations, which differs from Army SBIR practice where it is considered. Complete it for compliance, but do not treat it as a scoring opportunity.

Volume 5, Supporting Documents

May be required if applicable: DD Form 2345 for export-controlled topics; Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the DoW SBIR FY26 CSO; and Technical Data Rights Assertions if asserting data rights restrictions.

Required of all submissions: feasibility documentation, as described above, including IP rights assertions where applicable.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material, which will not be evaluated.

Volume 6, Fraud, Waste, and Abuse Training

Complete once per year, before submission.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Complete the webform in Volume 7 of the DSIP submission. The webform will not be accepted as a PDF supporting document in Volume 5, and previous versions of the form must not be uploaded to Volume 5.

How Your Proposal Will Be Evaluated

The rubric for this topic is different from the others in this release

DP027 has its own evaluation structure. Factor A and Factor B are of equal importance and are of more importance than Factor C, with Factor C being less important than Factors A and B. All evaluation criteria other than cost or price, when combined, are significantly more important than cost or price.

Criteria A, Defense Need. The Defense Need being fulfilled and the ability of the proposal to impact that Defense Need. This is assessed through the appropriateness, relevance, and specificity of an identified Defense Need; the adequacy of the proposed effort and its relationship to fulfilling the identified Defense Need; the level of defense mission impact and urgency of the Defense Need; and the breadth of applicability of the solution.

The Air Force adds a specific hint here that appears nowhere else in this document: while not required, signed letters of support from other Government personnel may be indicators of the appropriateness, relevance, and specificity of an identified Defense Need.

Read that carefully. On a topic where Defense Need is co-equal with Technical Approach as the most important factor, the Air Force has told you that a signed letter of support from a Government stakeholder is evidence it values. If you have a relationship with a base defense force support squadron, a security forces unit, AFLCMC/ES, or a JIATF-401 participant, a letter is worth pursuing during the open period.

Criteria B, Technical Approach. The clarity of the problem statement, technical approach, soundness, technical merit, and innovation of the proposed technical approach, its differentiation from current customer alternatives, and the proposed principal investigator's, project manager's, supporting staff's, and consultants' qualifications to execute the proposed approach.

The phrase "its differentiation from current customer alternatives" is doing real work in a crowded counter-UAS market. You will be read against fielded and competing systems. Name them and explain why your approach is different, especially on the non-emitting detection problem and on the cost target.

Criteria C, Commercialization. The potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

General evaluation process

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel. Confidential proposal and evaluation information is protected to the greatest extent possible. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

Selections are based on a determination of overall technical value plus evaluation of the cost volume, for selection of the proposals most advantageous to the Government. Where technical evaluations are essentially equal in merit, cost or price will be considered. Multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none.

Foreign risk evaluation

The DAF will evaluate all small business concerns submitting under this release on whether they present a security risk, using the due diligence process under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947, federal law enforcement, and other counterintelligence capabilities.

The risk-based assessment covers cybersecurity practices, patent analysis, employee analysis, foreign ownership including financial ties and obligations covering surety, equity, and debt obligations of the concern and its employees to a foreign country, person, or entity, foreign affiliations of a covered individual, owner, or other key personnel with an entity in a foreign country of concern, investment relationships with an individual or entity in a foreign country of concern, technology licensing agreements or joint ventures including joint venture like agreements with an individual or entity in a foreign country of concern, and business relationships between a covered individual, owner, or key personnel and an individual or entity in a foreign country of concern. The DAF also uses open-source analysis and analytical tools for nondisclosures of information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examines relationships to entities or individuals on the lists in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If security risks are assessed, the DAF may create a mitigation plan or decide not to select the proposal based on a totality of the review.

Awards must be denied under 15 U.S.C. 638(g)(16) or 638(o)(20) if the concern has an owner or covered individual party to a malign foreign talent recruitment program; a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; an owner or covered individual with a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or a security risk connecting the concern or its affiliates to an entity or individual on the UFLPA Entity List, the Non-SDN Chinese Military-Industrial Complex Companies List, the Section 889 Prohibition List, the Section 1260H Chinese Military Companies list, the Military End User List, the Entity List, the FCC List of Equipment and Services, or the Withhold Release Orders and Findings List. Awards are also denied where a security risk has a primary source that is classified or where the DAF determines a security risk warrants denial.

Applicants must disclose under penalty of perjury the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7, and must provide a written statement of any substantial changes to the foreign disclosure form to the awarding agency within 30 days while on a project for the DAF.

For a sensor hardware topic, the supply chain implications here are direct. Camera modules, RF front ends, and edge compute boards frequently trace to suppliers on one or more of the named lists. Audit your bill of materials against those lists before you propose, not after selection.

Ownership, support contractors, status, and protests

Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

Proposals may be handled for administrative purposes only by support contractors, which may include APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. Only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporation working under contract to provide technical support to Air Force Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by non-disclosure agreements, and concerns about any of them go to the DAF SBIR/STTR Contracting Officer.

The principal investigator and Corporate Official on the cover sheet are notified by email regarding selection or non-selection, with a separate notification for each proposal submitted. Automated feedback is provided for proposals designated Not Selected, and additional feedback may be provided at the sole discretion of the DAF. Proposals are received and evaluated by different organizations handled by topic, each on its own schedule, so notification timeframes vary.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for status before that time. Protests after award should be submitted, as prescribed in FAR 33.106(b) and FAR 52.233-3, to the Air Force SBIR/STTR Contracting Officer and to the individual procuring contracting officer listed on your firm's selection notification. Final reports go to the awarding DAF organization per contract instructions, not directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. Decide which single architecture you are submitting, because the open topic rule allows only one proposal per company. Assemble the feasibility package: test data showing detection and tracking of non-RF-emitting Group 1 to 3 UAS at low altitude with track and node location output. Audit your bill of materials against the foreign entity lists. Build the production cost model that gets you under $100,000 at full rate. Begin pursuing signed Government letters of support, since the rubric names them as an indicator on the co-equal top factor. Complete Volume 6 training, verify SAM and DSIP alignment, and send clarifying questions to the DAF SBIR/STTR One Help Desk, which explicitly encourages early inquiries.

September 23 through October 3. Draft Volume 2 in the required order. Write a requirements traceability section that walks each numeric threshold, 1 to 300 and 500 meters, 100 meter node range, 10 kilometer aggregate coverage, sub-$100,000 production cost, IP65, 95 percent humidity, minus 32 to 55 degrees Celsius, anti-tamper, ATO or IATO, Medusa C2 and API control, and states your position on each. Build the milestone schedule early since the TABA task list must track to it.

October 4 through October 12. Build the cost volume by element and fiscal year. Collect signed letters of intent, statements of work, and detailed cost proposals from every consultant and subcontractor. Check your work-performance percentages and the one-half subcontract cost cap. Write the detailed TABA request into Volume 5 if requesting TABA.

October 13 through October 16. Assemble Volume 5, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 35 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, black and white legible graphics, virus-checked PDF, no marketing material, no proprietary content in the abstract or work plan.

October 17 through October 19. Submit and certify in DSIP. Remember that with an open topic, the most recent certified submission is the one evaluated and any earlier one is marked nonresponsive, so certify the version you actually want reviewed.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-DP027?

‍ ‍

DAF26BX06-DP027 is a Department of the Air Force SBIR Direct to Phase II open topic titled "OPEN, Proliferated Low-Altitude Detection for C-sUAS," released under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. It seeks low-cost networked sensors that detect, track, and identify small, low-altitude, terrain-masked, and RF-silent Group 1 through 3 unmanned aircraft for permanent base defense.

‍ ‍

How much funding is available under DAF26BX06-DP027?

‍ ‍

Up to $2,000,000 for a period of performance up to 24 months. Proposals exceeding either limit will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition to that ceiling.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm the time on the live DSIP posting.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

How many proposals can my company submit to this topic?

‍ ‍

One. Because this is an open topic, a small business concern may only submit one proposal. If more than one is received from the same concern, only the most recent proposal certified and submitted before the deadline is evaluated, and all prior proposals from that concern for the same open topic are marked nonresponsive.

‍ ‍

What are the detection performance requirements?

‍ ‍

The system must detect targets from 1 meter up to 300 meters as the threshold and 500 meters as the objective off the ground. Individual sensor nodes must detect targets at a horizontal range of at least 100 meters. The nodes must integrate to create at least 10 kilometers of combined linear boundary coverage. Targets are Group 1 through 3 UAS, including non-RF-emitting drones, and the system must distinguish a drone from something that is not a drone.

‍ ‍

What is the cost target for the system?

‍ ‍

The final system must cost less than $100,000 at full-rate production. This is a technical design requirement, separate from the $2,000,000 development award ceiling. Address unit cost, node count, and the production cost path explicitly in your proposal.

‍ ‍

Do size, weight, and power limits apply?

‍ ‍

No. Solutions are strictly for permanent base defense applications, so strict size and weight limitations do not apply and systems can rely on direct or off-grid permanent power. This is a deliberate design freedom, so do not compress your architecture to hit SWaP targets this topic does not impose.

‍ ‍

What environmental and hardening requirements apply in Phase II?

‍ ‍

The hardware must be ruggedized for real-world environmental conditions, demonstrating ingress protection of at least IP65, operability in ambient relative humidity up to 95 percent non-condensing, and temperature tolerances from minus 32 to 55 degrees Celsius. The system must include anti-tamper features for critical components and be capable of receiving an ATO or IATO.

‍ ‍

Does the system have to integrate with a specific command and control system?

‍ ‍

Yes. The system must be able to integrate into the Medusa C2 system or other Air Force directed C2. It must also feature remote node control and be fully controllable via external API commands, and must fuse data from all sensors at a node into a single track providing at least the target's heading plus the absolute location of the detecting node.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This is a Direct to Phase 2 topic and Phase I proposals will be rejected.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

You must have accomplished a Phase I type effort outside the SBIR program and have developed and validated a working prototype tested in a simulated or non-operational relevant environment. Specifically, you must demonstrate your system is capable of detecting and tracking non-RF emitting Group 1 through 3 UAS at low altitudes while outputting basic track and sensor node location data.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work, and the feasibility effort must have been substantially performed by the applicant or the principal investigator.

‍ ‍

How is this topic evaluated?

‍ ‍

Under three factors. Criteria A, Defense Need, and Criteria B, Technical Approach, are of equal importance and both more important than Criteria C, Commercialization. All criteria other than cost or price, combined, are significantly more important than cost or price. Note this rubric differs from the other four topics in this release, which use a descending order of importance structure.

‍ ‍

Do letters of support help my proposal?

‍ ‍

The Air Force says that while not required, signed letters of support from other Government personnel may be indicators of the appropriateness, relevance, and specificity of an identified Defense Need. Since Defense Need is a co-equal top factor on this topic, pursuing a signed letter from a relevant Government stakeholder is a high-value use of the open period.

‍ ‍

How long can my technical volume be?

‍ ‍

35 pages or slides. Pages in excess will not be considered during evaluations. Type must be no smaller than 11-point on 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Cost proposal attachments and subcontract copies do not count toward the limit.

‍ ‍

Is this topic export controlled?

‍ ‍

The topic does not carry a topic-level ITAR and EAR restriction notice, unlike three other topics in this release. However, all applicants proposing to use foreign nationals must disclose that information regardless of whether the topic is subject to ITAR, and the general export control provisions apply to all projects with military or dual-use applications developing beyond fundamental research. Counter-UAS sensing raises export control questions readily, so form your own view early.

‍ ‍

How much of the work must my company perform?

‍ ‍

The instructions state two thresholds. The Consultants and Subcontractors section requires at least 50 percent of the R/R&D be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. The Performance of Work Requirements section states at least one-third of the Phase II research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility leases, and other subcontract or purchase agreements together may not exceed one-half of the total contract price without written Contracting Officer approval. Performing at least half in house satisfies every reading. Deviation requests must be made twice, prior to submission during the open period and again with the initial proposal.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 is required, but the DAF states information contained in the CCR will not be considered during proposal evaluations.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Up to $50,000 per Phase II award, in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal, and splittable as $25,000 on a first SBIR Phase II and $25,000 on a sequential one. The detailed request must be in Volume 5 with provider name, point of contact, unique qualifications, tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. Requests that only specify a value in Volume 3 will not be considered.

‍ ‍

Who owns the data and software I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years from contract award, after which the Government has Government purpose rights to the SBIR data.

‍ ‍

Where does this technology transition after Phase II?

‍ ‍

Phase III is transition to AFLCMC/ES and the JIATF-401 counter-UAS marketplace for base defense. Named commercial dual-use applications are airport security, critical infrastructure protection, and border patrol.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates all proposals evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The principal investigator and Corporate Official on the cover sheet are notified by email.

‍ ‍

Who do I contact with questions?

‍ ‍

The DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages early requests because late ones constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Solve the non-emitting detection problem explicitly, or do not bid. The entire premise of this topic is the drone that gives you nothing to listen for. If your detection stack depends materially on RF signature, your feasibility documentation will not clear the stated bar, which specifically requires demonstrated detection and tracking of non-RF emitting targets.

‍ ‍

Build the proposal around a requirements traceability matrix written as prose. There are roughly a dozen hard numbers and specifications in this topic. Walk each one and state your position: meet, exceed, or path to meet with the risk named. Evaluators on a specification-heavy topic reward the proposal that makes verification easy.

‍ ‍

Engineer to the cost target from the start. Under $100,000 at full-rate production for a system covering 10 kilometers of linear boundary is the hardest constraint here, and it interacts with everything. It rules out expensive per-node sensors and pushes toward modalities and compute that scale cheaply. Show the production cost model, not a prototype cost.

‍ ‍

Exploit the SWaP relief. Permanent base defense with permanent power is a rare gift in this market. Larger apertures, heavier sensors, more onboard compute, and mains or off-grid permanent power are all available to you. A proposal that reads like a tactical system is leaving performance on the table.

‍ ‍

Chase a Government letter of support during the open period. The Air Force told you it counts on the co-equal top factor. Security forces, base defense operations, AFLCMC/ES, and JIATF-401 participants are the relevant voices.

‍ ‍

Differentiate against named alternatives. Criteria B explicitly asks about differentiation from current customer alternatives. Counter-UAS is a crowded field with a lot of fielded and demonstrated systems. Name what is out there, be fair about it, and be specific about where you are different.

‍ ‍

Address the ATO path as a work plan task, not an assertion. Capability to receive an ATO or IATO is a Phase II requirement. Put the accreditation activity in the milestone schedule with the documentation artifacts it produces, and if you need help, note that cybersecurity assistance is an eligible TABA activity.

‍ ‍

Audit your supply chain before you propose. The foreign risk denial criteria name eight specific lists. Sensor and edge compute bills of materials commonly touch suppliers on them. Finding that out during a due diligence review after selection is a bad way to lose an award.

‍ ‍

Pick one architecture. The one-proposal-per-open-topic rule means internal debates get settled before submission, not by submitting both and letting the Government choose.

DAF SBIR DAF26BX06-DV026: Ground and Air Launched Drone Swarms Create a Self-Protecting Perimeter Using Autonomous AI

Quick Answer

DAF26BX06-DV026 is a Department of the Air Force SBIR Direct to Phase II topic under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. The Air Force wants to take autonomous drone swarm technology that already works in the commercial world, adapt it to launch from high-altitude mobility aircraft such as the C-130 and KC-135, and prove it can establish an autonomous monitoring and defense perimeter on the ground. Awards are up to $2,000,000 for a period of performance up to 24 months, with a 35 page technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026, submitted only through the Defense SBIR/STTR Innovation Portal.

This is a Direct to Phase II topic, which means no Phase I awards will be made and you cannot bootstrap your way in. You must already have a working swarm system deployed in demanding real-world environments, and you must be able to document that with deployment records, autonomous coordination metrics, and sensor integration data. The Air Force says so directly: traditional Phase I feasibility studies investigating the basic principles of swarm networking or autonomous flight are considered redundant. Your baseline technology needs to sit at Technology Readiness Level 5 or higher at project start, and the target at the end of Phase II is TRL 7.

Topic At a Glance

Topic number: DAF26BX06-DV026

Title: Ground and Air Launched Drone Swarms Create a Self-Protecting Perimeter Using Autonomous AI

Solicitation: Department of the Air Force 2026 SBIR Commercial Solutions Opening (CSO), Release 6, Direct to Phase II

Program type: Direct to Phase II (D2P2), no Phase I awards for this topic

Award maximum value: $2,000,000

Award maximum duration: 24 months

Technical volume page limit: 35 pages or slides

OUSD (R&E) Critical Technology Area: Applied Artificial Intelligence (AAI)

Component Technology Priority Areas: Trusted AI and Autonomy; Integrated Network System-of-Systems; Advanced Computing and Software

Projected CMMC level requirement: Level 2 (Self)

Export control status: Restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774

Starting technology maturity expected: TRL 5 or more

Target technology maturity at Phase II completion: TRL 7

Topic open date: September 23, 2026

Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR CSO

Selection timeline: Evaluations and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027

Submission portal: DSIP at dodsbirsttr.mil

Keywords: autonomous drones, AI-driven swarm, air-launched effects, perimeter defense, secure communications, mobility asset protection, Agile Combat Employment, high-altitude deployment, mobility launch platforms, dual-use, swarm technology, force protection

Note on the deadline time. The DAF instructions direct applicants to the DoW FY26 SBIR CSO for the proposal submission deadline date and time rather than restating it. DoW SBIR CSO deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP topic posting before you plan your final day, and do not assume you have until midnight.

What the Air Force Is Actually Looking For

The operational problem

Mobility Air Forces aircraft are the logistical backbone of the Department of War. They are also high-value, relatively vulnerable assets that operate in contested environments. Separately, forward operating bases need to improve their security posture. The Air Force sees one technology that addresses both: a drone swarm that can be launched from a mobility aircraft, survive the launch, fly autonomously, and then establish a monitoring and defense perimeter on the ground.

The framing matters for how you write. This is not a drone development topic. It is an adaptation and integration topic. The Air Force states plainly that the fundamental scientific and technical merit of coordinating multiple uncrewed aerial systems through artificial intelligence has already been established by the private sector. What has not been done is making that work at operational altitudes, off a mobility airframe, over encrypted military communications, to Air Force operational standards.

The immediate Phase II objective

The stated immediate objective is to propose methods for and demonstrate the deployment and autonomous operation of a multi-agent swarm from high-altitude mobility launch platforms, while simultaneously demonstrating the swarm's dual-use capability to establish an autonomous monitoring and defense perimeter.

A critical research and development component of this phase focuses on proposing and developing secure, encrypted military communication architectures that meet Department of the Air Force operational standards. Read that as a hard requirement rather than a nice-to-have. Replacing your existing commercial data links with secure military communications is named as one of the three specified technical goals.

The three specified technical goals

The topic lists three capability demonstrations that validate the functional requirements:

First, the system should integrate secure, encrypted military communications, replacing readily available data links to ensure secure command and control that aligns with Department of the Air Force standards.

Second, the swarm should demonstrate the capability to safely deploy from mobility platforms at operational altitudes.

Third, the artificial intelligence software should be adapted to seamlessly transition from aerial deployment into a coordinated flight pattern and autonomously execute a perimeter defense monitoring route.

What is deliberately out of scope

This is unusual and worth reading twice. The Air Force says the approach deliberately avoids prescribing specific end-state payloads, so that flexible, innovative integration of various electronic or advanced sensing effects can happen in subsequent operational phases based on evolving warfighter requirements.

In other words, do not build your proposal around a specific kill chain, jammer, or exotic sensor package. The Air Force wants the foundational architecture proven: high-altitude deployment, secure networking, and autonomous baseline behavior. A proposal that spends its pages on a novel payload is answering a question the Air Force did not ask.

Proposed methods named in the topic

The topic names two proposed method areas: upgrading readily available communication links to integrate secure military protocols, and developing the autonomous behaviors necessary to seamlessly transition from aerial deployment to ground-based perimeter defense.

Operating parameters that the Air Force wants demonstrated include secure communication integration and deployment capabilities under operational conditions, deployments at operational altitudes that simulate operational Mobility Air Forces scenarios, and validation of the swarm's ability to autonomously monitor and defend a designated perimeter using onboard visual and thermal sensors.

The desired R&D outcome

A military-adapted prototype capable of demonstrating dual-use capabilities in an operational environment at TRL 7. The named use cases are organic intelligence, surveillance, and reconnaissance plus self-protection for Mobility Air Forces operating in contested airspace, and providing forward operating locations with an instantly deployable, autonomous perimeter monitoring system.

The Feasibility Requirement, Which Is Where Most Proposals Will Fail

Direct to Phase II inverts the usual SBIR sequence. Instead of proposing to establish feasibility, you must prove you already did, outside the SBIR program. The Air Force will not review a proposal that fails this test, and it applies the test before technical merit is considered.

The two absolute rules

Rule one: the feasibility work must have been substantially performed by the applicant or the principal investigator. Work someone else did does not qualify.

Rule two: feasibility documentation cannot be based upon, or logically extend from, any prior or ongoing federally funded SBIR or STTR work. This authority exists specifically for companies that matured technology outside the SBIR pipeline. If your swarm capability came out of a previous SBIR or STTR award, you are not eligible to use it as your feasibility basis here.

The DAF states it will not consider the proposal if the applicant fails to demonstrate technical merit and feasibility have been established, or if the feasibility documentation does not support substantial performance by the applicant or the principal investigator. Note that feasibility documentation can be included as part of Volume 5.

What this specific topic accepts as proof

The topic is more concrete than most about what feasibility looks like, which is a gift. Use their categories as your section headings.

Readily available deployment records. Verifiable data or reports detailing active use of the proposed swarm software and hardware in relevant environments. The examples given are testing or use alongside state or federal fire agencies and municipal police departments. This documentation should indicate the system has progressed from controlled laboratory testing to validation in relevant environments.

Autonomous coordination metrics. Technical reports or system logs demonstrating the software's capability to autonomously control a multi-agent swarm without continuous, manual piloting of individual nodes. Named examples include data on mesh network stability, dynamic task allocation among drones, and collision avoidance algorithms operating in chaotic environments such as airspace obscured by smoke or complex urban terrain.

Sensor integration and tracking data. Documentation showing integration of visual and thermal (EO/IR) payloads, and the software's ability to autonomously use those sensors to detect, track, and relay data on designated targets or points of interest.

The Air Force says that providing this documentation demonstrates the baseline technology sits at a minimum TRL of 5 or 6, establishing that the foundational feasibility traditionally explored in Phase I has already been achieved through iterative development.

The practical read

The ideal applicant for this topic has flown swarms for wildland firefighting or law enforcement, has logs and after-action data from those deployments, and has EO/IR integration already working. If you have that, you are in a strong position and the writing job is largely documentation. If you do not, no amount of proposal quality will fix it, and your effort is better spent elsewhere.

Funding Allowance and Cost Structure

Award ceiling

Up to $2,000,000 across up to 24 months. The topic index carries an unambiguous warning: proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.

One nuance the DAF adds that is worth understanding. In the evaluation section, the DAF states that any per-award or per-topic funding caps are budgetary estimates only, and more or less funding may become available. It also states that multiple procurements are planned and anticipated, each proposal is a separate procurement evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic. Do not calibrate your proposal against an imagined competitor.

Contract type and fee

Generally firm-fixed-price contracts are appropriate for Phase II awards. In accordance with the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee. This differs from how some applicants approach cost-type work, so build fee in.

Technical and Business Assistance

The DAF will provide up to $50,000 per Phase II award for TABA, in addition to the per-topic award total, identified in the Volume 3 Cost Proposal. Applicants may elect to use half of the allocation, $25,000, on a first SBIR Phase II award and the other half on a sequential SBIR Phase II award.

TABA funding can only be used for the activities and purposes in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature through online databases. Those activities must serve one of these purposes: making better technical decisions, solving technical problems arising during the project, minimizing technical risks, developing and commercializing new commercial products and processes including IP protections, and screening for potential foreign involvement in technology development or commercialization activities.

The compliance trap is specific and unforgiving. A TABA request creditable to a provider must include the provider name, the provider point of contact with email and phone, an explanation of the provider's unique qualifications, the tasks the provider will perform including purpose and objective, and total provider cost with hours and labor rates. Blended or average rates are acceptable. The task milestone list must track to the milestone payment schedule otherwise provided by the applicant. If instead you are using TABA to hire new staff, augment staff, or direct staff into training, you must provide names and positions, the business need or training to be provided, the number of employees involved, and their qualifications or the detailed need for training, plus total staff or training cost, hours, and labor rates.

Most important: the detailed TABA request must appear in Volume 5 Supporting Documents. TABA requests that only specify a value in the Volume 3 Cost Proposal will not be considered.

Cost volume requirements

The DAF wants a detailed cost proposal broken out by individual cost element and by contractor fiscal year, in sufficient detail to determine the basis for estimates and the purpose, necessity, and reasonableness of each. Cost proposal attachments do not count toward page limits.

Direct labor: identify key personnel by name where possible, and labor category otherwise, with direct labor hours, labor overhead or fringe, and actual hourly rates for each individual.

Direct cost materials: itemized list of types, quantities, prices and purpose. For planned computer or software purchases, expect to provide manufacturer, price quotes, proposed use, and support for the need.

Other direct costs: specialized services such as machining or milling, special test and analysis, and temporary use or lease of specialized facilities or equipment, with usage hours, rates, sources, and justification. Leased hardware requires a lease versus purchase rationale.

Special tooling, special test equipment, and material: must be advantageous to the Government in the Contracting Officer's opinion and relate directly to the effort, and should not be items an applicant would ordinarily possess in the normal course of business.

Subcontracts: supported with copies of subcontract agreements that adequately describe the work and cost bases, including a statement of work, assigned personnel, hours and rates, materials, and proposed travel. A letter from a subcontractor agreeing to perform at a fixed price is expressly not sufficient. The prime must accomplish price analysis of proposed subcontractor costs.

Consultants: a separate agreement letter for each stating the service, hours required, and hourly rate, plus a short resume.

Travel: each effort should include at a minimum a kickoff or interim meeting. Justify destinations, trips, travelers, airfare, per diem, lodging, and ground transportation against the Joint Travel Regulation.

Indirect costs: indicate proposed rate bases, identify the specific rates and allocation bases, and provide rates and applications per fiscal year across the anticipated performance period. Do not propose composite rates.

Non-SBIR governmental or private investment is allowed but not required, and will not be a proposal evaluation factor.

A significant procedural point: if no exceptions are taken to an applicant's proposal, the Government may award a contract without exchanges. Your initial proposal should therefore contain your best terms from a cost, price, and technical standpoint. Do not hold anything back for a negotiation that may never happen.

The two work-performance rules, and a tension worth asking about

The DAF instructions contain two statements about how much work you must perform yourself, and they do not obviously agree.

In the Consultants and Subcontractors section, the instructions state that in accordance with the SBA SBIR Policy Directive, a minimum of 50 percent of the R/R&D must be performed by the proposing firm unless otherwise approved in writing by the Contracting Officer.

In the Performance of Work Requirements section, the instructions state that for Phase II, a minimum of one-third of the research or analytical effort must be performed by the awardee, measured by both direct and indirect costs, not including profit.

Separately, the instructions cap the proposed total of all consultant fees, facility leases or usage fees, and other subcontract or purchase agreements at one-half of the total contract price unless approved in writing by the Contracting Officer.

The conservative course is to plan on performing at least half the R/R&D in house and keeping all outside costs under half the contract price, which satisfies every reading. If your teaming structure cannot meet that, note the deviation process: requests for Performance of Work deviations must be made twice, first prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission opens. Given the ambiguity, this is a good question for the DAF SBIR/STTR One Help Desk early in the open period.

Where the work must be performed

All R/R&D must be performed in the United States by the small business and its team members. Based on rare and unique circumstances, the DAF may approve a particular portion of the work to be performed or obtained outside the United States, and the awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking that approval must request it with the initial proposal submission.

Export Control, Which Is Not Optional on This Topic

The technology in this topic is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. That has direct staffing consequences.

Offerors must disclose any proposed use of foreign nationals, their countries of origin, the type of visa or work permit held, and the statement of work tasks intended for accomplishment by those individuals. The topic warns that foreign nationals proposed to perform on this topic may be restricted due to the technical data under U.S. export control laws.

The instructions define a foreign national as any person who is not a citizen or national of the United States, not a lawful permanent resident, and not a protected individual as defined by 8 U.S.C. 1324b. All applicants proposing to use foreign nationals must follow the FY26 SBIR CSO and disclose regardless of whether the topic is subject to ITAR.

Where the topic area is subject to export control, foreign national individuals who are permitted to participate are limited to work in the public domain. Further, tasks assigned must not be capable of assimilation into an understanding of the project's overall objectives, which the instructions note prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer.

For projects with military or dual-use applications developing beyond fundamental research, the contractor must comply with all U.S. export control laws, is responsible for obtaining appropriate licenses or approvals including for deemed exports of hardware, technical data, and software, must obtain export licenses before using foreign persons including where work is performed on-site at a Government installation, is responsible for regulatory record keeping associated with licenses and exemptions, and must ensure these provisions apply to its subcontractors.

If you are asserting export-controlled status, a certified DD Form 2345 Militarily Critical Technical Data Agreement, or evidence of application submission, belongs in Volume 5. DD Form 2345 approval will be required if the proposal is selected for award.

Proposal Structure: The Seven Volumes

Formatting rules

Type no smaller than 11-point on standard 8.5 by 11 paper, one-inch margins, pages consecutively numbered. Note this differs from Army SBIR instructions, which permit 10-point, so do not reuse an Army-formatted document without checking.

Proposals should be direct, concise, and informative. Applicants are discouraged from including promotional and non-programmatic items, and if included, such material counts toward the page limit. Marketing material will not be evaluated and should not be included.

The technical volume limit for this topic is 35 pages or slides. Pages in excess of that count will not be considered by the Government in evaluations. Preferred submission format is PDF, and graphics must be distinguishable in black and white. Virus-check all submissions.

Volume 6 Fraud, Waste, and Abuse training must be completed before proposal submission. DSIP will not allow submission until the training is complete and certified. The DAF recommends completing submission early, since site traffic is heavy prior to solicitation close and causes system lag. The DAF will not be responsible for proposals not completely submitted prior to the deadline due to system inaccessibility unless advised by DoW, and will not accept alternative means of submission outside DSIP.

Volume 1, Cover Sheet

Completed per DSIP instructions. The technical abstract should include a brief description of program objectives, a description of the effort, anticipated benefits, and commercial applications of the proposed research, plus a list of keywords and terms. The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication, so it must not contain proprietary or classified information. If selected for funding, the technical abstract and discussion of anticipated benefits will be publicly released.

Volume 2, Technical Volume

Include the following items in the order provided.

Table of contents, located immediately after the cover sheet.

Glossary of acronyms and abbreviations used in the proposal.

Milestone identification: a program schedule with all key milestones identified.

Identification and significance of the problem or opportunity: briefly reference the specific technical problem or opportunity to be pursued.

Phase II technical objectives: detail the specific objectives of the Phase II work and describe the technical approach and methods to be used in meeting them, including an assessment of potential commercial application for each objective.

Work plan: a separate and distinct part of the proposal package, divided from the technical proposal by a page break, beginning on a new page. It must contain a summary description of the technical methodology and task description in broad enough detail to provide contractual flexibility. Do not include proprietary information, because if the proposal is selected the work plan will be incorporated into the resulting contract by reference. The recommended format is 1.0 Objective, a brief overview of the specialty area explaining purpose and expected outcome; 2.0 Scope, a concise description of the work including technology area, goals, and major milestones, with task development and deliverables as the key elements, consistent with section 4.0; 3.0 Background, identifying applicable specifications, standards, and other documents, constraints to understanding requirements, relationships to previous, current, or future operations, and techniques previously determined ineffective; and 4.0 Task/Technical Requirements, detailed individual task descriptions developed in orderly progression with sufficient detail to establish overall program requirements and goals, segregated into major tasks in separately numbered paragraphs. Each numbered major task should delineate work by subtask. The work plan must contain every task to be accomplished in definite, realistic, and clearly stated terms. Use "shall" for binding provisions, "should" or "may" for a declaration or purpose, and "will" when no contractor requirement is involved.

Deliverables: clearly describe the specific sample or prototype hardware and software to be delivered, plus data deliverables, schedules, and quantities. Be aware of the possible unique item identification requirement under DFARS 252.211-7003 for hardware. If hardware or software will be developed but not delivered, provide an explanation. At minimum, all Phase II contracts require Scientific and Technical Reports. Rights in technical data including software developed under a SBIR contract generally remain with the contractor, and the Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years commencing at contract award, after which the Government has Government purpose rights to the SBIR data. The Final Report's first page is a single-page project summary identifying the work's purpose, briefly describing the effort accomplished, and listing potential result applications; that summary may be published by DoW and must contain no proprietary or classified information. Status reports are due quarterly at a minimum. The Air Force may require additional reporting including software documentation and users' manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis when the project results in partial or total development and delivery of hardware, and updates to commercialization results.

Related work: describe significant activities directly related to the proposed effort, including previous programs conducted by the principal investigator, proposing firm, consultants, or others, and their application to the proposed project. Describe how these activities interface with the proposed project and discuss planned coordination with outside sources. List any applicant-identified subject matter experts regardless of affiliation, with comments regarding the applicant's knowledge of the state of the art in the specific approach proposed. Describe previous work not directly related but similar, giving a short description, the client for whom the work was performed including an individual to be contacted and phone number, and the date of completion.

Commercialization potential: the DoW requires a commercialization plan with the Phase II proposal, specifically addressing what the first planned product to incorporate the proposed technology is, who the probable customers are and the estimated market size, how much money is needed to bring the technology to market and how it will be raised, whether the firm has the necessary marketing expertise and if not how it will compensate, and who the probable competitors are and what price or quality advantage is anticipated. The plan should briefly describe commercialization potential for the project's anticipated results and plans to exploit it. Commercial potential is evidenced by the existence of private sector or non-SBIR governmental funding sources demonstrating commitment to Phase II efforts and results, the existence of Phase III follow-on commitments for the research subject, and other indicators of commercial technology potential including the firm's commercialization strategy. If awarded, the awardee must periodically update commercialization results via SBA, at completion of the effort and when submitting a new SBIR/STTR proposal to DoW; firms not submitting a new proposal will be asked for annual updates after completion. Note that the Commercialization Plan and the Company Commercialization Report are distinct documents.

Relationship with future R/R&D efforts: state the anticipated results of the proposed approach, specifically addressing plans for Phase III if any, and discuss the significance of the D2P2 effort in providing a basis for the Phase III effort if planned.

Key personnel: identify all key personnel with information directly related to education, experience, and citizenship. A technical resume for the principal investigator including publications must be included. Concise resumes for subcontractors and consultants are useful. Identify all non-U.S. citizens expected to be involved as direct employees, subcontractors, or consultants, and for those individuals provide countries of origin, type of visa or work permit held, and the tasks they are anticipated to perform. The principal investigator's primary employment must be with the small business at the time of award and during the entire period of performance, where primary employment means more than one-half of the PI's time is spent in the small business's employ, which precludes full-time employment with another entity. Only one principal investigator or project manager can be designated per proposal.

Facilities and equipment: describe instrumentation and physical facilities necessary and available to carry out the effort. Justify equipment to be purchased, with detail in the cost proposal. State whether proposed performance locations meet environmental laws and regulations of federal, state, and local governments for airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

Consultants and subcontractors: private companies, consultants, or universities may be involved and all should be described in detail and included in the cost proposal. Signed copies of all consultant or subcontractor letters of intent must be attached, briefly stating the contribution or expertise being provided. Include statements of work and detailed cost proposals, and information regarding unique qualifications. Subcontract copies and supporting documents do not count against the page limit. Identify any subcontractor or consultant foreign citizens.

Prior, current, or pending support of similar proposals or awards: while it is permissible with proper notification to submit identical proposals or proposals containing a significant amount of essentially equivalent work for consideration under numerous federal program solicitations, it is unlawful to enter into contracts or grants requiring essentially equivalent effort. Any potential for that situation must be disclosed before award. If this proposal is substantially the same as another submitted previously, currently, or in the process of being funded by another federal agency, DoW component, or the DAF, indicate so on the cover sheet and provide the agency names and addresses, submission or award dates, proposal titles, PI names and titles, solicitation titles and numbers and dates, contract numbers if awarded, and the applicable topics for each proposal or award. If the section does not apply, state so in the proposal and certify on the cover sheet, "No prior, current, or pending support for proposed work."

Volume 3, Cost Volume

Covered above under funding. Cost proposal information will be treated as proprietary.

Volume 4, Company Commercialization Report

Completion of the CCR in DSIP is required. Note a meaningful difference from Army SBIR practice: information contained in the CCR will not be considered by the DAF during proposal evaluations. It is a compliance item here, not a scoring input.

Volume 5, Supporting Documents

May be required if applicable: DD Form 2345 for export-controlled topics, which applies to this topic; Verification of Eligibility of Small Business Joint Ventures, which is Attachment 3 to the DoW SBIR FY26 CSO; and Technical Data Rights Assertions if asserting data rights restrictions.

Required of all proposal submissions: feasibility documentation. D2P2 proposals require a comprehensive, detailed effort description and should demonstrate sufficient technical progress or problem-solving results to warrant more extensive RDT&E. Developing technologies with commercial and military potential is described as extremely important, and the DAF is particularly seeking proposals emphasizing dual-use applications and commercialization. The applicant must provide information enabling the agency to make the 15 U.S.C. 638(cc) determination of scientific and technical feasibility and merit. Feasibility efforts detailed must have been substantially performed by the applicant or the PI. If technology in the feasibility documentation is subject to intellectual property rights, the applicant must provide IP rights assertions, and must provide a short summary for each item asserted with less than unlimited rights describing the restriction's nature and the intellectual property intended for use in the proposed research.

If appropriate, include a reference or works cited list as the last page. Do not include marketing material.

Volume 6, Fraud, Waste, and Abuse Training

Material is in the Volume 6 section of the DSIP proposal submission module and must be thoroughly reviewed once per year to proceed with submission. Complete this before you need it.

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

Small business concerns must complete the webform in Volume 7 of the DSIP proposal submission. The webform version will not be accepted as a PDF supporting document in Volume 5, and previous versions of the form must not be uploaded to Volume 5.

How Your Proposal Will Be Evaluated

The process

D2P2 proposals are evaluated on a competitive basis by subject matter expert scientists, engineers, or other technical personnel. Confidential proposal and evaluation information will be protected to the greatest extent possible. Proposals will be disqualified and not evaluated if the Phase I equivalency documentation does not establish the proposed technical approach's feasibility and technical merit.

Selections are based on a determination of the overall technical value of each proposal and an evaluation of the cost volume, for selection of the proposals most advantageous to the Government. Where technical evaluations are essentially equal in merit, cost or price will be considered in determining successful applicants. All evaluation criteria other than cost or price, when combined, are significantly more important than cost or price.

The criteria for this topic

DAF26BX06-DV026 is evaluated under the criteria set that applies to DV026, DV511, DV512, and DV513, in descending order of importance.

Criteria A, most important: the soundness, technical merit, and innovation of the proposed approach and its incremental progress toward topic or subtopic solution, and the qualifications of the proposed principal and key investigators, supporting staff, and consultants. This includes whether the proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements, and are consistent with the unique methods of performance and materials described in the technical proposal.

Criteria B, second: the degree of mission impact and the urgency of the identified need, the specificity of the defense requirement addressed, and the adequacy of the proposed effort in fulfilling the research topic or subtopic solution.

Criteria C, third: the potential for commercial application in the Government or private sector and the benefits expected to accrue from that commercialization.

Two things follow. First, cost realism is inside Criteria A, the most heavily weighted factor, not a separate cost evaluation. A technically strong proposal with a cost volume that does not match the described methods will be marked down on the top criterion. Second, mission impact and urgency sit above commercialization here, which is the reverse of the Army rubric weighting. Your Criteria B argument should be specific: which Mobility Air Forces problem, whose problem it is, and why now.

Foreign risk evaluation

The DAF will evaluate all small business concerns submitting under this release on whether the concern presents a security risk, using the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947, federal law enforcement, and other counterintelligence capabilities.

The risk-based assessment covers cybersecurity practices, patent analysis, employee analysis, foreign ownership of the concern including financial ties and obligations covering surety, equity, and debt obligations of the concern and its employees to a foreign country, person, or entity, foreign affiliations of a covered individual, owner, or other key personnel with an entity in a foreign country of concern, investment relationships with an individual or entity in a foreign country of concern, technology licensing agreements or joint ventures including joint venture like agreements with an individual or entity in a foreign country of concern, and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.

The DAF will also assess proposals using open-source analysis and analytical tools for nondisclosures of information set forth in 15 U.S.C. 638(g)(13) or 15 U.S.C. 638(o)(17), and examine any relationship of the concern to any entity or individual on the lists in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).

If the DAF assesses that a concern has security risks, it may either create a plan to mitigate them or decide not to select the proposal based on a totality of the review.

Award denial is mandatory under 15 U.S.C. 638(g)(16) or 638(o)(20) if the DAF determines the concern has an owner or covered individual who is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual with a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the concern, including any affiliates, to an entity or individual on the UFLPA Entity List, the Non-SDN Chinese Military-Industrial Complex Companies List, the Section 889 Prohibition List, the Section 1260H list of Chinese Military Companies, the Military End User List, the Entity List, the FCC List of Equipment and Services, or the Withhold Release Orders and Findings List. The DAF also will not award if the concern has a security risk with a primary source that is classified, or a security risk the DAF determines warrants denial.

Applicants must disclose under penalty of perjury the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. A written statement with any substantial changes to the foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.

If an award is denied on these grounds, the DAF will as appropriate and in a manner that does not compromise security provide notification advising the small business of the determination, the basis for it, and a statement that denial does not prohibit eligibility for an award in a subsequent cycle.

Ownership and support contractors

Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

Proposals may be handled for administrative purposes only by support contractors, which may include APEX, Peerless Technologies, Engineering Services Network, HPC-COM, Mile Two, REI Systems, MacB (an Alion company), Montech, Oasis, Astrion/Oasis, and Infinite Management Solutions. Only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporation working under contract to provide technical support to Air Force Life Cycle Management Center and Space Force may evaluate proposals. All support contractors are bound by non-disclosure agreements. Concerns about any of these contractors go to the DAF SBIR/STTR Contracting Officer.

Status, feedback, and protests

The principal investigator and the Corporate Official indicated on the cover sheet will be notified by email regarding selection or non-selection. Small businesses receive a notification for each proposal submitted, so read each carefully and note the proposal number and topic number referenced.

Automated feedback will be provided for proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic, and each organization operates within its own schedule for evaluation and selection, so notification timeframes will vary. If contacted regarding one proposal submission, it is not necessary to request information about additional submissions.

The DAF anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the DAF for proposal status before that time. Protests after award should be submitted, as prescribed in FAR 33.106(b) and FAR 52.233-3, to the Air Force SBIR/STTR Contracting Officer and to the individual procuring contracting officer listed on your firm's selection notification.

Final reports go to the awarding DAF organization per contract instructions. Companies do not submit final reports directly to the Defense Technical Information Center.

Timeline and What to Do When

The dates

Topic opens: September 23, 2026

Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR CSO, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.

Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027

Period of performance: up to 24 months from award

A working backward plan

Before September 23. This window is for assembling feasibility evidence, not writing. Pull your deployment records from fire agency or law enforcement work into a usable form. Extract the autonomous coordination logs: mesh stability, dynamic task allocation, collision avoidance in degraded visual environments. Package your EO/IR integration and tracking data. Confirm which of your people are U.S. persons under the definition in the instructions and identify any export control constraints on your team. Start the DD Form 2345 process if you do not already hold one, since approval will be required at award. Complete Volume 6 training. Verify SAM registration and DSIP account alignment. Contact the DAF SBIR/STTR One Help Desk with clarifying questions, and note the DAF explicitly encourages early questions because late ones constrain its ability to respond.

September 23 through October 3. Draft Volume 2 in the required order. The work plan is a separate document with a page break, written in contract language with shall, should, may, and will used deliberately, and with no proprietary content since it becomes part of the contract by reference. Build the milestone schedule first, because the TABA task milestone list must track to your milestone payment schedule.

October 4 through October 12. Build the cost volume by element and by fiscal year. Collect signed letters of intent from every consultant and subcontractor, with statements of work and detailed cost proposals. Check your work-performance percentages against the 50 percent R/R&D and one-half subcontract cost thresholds. Write the detailed TABA request into Volume 5 if you are requesting TABA.

October 13 through October 16. Assemble Volume 5, complete the Volume 7 webform, confirm the CCR in Volume 4, and run a compliance pass: 35 page limit, 11-point minimum type, one-inch margins, consecutive page numbers, graphics legible in black and white, PDF virus-checked, no marketing material, no proprietary information in the abstract or the work plan.

October 17 through October 19. Submit in DSIP and certify. The DAF explicitly warns about system lag from heavy traffic near close and disclaims responsibility for incomplete submissions caused by inaccessibility.

October 20 through October 21. Buffer only.

Frequently Asked Questions

‍ ‍

What is DAF SBIR topic DAF26BX06-DV026?

‍ ‍

DAF26BX06-DV026 is a Department of the Air Force SBIR Direct to Phase II topic titled "Ground and Air Launched Drone Swarms Create a Self-Protecting Perimeter Using Autonomous AI," released under the DAF 2026 SBIR Commercial Solutions Opening, Release 6. It seeks to adapt mature commercial autonomous drone swarm technology for launch from high-altitude mobility aircraft and for autonomous ground perimeter defense.

‍ ‍

How much funding is available under DAF26BX06-DV026?

‍ ‍

Up to $2,000,000 for a period of performance up to 24 months. Proposals exceeding either limit will not be considered for evaluation or award. Up to $50,000 in Technical and Business Assistance may be requested in addition to that ceiling.

‍ ‍

When is the proposal deadline?

‍ ‍

The topic closes October 21, 2026. The DAF instructions point to the DoW FY26 SBIR CSO for the exact submission time, which is ordinarily 12:00 p.m. Eastern on the close date. Confirm the time on the live DSIP topic posting rather than assuming an end-of-day deadline.

‍ ‍

When does this topic open?

‍ ‍

September 23, 2026, giving a 29 day submission window.

‍ ‍

Can I submit a Phase I proposal for this topic?

‍ ‍

No. This is a Direct to Phase II topic and no Phase I awards are anticipated. You must document that a prior Phase I type effort established feasibility, and that effort cannot have been performed under a prior or ongoing federally funded SBIR or STTR award.

‍ ‍

What feasibility documentation does this topic require?

‍ ‍

Three categories are named. Readily available deployment records showing verifiable active use of your swarm software and hardware in relevant environments, such as work alongside state or federal fire agencies or municipal police departments. Autonomous coordination metrics from technical reports or system logs showing autonomous control of a multi-agent swarm without continuous manual piloting, including mesh network stability, dynamic task allocation, and collision avoidance in chaotic environments. Sensor integration and tracking data showing EO/IR payload integration and autonomous detection, tracking, and data relay.

‍ ‍

What technology readiness level do I need to start?

‍ ‍

The Air Force expects the core readily available technology to sit at TRL 5 or more at project start, and states that the feasibility documentation demonstrates a minimum TRL of 5 or 6. The target at the end of the Phase II effort is TRL 7, a military-adapted system prototype demonstrated under operational conditions.

‍ ‍

Can I use a prior SBIR award as my feasibility basis?

‍ ‍

No. Feasibility documentation cannot be based upon or logically extend from any prior or ongoing federally funded SBIR or STTR work. The Direct to Phase II authority exists for companies that matured technology outside the SBIR pipeline.

‍ ‍

Does the Air Force want me to propose a specific payload?

‍ ‍

No. The topic deliberately avoids prescribing specific end-state payloads so that electronic or advanced sensing effects can be integrated in later operational phases based on evolving requirements. Focus your proposal on high-altitude deployment, secure military communications integration, and autonomous baseline behavior.

‍ ‍

Is this topic export controlled?

‍ ‍

Yes. The technology is restricted under ITAR 22 CFR Parts 120-130 and EAR 15 CFR Parts 730-774. You must disclose any proposed foreign nationals with their countries of origin, visa or work permit type, and assigned statement of work tasks, and the topic warns those individuals may be restricted from performing. A certified DD Form 2345, or evidence of application, belongs in Volume 5, and DD Form 2345 approval will be required if selected for award.

‍ ‍

Can foreign nationals work on this project?

‍ ‍

Only in limited ways. Where the topic area is subject to export control, permitted foreign national participants are limited to work in the public domain, and assigned tasks must not be capable of assimilation into an understanding of the project's overall objectives. The instructions note this prevents foreign persons from acting in key positions such as Principal Investigator or Senior Engineer.

‍ ‍

How long can my technical volume be?

‍ ‍

35 pages or slides for this topic. Pages in excess will not be considered during evaluations. Type must be no smaller than 11-point on 8.5 by 11 paper with one-inch margins and consecutively numbered pages. Cost proposal attachments and subcontract copies do not count toward the limit.

‍ ‍

How is my proposal evaluated?

‍ ‍

Under three criteria in descending order of importance. Criteria A covers soundness, technical merit, and innovation of the approach, incremental progress toward a solution, the qualifications of key personnel, and whether the proposed cost elements are realistic and consistent with the technical proposal. Criteria B covers degree of mission impact, urgency of the identified need, specificity of the defense requirement, and adequacy of the effort. Criteria C covers commercial application potential. All criteria other than cost or price, combined, are significantly more important than cost or price.

‍ ‍

Is cost evaluated separately?

‍ ‍

Cost realism sits inside Criteria A, the most important factor, so a cost volume inconsistent with your described methods hurts your top-weighted score. Separately, where technical evaluations are essentially equal in merit, cost or price will be considered in determining successful applicants.

‍ ‍

How much of the work must my company perform?

‍ ‍

The instructions state two thresholds. The Consultants and Subcontractors section requires a minimum of 50 percent of the R/R&D be performed by the proposing firm unless the Contracting Officer approves otherwise in writing. The Performance of Work Requirements section states a minimum of one-third of the research or analytical effort for Phase II must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility leases, and other subcontract or purchase agreements together may not exceed one-half of the total contract price without written Contracting Officer approval. Planning to perform at least half the R/R&D in house satisfies every reading; if you cannot, ask the DAF SBIR/STTR One Help Desk early and follow the deviation request process.

‍ ‍

How do I request a performance of work deviation?

‍ ‍

Requests must be made twice, first prior to submission during the topic open period, and again as part of the initial proposal submission. The DAF will not consider these requests before proposal submission.

‍ ‍

Does the Company Commercialization Report affect my score?

‍ ‍

No. Completing the CCR as Volume 4 is required, but the DAF states that information contained in the CCR will not be considered during proposal evaluations. This differs from Army SBIR practice, where the CCR is considered.

‍ ‍

What is TABA and how do I request it?

‍ ‍

Technical and Business Assistance is up to $50,000 per Phase II award, in addition to the per-topic ceiling, identified in the Volume 3 Cost Proposal. You may split it, using $25,000 on a first SBIR Phase II and $25,000 on a sequential SBIR Phase II. The detailed request must be in Volume 5, including provider name, point of contact, unique qualifications, tasks with purpose and objective, and total cost with hours and labor rates, and the task milestone list must track to your milestone payment schedule. TABA requests that only specify a value in Volume 3 will not be considered.

‍ ‍

Who owns the data and software I develop?

‍ ‍

Rights in technical data including software developed under a SBIR contract generally remain with the contractor. The Government obtains SBIR/STTR data rights in all data developed or generated under the contract for 20 years from contract award, after which the Government has Government purpose rights to the SBIR data.

‍ ‍

Do Phase II contracts include profit?

‍ ‍

Yes. Generally firm-fixed-price contracts are appropriate for Phase II awards, and in accordance with the SBA SBIR/STTR Policy Directive, Phase II contracts must include profit or fee.

‍ ‍

Will I be able to negotiate after submitting?

‍ ‍

Possibly not. If no exceptions are taken to your proposal, the Government may award a contract without exchanges. Your initial proposal should contain your best terms from a cost, price, and technical standpoint.

‍ ‍

Are venture-backed companies eligible?

‍ ‍

Yes. Small business concerns owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.

‍ ‍

When will I hear about selection?

‍ ‍

The DAF anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The principal investigator and Corporate Official on the cover sheet are notified by email, with a separate notification for each proposal submitted.

‍ ‍

Will I get feedback if not selected?

‍ ‍

Automated feedback is provided for proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.

‍ ‍

What is the commercial market for this technology?

‍ ‍

The topic names several. Interagency partners including NOAA seek high-altitude deployment capability to safely launch swarms into hurricanes and atmospheric rivers for real-time weather data collection. Commercially, the ruggedized secure swarm capability can be expanded for advanced disaster response, large-scale search and rescue, and commercial aviation monitoring. The Air National Guard application for Domestic Operations, including rapid wide-area sensor coverage to locate survivors during natural disasters and persistent autonomous border surveillance, is also named.

‍ ‍

Who do I contact with questions?

‍ ‍

For general information about the DAF SBIR/STTR program and proposal preparation instructions, contact the DAF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us. The DAF encourages applicants to request clarifying information as early as possible, since late requests constrain its ability to respond. For DSIP electronic submission system issues, contact dodsbirsupport@reisystems.com. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. If your company mailing address, email addresses, or points of contact change after submission, notify the One Help Desk with the subject line "FY26 SBIR CSO Address Change."

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Qualify yourself honestly on feasibility first. This topic has a narrow ideal applicant: a company with a fielded autonomous swarm, real deployment history in a demanding civil mission, EO/IR already integrated, and no SBIR lineage on that technology. If any of those four is missing, read the other four topics in this release before you commit a proposal team.

‍ ‍

Lead with the deployment record, not the vision. The single strongest asset you can put in front of these evaluators is verifiable operational data from fire or law enforcement work. Quantify it: number of sorties, swarm sizes, environmental conditions, autonomy percentage, intervention rates. Vague claims of maturity read as absence of evidence.

‍ ‍

Treat secure military communications as the core R&D. Of the three specified technical goals, this is the one most likely to be genuinely hard and most likely to separate serious proposals. Name the approach, the encryption and waveform path, the standards you are targeting, and the risks. If you have a partner for this, get their letter of intent and statement of work in early.

‍ ‍

Do not propose a payload. The Air Force said explicitly that it is avoiding end-state payload prescription. Respect that boundary and spend the pages on architecture, launch survivability, and autonomous transition behavior.

‍ ‍

Make the launch problem concrete. High-altitude release from a C-130 or KC-135 involves surviving the launch environment, achieving controlled autonomous flight after release, and doing it at operational altitudes. Address the airworthiness and integration path, and note that the topic mentions Phase III involves finalizing airworthiness certifications with the Air Force Life Cycle Management Center Mobility Directorate.

‍ ‍

Use the transition evidence the topic hands you. The topic states transition planning is actively underway, that the project team is engaging AMC Futures and the Chief Scientist to champion an Initial Capabilities Document based on Phase II capability demonstration data, and that ARCWERX is assisting in identifying follow-on acquisition vehicles. That is a named transition pathway. Reference it and show how your Phase II deliverables feed an Initial Capabilities Document.

‍ ‍

Write Criteria B as a mission argument, not a technology argument. Mission impact and urgency outrank commercialization in this rubric. Contested logistics, Agile Combat Employment, and base defense are the operative concepts. The topic cites AMC Commander statements on contested logistics and adaptive capabilities. Ground your urgency claim in that language.

‍ ‍

Get the cost volume consistent with the technical volume. Cost realism is inside the top-weighted criterion. If your work plan says you will run flight test campaigns at operational altitudes, your travel, test range, and airframe integration costs need to show up and be justified.

‍ ‍

Build the dual-use case around the named analogs. NOAA hurricane sampling, disaster response, large-scale search and rescue, commercial aviation monitoring, and Air National Guard Domestic Operations are all in the topic text. Commercialization is Criteria C, so it is not where you win, but a thin answer here is an unnecessary loss.

Army STTR ARM26TX06-NV003: Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions

Quick Answer

ARM26TX06-NV003 is a U.S. Army STTR Phase I topic released under the Department of the Army 2026 STTR Program Commercial Solutions Opening (CSO), Release 6. The Army is asking small businesses, working in formal partnership with a research institution, to prove out a "decision-as-a-program" capability: an agentic AI system built on a formal decision schema that turns messy engineering and acquisition questions into structured, auditable, signer-ready Decision Packages. Phase I awards are up to $300,000 for a period of performance of 1 to 6 months. The topic opens September 23, 2026 and closes October 21, 2026, with proposals certified in the Defense SBIR/STTR Innovation Portal (DSIP) no later than 12:00 p.m. ET on the close date.

The single most important thing to understand about this topic is that it is the STTR version of an Army topic that also exists as an SBIR topic under number ARM26BX06-NV012. The technical scope, the funding ceiling, the period of performance, and the evaluation rubric are the same. What differs is the program: STTR requires you to partner with a research institution and to divide the work with that partner according to statutory minimums. If you do not have a university or federal laboratory partner lined up, the SBIR twin is the door you want. If you do have one, and especially if the principal investigator sits on the academic side, this is the better fit.

Topic At a Glance

‍ ‍

Topic number: ARM26TX06-NV003

‍ ‍

Title: Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions

‍ ‍

Program: STTR, Small Business Technology Transfer

‍ ‍

Solicitation: Department of the Army 2026 STTR Program, Commercial Solutions Opening (CSO), Component-Specific Proposal Instructions, Release 6

‍ ‍

Agency: U.S. Army, under the Department of War (DoW) STTR program

‍ ‍

Phase offered: Phase I (Feasibility) only

‍ ‍

Award ceiling: Up to $300,000

‍ ‍

Period of performance: 1 to 6 months

‍ ‍

Contract type: FAR-based, firm-fixed-price, with payments tied to measurable milestones or deliverables

‍ ‍

Research institution partner: Required, as a condition of the STTR program

‍ ‍

OUSD (R&E) Critical Technology Area: Applied Artificial Intelligence (AAI)

‍ ‍

Component Technology Priority Areas: Trusted AI and Autonomy; Information Systems

‍ ‍

Projected CMMC level requirement: Level 1

‍ ‍

Submission portal: DSIP at dodsbirsttr.mil

‍ ‍

Topic open date: September 23, 2026

‍ ‍

Proposal deadline: October 21, 2026 at 12:00 p.m. ET

‍ ‍

DSIP Topic Q&A closes: October 7, 2026, two weeks prior to the close date

‍ ‍

Selection notification: Within 90 days of the topic close date, meaning on or about January 19, 2027

‍ ‍

SBIR companion topic: ARM26BX06-NV012, same title and scope, no research institution partner required

‍ ‍

Keywords: Agentic AI, Digital Engineering, schema-driven Decision Management, acquisition decisions, AI LLM

‍ ‍

A note on the topic number. The Release 6 topic index lists this topic as ARM26TX06-NV003, while the header on the topic description page carries a typographical variant. Use the number shown on the live DSIP topic posting, and confirm it before you submit, since the topic number goes in your technical volume header on every page.

‍ ‍

What Makes This an STTR and Not an SBIR

‍ ‍

This is the part worth getting right before you invest any writing time.

‍ ‍

STTR is a distinct program from SBIR, authorized under the same statute but with different structural requirements. The defining requirement is the research institution partnership. An STTR award is a collaboration between a small business concern and a research institution, typically a university, a federally funded research and development center, or a qualifying nonprofit research organization. The partnership is not optional and it is not a subcontract of convenience. It is the point of the program.

‍ ‍

Two consequences follow, and both come from the STTR statute and the SBA SBIR/STTR Policy Directive rather than from the Army component instructions themselves. First, the work must be divided between the small business and the research institution according to statutory minimums, with the small business performing at least 40 percent of the work and the research institution performing at least 30 percent, measured as a percentage of the total effort. Second, the principal investigator may be primarily employed by either the small business or the research institution. That second point is spelled out in the Army instructions, which state that the primary employment of the Principal Investigator or Project Manager must be with the small business concern, or with the research institution in the case of STTR, at the time of award and during the conduct of the project.

‍ ‍

Because the exact terms, definitions, and the required written allocation-of-rights agreement live in the DoW 2026 STTR Program CSO and the SBA Policy Directive rather than in the Army component-specific instructions, read those documents alongside this topic. The Army instructions are explicit that they supplement, and in some cases supersede, the DoW CSO, but they do not restate the STTR partnership mechanics.

‍ ‍

One eligibility difference is worth flagging carefully. The Army SBIR component instructions for Release 6 include a section addressing small businesses that are majority-owned in part by multiple venture capital operating companies, hedge funds, or private equity funds, confirming those firms are eligible to submit and receive SBIR awards provided they complete a joint venture eligibility certification. The Army STTR component instructions for the same release do not contain that section. The majority venture-capital ownership authority is an SBIR-specific provision of the statute. If your company is majority-owned by multiple VC, hedge fund, or private equity firms, verify your STTR eligibility against 13 CFR 121.702 and the SBA SBIR/STTR Policy Directive before you commit to this topic, because your answer under STTR may differ from your answer under SBIR. Note that the Verification of Eligibility of Small Business Joint Ventures document still appears on the STTR conditional Volume 5 list.

‍ ‍

If you are choosing between the two topics, the practical decision tree is short. No research institution partner means go SBIR. A strong university or laboratory partner whose people and instruments you actually need, or a principal investigator whose primary employment is academic, means go STTR. A partner you would be adding only to qualify for STTR means go SBIR, because a thin partnership shows up in the Technical Team and Technical Approach scoring.

‍ ‍

What the Army Is Actually Looking For

‍ ‍

The technical content of this topic is identical to its SBIR twin. Everything below comes from the topic description in the Release 6 STTR instructions.

‍ ‍

The core objective

‍ ‍

The Army wants proof of a decision-as-a-program capability. In plain terms, that means taking a complex engineering or acquisition question, one that today gets answered through slide decks, spreadsheets, email threads, and tribal knowledge, and turning it into a structured, machine-readable, auditable decision artifact that a decision authority can actually sign. The stated goal is to do this faster and with higher confidence than the status quo.

‍ ‍

The emphasis is on proof by demonstration, not a full product build. Phase I is not the place to promise a shipping platform. It is the place to show that the schema plus the agentic layer works on real decision problems, both point-in-time trade studies and long-horizon acquisition decision programs, with traceability, robustness, and human control intact.

‍ ‍

The three technical objectives

‍ ‍

Objective one: a unified representation. The Army wants a single decision model that supports two very different shapes of work. The first is the single-episode trade study, a bounded comparison of options against criteria. The second is the multi-episode "decision program," a long-running decision with refresh cycles as evidence and assumptions change over time. The topic specifically calls for context engineering for the ground vehicle domain, implemented through knowledge graphs and semantic layers that capture domain-specific relationships, constraints, and requirements. The system is expected to integrate data from Digital Engineering (DE) tools such as SysML 2.0 and UML, pulling from digital threads and digital twins to provide a unified view of system models across the product lifecycle.

‍ ‍

Objective two: agentic capabilities with human control. The AI layer must produce structured artifacts and reproducible outputs. Reproducibility is called out explicitly, which is a strong signal that nondeterministic, unauditable model output alone will not satisfy this topic. The agentic system is expected to perform structured elicitation into the formal model, generate decision workflow plans, and execute evaluation runs with clear "what flips the decision" logic. It is also expected to automate validation of technical documents, models, and outputs against standards and requirements, while maintaining predictable behavior consistent with established human-AI interaction guidance.

‍ ‍

Objective three: explicit bias checks, risks, and assumptions. The schema must be extended so that bias checks, risks, and assumptions become first-class, testable objects rather than prose buried in a report. The purpose is decision readiness: the ability to assess whether a decision is actually ready for sign-off before it is signed, and to responsibly refresh it when conditions change. Semantic understanding is expected to keep consistency across digital engineering artifacts and enable traceable decision rationale.

‍ ‍

Phase I desired outcomes

‍ ‍

The topic lists three Phase I outcomes:

‍ ‍

1. A decision schema that makes objectives, options, constraints, assumptions, risks, and bias checks first-class objects.

2. Agentic AI that performs structured elicitation into the formal model, generates decision workflow plans, and executes reproducible evaluation runs with clear "what flips the decision" logic.

3. Two end-to-end demonstrations showing the approach scales from point-in-time trade studies to long-horizon program decisions with refresh cycles as evidence and assumptions change.

‍ ‍

Two demonstrations, not one. That is a concrete, checkable requirement and a common place where proposals lose points by being vague.

‍ ‍

Where this goes in Phase II

‍ ‍

The Army is explicit that the DoW already has multiple contractors building AI and LLM tools for core warfighter purposes, but very little effort has gone toward an AIgentic decision intelligence capability that supports accelerated commercial acquisition or longer lead traditional development. That gap is the reason this topic exists.

‍ ‍

In Phase II, the expectation is that the successful contractor develops a combined AIgentic and AI/LLM decision intelligence workflow capability, exercised on two real cases provided from PAE Maneuver Ground and PAE Fires. The resulting software platform is to be modeled and developed as a commercial open-source platform usable by both the DoW and commercial enterprises for Product Design and Development (PDD) and acquisition.

‍ ‍

The topic names the current COTS baseline directly: DAOSoft, which provides an open capability with an advanced structured decision and trade study capability plus a partially developed AI/LLM decision intelligence workflow. The Army states it is looking for any and all ideas that can extend or replace current acquisition capabilities and is agnostic to all current solutions. It is also agnostic as to which developed AI commercial package fulfills the addition of AIgentics to current AI/LLM for continuous acquisition.

‍ ‍

The Phase II prototype is expected to be immediately useful, with follow-on Phase III contracts anticipated for individual customer installation, described by the Army as similar to current best practice deployment of large ERP systems from SAP and Oracle.

‍ ‍

For an STTR team, the open-source and platform expectations in Phase II deserve an early conversation with your research institution's technology transfer office. Who owns what, what gets published, and what can be released under an open-source license are questions that get much harder to answer after award than before.

‍ ‍

Phase III dual use

‍ ‍

The named commercial analog is the vehicle design process in the automotive industry. The Army notes the workflow can be relatively similar to the vehicle design process for the Army, with some different considerations. For a startup, this is a useful signal: the commercialization argument writes itself around complex-system product development and capital program decision-making outside defense.

‍ ‍

Reference cited in the topic

‍ ‍

The topic cites one reference, an SAE Mobilus paper: "Concept execution AI agentic decision intelligence framework product planning concept development," 2025-01-0455, at saemobilus.sae.org.

‍ ‍

Funding Allowance and What You Can Add On Top

‍ ‍

Base award

‍ ‍

Phase I under this topic is up to $300,000 for 1 to 6 months. Award funding guideline and period of performance limitations are established per topic, and the solicitation is blunt about this: proposals exceeding these limitations will be deemed unresponsive. Do not propose $325,000 and do not propose nine months.

‍ ‍

Remember that this single ceiling covers both partners. The $300,000 is the total award, split between your small business and your research institution according to the STTR work allocation. That constrains scope more than it does under SBIR, because you are funding two organizations with two different indirect rate structures out of the same pool. Build the budget early and check it against the statutory work split before you finalize the technical approach.

‍ ‍

The number of awards depends on funds availability. The Army reserves the right to award none, one, or more than one contract under any topic. Awards are FAR-based, firm-fixed-price, with payments tied to measurable milestones or deliverables agreed to by the Government. Milestone schedules are used to monitor technical progress, mitigate technical and cost risk, and address awardee cash flow needs. The Contracting Officer retains the right to negotiate contract type and price.

‍ ‍

Technical and Business Assistance (TABA)

‍ ‍

TABA is additional money on top of the award ceiling. For Phase I, the Army may provide up to $6,500 per project. For Direct to Phase II projects, up to $50,000. TABA is not guaranteed and depends on the Government's review of the requested services and available TABA budget.

‍ ‍

There are two options and the paperwork differs:

‍ ‍

Option 1, Army-preferred vendor. Up to $6,500 per Phase I project. If you use the Army's preferred provider, the TABA cost does not need to be included in your DSIP Cost Volume (Volume 3). If approved, funding goes directly to the Army's preferred provider. Participation is voluntary and application instructions come after contract award. Commonly requested services include customized market research and strategy, intellectual property support, CMMC compliance, DCAA compliance, and communications and marketing. Intellectual property support is worth a look for an STTR team specifically, given the allocation-of-rights work that comes with a research institution partnership.

‍ ‍

Option 2, firm-selected vendor. You may contract TABA services through one or more TABA providers, or use the funding to hire new or augment staff, or to have staff conduct or participate in training activities consistent with 15 U.S.C. 638(q)(1). If you choose your own provider, the proposed TABA amount must be included in the DSIP Cost Volume (Volume 3) and details of the TABA request must be included in Supporting Documents (Volume 5).

‍ ‍

Critical TABA compliance points:

‍ ‍

TABA funding will be denied if the costs are omitted from the initial proposal submission, or if proposed TABA costs exceed $6,500 per Phase I project.

‍ ‍

TABA costs cannot include any profit or fee for the proposer.

‍ ‍

TABA costs cannot be factored into the calculation of general and administrative expenses (G&A).

‍ ‍

The amount is based on the original contract period of performance and does not apply to period of performance extensions or enhancements.

‍ ‍

The TABA provider cannot be your firm or any affiliated entity, and TABA costs must be directly related to the provider's services, excluding indirect costs, profit, or fees passed through by your company.

‍ ‍

The rationale statement in Volume 5 is limited to two pages and must include the provider name, point of contact with email and phone, an explanation of the provider's suitability and qualifications, an outline of specific tasks, and total provider cost with number of hours and labor rates. A blended or average rate is acceptable.

‍ ‍

Phase II Enhancement

‍ ‍

The Department of the Army may provide a Phase II awardee with up to $500,000 in matching SBIR funding on a dollar-for-dollar basis if the performer obtains a commitment of non-SBIR/STTR funding from a DoW component, another federal agency, or a commercial investor. The enhancement effort must develop, deliver, and integrate a technology or product into a program within a DoW component, federal agency, or the commercial sector. Enhancement requests are subject to approval by the Army SBIR/STTR Program's Source Selection Authority, successful negotiations, and funding availability. Enhancement funding is typically applied to an active Phase II award through a contract modification, with additional scope of work and period of performance commensurate with the total funding received.

‍ ‍

For a startup, this matters at the strategy level: a credible non-dilutive path exists from a $300,000 Phase I to a Phase II with up to $500,000 in matched enhancement, then Phase III installation contracts.

‍ ‍

Timeline and Key Dates

‍ ‍

The dates that matter

‍ ‍

Topic opens for submission: September 23, 2026

‍ ‍

DSIP Topic Q&A closes: October 7, 2026

‍ ‍

Deadline for administrative questions to the Army: October 6, 2026, which is 15 days prior to closing

‍ ‍

Proposal deadline: October 21, 2026 at 12:00 p.m. ET

‍ ‍

Selection or non-selection notification: on or about January 19, 2027, within 90 days of close

‍ ‍

Start of Work Meeting, if awarded: within 30 calendar days after contract award

‍ ‍

Note that the proposal deadline is noon Eastern, not end of day. That is 11:00 a.m. Central, 10:00 a.m. Mountain, and 9:00 a.m. Pacific on October 21. Teams on the West Coast routinely lose proposals to this detail.

‍ ‍

The sequence in detail

‍ ‍

Pre-release period, before September 23, 2026. The topic sits in pre-release on DSIP. During pre-release, topic author names, phone numbers, and email addresses are published with the topic on the DSIP Topics and Topic Q&A page. This is the only window for direct contact with the topic author, and once the topic opens on September 23 that door closes.

‍ ‍

Topic open, September 23, 2026. The topic opens for proposal submission in DSIP.

‍ ‍

DSIP Topic Q&A window, closing October 7, 2026. Topic Q&A opens on the pre-release date and closes two weeks prior to the topic close date. All questions and answers are posted publicly on a non-attribution basis. Answers are generally posted within seven business days and are also emailed directly to the person who asked. Because answers can take seven business days, a question submitted on October 7 may not be answered until roughly October 16, leaving you only a few days to act on it. Ask early.

‍ ‍

Administrative question deadline, October 6, 2026. General questions about Army STTR Program administration and the Army component-specific proposal instructions should be submitted as soon as possible, and no later than 15 days prior to solicitation closing, to usarmy.SBIRSTTR@army.mil.

‍ ‍

Proposal deadline, October 21, 2026 at 12:00 p.m. ET. Complete proposals must be certified and submitted in DSIP by this time. Proposals cannot be submitted after the deadline and will not be accepted or evaluated.

‍ ‍

Selection or non-selection notification, on or about January 19, 2027. Within 90 days of the topic close date, by email to the Corporate Official listed on the proposal cover sheet, sent from the Army SBIR/STTR Program Office mailbox.

‍ ‍

Start of Work Meeting, within 30 calendar days after contract award. Held at your facility unless another location is designated in the contract.

‍ ‍

Periodic reviews. Monthly, bi-monthly, or quarterly review meetings as specified in the contract.

‍ ‍

Final Report of Inventions and Subcontracts. DD Form 882, due within six months after completion of the contracted work.

‍ ‍

Planning note: the Army warns that proposals should be submitted as early as possible to avoid delays caused by high traffic near closing. The Department of the Army is not responsible for missed submissions due to system latency or inaccessibility. A proposal sitting in "In Progress" or "Ready to Certify" status is not submitted, even if every volume has been uploaded before the close date.

‍ ‍

A working backward schedule for an STTR team

‍ ‍

The 29 day window is tighter for STTR than for SBIR, because a second institution has to move with you. University contracting offices do not work on startup timelines.

‍ ‍

Now through September 22. Contact your research institution's sponsored programs office immediately and tell them the deadline. Ask what they need from you and how long their internal review takes, because that answer sets your real deadline, not October 21. Confirm your SAM registration is active and that your DSIP profile matches it. Get every team member a DSIP account. Complete the annual Volume 6 Fraud, Waste and Abuse training. Reach the topic author during pre-release while direct contact is still allowed.

‍ ‍

September 23 through September 30. Settle the work split with your partner on paper, in percentages, and confirm it satisfies the STTR minimums. Get the research institution's budget and indirect rates in writing. Run Army customer discovery interviews. Draft the technical approach and lock down which two demonstrations you will propose.

‍ ‍

October 1 through October 7. Complete a full technical volume draft. Submit any remaining questions through DSIP Topic Q&A before it closes on October 7. Circulate the draft to your research institution partner for their sign-off on anything describing their scope, their people, or their facilities.

‍ ‍

October 8 through October 14. Build the combined Cost Volume with substantiating documentation from both organizations. Assemble every Volume 5 attachment, including the two page Non-Proprietary Work Plan, the foreign citizens list or the statement that none are involved, and Key Personnel with the principal investigator's technical resume. Complete the Volume 7 foreign affiliations web form. If your research institution requires institutional signature on anything, this is the week it has to happen.

‍ ‍

October 15 through October 17. Compliance pass. Verify the seven page limit, 10-point minimum type, one inch margins, page numbering, and headers with company name, topic number, and DSIP proposal number. Confirm the PDF is searchable, unlocked, unencrypted, and virus checked.

‍ ‍

October 18 through October 19. Upload everything to DSIP and execute the corporate official certification. Confirm the status is no longer "In Progress" or "Ready to Certify."

‍ ‍

October 20 through October 21. Buffer only. Do not plan to use these days.

‍ ‍

Eligibility and Registrations You Need Before You Can Submit

‍ ‍

You must be a Small Business Concern (SBC) meeting all eligibility requirements in 13 CFR 121.702 and the SBA SBIR/STTR Policy Directive, and you must have a qualifying research institution partner as required by the STTR program.

‍ ‍

System for Award Management (SAM). You must be registered and active in SAM in accordance with FAR Provision 52.204-7, both when submitting and at time of award. Proposals from firms failing this may be deemed unresponsive. You may only submit using your legal business name or a DBA name as indicated in the SAM registration for the provided Unique Entity Identifier (UEI). A DBA used on an offer must be registered and linked to your current, active SAM registration. Firms that are debarred, suspended, proposed for debarment, or voluntarily excluded are excluded from award, and the Army will not consent to subcontracts with such contractors.

‍ ‍

DSIP registration. DSIP is the official portal. Proposals submitted by any other means will be disregarded. Every individual who will prepare or submit must have an individual DSIP user account. Register as early as possible. Your DSIP account profile must correlate with your SAM registration, including the 5-digit CAGE code, 12-digit UEI, legal business name, DBA name, and physical address. Failure to correlate this information, or to submit required certifications, may significantly delay funding agreement award or become grounds for cancellation of the funding agreement.

‍ ‍

Principal Investigator employment. The primary employment of the Principal Investigator or Project Manager must be with the SBC, or with the Research Institution in the case of STTR, at the time of award and during the conduct of the proposed project. This flexibility is one of the real advantages of the STTR path for teams built around an academic investigator.

‍ ‍

Research institution partnership documents. The written agreement between the small business and the research institution, including the allocation of intellectual property rights, is governed by the DoW 2026 STTR Program CSO and the SBA SBIR/STTR Policy Directive. Confirm what has to be in place at proposal time versus at award, because the answer drives your schedule.

‍ ‍

Proposal Structure: What You Actually Submit

‍ ‍

Army component-specific instructions supplement and in some cases supersede the DoW 2026 STTR Program CSO. Where they conflict, the Army instructions take precedence.

‍ ‍

Volume 1, Proposal Coversheet

‍ ‍

Prepared in DSIP in accordance with the DoW solicitation.

‍ ‍

Volume 2, Technical Volume

‍ ‍

Format requirements, and the solicitation states that submissions failing to conform shall be deemed unresponsive:

‍ ‍

Single Adobe Acrobat PDF, searchable text format, including graphics. PDFs that cannot be opened using Adobe Acrobat products may be rejected. Perform a virus check before uploading. Do not lock, password protect, or encrypt the file. Do not include or embed active graphics such as videos or moving pictures.

‍ ‍

Page limit for Phase I: seven pages, including all key sections. The limit applies to the entire Technical Volume as uploaded to DSIP. At the Government's discretion, pages that clearly do not substantiate or contribute to the technical approach, such as a cover sheet or table of contents, may be excluded from the count. Any appendices or supplemental content that expand upon the required content do count toward the seven pages. You may allocate the pages across sections however you want.

‍ ‍

Layout: number all pages consecutively. No type smaller than 10-point, standard 8.5 by 11 inch paper, one-inch margins including the header. The header on each page, which may sit inside the one-inch margin, should contain the proposing SBC's name, the topic number, and the DSIP assigned proposal number from the cover sheet.

‍ ‍

General: graphics are strongly encouraged throughout. For plots and charts, include title, caption, axes labels, and scale. Avoid jargon and define all technical terms. Use the compress pictures feature to reduce file size.

‍ ‍

Required section order for Phase I:

‍ ‍

1. Introduction

2. Army Benefits

3. Technical Approach

4. Programmatic Potential

5. Commercial Potential

‍ ‍

These sections map one-to-one onto the Phase I evaluation rubric in Appendix A. Your Volume 2 must also be consistent with the Non-Proprietary Work Plan you upload in Volume 5.

‍ ‍

Seven pages is not much room to describe a two-organization project. The research institution's role has to be established economically, inside the Technical Approach and Technical Team narrative, and it has to read as integral rather than bolted on. Detailed resumes belong in Volume 5, not here.

‍ ‍

What each section needs, in the Army's own framing:

‍ ‍

Introduction. A clear, concise description of what your innovation does or will do, and where you are in your evolution. Make clear its intended impact on the Army. Evaluators should "get it" after reading this.

‍ ‍

Army Benefits. Identified Army use cases, the solution's advantages, and the potential level and scale of impact. If you are unsure how an Army end user would benefit, provide an analogous use case so evaluators can connect the dots. Three rubric prompts: Alignment, argue your innovation aligns with this topic's priorities as defined in the solicitation. Solution's Advantages, prove customers will choose you given limited resources and many choices, and account for indirect substitutes as well as direct competitors. Solution's Impact, the Army seeks higher-risk, high-impact solutions through STTR, not engineering changes or incremental improvements.

‍ ‍

Technical Approach. Details and supporting data on how you will solve the problem, key elements of your approach, the technical team, and risks with mitigation plans. Use data to substantiate that your risk mitigation plans are credible, attributed to reliable, credible sources. Rubric prompts: Scientific Feasibility, Enabling Technologies (do the required enabling technologies introduce added risk), Technical Team, Technical Risk and Mitigation Plans, and Data Quality.

‍ ‍

Programmatic Potential. Where your company is today, what will be accomplished under this STTR effort with Army customer discovery, and the risks and mitigations for transitioning beyond STTR funding into a contract with an Army or integration with an Army system. Rubric prompts: Project Milestone Schedule, Army Customer Discovery and Validation (are you "getting out of the building" and do you have formal or informal customer validation), and Army Transition Pathways (what is the next type of deal you aim to make with the Army after this award).

‍ ‍

Commercial Potential. The commercial market the DoW can build upon, your past success, and future potential. Rubric prompts: R&D to Product Revenue (has your team transitioned R&D into products with actual product revenue, which the Army defines as directly selling a solution rather than selling consulting, services, or research activities), Competitive Edge (why will you win, something your team does very well that is difficult to match, such as protected IP, unmatched relevant experience, a novel business model, or network effects), and Other People's Money (the non-DoW commercial market case).

‍ ‍

Volume 3, Cost Volume

‍ ‍

Cost and duration limits are detailed in the topic. Options are not anticipated at this time; if an option is identified in the topic posting, Base and Option costs must be separated and clearly identified. All proposed costs must be accompanied by documentation substantiating how the cost was derived. Failure to include supporting documentation may delay award, since the Contracting Officer will have to request it. Failure or refusal to provide documentation may result in dissolution of the contract action.

‍ ‍

For STTR, the cost volume carries the work split. Your research institution's costs, rates, and effort have to be substantiated the same way yours are, and the resulting allocation has to satisfy the STTR minimums. Ask your partner's sponsored programs office for a formal budget with their federally negotiated rates rather than an estimate.

‍ ‍

Volume 4, Company Commercialization Report

‍ ‍

Required for prior SBIR/STTR awardees. Information in the CCR will be considered during proposal evaluation.

‍ ‍

Volume 5, Supporting Documents

‍ ‍

This is where proposals most often die on compliance. The solicitation states plainly that a completed proposal submission in DSIP does not indicate that the mandatory supporting documents have been uploaded. Failure to upload any mandatory document as a separate attachment will result in the proposal being deemed administratively non-compliant and unresponsive. Unresponsive proposals are un-awardable and may be excluded from technical evaluation entirely.

‍ ‍

Mandatory items, uploaded as separate attachments:

‍ ‍

1. Non-Proprietary Work Plan. Two page limit. A summary based on the Volume 2 technical approach, outlining technical objectives, key milestones, and deliverables. It serves as the basis for performance requirements in the final contract and must be written for a public, technically literate audience with no sensitive or proprietary information.

2. List of Foreign Citizens. Identify any foreign nationals or dual citizens expected to be involved as a direct employee, subcontractor, consultant, or Research Institution. Provide a single PDF with a listing of citizenships, countries of origin, type of visa or work permit, and an explanation of anticipated level of involvement. If no foreign nationals will be involved, substitute a statement to that effect. The Army specifically warns that small businesses often incorrectly assume everyone with dual citizenship or a work permit is automatically permitted to work on SBIR/STTR projects and fail to identify them. Failure to provide this may significantly delay selection or award.

‍ ‍

This item deserves extra attention on an STTR proposal. Research institution personnel are named in the requirement, and university laboratories commonly include graduate students and postdoctoral researchers who are foreign nationals. Ask your partner for a complete roster of everyone who will touch the project, with citizenship and visa status, early enough that it does not become a last-week scramble.

‍ ‍

3. Key Personnel. Identify all key personnel with information on education and experience. A technical resume for the Principal Investigator, including publications if any, must be included. Resumes for other technical staff, subcontractors, and consultants are useful and may also be included. On an STTR, this is where your research institution investigators and their publication records belong.

‍ ‍

If applicable, also submit: SBIR/STTR Funding Agreement Certification; Verification of Eligibility of Small Business Joint Ventures; Assertion of use, release, or disclosure restriction per DFARS 252.227-7017; DD Form 2345 Military Critical Technical Data Agreement for ITAR-subject actions; SBC-selected details of TABA request; and other documentation such as letters of support. The Army may also accept cost/pricing information and other items only as specified in the topic. Anything else submitted will be disregarded, including promotional and non-project material.

‍ ‍

The assertion of use, release, or disclosure restriction is worth real thought on an STTR, since data rights questions get more complicated when a university's prior work and background IP are in the mix. A letter of support from your research institution partner is also an appropriate use of the "other documentation" slot.

‍ ‍

Volume 6, Fraud, Waste and Abuse Training

‍ ‍

Material is in the Volume 6 section of the DSIP proposal submission module and must be thoroughly reviewed once per year to proceed with proposal submission.

‍ ‍

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

‍ ‍

A web form. PDF uploads are no longer accepted. Disclosure does not mean automatic denial, but failure to complete the form completely and accurately may render the proposal administratively non-compliant and unresponsive.

‍ ‍

Per 15 U.S.C. 638(vv), 15 U.S.C. 638(g)(13), and the SBA SBIR/STTR Policy Directive, disclosures must consider subcontractors, subsidiaries, joint ventures, consultants, and their employees across four categories: foreign affiliations, including any subsidiary, parent company, or joint venture based in, funded by, or with a foreign affiliation with any foreign country of concern; contractual or financial obligations with a foreign entity, and the Army notes that a subcontracting agreement is by definition a contractual and financial obligation; related entities, meaning any foreign business entity, offshore entity, or entity outside the United States related to the SBC; and covered individuals, meaning anyone who contributes in a substantive, meaningful way to the scientific development or execution of the project, regardless of title or Key Personnel designation, whether employed by the prime, a subcontractor, a consultant, or a partnering Research Institution.

‍ ‍

That last clause names partnering research institutions explicitly. Your partner's foreign collaborations, foreign funding, and foreign-affiliated personnel are inside the scope of what the Army will assess. Have that conversation with your partner before you fill out the form, not after.

‍ ‍

How Your Proposal Will Be Evaluated

‍ ‍

The process

‍ ‍

Initial screening for responsiveness, timeliness, and SBC eligibility. Responsiveness means failing any material requirement of the solicitation, including compulsory terms and conditions, makes the proposal unresponsive. Timeliness means received on or before the due date and prior to the established set time. Assessment of responsiveness and eligibility may continue during technical evaluation and even after selection.

‍ ‍

National security and foreign risk assessment. The Army conducts a foreign risk evaluation review of every proposal, referencing the 2026 Department of War SBIR/STTR Foreign Risk Evaluation Program Common Decision Matrix dated 08 July 2026. The Army states it relies on statutory authority rather than non-regulatory guidance documents, and that the matrix is illustrative and non-exhaustive. The Army's assessment is not limited to the factors or countries listed. It evaluates the Volume 7 Foreign Disclosure and all areas identified under 15 U.S.C. 638(vv), including cybersecurity practices, patent analysis, employee analysis including subcontractor employee foreign affiliations, foreign ownership, financial ties and obligations, and employee ties to foreign entities. If risks are identified, the Army decides at its sole discretion and case by case whether they can be adequately mitigated. The Army is not required to coordinate with the proposer to develop a mitigation plan and is not obligated to disclose specific findings. Where risks cannot be effectively mitigated, the proposal may be removed from consideration regardless of technical evaluation results.

‍ ‍

Technical evaluation. Proposals passing initial screening receive a technical evaluation against the criteria in Appendix A, reviewed by a cadre of subject matter expert evaluators using the weighted rubric. Proposals are assessed on their own individual merit against the stated criteria, not against each other. Because foreign risk assessment runs in parallel, the Army reserves the right to pause, suspend, or entirely forego technical evaluation, and pausing does not create any right to a mitigation period. Designated support contractors, bound by non-disclosure agreements, may review submissions for evaluation purposes; submitting a response constitutes assent to that.

‍ ‍

Other assessment considerations. Under RFO FAR 25.502, the Government will eliminate any offeror that is unacceptable for reasons other than price, including use of prohibited sources. Proposers and subcontractors are strictly prohibited from using products or services listed in RFO FAR 40.202, including but not limited to TikTok/ByteDance, Kaspersky, and specific unmanned aircraft systems.

‍ ‍

Selection. Notification within 90 days of topic close. Selected proposals are not guaranteed a contract award, and the selection notice is not an authorization to commit or expend funds. After selection, proposals go to a Contracting Officer for further evaluation and negotiation, which may include representations and certifications, certified or other than certified cost data, and other information. Award happens only when a Contracting Officer signs an award document.

‍ ‍

Feedback. The Army will provide feedback to offerors per the SBA SBIR/STTR Policy Directive, with instructions in the selection decision notice. Offerors are entitled to no more than one feedback per proposal. This is not a FAR Part 15 debriefing, and offerors are neither entitled to nor will receive FAR Part 15 debriefs.

‍ ‍

Phase I scoring weights

‍ ‍

The Phase I Evaluation Criteria v4-0 rubric in Appendix A assigns these weights:

‍ ‍

Introduction, 3 percent

‍ ‍

Army Benefits, 15 percent, covering Alignment, Solution's Advantages, and Solution's Impact

‍ ‍

Technical Approach, 35 percent, covering Scientific Feasibility, Enabling Technologies, Technical Team, Technical Risks and Mitigation Plans, and Data Quality

‍ ‍

Programmatic Potential, 20 percent, covering Project Milestone Schedule, Army Customer Discovery and Validation, and Army Transition Pathway

‍ ‍

Commercial Potential, 25 percent, covering R&D to Product Revenue, Competitive Edge, and Other People's Money

‍ ‍

Proposal Quality, 2 percent, covering Quality of Prose and Images, Charts, Graphics

‍ ‍

Each element is scored Unsatisfactory, Marginal, Satisfactory, or Superior. A few of the distinctions worth internalizing, because they tell you exactly what "Superior" looks like:

‍ ‍

Alignment: Superior is "perfectly aligned with this Army topic's priorities," not merely "aligned."

‍ ‍

Solution's Impact: Satisfactory is "significant improvement vs. the state of the art." Superior is "radical improvement."

‍ ‍

Enabling Technologies: Satisfactory "requires proven technologies." Superior "requires Army-fielded technologies." Marginal "requires emerging, cutting edge technology," and Unsatisfactory "requires nonexistent or unavailable technology." This is a real trap for AI teams. Building on exotic, unproven infrastructure scores you down, not up.

‍ ‍

Technical Team: Superior is "technical people are highly qualified AND have significant experience." Note the conjunction. Satisfactory accepts highly qualified or significantly experienced. This is the criterion where a genuine research institution partnership pays for itself, since the combination of academic credentials and applied delivery experience across two organizations is exactly what the top of this scale describes.

‍ ‍

Army Customer Discovery and Validation: Unsatisfactory is "no customer interviews completed, no validation." Marginal is "a handful of customer interviews completed, no validation." Satisfactory is "extensive interviews completed, early validation beginning to inform transition strategy." Superior is "exhaustive interviews completed, validation informs credible transition strategy." You cannot score well here without having actually talked to Army stakeholders before you submit.

‍ ‍

R&D to Product Revenue: Unsatisfactory is "no evidence of creating product revenue from R&D efforts." Superior is "evidence of R&D yielding product revenue sufficient to fuel this company's growth." Note again the Army's definition of product revenue: directly selling a solution to solve a problem, not selling consulting, services, or research activities.

‍ ‍

Other People's Money: Unsatisfactory "fails to present non-DoD sources for future R&D funding." Superior is "diverse and robust non-DoD sources of future R&D funding."

‍ ‍

Taken together, 45 percent of your score sits in Programmatic Potential plus Commercial Potential. For a research-driven STTR team, that is the warning label on this topic. Nearly half the evaluation is not about the science. It is about whether you have done customer discovery with the Army, whether you have a named next deal, whether you have real product revenue history, and whether you have non-defense money in the picture. Academic strength does not compensate for a thin commercialization case, and the rubric is explicit that consulting and research revenue do not count as product revenue.

‍ ‍

Contract Requirements After Award

‍ ‍

Deliverables. Hardware or prototype deliverables per the topic, if applicable, with possible unique item identification requirements under DFARS 252.211-7003. Data deliverables can take the form of test data, computer software, algorithms, design details, progress reports, technical data, financial or management reports, or any information required by contract to be delivered. Data is ordered using DD Form 1423 Contract Data Requirements Lists (CDRLs) located at Section J, Exhibits of the contract. Each CDRL references a Data Item Description viewable through the Acquisition Streamlining and Standardization Information System (ASSIST).

‍ ‍

All Army SBIR/STTR funding agreements include two CDRL requirements: Status Reports under DID number DI-MGMT-80368A, due at a specified time after award and periodically thereafter (monthly, bi-monthly, or quarterly), and a Scientific and Technical Report under DID number DI-MISC-80711A, a final report delivered per the prepared DD Form 1423. The Army end user may require additional deliverables including software documentation and user manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis, or updated commercialization results.

‍ ‍

Note that computer software and algorithms are named as deliverable data types. For a software topic with a university partner, that makes the data rights and allocation-of-rights conversation a contract-shaping issue, not a formality.

‍ ‍

Meetings. A Start of Work Meeting within 30 calendar days of award, held at your facility unless otherwise designated, to establish mutual understanding of contract terms, conditions, line items, technical requirements, and sequence of events. Then periodic review meetings to report status, accomplishments, difficulties, and progress against planned goals and resources expended.

‍ ‍

Invention reporting. Under FAR 52.227-11 and DFARS 252.227-7039, Phase II contracts require an Interim Report of Inventions and Subcontracts on DD Form 882 twelve months from the date of initial contract award. All Phase I and Phase II contracts require a Final Report of Inventions and Subcontracts on DD Form 882 within six months after completion of the contracted work. STTR awardees must report inventions within two months of the inventor's report to the awardee, and may do so through the Edison Invention Reporting System at iedison.gov. With a research institution partner, make sure both organizations know who is responsible for capturing inventor disclosures.

‍ ‍

Controlled Unclassified Information. Successful firms must comply with CUI DoDI 5200.48. Firms must monitor CUI for aggregation and compilation based on the potential to generate classified information, report the potential classification of aggregated or compiled CUI to the ASA(ALT) Security Manager, and submit unclassified DoW information for review and approval for release in accordance with DoDI 5230.09. CUI records must follow approved mandatory disposition authorities. On a university-partnered project, CUI handling and publication review deserve an explicit plan, since the default academic instinct to publish collides with these obligations.

‍ ‍

CMMC. The projected CMMC level requirement for this topic is Level 1. CMMC compliance support is one of the commonly requested TABA services, which is worth knowing if you are not yet compliant.

‍ ‍

Asking Questions the Right Way

‍ ‍

There are two channels and they have different rules.

‍ ‍

Direct contact with topic authors, pre-release only. During pre-release, topic author names, phone numbers, and email addresses are published with the topic on DSIP. You may contact them by phone or email to ask technical questions about specific solicitation topics. Questions must be limited to specific information related to understanding a particular topic's requirements. You may not ask for advice or guidance on solution approach and may not submit additional material to the topic author. If information from an exchange is deemed necessary for proposal preparation, it will be made available to all parties through DSIP Topic Q&A. After pre-release, no further direct contact is allowed unless the author is responding to a question submitted during pre-release.

‍ ‍

DSIP Topic Q&A. Opens on the pre-release date and closes two weeks prior to the topic close date, meaning October 7, 2026. Written questions and answers are posted on a non-attribution basis for public viewing. Answers are generally posted within seven business days and emailed to the inquirer. Questions are limited to technical information focused on understanding the topic's requirements. Requests for advice on solution approach, or administrative questions about SBIR or STTR program eligibility, proposal or cost structure, page count, budget and duration limitations, or the proposal due date, will not receive a response. Administrative questions go to the component-specific contact instead.

‍ ‍

Once the proposal submission closes, no communication of any kind is allowed with the topic author or through Topic Q&A regarding submitted proposals.

‍ ‍

The Army advises monitoring DSIP frequently throughout the solicitation period for updates and amendments to topics and for new Q&A entries.

Frequently Asked Questions

‍ ‍

What is Army STTR topic ARM26TX06-NV003?

‍ ‍

ARM26TX06-NV003 is an Army STTR Phase I topic titled "Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions," released under the Department of the Army 2026 STTR Program Commercial Solutions Opening, Release 6. It seeks a demonstrated decision-as-a-program capability that converts complex engineering and acquisition questions into structured, auditable, signer-ready Decision Packages.

‍ ‍

How much funding is available under ARM26TX06-NV003?

‍ ‍

Phase I awards are up to $300,000 with a period of performance of 1 to 6 months. Up to $6,500 in Technical and Business Assistance funding may be requested in addition to the award ceiling. Proposals exceeding the topic's stated funding and duration limits will be deemed unresponsive. The $300,000 covers the combined effort of the small business and its research institution partner.

‍ ‍

When is the proposal deadline for ARM26TX06-NV003?

‍ ‍

Complete proposals must be certified and submitted in DSIP no later than 12:00 p.m. ET on October 21, 2026. That is noon Eastern, not end of day, which is 11:00 a.m. Central, 10:00 a.m. Mountain, and 9:00 a.m. Pacific. Proposals cannot be submitted after the deadline and will not be accepted or evaluated.

‍ ‍

When does this topic open for proposals?

‍ ‍

The topic opens for proposal submission on September 23, 2026, giving a 29 day submission window that closes October 21, 2026.

‍ ‍

When does the DSIP Topic Q&A window close?

‍ ‍

October 7, 2026, two weeks prior to the topic close date. Since answers are generally posted within seven business days, submit questions well before the cutoff if you need the answer in time to use it.

‍ ‍

What is the difference between this STTR topic and the Army SBIR topic ARM26BX06-NV012?

‍ ‍

The technical scope, funding ceiling, period of performance, and Phase I evaluation rubric are the same. The difference is the program. STTR requires a formal partnership with a research institution and a statutory division of work between the two organizations, and it allows the principal investigator to be primarily employed by either the small business or the research institution. SBIR has no partnership requirement and requires the principal investigator to be primarily employed by the small business.

‍ ‍

Do I need a university partner to apply for ARM26TX06-NV003?

‍ ‍

Yes. The STTR program requires a partnership with a qualifying research institution, which can be a university, a federally funded research and development center, or a qualifying nonprofit research organization. If you do not have a research institution partner, apply to the SBIR companion topic ARM26BX06-NV012 instead.

‍ ‍

What is the required work split between the small business and the research institution?

‍ ‍

Under the STTR program, the small business must perform at least 40 percent of the work and the research institution at least 30 percent, as a percentage of total effort. The governing definitions and requirements are in the DoW 2026 STTR Program CSO and the SBA SBIR/STTR Policy Directive rather than in the Army component-specific instructions, so verify the current terms there.

‍ ‍

Can the principal investigator work at the university rather than my company?

‍ ‍

Yes. The Army instructions state that primary employment of the Principal Investigator or Project Manager must be with the small business concern, or with the Research Institution in the case of STTR, at the time of award and during the conduct of the project. This is one of the meaningful advantages of the STTR path.

‍ ‍

Are venture-backed companies eligible for this STTR topic?

‍ ‍

Verify before you commit. The Army SBIR instructions for Release 6 include a provision confirming that firms majority-owned in part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible for SBIR awards, subject to a joint venture eligibility certification. The Army STTR instructions for the same release do not contain that provision, and the majority venture-capital ownership authority is SBIR-specific under the statute. Check your eligibility against 13 CFR 121.702 and the SBA SBIR/STTR Policy Directive.

‍ ‍

Is Direct to Phase II available for ARM26TX06-NV003?

‍ ‍

No. The Release 6 topic index lists this topic as Phase I (Feasibility). Direct to Phase II proposals may only be submitted where a topic posting explicitly allows them. Phase II proposals may otherwise only be submitted by Phase I awardees, and unsolicited Phase II proposals will be rejected without evaluation.

‍ ‍

How long is the technical volume?

‍ ‍

Seven pages for a Phase I proposal, including all required sections. Appendices and supplemental content count toward the seven pages. Cover sheets and tables of contents may be excluded at the Government's discretion. Minimum 10-point type, 8.5 by 11 inch pages, one-inch margins including the header.

‍ ‍

What are the required sections of the technical volume?

‍ ‍

In this order: Introduction, Army Benefits, Technical Approach, Programmatic Potential, and Commercial Potential. These map directly onto the Phase I evaluation rubric in Appendix A of the Army instructions.

‍ ‍

Where do I submit my proposal?

‍ ‍

Through the Defense SBIR/STTR Innovation Portal (DSIP) at dodsbirsttr.mil. Proposals submitted by any other means will be disregarded. Select Army as your component and ASA(ALT) as your command.

‍ ‍

What registrations do I need before submitting?

‍ ‍

An active SAM registration in accordance with FAR Provision 52.204-7, and individual DSIP user accounts for everyone preparing or submitting the proposal. Your DSIP account profile must match your SAM record, including CAGE code, UEI, legal business name, DBA name, and physical address. Register early, since mismatches can delay or void an award.

‍ ‍

What are the most common ways proposals get disqualified?

‍ ‍

Missing a mandatory Volume 5 attachment, since a completed DSIP submission does not mean supporting documents were uploaded. Failing the technical volume formatting requirements. Exceeding the funding or duration limits. Leaving the proposal in "In Progress" or "Ready to Certify" status instead of certifying it. Incomplete or inaccurate Volume 7 foreign affiliation disclosure. Failing to identify foreign nationals or dual citizens on the project, including research institution personnel.

‍ ‍

Do I have to disclose foreign nationals at my university partner?

‍ ‍

Yes. The List of Foreign Citizens requirement names Research Institutions explicitly, and the Volume 7 covered-individual definition applies to anyone contributing substantively to the project whether employed by the prime, a subcontractor, a consultant, or a partnering research institution. Request a complete roster with citizenship and visa status from your partner early.

‍ ‍

How is the Phase I proposal scored?

‍ ‍

By weighted rubric: Technical Approach 35 percent, Commercial Potential 25 percent, Programmatic Potential 20 percent, Army Benefits 15 percent, Introduction 3 percent, and Proposal Quality 2 percent. Each element is rated Unsatisfactory, Marginal, Satisfactory, or Superior.

‍ ‍

Do I need to talk to Army stakeholders before I submit?

‍ ‍

Effectively yes. Army Customer Discovery and Validation sits inside the 20 percent Programmatic Potential weight, and the rubric scores "no customer interviews completed, no validation" as Unsatisfactory while reserving Satisfactory and Superior for extensive or exhaustive interviews with validation informing a credible transition strategy.

‍ ‍

Can I contact the topic author?

‍ ‍

Only during the pre-release period, meaning before the topic opens on September 23, 2026, when author contact details are published with the topic on DSIP. Questions must be limited to understanding the topic's requirements. You may not ask for advice on your solution approach or send them material. After pre-release, use DSIP Topic Q&A, which closes October 7, 2026.

‍ ‍

When will I hear whether I was selected?

‍ ‍

Within 90 days of the October 21, 2026 close date, so on or about January 19, 2027. Notification goes by email to the Corporate Official listed on your proposal cover sheet. A selection notice is not a contract and is not authorization to commit or expend funds.

‍ ‍

Will I get a debrief if I am not selected?

‍ ‍

You will get feedback, not a debrief. The Army provides feedback per the SBA SBIR/STTR Policy Directive, with instructions in the selection decision notice, and offerors are entitled to no more than one feedback per proposal. Competitive procedures here are governed by the SBIR/STTR Policy Directive, so FAR Part 15 debriefings are not available.

‍ ‍

What kind of contract will I receive?

‍ ‍

A FAR-based, firm-fixed-price contract, with payments tied to measurable milestones or deliverables agreed to with the Government. The Contracting Officer retains the right to negotiate contract type and price.

‍ ‍

What is TABA and how do I get it?

‍ ‍

Technical and Business Assistance is funding provided in addition to the award ceiling, up to $6,500 per Phase I project, for services such as market research, IP support, CMMC compliance, DCAA compliance, and marketing. You can use an Army preferred vendor, in which case the cost stays out of your Cost Volume, or your own provider, in which case the cost must be in Volume 3 and a two-page rationale must be in Volume 5. TABA is denied if the costs are omitted from the initial submission or exceed the cap.

‍ ‍

What happens after Phase II?

‍ ‍

The Army anticipates follow-on Phase III contracts for individual customer installation, comparable to how large ERP deployments from SAP and Oracle are rolled out. Separately, the Army Phase II Enhancement Policy may provide up to $500,000 in matching funding on a dollar-for-dollar basis against committed non-SBIR/STTR funding from a DoW component, another federal agency, or a commercial investor.

‍ ‍

What CMMC level does this topic require?

‍ ‍

The projected requirement is CMMC Level 1. CMMC compliance assistance is one of the frequently requested TABA services if you need help getting there.

‍ ‍

Are there prohibited technologies I need to avoid?

‍ ‍

Yes. Proposers and their subcontractors are strictly prohibited from using products or services listed in RFO FAR 40.202, including but not limited to TikTok/ByteDance, Kaspersky, and specific unmanned aircraft systems. Offerors using prohibited sources will be eliminated.

‍ ‍

Who do I contact with administrative questions?

‍ ‍

Email usarmy.SBIRSTTR@army.mil for questions about Army STTR Program administration and the Army component-specific proposal instructions, no later than 15 days prior to solicitation closing, which is October 6, 2026. For DSIP portal problems, email DoDSBIRSupport@reisystems.com during normal operating hours, Monday through Friday, 9:00 a.m. to 5:00 p.m. ET. The Army SBIR/STTR Office is at 2530 Crystal Drive, Suite 11192, Arlington, Virginia 22202.

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

Everything that applies to the SBIR twin applies here, plus a set of considerations specific to running a two-organization proposal.

‍ ‍

Decide honestly which program fits. The STTR partnership requirement is a feature if your research institution brings people, instruments, datasets, or methods you cannot replicate, and a liability if it is decoration. Evaluators read Technical Team and Technical Approach closely, and a partner with no defined role is visible.

‍ ‍

Make the partnership do work in the narrative. Name what the research institution contributes that you cannot: the semantic modeling expertise, the knowledge graph work, the evaluation methodology, access to a laboratory or a corpus. Then show the seam, meaning how their contribution integrates with what you build. A proposal that reads as two projects stapled together scores worse than a single-organization proposal.

‍ ‍

Start the institutional clock immediately. Sponsored programs offices have their own internal deadlines, often a week or more before the sponsor deadline, and they control whether your budget and any required agreements arrive on time. Call them before you write anything.

‍ ‍

Resolve intellectual property early. Phase II envisions a commercial open-source platform, Phase III envisions installation contracts, and the deliverables include computer software and algorithms. Your partner's technology transfer office will have views on all of that. Better to hear them in September than during contract negotiation.

‍ ‍

Lead with reproducibility and auditability, not model capability. The word "auditable" is in the topic title. "Reproducible outputs," "traceability," "human control," and "predictable behavior" all appear in the description. The differentiator is not a better model, it is a governed system where a decision authority can see why the answer is the answer and what would change it.

‍ ‍

Build the "what flips the decision" logic explicitly. This phrase appears verbatim in the Phase I desired outcomes. If your proposal does not have a named capability that answers it, you are leaving a scoring element on the table.

‍ ‍

Plan for two demonstrations, and make them structurally different. One point-in-time trade study, one multi-episode decision program with a refresh cycle. Naming both, with distinct data and distinct evaluation runs, directly satisfies a stated Phase I outcome.

‍ ‍

Speak ground vehicle. The topic calls for context engineering specifically for the ground vehicle domain through knowledge graphs and semantic layers. Generic decision-support framing will read as misaligned, and Alignment is scored.

‍ ‍

Ground yourself in Digital Engineering standards. SysML 2.0 and UML are named. Digital threads and digital twins are named. Interoperability across DE tools is an explicit expectation.

‍ ‍

Use proven, ideally Army-fielded, enabling technologies. The rubric penalizes emerging or cutting-edge dependencies and rewards Army-fielded ones. This is where academic instincts can cut against you, since novelty is the currency of research and proven maturity is the currency of this rubric. Frame the novelty in the schema and the governance, not in the underlying infrastructure.

‍ ‍

Do not let the research strength mask a weak commercialization case. Commercial Potential is 25 percent, and the Army defines product revenue as directly selling a solution, explicitly excluding consulting, services, and research activities. Sponsored research funding is not product revenue and grant funding is not "other people's money" in the sense the rubric means. The automotive vehicle design analog in the Phase III dual-use paragraph is handed to you. Use it.

‍ ‍

Do the customer discovery now. Programmatic Potential is 20 percent and the top of the scale requires exhaustive interviews with validation that informs a credible transition strategy. PAE Maneuver Ground and PAE Fires are named in the Phase II text, which tells you exactly where the Phase II cases will come from and therefore who is worth talking to during pre-release.

‍ ‍

Position against, or alongside, DAOSoft. The Army names the current COTS baseline and states it is agnostic and open to any and all ideas that extend or replace current acquisition capabilities. That is an invitation to make a clear-eyed competitive argument, including against indirect substitutes, which the Solution's Advantages criterion explicitly asks about.

Army SBIR ARM26BX06-NV012: Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions

Quick Answer

ARM26BX06-NV012 is a U.S. Army SBIR Phase I topic released under the Department of the Army 2026 SBIR Program Commercial Solutions Opening (CSO), Release 6. The Army is asking small businesses to prove out a "decision-as-a-program" capability: an agentic AI system, built on a formal decision schema, that turns messy engineering and acquisition questions into structured, auditable, signer-ready Decision Packages. Phase I awards are up to $300,000 for a period of performance of 1 to 6 months. The topic opens for proposals on September 23, 2026 and closes on October 21, 2026. Proposals are submitted only through the Defense SBIR/STTR Innovation Portal (DSIP), and complete proposals must be certified in DSIP no later than 12:00 p.m. ET on October 21, 2026. This is a Phase I feasibility topic, so Direct to Phase II is not available under this topic number.

That gives you a 29 day submission window and, working back from the close date, roughly two weeks from open before the DSIP Topic Q&A channel closes on October 7, 2026.

Topic At a Glance

‍ ‍

Topic number: ARM26BX06-NV012

‍ ‍

Title: Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions

‍ ‍

Solicitation: Department of the Army 2026 SBIR Program, Commercial Solutions Opening (CSO), Component-Specific Proposal Instructions, Release 6

‍ ‍

Agency: U.S. Army, under the Department of War (DoW) SBIR/STTR program

‍ ‍

Phase offered: Phase I (Feasibility) only

‍ ‍

Award ceiling: Up to $300,000

‍ ‍

Period of performance: 1 to 6 months

‍ ‍

Contract type: FAR-based, firm-fixed-price, with payments tied to measurable milestones or deliverables

‍ ‍

OUSD (R&E) Critical Technology Area: Applied Artificial Intelligence (AAI)

‍ ‍

Component Technology Priority Areas: Trusted AI and Autonomy; Information Systems

‍ ‍

Projected CMMC level requirement: Level 1

‍ ‍

Submission portal: DSIP at dodsbirsttr.mil

‍ ‍

Topic open date: September 23, 2026

‍ ‍

Proposal deadline: October 21, 2026 at 12:00 p.m. ET

‍ ‍

DSIP Topic Q&A closes: October 7, 2026, two weeks prior to the close date

‍ ‍

Selection notification: Within 90 days of the topic close date, meaning on or about January 19, 2027

‍ ‍

Keywords: Agentic AI, Digital Engineering, schema-driven Decision Management, acquisition decisions, AI LLM

‍ ‍

What the Army Is Actually Looking For

‍ ‍

The core objective

‍ ‍

The Army wants proof of a decision-as-a-program capability. In plain terms, that means taking a complex engineering or acquisition question, one that today gets answered through slide decks, spreadsheets, email threads, and tribal knowledge, and turning it into a structured, machine-readable, auditable decision artifact that a decision authority can actually sign. The Army's stated goal is to do this faster and with higher confidence than the status quo.

‍ ‍

The emphasis in the topic language is on proof by demonstration, not a full product build. Phase I is not the place to promise a shipping platform. It is the place to show that the schema plus the agentic layer works on real decision problems, both point-in-time trade studies and long-horizon acquisition decision programs, with traceability, robustness, and human control intact.

‍ ‍

The three technical objectives

‍ ‍

Objective one: a unified representation. The Army wants a single decision model that supports two very different shapes of work. The first is the single-episode trade study, a bounded comparison of options against criteria. The second is the multi-episode "decision program," a long-running decision with refresh cycles as evidence and assumptions change over time. The topic specifically calls for context engineering for the ground vehicle domain, implemented through knowledge graphs and semantic layers that capture domain-specific relationships, constraints, and requirements. The system is expected to integrate data from Digital Engineering (DE) tools such as SysML 2.0 and UML, pulling from digital threads and digital twins to provide a unified view of system models across the product lifecycle.

‍ ‍

Objective two: agentic capabilities with human control. The AI layer must produce structured artifacts and reproducible outputs. Reproducibility is called out explicitly, which is a strong signal: nondeterministic, unauditable LLM output alone will not satisfy this topic. The agentic system is expected to perform structured elicitation into the formal model, generate decision workflow plans, and execute evaluation runs with clear "what flips the decision" logic. It is also expected to automate validation of technical documents, models, and outputs against standards and requirements, while maintaining predictable behavior consistent with established human-AI interaction guidance.

‍ ‍

Objective three: explicit bias checks, risks, and assumptions. The schema must be extended so that bias checks, risks, and assumptions become first-class, testable objects rather than prose buried in a report. The purpose is decision readiness: the ability to assess whether a decision is actually ready for sign-off before it is signed, and to responsibly refresh it when conditions change. Semantic understanding is expected to keep consistency across digital engineering artifacts and enable traceable decision rationale.

‍ ‍

Phase I desired outcomes

‍ ‍

The topic lists three Phase I deliverable outcomes:

‍ ‍

1. A decision schema that makes objectives, options, constraints, assumptions, risks, and bias checks first-class objects.

2. Agentic AI that performs structured elicitation into the formal model, generates decision workflow plans, and executes reproducible evaluation runs with clear "what flips the decision" logic.

3. Two end-to-end demonstrations showing the approach scales from point-in-time trade studies to long-horizon program decisions with refresh cycles as evidence and assumptions change.

‍ ‍

Two demonstrations, not one. That is a concrete, checkable requirement and a common place where proposals lose points by being vague.

‍ ‍

Where this goes in Phase II

‍ ‍

The Army is explicit that the DoW already has multiple contractors building AI and LLM tools for core warfighter purposes, but very little effort has gone toward an AIgentic decision intelligence capability that supports accelerated commercial acquisition or longer lead traditional development. That gap is the reason this topic exists.

‍ ‍

In Phase II, the expectation is that the successful contractor develops a combined AIgentic and AI/LLM decision intelligence workflow capability, exercised on two real cases provided from PAE Maneuver Ground and PAE Fires. The resulting software platform is to be modeled and developed as a commercial open-source platform usable by both the DoW and commercial enterprises for Product Design and Development (PDD) and acquisition.

‍ ‍

The topic names the current COTS baseline directly: DAOSoft, which provides an open capability with an advanced structured decision and trade study capability plus a partially developed AI/LLM decision intelligence workflow. The Army states it is looking for any and all ideas that can extend or replace current acquisition capabilities and is agnostic to all current solutions. The Army is also agnostic as to which developed AI commercial package fulfills the addition of AIgentics to current AI/LLM for continuous acquisition.

‍ ‍

The Phase II prototype is expected to be immediately useful, with follow-on Phase III contracts anticipated for individual customer installation, described by the Army as similar to current best practice deployment of large ERP systems from SAP and Oracle.

‍ ‍

Phase III dual use

‍ ‍

The named commercial analog is the vehicle design process in the automotive industry. The Army notes the workflow can be relatively similar to the vehicle design process for the Army, with some different considerations. For a startup, this is a useful signal: the commercialization argument writes itself around complex-system product development and capital program decision-making outside defense.

‍ ‍

Reference cited in the topic

‍ ‍

The topic cites one reference, an SAE Mobilus paper: "Concept execution AI agentic decision intelligence framework product planning concept development," 2025-01-0455, at saemobilus.sae.org.

‍ ‍

Funding Allowance and What You Can Add On Top

‍ ‍

Base award

‍ ‍

Phase I under this topic is up to $300,000 for 1 to 6 months. Award funding guideline and period of performance limitations are established per topic, and the solicitation is blunt about this: proposals exceeding these limitations will be deemed unresponsive. Do not propose $325,000 and do not propose nine months.

‍ ‍

The number of awards depends on funds availability. The Army reserves the right to award none, one, or more than one contract under any topic. Awards are FAR-based, firm-fixed-price, with fixed price payments tied to measurable milestones or deliverables agreed to by the Government. Milestone schedules are used to monitor technical progress, mitigate technical and cost risk, and address awardee cash flow needs. The Contracting Officer retains the right to negotiate contract type and price.

‍ ‍

Technical and Business Assistance (TABA)

‍ ‍

TABA is additional money on top of the award ceiling. For Phase I, the Army may provide up to $6,500 per project. For Direct to Phase II projects, up to $50,000. TABA is not guaranteed and depends on the Government's review of the requested services and available TABA budget.

‍ ‍

There are two options and the paperwork differs:

‍ ‍

Option 1, Army-preferred vendor. Up to $6,500 per Phase I project. If you use the Army's preferred provider, the TABA cost does not need to be included in your DSIP Cost Volume (Volume 3). If approved, funding goes directly to the Army's preferred provider. Participation is voluntary and application instructions come after contract award. Commonly requested services include customized market research and strategy, intellectual property support, CMMC compliance, DCAA compliance, and communications and marketing.

‍ ‍

Option 2, firm-selected vendor. You may contract TABA services through one or more TABA providers, or use the funding to hire new or augment staff, or to have staff conduct or participate in training activities consistent with 15 U.S.C. 638(q)(1). If you choose your own provider, the proposed TABA amount must be included in the DSIP Cost Volume (Volume 3) and details of the TABA request must be included in Supporting Documents (Volume 5).

‍ ‍

Critical TABA compliance points:

‍ ‍

TABA funding will be denied if the costs are omitted from the initial proposal submission, or if proposed TABA costs exceed $6,500 per Phase I project.

‍ ‍

TABA costs cannot include any profit or fee for the proposer.

‍ ‍

TABA costs cannot be factored into the calculation of general and administrative expenses (G&A).

‍ ‍

The amount is based on the original contract period of performance and does not apply to period of performance extensions or enhancements.

‍ ‍

The TABA provider cannot be your own firm or any affiliated entity.

‍ ‍

The rationale statement in Volume 5 is limited to two pages and must include the provider name, point of contact with email and phone, an explanation of the provider's suitability and qualifications, an outline of specific tasks, and total provider cost with number of hours and labor rates. A blended or average rate is acceptable.

‍ ‍

Phase II Enhancement

‍ ‍

Looking further out, the Department of the Army may provide a Phase II awardee with up to $500,000 in matching SBIR funding on a dollar-for-dollar basis if the performer obtains a commitment of non-SBIR/STTR funding from a DoW component, another federal agency, or a commercial investor. The enhancement effort must develop, deliver, and integrate a technology or product into a program within a DoW component, federal agency, or the commercial sector. Enhancement requests are subject to approval by the Army SBIR/STTR Program's Source Selection Authority, successful negotiations, and funding availability. Enhancement funding is typically applied to an active Phase II award through a contract modification, with additional scope of work and period of performance commensurate with the total funding received.

‍ ‍

For a startup, this matters at the strategy level: a credible non-dilutive path exists from a $300,000 Phase I to a Phase II with up to $500,000 in matched enhancement, then Phase III installation contracts.

‍ ‍

Timeline and Key Dates

‍ ‍

The dates that matter

‍ ‍

Topic opens for submission: September 23, 2026

‍ ‍

DSIP Topic Q&A closes: October 7, 2026

‍ ‍

Deadline for administrative questions to the Army: October 6, 2026, which is 15 days prior to closing

‍ ‍

Proposal deadline: October 21, 2026 at 12:00 p.m. ET

‍ ‍

Selection or non-selection notification: on or about January 19, 2027, within 90 days of close

‍ ‍

Start of Work Meeting, if awarded: within 30 calendar days after contract award

‍ ‍

Note that the proposal deadline is noon Eastern, not end of day. That is 11:00 a.m. Central, 10:00 a.m. Mountain, and 9:00 a.m. Pacific on October 21. Teams on the West Coast routinely lose proposals to this detail.

‍ ‍

The sequence in detail

‍ ‍

Pre-release period, before September 23, 2026. The topic sits in pre-release on DSIP. During pre-release, topic author names, phone numbers, and email addresses are published with the topic on the DSIP Topics and Topic Q&A page. This is the only window for direct contact with the topic author, and once the topic opens on September 23 that door closes.

‍ ‍

Topic open, September 23, 2026. The topic opens for proposal submission in DSIP.

‍ ‍

DSIP Topic Q&A window, closing October 7, 2026. Topic Q&A opens on the pre-release date and closes two weeks prior to the topic close date. All questions and answers are posted publicly on a non-attribution basis. Answers are generally posted within seven business days and are also emailed directly to the person who asked. Because answers can take seven business days, a question submitted on October 7 may not be answered until roughly October 16, leaving you only a few days to act on it. Ask early.

‍ ‍

Administrative question deadline, October 6, 2026. General questions about Army SBIR Program administration and the Army component-specific proposal instructions should be submitted as soon as possible, and no later than 15 days prior to solicitation closing, to usarmy.SBIRSTTR@army.mil.

‍ ‍

Proposal deadline, October 21, 2026 at 12:00 p.m. ET. Complete proposals must be certified and submitted in DSIP by this time. Proposals cannot be submitted after the deadline and will not be accepted or evaluated.

‍ ‍

Selection or non-selection notification, on or about January 19, 2027. Within 90 days of the topic close date, by email to the Corporate Official listed on the proposal cover sheet, sent from the Army SBIR/STTR Program Office mailbox.

‍ ‍

Start of Work Meeting. Held virtually within 30 calendar days after contract award, unless another location is designated in the contract.

‍ ‍

Periodic reviews. Monthly, bi-monthly, or quarterly review meetings as specified in the contract.

‍ ‍

Final Report of Inventions and Subcontracts. DD Form 882, due within six months after completion of the contracted work.

‍ ‍

Planning note: the Army warns that proposals should be submitted as early as possible to avoid delays caused by high traffic near closing. The Department of the Army is not responsible for missed submissions due to system latency or inaccessibility. A proposal sitting in "In Progress" or "Ready to Certify" status is not submitted, even if every volume has been uploaded before the close date.

‍ ‍

A working backward schedule

‍ ‍

If you are starting from scratch, here is a realistic way to use the 29 days.

‍ ‍

Now through September 22. Confirm your SAM registration is active and that your DSIP profile matches it exactly. Get every team member a DSIP account. Complete the annual Volume 6 Fraud, Waste and Abuse training. Identify the topic author during pre-release and get your requirements questions asked while direct contact is still allowed.

‍ ‍

September 23 through September 30. Run Army customer discovery interviews. This is the single highest leverage activity available to you and it cannot be faked in the writing. Draft the technical approach and lock down which two demonstrations you will propose.

‍ ‍

October 1 through October 7. Complete a full technical volume draft. Submit any remaining questions through DSIP Topic Q&A before it closes on October 7.

‍ ‍

October 8 through October 14. Build the Cost Volume with substantiating documentation. Assemble every Volume 5 attachment, including the two page Non-Proprietary Work Plan, the foreign citizens list or the statement that none are involved, and Key Personnel with the PI technical resume. Complete the Volume 7 foreign affiliations web form.

‍ ‍

October 15 through October 17. Compliance pass. Verify the seven page limit, 10-point minimum type, one inch margins, page numbering, and headers with company name, topic number, and DSIP proposal number. Confirm the PDF is searchable, unlocked, unencrypted, and virus checked.

‍ ‍

October 18 through October 19. Upload everything to DSIP and execute the corporate official certification. Confirm the status is no longer "In Progress" or "Ready to Certify."

‍ ‍

October 20 through October 21. Buffer only. Do not plan to use these days.

‍ ‍

Eligibility and Registrations You Need Before You Can Submit

‍ ‍

You must be a Small Business Concern (SBC) meeting all eligibility requirements in 13 CFR 121.702 and the SBA SBIR/STTR Policy Directive.

‍ ‍

System for Award Management (SAM). You must be registered and active in SAM in accordance with FAR Provision 52.204-7, both when submitting and at time of award. Proposals from firms failing this may be deemed unresponsive. You may only submit using your legal business name or a DBA name as indicated in the SAM registration for the provided Unique Entity Identifier (UEI). A DBA used on an offer must be registered and linked to your current, active SAM registration. Firms that are debarred, suspended, proposed for debarment, or voluntarily excluded are excluded from award, and the Army will not consent to subcontracts with such contractors.

‍ ‍

DSIP registration. DSIP is the official portal. Proposals submitted by any other means will be disregarded. Every individual who will prepare or submit must have an individual DSIP user account. Register as early as possible. Your DSIP account profile must correlate with your SAM registration, including the 5-digit CAGE code, 12-digit UEI, legal business name, DBA name, and physical address. Failure to correlate this information, or to submit required certifications, may significantly delay funding agreement award or become grounds for cancellation of the funding agreement.

‍ ‍

Venture capital, hedge fund, and private equity ownership. SBCs owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit and receive awards under the Army SBIR Program. All applicants that are majority-owned by multiple VCOC, HF, or PEF and are submitting to an Army topic must complete the Verification of Eligibility of Small Business Joint Ventures certification before submitting, and must include that certification with the submission.

‍ ‍

Principal Investigator employment. The primary employment of the Principal Investigator or Project Manager must be with the SBC at the time of award and during the conduct of the proposed project.

‍ ‍

Proposal Structure: What You Actually Submit

‍ ‍

Army component-specific instructions supplement and in some cases supersede the DoW 2026 SBIR Program CSO. Where they conflict, the Army instructions take precedence.

‍ ‍

Volume 1, Proposal Coversheet

‍ ‍

Prepared in DSIP in accordance with the DoW solicitation.

‍ ‍

Volume 2, Technical Volume

‍ ‍

Format requirements, and the solicitation states that submissions failing to conform shall be deemed unresponsive:

‍ ‍

Single Adobe Acrobat PDF, searchable text format, including graphics. PDFs that cannot be opened using Adobe Acrobat products may be rejected. Perform a virus check before uploading. Do not lock, password protect, or encrypt the file. Do not include or embed active graphics such as videos or moving pictures.

‍ ‍

Page limit for Phase I: seven pages, including all key sections. The limit applies to the entire Technical Volume as uploaded to DSIP. At the Government's discretion, pages that clearly do not substantiate or contribute to the technical approach, such as a cover sheet or table of contents, may be excluded from the count. Any appendices or supplemental content that expand upon the required content do count toward the seven pages. You may allocate the pages across sections however you want.

‍ ‍

Layout: number all pages consecutively. No type smaller than 10-point, standard 8.5 by 11 inch paper, one-inch margins including the header. The header on each page, which may sit inside the one-inch margin, should contain the proposing SBC's name, the topic number, and the DSIP assigned proposal number from the cover sheet.

‍ ‍

General: graphics are strongly encouraged throughout. For plots and charts, include title, caption, axes labels, and scale. Avoid jargon and define all technical terms. Use the compress pictures feature to reduce file size.

‍ ‍

Required section order for Phase I:

‍ ‍

1. Introduction

2. Army Benefits

3. Technical Approach

4. Programmatic Potential

5. Commercial Potential

‍ ‍

These sections map one-to-one onto the Phase I evaluation rubric in Appendix A. Your Volume 2 must also be consistent with the Non-Proprietary Work Plan you upload in Volume 5.

‍ ‍

What each section needs, in the Army's own framing:

‍ ‍

Introduction. A clear, concise description of what your innovation does or will do, and where you are in your evolution. Make clear its intended impact on the Army. Evaluators should "get it" after reading this.

‍ ‍

Army Benefits. Identified Army use cases, the solution's advantages, and the potential level and scale of impact. If you are unsure how an Army end user would benefit, provide an analogous use case so evaluators can connect the dots. Three rubric prompts: Alignment, argue your innovation aligns with this topic's priorities as defined in the solicitation. Solution's Advantages, prove customers will choose you given limited resources and many choices, and account for indirect substitutes as well as direct competitors. Solution's Impact, the Army seeks higher-risk, high-impact solutions through SBIR, not engineering changes or incremental improvements.

‍ ‍

Technical Approach. Details and supporting data on how you will solve the problem, key elements of your approach, the technical team, and risks with mitigation plans. Use data to substantiate that your risk mitigation plans are credible, attributed to reliable, credible sources. Rubric prompts: Scientific Feasibility, Enabling Technologies (do the required enabling technologies introduce added risk), Technical Team, Technical Risk and Mitigation Plans, and Data Quality.

‍ ‍

Programmatic Potential. Where your company is today, what will be accomplished under this SBIR effort with Army customer discovery, and the risks and mitigations for transitioning beyond SBIR funding into a contract with an Army or integration with an Army system. Rubric prompts: Project Milestone Schedule, Army Customer Discovery and Validation (are you "getting out of the building" and do you have formal or informal customer validation), and Army Transition Pathways (what is the next type of deal you aim to make with the Army after this award).

‍ ‍

Commercial Potential. The commercial market the DoW can build upon, your past success, and future potential. Rubric prompts: R&D to Product Revenue (has your team transitioned R&D into products with actual product revenue, which the Army defines as directly selling a solution rather than selling consulting, services, or research activities), Competitive Edge (why will you win, something your team does very well that is difficult to match, such as protected IP, unmatched relevant experience, a novel business model, or network effects), and Other People's Money (the non-DoW commercial market case).

‍ ‍

Volume 3, Cost Volume

‍ ‍

Cost and duration limits are detailed in the topic. Options are not anticipated at this time; if an option is identified in the topic posting, Base and Option costs must be separated and clearly identified. All proposed costs must be accompanied by documentation substantiating how the cost was derived. Failure to include supporting documentation may delay award, since the Contracting Officer will have to request it. Failure or refusal to provide documentation may result in dissolution of the contract action.

‍ ‍

Volume 4, Company Commercialization Report

‍ ‍

Required for prior SBIR/STTR awardees. Information in the CCR will be considered during proposal evaluation.

‍ ‍

Volume 5, Supporting Documents

‍ ‍

This is where proposals most often die on compliance. The solicitation states plainly that a completed proposal submission in DSIP does not indicate that the mandatory supporting documents have been uploaded. Failure to upload any mandatory document as a separate attachment will result in the proposal being deemed administratively non-compliant and unresponsive. Unresponsive proposals are un-awardable and may be excluded from technical evaluation entirely.

‍ ‍

Mandatory items, uploaded as separate attachments:

‍ ‍

1. Non-Proprietary Work Plan. Two page limit. A summary based on the Volume 2 technical approach, outlining technical objectives, key milestones, and deliverables. It serves as the basis for performance requirements in the final contract and must be written for a public, technically literate audience with no sensitive or proprietary information.

2. List of Foreign Citizens. Identify any foreign nationals or dual citizens expected to be involved as a direct employee, subcontractor, consultant, or Research Institution. Provide a single PDF with a listing of citizenships, countries of origin, type of visa or work permit, and an explanation of anticipated level of involvement. If no foreign nationals will be involved, substitute a statement to that effect. The Army specifically warns that small businesses often incorrectly assume everyone with dual citizenship or a work permit is automatically permitted to work on SBIR/STTR projects and fail to identify them. Failure to provide this may significantly delay selection or award.

3. Key Personnel. Identify all key personnel with information on education and experience. A technical resume for the Principal Investigator, including publications if any, must be included. Resumes for other technical staff, subcontractors, and consultants are useful and may also be included.

‍ ‍

If applicable, also submit: SBIR/STTR Funding Agreement Certification; Verification of Eligibility of Small Business Joint Ventures; Assertion of use, release, or disclosure restriction per DFARS 252.227-7017; DD Form 2345 Military Critical Technical Data Agreement for ITAR-subject actions; SBC-selected details of TABA request; and other documentation such as letters of support. The Army may also accept cost/pricing information and other items only as specified in the topic. Anything else submitted will be disregarded, including promotional and non-project material.

‍ ‍

Volume 6, Fraud, Waste and Abuse Training

‍ ‍

Material is in the Volume 6 section of the DSIP proposal submission module and must be thoroughly reviewed once per year to proceed with proposal submission.

‍ ‍

Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries

‍ ‍

A web form. PDF uploads are no longer accepted. Disclosure does not mean automatic denial, but failure to complete the form completely and accurately may render the proposal administratively non-compliant and unresponsive.

‍ ‍

Per 15 U.S.C. 638(vv), 15 U.S.C. 638(g)(13), and the SBA SBIR/STTR Policy Directive, disclosures must consider subcontractors, subsidiaries, joint ventures, consultants, and their employees across four categories: foreign affiliations, including any subsidiary, parent company, or joint venture based in, funded by, or with a foreign affiliation with any foreign country of concern; contractual or financial obligations with a foreign entity, and the Army notes that a subcontracting agreement is by definition a contractual and financial obligation; related entities, meaning any foreign business entity, offshore entity, or entity outside the United States related to the SBC; and covered individuals, meaning anyone who contributes in a substantive, meaningful way to the scientific development or execution of the project, regardless of title or Key Personnel designation, whether employed by the prime, a subcontractor, a consultant, or a partnering Research Institution.

‍ ‍

How Your Proposal Will Be Evaluated

‍ ‍

The process

‍ ‍

Initial screening for responsiveness, timeliness, and SBC eligibility. Responsiveness means failing any material requirement of the solicitation, including compulsory terms and conditions, makes the proposal unresponsive. Timeliness means received on or before the due date and prior to the established set time. Assessment of responsiveness and eligibility may continue during technical evaluation and even after selection.

‍ ‍

National security and foreign risk assessment. The Army conducts a foreign risk evaluation review of every proposal, referencing the 2026 Department of War SBIR/STTR Foreign Risk Evaluation Program Common Decision Matrix dated 08 July 2026. Importantly, the Army states it relies on statutory authority rather than non-regulatory guidance documents, and that the matrix is illustrative and non-exhaustive. The Army's assessment is not limited to the factors or countries listed. It evaluates the Volume 7 Foreign Disclosure and all areas identified under 15 U.S.C. 638(vv), including cybersecurity practices, patent analysis, employee analysis including subcontractor employee foreign affiliations, foreign ownership, financial ties and obligations, and employee ties to foreign entities. If risks are identified, the Army decides at its sole discretion and case by case whether they can be adequately mitigated. The Army is not required to coordinate with the proposer to develop a mitigation plan and is not obligated to disclose specific findings. Where risks cannot be effectively mitigated, the proposal may be removed from consideration regardless of technical evaluation results.

‍ ‍

Technical evaluation. Proposals passing initial screening receive a technical evaluation against the criteria in Appendix A, reviewed by a cadre of subject matter expert evaluators using the weighted rubric. Proposals are assessed on their own individual merit against the stated criteria, not against each other. Because foreign risk assessment runs in parallel, the Army reserves the right to pause, suspend, or entirely forego technical evaluation, and pausing does not create any right to a mitigation period. Designated support contractors, bound by non-disclosure agreements, may review submissions for evaluation purposes; submitting a response constitutes assent to that.

‍ ‍

Other assessment considerations. Under RFO FAR 25.502, the Government will eliminate any offeror that is unacceptable for reasons other than price, including use of prohibited sources. Proposers and subcontractors are strictly prohibited from using products or services listed in RFO FAR 40.202, including but not limited to TikTok/ByteDance, Kaspersky, and specific unmanned aircraft systems.

‍ ‍

Selection. Notification within 90 days of topic close. Selected proposals are not guaranteed a contract award, and the selection notice is not an authorization to commit or expend funds. After selection, proposals go to a Contracting Officer for further evaluation and negotiation, which may include representations and certifications, certified or other than certified cost data, and other information. Award happens only when a Contracting Officer signs an award document.

‍ ‍

Feedback. The Army will provide feedback to offerors per the SBA SBIR/STTR Policy Directive, with instructions in the selection decision notice. This is not a FAR Part 15 debriefing, and offerors are neither entitled to nor will receive FAR Part 15 debriefs.

‍ ‍

Phase I scoring weights

‍ ‍

The Phase I Evaluation Criteria v4-0 rubric in Appendix A assigns these weights:

‍ ‍

Introduction, 3 percent

‍ ‍

Army Benefits, 15 percent, covering Alignment, Solution's Advantages, and Solution's Impact

‍ ‍

Technical Approach, 35 percent, covering Scientific Feasibility, Enabling Technologies, Technical Team, Technical Risks and Mitigation Plans, and Data Quality

‍ ‍

Programmatic Potential, 20 percent, covering Project Milestone Schedule, Army Customer Discovery and Validation, and Army Transition Pathway

‍ ‍

Commercial Potential, 25 percent, covering R&D to Product Revenue, Competitive Edge, and Other People's Money

‍ ‍

Proposal Quality, 2 percent, covering Quality of Prose and Images, Charts, Graphics

‍ ‍

Each element is scored Unsatisfactory, Marginal, Satisfactory, or Superior. A few of the distinctions worth internalizing, because they tell you exactly what "Superior" looks like:

‍ ‍

Alignment: Superior is "perfectly aligned with this Army topic's priorities," not merely "aligned."

‍ ‍

Solution's Impact: Satisfactory is "significant improvement vs. the state of the art." Superior is "radical improvement."

‍ ‍

Enabling Technologies: Satisfactory "requires proven technologies." Superior "requires Army-fielded technologies." Marginal "requires emerging, cutting edge technology," and Unsatisfactory "requires nonexistent or unavailable technology." This is a real trap for AI startups. Building on exotic, unproven infrastructure scores you down, not up.

‍ ‍

Army Customer Discovery and Validation: Unsatisfactory is "no customer interviews completed, no validation." Marginal is "a handful of customer interviews completed, no validation." Satisfactory is "extensive interviews completed, early validation beginning to inform transition strategy." Superior is "exhaustive interviews completed, validation informs credible transition strategy." You cannot score well here without having actually talked to Army stakeholders before you submit.

‍ ‍

R&D to Product Revenue: Unsatisfactory is "no evidence of creating product revenue from R&D efforts." Superior is "evidence of R&D yielding product revenue sufficient to fuel this company's growth." Note again the Army's definition of product revenue: directly selling a solution to solve a problem, not selling consulting, services, or research activities.

‍ ‍

Other People's Money: Unsatisfactory "fails to present non-DoD sources for future R&D funding." Superior is "diverse and robust non-DoD sources of future R&D funding."

‍ ‍

Taken together, 45 percent of your score sits in Programmatic Potential plus Commercial Potential. For a deep-tech AI team, that means nearly half the evaluation is not about your architecture. It is about whether you have done customer discovery with the Army, whether you have a named next deal, whether you have real product revenue history, and whether you have non-defense money in the picture.

‍ ‍

Contract Requirements After Award

‍ ‍

Deliverables. Hardware or prototype deliverables per the topic, if applicable. Data is ordered using DD Form 1423 Contract Data Requirements Lists (CDRLs) located at Section J, Exhibits of the contract. Each CDRL references a Data Item Description viewable through the Acquisition Streamlining and Standardization Information System (ASSIST).

‍ ‍

All Army SBIR/STTR funding agreements include two CDRL requirements: Status Reports under DID number DI-MGMT-80368A, due at a specified time after award and periodically thereafter (monthly, bi-monthly, or quarterly), and a Scientific and Technical Report under DID number DI-MISC-80711A, a final report delivered per the prepared DD Form 1423. The Army end user may require additional deliverables including software documentation and user manuals, engineering drawings, operation and maintenance documentation, safety hazard analysis, or updated commercialization results.

‍ ‍

Meetings. A Start of Work Meeting within 30 calendar days of award, held virtually at your facility unless otherwise designated, to establish mutual understanding of contract terms, conditions, line items, technical requirements, and sequence of events. Then periodic review meetings to report status, accomplishments, difficulties, and progress against planned goals and resources expended.

‍ ‍

Invention reporting. Under FAR 52.227-11 and DFARS 252.227-7039, Phase II contracts require an Interim Report of Inventions and Subcontracts on DD Form 882 twelve months from the date of initial contract award. All Phase I and Phase II contracts require a Final Report of Inventions and Subcontracts on DD Form 882 within six months after completion of the contracted work. SBIR awardees must report inventions within two months of the inventor's report to the awardee, and may do so through the Edison Invention Reporting System at iedison.gov.

‍ ‍

Controlled Unclassified Information. Successful firms must comply with CUI DoDI 5200.48. Firms must monitor CUI for aggregation and compilation based on the potential to generate classified information, report the potential classification of aggregated or compiled CUI to the ASA(ALT) Security Manager, and submit unclassified DoW information for review and approval for release in accordance with DoDI 5230.09. CUI records must follow approved mandatory disposition authorities.

‍ ‍

CMMC. The projected CMMC level requirement for this topic is Level 1. CMMC compliance support is one of the commonly requested TABA services, which is worth knowing if you are not yet compliant.

‍ ‍

Asking Questions the Right Way

‍ ‍

There are two channels and they have different rules.

‍ ‍

Direct contact with topic authors, pre-release only. During pre-release, topic author names, phone numbers, and email addresses are published with the topic on DSIP. You may contact them by phone or email to ask technical questions about specific solicitation topics. Questions must be limited to specific information related to understanding a particular topic's requirements. You may not ask for advice or guidance on solution approach and may not submit additional material to the topic author. If information from an exchange is deemed necessary for proposal preparation, it will be made available to all parties through DSIP Topic Q&A. After pre-release, no further direct contact is allowed unless the author is responding to a question submitted during pre-release.

‍ ‍

DSIP Topic Q&A. Opens on the pre-release date and closes two weeks prior to the topic close date. Written questions and answers are posted on a non-attribution basis for public viewing. Answers are generally posted within seven business days and emailed to the inquirer. Questions are limited to technical information focused on understanding the topic's requirements. Requests for advice on solution approach, or administrative questions about SBIR eligibility, proposal or cost structure, page count, budget and duration limitations, or the proposal due date, will not receive a response. Administrative questions go to the component-specific contact instead.

‍ ‍

Once the proposal submission closes, no communication of any kind is allowed with the topic author or through Topic Q&A regarding submitted proposals.

‍ ‍

The Army advises monitoring DSIP frequently throughout the solicitation period for updates and amendments to topics and for new Q&A entries.

Frequently Asked Questions

‍ ‍

What is Army SBIR topic ARM26BX06-NV012?

‍ ‍

ARM26BX06-NV012 is an Army SBIR Phase I topic titled "Agentic-AI, Schema-Driven Decision Management for Auditable Studies and Acquisition Decisions," released under the Department of the Army 2026 SBIR Program Commercial Solutions Opening, Release 6. It seeks a demonstrated decision-as-a-program capability that converts complex engineering and acquisition questions into structured, auditable, signer-ready Decision Packages.

‍ ‍

How much funding is available under ARM26BX06-NV012?

‍ ‍

Phase I awards are up to $300,000 with a period of performance of 1 to 6 months. Up to $6,500 in Technical and Business Assistance funding may be requested in addition to the award ceiling. Proposals exceeding the topic's stated funding and duration limits will be deemed unresponsive.

‍ ‍

What is the period of performance for this Army SBIR Phase I?

‍ ‍

One to six months. Do not propose a longer schedule, because exceeding the stated period of performance limitation makes a proposal unresponsive.

‍ ‍

When is the proposal deadline for ARM26BX06-NV012?

‍ ‍

Complete proposals must be certified and submitted in DSIP no later than 12:00 p.m. ET on October 21, 2026. Note that this is noon Eastern, not end of day, which is 11:00 a.m. Central, 10:00 a.m. Mountain, and 9:00 a.m. Pacific. Proposals cannot be submitted after the deadline and will not be accepted or evaluated.

‍ ‍

When does this topic open for proposals?

‍ ‍

The topic opens for proposal submission on September 23, 2026, giving a 29 day submission window that closes October 21, 2026.

‍ ‍

When does the DSIP Topic Q&A window close?

‍ ‍

October 7, 2026, two weeks prior to the topic close date. Since answers are generally posted within seven business days, submit questions well before the cutoff if you need the answer in time to use it.

‍ ‍

Is Direct to Phase II available for ARM26BX06-NV012?

‍ ‍

No. The topic index for Release 6 lists this topic as Phase I (Feasibility). Direct to Phase II proposals may only be submitted where a topic posting explicitly allows them. Phase II proposals may otherwise only be submitted by Phase I awardees, and unsolicited Phase II proposals will be rejected without evaluation.

‍ ‍

How long is the technical volume?

‍ ‍

Seven pages for a Phase I proposal, including all required sections. Appendices and supplemental content count toward the seven pages. Cover sheets and tables of contents may be excluded at the Government's discretion. Minimum 10-point type, 8.5 by 11 inch pages, one-inch margins including the header.

‍ ‍

What are the required sections of the technical volume?

‍ ‍

In this order: Introduction, Army Benefits, Technical Approach, Programmatic Potential, and Commercial Potential. These map directly onto the Phase I evaluation rubric in Appendix A of the Army instructions.

‍ ‍

Where do I submit my proposal?

‍ ‍

Through the Defense SBIR/STTR Innovation Portal (DSIP) at dodsbirsttr.mil. Proposals submitted by any other means will be disregarded. Select Army as your component and ASA(ALT) as your command.

‍ ‍

What registrations do I need before submitting?

‍ ‍

An active SAM registration in accordance with FAR Provision 52.204-7, and individual DSIP user accounts for everyone preparing or submitting the proposal. Your DSIP account profile must match your SAM record, including CAGE code, UEI, legal business name, DBA name, and physical address. Register early, since mismatches can delay or void an award.

‍ ‍

What are the most common ways proposals get disqualified?

‍ ‍

Missing a mandatory Volume 5 attachment, since a completed DSIP submission does not mean supporting documents were uploaded. Failing the technical volume formatting requirements. Exceeding the funding or duration limits. Leaving the proposal in "In Progress" or "Ready to Certify" status instead of certifying it. Incomplete or inaccurate Volume 7 foreign affiliation disclosure. Failing to identify foreign nationals or dual citizens on the project.

‍ ‍

How is the Phase I proposal scored?

‍ ‍

By weighted rubric: Technical Approach 35 percent, Commercial Potential 25 percent, Programmatic Potential 20 percent, Army Benefits 15 percent, Introduction 3 percent, and Proposal Quality 2 percent. Each element is rated Unsatisfactory, Marginal, Satisfactory, or Superior.

‍ ‍

Do I need to talk to Army stakeholders before I submit?

‍ ‍

Effectively yes. Army Customer Discovery and Validation sits inside the 20 percent Programmatic Potential weight, and the rubric scores "no customer interviews completed, no validation" as Unsatisfactory while reserving Satisfactory and Superior for extensive or exhaustive interviews with validation informing a credible transition strategy.

‍ ‍

Can I contact the topic author?

‍ ‍

Only during the pre-release period, meaning before the topic opens on September 23, 2026, when author contact details are published with the topic on DSIP. Questions must be limited to understanding the topic's requirements. You may not ask for advice on your solution approach or send them material. After pre-release, use DSIP Topic Q&A, which closes October 7, 2026.

‍ ‍

When will I hear whether I was selected?

‍ ‍

Within 90 days of the October 21, 2026 close date, so on or about January 19, 2027. Notification goes by email to the Corporate Official listed on your proposal cover sheet. A selection notice is not a contract and is not authorization to commit or expend funds.

‍ ‍

What kind of contract will I receive?

‍ ‍

A FAR-based, firm-fixed-price contract, with payments tied to measurable milestones or deliverables agreed to with the Government. The Contracting Officer retains the right to negotiate contract type and price.

‍ ‍

Can venture-backed or private-equity-owned companies apply?

‍ ‍

Yes. Small businesses majority-owned in part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible under the Army SBIR Program. Those applicants must complete the Verification of Eligibility of Small Business Joint Ventures certification before submitting and include it with the submission.

‍ ‍

What is TABA and how do I get it?

‍ ‍

Technical and Business Assistance is funding provided in addition to the award ceiling, up to $6,500 per Phase I project, for services such as market research, IP support, CMMC compliance, DCAA compliance, and marketing. You can use an Army preferred vendor, in which case the cost stays out of your Cost Volume, or your own provider, in which case the cost must be in Volume 3 and a two-page rationale must be in Volume 5. TABA is denied if the costs are omitted from the initial submission or exceed the cap.

‍ ‍

What happens after Phase II?

‍ ‍

The Army anticipates follow-on Phase III contracts for individual customer installation, comparable to how large ERP deployments from SAP and Oracle are rolled out. Separately, the Army Phase II Enhancement Policy may provide up to $500,000 in matching SBIR funding on a dollar-for-dollar basis against committed non-SBIR funding from a DoW component, another federal agency, or a commercial investor.

‍ ‍

What CMMC level does this topic require?

‍ ‍

The projected requirement is CMMC Level 1. CMMC compliance assistance is one of the frequently requested TABA services if you need help getting there.

‍ ‍

Are there prohibited technologies I need to avoid?

‍ ‍

Yes. Proposers and their subcontractors are strictly prohibited from using products or services listed in RFO FAR 40.202, including but not limited to TikTok/ByteDance, Kaspersky, and specific unmanned aircraft systems. Offerors using prohibited sources will be eliminated.

‍ ‍

Who do I contact with administrative questions?

‍ ‍

Email usarmy.SBIRSTTR@army.mil for questions about Army SBIR Program administration and the Army component-specific proposal instructions, no later than 15 days prior to solicitation closing, which is October 6, 2026. For DSIP portal problems, email DoDSBIRSupport@reisystems.com during normal operating hours, Monday through Friday, 9:00 a.m. to 5:00 p.m. ET. The Army SBIR/STTR Office is at 2530 Crystal Drive, Suite 11192, Arlington, Virginia 22202.

‍ ‍

Positioning Advice for Startups Considering This Topic

‍ ‍

This topic rewards a specific profile. Read the rubric backward and it becomes clear.

‍ ‍

Lead with reproducibility and auditability, not model capability. The word "auditable" is in the topic title. "Reproducible outputs," "traceability," "human control," and "predictable behavior" all appear in the description. The differentiator here is not a better model, it is a governed system where a decision authority can see why the answer is the answer and what would change it.

‍ ‍

Build the "what flips the decision" logic explicitly. This phrase appears verbatim in the Phase I desired outcomes. If your proposal does not have a named capability that answers it, you are leaving a scoring element on the table.

‍ ‍

Plan for two demonstrations, and make them structurally different. One point-in-time trade study, one multi-episode decision program with a refresh cycle. Naming both, with distinct data and distinct evaluation runs, directly satisfies a stated Phase I outcome.

‍ ‍

Speak ground vehicle. The topic calls for context engineering specifically for the ground vehicle domain through knowledge graphs and semantic layers. Generic decision-support framing will read as misaligned, and Alignment is scored.

‍ ‍

Ground yourself in Digital Engineering standards. SysML 2.0 and UML are named. Digital threads and digital twins are named. Interoperability across DE tools is an explicit expectation.

‍ ‍

Use proven, ideally Army-fielded, enabling technologies. The rubric penalizes emerging or cutting-edge dependencies and rewards Army-fielded ones. If your stack needs something exotic, say how you have de-risked it, or design that dependency out.

‍ ‍

Do the customer discovery now. Programmatic Potential is 20 percent and the top of the scale requires exhaustive interviews with validation that informs a credible transition strategy. PAE Maneuver Ground and PAE Fires are named in the Phase II text, which tells you exactly where the Phase II cases will come from and therefore who is worth talking to during pre-release.

‍ ‍

Bring commercial revenue and non-defense money. Commercial Potential is 25 percent, and the Army's definition of product revenue excludes consulting, services, and research. The automotive vehicle design analog is handed to you in the Phase III dual-use paragraph. Use it.

‍ ‍

Position against, or alongside, DAOSoft. The Army names the current COTS baseline and states it is agnostic and open to any and all ideas that extend or replace current acquisition capabilities. That is an invitation to make a clear-eyed competitive argument, including against indirect substitutes, which the Solution's Advantages criterion explicitly asks about.

‍ ‍

Take the open-source expectation seriously. Phase II envisions a commercial open-source platform used by both the DoW and commercial enterprises. If your business model depends on a closed core, work out now how it reconciles with that expectation and address it in Commercial Potential.

FDA RFA-FD-25-020: Clinical Studies of Orphan Products Addressing Unmet Needs of Rare Diseases (R01)

The Short Answer

RFA-FD-25-020 is an FDA grant that pays for rare disease clinical trials. It provides up to $650,000 in total costs per year for up to four years, and up to $900,000 per year if you use an innovative or efficient trial design. The money is non-dilutive, meaning you give up no equity and no intellectual property. Applications are due October 20, 2026 and October 19, 2027, and the opportunity expires May 31, 2028.

The program is run by the FDA Office of Orphan Products Development (OOPD), not by the NIH, even though you apply through Grants.gov and eRA Commons. FDA uses its own Objective Review Process, its own page limits, and its own review criteria.

Small businesses and for-profit companies are explicitly eligible, and companies win these awards regularly. More on that below.

RFA-FD-25-020 At A Glance

• Funding opportunity number: RFA-FD-25-020

• Title: Reissue of RFA-FD-23-001, Clinical Studies of Orphan Products Addressing Unmet Needs of Rare Diseases (R01 Clinical Trials Required)

• Agency: U.S. Food and Drug Administration, Office of Orphan Products Development (OOPD)

• Activity code: R01 Research Project Grant

• Assistance Listing Number: 93.103

• Clinical trial status: Required. FDA will only accept applications proposing clinical trials.

• Award ceiling, standard: $650,000 total costs per year, years 1 through 4

• Award ceiling with innovative design justification: $900,000 total costs per year, years 1 through 4

• Maximum project period: 4 years

• Maximum possible total award: $3,600,000

• Cost sharing or matching: Not required

• Application types allowed: New, Renewal, Resubmission, Revision

• Next application deadline: October 20, 2026, by 11:59 PM Eastern Time

• Final application deadline: October 19, 2027, by 11:59 PM Eastern Time

• Resubmission-only deadlines: May 18, 2027 and May 16, 2028

• Opportunity expiration date: May 31, 2028

• Late applications: Not accepted under any circumstances

• Appeals of review outcome: Not accepted

• Foreign organizations: Eligible

Why Startups and Small Companies Should Pay Attention

The R01 label makes founders assume this is an academic-only program. It is not, and the award history proves it.

Under the immediately preceding version of this opportunity, RFA-FD-23-001, FDA funded roughly twenty distinct clinical trial projects. Four of those projects went to for-profit companies rather than universities or hospitals. Based on NIH RePORTER records, those company awards include:

• Ophirex, Inc. (California). Development of intravenous varespladib, a phospholipase A2 inhibitor, for snakebite envenoming. Approximately $2.89 million in cumulative reported funding across fiscal years 2023 through 2025.

• Extend Biosciences, Inc. (Massachusetts). A Phase 2 study of EXT608 in adults with hypoparathyroidism, conducted under IND 146180. Approximately $1.8 million in cumulative reported funding, with annual budgets of roughly $899,800, effectively at the top of the funding ceiling.

• Palvella Therapeutics, Inc. (Pennsylvania). SELVA, a multicenter Phase 3 baseline-controlled study of PTX-022 in microcystic lymphatic malformations. Approximately $1.13 million in cumulative reported funding across fiscal years 2024 and 2025.

• Targeted Therapy Technologies, LLC (New Jersey). A Phase II expanded access clinical trial in retinoblastoma. $1.3 million in cumulative reported funding across fiscal years 2024 and 2026.

Together, those four companies pulled in roughly $7.1 million from a single issue of this opportunity. That is close to one in five funded projects going to industry.

This is not new behavior at OOPD either. Under earlier issues of the same program, DNAtrix, Inc. won multi-year support for a Phase 2a study of DNX-2401 in glioblastoma, and Fibrocell Technologies, Inc. won multi-year support for a Phase 1/2 study of FCX-007 in recessive dystrophic epidermolysis bullosa. Companies have been winning orphan products clinical trials grants for a decade.

Three additional reasons this program fits a clinical-stage company unusually well:

1. None of the SBIR eligibility constraints apply. There is no 500-employee size standard, no requirement that the principal investigator be primarily employed by your company, no 51 percent United States ownership test, and no Phase I before Phase II sequencing. If your company can run the trial, you can apply.

2. Indirect costs are available even without a negotiated rate. If your organization has never established a federal indirect cost rate, FDA allows a de minimis rate of 10 percent of modified total direct costs. Most early-stage companies have no negotiated rate, and most assume that means zero overhead recovery.

3. The award is a regulatory asset, not just cash. OOPD holds regulatory milestone meetings with awardees and monitors progress toward approval. An FDA office is actively invested in your product reaching the market.

What FDA Is Actually Looking For

The purpose of RFA-FD-25-020 is to fund clinical trials that evaluate safety and efficacy in support of a new indication or a change in labeling for a product treating a rare disease or condition. That phrase is the center of gravity of the entire program. FDA is not funding discovery science, target validation, mechanism studies, or device engineering. FDA is funding the human trial data that moves a product closer to an approved label.

The problem FDA is trying to solve

There are more than 10,000 known rare diseases affecting roughly 30 million Americans, and only a few hundred of those diseases have approved treatments. The Orphan Products Grants Program has funded clinical trial research since 1983, and more than 80 of the studies it has funded have gone on to facilitate marketing approval of a rare disease product. That is the outcome FDA is buying with this money.

What is in scope

• Clinical trials in any phase of development, meaning Phase 1, Phase 2, and Phase 3 are all eligible

• Drugs, biologics, medical devices, and medical foods

• Studies of already approved products being evaluated for a new orphan indication

• Studies assessing multiple rare diseases at once, provided prevalence data is supplied for each disease

• Diagnostics and vaccines, but only where the United States population receiving them is fewer than 200,000 people per year

What FDA specifically rewards

Read the announcement closely and four preferences show up over and over. Applications that hit these read as responsive. Applications that ignore them read as academic proposals that wandered into the wrong program.

1. Efficient use of existing infrastructure. FDA wants you to plug into clinical trial networks, data standardization platforms, patient registries, electronic medical records, and CTSAs rather than building everything from scratch. Show that you are not reinventing infrastructure that already exists.

2. Genuine collaboration across stakeholders. FDA repeatedly names the combination of industry, academia, and patient organizations. A company applicant partnered with academic trial sites and a disease foundation is the archetype this program was written for.

3. Early and ongoing patient engagement. This is a scored review criterion in its own right, not a box to check. FDA wants documented evidence that patients and caregivers shaped the protocol design, the data elements, the feasibility assessment, and the data sharing approach. You also need to show how you reduced patient and caregiver burden, including impact on daily living. Letters from patients, caregivers, or patient organizations describing that engagement are required.

4. Innovative and efficient trial designs. This is where the extra $250,000 per year lives. FDA will consider additional funding for applications proposing seamless or adaptive designs that compress trial phases into one continuous trial, basket trials, umbrella trials, or platform trials that test multiple drugs or multiple diseases on common infrastructure. FDA will also consider it for innovative use of data modeling and simulation to study safety and efficacy. FDA strongly recommends engaging a review division about these approaches before you submit, through a preIND meeting, an INTERACT meeting, or another mechanism.

The rare disease definition you must document

FDA considers a product potentially eligible if it is indicated for a disease or condition with a prevalence of fewer than 200,000 people in the United States. For acute diseases lasting less than one year, the annual incidence must be fewer than 200,000 per year. You must document this in a dedicated subsection of your Rationale, using the exact heading "Rare Disease Population/Prevalence," with prevalence calculations and citations.

Orphan subsets of a non-rare disease can qualify, but only if you can explain, based on a characteristic of the product such as mechanism of action, toxicity profile, or prior clinical experience, why the product would be limited to that subset. An orphan subset argument cannot be based on unmet need alone or on how you would prefer to study or market the product. If you already hold OOPD orphan drug designation for the product and disease, include the designation number and date.

Funding Allowance in Detail

Annual budget caps

• Year 1: $650,000 total costs

• Year 2: $650,000 total costs

• Year 3: $650,000 total costs

• Year 4: $650,000 total costs

• Standard four-year maximum: $2,600,000 total costs

These are total costs, meaning direct plus indirect combined. This is the single most misread line in the announcement. Applicants who budget $650,000 in direct costs and then add overhead on top are over budget before review begins.

The innovation supplement

Applications proposing qualifying innovative and efficient trial approaches may request up to an additional $250,000 in total costs per year, raising the ceiling to $900,000 total costs per year for up to four years, or $3,600,000 across the full project period.

To access it you must submit a clear description and justification, limited to three pages, showing how you meet the innovative design requirements. That justification goes in the appendix, and the request must also be reflected in the budget request. FDA reviews the additional funding annually. Applications that request the supplement without meeting the requirements may be asked to reduce their budget.

Indirect costs

• If you request indirect costs, you must attach a copy of your most recent federal indirect cost rate or F&A agreement to the Research and Related Other Project Information component as line 12, Other Attachments.

• If you have never established an indirect cost rate and have no negotiated federal agreement, a de minimis rate of 10 percent of modified total direct costs is allowed. Modified total direct costs include direct salaries and wages, applicable fringe, materials and supplies, services, travel, and the first $25,000 of each subaward. It excludes equipment, capital expenditures, patient care charges, rental costs, tuition remission, scholarships, participant support costs, and any portion of a subaward above $25,000.

• Foreign and international organizations are funded at a fixed 8 percent of modified total direct costs.

Other budget rules

• Cost sharing is not required.

• Applications requesting multiple years must submit a separate detailed budget and narrative justification for each year.

• You must disclose other funds contributed to the study by any source, including your own company, both before and during the FDA funding period. Provide amounts, sources, and whether the funds are secured. Keep this separate from the FDA request justification.

• No award funds may pay any individual at a salary rate above Executive Level II of the Federal Executive Pay Scale.

• Awards provide one year of support with three additional recommended years contingent on annual appropriations, availability of funds, and satisfactory performance. Continuation also depends on enrollment progress, adequate product supply, and compliance with IND or IDE regulatory requirements.

Timeline and Key Dates

Recurring annual cycle

• Optional Letter of Intent: September 21, 2026, then September 20, 2027

• New application due dates: October 20, 2026, then October 19, 2027, both by 11:59 PM Eastern Time

• Resubmission-only due dates: May 18, 2027, then May 16, 2028

• Scientific merit review, new applications: February and March of 2027 and 2028

• Scientific merit review, resubmissions: June of 2027 and 2028

• Earliest project start date: July 2026 for the first cycle, with later cycles following the same pattern

• Opportunity expiration: May 31, 2028

The deadline before the deadline

The date that actually controls your timeline is not the application due date. It is the IND or IDE submission date.

Your protocol and all other required regulatory documents must be submitted to the applicable FDA IND or IDE review division a minimum of 30 days before the grant application deadline. For the October 20, 2026 cycle, that means the protocol needs to be with the review division on or before September 20, 2026.

The IND must be active, meaning not on clinical hold and not exempted, or the IDE must be approved, for your grant application to qualify for review. Miss this and the application is non-responsive regardless of scientific merit.

A realistic backward-planning schedule for an October cycle

• 6 to 8 months out: Request a preIND or INTERACT meeting if you plan to propose an innovative trial design, or if your regulatory path is unsettled.

• 4 to 6 months out: Confirm SAM.gov, UEI, eRA Commons, and Grants.gov registrations. Registration can take six weeks or longer, and failure to register in time is not an accepted excuse for late submission. Principal investigator eRA Commons accounts alone can take two weeks.

• 3 to 4 months out: Finalize the protocol, lock clinical sites, and begin collecting the three required categories of letters of support.

• 30 days plus before the deadline: Submit the final protocol to your IND or IDE. The version you submit to FDA in the grant application must be the same version submitted to the IND or IDE.

• 3 to 4 weeks out: Complete the Research Strategy, the innovation supplement justification if applicable, and the Data Management and Sharing Plan.

• 1 week out: Submit. Grants.gov and eRA Commons both run error checks, and any errors must be corrected and a changed or corrected application submitted before the deadline. A corrected application filed after the deadline is late, and late applications are not accepted.

Registration checklist

• System for Award Management (SAM) registration, active and renewed at least annually, which generates your Unique Entity Identifier and a CAGE code. Foreign organizations need an NCAGE code instead.

• eRA Commons accounts with at least one Signing Official and at least one Program Director or Principal Investigator. If the same person is both PI and Signing Official, they need two distinct accounts.

• Grants.gov registration, which requires active SAM registration first.

Who Is Eligible

Eligible organizations include:

• Public, state controlled, and private institutions of higher education

• Nonprofits with and without 501(c)(3) status

• Small businesses

• For-profit organizations other than small businesses

• State, county, city, township, and special district governments

• Federally recognized and non-federally recognized tribal governments and Native American tribal organizations

• Federal governments and United States territories or possessions

• Independent school districts, public housing authorities, faith-based and community-based organizations, and regional organizations

• Non-domestic, non-United States entities, and non-domestic components of United States organizations

Principal investigator requirements:

• Any individual with the skills, knowledge, and resources to carry out the research may serve as PD/PI.

• FDA expects an established investigator in the relevant scientific area who can provide both administrative and scientific leadership.

• Every PD/PI must hold an eRA Commons account, and the Commons ID must appear in the Credential field of the Senior/Key Person Profile. Omitting it causes the application to be rejected.

• Multiple PDs/PIs are allowed. One must be designated the Contact PI in item 14 of the SF424 (R&R). Multi-PI applications must include a Multiple PD/PI Leadership Plan covering governance, communication, decision-making on scientific direction, and conflict resolution.

• With multiple institutions, one must be the prime and all others must be funded through subcontracts, with their budgets attached to the Research and Related Subaward Budget Attachment form.

You may submit more than one application, provided each is scientifically distinct. FDA will not accept duplicate or highly overlapping applications under review at the same time.

Application Structure and Required Content

Page limits

FDA does not follow NIH page limitation guidelines or NIH review criteria. For this NOFO, the Research Strategy is limited to 12 pages. A resubmission adds a one-page Introduction addressing the prior Summary Statement.

Required Research Strategy sections

Your Research Strategy must contain these five sections, in this order, because they map directly onto the scored review criteria:

1. Rationale

2. Study Design including Data Quality and Interpretability

3. Inclusion of Patient Input

4. Investigator(s), Infrastructure, and Financial Resources

5. Ability to Advance the Current Field

Required subsections with mandated headings

Three subsections must appear under specific headings. Reviewers look for these headings literally.

• Under Rationale: "Rare Disease Population/Prevalence", documenting that the United States prevalence or incidence meets the rare disease threshold, with calculations and citations.

• Under Rationale: "Support of Product Development", explaining how the study will help support product approval or supply essential data for product development. If you propose multiple products or multiple diseases, describe how you intend to proceed with development, potentially across multiple sponsors.

• Under Study Design: "Study Monitoring Plan", describing your monitoring approach, whether a Data and Safety Monitoring Board, a Study Monitoring Committee, or an Independent Medical Monitor. Name the parties responsible, what will be monitored, the frequency, and the individual and study stopping guidelines.

Required letters of support

Letters of support do not go in the Research Strategy. They are uploaded to line 9 of the PHS 398 Research Plan form. Three categories are required:

1. Study sites. Leaders of the clinical research institutions conducting the study describe site support, resources, study infrastructure, and an estimate of how many patients with the target disease would be eligible.

2. Product availability. Evidence that the product is available to you in the form and quantity the trial needs. A current supplier letter is acceptable. If supply negotiations are underway but not final, submit a letter saying so. Verification of adequate supply is required before an award is made.

3. Patient engagement. Current letters from patients, caregivers, or patient organizations describing early and ongoing engagement in trial design.

Required appendices

• The full final protocol, specifically the version submitted to the IND or IDE

• Informed consent forms, assent forms, and any other information given to subjects, compliant with 21 CFR 50.25

• The innovative and efficient trial approach justification, limited to three pages, if you are requesting additional funding

• For resubmissions, the previous OOPD Summary Statement, with an optional point-by-point rebuttal

Do not use the appendix to get around page limits.

Other required elements

• A Data Management and Sharing Plan is required for all applications regardless of direct cost level, attached in the Other Plan(s) slot.

• At least one human subjects study record using the PHS Human Subjects and Clinical Trials Information form.

• The IND or IDE number and the date the final protocol version was submitted must appear with the project title on the face page of the application.

• If the IND or IDE sponsor is not the listed principal investigator, a letter from the sponsor permitting access to the IND or IDE must be submitted both in the IND or IDE and in the grant application.

How Applications Are Reviewed

Review happens in two stages.

Stage one, responsiveness screening. FDA grants management and program staff review every application against nine program responsiveness criteria. Applications found non-responsive receive notice that they will not be reviewed at all. The criteria include proposing a clinical trial that provides safety or efficacy data for a rare disease, using the generic name of the product, requesting no more than four years, documenting rare disease prevalence, explaining how the trial supports a new indication or labeling change, meeting the IND and IDE requirements under 21 CFR 312 for drugs and biologics or 21 CFR 812 for devices, providing the required appendices and letters, and complying with page and formatting limits.

Only medical foods that do not require premarket approval and devices classified as non-significant risk are exempt from the IND and IDE requirement. Non-significant risk device applicants must include a letter from the FDA Center for Devices and Radiological Health confirming the classification.

Stage two, objective review. Responsive applications go to an FDA Objective Review Committee of subject matter experts, which assigns an overall impact score reflecting the likelihood the project will exert a sustained and powerful influence on the field. FDA experts may be consulted on whether the study will generate data that could contribute to product approval. Funding decisions are made by the Commissioner of Food and Drugs or a designee, based on scientific and technical merit, availability of funds, and relevance to program priorities.

Every application receives a written critique. Appeals of objective review are not accepted for this NOFO.

Note that reviewers are told an application does not need to be strong in every category, and that a project which is not innovative in itself may still be essential to advance a field. The relative importance of strengths and weaknesses matters more than the count.

Additional items reviewers assess without separate scores

• Study timeline, including start-up activities, enrollment rate, follow-up, use of existing resources for efficiency, and contingency plans for enrollment shortfalls

• Protections for human subjects, across risk, adequacy of protection, potential benefits, importance of knowledge gained, and data and safety monitoring

• Biohazards

• Resource sharing plans

• Authentication of key biological and chemical resources

• Whether the budget and requested period of support are fully justified and reasonable

Common Reasons Good Science Loses This Grant

• The protocol was not submitted to the IND or IDE division at least 30 days before the deadline, or the IND is on clinical hold or exempted.

• The version of the protocol in the grant application does not match the version submitted to the IND or IDE.

• Budget built as $650,000 in direct costs, with indirect costs stacked on top, blowing the total cost cap.

• Prevalence documented in prose without the mandated "Rare Disease Population/Prevalence" heading, or without calculations and citations.

• Patient engagement described as an intention rather than evidenced with letters from patients, caregivers, or patient organizations.

• No letter confirming product availability in the form and quantity the trial requires.

• The innovation supplement requested without a three-page appendix justification meeting the stated design requirements.

• SAM, eRA Commons, or Grants.gov registration incomplete at the deadline, which is never an accepted reason for a late submission.

• Missing eRA Commons ID in the Credential field of the Senior/Key Person Profile, which causes outright rejection.

• Submitting close to the deadline, hitting Grants.gov or eRA Commons errors, and correcting them after 11:59 PM Eastern. Late is late.

Frequently Asked Questions

‍ ‍

What is RFA-FD-25-020?

‍ ‍

RFA-FD-25-020 is a Notice of Funding Opportunity from the FDA Office of Orphan Products Development that funds clinical trials of orphan products in support of a new indication or a change in labeling for a rare disease or condition. It is a reissue of RFA-FD-23-001 and uses the R01 activity code.

‍ ‍

How much money can I get from RFA-FD-25-020?

‍ ‍

Up to $650,000 in total costs per year for up to four years, which is $2.6 million maximum. If you propose a qualifying innovative or efficient trial design and justify it in a three-page appendix, you may request up to an additional $250,000 per year, raising the ceiling to $900,000 per year and $3.6 million across four years. All figures are total costs, meaning direct plus indirect combined.

‍ ‍

When are RFA-FD-25-020 applications due?

‍ ‍

New applications are due October 20, 2026 and October 19, 2027, both by 11:59 PM Eastern Time. Resubmission-only deadlines are May 18, 2027 and May 16, 2028. Optional letters of intent are requested by September 21, 2026 and September 20, 2027. The opportunity expires May 31, 2028. Late applications are not accepted.

‍ ‍

Can a small business or startup apply for RFA-FD-25-020?

‍ ‍

Yes. Small businesses and for-profit organizations are explicitly listed as eligible applicants. Under the previous issue of this opportunity, RFA-FD-23-001, roughly one in five funded projects went to for-profit companies, including Ophirex, Extend Biosciences, Palvella Therapeutics, and Targeted Therapy Technologies. Earlier issues funded companies including DNAtrix and Fibrocell Technologies.

‍ ‍

Is RFA-FD-25-020 an SBIR grant?

‍ ‍

No. This is an R01 research project grant, not an SBIR or STTR award. That means none of the SBIR eligibility restrictions apply. There is no small business size standard, no requirement that the principal investigator be primarily employed by the applicant company, no United States ownership percentage test, and no Phase I prerequisite. Companies of any size may apply.

‍ ‍

Do I need an active IND or IDE to apply?

‍ ‍

In almost all cases, yes. The protocol and all other required documents must be submitted to the applicable FDA IND or IDE review division at least 30 days before the grant application deadline. The IND must be active, meaning not on clinical hold and not exempted, or the IDE must be approved, for the application to qualify for review. The only exceptions are medical foods that do not require premarket approval and medical devices classified as non-significant risk, which need a letter from the Center for Devices and Radiological Health confirming the classification.

‍ ‍

What counts as a rare disease for this grant?

‍ ‍

For chronic diseases, a prevalence of fewer than 200,000 people in the United States. For acute diseases lasting less than one year, an annual incidence of fewer than 200,000 per year. Diagnostics and vaccines qualify only if the United States population receiving them is fewer than 200,000 people per year. Orphan subsets of non-rare diseases may qualify if a product characteristic such as mechanism of action or toxicity profile justifies limiting use to that subset.

‍ ‍

Which clinical trial phases are eligible?

‍ ‍

All of them. RFA-FD-25-020 supports clinical trials in Phase 1, Phase 2, and Phase 3 of product development, as long as the trial evaluates safety or efficacy in support of a new indication or a change in labeling.

‍ ‍

What kinds of products are eligible?

‍ ‍

Drugs, biologics, medical devices, and medical foods indicated for rare diseases or conditions. Already approved products being studied for a new orphan indication are eligible. Diagnostics and vaccines are eligible under the population limits described above.

‍ ‍

What are the innovative trial designs that unlock extra funding?

‍ ‍

Seamless and adaptive designs that compress trial phases into one continuous trial, plus basket, umbrella, and platform trials that test multiple drugs or multiple diseases on shared infrastructure. Innovative use of data simulation and modeling to study safety and efficacy also qualifies. FDA strongly recommends discussing these approaches with the relevant review division before applying, through a preIND or INTERACT meeting.

‍ ‍

Is cost sharing or matching required?

‍ ‍

No. RFA-FD-25-020 does not require cost sharing. You must still disclose other funds contributed to the study from any source, including your own company, with amounts, sources, and whether the funds are secured.

‍ ‍

Can I get indirect costs if my company has no negotiated federal rate?

‍ ‍

Yes. If your organization has never established an indirect cost rate and has no negotiated federal agreement, FDA allows a de minimis rate of 10 percent of modified total direct costs. If you do have a negotiated rate, attach the agreement to the Research and Related Other Project Information component as line 12, Other Attachments. Foreign organizations are funded at a fixed 8 percent.

‍ ‍

How long is the Research Strategy?

‍ ‍

Twelve pages for this NOFO. FDA does not follow NIH page limitation guidelines. Resubmissions add a one-page Introduction addressing the prior Summary Statement.

‍ ‍

Can foreign organizations apply?

‍ ‍

Yes. Non-domestic, non-United States entities are eligible, as are non-domestic components of United States organizations. Foreign components are allowed. Indirect costs for foreign and international organizations are capped at 8 percent of modified total direct costs.

‍ ‍

Can I submit more than one application?

‍ ‍

Yes, provided each application is scientifically distinct. FDA will not accept duplicate or highly overlapping applications under review at the same time, and will not accept a new application submitted before the summary statement issues from an overlapping prior application.

‍ ‍

Can I appeal if my application is not funded?

‍ ‍

No. Appeals of objective review are not accepted for applications submitted under this NOFO. The decision not to award, or to award at a particular funding level, is discretionary and not subject to appeal. You may, however, submit a resubmission application at a resubmission-only deadline, provided your prior application received a numeric score and does not require an IND protocol amendment before resubmission.

‍ ‍

Is this funding dilutive?

‍ ‍

No. This is a federal grant, not an investment. You give up no equity, no board seats, and no intellectual property rights. It is non-dilutive capital that also puts an FDA office in the position of tracking your product toward approval.

‍ ‍

How is FDA review different from NIH review?

‍ ‍

FDA uses its own Objective Review Process rather than NIH peer review, applies its own page limits rather than NIH page limitation guidelines, and applies its own review criteria. Applications are still submitted through Grants.gov and tracked in eRA Commons, and FDA still applies HHS grants policy, which is why the announcement reads like an NIH opportunity in places. When FDA program-specific instructions conflict with the general application guide, follow the FDA instructions.

‍ ‍

Who do I contact at FDA about this opportunity?

‍ ‍

Scientific and programmatic questions go to Katherine Needleman, Director of the Orphan Products Grants Program at OOPD, at katherine.needleman@fda.hhs.gov or 301-796-8660. Letters of intent go to OOPD_CTGrants@fda.hhs.gov. Peer review and grants management questions go to Patrick Johnson at the FDA Office of Acquisitions and Grants Services, at Patrick.Johnson@fda.hhs.gov. FDA encourages applicants to resolve responsiveness questions before submitting.

‍ ‍

What To Do Next

‍ ‍

If you have a rare disease product with a protocol at or near IND or IDE stage, the October cycle is winnable and the competition is smaller than founders assume. The gating item is regulatory, not scientific: the protocol has to be with the FDA review division 30 days before the application deadline.

‍ ‍

Where most companies lose this grant is not the science. It is the responsiveness screen, the total cost math, the patient engagement evidence, and the letters of support. Those are all solvable with enough runway.

‍ ‍

BW&CO helps deep tech, biotech, and medtech companies win non-dilutive federal funding, with more than $350 million in funding secured for clients to date. If you are evaluating RFA-FD-25-020, we can assess fit against your regulatory timeline and build the application strategy around it.

NIH Blueprint MedTech Translator (PAR-25-383): The Complete Startup Guide to the UG3/UH3 Medical Device Funding Opportunity

What is the NIH Blueprint MedTech Translator program?

The NIH Blueprint MedTech Translator (PAR-25-383) is a milestone-driven UG3/UH3 cooperative agreement that funds medical device companies and academic innovators to take a novel device from late preclinical development through FDA regulatory clearance to conduct a clinical study, and then through that first clinical study in humans. It is one of the few federal programs that pays for the expensive, unglamorous middle of device development: GLP large animal safety testing, design verification and validation, biocompatibility, cybersecurity, quality systems, IDE preparation, and the first-in-human trial itself.

Two things make it unusual. First, application budgets are not capped. Second, NIH pays a network of contract research organizations and expert consultants directly, outside your budget, so a startup gets prototyping, bench testing, animal studies, regulatory consulting, reimbursement strategy, IP counsel, and clinical trial support at no cost to the award.

The funding is non-dilutive. You keep your equity and you keep your intellectual property.

Next application deadline: September 28, 2026. Subsequent deadlines run through January 28, 2028.

Blueprint MedTech Translator at a glance

‍ ‍

Here are the core facts a founder needs before deciding whether to pursue this opportunity.

‍ ‍

• Funding Opportunity Number: PAR-25-383

• Title: Blueprint MedTech Translator (UG3/UH3, Clinical Trial Optional)

• Agency: National Institutes of Health, Department of Health and Human Services

• Activity code: UG3/UH3 Exploratory/Developmental Phased Award Cooperative Agreement

• Announcement type: Reissue of PAR-21-315

• Posted: June 17, 2025

• Expiration: January 29, 2028

• Award budget: not limited, but must reflect the actual needs of the project

• Cost sharing: not required

• Project period: UG3 phase up to four years, UH3 phase up to four years, five years total maximum

• Application types allowed: New, Resubmission, Revision

• Clinical trial: Optional at the UG3 stage, required in the UH3 stage

• Letter of intent: encouraged, not required

• Assistance Listing Numbers: 93.853, 93.372, 93.213, 93.279, 93.866, 93.273, 93.286, 93.242, 93.865, 93.121, 93.867

• Program email: Blueprint-MedTech@nih.gov

‍ ‍

Which NIH Institutes and Centers participate in Blueprint MedTech?

‍ ‍

Ten Institutes and Centers participate, and your device must address a disease or disorder within the mission of at least one of them. The Office of Behavioral and Social Sciences Research may co-fund awards.

‍ ‍

• Brain Research Through Advancing Innovative Neurotechnologies® (BRAIN) Initiative

  • There is a need to help transition BRAIN Initiative-relevant technologies from early device development to first-in-human studies. Projects that fit the following categories can be submitted through the Blueprint MedTech Program. BRAIN will support the following efforts coming into the BP MedTech UG3/UH3 funding opportunity:

  • Projects developing novel invasive neurostimulation devices for the human central nervous system (CNS).

  • Projects developing novel invasive brain recording devices for the human CNS.

  • Projects developing novel non-invasive brain stimulation devices for the human CNS. These devices should aim to achieve brain stimulation resolution of sub-millimeter at the cortical surface and depth. These approaches may incorporate electromagnetic, mechanical, or combination biological and device means (e.g., optogenetics).

• National Center for Medical Rehabilitation Research (NCMRR)

  • The National Center for Medical Rehabilitation Research within NICHD supports assistive and rehabilitation technology to improve the function of people with physical disabilities. NICHD will only accept applications related to the mission of the National Center for Medical Rehabilitation Research.

• Helping to End Addiction Long-term (HEAL) Initiative

  • Through Notice of Special Interest NOT-NS-24-075, the NIH HEAL Initiative encourages the development and translation of novel neurotechnologies, funded through the Helping to End Addiction Long-term (HEAL) Initiative and overseen by the NIH Blueprint MedTech program. Academic institutions and Small Business Concerns (SBCs) are encouraged to submit grant applications that propose non-clinical development and validation activities for subsequent clinical feasibility studies of medical devices for the diagnosis and treatment of pain and opioid use disorder (OUD). Applications supporting the development and translation of groundbreaking neurotechnologies that fit within the mission of the HEAL Initiative are encouraged.

• National Center for Complementary and Integrative Health (NCCIH)

  • The National Center for Complementary and Integrative Health (NCCIH) supports the development and validation of technologies that can facilitate the integration of complementary and integrative health approaches to enhance diagnosis, prevention, or treatment of diseases and/or associated symptoms, or promotion of well-being and whole person health relevant to the nervous and neuromuscular systems. In addition, NCCIH supports the integration of technologies with multisystem studies to understand the connections and interactions across systems involving the brain and the rest of the nervous system such as interoception, and/or the impact of multi-component interventions on multisystem connections and interactions in pre-clinical models or human subjects. NCCIH will not support clinical efficacy studies or pivotal trials of an intervention.

  • Complementary health approaches include a broad range of practices and interventions that are not typically part of conventional medical care. They can be classified by their primary therapeutic input, including nutritional (e.g., special diets, dietary supplements, herbs, probiotics, and microbial-based therapies), psychological (e.g., meditation, hypnosis, music-based interventions, relaxation therapies), physical (e.g., acupuncture, massage, chiropractic manipulation, other force-based manipulations, or devices related to these approaches), or a combination of psychological and physical (e.g., yoga, tai chi, dance therapies, some forms of art therapy such as music-based interventions).

• National Eye Institute (NEI)

  • The National Eye Institute is requesting applications for the development of FDA Class III medical devices, as well as invasive ocular implants and prosthetics (retinal or cortical) that can stimulate retinal or cortical neurons to produce visual percepts. NEI is not interested in projects focused on developing diagnostic/imaging devices or assistive devices through this program.

• National Institute of Biomedical Imaging and Bioengineering (NIBIB)

  • The mission of the National Institute of Biomedical Imaging and Bioengineering (NIBIB) is to transform, through technology development, our understanding of disease and its prevention, detection, diagnosis, and treatment. NIBIB may support the development of broadly applicable products, where the disease or organ being targeted is used as an initial model and could be adapted to other indications in the future. Before contacting NIBIB, applicants should first discuss the initial target with the Institute and/or Center on this page that is most relevant to the disease(s) being addressed by the proposed product.

• National Institute of Dental and Craniofacial Research (NIDCR)

  • Development of technologies for oral somatosensory or autonomic nerve stimulation to enable diagnosis and/or treatment of motor and sensory conditions, such as bruxism, sleep apnea, temporomandibular/facial pain, swallowing reflex, salivary gland production, and other dental, oral, and craniofacial related conditions and disorders related to the nervous system. These technologies can include the integration of intra- and extra-oral sensors and relevant treatment delivery mechanisms controlled by software systems that allow capture, analysis and display of target biosignatures including but not limited to neural activity.

  • Biofeedback & multimodal neurofeedback technologies for treatment of facial nerve disorders, as well as neurological (e.g., trigeminal neuralgia, peripheral neuropathy associated with Sjogren’s syndrome, burning mouth syndrome) and non-neurological (e.g., vascular/muscular, immune) facial pain. These technologies can include wearable and embeddable devices as well as virtual or augmented reality technology to address acute and chronic conditions.

  • Development, validation and testing of novel technologies to promote prevention and treatment of orofacial and craniofacial nerve injuries, including nerve regeneration.

  • Development, validation and testing of technologies that improve the accuracy and validity of dental, oral or craniofacial clinical pain measurements.

• National Institute of Mental Health (NIMH)

  • NIMH is specifically interested in novel brain stimulation/modulation technologies (invasive or noninvasive) for use in the treatment of psychiatric disorders, or in targeting specific domains of clinical functioning across psychiatric disorders, when appropriate (see RDOC). Devices capable of both recording and stimulating neural activity, with the ability for closed-loop control are also of interest (including synchronizing dense behavioral quantification with neural data); these devices should be able to demonstrate clear capability to record oscillations of interest to mental health applications. Devices can target specific age ranges, including vulnerable populations (pediatric, geriatric). Note: Animal studies to assess “efficacy” must follow NIMH criteria. Please contact NIMH staff above to ensure your project fits NIMH priorities, prior to application submission.

• Office of Behavioral and Social Sciences Research (OBSSR)

• National Institute of Neurological Disorders and Stroke (NINDS)

• National Institute on Aging (NIA)

  • NIA, as the primary federal agency for aging and Alzheimer’s Disease and related dementias (AD/ADRD) research, supports the development and application of innovative technology for early diagnosis and treatment of age-related disorders and AD/ADRD.

• National Institute on Alcohol Abuse and Alcoholism (NIAAA)

  • NIAAA’s mission is to generate and disseminate fundamental knowledge about the adverse effects of alcohol on health and well-being and to apply that knowledge to improve diagnosis, prevention, and treatment of alcohol-related problems, including alcohol use disorder (AUD), across the life span. NIAAA is interested in wearable devices that can monitor blood alcohol concentration in real time, non-invasive methods for the treatment of fetal alcohol spectrum disorders (FASD) in children and adults, and in the treatment of AUD.

• National Institute on Drug Abuse (NIDA)

  • NIDA will support applications aiming to develop novel medical devices intended for use in the diagnosis of, or in the cure, mitigation, treatment, or prevention of Substance Use Disorder (e.g., Opioid Use Disorder, Stimulant Use Disorder). See the NIDA Mission for additional details.

‍ ‍

Projects may also fall under the NIH BRAIN Initiative (Brain Research through Advancing Innovative Neurotechnologies) or the HEAL Initiative (Helping to End Addiction Long-term). A Notice of Special Interest, NOT-NS-24-075, specifically invites HEAL-aligned diagnostic and therapeutic device applications through this NOFO.

‍ ‍

Each participating Institute publishes its own interest statement with additional requirements, clinical study limitations, and budget guidance. Reading the interest statement for your target Institute before you write anything is not optional in practice. Two applications with identical technology can succeed or fail on Institute fit alone.

‍ ‍

How much funding can a startup receive from Blueprint MedTech Translator?

‍ ‍

There is no published budget cap. NIH states that application budgets are not limited but need to reflect the actual needs of the proposed project, and that applicants should propose a budget that is reasonable and appropriate for completion of the research.

‍ ‍

That freedom comes with four practical rules that shape every Blueprint MedTech budget.

‍ ‍

Rule one: your budget covers only your own work. Application budgets should only cover work performed by the Program Director or Principal Investigator and their staff. NIH pays Blueprint MedTech contractors and consultants directly for their work, so those expenses must not appear in your budget. This is the single most common budgeting error on this NOFO. Startups accustomed to SBIR budgeting will instinctively line-item a CRO for large animal work or a regulatory consultant for the pre-submission, and both belong outside the budget here.

‍ ‍

Rule two: requests of $500,000 or more in direct costs in any single year require advance permission. If you plan to request $500,000 or more in direct costs in any year, excluding consortium facilities and administrative costs, you must contact a Scientific or Research Contact at least six weeks before submitting and follow NIH policy on acceptance for review of applications requesting $500,000 or more. Skipping this step can cost you the cycle.

‍ ‍

Rule three: funding may be throttled to $100,000 until FDA weighs in. Applicants who do not already have sufficiently relevant FDA feedback covering all planned activities will be expected to obtain it as the first milestone of the award. Until FDA feedback is received and is consistent with the likely success of the regulatory path to market and the overall device development plan, funding may be restricted to a maximum of $100,000 in direct costs. If FDA feedback contradicts the plan in the application, program staff will evaluate the concerns and the change of scope required, and any remaining funds from the original award will not be released.

‍ ‍

Rule four: budgets are negotiated, not simply awarded. As a cooperative agreement, milestones and budget are negotiated with NIH program staff before award, and the budget for the UH3 clinical phase is renegotiated at the transition point.

‍ ‍

Because Institute-specific budget expectations vary widely, contacting the program officer at your target Institute is the only reliable way to calibrate the number.

‍ ‍

What free resources does the Blueprint MedTech program provide?

‍ ‍

This is the part founders consistently undervalue. Beyond the cash award, Blueprint MedTech participants get streamlined access to NIH-funded service providers and contract research organizations that NIH pays for directly. The program provides:

‍ ‍

• Design optimization, prototype development, and pilot-scale manufacturing

• Bench and safety testing

• Biocompatibility, sterilization, and large animal testing

• Clinical study advising and clinical trial support, including medical monitoring

• Commercialization planning and business development

• Regulatory, quality system, and reimbursement support

• Legal support and intellectual property protection

• Access to industry expert mentors and meetings with an external oversight committee

• Planning resources for concept development, team building, and needs assessment

‍ ‍

For a seed-stage medtech company, the in-kind value of GLP large animal safety studies, biocompatibility panels, and regulatory consulting can rival or exceed the cash award.

‍ ‍

Applicants are required to submit a Resource Checklist attachment identifying which of these resources they intend to use. NIH encourages a specific statement along these lines: "If selected for funding, we expect that the following resources will be made available to this project by the Blueprint MedTech program. Since the program will provide these resources at no cost, this application does not request any labor or budget associated with these resources."

‍ ‍

What is NIH actually looking for in a Blueprint MedTech application?

‍ ‍

NIH is looking for a device that is nearly finished, aimed at a real clinical gap, backed by real data, and blocked mainly by the cost of regulatory-grade testing and a first clinical study.

‍ ‍

More precisely, the program wants novel medical device technologies that advance patient care toward new or improved therapeutics or diagnostics that are safe and effective. Responsive applications propose devices expected to be regulated by the FDA that present first-of-its-kind technologies, new safety questions, or new regulatory questions. Applications may also refine existing technologies toward a new intended use or use in a novel setting, for example translating a neuromodulation device approved only for healthcare settings into a home-use device.

‍ ‍

Expected regulatory pathway

‍ ‍

Proposed devices and indications will likely follow the De Novo or Premarket Approval (PMA) pathways. Devices that fit an existing 510(k) pathway may still be accepted, but only if the application demonstrates clear clinical and technological innovation beyond the state of the art of existing FDA-cleared predicates. Such devices should reasonably be expected to provide new clinically meaningful diagnostic or therapeutic options, or to improve the benefit-risk profile of a treatment or diagnostic through substantial safety innovations.

‍ ‍

Device maturity requirements

‍ ‍

Devices within scope of this program must meet at least one of three conditions:

‍ ‍

1. The device is very close to the final system and is manufactured using very close to the same manufacturing process as the device that will be marketed or studied in a larger clinical trial after this project, or

2. The device has received Pre-Submission feedback from the FDA, or

3. The device requires early feasibility clinical data to inform the final device design or manufacturing processes.

‍ ‍

Entry criteria

‍ ‍

For entry into the program, projects should have all three of the following:

‍ ‍

• Comprehensive supporting data based on bench, in vitro, and in vivo models representative of the intended patient population and indication

• One or more clinically meaningful device outcome measures identified with input from key stakeholders including clinicians, patients, and caregivers, supported by literature

• A compelling case for a successful IDE submission for a Significant Risk study, or IRB approval for a Non-Significant Risk study, by the end of the UG3 phase

‍ ‍

For novel devices, proof-of-concept data on device function is required, obtained using a prototype close to the final device design anticipated for clinical testing, ideally tested in an in vivo animal model representative of the intended patient population. For first-in-human studies, preliminary human data is not required.

‍ ‍

A note on market size

‍ ‍

NIH explicitly states that the market for these device categories may be small compared with other markets, and that applications should not be penalized for a comparatively smaller market provided the market is sustainable. NIH supports research for both rare and high incidence disorders within its mission. This is a meaningful opening for rare disease device companies that struggle to raise venture capital on total addressable market alone.

‍ ‍

How does the UG3 and UH3 phased structure work?

‍ ‍

Every project must have two phases, and every project starts in the UG3 phase. The UH3 phase is not guaranteed. Transition happens only after NIH administrative review.

‍ ‍

UG3 phase: get to an IDE or IRB approval

‍ ‍

The UG3 phase supports the translational device work needed to obtain an IDE and IRB approval for a Significant Risk clinical study, or IRB approval for a Non-Significant Risk study. Duration depends on project maturity at entry and the specific indication, and ranges from one to four years.

‍ ‍

Activities appropriate to the UG3 phase include:

‍ ‍

• Non-GLP animal studies to develop surgical techniques, optimize therapeutic or diagnostic parameters, and refine device design ahead of GLP testing

• Bench-top and animal testing to demonstrate compliance with FDA Recognized Standards

• GLP-compliant large animal safety testing of an implanted device

• Activities to become current Good Manufacturing Practice (cGMP) compliant

• Activities to bring development under Design Control and Quality Systems

• Usability and acceptability studies

• Device, software, firmware, and cybersecurity design verification and validation

• Development of packaging, connectors, and accessories needed for translation

• Regulatory activities including FDA pre-submission meetings, IDE submission, Humanitarian Device Exemption, Request for Risk Designation, 513(g) submission, and Breakthrough Device Designation

‍ ‍

UH3 phase: run the clinical study

‍ ‍

The UH3 phase supports a clinical study leading to one of three outcomes: a marketing application, if the study is sufficiently powered to demonstrate safety and effectiveness for regulatory approval; a larger clinical study that will lead to a marketing application; or use of the clinical experience to inform device design decisions. The UH3 phase can last up to four years.

‍ ‍

The clinical study must provide information about device function or final design that cannot practically be obtained through additional bench or animal work, because of the novelty of the device or its intended use.

‍ ‍

Activities appropriate to the UH3 phase include:

‍ ‍

• Optimization of device design with respect to human functional anatomy

• Identification of the simplest, most reliable, and most cost-effective device configuration for advanced clinical studies and eventual market approval

• Studies of key physiological variables that may affect device function in humans

• Initial device safety assessments, but only in conjunction with obtaining enabling data about device design or function

‍ ‍

What determines whether you transition from UG3 to UH3?

‍ ‍

Program staff conduct an administrative review, with possible input from independent consultants. The decision rests on:

‍ ‍

• Successful achievement of the defined UG3 milestones

• The competitive landscape

• Programmatic priorities and current portfolio balance

• For Significant Risk studies, documentation of final or conditional IDE approval from FDA

• IRB approvals

• Submission of the final clinical protocol and supporting documents to NIH for administrative review, and NIH notification of approval

• Agreement on updated timeline, milestones, and budget for the clinical study

• Availability of funds

‍ ‍

NIH is direct about the implication: expectations align with industry norms for advancing devices through the development pipeline, and an inherent rate of attrition is possible within this program. Not every UG3 award becomes a UH3 award. Build your company plan accordingly.

‍ ‍

Why milestones decide the outcome of a Blueprint MedTech award

‍ ‍

Blueprint MedTech is a milestone-driven cooperative agreement, which means milestones are not a formality in the application. They are the operating contract for the award.

‍ ‍

Each Specific Aim in the application should have at least one milestone associated with it. Each milestone should tie to tangible deliverables that are specific, measurable, achievable, relevant, and time-bound. NIH treats milestones as go or no-go decision points where significant uncertainty for the project is resolved. Applicants are advised to include aims, milestones, and deliverables addressing both technical and commercial feasibility.

‍ ‍

Two milestones are effectively mandatory in Year 1:

‍ ‍

• For projects that need non-clinical testing to support an IDE, an FDA pre-submission meeting with NIH program staff in attendance must be a Year 1 milestone. FDA feedback from that meeting must clearly indicate that the proposed non-clinical testing plan is sufficient to support a successful IDE submission by the end of the UG3 phase.

• For projects requiring non-clinical testing to support an IRB Non-Significant Risk designation, preliminary communication with the IRB about what non-clinical testing will be necessary must be a Year 1 milestone.

‍ ‍

After award, NIH program staff evaluate progress toward milestones every year and recommend whether further funds should be released. If a project does not meet its milestones, funding may be discontinued. Continued funding also depends on the overall robustness of the entire data package, overall progress, portfolio balance and program priorities, the competitive landscape, and availability of funds.

‍ ‍

Milestones are negotiated with NIH program staff before award and are written into the Notice of Award. In rare, well-justified cases, future-year milestones may be renegotiated based on data obtained during the previous year.

‍ ‍

Blueprint MedTech Translator deadlines and timeline

‍ ‍

Applications are due by 5:00 PM local time of the applicant organization. When a due date falls on a weekend or federal holiday, the deadline moves automatically to the next business day.

‍ ‍

Upcoming due dates and review cycles

‍ ‍

September 28, 2026 submission. Scientific merit review March 2027. Advisory Council review May 2027. Earliest project start July 2027.

‍ ‍

January 28, 2027 submission. Scientific merit review July 2027. Advisory Council review October 2027. Earliest project start December 2027.

‍ ‍

May 28, 2027 submission. Scientific merit review November 2027. Advisory Council review January 2028. Earliest project start April 2028.

‍ ‍

September 28, 2027 submission. Scientific merit review March 2028. Advisory Council review May 2028. Earliest project start July 2028.

‍ ‍

January 28, 2028 submission. Scientific merit review July 2028. Advisory Council review October 2028. Earliest project start December 2028. This is the final due date before the NOFO expires on January 29, 2028.

‍ ‍

The same dates apply to new, resubmission, and revision applications. There are no AIDS-related deadlines for this opportunity.

‍ ‍

The timeline you should actually plan against

‍ ‍

Count backward from the deadline, not forward from today.

‍ ‍

• Twelve weeks before the due date: contact NIH program staff at your target Institute. NIH states that when possible, applicants should contact program staff at least twelve weeks before a receipt date. Early contact is how you learn whether your indication fits, what the Institute expects on clinical study design, and what budget range is realistic.

• Six weeks before the due date: if you are requesting $500,000 or more in direct costs in any year, this is your hard deadline for contacting a Scientific or Research Contact.

• Six weeks or more before the due date: begin System for Award Management registration if you are not already registered. NIH warns that registration can take six weeks or more, and that failure to complete registrations in advance is not a valid reason for late submission.

• Two weeks before the due date: eRA Commons accounts can take up to two weeks to obtain. Every Program Director or Principal Investigator needs one, and their eRA Commons ID must appear in the Credential field of the Senior/Key Person Profile form.

• Several days before the due date: submit early. Errors found during the Grants.gov and eRA Commons validation process must be corrected and a changed or corrected application resubmitted on or before the due date and time.

‍ ‍

Add roughly nine to ten months from submission to earliest award start. A September 2026 submission that succeeds starts in July 2027.

‍ ‍

Who is eligible to apply for Blueprint MedTech Translator?

‍ ‍

Eligibility is broad, and startups are explicitly welcome. Individuals, institutions, and businesses developing their own devices, or that already have established collaborations with device manufacturers, may apply directly.

‍ ‍

Eligible organizations include:

‍ ‍

• Higher education institutions, both public and private

• Nonprofits with and without 501(c)(3) status

• For-profit organizations, including small businesses

• Local, state, county, city, township, and special district governments

• Federally recognized and other Native American tribal governments and organizations

• Eligible agencies of the federal government

• U.S. territories and possessions

• Independent school districts, public housing authorities, faith-based and community-based organizations, and regional organizations

• Non-domestic (non-U.S.) entities, including foreign organizations and foreign components of U.S. organizations

‍ ‍

Foreign components as defined in the NIH Grants Policy Statement are allowed.

‍ ‍

What this means for a venture-backed startup

‍ ‍

Three points matter for founders comparing this to SBIR and STTR.

‍ ‍

First, this is not an SBIR or STTR program. The SBIR ownership and size restrictions do not apply here, so majority venture-owned and larger private companies that have aged out of SBIR eligibility can still compete.

‍ ‍

Second, cost sharing is not required.

‍ ‍

Third, an organization may submit more than one application as long as each is scientifically distinct. NIH will not accept duplicate or highly overlapping applications under review at the same time.

‍ ‍

Required registrations

‍ ‍

All registrations must be complete before the application is submitted:

‍ ‍

• System for Award Management (SAM), which must be renewed at least annually and which assigns a CAGE code for domestic organizations

• NATO Commercial and Government Entity (NCAGE) code for foreign organizations, in lieu of a CAGE code

• Unique Entity Identifier (UEI), issued through the SAM registration process, which must match the identifier in eRA Commons

• eRA Commons, requiring at least one Signing Official and at least one Program Director or Principal Investigator account. If the PI is also the Signing Official, two distinct accounts are required.

• Grants.gov, which requires an active SAM registration first

‍ ‍

Applications may be submitted through NIH ASSIST, Grants.gov Workspace, or an institutional system-to-system solution.

‍ ‍

What attachments does a Blueprint MedTech application require?

‍ ‍

This NOFO has an unusually heavy set of required attachments with strict page limits. Missing or oversized attachments cause withdrawal without review. Treat this list as a compliance checklist.

‍ ‍

Required attachments

‍ ‍

• Needs Assessment, three pages maximum, filed as "Needs Assessment.pdf"

• IP Strategy, three pages maximum, filed as "IP Strategy.pdf"

• Gantt Chart, one page maximum, filed as "Gantt.pdf"

• Long-term Care Plan for Patients, three pages maximum, filed as "Long-term Care.pdf"

• Resource Checklist, three pages maximum, filed as "Resource Checklist.pdf"

• UG3 Milestone Plan, included in the Research Strategy

• UH3 Milestone Plan, attached at Section 2.7 Study Timeline in the PHS Human Subjects and Clinical Trials Information form

• Team Management Plan, two pages maximum, attached at Section 3.5

• Data Safety and Monitoring Plan, attached at Section 3.3

• Data Management and Sharing Plan, required regardless of direct costs requested

‍ ‍

Optional attachments with enforced page limits

‍ ‍

Exceeding these limits also causes withdrawal.

‍ ‍

• Schematics, two pages maximum, filed as "Schematics.pdf"

• IRB Communications, five pages maximum, filed as "IRB Communications.pdf"

• FDA Communications, ten pages maximum including a one-page summary, submitted only in Section 4.5.a or as post-submission material. Pre-submissions themselves should not be included.

‍ ‍

What goes in the harder attachments

‍ ‍

Needs Assessment. Establish performance requirements with clear, quantifiable metrics. Identify significant issues faced by patients, clinicians, caregivers, and customers. Critically evaluate primary or secondary data used to identify deficiencies in current capabilities. Describe the beneficiaries and how their needs were identified. Distinguish wants from needs. Describe how finite resources will be deployed. Identify human factors and ergonomics incorporated into the design.

‍ ‍

IP Strategy. Describe the IP landscape around your device, including known constraints such as restrictions under transfer or sharing agreements, your own prior filings and publications, and similar patented or marketed technologies. If you are using technology your institution does not own, address anything that could constrain your freedom to operate, and include a letter from the IP owner stating whether they will provide the technology, any limits on studies performed with it, agreement on public disclosure of results including negative results, and whether an agreement is already in place. Give filing dates, patent types, application status, and USPTO links for relevant filings, and describe future filing plans. Academic applicants should prepare this with their technology transfer office.

‍ ‍

Long-term Care Plan for Patients. Describe anticipated care needs of participants after the trial ends that relate to their participation, such as continued device access, device maintenance, and explant. Consider post-trial scenarios including device or trial failure, success, regulatory approval options, and a manufacturer decision to discontinue the product. Then describe the actual plan, which may include explant of indwelling devices, surgical removal of batteries and capping exposed metals from leads and IS-1 connectors, manufacturer-supported device maintenance for responders, or manufacturer support for compassionate use exemption filings. Address post-trial obligations including hardware and software maintenance and device-related medical expenses.

‍ ‍

Team Management Plan. Define team structure and relationships, illustrated with an organizational chart. Describe governance, communication plans, decision processes for scientific direction and intellectual property, and conflict resolution procedures. Address authorship policies and decisions about what to publish, consistent with the interests of commercial partners. The plan must establish and name a Scientific Steering Group of senior and key team members that meets regularly. If organizations are partnering, the Scientific Steering Group must include representatives from each. Technology transfer officials are encouraged to be members.

‍ ‍

Neuroethics section. Within Protection of Human Subjects, describe ethical considerations related to the design and conduct of the study, for example therapeutic misconception where research is ancillary to a clinical procedure or offers no prospect of participant benefit, and the long-term implications of the study, such as psychosocial or legal implications of predictive biomarkers for pre-symptomatic individuals. Reference the Neuroethics Guiding Principles for the NIH BRAIN Initiative.

‍ ‍

Letters of support

‍ ‍

Include letters from consultants, contractors, and collaborators. Academic applicants must include a letter from the technology transfer official managing the project's IP. Multi-institution projects need a letter from each institution clarifying how IP will be shared or managed. Collaborations with private entities need a letter stating whether the entity will provide the device or technology, limits on studies, limits on data sharing, and whether licensing agreements are in place. CRO and CMO letters may summarize test results but should not contain detailed results of all testing, and generally run two pages maximum.

‍ ‍

What makes a Blueprint MedTech application non-responsive?

‍ ‍

Non-responsive applications are withdrawn and never reviewed. There are three categories.

‍ ‍

Activities that make an application non-responsive

‍ ‍

• Animal model development. All in vivo models must be established, characterized, and available to the applicant.

• Projects focused on technologies for augmentation of healthy individuals

• Delayed-onset clinical studies

• Device technologies not regulated by the FDA

‍ ‍

Omissions that make an application non-responsive

‍ ‍

• Specific Aims that do not cover activities for both the UG3 and UH3 phases

• Failure to plan a delayed-start clinical study or trial in the UH3 phase, including all required supporting documentation

• Missing any required attachment listed above

• Missing a UH3 Milestone Plan

‍ ‍

Formatting failures that make an application non-responsive

‍ ‍

• Any required or optional attachment that exceeds its page limit

‍ ‍

Note the distinction NIH draws between delayed onset and delayed start. A delayed-start study is one that can be described in full but will not begin immediately, which is exactly what the UH3 phase requires. A delayed-onset study is one that cannot yet be described, and those are not accepted.

‍ ‍

How is a Blueprint MedTech application reviewed?

‍ ‍

Applications are evaluated for scientific and technical merit by an appropriate Scientific Review Group under NIH peer review policy, using the revised NIH review framework that took effect for due dates on or after January 25, 2025.

‍ ‍

Reviewers consider three factors. Factors 1 and 2 each receive a separate factor score, and all three inform the overall impact score.

‍ ‍

Factor 1: Importance of the Research (Significance and Innovation)

‍ ‍

Reviewers assess whether the work addresses an important gap, solves a critical problem, or creates a valuable conceptual or technical advance, and whether it applies novel concepts, methods, or technologies.

‍ ‍

Specific to this NOFO, reviewers evaluate:

‍ ‍

• Whether there is a significant advantage over all existing clinically available approaches for the same indication, regardless of class, including drugs, biologics, and competing devices

• Whether the device reduces a known serious adverse event, a known device failure mode, or a use-related hazard or error, or improves the safety of another device or intervention

• For devices improving on earlier generations, whether the advantages are justified and whether the changes are likely to succeed where the predecessor did not

• Whether proof-of-concept data for a novel device was obtained with a prototype close to the final design

• Whether the device and its capabilities are described in enough detail to judge appropriateness for the proposed clinical study

• Whether the approach, targets, and patient population are justified

• Whether there are adequate plans to engage FDA early

• Whether the Needs Assessment incorporates input from patients, clinicians, and caregivers on device performance requirements, and identifies beneficiaries and their needs

‍ ‍

Factor 2: Rigor and Feasibility (Approach)

‍ ‍

Reviewers assess whether the work will produce unbiased, reproducible, robust data, whether design and controls are sound, whether sample size is sufficient and justified, and whether the studies can be done within the proposed timeframe.

‍ ‍

Specific to this NOFO, reviewers evaluate:

‍ ‍

• Whether the regulatory plan is reasonable in terms of the path to market and FDA data requirements for the applicable standard, meaning reasonable assurance of safety and effectiveness for PMA or substantial equivalence for 510(k)

• Whether the estimated timeline for clinical adoption reflects feasible benchmarks

• Whether and how key stakeholders will be engaged at each step

• Whether the project plan and timeline make an IDE at the end of the UG3 phase, or IRB approval for a Non-Significant Risk study, likely

• Whether neuroethical concerns are adequately addressed

• Whether any large animal safety study uses GLP and the final device design, or whether a clear reason it is unnecessary is provided, such as an FDA communication

• Whether the Long-term Care Plan anticipates key patient needs, is reasonable, and addresses financial liability for injury, device removal, device revision, and management of indwelling devices

• Whether the Gantt chart provides sufficient detail and demonstrates feasible plans

• Whether milestones are timely, robust, and tied to clear quantitative go or no-go criteria

• Whether milestone timelines are realistic, inclusive of necessary steps, and free of unnecessary ones

• Whether milestones reflect planned regulatory requirements such as FDA pre-submission meetings and IDE submission

• Whether potential challenges and solutions are presented, including strategies for enrollment shortfalls

‍ ‍

Factor 3: Expertise and Resources (Investigators and Environment)

‍ ‍

Reviewers assess investigator background and training, the leadership plan for multiple-PI applications, and institutional resources. Specific to this NOFO, reviewers evaluate whether the selection of Blueprint MedTech resources is adequately justified, whether team governance is appropriate, and whether the Scientific Steering Group members are appropriate and constitute an interdisciplinary team.

‍ ‍

Additional considerations

‍ ‍

Reviewers also consider, without scoring, the IP Strategy attachment, including whether IP landscape issues and barriers are addressed, whether known constraints could impede device development, whether filing plans are well described, and whether IP sharing across multiple institutions is adequately addressed. Human subjects protections, vertebrate animals, biohazards, authentication of key resources, and budget and period of support are also considered.

‍ ‍

After peer review

‍ ‍

Applications may undergo a committee process in which only those with the highest merit, generally the top half under review, are discussed and scored. Recommended applications then receive a second level of review by the appropriate national Advisory Council or Board. Funding decisions weigh scientific and technical merit, availability of funds, and relevance to program priorities.

‍ ‍

What does the cooperative agreement mean for your company?

‍ ‍

A cooperative agreement is not a grant you receive and then execute independently. NIH program staff have substantial programmatic involvement beyond normal stewardship. Founders should understand what they are signing up for.

‍ ‍

What you retain

‍ ‍

• Custody of and all rights to the data and technology developed under the award, subject to government rights of access consistent with HHS, PHS, and NIH policy

• Responsibility for defining objectives and approaches, planning, conducting, analyzing, interpreting, publishing, and sharing results

• The right and encouragement to pursue patent protection

‍ ‍

The program strongly encourages recipients and their collaborators to obtain and retain IP developed around the device during the project period, and to identify and foster relationships with licensing and commercialization partners early.

‍ ‍

What NIH expects from you

‍ ‍

• Developing and proposing rigorous milestones

• Progress reports complete enough to include experimental design, assumptions, results, interpretations, and a conclusion on whether milestones were met. If program staff request raw data, you agree to provide it.

• Participation in virtual progress meetings with NIH staff at least twice a year

• Communicating regulatory meeting dates and agendas to NIH program staff and inviting their participation

• Sharing CRO study reports, meeting minutes and data packages, letters, and other FDA communications, and providing IDE or IND numbers and ClinicalTrials.gov registration numbers

• Providing regulatory and clinical documents required for administrative review

• Verifying the clinical study follows Good Clinical Practices and Institute-specific data and safety monitoring guidelines

• Collaborating and communicating effectively with NIH service contractors

‍ ‍

What NIH does

‍ ‍

NIH program staff provide input on milestones and recommend their finalization, assess progress toward milestones, recommend whether further funds should be released, participate with your team in meetings with regulatory agencies, and may consult independent specialists under confidentiality agreements to protect intellectual property. In rare, well-justified cases, program staff may add critical experiments as additional milestones, sometimes with additional NIH funds.

‍ ‍

A Program Officer handles normal stewardship, but the Associate Division Director overseeing the program makes final decisions on project continuation, a second level of approval designed to mitigate perceived bias. Disagreements can be escalated through other Associate Division Directors to the Institute Director. A formal Dispute Resolution Panel process exists for scientific or programmatic disagreements. Final NIH decisions regarding a discontinuation are not appealable.

‍ ‍

Quality and compliance requirements

‍ ‍

Use of Design Control and Quality Systems processes to the degree specified by FDA is required. Intermediate steps such as design reviews, design verification, design validation, and design transfer should appear in annual milestones where appropriate, along with IDE submission. NIH recognizes the required degree varies substantially by device, and encourages applicants to discuss this with FDA and regulatory consultants before submitting so the extent of the requirement is clearly defined and verifiable in the application.

‍ ‍

Applicants should consider Quality System requirements at the IDE stage when planning device development activities, and should follow Institute-specific guidelines and policies for monitoring clinical research when forming a data and safety monitoring plan.

‍ ‍

How to build a competitive Blueprint MedTech application

‍ ‍

Six moves separate funded applications from withdrawn ones.

‍ ‍

Call the program officer first, not last. NIH says twelve weeks before the deadline. This program is a negotiated partnership, and the negotiation starts before you write. Program staff will tell you whether your indication fits their Institute's mission, what clinical study requirements apply, and what budget is realistic. The Institute contact list is published on the Blueprint MedTech website.

‍ ‍

Get FDA feedback before you submit if you possibly can. Pre-submission feedback is encouraged rather than required, but the alternative is a Year 1 milestone and a possible $100,000 funding restriction until FDA responds. Applications that arrive with approved pre-submission minutes showing FDA agreement on the non-clinical testing plan are substantially stronger and start faster.

‍ ‍

Write your milestones like an operating plan, not a research schedule. Every Specific Aim needs at least one milestone. Every milestone needs quantitative go or no-go criteria. Cover technical, regulatory, and commercial feasibility. These become the terms of your award and the basis of every annual funding decision.

‍ ‍

Build the whole application around one Institute's mission and one indication. Your device may have several uses. The application must focus on a disease or disorder within the mission of a participating Institute, and the target patient population and intended use should drive both device design and the proposed clinical activities.

‍ ‍

Treat the attachment checklist as a go or no-go gate. Five required other attachments, two milestone plans, a team management plan, a DSMP, and a data management and sharing plan, each with page limits that are enforced by withdrawal rather than by a request to fix. Assign an owner and a deadline to each one.

‍ ‍

Budget only your own work, and claim the free resources explicitly. Leave NIH-paid contractors and consultants out of the budget, name the Blueprint MedTech resources you will use in the Resource Checklist, and justify why you are not using the ones you skipped.

Frequently asked questions about the Blueprint MedTech Translator (PAR-25-383)

‍ ‍

What is the deadline for PAR-25-383?

‍ ‍

The next application deadline is September 28, 2026. Additional deadlines follow on January 28, 2027, May 28, 2027, September 28, 2027, and January 28, 2028. All applications are due by 5:00 PM local time of the applicant organization. The NOFO expires January 29, 2028.

‍ ‍

How much money can I request from Blueprint MedTech Translator?

‍ ‍

There is no budget cap. NIH states that application budgets are not limited but must reflect the actual needs of the proposed project. If you request $500,000 or more in direct costs in any single year, you must contact a Scientific or Research Contact at least six weeks before submitting and follow NIH policy on acceptance of applications requesting $500,000 or more.

‍ ‍

Can a startup or small business apply to Blueprint MedTech Translator?

‍ ‍

Yes. For-profit organizations, including small businesses, are explicitly eligible. Individuals, institutions, and businesses developing their own devices, or that already have established collaborations with device manufacturers, are welcome to apply directly. Foreign organizations are also eligible.

‍ ‍

Is Blueprint MedTech an SBIR or STTR program?

‍ ‍

No. Blueprint MedTech Translator is a UG3/UH3 cooperative agreement, not an SBIR or STTR award. SBIR ownership and company size restrictions do not apply, so companies that are majority venture-owned or otherwise ineligible for SBIR can compete here. Note that Blueprint MedTech also offers companion SBIR opportunities, so confirm which mechanism fits your company with program staff.

‍ ‍

Do I need FDA feedback before applying?

‍ ‍

Not strictly, but it matters a great deal. Applicants are encouraged, though not required, to consult FDA through a Pre-Submission meeting. If you do not have sufficiently relevant FDA feedback covering all planned activities at the time of application, obtaining it becomes your first milestone, and funding may be restricted to a maximum of $100,000 in direct costs until FDA feedback consistent with your regulatory path and development plan is received.

‍ ‍

How long does a Blueprint MedTech award last?

‍ ‍

The UG3 phase may run up to four years and the UH3 phase may run up to four years, but the total combined project period may not exceed five years. UG3 duration depends on how mature the project is at entry and on the specific indication, and can be as short as one year.

‍ ‍

Is the UH3 clinical phase guaranteed?

‍ ‍

No. All projects start in the UG3 phase. Only UG3 projects that meet defined criteria are eligible to transition after an NIH administrative review that considers milestone achievement, the competitive landscape, programmatic priorities and portfolio balance, IDE and IRB approvals, the final clinical protocol, agreement on updated timeline and budget, and availability of funds. NIH states plainly that an inherent rate of attrition is possible.

‍ ‍

What is the difference between a Significant Risk and Non-Significant Risk study here?

‍ ‍

A Significant Risk study requires an Investigational Device Exemption from FDA before the clinical study can begin, so the UG3 phase must deliver an IDE. A Non-Significant Risk study does not require an IDE, so the UG3 phase must deliver IRB approval instead. Your milestone plan, regulatory milestones, and non-clinical testing plan differ accordingly.

‍ ‍

What kinds of devices are in scope?

‍ ‍

Devices expected to be regulated by FDA that present first-of-its-kind technology, new safety questions, or new regulatory questions, and that address a disease or disorder within the mission of a participating Institute or Center or the BRAIN or HEAL Initiatives. Devices refining existing technology for a new intended use or a novel setting, such as moving a clinic-only neuromodulation device to home use, are also responsive. Expected pathways are De Novo or PMA, with 510(k) devices accepted only when innovation clearly exceeds the state of the art of existing cleared predicates.

‍ ‍

What will make my application be rejected without review?

‍ ‍

Four activity categories are non-responsive: animal model development, technologies for augmentation of healthy individuals, delayed-onset clinical studies, and device technologies not regulated by FDA. Applications are also withdrawn for missing Specific Aims that cover both phases, missing a planned delayed-start UH3 clinical study, missing any required attachment, missing a UH3 Milestone Plan, or exceeding any attachment page limit.

‍ ‍

Do I have to include a clinical trial?

‍ ‍

The NOFO is Clinical Trial Optional at the application stage, but in practice the structure requires a clinical study in the UH3 phase. Applications must include Specific Aims covering both phases and a delayed-start clinical study or trial planned in the UH3 phase with all required supporting documentation.

‍ ‍

What free services does Blueprint MedTech provide, and do they come out of my budget?

‍ ‍

Blueprint MedTech provides design optimization, prototype development and pilot-scale manufacturing, bench and safety testing, biocompatibility and large animal studies, clinical support, business development, regulatory and quality systems support, legal and IP support, and expert consultants. NIH pays these contractors and consultants directly, so those costs must not be included in your application budget. You identify what you plan to use in the required Resource Checklist attachment.

‍ ‍

Who owns the intellectual property?

‍ ‍

You do. Recipients retain custody of and all rights to data and technology developed under the award, subject to government rights of access consistent with HHS, PHS, and NIH policy. The program strongly encourages recipients and collaborators to obtain and retain IP developed around the device, and expects Principal Investigators to work closely with technology transfer officials on royalty agreements, patent filings, and commercialization plans.

‍ ‍

Is cost sharing required?

‍ ‍

No. This NOFO does not require cost sharing as defined in the NIH Grants Policy Statement.

‍ ‍

Can I submit more than one application?

‍ ‍

Yes, provided each application is scientifically distinct. NIH will not accept duplicate or highly overlapping applications under review at the same time, and will not accept a new application submitted before the summary statement issues from an overlapping application under review.

‍ ‍

Is a letter of intent required?

‍ ‍

No. A letter of intent is not required, is not binding, and does not enter into review, but NIH asks prospective applicants to submit one so staff can estimate review workload. Send it to Blueprint-MedTech@nih.gov with the descriptive title, PI names and contact information, other key personnel, participating institutions, and the funding opportunity number and title.

‍ ‍

How long does it take to get funded?

‍ ‍

Roughly nine to ten months from submission to earliest possible start. A September 28, 2026 submission goes to scientific merit review in March 2027, Advisory Council review in May 2027, and has an earliest start date of July 2027.

‍ ‍

Does a small market hurt my application?

‍ ‍

No. NIH states directly that the market for these device types may be small compared with other markets, that applications should not be penalized for a comparatively smaller market provided the market is sustainable, and that NIH supports research for both rare and high incidence disorders within its mission. For rare and ultra-rare diseases where commercialization is challenging, NIH encourages applicants to discuss alternative strategies with Scientific and Research staff.

‍ ‍

How much NIH involvement should I expect after award?

‍ ‍

Substantial. Expect virtual progress meetings with NIH staff at least twice a year, NIH participation in your FDA meetings, sharing of CRO reports and FDA communications with program staff, annual milestone evaluations that determine whether further funds are released, and the possibility that program staff request raw data. Milestones are negotiated before award and written into the Notice of Award.

‍ ‍

What registrations do I need and how early should I start?

‍ ‍

You need active SAM, UEI, eRA Commons, and Grants.gov registrations, plus an NCAGE code if you are a foreign organization. NIH warns that SAM registration can take six weeks or more and eRA Commons accounts up to two weeks. All registrations must be complete before submission, and incomplete registration is not a valid excuse for a late application.

‍ ‍

Who do I contact at NIH about Blueprint MedTech?

‍ ‍

The program email is Blueprint-MedTech@nih.gov. Institute-specific scientific contacts include Nick Langhals at NINDS, Leonardo Angelone at NIDA, Erin Burke Quinlan at NCCIH, Tony Douglas Gover and Paekgyu Lee at NEI, Elizabeth Powell at NIAAA, Eunyoung Kim at NIMH, Michael Wolfson at NIBIB, and Melissa Ghim at NIDCR. NIH recommends contacting program staff at least twelve weeks before a receipt date.

‍ ‍

Key NIH contacts for PAR-25-383

‍ ‍

Program email for all inquiries and letters of intent: Blueprint-MedTech@nih.gov

‍ ‍

Scientific and research contacts

‍ ‍

• Nick Langhals, PhD, NINDS, 301-496-1779, Blueprint-MedTech@nih.gov

• Leonardo Angelone, PhD, NIDA, Blueprint-MedTech@nih.gov

• Erin Burke Quinlan, PhD, NCCIH, 301-451-0636, erin.quinlan@nih.gov

• Tony Douglas Gover, NEI, 301-529-7370, tony.gover@nih.gov

• Paekgyu Lee, NEI, 301-435-8164, paek.lee@nih.gov

• Elizabeth Powell, PhD, NIAAA, 301-443-0786, elizabeth.powell3@nih.gov

• Eunyoung Kim, PhD, NIMH, 301-496-3513, eunyoung.kim@nih.gov

• Michael Wolfson, NIBIB, 301-451-4778, michael.wolfson@nih.gov

• Melissa M. Ghim, PhD, NIDCR, ghimm@mail.nih.gov

‍ ‍

Application submission support

‍ ‍

• eRA Service Desk, 301-402-7469 or 866-504-9552

• General NIH grants information, GrantsInfo@nih.gov, 301-480-7075

• Grants.gov customer support, 800-518-4726, support@grants.gov

‍ ‍

Is Blueprint MedTech Translator right for your company?

‍ ‍

This program is a strong fit if you have a device that works, data that proves it works, a clear FDA pathway, and a funding gap between your last preclinical result and your first patient. It is a poor fit if your animal model is not yet established, your device is not FDA regulated, your technology targets enhancement of healthy people, or you cannot yet describe the clinical study you intend to run.

‍ ‍

The application is demanding. Between the two milestone plans, five required attachments with hard page limits, a needs assessment grounded in stakeholder input, an IP strategy prepared with counsel, a long-term patient care plan, and a team management plan naming a Scientific Steering Group, this is a substantially heavier lift than a standard R01 or SBIR submission. It also rewards the work: uncapped budgets, free access to CROs and regulatory consultants, and a federal partner with an interest in getting your device to market.

‍ ‍

BW&CO helps deep tech, biotech, and medtech founders win non-dilutive federal funding. We have helped clients secure more than $350 million in funding across NIH, NSF, DoD, NASA, DOE, and ARPA-H. If you are evaluating Blueprint MedTech Translator for the September 28, 2026 deadline or a later cycle, the first step is a mission-fit conversation with the right Institute, and the second is an honest read on whether your data package clears the entry criteria.

NIH Highlighted Topic: Building Health through Multidomain Resilience Research from Molecules to Communities

Highlighted Topic 117 | Participating ICOs: NHLBI, NCCIH, NCI, NIA, NIAAA, NIMHD, OBSSR, ODP, ODS, ORWH, THRO | Posted August 28, 2026 | Expires August 25, 2028 | Apply through the NIH SBIR parent announcement (PA-27-100) or the NIH STTR parent announcement (PA-27-102).

Executive Summary

NIH has designated multidomain resilience research as a formal Highlighted Topic, with eleven Institutes, Centers, and Offices publishing their own areas of interest, spanning cardiopulmonary health, cancer, aging, alcohol use, minority health and health disparities, integrative health, dietary supplements, women's health, autoimmunity, disease prevention, behavioral science, and tribal health.

The framing is a genuine inversion of how most biomedical research is funded. Rather than asking why people get sick, NIH is asking why some people do not get sick despite carrying known risk. NHLBI illustrates it with four cases that make the concept concrete: hypertension without stroke, full recovery after heart valve surgery, preserved lung function despite tobacco exposure, and the interplay of resilience with sickle cell disease exacerbation such as vaso-occlusive crises. Resilience, in NIH's working definition, is a living system's capacity to resist, recover, adapt, or grow from challenges or stressors, tracked over time across interconnected individual, community, and environmental systems.

NIH also says plainly what has been holding the field back: heterogeneous definitions, models, and measures. That diagnosis is the opportunity. The named high-priority research areas are developing and refining resilience measures and metrics, data interoperability, mechanistic understanding of protective and restoring factors distinct from disease-risk reduction, and identifying biomarkers that reflect or predict resilience. Three of those four are measurement and infrastructure problems, which is to say they are product problems.

For a small business, the concentrated openings are validated resilience measurement instruments and digital assessments, biomarker panels that predict recovery capacity rather than disease risk, controlled-perturbation and challenge-recovery testing protocols paired with longitudinal monitoring hardware, multisystem phenotyping analytics, and data interoperability and federated analysis platforms. NIA in particular asks for dynamic resilience measures using controlled perturbations and longitudinal monitoring, plus advanced analytics for multisystem resilience phenotyping, which reads as an instrument-plus-software specification rather than a research question.

There is no dedicated funding and no separate application. A Highlighted Topic is a priority signal, not a Notice of Funding Opportunity. You apply through the standard NIH SBIR or STTR omnibus and compete in the normal pool, and NIH states that applying in a Highlighted Topic area will not affect referral or review. NIMHD states it may dedicate available funds to this topic area and may give special consideration to meritorious applications in it. NCCIH states it may give special consideration. The other participating ICOs make no such statement.

One structural trap to notice immediately. Of the eleven participating ICOs, five do not award grants: OBSSR, ODP, ODS, ORWH, and THRO. Two of those five, ODS and ORWH, published the most commercially concrete interests on the entire page, dietary supplement resilience biomarkers and federated data platforms respectively. Your application still has to land on the mission of one of the six that write checks: NHLBI, NCCIH, NCI, NIA, NIAAA, or NIMHD.

Under the current SBIR parent announcement, standard budget guidelines run up to $323,090 for Phase I and up to $2,153,927 for Phase II, and NIA is approved to exceed both. The next standard receipt dates are September 5, 2026, January 5, 2027, and April 5, 2027, and the topic stays live through August 25, 2028.

A Quick Note on the NIH SBIR and STTR Program

‍ ‍

The NIH, CDC, and FDA SBIR and STTR programs are the largest source of non-dilutive early-stage funding for health, biomedical, and life science technology in the United States. NIH alone sets aside well over a billion dollars a year. Awards are grants, not investments. No equity, no repayment, no board seat.

‍ ‍

The program runs in phases. Phase I funds proof of concept and feasibility. Phase II funds the substantive research and development that turns a validated concept into a product. Fast-Track combines both in one application, and Direct to Phase II lets companies that have already established feasibility skip Phase I. Phase IIB and the Commercialization Readiness Pilot extend funding for late-stage work such as validation, scale-up, and regulatory submissions. Applicants must be for-profit U.S. small businesses with 500 or fewer employees and majority U.S. ownership.

‍ ‍

For the complete breakdown of the NIH SBIR and STTR program, including all budget caps by Institute, clinical trial policies, eligibility mechanics, review criteria, and the full timeline, see our full executive summary here: NIH, CDC and FDA Parent SBIR Grant (PA-27-100).

‍ ‍

Everything below is specific to this Highlighted Topic.

‍ ‍

What Is a Highlighted Topic, and How Is It Different From a Funding Opportunity?

‍ ‍

A Notice of Funding Opportunity (NOFO) is a solicitation. It has an announcement number, its own application package, its own review criteria, and usually its own set-aside funding. You apply to it directly.

‍ ‍

A Highlighted Topic is a published statement of scientific priority maintained centrally by NIH. It has no application package and no guaranteed funding. You cannot apply to it. You apply through a broad opportunity such as the SBIR or STTR parent announcement, and the topic tells you what the participating ICOs want to fund inside their existing budgets.

‍ ‍

NIH is explicit about how this works:

‍ ‍

• Apply through an appropriate parent announcement or other broad NIH opportunity.

• Reach out early to the listed scientific contacts to discuss alignment.

• If an ICO chooses to dedicate funding to a topic, the amount depends on available funds, the number of meritorious applications, and competing priorities.

• Applying in a Highlighted Topic area will not affect NIH referral or review of your application.

‍ ‍

NIH reviews each topic annually for continued alignment and Institutes can post or retire topics at any time, so verify the topic is still live before each cycle you plan to submit in.

‍ ‍

There is no notice number to enter in the Agency Routing Identifier field, unlike the older Notice of Special Interest model. Make the alignment explicit in your cover letter and Specific Aims, and confirm handling with your target Institute's program officer before you submit.

‍ ‍

In this particular topic, the map matters more than usual. Resilience is not a study section. There is no established review culture for it, six different Institutes could plausibly claim the same project, and NIH has openly acknowledged the field lacks harmonized terminology. That combination means the Institute you land at will substantially determine how your application is read.

‍ ‍

What Are They Looking For? A Detailed Overview

‍ ‍

The Stated Purpose

‍ ‍

The topic aims to accelerate rigorous, reproducible, interdisciplinary resilience science to promote health and well-being across the lifespan and across populations. NIH describes resilience mechanisms as operating across scales and domains to maintain health, enabling prevention and recovery from chronic and acute disease despite known risk factors.

‍ ‍

The focus is research on:

‍ ‍

• Protective pathways and their biological mechanisms that maintain physiological function throughout the life course

• Harmonized terminology

• Standardized protocols

• Validated measures and biomarkers

• Implementation science to optimize evidence-based interventions, including lifestyle interventions, across populations

‍ ‍

NIH specifically names children, tribal communities, and groups at risk for health disparities as populations of interest.

‍ ‍

How NIH Defines Resilience

‍ ‍

NIH uses a broad definition: a living system's capacity to resist, recover, adapt, or grow from challenges or stressors, with outcomes tracked over time across interconnected individual, community, and environmental systems. NIH attributes this framing to Brown and colleagues, 2023.

‍ ‍

Those four verbs are not interchangeable and they are worth treating as a menu. Resistance means the stressor lands and nothing breaks. Recovery means function returns to baseline. Adaptation means the system reorganizes to a new functional state. Growth means it ends up better than before. A well-constructed application picks one and measures it, rather than gesturing at resilience generally.

‍ ‍

The Background Problem NIH Wants Solved

‍ ‍

NIH states that resilience spans whole-person systems, integrating molecular, cellular, physiological, and psychological levels within social communities and environmental contexts, and that translating this multiscale, multidomain nature has been limited by heterogeneous definitions, models, and measures.

‍ ‍

The named high-priority research areas follow directly from that:

‍ ‍

• Developing and refining resilience measures and metrics

• Data interoperability

• Advancing mechanistic understanding of protective and restoring factors distinct from disease-risk reduction

• Identifying biomarkers that reflect or predict resilience

‍ ‍

The Structural Requirement That Decides Most Applications

‍ ‍

This is the single most actionable sentence in the topic, and it functions as a checklist. NIH states that aligned applications would:

‍ ‍

1. Define the challenge or stressor

2. Define the system or systems

3. Define the resilience response or outcome

4. Include at least one domain of analysis, preferably across domains, to accelerate translation into implementable prevention, treatment, and recovery strategies

‍ ‍

Applications that skip step one are the most common failure mode in resilience science. Without a specified stressor there is no resilience to measure, only cross-sectional association. If you write to this topic, name the stressor explicitly and early, and design so that it is either naturally occurring and documented or experimentally applied.

‍ ‍

The Distinction That Separates Real Responsiveness From Repackaging

‍ ‍

Note carefully the phrase "distinct from disease-risk reduction." NIH is drawing a line, and reviewers will apply it.

‍ ‍

Lowering someone's blood pressure reduces disease risk. Understanding why a hypertensive person never has a stroke is resilience. Reducing tobacco exposure reduces risk. Understanding why some heavy smokers preserve lung function is resilience. A number of companies will reframe an existing risk-reduction product as resilience-promoting for this cycle. That reframing is visible, and it will be scored accordingly. The test is whether your work explains or enhances maintenance of health in the continued presence of risk rather than removal of the risk.

‍ ‍

A Methodological Signal Worth Reading Twice

‍ ‍

Both NIA and ODS ask for controlled perturbations and challenge-recovery designs with repeated measures. That is a design requirement, not a stylistic preference. A stressor is applied or occurs, and the system is measured before, during, and after. Cross-sectional designs cannot capture resist, recover, adapt, or grow, because all four are trajectories.

‍ ‍

For a company, this is actually favorable. Challenge-recovery designs with longitudinal monitoring are exactly where instrumentation, wearables, remote monitoring, and analytics create value, and they are exactly what a purely observational cohort study cannot deliver.

‍ ‍

Participating Institutes and Centers That Award Grants

‍ ‍

National Heart, Lung, and Blood Institute (NHLBI)

‍ ‍

NHLBI is interested in studies that:

‍ ‍

• Use data science and precision health to define individual heart, lung, blood, and sleep health signatures, including resilience metrics, stressors, tipping points, trajectories, and longitudinal outcomes across resistance, recovery, adaptation, and growth

• Leverage large biomedical resources including NHLBI-funded cohort studies, Trans-omics for Precision Medicine (TOPMed), Researching COVID to Enhance Recovery (RECOVER), All of Us, and LungMap

• Identify mechanisms that preserve, enhance, or restore homeostasis under stress and explain sustained health despite known risk, with the examples of hypertension without stroke, full recovery after heart valve surgery, preserved lung function despite tobacco exposure, and the interplay of resilience with sickle cell disease exacerbation such as vaso-occlusive crises

• Integrate multidomain exposures and biopsychosocial factors such as mindfulness, belief systems, and optimism, alongside community engagement, and include all populations within the NHLBI mission

‍ ‍

Contact: NHLBI Highlighted Topics (nhlbihighlightedtopics@mail.nih.gov).

‍ ‍

The resource-leverage bullet is the most useful thing on this page for a cash-constrained company. Building and validating analytics on TOPMed, RECOVER, All of Us, or existing NHLBI cohorts means you are not funding new cohort collection out of a Phase I budget. That is the difference between a fundable aim and an unfundable one at $323,090, and it also gives your validation claims a credibility that a small proprietary dataset never will. The phrase "tipping points" is worth noticing too, since it points toward early-warning and state-transition detection, which is a defensible product category.

‍ ‍

National Center for Complementary and Integrative Health (NCCIH)

‍ ‍

NCCIH is interested in research advancing understanding of resilience as a whole-person, multilevel process that informs strategies for health promotion, disease prevention, recovery, and overall well-being across the lifespan. Areas of interest:

‍ ‍

• Identifying, validating, and promoting modifiable protective pathways and factors contributing to resilience across molecular, cellular, physiological, behavioral, psychological, social, and environmental domains

• How complementary and integrative health approaches, lifestyle, and environmental factors affect the biological and behavioral mechanisms that enhance capacity to resist, recover, adapt, or grow

• Mechanistic research to identify and validate measures and biomarkers of resilience, and to generate evidence supporting implementation of effective resilience-promoting strategies across populations and settings

‍ ‍

NCCIH states it may give special consideration to support meritorious applications in this topic area.

‍ ‍

Contacts: Erin Burke Quinlan, PhD and Jennifer Baumgartner (NCCIHDERFunding@nih.gov).

‍ ‍

NCCIH matters disproportionately here for a reason that is not obvious from the topic page. Its standing small business portfolio already covers nutritional and natural products including dietary supplements and botanicals, psychological approaches such as meditation and music-based interventions, physical approaches including devices, and combined approaches such as yoga and tai chi. That makes NCCIH the natural funding home for several categories of resilience product that no other participating Institute would readily take, and the only one of the six signaling a preference alongside NIMHD.

‍ ‍

National Cancer Institute (NCI)

‍ ‍

NCI seeks projects advancing mechanistic understanding and interventions across cancer biology, prevention, and control, particularly studies that:

‍ ‍

• Develop, refine, or validate multilevel measures, biomarkers, and resilience signatures to defined stressors across cancer risk, tumor initiation, progression, treatment, and survivorship

• Identify protective factors and mechanisms enabling resistance to malignant transformation or favorable outcomes despite genetic, environmental, behavioral, or biological risk, including but not limited to DNA repair, immune surveillance, microbiome and host interactions, epigenetic stability, inflammation resolution, and metabolic adaptability

• Use advanced analytics in large, diverse longitudinal cohorts, and mechanistic studies in patients, human tissues, or model systems, to design, test, or implement interventions and strategies for risk stratification, early detection, prevention behaviors, treatment tolerance, and survivorship

‍ ‍

Contact: NCI Resilience HT Team (NCIResilienceHTTeam@mail.nih.gov).

‍ ‍

Note the phrase "resilience signatures to defined stressors." NCI has embedded the stressor requirement into its own bullet. Note also treatment tolerance, which is the most immediately commercial item in NCI's list: predicting which patients will tolerate a given regimen is a risk-stratification product with an obvious buyer, and it is framed here as resilience rather than toxicity prediction.

‍ ‍

National Institute on Aging (NIA)

‍ ‍

NIA's interests, as they relate to resilience in older individuals:

‍ ‍

• Development and validation of dynamic resilience measures using controlled perturbations and longitudinal monitoring

• Advanced analytics for multisystem resilience phenotyping

• The impact of age, early-life, psychosocial, and other factors on changes in neurobiological, molecular, cellular, physiological, social, and behavioral resilience mechanisms; how these factors individually and interactively influence severity of and recovery from stressors; and how dysregulation or modulation of these mechanisms, particularly in those with multiple contributors to impaired resilience, shapes aging-related clinical endpoints

• Shared and tissue-specific pathways and mechanisms of inter-organ or system-level coordination

• Mechanisms underlying sex differences

• Therapeutic targets for, and mechanisms by which, interventions improve resilience and preserve or restore clinical outcomes in representative populations

‍ ‍

Contact: Stacy Carrington-Lawrence, PhD (stacy.carrington-lawrence@nih.gov).

‍ ‍

NIA's first two bullets are the clearest product specifications in the entire topic. A validated perturbation protocol plus a monitoring modality plus an analytic layer that outputs a multisystem resilience phenotype is a commercial instrument, not a research finding. NIA also carries the most favorable budget ceilings of any participating Institute, discussed below.

‍ ‍

National Institute on Alcohol Abuse and Alcoholism (NIAAA)

‍ ‍

NIAAA seeks research on mechanisms shaping alcohol use, alcohol-related outcomes, recovery, and resilience across biological, behavioral, psychological, social, and environmental levels, and states that priority goes to reproducible studies that identify protective pathways and biomarkers, explain heterogeneity, and inform prevention and intervention. Named areas:

‍ ‍

• Longitudinal lifespan cohort studies using multimodal AI to integrate biological, behavioral, and environmental data and identify resilience to alcohol use disorder and alcohol harms, including resistance, recovery, and adaptation, and influences such as inter-brain synchrony, social enrichment, peer context, sleep, and community and environmental factors

• Reverse translational and New Approach Methodologies studies of cellular, molecular, and circuit mechanisms that promote resilience despite alcohol risk exposure

• Integrative multiomic studies of heterogeneity in resilience to alcohol use disorder, emphasizing protective pathways, validated biomarkers, and standardized, reproducible measures

‍ ‍

Contacts: Laura Kwako (laura.kwako@nih.gov) and Miri Gitik (miri.gitik@nih.gov).

‍ ‍

NIAAA's standing small business priorities already include biosensors and wearables for real-time monitoring, digital health and telehealth platforms, diagnostic tools and biomarkers, and advanced data analytics using machine learning on large health datasets. The overlap with this topic's multimodal AI and biomarker bullets is close to exact, which makes NIAAA one of the more mechanically straightforward routes for a data or sensor company.

‍ ‍

National Institute on Minority Health and Health Disparities (NIMHD)

‍ ‍

NIMHD supports solutions-oriented biological, behavioral, clinical, and population science research focused on resilience among populations with health disparities, including:

‍ ‍

• Identifying novel biological, behavioral, social, and environmental mechanisms that shape resilience across the life course, and elucidating pathways that buffer or mitigate stress-related health effects

• Developing measures, biomarkers, and scalable interventions that generalize across populations and community contexts

• Applying community-engaged, systems science, data science, and translational approaches to advance resilience research and its real-world impact

• Examining epigenetic processes, vagal nerve function, and environmental and biological interactions to identify mechanisms and clinical targets for resilience

• Investigating relationships between psychological resilience and the onset, severity, and progression of health events, as well as recovery duration, quality, and long-term outcomes

‍ ‍

NIMHD states it may dedicate available funds to support applications in this Topic area, depending on availability of funds, the number of meritorious applications, and competing ICO priorities, and separately that it may give special consideration to meritorious applications in this topic area.

‍ ‍

Contact: Rada Dagher, PhD, MPH (Rada.dagher@nih.gov).

‍ ‍

NIMHD is the only ICO in this topic making both statements, which makes it the strongest signal on the page. The word scalable in its second bullet is doing real work: NIMHD is asking for interventions that generalize and deploy, which is a commercial requirement rather than an academic one. Vagal nerve function is also named explicitly, which is a specific and measurable physiological target with existing device and wearable pathways.

‍ ‍

Participating Offices That Do Not Award Grants

‍ ‍

Five participating ICOs cannot fund your application. Their published interests are still worth reading, because they tell you what NIH leadership is prioritizing and because a well-aimed application can be responsive to an office's interest while being funded by an Institute. But you must land on an Institute's mission.

‍ ‍

Office of Dietary Supplements (ODS). ODS seeks research on how dietary supplements, meaning oral interventions of vitamins, minerals, natural products, botanicals, fatty acids, proteins, amino acids, or other bioactive food constituents, affect physiological, metabolic, cognitive, and immune resilience across the lifespan. Studies using repeated measures and challenge-recovery designs to test whether supplements help resist, recover, adapt, or grow after aging-related, infectious, metabolic, psychosocial, or environmental stressors are emphasized. Specific interests include elucidating biological mechanisms or protective pathways through which supplements influence adaptive responses to physiological stressors; identifying and validating supplement exposure biomarkers associated with maintenance or recovery of physiological function, resistance to defined stressors, or adaptive capacity; and developing and validating ways to measure resilience in a dietary supplementation context. Contact: Adam J. Kuszak, PhD (ods-funding@od.nih.gov).

‍ ‍

This is the most product-specific section on the entire NIH page, and ODS has no money. If you are a supplement, botanical, or nutraceutical company, the practical route is almost always NCCIH, whose small business program explicitly covers nutritional and natural products, or NIA if the framing is aging and older adults. Talk to ODS for scientific alignment, then talk to NCCIH or NIA about who would actually fund it.

‍ ‍

Office of Research on Women's Health (ORWH). ORWH is interested in projects that advance resilience research across the life course relevant to women's health, including pregnancy, menopause, and aging; incorporate sex as a biological variable in resilience mechanisms, measures, biomarkers, and trajectories; and address sex differences in multidomain resilience, including through computational models, to support rigorous, generalizable prevention, treatment, and recovery strategies. Contact: Marquitta White, MS, PhD (orwhinfo@nih.gov).

‍ ‍

The Office of Autoimmune Disease Research within ORWH (OADR-ORWH) is interested in the role of stressors on early immune changes in the prodromal phase of autoimmunity; resilience as an immunopreventative strategy for autoimmune disease; and utilizing federated data platforms to enhance pattern recognition in complex multiomic datasets, enabling deeper insight into the multimodal drivers of autoimmune disease pathogenesis and co-occurring autoimmune diseases. Contact: Victoria Shanmugam, MBBS, FRCP, FACR, CCD (oadrinfo@nih.gov).

‍ ‍

The federated data platform bullet is a software specification, and prodromal autoimmunity is a diagnostics opportunity. Neither office can fund it. Sex differences in resilience mechanisms is a named NIA interest as well, which gives you a funding route for the ORWH angle.

‍ ‍

Office of Disease Prevention (ODP). For this topic, ODP is particularly interested in projects testing interventions to promote health and well-being in individuals, families, communities, or populations facing biological, social, economic, or environmental challenges, and encourages research enhancing protective factors across the life course to prevent disease and disability, improve well-being, and reduce long-term disease burden. Contact: Valerie Robinson, PhD, MPhil, MHA (valerie.robinson@nih.gov).

‍ ‍

Office of Behavioral and Social Sciences Research (OBSSR). Participating, with Janine Simmons, MD, as contact (OBSSRNews@mail.nih.gov).

‍ ‍

Tribal Health Research Office (THRO). Participating, with Sheila Caldwell, PhD (throinfo@od.nih.gov) and Christopher Barnhart, PhD (christopher.barnhart@nih.gov) as contacts. Note that the topic's purpose statement names tribal communities explicitly as a population of interest.

‍ ‍

Where Does a Small Business Actually Fit?

‍ ‍

Be honest with yourself here: this is the most research-heavy of NIH's current Highlighted Topics, and a large share of what it describes belongs in an R01 rather than an SBIR. Mechanistic biology in model systems, secondary analysis of existing cohorts for scientific insight, and epidemiological characterization are not products. NIH SBIR and STTR awards fund research and development toward a commercially viable product or service.

‍ ‍

That said, NIH named measures, metrics, biomarkers, and data interoperability as high-priority areas, and those are all things that get built and sold. The genuine openings:

‍ ‍

Validated resilience measurement instruments. NIH says the field is limited by heterogeneous measures and asks for harmonized terminology, standardized protocols, and validated measures. A validated, licensable instrument, whether a clinical assessment, a digital measure, or a scored composite, is a real product with a real market, and NCCIH, NIMHD, NIA, and NCI all ask for measure development independently. Whoever produces the instrument the field standardizes on owns a durable position.

‍ ‍

Controlled perturbation and challenge-recovery testing systems. NIA's leading bullet, and echoed by ODS. A standardized stressor protocol plus a monitoring modality plus a scoring output is an instrument. This is the clearest hardware and software opportunity in the topic.

‍ ‍

Multisystem phenotyping analytics. NIA asks for advanced analytics for multisystem resilience phenotyping. NHLBI asks for health signatures including resilience metrics, tipping points, and trajectories. NIAAA asks for multimodal AI integrating biological, behavioral, and environmental data. Three Institutes, one product category.

‍ ‍

Biomarker panels that predict recovery rather than risk. NIH asks for biomarkers that reflect or predict resilience. This is a distinct diagnostic category from disease-risk biomarkers, and the clinical use cases are concrete: who will tolerate this treatment, who will recover from this surgery, who will decompensate under this stressor. NCI names treatment tolerance directly. NHLBI names recovery after heart valve surgery.

‍ ‍

Remote monitoring and wearables for longitudinal trajectory capture. Resist, recover, adapt, and grow are all trajectories, and trajectories require repeated measurement. Continuous monitoring is the enabling technology, and NIAAA's standing portfolio already funds wearables and biosensors.

‍ ‍

Data interoperability and federated analysis platforms. NIH names data interoperability as a high-priority area, and OADR-ORWH names federated data platforms specifically. Software with a plausible route to institutional customers.

‍ ‍

Scalable intervention delivery. NIMHD asks for scalable interventions that generalize across populations and community contexts, and it is the Institute most likely to dedicate funds. Digital and community-deployable intervention platforms fit here.

‍ ‍

Supplement and natural product mechanisms and exposure biomarkers. ODS's full list, funded through NCCIH or NIA.

‍ ‍

Vagal nerve function measurement or modulation. Named explicitly by NIMHD, with existing device and wearable pathways.

‍ ‍

What Will Not Work

‍ ‍

A risk-reduction product relabeled as resilience. Covered above, and it is the single most predictable failure here. NIH drew the line explicitly with the phrase "distinct from disease-risk reduction."

‍ ‍

A wellness or mindfulness app with no defined stressor and no measurement. NIH's structural requirement is to define the challenge or stressor, the system, and the resilience outcome. An application that cannot name its stressor is not responsive, regardless of how well the intervention is described.

‍ ‍

A cross-sectional study. All four resilience outcomes are trajectories. If your design measures once, it cannot detect resistance, recovery, adaptation, or growth.

‍ ‍

A measure with no validation plan. The field's problem is that everyone has a measure and none of them agree. Producing another unvalidated instrument adds to the problem NIH is trying to solve. Validation against an independent criterion is the whole value proposition.

‍ ‍

Two Strategic Notes

‍ ‍

Use the existing data assets. NHLBI explicitly invites leveraging TOPMed, RECOVER, All of Us, LungMap, and NHLBI cohorts. NCI asks for advanced analytics in large, diverse longitudinal cohorts. NIAAA asks for longitudinal lifespan cohort studies. For a small business, this is the difference between a feasible Phase I and an impossible one, because you can develop and validate an analytic or a measure without funding primary data collection. It also strengthens the generalizability claim that reviewers will otherwise attack.

‍ ‍

STTR deserves a hard look. NIH describes this topic as inherently interdisciplinary across molecular, cellular, physiological, psychological, social, community, and environmental levels, and NIMHD asks for community-engaged approaches. Very few small companies hold that range internally. Under STTR, a formal collaboration with a university or nonprofit research institution is required, at least 40 percent of the work is performed by the small business and at least 30 percent by the research institution, and the Principal Investigator may be primarily employed by either organization. If you need an academic cohort, a validated psychometric bench, or a community-engaged research partner to be credible, PA-27-102 is often the stronger application.

‍ ‍

How Much Funding Would I Receive?

‍ ‍

There is no funding amount attached to the Highlighted Topic itself. Budgets come from the parent announcement and from the Institute that funds you.

‍ ‍

Under the current NIH SBIR and STTR parent announcements, standard guidelines provide:

‍ ‍

• Phase I: up to $323,090, typically over one to two years

• Phase II: up to $2,153,927, typically over two to three years

• Fast-Track: Phase I and Phase II in a single application and review

• Direct to Phase II: available under SBIR for companies that have already established feasibility

• Phase IIB (PA-27-101): follow-on funding beyond Phase II

• Commercialization Readiness Pilot: late-stage, milestone-driven support, with amounts varying by Institute

‍ ‍

Cost sharing is not required.

‍ ‍

NIA Carries the Best Ceilings in This Topic

‍ ‍

Among the six participating Institutes that award grants, NIA holds approval to exceed the standard caps in both of its lanes:

‍ ‍

• Up to $700,000 for Phase I and $3 million for Phase II for Alzheimer's disease and AD-related dementia projects

• Up to $500,000 for Phase I and $2.5 million for Phase II for other projects within the NIA mission space

‍ ‍

That second line is easy to miss and it matters. A resilience-in-aging project that has nothing to do with dementia still carries a Phase I ceiling roughly 55 percent above standard and a Phase II ceiling about 16 percent above standard. Given that NIA also published the two most product-shaped bullets in the entire topic, dynamic resilience measures using controlled perturbations and multisystem resilience phenotyping analytics, the combination of scope fit and budget headroom makes NIA worth a conversation even if aging is not your primary framing.

‍ ‍

NCI supports CRP projects up to the SBA statutory maximum of $4,191,495, plus up to $500,000 for technical assistance. NIMHD operates under standard caps but is the only participating ICO signaling both possible dedicated funds and special consideration.

‍ ‍

Full Institute-by-Institute budget detail is in our NIH SBIR program executive summary.

‍ ‍

What Could I Use the Funding For?

‍ ‍

Funds support research and development toward a commercially viable product or service aligned with the mission of a participating Institute. Allowable costs include personnel, materials, instrument and device development, assay development, software development, validation studies, analysis of existing datasets, intellectual property protection, and other direct R&D expenses.

‍ ‍

Phase II, Phase IIB, and CRP funds may additionally cover scale-up, multi-site validation, regulatory preparation, and commercialization activities.

‍ ‍

Clinical trial policy depends on the Institute. Among the participating Institutes that award grants, NCI, NHLBI, NIA, and NIMHD accept clinical trials through their small business programs, and several accept them through Phase IIB as well. Policy for NCCIH and NIAAA under the current parent announcement should be confirmed directly with program staff before you design around it. Note that challenge-recovery and controlled-perturbation studies in human participants may or may not meet the NIH definition of a clinical trial depending on design, and that determination affects which announcement track and which forms apply. This is a specific question worth putting to your program officer in writing.

‍ ‍

What Is the Timeline?

‍ ‍

Highlighted Topic dates

‍ ‍

• Posted: August 28, 2026

• Expires: August 25, 2028

‍ ‍

SBIR and STTR standard receipt dates (PA-27-100 and PA-27-102)

‍ ‍

• September 5, 2026. This falls on a Saturday, and Labor Day is Monday, September 7, so submissions are accepted through Tuesday, September 8, 2026.

• January 5, 2027

• April 5, 2027

• September 5, 2027, which falls on a Sunday before Labor Day, so that cycle effectively closes Tuesday, September 7, 2027

• January 5, 2028

• April 5, 2028

‍ ‍

Because the topic expires on August 25, 2028, April 5, 2028 is the last standard receipt date inside the active window, giving you six cycles in total. The September 2028 date falls just outside it. All applications are due by 5:00 PM local time of the applicant organization.

‍ ‍

Review and award timeline for the September 2026 cycle

‍ ‍

• Scientific merit review: November 2026

• Advisory council review: January 2027

• Earliest project start date: April 2027

‍ ‍

Review and award timeline for the January 2027 cycle

‍ ‍

• Scientific merit review: March 2027

• Advisory council review: May 2027

• Earliest project start date: July 2027

‍ ‍

Review and award timeline for the April 2027 cycle

‍ ‍

• Scientific merit review: July 2027

• Advisory council review: August 2027

• Earliest project start date: December 2027

‍ ‍

A policy change that matters for planning. NIH tightened its late application policy under NOT-OD-26-064, effective for due dates on or after May 25, 2026. Small business applications no longer receive the discretionary late submission window. Submit early enough to resolve eRA Commons validation errors before the deadline.

‍ ‍

Practical planning guidance. Budget at least twelve weeks of lead time before your target due date, and more if your federal registrations are not complete. SAM.gov, UEI, the SBA Company Registry, eRA Commons, and Grants.gov registrations can take four to six weeks on their own and must all be finished before you can submit. For a first-time applicant, expect 120 to 200 hours of total effort.

‍ ‍

Two topic-specific timing items. If your plan depends on access to an existing NIH data resource such as TOPMed, RECOVER, or All of Us, start the data access request early, since approval processes have their own timelines and reviewers will want evidence that access is secured rather than hoped for. And if your design involves community-engaged research, which NIMHD asks for, community partnership agreements and letters with defined roles cannot be assembled in the final two weeks.

‍ ‍

Who Is Eligible to Apply?

‍ ‍

Eligibility comes from the parent announcement, not from the topic. Applicants must be U.S. small business concerns that are:

‍ ‍

• Organized for profit with a place of business located in the United States

• At or below 500 employees, including affiliates

• More than 50 percent owned and controlled by U.S. citizens or permanent resident aliens, by qualifying U.S. entities, or by a combination

‍ ‍

For STTR, the company must also have a formal collaboration with a U.S. research institution, with at least 40 percent of the work performed by the small business and at least 30 percent by the research institution.

‍ ‍

Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted.

‍ ‍

Are There Restrictions I Should Know About?

‍ ‍

• Only U.S. small business concerns are eligible; foreign organizations are not.

• Applications involving foreign subawards or subcontracts will not be considered for funding.

• Your application must be relevant to the mission of a participating Institute or Center that awards grants. For this topic that means NHLBI, NCCIH, NCI, NIA, NIAAA, or NIMHD. OBSSR, ODP, ODS, ORWH, and THRO do not award grants.

• Duplicate or highly overlapping applications submitted under multiple HHS announcements are not permitted.

• Companies must satisfy applicable SBA performance benchmark requirements, including the Phase I to Phase II transition rate benchmark and the Phase II commercialization rate benchmark for companies with substantial award histories.

• Phase I generally requires at least 67 percent of the research effort to be performed by the small business; Phase II at least 50 percent. Consultant and contractual arrangements in Phase I are generally limited to roughly 33 percent of the total amount requested, which is a real constraint if your design leans heavily on an academic cohort or a community partner. STTR is the cleaner structure in that case.

• Additional national security, foreign relationship, and foreign ownership disclosure requirements apply and may result in denial of award. The 2026 SBIR and STTR reauthorization tightened foreign risk management and due diligence review, and that screening now sits inside the review critical path.

• Cost sharing is not required.

• Applying under a Highlighted Topic does not change referral or review, and does not guarantee that funds have been set aside.

‍ ‍

What Kind of Application Is Likely to Win Here?

‍ ‍

NIH reviews small business applications on Significance, Investigators, Innovation, Approach, and Environment, with commercialization potential specifically evaluated for Phase II and Fast-Track. Within this topic, five things separate competitive applications.

‍ ‍

One: you named the stressor. NIH gave the structure explicitly: define the challenge or stressor, the systems, and the resilience response or outcome, and include at least one domain of analysis. Most weak resilience applications fail at the first item. Put the stressor in your Specific Aims page, not buried in the approach.

‍ ‍

Two: you picked one of the four verbs and measured it. Resistance, recovery, adaptation, and growth are different phenomena with different measurement requirements. Specificity here reads as rigor. Gesturing at resilience generally reads as vagueness.

‍ ‍

Three: you are not doing risk reduction in a new coat. NIH said "distinct from disease-risk reduction." Your work should explain or enhance maintained health in the continued presence of risk.

‍ ‍

Four: you picked the right Institute, and you picked it before writing. Six Institutes could plausibly claim a resilience measurement product, and five participating offices cannot fund it at all. This topic has more misrouting risk than any other current Highlighted Topic. Email the named contact, describe the technology in a paragraph, and ask whether it fits and which mechanism they would suggest. For supplement and natural product work specifically, ask ODS about science and NCCIH or NIA about funding.

‍ ‍

Five: your validation plan is the centerpiece, not an afterthought. NIH's stated problem is heterogeneous measures and lack of reproducibility, and NIAAA states outright that priority goes to reproducible studies. Whatever you build, the aim that matters is the one where you validate it against an independent criterion in a population that looks like the intended market.

Frequently Asked Questions

Is the NIH multidomain resilience Highlighted Topic a funding opportunity I can apply to directly?

No. An NIH Highlighted Topic is a published statement of scientific priority, not a Notice of Funding Opportunity. There is no application package and no separate deadline. Small businesses apply through a broad NIH opportunity, which means the SBIR parent announcement PA-27-100 or the STTR parent announcement PA-27-102.

How does NIH define resilience for this topic?

NIH defines resilience broadly as a living system's capacity to resist, recover, adapt, or grow from challenges or stressors, with outcomes tracked over time across interconnected individual, community, and environmental systems. NIH attributes this framing to Brown and colleagues, 2023. The four outcomes are distinct: resistance means function is maintained through the stressor, recovery means function returns to baseline, adaptation means the system reorganizes to a new functional state, and growth means it ends up better than before.

What does NIH require an aligned application to include?

NIH states that aligned applications would define the challenge or stressor, define the system or systems, define the resilience response or outcome, and include at least one domain of analysis, preferably across domains, in order to accelerate translation into implementable prevention, treatment, and recovery strategies. Failing to specify the stressor is the most common way a resilience application loses responsiveness.

How much funding is available under this Highlighted Topic?

The topic itself carries no funding amount. Standard SBIR guidelines provide up to $323,090 for Phase I and up to $2,153,927 for Phase II. Among the participating Institutes, NIA holds approval to exceed those caps, allowing up to $700,000 for Phase I and $3 million for Phase II on Alzheimer's disease and AD-related dementia projects, and up to $500,000 for Phase I and $2.5 million for Phase II for other projects in its mission space. NCI supports Commercialization Readiness Pilot projects up to the SBA statutory maximum of $4,191,495 plus up to $500,000 for technical assistance.

Does applying under this Highlighted Topic improve my chances of being funded?

Not in review. NIH states that applying in a Highlighted Topic area will not affect referral or review of applications. NIMHD states it may dedicate available funds to this topic area and may give special consideration to meritorious applications in it, and NCCIH states it may give special consideration. The other participating ICOs make no such statement. The main advantage is informational.

Which NIH Institutes and Centers participate, and which ones can actually fund my application?

Eleven ICOs participate. Six award grants: NHLBI, NCCIH, NCI, NIA, NIAAA, and NIMHD. Five do not: OBSSR, ODP, ODS, ORWH including the Office of Autoimmune Disease Research, and THRO. Your application must be relevant to the mission of at least one of the six that award grants.

I work on dietary supplements and the Office of Dietary Supplements published detailed interests. Can ODS fund my SBIR?

No. ODS does not award grants, despite publishing the most product-specific interests in this topic, including supplement exposure biomarkers and challenge-recovery designs testing whether supplements help resist, recover, adapt, or grow. The practical route is NCCIH, whose small business program explicitly covers nutritional and natural products including botanicals, or NIA if the framing is aging and older adults. Discuss science with ODS and funding with NCCIH or NIA.

What are the application deadlines?

The topic is open from August 28, 2026 through August 25, 2028. SBIR and STTR standard receipt dates are September 5, 2026, January 5, 2027, April 5, 2027, September 5, 2027, January 5, 2028, and April 5, 2028. Because the topic expires in August 2028, April 5, 2028 is the last standard receipt date inside the active window. September 5, 2026 falls on a Saturday before Labor Day, so that cycle accepts submissions through Tuesday, September 8, 2026, and September 5, 2027 falls on a Sunday before Labor Day, so that cycle closes Tuesday, September 7, 2027. All applications are due by 5:00 PM local time of the applicant organization.

What is the difference between resilience research and disease-risk reduction?

NIH explicitly asks for mechanistic understanding of protective and restoring factors distinct from disease-risk reduction. Lowering a risk factor reduces exposure to risk. Resilience explains or enhances maintained health in the continued presence of risk. NHLBI's examples make the distinction concrete: hypertension without stroke, preserved lung function despite tobacco exposure, and full recovery after heart valve surgery. Repackaging an existing risk-reduction product as resilience-promoting is visible to reviewers.

What kinds of resilience projects fit NIH SBIR rather than a research grant?

The strongest small business fits are validated resilience measurement instruments, controlled perturbation and challenge-recovery testing systems paired with longitudinal monitoring, multisystem phenotyping analytics, biomarker panels that predict recovery capacity rather than disease risk, remote monitoring and wearables for trajectory capture, data interoperability and federated analysis platforms, scalable intervention delivery, supplement and natural product exposure biomarkers, and vagal nerve function measurement or modulation. Mechanistic biology in model systems and secondary cohort analysis for scientific insight generally belong in an R01 instead.

Can I use existing NIH datasets instead of collecting new data?

Yes, and NIH encourages it. NHLBI explicitly invites leveraging its cohort studies, TOPMed, RECOVER, All of Us, and LungMap. NCI asks for advanced analytics in large, diverse longitudinal cohorts. For a Phase I budget this is often the difference between a feasible and an infeasible aim, and it strengthens generalizability claims. Start data access requests early, because approval has its own timeline and reviewers want evidence access is secured.

Why do NIA and ODS emphasize controlled perturbations and challenge-recovery designs?

Because resistance, recovery, adaptation, and growth are all trajectories, and a cross-sectional measurement cannot capture a trajectory. A stressor must be applied or occur, with the system measured before, during, and after. For companies this is favorable, since instrumentation, wearables, remote monitoring, and analytics are precisely what these designs require and precisely what an observational cohort cannot deliver.

Should my company apply for SBIR or STTR?

Choose SBIR if your company performs the majority of the research and your Principal Investigator is primarily employed by the company. Choose STTR if the project depends on a formal collaboration with a university or nonprofit research institution. Because NIH describes this topic as inherently interdisciplinary across molecular, physiological, psychological, social, community, and environmental levels, and because NIMHD asks for community-engaged approaches, STTR is frequently the stronger structural fit. Phase I SBIR generally limits consultant and contractual arrangements to roughly 33 percent of the total requested, which constrains designs that lean heavily on academic or community partners.

Can I run a clinical trial with this funding?

It depends on the Institute. Among the participating Institutes that award grants, NCI, NHLBI, NIA, and NIMHD accept clinical trials through their small business programs, and several accept them through Phase IIB as well. Confirm NCCIH and NIAAA policy directly with program staff. Note also that challenge-recovery and controlled-perturbation studies in human participants may or may not meet the NIH definition of a clinical trial depending on design, and that determination affects which forms and which track apply, so put the question to your program officer in writing.

Who is eligible to apply?

For-profit U.S. small business concerns with 500 or fewer employees including affiliates, more than 50 percent owned and controlled by U.S. citizens or permanent residents or by qualifying U.S. entities. Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted. STTR additionally requires a formal collaboration with a U.S. research institution.

How long will it take me to prepare an application?

For a first-time applicant, expect 120 to 200 hours in total. Start at least twelve weeks before your target due date. Federal registrations across SAM.gov, UEI, the SBA Company Registry, eRA Commons, and Grants.gov can take four to six weeks on their own and must be complete before you can submit.

What happens if I submit late?

It will not be accepted. NIH tightened its late application policy for due dates on or after May 25, 2026, and small business applications no longer receive the discretionary late submission window.

Could this Highlighted Topic be withdrawn before it expires?

Possibly. NIH reviews each Highlighted Topic annually for continued alignment with agency priorities, and Institutes can post and retire topics at any time. The posted expiration date is August 25, 2028, but verify the topic is still live before each cycle you plan to submit in.

How Can BW&CO Help?

BW&CO is a non-dilutive federal funding advisory firm. We have helped clients secure more than $350 million in federal funding, and this topic is a good example of where advisory work earns its keep: eleven participating ICOs, only six of which can fund anything, the two most product-specific bullet lists belonging to offices with no money, a definitional line between resilience and risk reduction that reviewers will enforce, and one Institute quietly carrying budget ceilings well above the standard caps.

We can:

• Identify the right Institute and mechanism for your technology, including routing supplement, natural product, women's health, autoimmune, and federated data platform concepts to an Institute that can actually fund them.

• Structure the application around NIH's own checklist, so the stressor, the system, the resilience outcome, and the domains of analysis are unmistakable on the Specific Aims page.

• Triple your likelihood of success through proven strategy and insider-aligned proposal development.

• Reduce your time spent on the proposal by 50 to 80 percent, so your team stays on the technology.

• Structure academic, cohort, and community partnerships so they strengthen the application without breaching the outsourcing limits.

NIH Highlighted Topic: Wastewater-Based Epidemiology as a Tool for Monitoring Environmental Chemicals, Medications, Drugs, and Pathogenic Exposures

Highlighted Topic 103 | Participating ICOs: NIEHS, NIAID, NIDA | Posted August 27, 2026 | Expires August 27, 2028 | Apply through the NIH SBIR parent announcement (PA-27-100) or the NIH STTR parent announcement (PA-27-102).

Executive Summary

NIH has designated wastewater-based epidemiology (WBE) as a formal Highlighted Topic, with NIEHS, NIAID, and NIDA each publishing their own areas of interest. Of the Highlighted Topics NIH has posted to date, this is one of the most product-shaped. Nearly every gap NIH names is a hardware, assay, or software problem rather than an open scientific question, which makes it unusually well suited to SBIR and STTR applicants rather than to academic investigators alone.

The premise is straightforward. Wastewater is a continuous, population-scale biological and chemical sample that nobody has to consent to, travel for, or remember to provide. NIH points out that it can indicate exposure to pesticides, plasticizers, personal care products, heavy metals, industrial releases, emerging contaminants, and disaster-related spills and fires, and that beyond pathogens it can also detect medications and drug metabolites. Compared with human biomonitoring, which requires collecting blood or urine from individuals, WBE is non-invasive and cost-effective, and it scales across both geography and time in a way individual sampling never will.

What NIH says is missing is the engineering and the standards layer. The named challenges are sampling variability driven by where and when samples are collected, analytical methods, data integration and statistical modeling, and data interpretation, meaning how a detection in wastewater actually correlates with real-world human exposure and what it implies for public health. NIH also names best practices, communication of findings, and ethical and privacy considerations as important open questions.

For a company, that list reads like a product roadmap: autosamplers and passive samplers that reduce variability, validated multi-residue chemical panels, molecular assays for targets that current methods miss, normalization and back-calculation methods that turn a concentration into a defensible population estimate, and data infrastructure that lets utilities, health departments, and labs actually share results.

The three participating Institutes divide the space cleanly. NIEHS wants chemical and environmental exposure work, including assay and biomarker development and bringing WBE to small and rural systems. NIAID wants pathogen and genomic epidemiology methods, human versus animal signal separation, and assays for chlorine-resistant protozoan parasites and cysts. NIDA wants substance use and overdose surveillance, emerging substance identification, and triangulation with other drug use data sources.

There is no dedicated funding and no separate application. A Highlighted Topic is a priority signal, not a Notice of Funding Opportunity. You apply through the standard NIH SBIR or STTR omnibus and compete in the normal pool, and NIH states that applying in a Highlighted Topic area will not affect referral or review. NIEHS states it may give special consideration to meritorious applications in this topic area. NIAID and NIDA make no such statement for this topic.

Under the current SBIR parent announcement, standard budget guidelines run up to $323,090 for Phase I and up to $2,153,927 for Phase II. One caveat matters specifically here: certain NIEHS program areas carry substantially lower caps, and that is discussed below. The next standard receipt dates are September 5, 2026, January 5, 2027, and April 5, 2027, and the topic stays live through August 27, 2028.

A Quick Note on the NIH SBIR and STTR Program

‍ ‍

The NIH, CDC, and FDA SBIR and STTR programs are the largest source of non-dilutive early-stage funding for health, biomedical, and life science technology in the United States. NIH alone sets aside well over a billion dollars a year. Awards are grants, not investments. No equity, no repayment, no board seat.

‍ ‍

The program runs in phases. Phase I funds proof of concept and feasibility. Phase II funds the substantive research and development that turns a validated concept into a product. Fast-Track combines both in one application, and Direct to Phase II lets companies that have already established feasibility skip Phase I. Phase IIB and the Commercialization Readiness Pilot extend funding for late-stage work such as validation, manufacturing scale-up, and regulatory submissions. Applicants must be for-profit U.S. small businesses with 500 or fewer employees and majority U.S. ownership.

‍ ‍

For the complete breakdown of the NIH SBIR and STTR program, including all budget caps by Institute, clinical trial policies, eligibility mechanics, review criteria, and the full timeline, see our full executive summary here: NIH, CDC and FDA Parent SBIR Grant (PA-27-100).

‍ ‍

Everything below is specific to this Highlighted Topic.

‍ ‍

What Is a Highlighted Topic, and How Is It Different From a Funding Opportunity?

‍ ‍

A Notice of Funding Opportunity (NOFO) is a solicitation. It has an announcement number, its own application package, its own review criteria, and usually its own set-aside funding. You apply to it directly.

‍ ‍

A Highlighted Topic is a published statement of scientific priority maintained centrally by NIH. It has no application package and no guaranteed funding. You cannot apply to it. You apply through a broad opportunity such as the SBIR or STTR parent announcement, and the topic tells you what the participating Institutes want to fund inside their existing budgets.

‍ ‍

NIH is explicit about how this works in practice:

‍ ‍

• Apply through an appropriate parent announcement or other broad NIH opportunity.

• Reach out early to the listed scientific contacts to discuss alignment.

• If an ICO chooses to dedicate funding to a topic, the amount depends on available funds, the number of meritorious applications, and competing priorities.

• Applying in a Highlighted Topic area will not affect NIH referral or review of your application.

‍ ‍

NIH also notes that Institutes can post new topics at any time and that each topic is reviewed annually for continued alignment with agency priorities. Topics do get retired. If you are building a multi-year federal funding plan around one, verify it is still live before each cycle.

‍ ‍

What the topic buys you is intelligence, not scoring advantage. Three Institutes have written down what they would fund in this space and named the program staff to call. In a field as new as WBE, where there is no established study section culture and no obvious default Institute, that mapping is worth more than a modest scoring bump. The most common way a strong WBE application fails is landing at the wrong Institute, because a chemical exposure project reviewed by pathogen reviewers, or vice versa, tends to score as out of scope rather than as weak.

‍ ‍

There is no notice number to enter in the Agency Routing Identifier field for a Highlighted Topic, unlike the older Notice of Special Interest model. Make the alignment explicit in your cover letter and Specific Aims, and confirm handling with your target Institute's program officer before you submit.

‍ ‍

What Are They Looking For? A Detailed Overview

‍ ‍

The Stated Purpose

‍ ‍

The topic encourages research on wastewater-based epidemiology approaches for understanding exposure to environmental contaminants, medications, drugs, and pathogens at the community level. That last phrase is the whole framing. This is not about diagnosing individuals. It is about characterizing populations.

‍ ‍

Why NIH Considers This Worth Prioritizing

‍ ‍

NIH's background statement makes four arguments, and each one is a section of your significance narrative if you write here.

‍ ‍

Wastewater is a broader signal than most people assume. NIH lists pesticides, plasticizers, personal care products, heavy metals, industrial releases, emerging contaminants, and disaster-related spills and fires as detectable exposures. It also states plainly that while wastewater has been used to detect pathogens, it can also detect medications and drug metabolites. If your mental model of WBE is still SARS-CoV-2 surveillance, this topic is considerably wider than that.

‍ ‍

It solves a real limitation of human biomonitoring. Individual biomonitoring requires collecting blood or urine from people. WBE is non-invasive and cost-effective, and it evaluates community exposure patterns across large populations both geographically and over time. That produces insight into community health and behavior that individual sampling cannot practically deliver at scale.

‍ ‍

It requires convergence. NIH describes WBE as combining advanced analytical chemistry, molecular biology, and epidemiological approaches, and notes that it inherently involves data sharing and collaboration across many scientific disciplines. This is an explicit invitation to build interdisciplinary teams, and it is one reason STTR deserves a hard look here.

‍ ‍

The unsolved problems are technical. This is the part to read closely, because it is where the fundable product work lives.

‍ ‍

The Named Technical Gaps

‍ ‍

NIH groups the open challenges into four clusters. Read these as product requirements.

‍ ‍

Sampling variability. Driven by sample location and timing of sample collection. This is the single most cited weakness in the WBE literature, and it is a hardware and protocol problem. Grab samples misrepresent diurnal patterns. Composite sampling helps but adds cost and complexity. Sample location within a sewer network determines what population you actually measured. Passive samplers, flow-proportional autosamplers, in-line sensors, and sample stabilization chemistry all sit directly on this gap.

‍ ‍

Analytical methods. Detection and quantification of targets that current methods handle poorly, in a matrix that is actively hostile to analysis. Wastewater is chemically complex, biologically active, and variable hour to hour. Recovery, matrix effects, degradation between collection and analysis, and limits of detection at environmentally relevant concentrations are all live problems.

‍ ‍

Data integration and statistical modeling. Turning measurements into population-level estimates requires normalization for flow, population size, in-sewer degradation, and per-capita excretion assumptions. Every one of those introduces uncertainty, and the field has not standardized any of them.

‍ ‍

Data interpretation. NIH states the question directly: how does detection in wastewater correlate with real-world human exposure, and what are the public health implications? This is the validation gap, and it is why parallel clinical and wastewater studies show up in NIAID's list. Any company selling a WBE product will eventually be asked to defend the inferential chain from a concentration in a pipe to a claim about a population.

‍ ‍

NIH additionally names best practices, communication of findings, and ethical and privacy issues as important considerations. Do not treat that as boilerplate. In a field where results can be attributed to a neighborhood, a building, or an institution, the ethics section of a WBE application carries real weight, and NIDA explicitly asks for research analyzing those implications.

‍ ‍

Participating Institutes and What Each One Wants

‍ ‍

Only three Institutes participate in this topic, which makes Institute selection simpler than usual but also raises the stakes on getting it right. Your application will be assigned to one, that Institute's budget will pay for it, and its priorities will decide whether it gets funded after review.

‍ ‍

National Institute of Environmental Health Sciences (NIEHS)

‍ ‍

NIEHS is the chemical and environmental exposure home for this topic, and it is the only participating Institute signaling any preference. NIEHS encourages multidisciplinary collaborations and partnerships with public health experts, epidemiologists, analytical chemists, and experts in contaminant fate and transport.

‍ ‍

Stated areas of interest:

‍ ‍

• WBE studies to identify known and emerging environmental contaminants impacting community health

• WBE to identify the origins of contaminants and quantify contaminant contribution to disease

• Studies promoting multi-level assessment of sewer networks at various scales, including single and multiple wastewater treatment plants, neighborhoods, and individual buildings

• Technology and methodology development to advance WBE, including biomarkers for monitoring community health and assays for detection and quantification of chemical exposures

• Creation and incorporation of data infrastructure and standardized protocols for WBE collaboration

• Increasing community awareness and bringing WBE to small-serving communities such as rural systems

‍ ‍

NIEHS states it may give special consideration to support meritorious applications in this topic area.

‍ ‍

ICO scientific contacts: Danielle Carlin, PhD, DABT (danielle.carlin@nih.gov); Yuxia Cui, PhD (yuxia.cui@nih.gov); Heather Henry, PhD (heather.henry@nih.gov).

‍ ‍

Two of these bullets are unusually direct invitations to small businesses. "Technology and methodology development, including biomarkers and assays for detection and quantification of chemical exposures" is a description of a product. So is "data infrastructure and standardized protocols." And the small-serving and rural communities bullet is a market-access argument that most competitors will ignore, which makes it a differentiator: the small utility that serves 3,000 people cannot afford a research-grade LC-MS workflow, and a low-cost, low-skill, ruggedized approach has both public health value and a genuinely underserved commercial market.

‍ ‍

National Institute of Allergy and Infectious Diseases (NIAID)

‍ ‍

NIAID owns the pathogen side. Stated areas of interest:

‍ ‍

• Genomic epidemiology method development to better detect and track microbes, predict microbial case surges, analyze and share WBE metadata and data, integrate WBE data across platforms, and identify novel applications for secondary analyses of WBE data

• Development of clearer methods to distinguish human versus animal and agricultural signals, and One Health integration

• Using WBE to study microbe biology, including transmission, evolution, and persistence

• Parallel clinical and WBE studies analyzing the contribution of microbes identified in the environment to human disease

• Development of novel assays and laboratory methods for detection and quantification of protozoan parasites and cysts that resist chlorination

‍ ‍

ICO scientific contacts: Brooke Bozick, PhD (brooke.bozick@nih.gov); M. "Kate" Bradford Plimack, PhD (kate.plimack@nih.gov).

‍ ‍

Two of these are exceptionally well-defined product problems. Human versus animal signal discrimination is a discrete, solvable technical question with immediate commercial value, because it determines whether a positive result triggers a public health response or gets written off as agricultural runoff, and no standardized solution has been adopted. Chlorine-resistant protozoan parasites and cysts, meaning organisms in the Cryptosporidium and Giardia class, is an even tighter specification: NIAID has essentially named the analyte class and the failure mode of existing methods. If you have an assay platform that concentrates and detects environmental cysts, this bullet was written for you.

‍ ‍

Note also that NIAID's standing small business portfolio already funds diagnostics and prevention strategies across bacterial, fungal, viral, and parasitic targets, so a WBE assay application does not require NIAID to stretch its mission.

‍ ‍

National Institute on Drug Abuse (NIDA)

‍ ‍

NIDA frames its interest around public health response rather than measurement for its own sake. NIDA is interested in WBE research that supports community and public health responses to substance use and overdose, and it makes two participation requests that function as near-requirements:

‍ ‍

• Applicants are encouraged to partner with local or state public health agencies to ensure public health relevance and the ability to respond to identified hotspots and outbreaks.

• Applicants are encouraged to engage people who may be affected by the research or the reporting of results, including people who use drugs and other community members.

‍ ‍

Stated areas of interest:

‍ ‍

• Tracking patterns of substance use or exposures, including illicit drugs, medications for opioid use disorder, and naloxone

• Identifying emerging substances

• Examining links between substances detected in wastewater and community-level health outcomes such as fatal and non-fatal overdose

• Triangulating WBE with other drug use data sources to inform public health surveillance and response

• Analyzing the ethical implications of wastewater surveillance of substance use and misuse detection

‍ ‍

ICO scientific contact: MeLisa Creamer (melisa.creamer@nih.gov).

‍ ‍

The naloxone and medications-for-OUD bullet is worth pausing on. Most WBE drug work measures consumption of illicit substances. NIDA is also asking about measuring treatment and harm reduction penetration, which is a fundamentally different and largely unbuilt product: a community-level indicator of whether interventions are actually reaching people. That is a metric health departments and payers would plausibly buy, and almost nobody is selling it.

‍ ‍

NIDA's standing small business priorities already include forensic testing technologies for identifying emerging drugs and diagnostic tools for detection and quantification of drug exposure, both of which map onto this topic without any stretching.

‍ ‍

Where Does a Small Business Actually Fit?

‍ ‍

More cleanly here than in most Highlighted Topics. NIH SBIR and STTR awards fund research and development toward a commercially viable product or service, and this topic's gaps are largely instrumentation, assay, and software gaps. The strongest fits:

‍ ‍

Sampling hardware and sample stabilization. Flow-proportional and passive samplers, in-sewer deployable devices, cold-chain-free preservation chemistry, and sampling designs that let a single device characterize a neighborhood rather than a whole treatment plant. NIEHS explicitly asks for multi-level sewer network assessment down to the building scale, which is a hardware and deployment problem before it is a science problem.

‍ ‍

Analytical assays and panels. Multi-residue chemical panels for pesticides, plasticizers, personal care products, heavy metals, and emerging contaminants. Molecular panels for pathogens. Concentration and detection methods for chlorine-resistant protozoan cysts, which NIAID names specifically. Assays for drug metabolites and for medications including buprenorphine, methadone, and naloxone.

‍ ‍

Field-deployable and decentralized testing. Everything above, but cheap enough and simple enough for a rural utility or a small health department to run without a PhD analytical chemist. NIEHS's small-serving communities bullet is the funding hook, and the addressable market is large and structurally underserved.

‍ ‍

Normalization, modeling, and interpretation software. Turning a concentration into a defensible population estimate is the field's central unsolved problem and it is pure software plus validation. This is the highest-margin, lowest-capital entry point in the topic, and NIH names it twice, under data integration and statistical modeling and again under data interpretation.

‍ ‍

Data infrastructure and interoperability. NIEHS asks for data infrastructure and standardized protocols for WBE collaboration. NIAID asks for the ability to analyze and share WBE metadata, integrate data across platforms, and enable secondary analyses. That is a platform specification written by two Institutes independently.

‍ ‍

Human versus animal source attribution. NIAID's One Health bullet. A validated discrimination method is a component that every other WBE product would want to license.

‍ ‍

Biomarkers of community health. NIEHS asks for biomarkers for monitoring community health, which is broader than contaminant measurement and largely undefined. This is the most scientifically speculative bullet in the topic and correspondingly the most defensible if you have real preliminary data.

‍ ‍

Surveillance-to-response platforms. NIDA's framing is explicit that measurement without response capability is not the goal. A system that detects an emerging substance and routes an actionable alert to a health department, with the ethical and privacy architecture built in rather than bolted on, addresses NIDA's stated interest directly.

‍ ‍

What Will Not Work

‍ ‍

Three failure modes are predictable here.

‍ ‍

A surveillance service with no technology development. Running existing assays on new samples in a new city is a service business, not research and development. SBIR reviewers will identify it immediately. The innovation has to be in the method, the instrument, the model, or the platform.

‍ ‍

A COVID-era pathogen dashboard repositioned. A number of companies built SARS-CoV-2 wastewater dashboards and are looking for a second act. Reviewers in this space have seen that pitch. If the underlying technology is a data pipeline that ingests third-party lab results, the innovation claim is thin unless the modeling and interpretation layer is genuinely novel and validated.

‍ ‍

Measurement with no validation against human exposure. NIH names data interpretation as a core gap. An application that produces numbers without addressing what those numbers mean for actual human exposure is answering the easy half of the question.

‍ ‍

Two Structural Considerations

‍ ‍

Partnering with a health department cuts both ways. NIDA encourages partnership with local or state public health agencies, and NIEHS encourages partnerships with public health experts and epidemiologists. Those partnerships are genuinely necessary for credibility and for site access. They also consume your outsourcing allowance: under SBIR, Phase I generally requires at least 67 percent of the research effort to be performed by the small business and Phase II at least 50 percent, and consultant plus contractual arrangements in Phase I are generally capped around 33 percent of the total requested. Structure the partnership as site access, sample provision, and advisory input rather than as a large subaward, or move to STTR where the collaboration allowance is built into the mechanism.

‍ ‍

STTR is often the better vehicle here. NIH describes WBE as inherently requiring analytical chemistry, molecular biology, and epidemiology together, plus data sharing across disciplines. Few small companies hold all of that in house. Under STTR, a formal collaboration with a university or nonprofit research institution is required, at least 40 percent of the work is performed by the small business and at least 30 percent by the research institution, and the Principal Investigator may be primarily employed by either organization. For a company that needs an academic environmental epidemiologist or a university analytical core to be credible, PA-27-102 is frequently the stronger application. One exception is noted in the funding section below.

‍ ‍

How Much Funding Would I Receive?

‍ ‍

There is no funding amount attached to the Highlighted Topic itself. Budgets come from the parent announcement you apply through and from the Institute that funds you.

‍ ‍

Under the current NIH SBIR and STTR parent announcements, standard guidelines provide:

‍ ‍

• Phase I: up to $323,090, typically over one to two years

• Phase II: up to $2,153,927, typically over two to three years

• Fast-Track: Phase I and Phase II in a single application and review

• Direct to Phase II: available under SBIR for companies that have already established feasibility

• Phase IIB (PA-27-101): follow-on funding beyond Phase II

• Commercialization Readiness Pilot: late-stage, milestone-driven support, with amounts varying by Institute

‍ ‍

Cost sharing is not required.

‍ ‍

The NIEHS Budget Caveat You Need to Check First

‍ ‍

This matters more in this topic than almost anywhere else in the NIH portfolio, because NIEHS is the most natural home for chemical-focused WBE work and NIEHS applies reduced caps to two of its program areas.

‍ ‍

NIEHS caps its Superfund Research Program topics at $200,000 for Phase I, $1.25 million for Phase II, and $300,000 for CRP. Its Worker Training Program topics are capped at $100,000, Phase I only. Both of those NIEHS programs accept SBIR applications only, not STTR.

‍ ‍

The Superfund Research Program focuses on detection and remediation technologies for hazardous substances relevant to Superfund and other contaminated sites. A WBE project framed around detecting industrial releases, heavy metals, disaster-related spills, or site-associated contaminants could plausibly be routed there, and the difference between the standard cap and the SRP cap is more than $900,000 in Phase II. It also removes STTR as an option, which changes your whole team structure.

‍ ‍

This is a five-minute email to a program officer that can reshape the entire application. Ask directly whether your project would be handled under general NIEHS mission or under the Superfund Research Program before you build a budget.

‍ ‍

NIAID and NIDA both operate under the standard caps and both accept STTR.

‍ ‍

Full Institute-by-Institute budget detail is in our NIH SBIR program executive summary.

‍ ‍

What Could I Use the Funding For?

‍ ‍

Funds support research and development toward a commercially viable product or service aligned with the mission of a participating Institute. Allowable costs include personnel, materials, prototype fabrication, assay development, instrument builds, field deployment and validation studies, method comparison work, software development, intellectual property protection, and other direct R&D expenses.

‍ ‍

Phase II, Phase IIB, and CRP funds may additionally cover scale-up, manufacturing, validation at multiple sites, regulatory preparation, and commercialization activities.

‍ ‍

For most WBE projects, human subjects considerations are lighter than founders expect. Wastewater collected at a treatment plant or sewer node is generally not individually identifiable and is typically not treated as human subjects research, though that determination belongs to your IRB and your Institute, not to you. Where it changes is in the parallel clinical and wastewater studies NIAID names, which do involve human participants and human specimens, and in any building-level or institution-level sampling where results could be attributed to a small identifiable group. If your design includes either, raise it with program staff early, because it affects which forms you file and how the application is reviewed.

‍ ‍

What Is the Timeline?

‍ ‍

Highlighted Topic dates

‍ ‍

• Posted: August 27, 2026

• Expires: August 27, 2028

‍ ‍

SBIR and STTR standard receipt dates (PA-27-100 and PA-27-102)

‍ ‍

• September 5, 2026. This falls on a Saturday, and Labor Day is Monday, September 7, so submissions are accepted through Tuesday, September 8, 2026.

• January 5, 2027

• April 5, 2027

• September 5, 2027, which falls on a Sunday before Labor Day, so that cycle effectively closes Tuesday, September 7, 2027

• January 5, 2028

• April 5, 2028

‍ ‍

Because the topic expires on August 27, 2028, April 5, 2028 is the last standard receipt date that falls inside the active window. That gives you six cycles in total. All applications are due by 5:00 PM local time of the applicant organization.

‍ ‍

Review and award timeline for the September 2026 cycle

‍ ‍

• Scientific merit review: November 2026

• Advisory council review: January 2027

• Earliest project start date: April 2027

‍ ‍

Review and award timeline for the January 2027 cycle

‍ ‍

• Scientific merit review: March 2027

• Advisory council review: May 2027

• Earliest project start date: July 2027

‍ ‍

Review and award timeline for the April 2027 cycle

‍ ‍

• Scientific merit review: July 2027

• Advisory council review: August 2027

• Earliest project start date: December 2027

‍ ‍

A policy change that matters for planning. NIH tightened its late application policy under NOT-OD-26-064, effective for due dates on or after May 25, 2026. Small business applications no longer receive the discretionary late submission window. Submit early enough to resolve eRA Commons validation errors before the deadline, not after.

‍ ‍

Practical planning guidance. Budget at least twelve weeks of lead time before your target due date, and more if your federal registrations are not complete. SAM.gov, UEI, the SBA Company Registry, eRA Commons, and Grants.gov registrations can take four to six weeks on their own and must all be finished before you can submit anything. For a first-time applicant, expect 120 to 200 hours of total effort on a competitive submission.

‍ ‍

One WBE-specific timing note: if your project requires access to a sewer network, a treatment plant, or a health department's data, secure those agreements and letters of support before you start writing. Utility and municipal approvals move on their own schedule, and a missing site access letter is a common reason otherwise strong environmental applications lose points on Environment and Approach.

‍ ‍

Who Is Eligible to Apply?

‍ ‍

Eligibility comes from the parent announcement, not from the topic. Applicants must be U.S. small business concerns that are:

‍ ‍

• Organized for profit with a place of business located in the United States

• At or below 500 employees, including affiliates

• More than 50 percent owned and controlled by U.S. citizens or permanent resident aliens, by qualifying U.S. entities, or by a combination

‍ ‍

For STTR, the company must also have a formal collaboration with a U.S. research institution, with at least 40 percent of the work performed by the small business and at least 30 percent by the research institution. Note again that NIEHS Superfund Research Program and Worker Training Program topics accept SBIR only.

‍ ‍

Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted.

‍ ‍

Are There Restrictions I Should Know About?

‍ ‍

• Only U.S. small business concerns are eligible; foreign organizations are not.

• Applications involving foreign subawards or subcontracts will not be considered for funding. WBE has an active international research community, and collaborations that would be natural scientifically are not permissible under this mechanism.

• Your application must be relevant to the mission of a participating Institute. For this topic that means NIEHS, NIAID, or NIDA.

• Duplicate or highly overlapping applications submitted under multiple HHS announcements are not permitted.

• Companies must satisfy applicable SBA performance benchmark requirements, including the Phase I to Phase II transition rate benchmark and the Phase II commercialization rate benchmark for companies with substantial award histories.

• Phase I generally requires at least 67 percent of the research effort to be performed by the small business; Phase II at least 50 percent. Consultant and contractual arrangements in Phase I are generally limited to roughly 33 percent of the total amount requested.

• Additional national security, foreign relationship, and foreign ownership disclosure requirements apply and may result in denial of award. The 2026 SBIR and STTR reauthorization tightened foreign risk management and due diligence review, and that screening now sits inside the review critical path.

• Cost sharing is not required.

• Applying under a Highlighted Topic does not change referral or review, and does not guarantee that funds have been set aside.

‍ ‍

What Kind of Application Is Likely to Win Here?

‍ ‍

NIH reviews small business applications on Significance, Investigators, Innovation, Approach, and Environment, with commercialization potential specifically evaluated for Phase II and Fast-Track. Within this topic, five things separate competitive applications.

‍ ‍

One: you picked the right Institute before you started writing. Three Institutes with genuinely different scopes means the same instrument can be three different applications. A sampler validated on pesticides is NIEHS. The same sampler validated on protozoan cysts is NIAID. Validated on fentanyl analogs it is NIDA. Email the named contact, describe the technology in a paragraph, ask whether it fits and which mechanism they would suggest. It is the highest-return hour you will spend, and for NIEHS it is also how you find out which budget cap applies.

‍ ‍

Two: you addressed a named gap rather than a general capability. NIH gave you the list: sampling variability, analytical methods, data integration and modeling, data interpretation, best practices, communication, and ethics. An application that maps its aims onto those specific gaps is visibly responsive. One that describes a general WBE platform is not.

‍ ‍

Three: you have real validation data, ideally against an independent measure. The interpretation gap is the field's credibility problem. Applications that show their wastewater signal tracking something externally verifiable, whether clinical case counts, prescription data, overdose records, or paired human biomonitoring, are answering the question reviewers actually have.

‍ ‍

Four: you brought the partners. All three Institutes ask for collaboration in some form, and NIDA asks twice, for public health agency partnership and for engagement with affected community members including people who use drugs. Letters of support from partners with no defined role in the research plan are transparent to reviewers. Give each partner a named function, specific deliverables, and where appropriate a line in the budget.

‍ ‍

Five: you took ethics and privacy seriously as design, not as compliance. NIH names ethical and privacy issues in the background, and NIDA lists analyzing the ethical implications of wastewater surveillance as a fundable area in its own right. Building-level and institution-level sampling can attribute drug use to an identifiable group, and that has already generated public controversy in the field. An application that has thought through spatial resolution limits, data governance, and how findings get communicated is stronger on Approach and considerably more commercially credible, because your eventual customers will ask the same questions

Frequently Asked Questions

Is the NIH wastewater-based epidemiology Highlighted Topic a funding opportunity I can apply to directly?

No. An NIH Highlighted Topic is a published statement of scientific priority, not a Notice of Funding Opportunity. There is no application package and no separate deadline. Small businesses apply through a broad NIH opportunity, which means the SBIR parent announcement PA-27-100 or the STTR parent announcement PA-27-102.

How much funding is available under this topic?

The topic itself carries no funding amount. Standard SBIR guidelines provide up to $323,090 for Phase I and up to $2,153,927 for Phase II. One exception matters here: NIEHS caps Superfund Research Program topics at $200,000 for Phase I, $1.25 million for Phase II, and $300,000 for CRP, and caps Worker Training Program topics at $100,000 for Phase I only. Both of those NIEHS programs accept SBIR only, not STTR. Confirm with NIEHS program staff which program area would handle your project before building a budget.

Does applying under this Highlighted Topic improve my chances?

Not in review. NIH states that applying in a Highlighted Topic area will not affect referral or review of applications. NIEHS states it may give special consideration to meritorious applications in this topic area. NIAID and NIDA make no such statement for this topic. The real advantage is informational: three Institutes have documented what they want to fund and named the program staff to contact.

Which NIH Institutes participate in the wastewater-based epidemiology Highlighted Topic?

Three: the National Institute of Environmental Health Sciences (NIEHS), the National Institute of Allergy and Infectious Diseases (NIAID), and the National Institute on Drug Abuse (NIDA). NIEHS covers chemical and environmental contaminant exposure, NIAID covers pathogens and genomic epidemiology, and NIDA covers substance use and overdose surveillance.

What are the deadlines?

The topic is open from August 27, 2026 through August 27, 2028. SBIR and STTR standard receipt dates are September 5, 2026, January 5, 2027, April 5, 2027, September 5, 2027, January 5, 2028, and April 5, 2028. Because the topic expires in August 2028, April 5, 2028 is the last standard receipt date inside the active window. September 5, 2026 falls on a Saturday before Labor Day, so that cycle accepts submissions through Tuesday, September 8, 2026, and September 5, 2027 falls on a Sunday before Labor Day, so that cycle closes Tuesday, September 7, 2027. All applications are due by 5:00 PM local time of the applicant organization.

What specific technical problems is NIH asking companies to solve?

NIH names four clusters of challenges: sampling variability driven by sample location and timing of collection; analytical methods; data integration and statistical modeling; and data interpretation, meaning how detection in wastewater correlates with real-world human exposure and what it implies for public health. NIH also names best practices, communication of findings, and ethical and privacy issues as important considerations. Each of those is a defensible basis for an SBIR aim.

Can wastewater-based epidemiology detect more than pathogens?

Yes, and NIH says so explicitly. The topic states that wastewater can indicate exposure to pesticides, plasticizers, personal care products, heavy metals, industrial releases, emerging contaminants, and disaster-related spills and fires, and that while it has been used to detect pathogens it can also detect medications and drug metabolites. The topic is considerably broader than pathogen surveillance.

Who is eligible to apply?

For-profit U.S. small business concerns with 500 or fewer employees including affiliates, more than 50 percent owned and controlled by U.S. citizens or permanent residents or by qualifying U.S. entities. Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted. STTR additionally requires a formal collaboration with a U.S. research institution.

Should my company apply for SBIR or STTR?

Choose SBIR if your company performs the majority of the research and your Principal Investigator is primarily employed by the company. Choose STTR if the project depends on a formal collaboration with a university or nonprofit research institution. Because NIH describes WBE as requiring analytical chemistry, molecular biology, and epidemiology together, STTR is frequently the stronger structural fit. The exception is NIEHS Superfund Research Program and Worker Training Program topics, which accept SBIR only.

Is wastewater sampling considered human subjects research?

Usually not, but the determination is not yours to make. Wastewater collected at a treatment plant or sewer node is generally not individually identifiable and is typically not treated as human subjects research. That changes for the parallel clinical and wastewater studies NIAID names, which involve human participants and specimens, and for building-level or institution-level sampling where results could be attributed to a small identifiable group. Raise either scenario with program staff and your IRB early.

Do I need a partnership with a utility or health department?

Not formally required, but effectively yes for most designs. NIDA encourages partnering with local or state public health agencies and engaging affected community members including people who use drugs. NIEHS encourages partnerships with public health experts, epidemiologists, analytical chemists, and contaminant fate and transport experts. Beyond responsiveness, you need site access to collect samples. Secure those agreements before you begin writing, because municipal approvals move on their own schedule and a missing site access letter costs points on Environment and Approach.

How do partnerships interact with the SBIR work allocation rules?

Carefully. Phase I generally requires at least 67 percent of the research effort to be performed by the small business and Phase II at least 50 percent, and consultant plus contractual arrangements in Phase I are generally limited to roughly 33 percent of the total requested. Structure agency and academic partnerships as site access, sample provision, data sharing, and advisory input rather than as large subawards, or use STTR where a substantial research institution role is built into the mechanism.

What kinds of wastewater projects are unlikely to be funded?

Three patterns predictably fail. A surveillance service that runs existing assays on new samples in new locations is a service business rather than research and development. A repositioned COVID-era dashboard that ingests third-party lab results has a thin innovation claim unless the modeling and interpretation layer is genuinely novel. And measurement work that produces numbers without addressing what they mean for real human exposure answers only the easy half of the question NIH asked.

How long will it take me to prepare an application?

For a first-time applicant, expect 120 to 200 hours in total. Start at least twelve weeks before your target due date. Federal registrations across SAM.gov, UEI, the SBA Company Registry, eRA Commons, and Grants.gov can take four to six weeks on their own and must be complete before you can submit.

What happens if I submit late?

It will not be accepted. NIH tightened its late application policy for due dates on or after May 25, 2026, and small business applications no longer receive the discretionary late submission window.

Could this topic be withdrawn before it expires?

Possibly. NIH reviews each Highlighted Topic annually for continued alignment with agency priorities, and Institutes can post and retire topics at any time. The posted expiration date is August 27, 2028, but verify the topic is still live before each cycle you plan to submit in.

How Can BW&CO Help?

BW&CO is a non-dilutive federal funding advisory firm. We have helped clients secure more than $350 million in federal funding, and wastewater-based epidemiology sits at exactly the kind of intersection we handle well: an emerging measurement field with real hardware and software product opportunities, three possible Institute sponsors with meaningfully different scopes, one buried budget cap that can cost you $900,000 if you find it late, and partnership requirements that interact awkwardly with SBIR work allocation rules.

We can:

• Identify the right Institute and mechanism for your technology, and determine before you write whether NIEHS would handle your project under general mission or under the Superfund Research Program, which decides both your budget ceiling and whether STTR is available.

• Triple your likelihood of success through proven strategy and insider-aligned proposal development.

• Reduce your time spent on the proposal by 50 to 80 percent, so your team stays on the technology.

• Structure utility, health department, and academic partnerships so they strengthen the application without breaching the outsourcing limits.

NIH Highlighted Topic: Catalyzing Interdisciplinary Research on HIV-Associated Co-occurring Conditions

Highlighted Topic 99 | Lead Office: NIH Office of AIDS Research (OAR) | Posted July 28, 2026 | Expires July 28, 2028 | Apply through the NIH SBIR parent announcement (PA-27-100) or the NIH STTR parent announcement (PA-27-102).

Executive Summary

NIH has designated HIV-associated co-occurring conditions as a formal Highlighted Topic, and sixteen NIH Institutes, Centers, and Offices have attached their own stated interests to it. For a small business, this is one of the most cross-cutting priority signals NIH has published in the HIV space, because it opens the door to funding from cancer, cardiopulmonary, aging, metabolic, mental health, substance use, oral health, musculoskeletal, and integrative health budgets at the same time, all through a single application to the standard SBIR or STTR omnibus.

The science being requested is a shift in framing. Antiretroviral therapy has turned HIV into a manageable chronic condition, and the unsolved problem is no longer viral suppression. It is that people with HIV develop comorbidities earlier, carry more of them at once, experience treatment-related toxicities, and navigate mental health, substance use, and structural barriers that disease-specific care models were never designed to handle. NIH wants to fund work that treats those conditions as an interconnected system rather than a list of separate diseases, and it wants that work to reach patients through care models that actually get implemented.

For companies, the commercially relevant openings are concentrated in a handful of places: multi-condition risk prediction and early screening, point-of-care and decentralized diagnostics for comorbidities and coinfections, digital therapeutics and adherence technologies that address HIV alongside substance use or mental health, biomarkers of accelerated aging and organ injury, drug interaction and polypharmacy decision support, and platforms that let a single clinic deliver integrated care without adding staff.

There is no dedicated pot of money and no separate application form. A Highlighted Topic is a priority signal, not a Notice of Funding Opportunity. You apply through the normal NIH SBIR or STTR omnibus, you compete against every other small business application in that cycle, and NIH states plainly that applying in a Highlighted Topic area will not affect how your application is referred or reviewed. What the topic does give you is unusually specific intelligence about what sixteen ICOs want to buy, plus named program staff to call before you write a word. Two participating Institutes, NHLBI and NIDA, state they may dedicate funds to this topic area, and three, NCCIH, NIDA, and NIDCR, state they may give special consideration to meritorious applications in it.

Under the current SBIR parent announcement, standard budget guidelines run up to $323,090 for Phase I and up to $2,153,927 for Phase II, with several Institutes approved to exceed those caps. The next standard receipt dates are September 5, 2026, January 5, 2027, and April 5, 2027, and the topic stays live through July 28, 2028.

One timing change matters more here than almost anywhere else in the NIH portfolio: HHS eliminated dedicated AIDS-specific SBIR and STTR due dates for applications due on or after May 25, 2026. HIV-focused companies that built their calendars around the legacy AIDS cycles need to rebuild them around the standard September, January, and April dates.

A Quick Note on the NIH SBIR and STTR Program

‍ ‍

The NIH, CDC, and FDA SBIR and STTR programs are the largest source of non-dilutive early-stage funding for health, biomedical, and life science technology in the United States. NIH alone sets aside well over a billion dollars a year. Awards are grants, not investments. There is no equity, no repayment, and no board seat.

‍ ‍

The program runs in phases. Phase I funds proof of concept and feasibility. Phase II funds the substantive research and development that turns a validated concept into a product. Fast-Track combines both in a single application, and Direct to Phase II lets companies that have already established feasibility skip Phase I entirely. Phase IIB and the Commercialization Readiness Pilot extend funding for late-stage work such as clinical validation, manufacturing scale-up, and regulatory submissions. Applicants must be for-profit U.S. small businesses with 500 or fewer employees and majority U.S. ownership.

‍ ‍

For the complete breakdown of the NIH SBIR and STTR program, including all budget caps by Institute, clinical trial policies, eligibility mechanics, review criteria, and the full timeline, see our full executive summary here: NIH, CDC and FDA Parent SBIR Grant (PA-27-100).

‍ ‍

Everything below is specific to this Highlighted Topic.

‍ ‍

What Is a Highlighted Topic, and How Is It Different From a Funding Opportunity?

‍ ‍

This distinction trips up nearly every first-time applicant, so it is worth being precise.

‍ ‍

A Notice of Funding Opportunity (NOFO) is a solicitation. It has an announcement number, its own application package, its own review criteria, and in most cases its own set-aside funding. You apply to it directly.

‍ ‍

A Highlighted Topic is a published statement of scientific priority maintained centrally by NIH. It has no application package. It has no guaranteed funding. You cannot apply to it. Instead, you apply through a broad opportunity such as the SBIR or STTR parent announcement, and the topic tells you what the participating Institutes and Centers currently want to fund inside their existing budgets.

‍ ‍

NIH is explicit about the practical consequences:

‍ ‍

• Apply through an appropriate parent announcement or other broad NIH opportunity.

• Reach out early to the listed scientific contacts to discuss alignment.

• If an ICO chooses to dedicate funding to a topic, the amount depends on available funds, the number of meritorious applications, and competing priorities.

• Applying in a Highlighted Topic area will not affect NIH referral or review of your application.

‍ ‍

That last point is the one to internalize. The topic does not give you a scoring advantage. What it gives you is a map. Sixteen ICOs have each written down, in their own words, what they would fund in this space and who to call about it. That intelligence is worth considerably more than a modest scoring bump, because the single most common reason strong small business applications fail at NIH is misalignment with the Institute that ends up holding the application.

‍ ‍

Highlighted Topics replaced the older Notice of Special Interest (NOSI) model for this purpose. If you have applied to NIH before and are looking for a notice number to enter into the Agency Routing Identifier field, there is not one for a Highlighted Topic. The practical approach is to make the alignment explicit in your cover letter and in your Specific Aims, and to confirm handling with the program officer at your target Institute before you submit.

‍ ‍

What Are They Looking For? A Detailed Overview

‍ ‍

The Core Scientific Problem

‍ ‍

NIH frames the problem in terms that any founder in this space will recognize from the clinic.

‍ ‍

Antiretroviral therapy transformed HIV into a manageable chronic condition. But people with HIV still face high risk and early onset of comorbidities, adverse effects from ART itself, and a set of medical, psychosocial, and structural challenges that are tangled together rather than separable. The burden extends beyond people living with HIV: NIH specifically calls out HIV-exposed but uninfected children, who may carry elevated risks of immune, metabolic, and developmental problems compared with unexposed peers, particularly in low and middle-income settings.

‍ ‍

The stated knowledge gaps are where the fundable work lives:

‍ ‍

Mechanistic gaps. How do HIV, ART, and psychosocial stressors interact to drive the early onset and progression of comorbidities? This is the question underneath accelerated aging, chronic inflammation, and immune activation.

‍ ‍

Shared-pathway gaps. Many comorbidities intersect and share risk factors before diverging into disease-specific trajectories. NIH gives two examples directly: metabolic syndrome raising risk for diabetes, cardiovascular disease, and chronic kidney disease at once; and certain coinfections raising cancer risk. The implication is a real product thesis. If you can identify or intervene on a shared upstream factor, you address multiple outcomes with one technology, and that is a much stronger commercial story than a single-indication tool.

‍ ‍

Model gaps. Traditional disease-specific models do not capture shared factors, and they do not capture the multilevel determinants that decide whether an intervention actually gets implemented in a real health system.

‍ ‍

Care delivery gaps. NIH wants whole-person care that links infectious diseases, endocrinology, psychiatry, nursing, pharmacy, and community health, with emphasis on early screening, lifestyle-based prevention, and sustained engagement in HIV care, all while accounting for local context and health system constraints.

‍ ‍

The Stated Purpose

‍ ‍

The topic aims to catalyze interdisciplinary research on HIV-associated co-occurring conditions and to expand multidisciplinary teams that can develop and deliver preventive strategies improving health and quality of life across the lifespan. Three emphases are named:

‍ ‍

1. Shared factors and multi-organ effects, to inform early preventive strategies.

2. Implementation science approaches to identify barriers and facilitators, optimize multidisciplinary care, and deliver scalable, sustainable care models.

3. Multidisciplinary teams with multiple Program Directors and Principal Investigators holding complementary expertise, cross-NIH alignment, and use of existing NIH resources.

‍ ‍

Meaningful community engagement is strongly encouraged throughout.

‍ ‍

Alignment With the Make America Healthy Again Initiative

‍ ‍

This topic is being issued as part of the Make America Healthy Again (MAHA) initiative, and NIH lists the specific MAHA workstreams it aligns with. This matters strategically, because it tells you which vocabulary and which framings currently carry institutional weight. The named alignments include:

‍ ‍

• The NIH MAHA Chronic Disease Initiative, which aligns existing NIH chronic disease research and aims to generate actionable results for diseases arising in childhood and adulthood.

• The Whole-Person-Health approach to chronic disease prevention, including metabolic health at all stages of life.

• Prescribing patterns and impact on mental health, including evaluation of prescription patterns and overprescription trends.

• Food for Health, studying food and lifestyle interventions and their effect on outcomes and cost.

• Nutrition, including dietary patterns that support metabolic health and precision nutrition.

• The oral health and systemic disease connection, including oral microbiome relationships with gut health and immune function.

• The Gut Microbiome Research Initiative, on the microbiome's role in chronic disease development and progression.

• Longitudinal research for chronic disease prevention, leveraging existing NIH cohorts including All of Us, ABCD, HBCD, and ECHO.

• Clinical trial networks, strengthening existing networks through engagement with large public and private hospital systems including the VA.

• Mental health and addiction research, with focus areas including screen time in children and adolescents.

‍ ‍

If your technology touches metabolic health, nutrition, the microbiome, polypharmacy, or prevention, there is language here you should be borrowing.

‍ ‍

Participating Institutes, Centers, and Offices, and What Each One Wants

‍ ‍

This is the section to read closely. Your application will be assigned to one Institute, that Institute's budget will pay for it, and that Institute's priorities will determine whether it gets funded after review. Below is what each participating ICO has stated for this topic.

‍ ‍

Office of AIDS Research (OAR), lead office. OAR is interested in facilitating interdisciplinary research, including implementation science, to advance understanding of the common factors underlying HIV-associated co-occurring conditions, supporting early prevention, integrated whole-person care, and improved health and quality of life across the lifespan. OAR does not award grants. Your application must be relevant to at least one participating Institute or Center that does. OAR is the central scientific contact for the topic overall, and Geetanjali Bansal, PhD, is the ICO scientific contact.

‍ ‍

National Cancer Institute (NCI). NCI wants to advance understanding of the risks, development, progression, prevention, diagnosis, and treatment of cancer in people with HIV, and to test and implement bundled cancer and HIV interventions. NCI notes that people with HIV have increased incidence of certain cancers, are diagnosed at earlier ages and higher stages, have worse overall and cancer-specific survival, and are less likely to receive cancer treatment. Named example topics: characterizing how HIV infection contributes to the development and pathogenesis of HIV-related tumors; discovering and developing new biomarkers, diagnostics, and therapeutics to improve prevention, diagnosis, treatment, and outcomes; and identifying factors that drive cancer disparities for people with HIV, including work to improve adoption, implementation, and sustainment of effective interventions. Contact: Rebecca Liddell Huppi, PhD.

‍ ‍

National Heart, Lung, and Blood Institute (NHLBI). NHLBI is interested in mechanisms and pathways behind HIV-associated heart, lung, blood, and sleep (HLBS) comorbidities, and in interventions that improve care, including implementation research. Stated priorities: combined effects of aging, HIV, and ART on HLBS conditions; aging- and HIV-related changes in hematopoiesis, including hematopoietic stem cells and their niche; the impact of sleep deficiency and sleep-disordered breathing on HIV-associated cardiopulmonary and cardiometabolic disease; vascular contributions to cognitive impairment and dementia; implementation strategies that improve uptake and sustainability of evidence-based HLBS interventions; mechanistic studies to reduce the effects of HIV and aging on HLBS comorbidities, including traditional risk factors and sex differences; and novel methods to detect subclinical HIV-related HLBS conditions plus strategies to mitigate clinical disease. NHLBI states it may dedicate available funds to applications in this topic area, subject to funds, the number of meritorious applications, and competing priorities.

‍ ‍

National Institute on Aging (NIA). NIA supports projects addressing HIV-associated co-occurring conditions in midlife and older age, spanning the NIH Stage Model from basic science (Stage 0) through intervention development and refinement (Stage 1) to implementation (Stage V). Areas of interest: the etiologies and pathogenesis of these conditions, including the roles of chronic immune activation and antiretroviral and other drug toxic effects; optimizing medications, care coordination, and behavioral and social interventions to improve outcomes, function, and quality of life; and developing, testing, implementing, and scaling evidence-based interventions that address poor outcomes. Contact: Marcel E. Salive, MD, MPH.

‍ ‍

National Institute on Drug Abuse (NIDA). NIDA seeks interdisciplinary research on how drug use, addiction, and HIV interact across the lifespan. Named examples: how HIV, ART, and polysubstance use affect brain function, behavior, mood, sleep, pain, and cognition; molecular, neurochemical, cellular, and circuit functions underpinning HIV and co-occurring substance use disorders; shared pathways linking substance use, HIV, stress, trauma, and mental health conditions; individual and community factors affecting HIV prevention, care engagement, and ART adherence, with focus on improving access in underserved populations; integrated interventions addressing HIV, SUD, HCV, and co-occurring mental health conditions; and basic, clinical, and translational research on treatment of SUD and overdose in people with HIV. NIDA states it may dedicate available funds to this topic area and may give special consideration to meritorious applications in it.

‍ ‍

National Institute of Mental Health (NIMH). NIMH is interested in interdisciplinary biological and behavioral approaches to the neuropsychiatric mechanisms behind central nervous system comorbidities in people with HIV across the lifespan; how HIV biology, treatment exposures, and psychosocial burden converge on shared pathways driving neurocognitive and mental health disorders, in order to inform early intervention and scalable whole-person care models; and multidisciplinary implementation research identifying barriers to neurocognitive and mental health diagnosis and treatment in people with HIV, with emphasis on community engagement and sustainable care delivery. Contacts: Vasudev Rao, MBBS, MS, and Teri Senn, PhD. Note that NIMH's standing small business program already names technologies addressing basic, behavioral, and implementation science related to people living with HIV as an interest area, which makes it an unusually natural home for an SBIR application under this topic.

‍ ‍

National Institute of Allergy and Infectious Diseases (NIAID). NIAID is interested in coinfections affecting people with HIV across the lifespan, from infant through adult, and encourages multidisciplinary applications addressing the impact of stigma and other intersecting behavioral, biological, and health system factors on diagnosis, prevention, and treatment. The named coinfections are tuberculosis, viral hepatitis, and sexually transmitted infections. Contact: Robin E. Huebner, PhD, MPH.

‍ ‍

National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK). NIDDK supports basic, clinical, and implementation science examining the impact of HIV on organs, tissues, and biological systems, including person-oriented comorbidity research. Priorities include enteropathy and gastrointestinal homeostasis; liver diseases and viral hepatitis coinfections; digestive diseases, nutrition, obesity, diabetes, and related complications; and kidney, urologic, and hematologic diseases that may present differently or follow altered clinical courses in the context of HIV. On the clinical side, NIDDK wants work that improves implementation and delivery of evidence-based care and develops strategies to improve HIV diagnosis and progression. Studies addressing social, behavioral, and environmental factors influencing HIV and comorbidities in diabetes, digestive, and kidney disease are named as high priority, particularly regarding disease severity and treatment adherence. Contacts: Deepak Nihalani, Khoa Nguyen, and Minnjuan Flournoy Floyd.

‍ ‍

National Institute on Alcohol Abuse and Alcoholism (NIAAA). NIAAA notes that heavy alcohol use, including alcohol use disorder, interacts with both behavioral risk and organ pathophysiology in people living with HIV, accelerating physiological and physical vulnerability, affecting medication adherence and toxicities, and complicating care. Research should improve understanding of the pathophysiology of alcohol-associated comorbidities; develop biomedical and behavioral approaches to restore alcohol-induced organ dysfunction; and implement interventions addressing alcohol and associated mental health, substance use, comorbidities, coinfections, and complications in vulnerable populations. Named complications include cardiovascular disease, metabolic disorders, neurocognitive impairment, and cellular and immune dysfunction. Contact: Kendall Bryant, PhD.

‍ ‍

National Center for Complementary and Integrative Health (NCCIH). NCCIH supports research on complementary and integrative health approaches for symptom management in people living with HIV, framing HIV as a chronic multisystem condition with complex symptoms including pain, fatigue, and neurocognitive and mental health challenges that suit a Whole Person Health approach. Priorities: testing complementary and integrative interventions such as mind-body approaches and natural products to address symptom clusters and improve function and quality of life; elucidating biological, behavioral, and psychosocial mechanisms including inflammation, neuroimmune, and stress pathways, and identifying biomarkers and patient characteristics; integrating these approaches into HIV care through pragmatic and hybrid effectiveness-implementation studies and scalable delivery models; and evaluating risks such as drug and herb interactions, synthesizing evidence, and developing guidance for informed decision-making. NCCIH states it may give special consideration to meritorious applications in this topic area. Contact: Lanay Mudd, PhD.

‍ ‍

National Institute of Dental and Craniofacial Research (NIDCR). NIDCR supports interdisciplinary research on shared risk factors influencing the onset and progression of HIV-associated comorbidities in the oral and craniofacial complex across the lifespan. Areas of interest: mechanisms of HIV-related oral disease, including immune dysregulation, inflammation, and ART effects; biological, behavioral, and contextual risk factors linking oral and systemic comorbidities and coinfections, including HPV-associated cancer and metabolic and inflammatory diseases; interdisciplinary preventive, diagnostic, and treatment approaches, including probiotics, mucosal immunity modifiers, early cancer detection, and management of oral and salivary gland complications; and integration of oral health into the multidisciplinary HIV care continuum. NIDCR states it may give special consideration to meritorious applications in this topic area. Contact: NIDCR Division of Extramural Research.

‍ ‍

National Institute of Arthritis and Musculoskeletal and Skin Diseases (NIAMS). NIAMS seeks research on HIV-associated comorbidities affecting the musculoskeletal system, skin, and systemic rheumatic diseases, and encourages studies of how HIV infection, ART, and host or viral factors contribute to early onset, acceleration, or worsening of NIAMS-relevant comorbidities. Named conditions include musculoskeletal pain; muscle diseases such as sarcopenia and cachexia; cartilage degeneration and osteoarthritis; osteoporosis, osteopenia, and fractures; arthritis and other rheumatic diseases; and dermatologic manifestations. NIAMS supports basic, translational, and clinical research characterizing the burden, trajectory, and risk of these conditions across the lifespan, and states that priority is given to implementation science projects that develop, test, and scale multidisciplinary whole-person care models integrating musculoskeletal, rheumatic, and skin health into HIV prevention and treatment settings. Contact: Heiyoung Park, PhD. Important operational note for small businesses: NIAMS does not accept clinical trial applications under the SBIR parent announcement.

‍ ‍

Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD). NICHD is listed as a participating ICO with a scientific contact, Sonia Lee, PhD, but has not published a topic-specific scope statement. Given the topic's explicit attention to HIV-exposed uninfected children and to outcomes across the lifespan, pediatric, maternal, and developmental angles are clearly in play, but this is an Institute where a pre-submission conversation is not optional.

‍ ‍

Office of Behavioral and Social Sciences Research (OBSSR). Participating, with Cathy Maulsby, PhD, as contact. OBSSR does not award grants.

‍ ‍

Office of Disease Prevention (ODP). ODP is particularly interested in innovative prevention research using rigorous study design, measurement, and analysis methods to test interventions, implementation strategies, and multidisciplinary care approaches that prevent co-occurring conditions in people with HIV across the lifespan. ODP does not award grants. Contact: JoyAnn Courtney, PhD.

‍ ‍

Office of Research on Women's Health (ORWH). ORWH is interested in research projects addressing HIV-associated co-occurring conditions in women. ORWH does not award grants. Contact: Balkissa Ouattara, MD, PhD, MPH.

‍ ‍

Tribal Health Research Office (THRO). Participating, with Sheila Caldwell, PhD, and Christopher Barnhart, PhD, as contacts. THRO does not award grants.

‍ ‍

Email addresses for every contact are published on the NIH topic page. Note carefully that five of the sixteen participating ICOs are offices that cannot fund anything. Your application still has to land on the mission of an Institute or Center that writes checks.

‍ ‍

Where Does a Small Business Actually Fit?

‍ ‍

This is the honest part, and it is the question a founder should ask before spending 150 hours on an application.

‍ ‍

A large share of what this topic describes is classic investigator-initiated academic research: mechanistic biology, cohort analyses, implementation science trials in health systems. Much of that is better suited to an R01 than to an SBIR. NIH SBIR and STTR awards fund research and development toward a commercially viable product or service. If the deliverable at the end of your project is a paper and a set of findings rather than something a customer buys, an SBIR reviewer will say so.

‍ ‍

The good news is that this topic contains an unusual density of genuine product opportunities, because "shared factors, multi-organ effects, early screening, and scalable care models" is a description of things that get built and sold. The strongest small business fits:

‍ ‍

Multi-condition risk prediction and early screening. The topic's central scientific bet is that shared upstream factors drive several downstream comorbidities. A validated tool that stratifies risk across cardiometabolic, renal, hepatic, neurocognitive, and oncologic outcomes at once maps directly onto NHLBI, NIDDK, NIA, and NCI interests simultaneously, and onto the MAHA prevention framing.

‍ ‍

Point-of-care and decentralized diagnostics. Coinfection detection for TB, viral hepatitis, and STIs sits squarely in NIAID's stated scope. Oral and salivary diagnostics sit in NIDCR's. Detection of subclinical HLBS disease is a named NHLBI priority.

‍ ‍

Biomarkers of accelerated aging, immune activation, and organ injury. NIA names chronic immune activation and drug toxic effects explicitly. NHLBI names hematopoietic changes. NCCIH names inflammation, neuroimmune, and stress mechanisms plus biomarker identification.

‍ ‍

Digital therapeutics and integrated behavioral health. NIDA's interest in integrated interventions addressing HIV, SUD, HCV, and co-occurring mental health conditions is one of the clearest commercial openings in the entire topic, and NIDA is one of the two Institutes signaling possible dedicated funds. NIMH's interest in scalable whole-person care models points the same direction.

‍ ‍

Adherence, polypharmacy, and interaction safety. ART adherence is named by NIDA. Medication optimization is named by NIA. Drug and herb interaction risk is named by NCCIH. Prescribing patterns are a named MAHA workstream. Clinical decision support that manages ART alongside comorbidity medications and supplements has an unusually broad set of sponsors.

‍ ‍

Care coordination and integration platforms. Nearly every ICO in the topic asks for something that in practice requires software: integrating oral health into the HIV care continuum, integrating musculoskeletal and skin health, bundling cancer and HIV interventions, coordinating care across infectious disease, endocrinology, psychiatry, pharmacy, and community health. Note that NIAMS explicitly prioritizes implementation science for exactly this, which is rare.

‍ ‍

Biosensors and wearables. NIAAA's standing small business priorities already include transdermal and wearable alcohol monitoring, which lands directly on this topic's alcohol and organ dysfunction thread.

‍ ‍

Therapeutics. Treatments targeting shared inflammatory or metabolic pathways, or targeting a specific comorbidity in the HIV context, fit multiple Institutes. This is the longest and most capital-intensive path, and Fast-Track or Direct to Phase II with a clear regulatory strategy is usually the right structure.

‍ ‍

One structural constraint to plan around. The topic repeatedly references low and middle-income settings and global context. The SBIR parent announcement does not permit foreign subawards or subcontracts, and applications involving them will not be considered for funding. If your work is genuinely LMIC-facing, the research plan has to be structured so that the funded work happens domestically, with international relevance argued rather than internationally performed. This is a common and avoidable reason HIV-focused SBIR applications get administratively withdrawn.

‍ ‍

STTR is worth a hard look here. This topic asks for multidisciplinary teams with complementary expertise and meaningful community engagement, which is exactly what the STTR mechanism is built for. Under STTR, a formal collaboration with a university or nonprofit research institution is required, and the Principal Investigator may be primarily employed by either the company or the research partner. For a company that needs an academic HIV clinician, an implementation scientist, or a community-engaged research partner in order to be credible, STTR (PA-27-102) is often the stronger vehicle than SBIR.

‍ ‍

How Much Funding Would I Receive?

‍ ‍

There is no funding amount attached to the Highlighted Topic itself. Budgets are set by the parent announcement you apply through and by the Institute that funds you.

‍ ‍

Under the current NIH SBIR and STTR parent announcements, standard guidelines provide:

‍ ‍

• Phase I: up to $323,090, typically over one to two years

• Phase II: up to $2,153,927, typically over two to three years

• Fast-Track: combines Phase I and Phase II in one application and one review

• Direct to Phase II: available under SBIR for companies that have already established feasibility

• Phase IIB (PA-27-101): follow-on funding beyond Phase II, with budgets that can run substantially larger

• Commercialization Readiness Pilot: late-stage, milestone-driven support, up to the SBA statutory maximum of $4,191,495 at NCI, with amounts varying by Institute

‍ ‍

Several Institutes participating in this topic hold approval to exceed the standard caps. NIA allows up to $700,000 for Phase I and $3 million for Phase II on Alzheimer's disease and AD-related dementias, and up to $500,000 and $2.5 million for other projects in its mission space, which is directly relevant given the topic's inclusion of neurocognitive comorbidity and vascular contributions to dementia. NIGMS allows Phase IIB budgets up to $3 million, or $4 million for Strategic Breakthrough awards involving clinical trials. NCI supports CRP projects up to the statutory maximum plus up to $500,000 for technical assistance.

‍ ‍

Cost sharing is not required. Phase I generally requires at least 67 percent of the research effort to be performed by the small business; Phase II generally requires at least 50 percent.

‍ ‍

Full Institute-by-Institute budget detail is in our NIH SBIR program executive summary.

‍ ‍

What Could I Use the Funding For?

‍ ‍

Funds support research and development toward a commercially viable product or service aligned with the mission of a participating Institute or Center. Allowable costs include personnel, materials, prototype fabrication, assay development, validation studies, testing, intellectual property protection, and other direct R&D expenses.

‍ ‍

Phase II, Phase IIB, and CRP funds may additionally cover scale-up, clinical validation, regulatory preparation including IND and IDE-enabling studies, and commercialization activities.

‍ ‍

Whether you can run a clinical trial depends entirely on which Institute funds you. Most ICOs with a direct clinical mission accept clinical trials, including NCI, NHLBI, NIA, NICHD, NIDA, NIMH, and NIDDK, all of which participate in this topic. NIAMS and NIDCR, which also participate in this topic, do not accept clinical trials under the SBIR parent announcement. If your project involves human subjects, confirm your target Institute's specific policy before you build the research plan around it.

‍ ‍

What Is the Timeline?

‍ ‍

Highlighted Topic dates

‍ ‍

• Posted: July 28, 2026

• Expires: July 28, 2028

‍ ‍

SBIR and STTR standard receipt dates (PA-27-100 and PA-27-102)

‍ ‍

• September 5, 2026. This falls on a Saturday, and Labor Day is Monday, September 7, so submissions are accepted through Tuesday, September 8, 2026.

• January 5, 2027

• April 5, 2027

• The same September, January, and April cycle continues into 2027 and 2028 while the topic remains active. September 5, 2027 falls on a Sunday ahead of Labor Day, so that cycle effectively closes Tuesday, September 7, 2027.

‍ ‍

All applications are due by 5:00 PM local time of the applicant organization.

‍ ‍

Review and award timeline for the September 2026 cycle

‍ ‍

• Scientific merit review: November 2026

• Advisory council review: January 2027

• Earliest project start date: April 2027

‍ ‍

Review and award timeline for the January 2027 cycle

‍ ‍

• Scientific merit review: March 2027

• Advisory council review: May 2027

• Earliest project start date: July 2027

‍ ‍

Review and award timeline for the April 2027 cycle

‍ ‍

• Scientific merit review: July 2027

• Advisory council review: August 2027

• Earliest project start date: December 2027

‍ ‍

Two timing changes that specifically affect HIV-focused applicants

‍ ‍

First, HHS eliminated dedicated AIDS and AIDS-related SBIR and STTR due dates for applications due on or after May 25, 2026. HIV-focused companies previously had access to a separate offset schedule that routed applications into AIDS-specific review. That is gone. You now compete on the standard small business calendar, which makes Institute alignment and cycle selection more consequential than before.

‍ ‍

Second, NIH tightened its late application policy under NOT-OD-26-064, effective for due dates on or after May 25, 2026. Small business applications no longer receive the discretionary late submission window. Plan to submit early enough to resolve eRA Commons validation errors before the deadline, not after it.

‍ ‍

Practical planning guidance. Budget at least twelve weeks of lead time before your target due date, and more if your federal registrations are not already complete. SAM.gov, UEI, SBA Company Registry, eRA Commons, and Grants.gov registrations can take four to six weeks on their own and must be finished before you can submit anything. For a first-time applicant, expect 120 to 200 hours of total effort on a competitive submission.

‍ ‍

Who Is Eligible to Apply?

‍ ‍

Eligibility comes from the parent announcement, not from the topic. Applicants must be U.S. small business concerns that are:

‍ ‍

• Organized for profit with a place of business located in the United States

• At or below 500 employees, including affiliates

• More than 50 percent owned and controlled by U.S. citizens or permanent resident aliens, by qualifying U.S. entities, or by a combination

‍ ‍

For STTR, the company must also have a formal collaboration with a U.S. research institution, with at least 40 percent of the work performed by the small business and at least 30 percent by the research institution.

‍ ‍

Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted.

‍ ‍

Are There Restrictions I Should Know About?

‍ ‍

• Only U.S. small business concerns are eligible; foreign organizations are not.

• Applications involving foreign subawards or subcontracts will not be considered for funding. This is the single most important constraint to plan around given the topic's global framing.

• Your application must be relevant to at least one participating Institute or Center that awards grants. Five of the participating offices in this topic, OAR, OBSSR, ODP, ORWH, and THRO, do not.

• Clinical trials are not accepted by every Institute. Among the ICOs in this topic, NIAMS and NIDCR do not accept them under the SBIR parent announcement.

• Duplicate or highly overlapping applications submitted under multiple HHS announcements are not permitted.

• Companies must satisfy applicable SBA performance benchmark requirements, including the Phase I to Phase II transition rate benchmark and the Phase II commercialization rate benchmark for companies with substantial award histories.

• Additional national security, foreign relationship, and foreign ownership disclosure requirements apply and may result in denial of award. The 2026 reauthorization tightened foreign risk management and due diligence review, and this screening now sits inside the review critical path rather than beside it.

• Cost sharing is not required.

• Applying under a Highlighted Topic does not change referral or review, and does not guarantee that any funds have been set aside.

‍ ‍

What Kind of Application Is Likely to Win Here?

‍ ‍

NIH reviews small business applications on Significance, Investigators, Innovation, Approach, and Environment, with commercialization potential specifically evaluated for Phase II and Fast-Track. Within this topic, four things separate the competitive applications from the rest.

‍ ‍

One: you picked the right Institute, and you picked it before you started writing. Sixteen ICOs participating means sixteen possible framings of the same technology, and the framing determines which study section reviews you and which budget pays for you. A cardiometabolic risk tool assigned to NHLBI is a different application than the same tool assigned to NIDDK. Email the named contact, describe the technology in a paragraph, and ask directly whether it fits and which mechanism they would suggest. That conversation is free and it is the highest-return hour you will spend.

‍ ‍

Two: you actually addressed shared factors, not one disease. The intellectual center of this topic is that comorbidities in people with HIV intersect and share upstream drivers. An application that addresses a single condition in people with HIV is responsive to that Institute's general mission but not distinctively responsive to this topic. An application that shows how one intervention affects multiple outcomes through a shared mechanism is.

‍ ‍

Three: you took implementation seriously. NIH says outright that traditional disease-specific models insufficiently capture multilevel implementation determinants, and NIAMS goes further by prioritizing implementation science outright. For a company, this translates into concrete asks: who delivers this, in what clinic, paid for by whom, fitting into what workflow, sustained how after the grant ends. Applications that treat adoption as somebody else's problem read as naive here.

‍ ‍

Four: your team is genuinely multidisciplinary, and your community engagement is real. Multiple Program Directors and Principal Investigators with complementary expertise are strongly encouraged. Meaningful community engagement is strongly encouraged. Reviewers in this space are well practiced at spotting a letter of support from a community organization that has no role in the actual research plan.

Frequently Asked Questions

Is this a Notice of Funding Opportunity I can apply to directly?

No. This is an NIH Highlighted Topic, which is a published statement of scientific priority rather than a solicitation. There is no application package and no separate deadline. You apply through a broad NIH funding opportunity, and for small businesses that means the SBIR parent announcement PA-27-100 or the STTR parent announcement PA-27-102.

How much funding is available under this Highlighted Topic?

The topic itself carries no funding amount. Your budget is governed by the parent announcement you apply through: under standard guidelines, up to $323,090 for SBIR Phase I and up to $2,153,927 for Phase II, with several Institutes approved to exceed those caps. NHLBI and NIDA both state they may dedicate available funds to this topic area, subject to available funds, the number of meritorious applications, and competing priorities.

Does applying under this Highlighted Topic improve my chances?

Not in review. NIH states that applying in a Highlighted Topic area will not affect referral or review of applications. Three participating ICOs, NCCIH, NIDA, and NIDCR, state they may give special consideration to meritorious applications in this topic area, and two, NHLBI and NIDA, state they may dedicate funds. The real advantage is informational: sixteen ICOs have documented what they want and named the staff to call about it.

What are the deadlines?

The topic is open from July 28, 2026 through July 28, 2028. SBIR and STTR standard receipt dates are September 5, 2026, January 5, 2027, and April 5, 2027, with the cycle continuing while the topic remains active. Because September 5, 2026 falls on a Saturday before Labor Day, that cycle accepts submissions through Tuesday, September 8, 2026. All applications are due by 5:00 PM local time of the applicant organization.

Are there separate AIDS-specific due dates for HIV-related SBIR applications?

Not anymore. HHS eliminated dedicated AIDS and AIDS-related SBIR and STTR due dates for applications due on or after May 25, 2026. HIV-focused companies now submit on the standard small business schedule and compete within it.

Which NIH Institutes participate in this topic?

Sixteen ICOs: the Office of AIDS Research as lead, plus NCCIH, NCI, NHLBI, NIA, NIAAA, NIAID, NIAMS, NICHD, NIDA, NIDCR, NIDDK, NIMH, OBSSR, ODP, ORWH, and THRO. Five of those, OAR, OBSSR, ODP, ORWH, and THRO, are offices that do not award grants, so your application must also be relevant to a participating Institute or Center that does.

Who is eligible to apply?

For-profit U.S. small business concerns with 500 or fewer employees including affiliates, more than 50 percent owned and controlled by U.S. citizens or permanent residents or by qualifying U.S. entities. Foreign organizations are not eligible, and foreign subawards and subcontracts are not permitted.

My work focuses on low and middle-income settings, which the topic specifically mentions. Can SBIR fund that?

Only with careful structuring. The topic references low and middle-income settings and HIV-exposed uninfected children in those settings, but the SBIR parent announcement prohibits foreign subawards and subcontracts. The funded research has to be performed domestically. Global relevance can be argued in the significance and commercialization sections; it cannot be delivered through an international subaward under this mechanism.

Can I run a clinical trial with this funding?

It depends on the Institute. Most participating ICOs with a direct clinical mission accept clinical trials, including NCI, NHLBI, NIA, NICHD, NIDA, NIMH, and NIDDK. NIAMS and NIDCR, both participating in this topic, do not accept clinical trials under the SBIR parent announcement. Confirm your target Institute's policy before designing the project.

Should I apply for SBIR or STTR?

SBIR if your company performs the majority of the research and your Principal Investigator is primarily employed by the company. STTR if the project depends on a formal collaboration with a university or nonprofit research institution. Given that this topic explicitly asks for multidisciplinary teams and community engagement, STTR is often the better structural fit, and STTR allows the Principal Investigator to be primarily employed by either the company or the research partner.

Where do I reference the Highlighted Topic in my application?

Unlike a Notice of Special Interest, a Highlighted Topic has no notice number to enter in the Agency Routing Identifier field. Make the alignment explicit in your cover letter and in your Specific Aims, and confirm handling with the program officer at your target Institute before you submit.

What does NIH mean by "shared factors" and why does it matter commercially?

NIH's point is that many comorbidities in people with HIV intersect and share risk factors before diverging into disease-specific trajectories, using metabolic syndrome raising diabetes, cardiovascular, and kidney disease risk as one example and coinfection-driven cancer risk as another. Commercially this is favorable, because a technology addressing an upstream shared factor has a larger addressable market and a stronger clinical value proposition than a single-indication tool, and it can be framed to fit several Institutes at once.

How long will it take me to prepare an application?

For a first-time applicant, expect 120 to 200 hours in total. Start at least twelve weeks before your target due date. Federal registrations across SAM.gov, UEI, SBA Company Registry, eRA Commons, and Grants.gov can take four to six weeks on their own and must be complete before submission.

What happens if I miss the deadline?

Nothing good. NIH tightened its late application policy for due dates on or after May 25, 2026, and small business applications no longer receive the discretionary late submission window. Build in time to fix validation errors before the deadline rather than after it.

Is this topic connected to a broader federal initiative?

Yes. NIH issued it as part of the Make America Healthy Again initiative, and the topic page names the specific MAHA workstreams it aligns with, including the NIH Chronic Disease Initiative, the Whole-Person-Health approach, prescribing patterns and mental health, Food for Health, nutrition and metabolic health, the oral health and systemic disease connection, the Gut Microbiome Research Initiative, longitudinal cohort research, clinical trial networks, and mental health and addiction research. Framing your significance section in that vocabulary is a low-cost, high-signal move.

How Can BW&CO Help?

BW&CO is a non-dilutive federal funding advisory firm. We have helped clients secure more than $350 million in federal funding, and we specialize in exactly the problem this topic creates: a broad scientific priority with sixteen possible sponsors, no dedicated money, and no obvious front door.

We can:

• Identify the right Institute and the right mechanism for your technology, Phase I, Phase II, Fast-Track, Direct to Phase II, Phase IIB, or CRP, and position you with the program officer who controls that budget.

• Triple your likelihood of success through proven strategy and insider-aligned proposal development.

• Reduce your time spent on the proposal by 50 to 80 percent, so your team stays focused on the technology and the company.

• Structure the research plan so that foreign collaboration, clinical trial sequencing, and registration timelines do not sink an otherwise fundable application.

USSOCOM sUMS-G Rapid Capability Assessment: The Complete Guide for Ground Robotics Companies

Below is a brief summary. Please check the full solicitation before applying (link in resources section).

Quick Answer: What Is the sUMS-G Rapid Capability Assessment?

The sUMS-G Rapid Capability Assessment is an open Call on the Vulcan platform seeking commercially available small-to-medium Uncrewed Ground Systems (UGS) and Unmanned Ground Vehicles (UGV) that can contribute to the U.S. Special Operations Command small Uncrewed Multi-Domain Systems (sUMS) Ground Capability Portfolio. The Call opened 16 August 2026 and closes 01 October 2026 at 22:59 CDT. Companies respond by submitting a Scout Card through Vulcan, then completing a structured self-assessment of their system against a small tactical robotic ecosystem architecture. The engagement objective is market research, which means no funding is awarded directly from this Call. Selection can lead to a demonstration invitation and downstream consideration for prototype agreements, Other Transaction Agreements, SBIR or STTR topics, CRADAs, or FAR-based procurement.

The central question the Government is asking is direct: which small-to-medium UGS can solve the identified mission-thread Key Technical Problem and provide a viable capability for the sUMS Ground Capability Portfolio?

If your company builds throwable robots, packable or man-packable UGVs, quadrupeds, tracked or wheeled tactical UGVs, or purpose-built robotic platforms with manipulators, this is the single most important open door into the SOF ground robotics portfolio in fiscal year 2026.

At a Glance

‍ ‍

Call name: sUMS-G Rapid Capability Assessment

‍ ‍

Sponsor: U.S. Special Operations Command (USSOCOM), small Uncrewed Multi-Domain Systems (sUMS) Ground Capability Portfolio, aligned to the Program Executive Office for Tactical Information Systems (PEO-TIS) Remote Capabilities program office

‍ ‍

Platform: Vulcan, at vulcan-sof.com, the SOF enterprise technology scouting platform and the front end for Engage SOF (eSOF)

‍ ‍

Engagement objective: Market research

‍ ‍

Open date: 16 August 2026, 23:00 CDT

‍ ‍

Deadline: 01 October 2026, 22:59 CDT

‍ ‍

Submission vehicle: Scout Card, plus a structured self-assessment and supporting evidence

‍ ‍

Funding attached to this Call: None published. This is a market research and assessment engagement, not a solicitation with an award ceiling.

‍ ‍

Classification level: Unclassified only

‍ ‍

Who should respond: Commercial UGS and UGV manufacturers, robotics integrators, autonomy software companies with a hosted platform, payload and manipulator developers with a fielded host vehicle

‍ ‍

What disqualifies you fastest: Submitting a concept, a roadmap, or a future configuration instead of a system you can put on the ground and demonstrate now

‍ ‍

Why This Call Matters More Than a Typical RFI

‍ ‍

USSOCOM validated its ground robotics requirements in March 2026. That validation is the gate that opens formal solicitation activity, and the portfolio lead told industry at SOF Week 2026 that solicitations would flow across the different categories of ground robotic products in the cycle that followed. The Remote Capabilities office also posted a Ground Robotics Element and Team Man Portable Systems capability assessment event on its fiscal year 2026 industry slide. This Call is the market research front end of that activity.

‍ ‍

Two structural facts make the ground portfolio unusual. First, PEO-TIS does not own most of the platforms its sensors ride on, with one stated exception: the ground robotics portfolio, where the office does provide the platform. That makes the ground portfolio a direct platform buyer rather than a payload integrator working through another program office. Second, the office described itself as being in a constant state of market research and running roughly three RFIs per year per system category, moving faster when the operational environment changes. Companies that get into the assessment record now are positioned for the next several cycles, not just this one.

‍ ‍

The buying posture briefed to industry was blunt. The office is looking to field what it selects. In the portfolio lead's framing, if development work is needed, that development work will most likely happen after fielding, usually as software modification or SOF-peculiar adaptation such as marinizing a system for maritime special operations use. The standing guidance to vendors was to bring mature items that are tested, that can be produced and scaled, and that operate in contested environments.

‍ ‍

Translated for a startup: this is a fielding pipeline, not a research program. Maturity beats ambition here.

‍ ‍

The sUMS Ground Capability Portfolio Structure

‍ ‍

The portfolio is organized into categories by size, transportability, and mission role. Understanding which category your system belongs in is the first strategic decision you make, because the Government assesses systems inside a category and against a mission thread, not against the entire robotics market.

‍ ‍

T-0.1, Training and Experimentation. Modular interface and drone docking systems. This category supports modular integration, concepts, and experimentation and does not fit the primary operational portfolio categories. If your product is an interface standard, a docking or launch module, a payload carrier, or a test article that enables integration rather than delivering an operational effect, this is your lane.

‍ ‍

E-0.1, Throwables. Throwable, ruggedized recon and ISR robots. Small spherical or impact-tolerant platforms deployed by hand into a structure, a stairwell, a tunnel, or a vehicle. Assessment attention lands on survivability at impact, self-righting, camera and audio fidelity, and how quickly an operator gets usable video.

‍ ‍

E-0.2, Packable. Compact tracked or wheeled UGVs that fit in a pack. The emphasis is on compactness and rapid deployment without dedicated transport.

‍ ‍

E-0.3, Man-Packable. Crawling and articulated platforms carried by a single operator. Serpentine and segmented designs for confined space, void, tunnel, and rubble access sit here.

‍ ‍

E-1.1, Element-Man-Packable. Quadruped and legged platforms at the element level. Stair climbing, rubble traverse, and payload carriage on legs. This is the fastest-growing commercial segment and the most crowded category in the portfolio, which raises the evidentiary bar rather than lowering it.

‍ ‍

E-1.2, Team-Man-Packable. Team-level, team-packable wheeled or tracked UGVs, typically multi-wheeled platforms carrying mission payloads for a whole team rather than one operator.

‍ ‍

E-2.0, Heavy. Heavy payload, high capacity tracked platforms. Logistics carriage, casualty movement, heavy sensor masts, and breaching or engineering support at scale.

‍ ‍

E-3.0, Dedicated Purpose. Specialized mission platforms with dedicated capability, including manipulator-equipped systems for tasks that a general purpose UGV cannot perform.

‍ ‍

The portfolio banner is scalable, modular, mission ready, and the framing question the Government keeps returning to is the right UGS or UGV for the right mission with the right effect. Your submission is stronger when it names the mission thread it serves and stays in its category, and weaker when it claims to cover four categories at once.

‍ ‍

What the Government Is Actually Looking For

‍ ‍

Available now, not conceptual

‍ ‍

The Call is explicit that vendors should describe the capability actually available for demonstration, not a conceptual or future configuration. This is the single most consequential instruction in the document. A Scout Card that describes a system arriving next year is not a responsive submission, and the assessment structure is designed to surface the difference.

‍ ‍

The complete system, not the chassis

‍ ‍

Responses should clearly identify the system configuration, hardware, software and firmware, payloads, communications, autonomy features, support equipment, and other components included in the proposed capability. Two implications follow. First, the boundaries of what you are offering must be unambiguous, because the Government is assessing a deployable capability rather than a vehicle. Second, everything you omit is read as absent. If the operator control unit, the charging solution, the spares kit, the training materials, and the transit case are part of the capability, list them.

‍ ‍

A structured self-assessment against a defined architecture

‍ ‍

After submission, vendors complete a structured self-assessment based on the small tactical robotic ecosystem architecture developed by Dr. Jon M. Hackett, whose doctoral research addressed small tactical robotics applications and who serves as a program manager in the intelligent robotic autonomous systems space. The assessment characterizes the capability across a defined set of dimensions:

‍ ‍

1. Intended mission

2. Operating environment

3. Human-machine interaction

4. Mobility

5. Power

6. Communications

7. Autonomy

8. Interfaces

9. Supportability

10. Resilience

11. Integration with other systems

‍ ‍

This is not a marketing questionnaire. It is a comparative instrument, and it is the mechanism by which the Government builds an apples-to-apples picture of a fragmented commercial market. Prepare for it before you submit, because your answers become part of the assessment record attached to your Scout Card.

‍ ‍

Practical guidance on the harder dimensions:

‍ ‍

Human-machine interaction. Expect scrutiny on operator workload, one-to-many control, glove and night operation, latency, and whether the operator can reconfigure the system at their own level rather than sending it back to the manufacturer.

‍ ‍

Power. Battery chemistry, standard military battery compatibility, hot swap, charge time, runtime at realistic duty cycles rather than idle, and the logistics footprint required to keep the system running for a multi-day mission.

‍ ‍

Communications. Line of sight and non line of sight performance, mesh and MANET behavior, bandwidth demand, degraded and denied operation, spectrum and waveform details, and behavior on link loss. Contested electromagnetic environments are a stated requirement across the portfolio, not a differentiator.

‍ ‍

Autonomy. Where the autonomy sits, what it does without a link, what degradation looks like, and how it behaves at the edge. USSOCOM has publicly named swarm technology, decentralized control and collective intelligence, and environment-agnostic traversability as capability development areas. Vendor-locked, proprietary vertical autonomy stacks are treated as a liability across the SOF autonomy enterprise.

‍ ‍

Interfaces. This is where deals are won or lost. The command is buying sensors, payloads, radios, and autonomy as interchangeable elements of an architecture, and conformance to published standards is becoming the price of admission. The USSOCOM Modular Payload Standard, managed for the command by the Johns Hopkins University Applied Physics Laboratory, defines common interfaces and attributes for payloads and hosting platforms, and has expanded from Group 2 UAS to Groups 1 and 3, unmanned surface vessels, and dismounted applications, with a micro variant for smaller systems. The guidance from the command's chief systems engineer for Tactical Information Systems was explicit: adopt common standards, and do not arrive with a proprietary standard that locks the Government out of the interface. Document your mechanical, electrical, and data interfaces. State plainly whether they are open, licensable, or closed.

‍ ‍

Supportability and resilience. Mean time between failure and repair data, field repairability at the operator level, spares and tooling, environmental and ingress protection ratings, temperature range, EMI and EMC test results, transportability, and safety documentation.

‍ ‍

Integration with other systems. Data output formats, message standards, ATAK and common operating picture integration, edge processing, and whether your system can hand off to and receive tasking from other unmanned systems. The stated goal on the sensor side is edge processing with the least amount of data required to make a decision moving forward to the decision point, rather than everything returning to a centralized node.

‍ ‍

Evidence, tiered honestly

‍ ‍

For each material claim, vendors should be prepared to provide supporting evidence: test data, technical documentation, photographs, videos, interface information, safety documentation, or prior demonstration results. The Call requires vendors to clearly distinguish between four claim tiers:

‍ ‍

1. Demonstrated capability

2. Vendor-tested capability

3. Calculated or estimated performance

4. Planned or future capability

‍ ‍

Label every claim to the correct tier. Assessors are reading many submissions in the same category, and the fastest way to lose credibility is to present a calculated figure as a demonstrated one. A submission that is honest about tiers and thin in places reads as trustworthy. A submission that presents everything as demonstrated reads as unverified, and it will be tested at demonstration if you get that far.

‍ ‍

What the Government Will Do With Your Submission

‍ ‍

The Government may use the information and supporting evidence to inform comparative assessment, selection for demonstration, and subsequent marketplace consideration.

‍ ‍

Equally important is what the Call says it does not do. Submission or successful completion of a demonstration does not constitute operational approval, certification, fielding authorization, or a Government commitment to procure the system. Treat a favorable assessment as qualification and visibility inside the SOF enterprise, not as a contract.

‍ ‍

Assessments published in Vulcan become visible to Government users across the SOF and defense enterprise. That is the durable value of a strong submission: a well-evidenced Scout Card with a published Government assessment continues working for you across future Calls, RFIs, and program office searches long after this deadline passes.

‍ ‍

Timeline and Key Dates

‍ ‍

16 August 2026, 23:00 CDT. Call opens on Vulcan. Submissions accepted.

‍ ‍

Now through late September 2026. Build or refresh the Scout Card, assemble the evidence package, resolve export control and data rights questions, and confirm any spectrum authorizations you would need for a live demonstration.

‍ ‍

01 October 2026, 22:59 CDT. Submission deadline. This is a hard cutoff in the platform, and Vulcan has no private or draft state that holds a partial submission past the close.

‍ ‍

Following submission. Vendors complete the structured self-assessment. Expect requests for supporting evidence against material claims.

‍ ‍

After the assessment window. Government comparative assessment and downselection for demonstration. On comparable SOF assessment engagements, published assessments typically reach vendor Scout Cards on the order of twenty business days after an assessment event concludes.

‍ ‍

Downstream. Selection for a demonstration or assessment event, then negotiation of an agreement if the evaluation is favorable.

‍ ‍

Two planning notes. First, the deadline sits one day into fiscal year 2027, which means the assessment and any resulting negotiation activity happens under new-year funding. Second, if your system radiates on any frequency, approval to transmit is required before a demonstration, which may include compliance with FCC Title 47 Part 15 or a Special Temporary Authority. The FCC recommends submitting an STA request 30 to 60 days before an event. Start that clock now rather than after you receive an invitation.

‍ ‍

Funding Allowance: What Money Is and Is Not Attached

‍ ‍

Be clear-eyed here, because this is where companies misread SOF engagements most often.

‍ ‍

This Call carries no published funding ceiling and makes no award. The engagement objective is market research. You are not writing a priced proposal, and there is no dollar figure to size a budget against. What you are buying with your effort is assessment, visibility, and eligibility for the pathways below.

‍ ‍

Where the money actually appears. On SOF assessment engagements, favorably evaluated solutions move into negotiation under one or a combination of the following authorities. This is the standard path forward language used across USSOCOM assessment events run through SOFWERX:

‍ ‍

1. Business to business research and development agreement as a sub-award through the SOFWERX Partnership Intermediary Agreement, under 15 U.S. Code Section 3715

2. Other Transaction Agreement for research or prototype projects, under 10 U.S. Code Sections 4021 and 4022. An award under Section 4022 may result in a follow-on production agreement without additional competition based on successful prototype completion, against prototype criteria determined for each project

3. Procurement for experimental purposes, under 10 U.S. Code Section 4023

4. Cooperative Research and Development Agreement, under 15 U.S. Code Section 3710a

5. Prizes for advanced technology achievements under 10 U.S. Code Section 4025, or prize competitions under 15 U.S. Code Section 3719

6. FAR-based procurement contract

‍ ‍

The Section 4022 prototype-to-production path is the one worth understanding in detail. It is the mechanism by which a successful prototype effort converts into production without recompeting, and it is the reason non-traditional defense companies pursue OTAs rather than waiting for a full and open competition.

‍ ‍

The parallel non-dilutive tracks. A strong showing in this portfolio also sets up funding you pursue on your own initiative rather than waiting to be selected:

‍ ‍

1. USSOCOM SBIR and STTR, including Direct to Phase II, which allows a Phase II award without a prior Phase I when you can document that the feasibility objectives have already been met. For a company with a fielded UGV, Direct to Phase II is frequently the right entry point rather than Phase I

2. Department of War SBIR and STTR release cycles, where SBIR Phase I awards commonly land in the low hundreds of thousands and Phase II awards run into the low millions against the current statutory ceiling, with topic-specific variation

3. The USSOCOM Broad Agency Announcement, a standing mechanism for unsolicited proposals against command interests

4. SOFWERX technical experimentation and assessment events, which run on a white paper submission and review cycle culminating in live assessment with operators in the loop

5. Cross-service and cross-agency opportunities in ground autonomy, including Army and Marine Corps robotics programs and DIU solicitations, where the same evidence package you build for this Call is directly reusable

‍ ‍

Budget the real cost of participation. Submission itself is free. What costs money is being demonstration-ready: shipping and travel to an assessment event, an operator and a maintainer to run the system, spares, a demonstration article you can afford to break, spectrum authorization, and the engineering time to produce interface documentation and test data you may not currently have written down. Companies that win these engagements have that package on the shelf before the Call opens.

‍ ‍

Eligibility and Access Requirements

‍ ‍

Vulcan registration. You need a Vulcan account at vulcan-sof.com, registered with your official organizational email address rather than a personal address. Registration establishes access type as commercial, academic, non-profit, or government, and your organizational affiliation is verified. Set this up first if you do not already have an account, because verification takes time you will not have on 30 September.

‍ ‍

Unclassified only. All submissions must be at the unclassified level. Do not put classified or export-restricted technical detail into a Scout Card. If your differentiator cannot be described unclassified, describe the capability and offer the detail through an appropriate channel.

‍ ‍

U.S. persons and U.S. industry. SOF assessment engagements are routinely restricted to U.S. persons or U.S. industry. Confirm the specific restriction in the Call document before investing.

‍ ‍

Export control. ITAR and export licensing exposure is real for ground robotics with military applications, particularly where foreign nationals are employed on the effort. USSOCOM SBIR practice, for example, requires a firm employing foreign nationals on an ITAR topic to possess an export license to receive an award. Resolve your position before you are asked.

‍ ‍

Cybersecurity. Awardees may need to comply with NIST SP 800-171 for protecting Controlled Unclassified Information in non-federal systems. If you are pre-revenue on defense work, understand this as a cost of doing business downstream rather than a surprise during negotiation.

‍ ‍

Business size. There is no small business set-aside on a market research Call of this type. Startups and large primes are assessed on technical merit inside the same category, which is favorable for a mature small company with a real product and unfavorable for a company selling a roadmap.

‍ ‍

How to Submit

‍ ‍

1. Register or log in at vulcan-sof.com using your organizational email address

2. Navigate to Calls in the top menu and open the Call titled sUMS-G Rapid Capability Assessment

3. Decide whether to submit an existing Scout Card or create a new one. Vulcan lets you tailor elements of a submission to the specific context of each Call without maintaining multiple Scout Cards for the same solution

4. Do not create a duplicate Scout Card for a solution you have already carded. Duplicates will be removed. Tailor the existing card to this Call instead

5. Complete the card with a precise capability description, system boundaries, photographs, video, interface information, applicable tags, technology readiness level, and any Government references

6. Complete the structured self-assessment when prompted

7. Assemble and be ready to provide the supporting evidence package against every material claim

8. Submit before 01 October 2026 at 22:59 CDT. Cards remain editable up to the close, and there is no draft state that survives the deadline

‍ ‍

Questions on the platform itself go to the Vulcan support team at support@vulcan-sof.com.

‍ ‍

The Five Mistakes That Sink Ground Robotics Submissions

‍ ‍

Selling the roadmap. The Call asks for what is available for demonstration. A future configuration described as though it exists fails the assessment and damages credibility for the next Call.

‍ ‍

Category sprawl. Claiming that one platform serves throwable, man-packable, team-packable, and heavy roles at once reads as a company that has not chosen a mission thread. Pick the category where you are strongest and win it.

‍ ‍

Undocumented interfaces. A proprietary interface with no published specification, or an unwillingness to discuss licensing, is now a first-order disqualifier in a portfolio built on modular payload standards.

‍ ‍

Unlabeled claim tiers. Presenting calculated endurance, estimated range, or simulated autonomy performance without labeling it as such is the most common failure mode in structured self-assessments.

‍ ‍

Ignoring supportability. Companies over-invest in mobility demonstration video and under-invest in the mean time between failure data, spares posture, field repair procedures, and safety documentation that determine whether a system can actually be fielded. The office intends to field what it selects, and supportability is what fielding turns on.

‍ ‍

Who Should Respond

‍ ‍

You are a strong fit if you have a fielded or demonstration-ready UGS or UGV in one of the portfolio categories, you can document performance with test data, and you can put an operator and a system in a room in front of an evaluation panel within a few months.

‍ ‍

You are a plausible fit if you build payloads, manipulators, autonomy software, power systems, or comms modules and you can present them integrated on a host platform. Partnering matters here. The command has repeatedly urged vendors to team with one another, because a modular, standards-based architecture rewards integrated, compliant solutions over isolated components.

‍ ‍

You are a poor fit if your system exists as a CAD model, a simulation, or a single hand-built prototype that has never left a controlled environment. Use the time to pursue SBIR, STTR, or BAA funding to reach demonstration maturity, then enter the portfolio at the next assessment cycle.

Frequently Asked Questions

What is the deadline for the sUMS-G Rapid Capability Assessment? Submissions close 01 October 2026 at 22:59 CDT. The Call opened 16 August 2026 at 23:00 CDT.

Is there funding attached to this Call? No. The engagement objective is market research, and no funding ceiling is published. Favorably assessed companies may be selected for demonstration and then move into negotiation under a range of authorities including Other Transaction Agreements for prototypes, sub-awards through the SOFWERX Partnership Intermediary Agreement, procurement for experimental purposes, CRADAs, prize authorities, or FAR-based contracts.

How much funding could this eventually lead to? There is no published figure for this Call. Downstream award size depends entirely on the vehicle. Prototype OTAs under 10 U.S. Code Section 4022 can carry follow-on production without recompetition. USSOCOM SBIR Phase II and Direct to Phase II awards typically run into the low millions against the current statutory ceiling. Treat this Call as qualification, and pursue priced funding vehicles in parallel.

What is a Scout Card? A Scout Card is the standard capability submission format on Vulcan. It summarizes and depicts your capability, including a description of what differentiates it, technology readiness level, media, tags, and supporting documentation. Government users across the SOF and defense enterprise can search Scout Cards, and published Government assessments attach to the card.

Can I reuse an existing Scout Card? Yes, and you should. Vulcan allows you to tailor elements of a submission to the specific context of each Call without maintaining multiple cards for the same solution. Do not create a duplicate card for a solution you have already carded, because duplicates will be removed.

What does sUMS stand for? Small Uncrewed Multi-Domain Systems. It is a USSOCOM line of effort covering Group 1 and Group 2 unmanned aerial systems and unmanned ground systems, delivering tactical organic robotic and modular payload solutions to the SOF operator. sUMS-G refers to the ground portion of that portfolio.

Which office runs this? The sUMS portfolio sits under the Remote Capabilities program office within the USSOCOM Program Executive Office for Tactical Information Systems, part of SOF Acquisition, Technology and Logistics. Remote Capabilities holds the mandate for unmanned systems across space, air, ground, and maritime domains.

Do I need to be a small business? No. There is no small business set-aside on this Call. Submissions are assessed on technical merit within a capability category.

Can a non-U.S. company respond? SOF assessment engagements are routinely limited to U.S. persons or U.S. industry, and export control rules apply to systems with military application. Confirm the specific restriction in the Call document before investing effort.

Does my system have to be a complete robot, or can I submit a payload? The Call asks for a capability available for demonstration, described as a complete configuration including hardware, software, payloads, communications, autonomy, and support equipment. A payload or software component is best submitted integrated on a host platform, ideally through a teaming arrangement. The command has actively encouraged vendors to partner rather than pitching isolated components.

What is the structured self-assessment based on? It is based on the small tactical robotic ecosystem architecture developed by Dr. Jon M. Hackett. It characterizes your capability across intended mission, operating environment, human-machine interaction, mobility, power, communications, autonomy, interfaces, supportability, resilience, and integration with other systems.

What evidence do I need? Be prepared to substantiate every material claim with test data, technical documentation, photographs, video, interface information, safety documentation, or prior demonstration results. Each claim must be labeled as demonstrated capability, vendor-tested capability, calculated or estimated performance, or planned or future capability.

Does a successful demonstration mean I have been selected or approved? No. Submission or successful completion of a demonstration does not constitute operational approval, certification, fielding authorization, or a commitment to procure. It qualifies you for comparative assessment, demonstration selection, and marketplace consideration.

How mature does my system need to be? Mature enough to demonstrate now. USSOCOM's stated posture is to field what it selects, with SOF-peculiar development, usually software modification or platform adaptation, occurring after fielding rather than before. Systems that are finicky at the tactical edge are not competitive.

Do standards compliance and open interfaces matter? Substantially. The command is building a modular architecture around the USSOCOM Modular Payload Standard, managed for the command by Johns Hopkins University Applied Physics Laboratory, and it has told industry directly not to arrive with proprietary standards that lock the Government out of the interface. Document your interfaces and be prepared to discuss access.

What if my system transmits on a radio frequency? Any developmental device radiating on a given frequency or band needs prior approval to transmit, which may include FCC Title 47 Part 15 compliance or a Special Temporary Authority. The FCC recommends submitting an STA request 30 to 60 days before an event, so begin that process before you receive a demonstration invitation.

Where do I submit? On the Vulcan platform at vulcan-sof.com, under the Call titled sUMS-G Rapid Capability Assessment. Register with your official organizational email address if you do not have an account.

What happens if I miss the deadline? The Remote Capabilities office described itself as being in a constant state of market research and typically running about three RFIs per year per system category, with additional activity when operational needs shift. A ground robotics assessment event and a small UAS assessment event were both on the fiscal year 2026 and 2027 industry slides. Missing this Call is not fatal, but it delays you by a cycle and cedes the assessment record to competitors in your category.

Get Your Submission Assessed Before the Government Does

The companies that convert SOF assessment engagements into agreements are the ones that walk in with the evidence package already built: labeled claim tiers, documented interfaces, test data behind every number, a clear category, and a named mission thread.

BW&CO helps deep-tech, robotics, autonomy, and dual-use founders position for non-dilutive federal funding and build the technical and strategic packages that agencies act on. Innovation Funding Simplified. More than $350M in funding secured for our clients.

If you are weighing whether your UGS or UGV is ready for the sUMS-G Call, or you want to run a parallel SBIR, STTR, Direct to Phase II, or BAA strategy alongside it, let's talk before the 01 October deadline.

Medical Extraction BAA (MED FCD): Complete Guide for Startups and Small Businesses

Below is a brief summary. Please check the full solicitation before applying (link in resources section).

Quick Answer

The Medical Extraction Broad Agency Announcement (BAA) is an open call from the U.S. Army Medical Future Capability Directorate (MED FCD) for technologies that can retrieve, secure, and move wounded Soldiers out of contested battlefields without exposing rescue personnel to unnecessary risk. It is issued under the broader Army Medical Operational Capabilities for 2040 BAA, submissions are made through the USSOCOM-sponsored Vulcan platform as a Scout Card with a quad chart and white paper, and the call is open on a rolling basis from August 25, 2026 through December 31, 2026 at 10:59 PM CST. One point matters more than any other for planning purposes: MED FCD has stated that it does not currently have the resources or authorization to award or fund contracts under this announcement. This is a visibility, evaluation, and experimentation pathway, not a funded solicitation.

That does not make it low value. It makes it a different kind of asset. Read on for what the Army is actually asking for, how the process works, what it costs you to participate, and how companies convert a MED FCD engagement into real dollars from other parts of the Department.

Quick reference facts

• Opportunity name: Medical Extraction BAA (MED FCD)

• Parent announcement: Army Medical Operational Capabilities for 2040 Broad Agency Announcement

• Sponsoring organization: U.S. Army Medical Capability Future Capability Directorate (MED FCD)

• Higher headquarters: Futures and Concepts Command, U.S. Army Futures Command

• Submission platform: Vulcan (vulcan-sof.com)

• Submission vehicle: Vulcan Scout Card, tailored to this specific Call

• Required attachments: Quad chart and white paper

• Open date: August 25, 2026 at 1:00 PM CDT

• Close date: December 31, 2026 at 10:59 PM CST

• Submission window: Rolling and open ended for the full period, no single due date for the initial submission

• Funding available under this BAA: None. MED FCD states it cannot directly award or fund contracts

• Engagement objectives listed by the Government: FAR acquisition, capability demonstration, technology experimentation, market research

• Number of areas of interest: One, focused on medical extraction in contested environments

• Anticipated next steps for strong submissions: Virtual briefing with MED FCD, invitation to a technology experimentation event, and possible requests for a formal white paper, statement of work, and cost proposal

• Award guarantee: None. Progression through evaluation phases does not imply or guarantee a contract

• Data protections cited: Trade Secrets Act, Economic Espionage Act, FOIA Exemption 4, Executive Order 12600

What is the Medical Extraction BAA?

A Broad Agency Announcement is a standing government invitation for ideas rather than a competition for a fixed pot of money against a fixed statement of work. The Medical Extraction BAA is a focused Call inside the Army Medical Operational Capabilities for 2040 BAA, and its purpose is to find technologies and concepts that help tactical medical units at Army Corps level and below clear the battlefield, meaning the evacuation of the wounded, ill, and injured.

MED FCD uses the announcement to build a picture of what industry can actually deliver, to identify candidates worth putting in front of senior military leadership, and to select technologies for operational demonstration and experimentation. The Government has been unusually direct that it will amend or update its technical focus areas during the active period and may issue a separate call for follow-on white papers at any time, so the scope you see today can shift before December.

Who is MED FCD and why does this BAA exist?

MED FCD is the Army organization responsible for developing medical concepts and requirements for the future force. Future Capability Directorates sit under Futures and Concepts Command within Army Futures Command, and they drive functional transformation by shaping concepts, requirements, and experimentation. The medical directorate, previously known as MED CDID, has long been associated with the Army Medical Center of Excellence at Joint Base San Antonio.

The practical implication for a founder is important. MED FCD is a requirements and concepts organization, not a program executive office and not a contracting activity. It does not buy things. It defines what the Army needs, validates that industry can build it, and hands that evidence to the organizations that do buy things. Companies that understand this distinction write far better submissions, because they stop pitching a sale and start offering proof for a requirement.

The problem statement in plain language

Enemy action in a modern fight is expected to break the evacuation chain. Fires, maneuver, electronic warfare, and contested airspace will slow or stop the movement of casualties to a medical treatment facility. Three things happen as a result. Treatment is delayed. Consumption of medical supplies at forward locations goes up because casualties are held longer, which compounds an already strained resupply problem. And the cumulative effect reduces the return to duty rate while increasing preventable deaths.

Urban terrain makes it worse. Routes are blocked by rubble, craters, and debris. Casualties have to be pulled out of collapsed buildings. Medical units may have to interact with civilian medical infrastructure and handle large numbers of injured civilians and enemy prisoners of war alongside their own wounded.

Layered on top of that is the risk to the rescue team. Today, extracting a non-ambulatory casualty from rugged terrain or a compromised urban area usually means putting multiple healthy Soldiers into the same danger that produced the casualty, often on foot, often slowly, often within observation of the adversary. That is the specific gap this BAA is trying to close.

Detailed overview of what MED FCD is looking for

The announcement contains a single area of interest, and every requirement in it is worth reading as a hard filter on your solution.

MED FCD is seeking innovative technological capabilities to facilitate medical extractions in highly contested environments where maintaining a low operational profile is critical. Proposed solutions must be capable of retrieving and securing ambulatory and non-ambulatory casualties who cannot climb or physically assist in their own loading, which reduces the exposure of accompanying rescue personnel. The system must demonstrate high mobility across rugged, unstructured terrain while maintaining rigorous patient stabilization, and the extraction and transport process must inflict no further harm to the casualty.

The five requirements your submission has to answer directly

1. Self loading without casualty participation. The system has to get an unconscious or immobilized 95th percentile Soldier with full kit off the ground or out of a structure and secured, without that Soldier climbing, gripping, rolling, or helping in any way. This is the single most common place where otherwise strong robotics submissions fail. If your concept assumes the casualty can pull themselves onto a platform, it does not meet the requirement as written.

2. Reduced exposure of rescue personnel. The Government is asking for low profile, automated, or semi autonomous capability. Every Soldier your system removes from the point of injury is a measurable benefit, so quantify it. If current practice requires four Soldiers for eight minutes at the casualty location and your system requires one Soldier for ninety seconds, or none at all, say so in exactly those terms.

3. Low operational profile. Signature management is treated as a critical attribute, not a nice to have. Address visual, acoustic, thermal, and electromagnetic signature. Address behavior in GPS denied and communications degraded conditions, because a system that needs a continuous high bandwidth link to a distant operator is not low profile in an electronic warfare environment.

4. High mobility over unstructured terrain. Rubble, craters, stairs, slopes, mud, snow, doorways, breach points, and the interior of a partially collapsed building. State your ground pressure, obstacle and step height, gap crossing, gradeability, speed with a loaded litter, endurance in hours or kilometers, and how the system is transported to the point of employment.

5. Patient stabilization with no further harm. This is a clinical requirement, not an engineering afterthought. Address spinal motion restriction, immobilization, ride quality and vibration and shock transmitted to the casualty, thermal protection, airway position, tourniquet and dressing integrity during movement, hemorrhage control during transfer, and compatibility with standard litters, SKEDs, and monitoring equipment. Evidence from a clinician, biomechanical data, or cadaveric or manikin testing carries real weight here.

Technology areas that fit this area of interest

The Government notes that its categories provide context rather than a comprehensive list, so adjacent concepts are welcome. Solutions that typically map well include:

• Uncrewed ground vehicles configured for casualty extraction and casualty carry

• Robotic or powered litter systems, including self loading litter and transfer mechanisms

• Autonomous or teleoperated casualty evacuation platforms with a medical payload

• Mechanical casualty retrieval devices such as winch, drag, sled, grapple, and conveyor based loading systems

• Exoskeletons and powered assist devices that let one or two Soldiers move a casualty that would normally take four

• Low signature aerial lift and resupply platforms with validated casualty carriage

• Casualty packaging, immobilization, and litter interface systems designed for machine handling

• Subterranean and collapsed structure retrieval systems

• Casualty location, triage, and tagging sensors that feed the extraction decision

• Autonomy stacks for GPS denied navigation, obstacle negotiation, and human machine teaming with a medic in the loop

• En route patient monitoring, telemedicine, and automated care integrated into the extraction platform

• Power, energy, and thermal management that supports realistic mission endurance

• Modular kits that convert existing tactical vehicles or robotic platforms into casualty carriers

Themes worth weaving into your narrative

MED FCD thinks in concepts, doctrine, and requirements, so the language of the Army medical modernization enterprise helps your submission land. Useful framing includes multi domain operations, prolonged casualty care when evacuation is delayed well beyond the traditional golden hour, return to duty rate, preventable death, Soldier load and burden, the DOTMLPF-P implications of fielding your system, joint interoperability, training burden on a combat medic, sustainment and repairability in the field, and transportability inside existing formations.

Be equally clear about what you do not do. A submission that claims to solve the entire casualty evacuation problem reads as unserious. The BAA states plainly that a white paper attempting to address the whole scope of the technology described will most likely be rejected.

Funding allowance

This section deserves careful attention, because it is the part most often misread.

There is no funding attached to this BAA. MED FCD has stated in the announcement that while it is an integral part of finding technology solutions for Army requirements, it does not currently possess the resources or authorization to directly award or fund contracts. Selected participants may later be asked for formal white papers, technical statements of work, and cost proposals, but the announcement is explicit that progression through those technical assessment phases is solely for evaluation purposes and does not guarantee or imply a future contract award.

No dollar ceiling, floor, or period of performance is published. Because the Government has not specified a dollar range, there is no target award size to design toward. When a rough order of magnitude cost is requested in a white paper, it should be a defensible estimate of what your proposed effort actually costs, consistent with the level of work you are proposing, including profit or fee if any. Do not inflate it to look substantial and do not deflate it to look cheap. An unrealistic ROM is one of the fastest ways to lose credibility with an evaluator who has seen hundreds of these.

What the Government does offer instead of money:

• Direct evaluation of your capability by the Army organization that writes medical requirements

• Virtual briefings with MED FCD for high potential candidates

• Invitations to technology experimentation events where your system is exercised against realistic conditions

• Operational demonstrations facilitated by the directorate

• Exposure of your capability to senior military leadership and joint service partners, explicitly for the purpose of maximizing visibility for potential external government funding

• A persistent Scout Card profile in Vulcan, which remains discoverable by government users across the ecosystem beyond this single call

• Government feedback that can materially sharpen your product roadmap and your future proposals

What participation costs you. Budget realistically for internal engineering and clinical time to prepare the quad chart and white paper, executive time for a virtual briefing, and, if you are selected for experimentation, travel, shipping, prototype hardware, spares, and on site technical personnel. Experimentation events are typically an unfunded expense for the vendor. Companies that treat this as an internal research and development investment tend to be satisfied with the outcome. Companies that treat it as a revenue event tend not to be.

How this becomes real money. A validated requirement plus documented government interest is the raw material for funded pursuits elsewhere in the Department. Common pathways for Army medical extraction technology include Army SBIR and STTR topics and the xTech prize competitions, the Medical Technology Enterprise Consortium and other other transaction authority consortia, U.S. Army Medical Research and Development Command broad agency announcements, congressionally directed medical research programs, Defense Health Agency and service SBIR programs, Defense Innovation Unit solicitations, and program office funding once a program of record forms around the requirement. A MED FCD demonstration, a letter of support, or a named government sponsor changes the strength of every one of those applications. If your goal is non dilutive capital, the sequence that works is engagement first, evidence second, funded solicitation third.

Timeline

• August 25, 2026 at 1:00 PM CDT: Announcement opens for submissions

• August 25 through December 31, 2026: Rolling submission window. Scout Cards may be submitted at any time during the period

• Any time during the active period: The Government may amend or update technical focus areas, and may issue a separate call for follow on white papers

• Continuous: MED FCD evaluates submitted Scout Cards against the BAA criteria and contacts high potential candidates

• After initial contact: Virtual briefings and technology experimentation coordination, with possible requests for formal white papers, statements of work, and cost proposals

• December 31, 2026 at 10:59 PM CST: Announcement closes unless amended

Recommended working schedule

Because the call is rolling and evaluation is continuous, earlier submissions get more calendar time in front of evaluators and more opportunity to be matched to an experimentation event. A workable internal schedule looks like this:

• Week 1: Confirm fit against the five hard requirements. Decide which single slice of the problem you are addressing. Register or refresh your Vulcan account

• Week 2: Build or update the Scout Card, gather performance data, capture imagery and video of the system operating

• Week 3: Draft the quad chart and white paper. Have a clinician or former medic review the patient stabilization claims

• Week 4: Internal red team review against the area of interest language line by line, then submit

• Ongoing: Prepare a fifteen minute virtual briefing deck in advance so you can respond to interest within days rather than weeks

Do not wait until December. A submission that arrives in the final week has almost no runway for the briefing and experimentation activity that creates the value.

How to submit, step by step

1. Register on Vulcan at vulcan-sof.com. Vulcan is a technology scouting platform sponsored by USSOCOM and used by organizations across the Department of Defense, including this Army medical directorate. Account setup and validation take time, so start here.

2. Build or select a Scout Card. A Scout Card is a persistent, structured profile of a single solution. If your technology is already in Vulcan, select the existing card rather than creating a new one.

3. Do not create duplicates. The Government is explicit that duplicate Scout Cards for the same solution will be removed. Vulcan allows you to tailor elements of a submission to the context of a specific Call without maintaining multiple cards for the same solution.

4. Tailor the submission to this Call. Use the area of interest language. An evaluator should be able to see the mapping between your capability and the five requirements without hunting for it.

5. Attach the quad chart. PowerPoint is preferred. Word and PDF are acceptable as long as the file opens and reads cleanly.

6. Attach the white paper, following the Section A through D format below. Reference the BAA number in the subject or title of the response. Submit as PDF or Microsoft Word.

7. Submit before the deadline and be ready to respond quickly if MED FCD reaches out. Contact information for the contracting officers is provided to interested companies by MED FCD when they are asked to submit a proposal, so you will not have a named point of contact before that happens.

White paper format

The announcement specifies four sections.

Section A. Title, the technology area of interest you are responding to, period of performance, estimated cost of the task, name and address of the offeror, technical and contracting points of contact, telephone and fax numbers.

Section B. Task objective with a description of the work to be performed.

Section C. Technical summary and proposed deliverables. Include the anticipated period of performance and a rough order of magnitude cost, which is the total cost plus profit or fee if any. This is not a cost proposal and does not include the material that normally accompanies one. Provide a short technical description of the concepts and the plans to accomplish the technical objectives, briefly describe the technologies to be pursued, and identify any independent research and development work already underway in your company that has direct application. Address only the specific part of the BAA you intend to accomplish. A white paper that tries to cover the whole scope will most likely be rejected.

Section D. Quad chart. The quad has to present the capability as a single page snapshot and must visually convey the concept of employment, meaning what the capability will actually accomplish in operational terms, a description of the technical effort needed to get there, the benefit to MED FCD, your technical and management resources, costs, and schedule with major milestones.

Practical guidance on the quad chart

The quad is usually what determines whether anyone reads the white paper. Treat the concept of employment quadrant as the most important real estate on the page and use a real image or a clear graphic of the system moving a casualty in the environment described, not a rendering on a white background. Put numbers on the page. Weight, dimensions, casualty capacity, terrain performance, endurance, current technology readiness level, and the count of Soldiers required at the point of injury with and without your system. Leave the marketing adjectives out entirely.

Intellectual property and proprietary information

The Government acknowledges that information provided in response to this BAA is presented in confidence and may contain trade secret, commercial, or financial information, and it agrees to protect that information from unauthorized disclosure to the maximum extent permitted or required by the Trade Secrets Act at 18 U.S.C. 1905, the Economic Espionage Act at 18 U.S.C. 1831 and following, Freedom of Information Act Exemption 4 at 5 U.S.C. 552(b)(4), Executive Order 12600 covering pre disclosure notification procedures for confidential commercial information, and any other applicable statute or regulation.

Sound practice still applies. Mark proprietary material clearly and consistently on every page and every file. Describe your approach at a level that demonstrates feasibility without disclosing the specific implementation details that constitute your competitive advantage. Confirm export control and International Traffic in Arms Regulations status before you transmit technical data, especially if you have foreign nationals on your engineering team or a foreign parent entity. Keep in mind that a Scout Card is designed to be discoverable by government users across the Vulcan ecosystem, which is a benefit for visibility and a reason to be deliberate about what goes into the card versus what stays in a marked attachment.

Who should respond

This BAA is a strong fit if you are a robotics, autonomy, uncrewed systems, exoskeleton, medical device, or casualty handling company with hardware you can point at, even at low technology readiness level, and if you can absorb the cost of an unfunded engagement in exchange for requirements insight and senior leader visibility. It is a particularly good fit for dual use companies from search and rescue, mining, wildland firefighting, industrial rescue, and civilian emergency medical services, where the physics of moving an incapacitated human through bad terrain is already your core problem.

It is a poor fit if you need a contract award inside the next twelve months to survive, if your concept exists only as a slide deck with no path to a demonstrable prototype, if your solution requires the casualty to assist in loading, or if you cannot support travel and hardware costs for an experimentation event.

Common reasons submissions fail

• Trying to address the entire scope of the announcement instead of one specific slice

• Assuming casualty participation in loading, which contradicts the stated requirement

• Treating patient stabilization as a secondary feature with no clinical evidence behind it

• Ignoring signature management and degraded communications entirely

• A quad chart full of adjectives and no numbers

• No concept of employment, so an evaluator cannot picture the system in use by a real medical unit

• An unrealistic rough order of magnitude cost, in either direction

• Submitting a generic corporate capability statement rather than a tailored response to this Call

• Duplicate Scout Cards, which the Government will remove

• Submitting in the last two weeks, leaving no time for briefing or experimentation

How to convert this engagement into funding

Treat the MED FCD submission as the first move in a sequence rather than the end of one. Submit early and get on the calendar for a virtual briefing. Ask directly, during that briefing, which organizations own the transition path for the capability and whether the directorate can identify a government sponsor. Say yes to experimentation and show up prepared, because performance in front of operators is the evidence that funded solicitations reward. Capture everything that comes out of the engagement, including feedback, performance data, imagery, and any written expression of interest. Then use it. That package strengthens an Army SBIR or STTR proposal, a consortium white paper, an other transaction authority pursuit, a medical research program application, or a direct approach to a program office, and it does so far more than a well written proposal with no government relationship behind it.

Frequently asked questions

Is there funding available under the Medical Extraction BAA?

No. MED FCD has stated that it does not currently possess the resources or authorization to directly award or fund contracts under this announcement. Selection and progression through evaluation phases is for assessment purposes only and does not guarantee or imply a future contract award.

What is the deadline for the Medical Extraction BAA?

The announcement closes on December 31, 2026 at 10:59 PM CST unless it is amended. Submissions opened on August 25, 2026 at 1:00 PM CDT and are accepted on a rolling basis throughout that period.

Who issued the Medical Extraction BAA?

The U.S. Army Medical Capability Future Capability Directorate, known as MED FCD, which sits under Futures and Concepts Command within U.S. Army Futures Command. It is issued as a Call under the Army Medical Operational Capabilities for 2040 Broad Agency Announcement.

What do I have to submit?

A Vulcan Scout Card tailored to this Call, with a quad chart and a white paper attached. The white paper follows a four part format covering administrative data, task objective, technical summary with rough order of magnitude cost, and the quad chart itself.

What is a Vulcan Scout Card?

A Scout Card is a persistent structured profile of a single technology solution inside the Vulcan platform, which is a technology scouting environment sponsored by USSOCOM and used by government organizations across the Department of Defense. The card makes your capability discoverable by government users beyond the specific Call you submit it to, and attachments provide the specificity that a particular Call requires.

Can I submit the same Scout Card to multiple calls?

Yes, and you should. Vulcan lets you tailor elements of a submission to the context of each Call without maintaining multiple cards for the same solution. Duplicate cards for the same solution will be removed.

What technology readiness level does MED FCD expect?

The announcement does not specify a required technology readiness level. Because the objective is evaluation, experimentation, and demonstration, concepts from early prototype through advanced prototype are generally in scope, but you need something more than a paper concept if you want to reach an experimentation event. State your current level honestly and show the path to the next one.

Does my system have to be fully autonomous?

No. The announcement asks for low profile, automated, or semi autonomous capability. Teleoperated and Soldier assisted systems are responsive as long as they reduce the exposure of rescue personnel and can secure a casualty who cannot assist in loading.

Does the system have to handle non ambulatory casualties?

Yes. This is the central requirement. The system must be capable of retrieving and securing both ambulatory and non ambulatory casualties who are unable to climb or physically assist in their own loading. A solution that depends on casualty participation does not meet the stated requirement.

Do I need a security clearance or a government sponsor to submit?

The announcement does not state a clearance requirement for submission. Later experimentation events, particularly classified ones, can require cleared personnel, and government sponsorship becomes relevant as a technology moves into selection and experimentation. Plan for that possibility rather than assuming it.

Are small businesses and startups eligible?

Yes. Broad agency announcements of this type are open to a wide range of respondents, and this Call is explicitly aimed at innovative capability wherever it exists. Small businesses, startups, universities, and nontraditional defense entrants are all appropriate respondents. If you anticipate any future contracting relationship, get your System for Award Management registration, unique entity identifier, and CAGE code in order early.

Can non U.S. companies respond?

Foreign entities should proceed carefully. The announcement does not publish an eligibility restriction, but export control, International Traffic in Arms Regulations, foreign ownership control and influence considerations, and any subsequent contracting action will all shape what is actually possible. Companies with a U.S. subsidiary and U.S. based engineering are in a materially stronger position.

Will my proprietary information be protected?

The Government acknowledges that responses are presented in confidence and commits to protecting trade secret, commercial, and financial information to the maximum extent permitted by the Trade Secrets Act, the Economic Espionage Act, FOIA Exemption 4, and Executive Order 12600. You are still responsible for marking proprietary material clearly and for calibrating how much implementation detail you disclose.

What happens after I submit?

MED FCD evaluates Scout Cards against the BAA criteria on a continuous basis and contacts high potential candidates to coordinate virtual briefings or technology experimentation events. Selected participants may be asked for formal white papers, technical statements of work, and cost proposals. None of this guarantees an award.

How much cost should I put in the rough order of magnitude estimate?

No dollar range is published, so base the number on the actual cost of the specific effort you are proposing, including profit or fee if any, and make sure it is consistent with the scope of work described. The estimate should look like something an engineer built, not something a salesperson chose.

Is it worth responding if there is no money?

For most hardware companies working on casualty movement, yes, provided you go in with the right expectation. You are buying direct access to the organization that writes Army medical requirements, structured feedback on your capability, a chance to demonstrate in front of operators and senior leaders, and a documented government relationship that materially improves your odds in the funded solicitations that follow. You are paying for it with engineering time and, if selected, travel and hardware. Decide that trade deliberately.

How do I find funded opportunities for this technology instead?

Army SBIR and STTR topics, xTech competitions, the Medical Technology Enterprise Consortium and other other transaction authority consortia, U.S. Army Medical Research and Development Command announcements, congressionally directed medical research programs, service and Defense Health Agency SBIR programs, and Defense Innovation Unit solicitations all fund technology in this space. Which one fits depends on your maturity, your entity type, and whether you already have a government sponsor.

Can BW&CO help me respond?

Yes. We help deep tech, medtech, and defense adjacent companies decide whether an opportunity like this is worth their time, position the capability against the stated requirement, build the quad chart and white paper, prepare for the government briefing, and sequence the engagement into funded non dilutive pursuits afterward.

Next step

If you are building casualty extraction, robotic mobility, exoskeleton, or en route care technology and want a candid read on whether this BAA is worth your engineering hours, we will tell you straight. BW&CO has helped clients secure more than $350 million in non dilutive funding, and the first conversation is about fit, not a pitch.

Innovation Funding Simplified.