Spectral Autonomy

Big Iron and its integration into AMS-GRA

Part of the Open Architecture Field Guide.

Big Iron addresses modular electronic-warfare integration. The AMS-GRA version 14.0 documentation records its integration into the broader mission-system architecture and adds the Assembly concept for implementations with different system boundaries.

In this guide

The integration problem behind Big Iron

An electronic-warfare payload combines radio-frequency hardware, processing, and mission software. Its sensing resources produce data for processing functions, and those functions exchange tasking, status, and reports with the platform that carries them. A modular architecture has to describe both the payload's internal boundaries and its participation in the wider mission system.

Big Iron developed around this EW integration problem. The AMS-GRA version 14.0 documentation records its integration into the broader mission-system architecture. That record explains why a program may refer to Big Iron while the current architecture documents relevant to its work are part of AMS-GRA. [1]

The relationship is useful to understand because the underlying equipment does not all change at once. A fielded payload can retain hardware and interfaces from an earlier baseline while new software or integration work follows a later one. The engineering task is to connect the delivered configuration to the specific interfaces and responsibilities that apply to it.

What the AMS-GRA integration record explains

The version 14.0 Executive Summary identifies changes to the Mission Agnostic Service Infrastructure (MASI) associated with the integration of Big Iron. MASI is the infrastructure supporting mission software. The changes include common health and status reporting and a management interface, giving different units a defined relationship to their supporting environment. [1]

This matters when software contributions developed for different equipment must participate in one mission system. The processing function has its own purpose, but the platform also needs to manage its state and understand whether it is operating. Common infrastructure interfaces provide a place for those cross-cutting responsibilities.

The same release introduces the Assembly concept. An Assembly provides an integration and procurement boundary for capabilities whose physical organization differs from the full AMS-GRA Mission System decomposition. The documented use cases include legacy equipment and systems with limited size, weight, or power. [1]

Big Iron in the AMS-GRA integration recordBig Iron and earlier AMS-GRA work feed the v14.0 architecture baseline. That baseline documents the Assembly concept.documentsBig IronAMS-GRA developmentAMS-GRA v14.0Assembly concept

Scroll horizontally to inspect the diagram.

Figure 1. The AMS-GRA v14.0 Executive Summary records Big Iron integration and the introduction of Assemblies. The arrows indicate incorporation into that documented baseline.

An Assembly therefore connects incremental modernization to the architecture's functional boundaries. A program can identify the included services and equipment, establish the applicable interfaces, and assess that defined contribution. This is more concrete than treating a legacy payload as though its internal organization had already been rebuilt around every unit of the complete architecture.

Keeping hardware and mission-software responsibilities clear

The hardware still has its own interface description. SOSA, for example, applies selected modular hardware profiles within a sensor-system architecture. Those profiles concern connections and supporting services for hardware elements. Mission-system interfaces concern the functions and information exchanges through which software participates in the platform. [2]

A processing upgrade can involve both views. The hardware supplier provides computing resources and their physical interfaces. The software supplier provides a function with defined inputs, outputs, and management behavior. The integrator connects those contributions and checks the complete path from observations to reported information.

For a program whose requirements name Big Iron, the selected architecture revision and delivered configuration remain the starting point. The AMS-GRA integration record then shows how the relevant EW work relates to the current Mission System, software, infrastructure, and Assembly documents. The AMS-GRA chapter explains the units and interfaces used to read that record.

References

  1. AFLCMC/WA, AMS-GRA v14.0: Executive Summary, Mission System, Software Architecture, and Assembly volumes, April 2026. Distribution A.
  2. The Open Group, Sensor Open Systems Architecture Consortium and Technical Standard.