The most consequential signal from senior Army leaders at TEM-15, AUSA Global Force, and the McAleese Conference was not a specific prototype, vendor, or technical milestone; it was confirmation that the Department of the Army is reshaping how it acquires Command and Control capability. Next Generation Command and Control (NGC2) is the visible catalyst, but acquisition reform is the underlying transformation. PAEs have defined their organizations, commercial-first pathways are being operationalized, and acquisition constructs are evolving from a prime/sub approach to a modular architecture. For industry leaders, the strategic question has shifted from winning programs to aligning within a system that has redistributed authority, risk, and integration responsibility.

Portfolio-Centric Authority: The Rise of the PAE

The elevation of the Portfolio Acquisition Executive (PAE) represents a fundamental shift in decision authority. The Department of the Army has moved away from siloed program offices toward a portfolio-based structure with clearer accountability, fewer oversight layers, and greater authority at a program management-level. Attention is now shifting to organizing the "trade space" between portfolios, where resources and authority can be adjusted as operational priorities evolve.

Portfolio oversight allows senior leaders to observe which capabilities generate operational value, adjust priorities accordingly, and expedite capability acquisition. NGC2 became a program of record in April 2025, and within months, prototype capabilities were placed directly into operational formations. By September 2025, the 4th Infantry Division was conducting live-fire training missions using Anduril's NGC2 prototypes, while exercises such as the Ivy Stings expanded experimentation. In early 2026, the 25th Infantry Division evaluated Lockheed Martin's first NGC2 prototype during the Lightning Surge exercise series. Together, these events illustrate a rapid "prototype-to-formation" pathway in which operational units, not just acquisition structures, shape the system's evolution.

This tempo contrasts sharply with earlier efforts. The Army Battle Command System rollout in the early 2000s followed a multi-year deployment model, with fielding constrained to a limited number of brigades each year. NGC2 is advancing through repeated operational exercises and divisional experimentation within a far shorter timeframe.

The implications for industry are significant. Rather than displacing program authority, the portfolio construct adds a coordination layer in which outcomes from individual programs inform broader resource allocation decisions. This innovation creates a "ladder of escalation" from program-level experimentation through Capability Program Executives (CPE) coordination to portfolio-level priority discussions.

Program Managers (PMs) within CPEs remain the primary industry interface, and many are expanding engagement efforts to enable closer collaboration with operators. Operational formations are becoming more influential as exercises provide direct feedback that shapes capabilities. Effective capture strategies will continue to center on PM- and CPE-relationships while recognizing that successful programs gain visibility at the portfolio level.

That coordination power is real, but not uncontested; expanded PAE flexibility in moving resources within portfolio boundaries may face congressional pushback as the new model matures.

Commercial-First as Capital Strategy

"Commercial-first" is no longer an abstract preference; it is being operationalized as acquisition doctrine. Output-based contracting, streamlined procurement pathways, and accelerated experimentation cycles signal that the Army intends to leverage commercial innovation rather than replicate it internally. Senior leaders at TEM 15 reinforced this by linking successful commercialization to government-facilitated private equity exposure, which suggests that Army demand should strengthen commercial viability rather than displace it.

For industry, commercial-first changes the risk calculus. Unlike traditional programs of record with defined quantities and multi-year commitments, commercial pathways provide less certainty about ultimate demand. Firms may invest in capabilities that demonstrate operational value without clear guarantees regarding production scale. Whether a solution supports a niche requirement or becomes a widely adopted capability can significantly alter the return profile.

Speed in this model does not eliminate scrutiny. Schedule is increasingly part of the evaluation itself, alongside risk and past performance. Supply-chain and product maturity, interoperability, and documented risk reduction all become more important when government is asking industry to invest earlier and accept greater uncertainty. Firms must prove not only that a capability works, but that it can scale responsibly under compressed timelines.

Commercial-first functions as a capital strategy. IP posture, pricing models, and production ramp considerations are moving earlier in the lifecycle as firms balance innovation with financial exposure. The emerging quid pro quo is clear: industry assumes greater investment risk in exchange for faster access to operational experimentation and potential scaling opportunities. Structuring capital, partnerships, and product development around scalable, commercially-informed architecture is industry’s best way to position for success. Those that treat commercial-first as marketing rhetoric will struggle.

From Prime/Sub to Ecosystem Leadership

The acquisition architecture underpinning NGC2 is reshaping traditional prime/sub relationships. Senior Army leaders have made clear that the future ecosystem will involve multiple vendors operating across the transport, infrastructure, data, and application layers, with no single firm expected to control the full system. The traditional hierarchy of Prime Contractor and Subcontractor is giving way to a more fluid model of Team Lead and Teammate, where firms contribute discrete capability layers rather than vertically integrated solutions.

This shift is both architectural and cultural. Containerized services and standardized data frameworks make it technically easier to introduce or replace components, reducing the friction historically associated with changing subcontractors or adding vendors midstream. Teaming relationships may become more dynamic, with partners entering or exiting solution stacks as capabilities evolve or operational needs change.

Where integration responsibility ultimately resides is an unresolved question. Historically, large system integrators or government program offices assumed the burden of stitching together complex architectures. In a composable environment, that work increasingly shifts toward standards-based interoperability and DevSecOps pipelines that allow components to interact without a single integrator controlling the entire stack.

For industry leaders, the competitive moat is no longer controlling the IP or the full stack, it is being indispensable because they can build stacks that the end users, warfighters, value. All firms must define clearly where they lead, where they partner, and how their capabilities interact with adjacent layers.

Institutional Friction and the Politics of Reform

Structural reform inevitably redistributes advantage. Portfolio authority’s flexibility allows leaders to direct investment toward solutions demonstrating operational value, but also introduces greater uncertainty for competing programs. Budget fluidity and centralized oversight can alter program trajectories more quickly than traditional structures allowed.

At TEM 15, senior leaders were explicit that industry engagement with Congress or the Pentagon must occur within the spirit of the new acquisition structure rather than seeking to bypass it. Reform does not eliminate the enduring tension between requirements and contracting, but it exists within a faster-moving system.

The most important question is how the new process will evolve. Some senior leaders we spoke to openly doubted if the new model results in meaningful change to the overall system and timelines. Members of Congress have expressed concerns about the lack of competition in this system. Most importantly, firms will respond differently: some through defensive strategies such as policy advocacy, contractual maneuvering, or consolidation; others through entrepreneurial approaches, investing ahead of demand; and a third group by shifting focus toward more predictable defense markets or allied-nation opportunities in Europe or Japan. These reactions reflect the realities of institutional change rather than a failure of reform. For industry, the central question is not whether the system will evolve, but to foresee the evolution and determine how best to adapt as it does.

Acquisition Reform as Institutional Doctrine

Acquisition transformation is the enabling condition for everything that follows. NGC2 may be the visible driver, but the more durable shift is structural. If the portfolio model, commercial-first pathways, and modular ecosystem structures demonstrate success here, they are likely to propagate across other modernization efforts. Acquisition logic is beginning to shape technical design rather than merely respond to it; the same themes are increasingly visible across wider DoW acquisition discourse, suggesting this institutional logic will not remain confined to Army C2 modernization.

Understanding how NGC2's architecture enables and reinforces this acquisition model is therefore essential. The next paper in this series examines that architecture directly: NGC2 as the forcing function shaping the future Command and Control ecosystem.