Spectral Autonomy

Big Iron: The Air Force's Open Architecture for Electronic Warfare

Part of the Open Architecture Field Guide. All information is derived from unclassified, publicly releasable (Distribution A) sources.

Big Iron is the Air Force's open architecture for airborne electronic warfare. It standardizes how EW mission software plugs into an aircraft so capability moves between platforms instead of being rebuilt for each one. As of AMS-GRA version 14.0 it was absorbed into AMS-GRA, though it still stands on its own for programs that do not need the full AMS-GRA mission-system infrastructure, such as attritable drones.

What it does

Electronic warfare has been the hardest part of an aircraft to open up. A jammer or a warning receiver built for one platform rarely transfers to another, because the RF front end, the processing chain, and the mission software are usually specific to that airframe. Replacing or upgrading an EW capability then means a custom integration effort each time.

Big Iron standardizes the software and integration side of that problem. It defines how an EW capability connects to the mission system, how it is tasked, and how it reports. It works alongside SOSA, which standardizes the EW hardware: the cards, slot profiles, and chassis. One covers the software, the other the hardware. Built to both, an EW capability can port across platforms at both layers.

An electronic-warfare capability is built to two open standardsAn electronic-warfare capability is built to Big Iron for software and mission integration and to SOSA for hardware. Command, control, and sensor data move over OMS and UCI.Electronic Warfare capabilityBUILT TOBig Ironsoftware & mission integrationSOSAhardware: cards, slots, chassisCommand, control, and sensor data move via OMS and UCI.
Spectral Autonomy
An electronic-warfare capability is built to Big Iron for software and mission integration and to SOSA for hardware, with command, control, and sensor data over OMS and UCI.

Where it sits

Big Iron is owned by the Air Force Life Cycle Management Center's Warfare Directorate (AFLCMC/WA). As of AMS-GRA version 14.0 (April 2026), it was absorbed into AMS-GRA. AMS-GRA comes from the same directorate, which is why the two converged. Big Iron still describes fielded electronic-warfare programs, but it is no longer developed as a separate architecture.

For a program office or a vendor, the effect is straightforward. Electronic warfare is now covered inside the AMS-GRA mission-systems architecture, under the same architecture as the rest of the mission system, rather than under a second standard tracked and reconciled on the side.

Big Iron still has a place of its own. An attritable drone or a low size-weight-and-power electronic-warfare payload that does not need the full AMS-GRA mission-system infrastructure can be built to Big Iron directly, rather than carrying everything AMS-GRA brings. It is no longer iterated as a separate architecture, but it remains the lighter target for programs that do not need the whole suite.

Big Iron before and after its integration into AMS-GRABefore AMS-GRA version 14.0, Big Iron was a standalone Air Force electronic-warfare architecture owned by AFLCMC/WA. As of version 14.0 in April 2026, Big Iron is integrated into AMS-GRA, owned by the same office, and a new Assembly entry point was added. Big Iron remains valid for fielded programs but is no longer developed as a separate architecture.BEFORE v14.0AMS-GRAAFLCMC/WABig Iron (EW)AFLCMC/WA, standaloneSame owner, separate documentsAS OF v14.0 (APR 2026)AMS-GRA v14.0AFLCMC/WABig Iron, integratedAssembly (new entry point)No longer a separate architecture,still valid for fielded programs
Spectral Autonomy
Big Iron was absorbed into AMS-GRA at version 14.0. It remains usable for fielded programs but is no longer developed as a separate architecture.

How it connects

An electronic-warfare system built to Big Iron sits within a small set of adjoining open standards:

  • SOSA defines the EW hardware it runs on: the cards, backplane slot profiles, and chassis.
  • OMS and UCI carry the command, control, and sensor data. OMS is the mission-system abstraction layer; UCI is the message set that moves across it.
  • AMS-GRA is the mission-systems architecture Big Iron is now part of, and the compliance target a modern EW capability is built against.

Where it appears

Big Iron–aligned EW systems have flown in the Air Force Research Laboratory's AERRES campaign on MIRAGE pods. In 2026, BAE Systems demonstrated Big Iron and SOSA alignment across platforms beyond crewed aircraft, including weapon pods, Collaborative Combat Aircraft, larger unmanned aircraft, rotary-wing platforms, ground vehicles, and surface vessels.

Where this fits

FAQ

Is Big Iron a separate architecture?
No longer. It was absorbed into AMS-GRA at version 14.0. It still stands on its own for fielded programs and for low-SWaP systems such as attritable drones that do not need the full AMS-GRA infrastructure.
Is Big Iron part of GARA?
No. It belongs to AMS-GRA. GARA is a different Air Force reference architecture, owned by a different office.
What does Big Iron cover that SOSA does not?
SOSA standardizes the EW hardware. Big Iron standardizes the EW software and its integration into the mission system.

Sources