The application layer opens
On October 14 the Army made initial awards to nine companies to build applications for Next Generation Command and Control, $93.6 million across the group for the first year. The list includes General Dynamics Mission Systems, Air Space Intelligence Federal, Immersive Wisdom, LMI, Mente Systems, Stilman Advanced Strategies, Onebrief, Rune Technologies, and AIR. Two weeks earlier Anduril received $162.8 million, with options up to $1.8 billion, to keep building the common data baseline the applications run on.
Brig. Gen. Shane Taylor called the effort "a blueprint and reference point for how industry can integrate in the future." After a year of transport and data layer work, the Army is now buying the software soldiers will touch. That is a good sign for everyone building in this space.
It follows last month's first corps-level fielding of the network and transport layers.
Planning gets faster
Several names on the list are known for planning and staff work, which is where the Army's time has historically gone. Collaborative planning tools can take a course of action from days to hours, and the gains compound across a staff. Faster planning is real value and it deserves the investment.
But a plan is a set of intentions. Secretary Driscoll put the standard plainly in July: the side that can sense a target, process the data, and deliver an effect the fastest, wins. Approval is the midpoint of that chain. The clock keeps running until something moves.
We made a version of this point when we wrote that planning tools stop where the mission starts. The tools have gotten much better since. The handoff after approval has not changed much.
The gap after approval
Follow one task from an approved plan. A reconnaissance task is approved at the command post. It goes out as a line in an order, a slide, or a radio call. Someone at the company figures out which asset can take it. Someone on the ground confirms it was received, retasks a drone, and reports back by voice. The plan tool rarely learns whether the task was executed, when, or what the asset saw when it got there.
That gap between an approved task and an asset in motion is where minutes turn into hours. It is also where the network is weakest, because the assets and the people running them are at the far end of every link.
Closing it at the edge
EdgeLance is built for that gap. When a plan task is approved, it becomes a signed directive bound to its mission, so a forged or replayed order is refused. The directive is offered to the assets that can execute it, with a lease that lapses if nobody acts. As the asset works the task, field receipts and the live target track flow back onto the original plan task, where the staff can see them.
The whole chain runs on the team's own devices and mesh, so it keeps working when the link to the command post does not. EdgeLance takes the approved tasks that planning tools produce and carries them the last mile. The planning tools get faster. EdgeLance makes sure their output arrives.
Two things make that safe. Every directive is signed and bound to its mission, so a forged or replayed order is refused, and the targets it points at come from a tracker that rejects spoofed reports. The chain is built from mission blocks that share one vocabulary, so a new asset type joins without a custom integration. The longer treatment is in the whitepaper The Execution Gap.
Measure the whole chain
As NGC2 applications reach units, the most useful metric is the time from approved task to executed task, measured where the asset is. That number captures the whole kill chain the Army is trying to shorten. Planning speed is one part of it. The part that happens after approval decides most of the rest.