Fifteen vendors, five contracts, one commander
At AUSA last month, Col. Christopher Hill Sr. explained how the Army's Accelerated Capability Events work. Hill directs the Global-Tactical Edge Acquisition Directorate, which embeds teams in the Army's service component commands. An event starts with a problem set from the commanding general. The directorate first confirms that no portfolio acquisition executive already has a solution. Then it goes to industry and typically gets 150 to 250 responses. Fifteen vendors are invited to a soldier-led demonstration. Five receive contracts.
Those five get feedback from soldiers and from the Army Test and Evaluation Command, and 45 days to adapt before an operational assessment. The commander makes the final selection. "Our mantra is: warfighting command gets 51% of the vote," Hill said. The directorate aims to run events quarterly. One with U.S. Army Europe and Africa is slated for this month, and U.S. Army Pacific's autonomous sustainment event puts its finalists in front of soldiers at the Joint Pacific Multinational Readiness Center in Hawaii this month as well.
The test is the acquisition
The Army's own description of the model is specific about what vendors face. Each event is a 180-day sprint tied to a commanding general's demand signal. It looks for mature technology, Technology Readiness Level 7 or higher. Companies that survive the down-select spend two weeks in a soldier-led demonstration under realistic conditions. Technology that passes moves to a leave-behind period, where the unit keeps it and uses it in daily operations. Success earns an Other Transaction Agreement that lets program offices adopt and scale it.
This inverts the usual order. In a traditional program the requirement is written first and the soldier meets the product years later. Here the soldier's two weeks come first, and money follows the commander's decision. Hill described that decision as the moment he comes in with dollars. For a buyer, it is a cheap way to find out what a product does outside a conference room.
What two weeks with soldiers does to software
Hardware tends to fail in visible ways. It overheats, breaks, or runs out of battery. Software fails more quietly, and a soldier-led event is good at finding the quiet failures. The application that worked in the booth needs an account server the training area cannot reach. Setup takes a vendor engineer forty minutes and a soldier an afternoon. The map loads at the command post and thins out at the observation post. The AI feature turns out to be a call to a data center.
The leave-behind period is the harder half. The vendor goes home and the product stays. Whatever the field service representative was quietly doing during the demonstration now has to be done by a specialist with a full day of other work. Software that survives that period can be installed, updated, and recovered by the unit, and it keeps its data and its functions when the link drops.
Build for the leave-behind
EdgeLance has not been through an Accelerated Capability Event, and nothing here should read otherwise. EdgeLance demonstrated at Warhacker in San Diego in June, to Defense Unicorns and to senior military leaders, and incorporated the feedback into the product. A two-week soldier-led event followed by a leave-behind is a harder test than a demonstration, and it is the right one. The product is designed for it. It runs on hardware units already carry. The mission lives on each device, so a node that loses every peer keeps its map, tasks, and AI and syncs when a peer returns. Models are staged in signed mission packs that are checked against each device before step-off.
Approval is the other gate. The September 28 counter-drone memo directs a single department-wide process to cut authority-to-operate timelines for tested, validated counter-drone systems from months to days or weeks. That memo covers one mission area. If the approach spreads, the accreditation evidence becomes part of the demonstration, and a vendor that can produce that evidence from its build will not spend its 45 days assembling a binder.
Four checks for the command running the event
A command with 51 percent of the vote can make any edge software prove itself with four checks. Pull the link for a full day and see what still works. Send the vendor's engineers home and have a soldier install it on a second device. Ask where the data is when the unit moves, and who can delete it. Ask for the record of one event from the exercise: who was tasked, what the AI said, and which source it used.
Events like these reward products that were built for the conditions the soldier lives in, and that is good for every serious vendor in the field. The whitepaper on acquisition pathways for edge platforms covers the contracting mechanics. The platform page and the capabilities show what EdgeLance runs on a unit's own hardware.