NGC2 is the Army’s new Command and Control stack and redefines the model for executing the Army’s acquisition modernization. The Department of the Army has defined a modular four-layer construct—transport, infrastructure, data, and application—that does more than organize technology. This modular stack prevents control of the ecosystem by any one vendor, which enables modular competition, enforces interoperability at scale, and allows capability to evolve at the pace of commercial innovation.
This architecture is a market determinant, not a technical detail, and industry leaders must understand the impact. The way data is structured, services are containerized, and applications are deployed will influence vendor roles, margin distribution, teaming dynamics, and long-term competitive positioning. NGC2 functions as a defense-specific operating model in which a reusable capability stack supports mission-specific applications and outcomes. It is shaping how capability will be built, integrated, scaled, and competed across the future Command and Control ecosystem.
At the core of NGC2 is a data architecture governed by a defined taxonomy that determines how data is created, exchanged, and acted upon across the ecosystem. In practical terms, the Army is defining how data looks, what it can do, and how it moves between layers. Shared data standards can reduce compatibility problems between systems while expanding competition among vendors that can operate within the same model. That makes the data layer a strategic control point. By standardizing data structure and behavior, the Army is increasingly standardizing the terms of participation for vendors operating within NGC2.
The June 2026 decision to establish a common data layer baseline — with Anduril's Lattice and Palantir's Foundry providing the edge-to-cloud data mesh, and Raft supplying data registries and federation tools — shows that this is no longer a design aspiration. The Army has selected specific firms to lead the common data layer after ten months of operational validation with the 4th Infantry Division and 25th Infantry Division. Firms that engaged early in the standard-setting process are now shaping the rules of ecosystem participation; those that did not are adapting to standards they had less influence over.
With a modular stack, units can assemble storage, visualization, telemetry, maps, voice, and AI/ML workflows based on mission need. Containerization allows a full stack from infrastructure to application to move across formations without rebuilding the architecture each time. Participation becomes more standards-based and less dependent on bespoke integration, which lowers barriers to entry for firms delivering interoperable capability slices. At the same time, integration is not disappearing — the Army is shifting from closed, contractor-controlled integration toward integration governed by the architecture itself. That creates pressure on incumbents relying on proprietary data models or closed interfaces, and opportunity for firms that can build within the common standard.
NGC2's data layer is now governing the architecture. It is the foundation for interoperability, modular procurement, and ecosystem competition.
The Army has pursued C2 interoperability and modularity before, but prior efforts moved slowly, constrained by long deployment cycles, tightly coupled systems, and slow dissemination of operational feedback. NGC2 has learned from these issues by employing a substantially quicker design-build-test cycle. The architecture is being validated through operational formations rather than relying primarily on large, centrally orchestrated modernization events.
As discussed in Part I, NGC2 moved from program of record to divisional experimentation within months. What matters architecturally is what has followed. By May 2026, the 4th Infantry Division's Ivy Mass exercise stressed every element of NGC2 at division scale across Fort Carson and Piñon Canyon, including fighting through cyber and electromagnetic attacks modeled on real-world threats. In the same month, the 25th Infantry Division conducted Lightning Surge 3 during Exercise Balikatan 2026, demonstrating sensor-to-fires integration across Hawaii, the continental United States, and the Philippines simultaneously. Project Convergence-Capstone 6, planned for July 2026, will serve as the culminating event: a division-scale, force-on-force NGC2 validation at the National Training Center. Containerized modules are already being exchanged across prototype environments, demonstrating that portability is not just a design aspiration.
That credibility is still conditional. If portable modules stop traveling across environments, if the data standard proves too rigid for operational variation, or if adoption stalls beyond the initial formations, NGC2 could begin to resemble earlier efforts that never translated into durable scale. But the direction of travel, from prototype to operational validation to acquisition decision, is now established rather than theoretical.
While NGC2's architecture is complex beneath the surface, its visible manifestation is simplicity at the application layer. The Army has articulated an "app store" logic in which warfighters select, configure, and employ applications based on mission needs rather than the underlying vendor stack. Users do not have to worry about infrastructure, data standards, or AI services directly – they build and use mission-specific applications built on top of a reusable architectural foundation.
The value of this modularity is already visible in practice. The 4th Infantry Division and 25th Infantry Division are shaping and employing applications differently based on operational context, reinforcing that the end state is not a single optimized configuration but a configurable tool bag adapted by formation, mission, and echelon. The modular architecture and DevSecOps pipelines create room for smaller firms to contribute niche capabilities, from edge compute to electromagnetic spectrum integration, across the stack without requiring the entire system to be rebuilt
The value of the app-store model is configurability. In practical terms, users can tailor applications, but only within architectural guardrails that preserve interoperability and coherence across formations. Discoverability, curation, certification, and lifecycle management will determine whether configurability becomes an advantage or a source of fragmentation.
For industry, the app layer is where usability, discoverability, and mission relevance become competitive differentiators. NGC2 is changing not only how systems are built, but where value and margin may increasingly accrue.
Perhaps the most consequential metric emerging from NGC2 is adoption. Senior leaders have emphasized that usage, not documentation compliance, is the primary indicator of success. NGC2 is being judged not by conformance to design principles on paper, but by whether formations use it, adapt it, and carry it forward into repeated operational cycles. If the application layer is where architecture becomes visible to users, adoption is where it becomes legible to the institution.
Application growth within participating divisions, the sharing of containerized modules across the Anduril and Lockheed prototype environments, and exercises such as Lightning Surge, Scarlet Dragon, and the Ivy Stings all point to the same pattern: the architecture is earning credibility through operational use. The scaling process has surfaced real challenges, including cybersecurity in Sting 2, bandwidth limitations in Sting 3, and data connectivity issues in Sting 4. However, leaders treat those issues as implementation problems to solve rather than as evidence that the model is fundamentally unsound. The ability to identify, refine, and resolve those problems in the field is itself helping build confidence in the architecture.
The data baselining decision is the strongest evidence that adoption is functioning as intended. Ten months of operational feedback from two divisions directly informed the Army's selection of a common data layer baseline, converting exercise results into a concrete acquisition action. The adoption-to-scaling pathway the architecture was designed to produce is now demonstrable rather than theoretical.
A modular stack does not eliminate complexity; it relocates it. NGC2 reduces dependence on monolithic integration through standards, shared data structures, and containerized services. But integration responsibility does not disappear; it shifts toward a more distributed model in which governance, orchestration, and technical discipline become more important.
That creates several open questions. Where does integration responsibility ultimately sit as the stack becomes more modular? How much flexibility can the app-store model tolerate before coherence erodes? A system that is too rigid undermines configurability, while one that is too open risks fragmentation, duplication, and uneven performance across formations.
Cybersecurity and compliance add another layer of tension. A modular stack accelerates innovation and portability but also expands interfaces, dependencies, and accreditation demands. Interoperability is both an enabler and a constraint: it widens participation but limits how far vendors can differentiate outside the common architecture.
A modular stack still requires governance. The Army has not fully resolved where orchestration authority, integration accountability, and architectural discipline will sit as the ecosystem matures.
NGC2's architecture is not separate from the Army's broader acquisition shift; it is the road map to make that shift workable. Portfolio authority, modular teaming, and commercial-first pathways all depend on an architecture that supports interoperable participation, portable capability, and scaling through operational use. NGC2 is beginning to demonstrate that the future defense operating model may be less vertically integrated and more composable, data-centric, and ecosystem-driven.
The architecture matters beyond Command and Control alone. It shows how a reusable capability stack can support mission-specific outcomes without requiring a single vendor to own the full system. Acquisition logic is no longer merely responding to technical design; it is actively shaping it.
Part I examined how authority and capital are being redistributed. Part II has shown how the Army is using a modular architecture to turn that modernization concept into a functioning model. Part III examines how companies position, engage, and adapt to compete in a modular, portfolio-driven ecosystem.