Combat cloud
A term for the shared data and communications layer that links sensors, platforms and decision-makers in air operations, used with different meanings by different air forces.
The term combat cloud is a label for a distributed information environment in which sensors, aircraft, weapons and command nodes share data and can be tasked across a network, rather than each platform relying on a fixed link to a single controlling node. The term is not a standard. It has no agreed definition in NATO doctrine, and air forces and industry teams apply it to different things, so any use of the phrase needs checking against the context in which it appears.
Where the term comes from
The idea grew out of network-centric thinking in air forces. The cloud part is an analogy to commercial cloud computing: data and services that are available to authorised users across the network, with processing placed where it is most useful. In practice a combat cloud is a system of systems, combining communications, data standards, shared services and software, not a single product that can be bought.
Two usages worth separating
In the United States the term has been associated with the Air Force’s Advanced Battle Management System (ABMS). The Congressional Research Service describes ABMS as an effort to build a next-generation command and control system using cloud environments and new communication methods, with sensors and command systems disaggregated, and as the Air Force’s contribution to the Department of Defense’s Joint All-Domain Command and Control effort. ABMS covers software, hardware, infrastructure and policy together, and the Air Force treats new ways of commanding airborne forces as part of it. Here the emphasis is on shared data and command.
In Europe the phrase is most visible in the Future Combat Air System (FCAS, or SCAF in French). A 2020 report to the French Senate describes the combat cloud as the less visible core of that system, linking platforms to each other and to databases, and argues that innovation is needed in it as much as in the aircraft. The same report records that the pillar was led by Airbus, with Thales also involved. Here the cloud is the architecture that joins a crewed aircraft, uncrewed companions and other forces.
How it is meant to work
Common elements across usages are open data and interface standards, resilient communications that tolerate loss of links, edge processing close to sensors, and software services that fuse and distribute information. These overlap with tactical data links, which carry formatted messages between known participants, and with sensor fusion, which combines inputs into a single track picture. A combat cloud is generally presented as extending both, adding flexible routing and shared services over a heterogeneous network.
Why it matters for defence technology
The concept shifts value from individual platforms to software, interfaces and integration, which shapes how programmes are structured and who holds the architecture. Congress has raised concerns about retiring existing airborne command platforms before a replacement is proven, and about funding and acquisition oversight for ABMS.
What to watch
Watch whether programmes publish interface specifications, how allied interoperability is demonstrated, and whether the term converges on a shared definition or fades into more specific vocabulary such as battle management and multi-domain operations.
Sources
Related: Command and control (C2) · Multi-domain operations · Sensor fusion · Tactical data links (Link 16 and its relatives)