The Drone Dominance Program has produced the largest unit-count signal in recent DoD small-UAS procurement: 30,000 systems purchased, 60,000 more planned, and an advanced market commitment covering more than 200,000 Group 1 platforms. DIBC's BES-26-01 solicitation asks for domestic prototype manufacturing of military-critical 18650 and 21700 cells at 50 MWh per year within two years, against a stated objective of 3 GWh.
A cell manufacturer deciding whether to fund a defense-grade cylindrical line has to convert those numbers into a production forecast. The conversion needs four fields that neither program publishes: watt-hours per platform, named cell suppliers, configuration persistence across delivery tranches, and committed government offtake against the capacity target. BES-26-01 quad-charts closed July 17, and no award has appeared publicly through August 14. Anyone who responded made a capital decision measured in years against demand data that does not exist in public form. I have looked for these fields across SAM.gov notices, DIU announcements, the DIBC solicitation documents, DoD press releases, SEC filings, and attributable defense trade reporting from June through August 2026. They are not there.
This is an information-architecture problem before it is a policy problem. DDP publishes aircraft counts. DIBC publishes a capacity objective. The data that would let a production planner move from one to the other sits in neither.
What DDP discloses at the battery level
DDP's July 1 announcement names 19 companies advancing to Gauntlet II, each required to deliver 120 drones with lethality payloads. For those 19, the public record carries no battery energy per aircraft, no named cell manufacturer or chemistry, no pack configuration, and no BMS revision attached to the 120-unit orders. The Phase I RFS required bills of materials from vendors; those are held privately. The scope of that statement is public sources only, which is the point. The fields a supplier would build a forecast from are the fields the program does not release.
One partial example shows both what is available and what is not. Trade reporting identified Mountain Horse Solutions/AG3Labs as entering the Draganfly Flex FPV family. Draganfly's product sheet gives pack sizes by variant: 6S 7,000 mAh on the Flex 5 and 7, 12S 7,000 mAh on the Flex 10, 12S 14,000 mAh on the Flex 13, or roughly 155 to 622 Wh depending on which one flies. Nothing public establishes which variant was delivered, whether the commercial specification governed the competition configuration, or who supplied the cells. Product-family data is available; order-specific demand is not.
The rest of the roster follows the same pattern. Red Cat confirmed that Teal Drones advanced to Gauntlet II without battery detail. Vector announced its 120-system delivery and referenced resilient supply chains without naming a cell or a pack configuration. The Phase I solicitation and the Lethality Prize Challenge on SAM.gov contain no battery CLIN, energy requirement, cell specification, or named battery supplier.
Design evolution versus specification freeze
The Phase I RFS states that "vendors may evolve their design between deliveries internal to each phase," subject to holding performance and to preserving or increasing the percentage of U.S.-sourced components. Phase I ran in two delivery batches, with vendors providing a delta package covering changes that affect system operation or field maintenance.
Nothing in that structure treats a battery or cell change differently from an airframe, motor, or payload change. The RFS does not require the cell maker, chemistry, pack BOM, or BMS revision to persist across batches, does not designate a new cell part number, production site, or electrolyte formulation as a reassessment trigger, and does not commit the government to publishing configuration-level change histories.
For a rapid-fielding effort optimizing on operational capability, that is sound design. Vendors iterate, capability improves, and selection runs on demonstrated performance. Cell manufacturing capital requires the inverse: a frozen specification and forecastable MWh over a horizon long enough to amortize a line. Under the RFS a vendor can change its battery between batch one and batch two under the same general constraints that govern any other component. The consequence for a supplier is that a 120-unit order is not a committed demand signal for any particular cell.
Within-phase flexibility is one source of drift. Down-selection is another. Gauntlet II narrows 19 companies to a smaller cohort, so a cell manufacturer who identifies the battery in one vendor's Phase I delivery has no assurance that the vendor advances, and the vendor that does advance may change cells between phases. Planning production against DDP volume would require knowing which platform-battery pairing survives selection, holds across phases, and carries into production quantities. Public sources do not support that at any gate.
This sits on top of the qualification problem I covered in issue 4. Navy S9310-AQ-SAF-010 Rev 3 treats a cell-manufacturer change as Class I, which puts recertification on a timeline measured in years. A supplier weighing a defense line needs confidence that the volume waiting on the far side of an 18-to-36-month qualification still exists under the same configuration long enough to pay back the investment. DDP's public structure supplies neither the volume commitment nor the configuration assurance.
The arithmetic, such as it is
With no platform-specific energy data from DDP, the conversion has to run on commercial analogues. Published specifications for commercially available Group 1 FPV platforms bracket roughly 89 to 622 Wh per aircraft: an iFlight Chimera7 at 6S 4,000 mAh (89 Wh) at the bottom, the Draganfly Flex 13 at 12S 14,000 mAh (622 Wh) at the top.
| Low end (89 Wh) | High end (622 Wh) | |
|---|---|---|
| 200,000 aircraft | 17.8 MWh | 124.3 MWh |
| % of BES-26-01 annual target (50 MWh/yr) | 36% | 249% |
| % of 3 GWh objective | 0.6% | 4.1% |
Both columns assume one flight battery per delivered aircraft. They exclude spare packs, training consumption, qualification articles, manufacturing scrap, replacement demand, and charger or controller batteries. DDP publishes values for none of those. The RFS names batteries as an example of a common failure component relevant to the required 5% spares package, but that obligation applies to vendor-identified failure components as a group rather than as a fixed battery-spares ratio.
The arithmetic is crude on purpose. What it establishes is a scale relationship, and the relationship holds across the entire bracket: 200,000 Group 1 drones is a single-digit percentage of the 3 GWh objective even on generous assumptions.
DIBC and DDP do not reference each other
Neither the BES-26-01 RPP nor its Q&A contains the terms "Drone Dominance" or "DDP," and neither names any DoD procurement program as the demand source behind the 3 GWh objective. Asked whether the government anticipated committed offtake or a guaranteed-demand quantity, DIBC responded:
"The DoW relies on a strong Industrial Base, of which commercial application and demand is critical to long term product viability."
The answer contains no government quantity, purchasing floor, utilization commitment, or named consuming program.
The RPP lists guaranteed-price offtake and DPA Title III purchase commitments among possible funding mechanisms. Possible, not awarded. The Q&A adds that such arrangements are typically negotiated after a Phase II submission, and that award count and value depend on FY2027 appropriations.
The 3 GWh objective carries its own missing denominators. DIBC does not publish the composition of that target by program, platform, or application type, nor the expected split between defense and commercial demand. The Q&A language about commercial application and demand implies the government expects commercial volume to carry a meaningful share of it, but neither share is quantified. A respondent building a commercial-viability plan cannot determine from public sources what fraction of 3 GWh the government intends to fill through its own procurement, what fraction depends on commercial markets, or whether any specific DoD program was sized against the target at all.
I noted a structurally similar gap in issue 6, where Forge Nano's SEC filing and Samsung SDI's announced 3 GWh U.S. facility both presented nameplate capacity with no public conversion to defense demand. The DIBC case carries more weight because it is a government-initiated solicitation asking industry to build against a number the government has not decomposed.
Configuration-adjusted MWh
The metric that would join these two programs does not exist in the public record. Call it configuration-adjusted MWh: battery energy delivered over a stated planning horizon that remains attributable to one unchanged, approved platform-battery configuration, and can therefore be aggregated without assuming that qualification and compliance evidence survives a substitution.
The metric neither DDP nor DIBC publishes but both would need to connect procurement intent to supply chain investment. Volume following an undocumented configuration change begins a separate accounting bucket unless approval continuity is affirmatively established.
The approval boundary would have to identify, at minimum:
- Cell maker and part revision
- Pack BOM and assembler
- BMS hardware and firmware
- Production site or route
- Evidence owner
- Authorized platforms
- Change-notification obligation
This is an analytical construct, not a proposal. DDP does not track it and DIBC does not require it. I am naming it because its absence is what makes the conversion from "200,000 drones" to "X MWh of forecastable cell demand under configuration Y" impossible to perform from public sources.
Where the capital probably lands
If near-term MWh from DDP is small against the 3 GWh objective, and configuration persistence across delivery tranches is not assured, then DDP's immediate capital effect falls somewhere other than cell production:
- Pack integration and assembly, where vendors build or source packs for their specific platform configurations
- Assessment and test infrastructure, where qualification articles are produced and evaluated
- Provenance databases, where §4865 compliance evidence is generated and maintained
These are structurally different investments. Pack integration is lower capital, shorter lead time, and reconfigurable when the platform design moves. A cell line is higher capital, longer lead time, and needs forecastable MWh under a stable specification before anyone commits to it. DDP's current demand structure fits the first profile, which puts integrators and pack assemblers, not cell producers, in position to capture near-term program value.
Whether that sequencing is deliberate or an artifact of the demand-signal gap is not distinguishable from public documents; both readings fit the same evidence. The operational consequence is identical either way. A manufacturer evaluating BES-26-01 today cannot point to a DDP document stating how many MWh of its product will be consumed, by which platforms, in which configuration, over what period.
None of this argues the procurement is soft. Nineteen companies are building and delivering aircraft, and the unit counts are real orders. But nobody underwrites a cell line against unit counts. The conversion requires energy per platform, supplier identity, configuration persistence, and offtake, and until one of the two programs publishes them, respondents to BES-26-01 are committing capacity against demand they have to infer.
- Gauntlet II results and battery pairings: DDP schedules Gauntlet II for late August, and the planned 60,000-unit order following down-selection would be the first public opportunity to observe whether winning platforms disclose cell or pack configurations.
- BES-26-01 award status: DIBC's cylindrical-cell solicitation closed July 17, but no award appears on DIBC's awards page as of August 14, leaving the question of whether any award will include government offtake or a purchase floor.
- DDP supply-chain compliance list: The July 23 framework says DCMA will publish a non-exhaustive list of covered-country components that fail DDP standards, which would be the first public artifact connecting platform approval to specific battery-level provenance decisions.
- DFARS 2024-D011 NPRM status: The Unified Agenda still shows the §4865 implementing rule at proposed-rule stage with a July 2026 NPRM target, and its publication would determine whether DDP's program-specific battery rules align with or diverge from the government-wide compliance architecture.