Next Gen AOC Is a Twenty-One Center Integration Problem
Kessel Run's Next Gen AOC effort aims to modernize 21 Air Operations Centers before a 2027 contract transition. The challenge is not adding software; it is managing interfaces across legacy and new command-and-control components.
Twenty-one Air Operations Centers are about to undergo a generational software transplant. Next Gen AOC is not mainly a model-selection problem. It is an integration problem.
Air & Space Forces Magazine reported that Kessel Run is launching the Next-Generation AOC program with a request for information, a draft RFP planned for August 2026, and a contract award target of June 2027. The Next Gen AOC report notes that the Air Force treats its 21 AOCs as the AN/USQ-163 Falconer weapon system.
That weapon-system framing matters. An AOC is not a dashboard. It is the command-and-control environment that supports air tasking, planning, targeting, refueling, movement, and execution. Replacing or modernizing its software means touching many operational workflows at once.
Kessel Run already has software in the fight. KRADOS, the Kessel Run All-Domain Operations Suite, has been part of the Block 20 modernization path. AppTX and related applications have helped move pieces of AOC work toward cloud-based software. The next step is larger. It has to connect new software, old systems, data feeds, users, networks, and operational processes across the AOC enterprise.
The integration challenge is not “add AI/ML.” AI and data fusion may help, but only if the data paths, authority rules, and user workflows are stable enough to support them. A model cannot rescue a command-and-control system if the upstream data is stale, the interfaces are unclear, or the user cannot tell which source is authoritative.
The hard seams are concrete. Legacy components have to exchange data with new services. Planning tools have to align with execution tools. Airspace, targeting, tanker, and movement data have to carry consistent meaning. Users need continuity during transition. Security controls and deployment paths must work across operational environments.
Polyrhythm reads programs like this the way a structural engineer reads a renovation plan: not by what is being added, but by which load-bearing interface is being touched. A modernization effort can fail if it changes the wrong seam too late or hides a dependency behind a clean user interface.
The schedule makes that risk sharper. A June 2027 contract target means architecture choices made in 2026 will set the boundaries for years of delivery. The program needs interface contracts, data governance, test environments, migration paths, and rollout evidence before the new stack becomes unavoidable.
The user transition is also part of the architecture. Operators cannot pause the air tasking cycle while a new system settles in. The program has to decide which workflows move first, which legacy views stay available, how training keeps pace, and how data confidence is shown during the transition. A modern interface that hides uncertain data will not help the floor make better decisions.
Next Gen AOC will matter because AOCs are where airpower gets planned and controlled. The integration challenge is not model selection. It is interface contracts between dozens of legacy and new components, across 21 centers, under operational pressure. That pressure makes early architecture choices decisive before the next contract starts. That is exactly where Polyrhythm earns its keep.