The Army awarded ACC Construction Co. Inc., a Georgia-based construction firm, an $87.6 million contract on July 27 to build a mission command center. The facility will be completed by July 12, 2029. That timeline and contract structure matter because they reflect the Army's evolving view of how command and control survives in a contested environment, not in centralized, vulnerable nodes, but distributed across hardened, purpose-built installations that can operate independently when the network degrades or comes under attack.
The Army Contracting Command, Detroit Arsenal, issued the firm-fixed-price contract, W912CH-26-DA079, through competitive bidding. The total action value is $87.6 million; the cumulative face value, including options, is $93 million. No installation location has been publicly named yet, though the Detroit Arsenal contracting activity typically handles ground-forces infrastructure, suggesting the facility will serve an armored or mechanized unit. That naming matters: it will signal whether the Army is hardening division-level command, a brigade support element, or forward tactical operations centers, each represents a different bet on where C2 redundancy and survivability should sit in the formation.
The construction award sits inside a larger Army infrastructure push. The Air Force Research Laboratory is simultaneously running an open solicitation for AI-based command and control capabilities designed to operate in distributed, contested environments. The two efforts are not disconnected. The AFRL solicitation targets software-layer distribution; this construction contract builds the physical nodes that software must inhabit. Together they express a doctrine shift: away from the monolithic command center model, which presents a single point of failure in EW or cyber attack, toward a network of hardened facilities that can operate independently or in degraded connectivity. The Army requested $572.8 million for JADC2 research and development in FY26, this construction contract is the real-estate expression of where that money lands operationally.
The critical open question is platform integration. The contract runs through July 12, 2029, which means the facility must be spec'd to host specific command and control systems, likely Lattice, IBCS, or another JADC2-enabling platform, within the next 18 months or risk building infrastructure that exceeds the lifecycle of the software it houses. If the Army has already locked that integration requirement into ACC's scope, the contract becomes a validation milestone for the C2 platform chosen. If not, the construction timeline becomes a constraint on which platforms can actually deploy into hardened facilities. Either way, whoever is building the C2 software the facility will depend on has just gotten a clear signal: your platform must be installation-hardened-ready by 2028 or you lose the operational slot.
The location disclosure will be the next real signal. Army installations hosting new hardened command nodes reveal which command sees itself as most under threat from distributed attack and therefore most in need of survivable, disconnected command infrastructure. A brigade-level forward ops center in the Indo-Pacific signals a different strategic bet than a division-level facility in Europe or a sustainment command node at an CONUS installation. Watch the announcement. The contract value tells you the Army is serious about distributed architecture. The location tells you which part of the force gets to go first.
