WIN-T goes to the turn-in point
III Armored Corps at Fort Hood is the first unit to receive the Next Generation Command and Control baseline under the Army's consolidated fielding process. DefenseScoop reported that the corps is turning in the remaining pieces of WIN-T, the network that began fielding in 2004, and taking delivery of dismounted satellite antennas, automated network traffic management, and forward servers that process data close to the fight.
The corps is getting two of NGC2's four layers to start: infrastructure and transport. The data and application layers come "when fielded," in the words of an Army official. I Corps follows with the full stack, starting with software deliveries in October.
Transport first is the right order
This sequence is sound. Applications without a network to run on are demos. The Army spent the last year proving the network works at scale. At Project Convergence Capstone 6 it ran NGC2 at division scale in desert heat against a live opposing force, and the commanding general of the 4th Infantry Division summarized it: "functional but not optimized."
Secretary of the Army Dan Driscoll put the goal in one sentence at the same event. "The side that can sense a target, process the data, and deliver a kinetic effect the fastest, wins." Transport moves the data. The applications are what turn data into the effect.
Soldier to corps is a long distance
The Army describes NGC2 as letting every echelon, from soldier to corps, run warfighting applications and AI. At the corps headquarters that is a server room problem. At the platoon it is a different problem entirely, because the platoon is where the forward server is furthest away and the link to it is most likely to be jammed, saturated, or simply out of range.
An application designed for the command post usually assumes it can reach the data layer. Below the command post, that assumption breaks several times a day. The soldier still needs the map, the task list, the latest intelligence, and a way to report. If those disappear whenever the link does, the soldier goes back to the radio and the notebook, and the data layer never sees what the soldier saw.
What the app layer needs at the edge
Applications at the tactical edge have to run on the device, keep working when the link drops, sync with peers when the server is out of reach, and catch up with the data layer when a path returns. They have to run on the hardware the soldier is issued. And they have to respect the same data contracts the Army just aligned with industry, so what the squad generates is useful to the corps without translation.
That is the layer EdgeLance builds. It runs the mission workspace on phones, tablets, and laptops, syncs device to device across the team, and hands approved data to the enterprise when a link exists. NGC2 builds the highway. EdgeLance is designed to be what the squad drives on it, including the stretches where the highway is out.
The data layer the Army is building is the right destination for what the squad produces. The squad's job is to keep producing it while the destination is unreachable, then deliver it intact. That is the same store-and-forward continuity problem every disconnected unit already lives with, and it is why we argued earlier this year that the next C2 acquisition would be a layer.
The next fielding milestone
The Army plans to scale NGC2 across the force and add or remove vendors as it goes. The corps-level fielding shows the program can deliver. The measure that matters to a rifle platoon is whether the applications that arrive work when the platoon is on its own. That is where the next round of fielding will be judged.
We have written before about the layer between the platforms and the radios. NGC2 is the first program of record funding both ends of it at once. The middle is where the next year of fielding gets decided.