OFFSETOFFSET

Next Generation Command and Control (NGC2)

10 min read

Next Generation Command and Control (NGC2)

NGC2 is the Army’s replacement for its legacy command and control stack, and it is two stories at once. The first is a technology story about collapsing dozens of function-siloed systems onto a common data layer. The second is a budget structure story: to build it, the Army collapsed roughly a dozen budget lines into six, which changed what Congress can see and control. The second story is why NGC2 matters to anyone who does not care about tactical networks.

FieldValue
TypeArmy command and control program
Acquisition homeCapability Program Executive C3N (BG Shane Taylor), Aberdeen Proving Ground
RequirementsFutures_and_Concepts_Command under T2COM
Program office establishedApril 2025, first PM Col. Chris Anderson
FY2027 request$3.78B across six lines
Major Force ProgramMFP-6 in development. Predecessor lines were MFP-2 and MFP-3
Status (Aug 2026)Declared “ready to scale” after Project Convergence Capstone 6

What it is

The Army describes its legacy problem as C2 systems “focused on single functions like fires, logistics, or airspace management.” A division command post ran dozens of unintegrated programs of record, each with its own database, network dependency and vendor. NGC2 replaces that with a data-centric architecture delivered as four layers: transport, infrastructure, data, and applications, spanning soldier to corps.

Origin: a proof of concept at Project Convergence Capstone 4, run February to March 2024. The Chief of Staff of the Army approved an NGC2 Capability Characteristics of Need document in May 2024, aligning requirements work with program initiation. At the December 2024 Technical Exchange Meeting in Savannah, officials framed NGC2 as a “clean sheet” design rather than an evolution of legacy architectures. Joe Welch, then deputy to the commander of Army Futures Command, described the design principle as “clean sheet, unconstrained.”

Naming caution. Three organizations in this story have been renamed recently and reporting from different dates is inconsistent. PEO C3T became PEO C3N on October 9, 2024, then reorganized into Capability Program Executive C3N in 2026. Army_Futures_Command and TRADOC merged into T2COM on October 2, 2025, with requirements now under Futures_and_Concepts_Command. See Army_Transformation_Initiative.

NGC2 is distinct from C2 Fix, the near-term bridge effort launched in 2022 that modernizes division and brigade C2 using existing programs of record plus commercial capability. Officials have called C2 Fix the “down payment” on NGC2. Do not conflate them, and do not conflate NGC2’s budget with C2NOW, a separate program that some aggregate figures fold in.

The industry teams

AwardDateValueTeam
4th Infantry Division prototypeJuly 2025$99.6M OTA, 11 monthsAnduril prime, with Palantir, Striveworks, Govini, Instant Connect Enterprise, Research Innovations Inc., Microsoft
25th Infantry Division prototypeSeptember 2, 2025$26M OTA, ≤16 monthsLockheed Martin prime, with Raft and Hypergiant
Common data layer baselineJune 22, 2026Not separately disclosedAnduril lead, Palantir Foundry plus Anduril Lattice, Raft on registries and federation

Two cautions on these numbers. They are agreement values, not obligations; no public reporting distinguishes ceiling from obligated funds. And the June 2026 data layer award was placed under Anduril’s existing Army enterprise agreement rather than as a standalone contract, so it carries no separate published value.

That enterprise agreement is its own fact worth holding separately: in March 2026 the Army consolidated roughly 120 existing Anduril contracts into a single vehicle with a $20 billion ceiling over up to ten years. It is an ordering vehicle, not an obligation, and Anduril itself characterized it as an “ordering guide.” A parallel agreement was established with Palantir.

The data layer is the incumbency. Whoever owns the common data baseline owns the integration surface every other application must cross. That is a structurally different position from owning an application, and it is why the June 2026 award matters more than either prototype award.

The budget line consolidation

This is the part that generalizes beyond the Army network.

Going into FY2027 the Army collapsed its C2 portfolio from twelve major budget lines to six, a roughly 50 percent reduction. Army Undersecretary Michael Obadal described the trajectory as about a 30 percent reduction in line items from FY2025 to FY2026, a further 35 percent consolidation into FY2027, and roughly 20 percent growth in the NGC2 top line.

The six surviving lines, verified directly in the FY2027 President’s Budget exhibits:

RDT&E (Appropriation 2040A, Budget Activity 05), R-1 lines 162 through 165:

PETitleFY2027 request
0605330AC2 Transport$45,370K
0605331AC2 Applications$488,401K
0605332AC2 Data$306,019K
0605333AC2 Infrastructure$64,849K
RDT&E subtotal$904,639K

Procurement (Appropriation 2035A, Other Procurement Army, BA-02), P-1 lines 16 and 17:

LineTitleFY2027 request
16C2 Infrastructure$1,293,203K
17C2 Transport$1,581,863K
Procurement subtotal$2,875,066K

Total FY2027 NGC2 request: 3.78 billion.

Per layer, all-in: C2 Transport 1.358B, C2 Applications 306.0M.

The evidence that this was a consolidation and not new money

Three things in the primary documents establish it:

  1. All four RDT&E lines show blank entries for FY2025 actuals, FY2026 enacted and FY2026 total. They are new lines created in the FY2027 request, not renamed continuations.
  2. Legacy Other Procurement line 15, “Tactical Network Communication,” is zeroed in FY2027, having carried 665,309K in FY2026. The money migrated into the two new lines directly beneath it.
  3. PE 0604818A Army Tactical Command and Control drops from 42,584K, a roughly $390 million reduction consistent with migration into the consolidated lines.

The FY2026 request had already been structured the same way, at roughly $2.95 billion described as a “zero sum realignment” of existing C2 resources rather than net-new money.

What the consolidation did to Major Force Programs

Worth stating because it is invisible unless you read the PE prefixes.

The four new NGC2 development lines all begin 06, which is MFP-6, Research and Development. Among the donor lines are 0203728A (JADOCS, MFP-2 General Purpose Forces) and 0303142A (SATCOM Ground Environment, MFP-3 C3I and Space). So the consolidation pulled money out of fielded-system mission categories and into a development category, across MFP boundaries, in a single budget action.

This is normal under the coding rules, since budget activity 7 lines carry the MFP of the fielded system while development lines carry 06. It is also a genuine reduction in traceability: capability that was previously visible as general purpose forces money is now visible as research and development money, and will not reacquire a mission MFP until it fields into BA-7. Anyone tracking Army C2 spend across FY2026 and FY2027 on a consistent basis has to bridge that discontinuity manually.

For contrast, see The asymmetry that actually matters: SOF program elements carry MFP-11 across their whole lifecycle and never undergo this shift.

Congressional reaction

Congress did not block NGC2. It fenced it and demanded to see the plan.

Section 114 of the enacted FY2026 NDAA, “Limitation on Availability of Funds for the Next Generation Command and Control Portfolio of Capabilities of the Army,” provides that not more than 50 percent of FY2026 Army NGC2 funds may be obligated or expended until the Secretary of the Army submits a report to the congressional defense committees. The required report covers:

  1. Detailed funding plans for current and new procurements for experimentation and final fielding, plus a cost and capability assessment
  2. Testing and fielding plans, including how new programs meet the resiliency requirements of § 168 of the FY2020 NDAA and how they will use NSA High Assurance certified encryption
  3. Plans to integrate existing programs of record with new ones and ensure interoperability with fielded Army systems
  4. A rigorous developmental test campaign and formal operational test and evaluation prior to fielding

The Joint Explanatory Statement records that § 114 originated as a House provision with no Senate counterpart, and that the conference adopted it with an amendment adding the test and evaluation requirement.

FY2027 authorization. The HASC chairman’s mark of the FY2027 NDAA (H.R. 8800), released in late May 2026, would reduce authorized NGC2 funding by $710 million.

On consolidation specifically. Appropriators approved all 13 of the Army’s FY2026 budget line consolidation requests, which covered electronic warfare, counter-UAS and drone lines rather than the C2 portfolio, but rejected the Army’s separate request to raise reprogramming notification thresholds from 50 million for procurement and $25 million for R&D, stating such changes were unlikely to improve program execution. That pairing is the clearest read on congressional posture: willing to consolidate lines, unwilling to loosen the reporting that consolidation makes more necessary.

In February 2026, amid the funding cap, Obadal publicly warned industry not to bring negativity about NGC2 or competitors to Congress, saying mixed messages on the Hill create doubt that slows solutions.

Two honest gaps. It is not publicly confirmed whether the Secretary of the Army has submitted the § 114 report, so whether the 50 percent fence has lifted is an open question for anyone modeling FY2026 execution. And while “reduced line-item visibility” is the obvious throughline, no bill or committee report reviewed states that objection in those words; what is documented is the § 114 fence, the reprogramming-threshold rejection, and the $710 million authorization cut.

Status as of August 2026

Project Convergence Capstone 6, a roughly ten-day joint exercise at Fort Irwin with about 10,000 US and allied participants testing roughly 90 technologies, concluded in July 2026 and ended the ten-month prototyping phase. Army leaders declared NGC2 “ready to scale” at a media roundtable.

The caveat came from the unit that used it. Maj. Gen. Patrick Ellis, commanding general of the 4th Infantry Division, characterized the system as functional but not optimized.

Next up is I Corps headquarters at Joint Base Lewis-McChord with enablers and several downtrace units, deliveries aligned to training events. The Army plans two divisions with full-stack NGC2 in FY2027 and procurement for three more division equivalents for FY2028 fielding, with a stated ambition of all eleven divisions within five years.

Why it matters

It is the acquisition template. Competing division-level prototypes to non-traditional vendors, a single common data layer, a large exercise as the decision event, then continuous fielding. Anyone forecasting how the Army will buy software should study this sequence rather than the Defense_Acquisition_System milestone chart.

It is a live test of whether Congress will trade visibility for speed. The Army’s argument is that software-defined capability cannot be managed through dozens of narrow line items on annual cycles. The congressional counter is that line items are the instrument of control, and fewer of them means less ability to direct or stop anything. Section 114 is the compromise so far: consolidation permitted, money fenced until the plan is delivered. How that resolves will shape budget structure well beyond Army C2.

It resets who the vendor is. The data layer holder sits between the Army and every application vendor. That is an incumbency built out of architecture rather than a program of record.

See also

Sources

Graph View

1

click focuses · double-click opens

Backlinks