The U.S. Air Force's Air Mobility Command has contracted three software companies for a combined $21 million to bring real-time data integration to its airlift and tanker units—a capability designed specifically to hold together when communications links degrade or fail. The awards center on the Open Mission Engine (OMEN), a platform-agnostic, open software development kit that allows mobility aircraft to maintain a common operating picture covering fuel state, logistics, and fleet status regardless of network availability. For satcom and defense-sector professionals, the program is notable because it treats connectivity degradation as an explicit design condition rather than an edge case—a posture that reflects broader changes in how U.S. aviation commands think about link reliability in contested environments.
OMEN Architecture and the Tactical Moving Map
The Open Mission Engine is being developed as an open SDK, meaning it exposes standardized interfaces that allow different applications and data sources to be integrated without rebuilding underlying infrastructure for each new use case. Air Space Intelligence (ASI), one of the three contract awardees, received a Phase 2 prototype agreement from the Department of War Innovation Unit (DIU) specifically to build the OMEN platform and a companion Tactical Moving Map application tailored to Mobility Air Forces.
That mapping application is the first operational product built atop OMEN's framework. Defense Daily's reporting on the DIU solicitation that preceded the awards describes the tactical moving map as consolidating blue-force awareness, threat data, and airspace status onto a single aircrew display—and engineering it to function when the aircraft is completely offline. This capability matters in practical operational terms: mobility crews transiting communications-contested or bandwidth-limited environments have historically relied on whatever data was loaded before departure, with limited ability to receive updates once airborne and out of reliable link range. The open SDK model is intended to change that baseline by standardizing the development environment for mobility mission applications, lowering the barrier for integrating new data sources, and enabling software updates to be pushed and ingested across the fleet whenever a link window opens. Air & Space Forces Magazine's reporting confirms that delivering real-time updates in degraded environments is a core requirement of the contract, not a stretch goal.★
Air & Space Forces Magazine's headline framed the contracts as moving the mobility fleet "toward" a common operating picture with real-time data, positioning the awards as a development milestone on a longer capability arc rather than a completed fielding. The same report's description of covered data types extends beyond fuel and logistics to include broader "mobility fleet data"—an indication that OMEN is intended as a multi-domain data integration layer rather than a purpose-built tool for a single data stream. ASI's announcement likewise described the Tactical Moving Map as built specifically "for the Mobility Air Forces"—the broader construct that encompasses AMC's airlift and tanker units—signaling that the intended recipient community spans the full mobility enterprise.
The platform-agnostic design choice has significant practical implications. By specifying open, platform-agnostic architecture in the solicitation—as Defense Daily's earlier reporting on the DIU requirement documents—the Air Force positioned OMEN to be portable across that varied fleet from the outset, which should reduce integration friction and lifecycle cost compared with bespoke, hardware-coupled solutions.
Why Degraded-Environment Performance Is the Central Design Requirement
AMC's airlift and tanker fleets operate across a uniquely demanding range of connectivity conditions. The OMEN program directly addresses the scenario where a common operating picture—the shared display of aircraft locations, fuel states, and fleet logistics across the mobility enterprise—becomes difficult to maintain because the underlying data links are unreliable or intermittent.
A system that caches, updates, and propagates fuel and fleet data across intermittent links reduces that operational exposure materially.
Logistics and mobility fleet status present a parallel set of concerns at the campaign level. OMEN's architecture is intended to automate state synchronization and make it resilient to those gaps.★
The offline-capable tactical moving map reinforces this design intent at the individual aircrew level. Having blue-force awareness, threats, and airspace status consolidated on a single display that continues functioning without a live feed means crews retain situational awareness during the gap and can immediately begin acting on updated information the moment connectivity is restored—rather than waiting for a full data refresh before they can trust the picture.★
Contracting Structure, DIU Involvement, and Near-Term Milestones
The $21 million total is distributed across three software companies, with ASI publicly confirmed as one awardee through its own announcement. That announcement was published on September 15, 2026, via PR Newswire; Air & Space Forces Magazine's broader reporting on the full award package followed on September 28, 2026. Together, those dates bracket a roughly five-month arc★ from Defense Daily's April 6, 2026 coverage of the original DIU solicitation to the point at which Phase 2 agreements became publicly confirmed. ASI's release also described its task specifically as building both the OMEN SDK and the Tactical Moving Map application—confirming that a single awardee holds responsibility for constructing the core platform infrastructure as well as the first application running atop it★.
The April 2026 Defense Daily reporting on the original solicitation framed the government's requirements around platform-agnosticism and open architecture, reflecting a deliberate decision not to lock the program to a single vendor's hardware or software environment—a choice that should also support competitive follow-on development as the application ecosystem around OMEN matures.
The Tactical Moving Map is described as the first application in what is evidently intended to be a broader ecosystem. Open SDKs generate value precisely because they enable third-party and government development teams to build additional mission applications without requiring the original SDK vendor to do all subsequent work. Whether AMC or other commands have already identified specific follow-on applications for the OMEN framework is not detailed in available reporting, but the open-development structure makes expansion technically straightforward once the SDK is proven in prototype.
For satcom and communications providers working with military mobility customers, the OMEN program carries a concrete indirect implication. The Air Force is explicitly designing command-and-control software to function across the full spectrum from fully networked to fully disconnected★. That posture does not reduce demand for reliable satellite communications to mobility platforms—real-time updates are only possible when a link is available—but it resets the baseline expectation for what happens when links are intermittent. Systems and services that can support graceful degradation and recovery, prioritize high-value low-bandwidth data packets such as fuel state and threat updates when throughput is constrained, and synchronize efficiently during brief link windows will be better positioned than those optimized only for continuous full-bandwidth conditions. The OMEN contract is a visible data point in a broader pattern: U.S. defense aviation is increasingly architecting software around connectivity uncertainty rather than connectivity reliability, and procurement language and contract requirements in adjacent programs are likely to reflect that shift.
★ AI inference: One or more analytical conclusions in this article were drawn by the AI from cited facts and are not directly stated in the cited sources.