AMS-GRA: Modular mission-system architecture
Part of the Open Architecture Field Guide.
The Agile Mission Suite Government Reference Architecture (AMS-GRA) defines functional boundaries and interfaces for modular mission systems. Its Minimum Procurable Units give programs a basis for acquiring and integrating components separately.
In this guide
A mission system changes at several rates
A mission system combines the sensors, processing, and software that carry out a platform's mission. Those parts do not age at the same rate. An installed aperture may remain useful while the processors behind it are replaced, and processing hardware may remain in place through several software upgrades. A tightly coupled design makes these different cycles difficult to manage because changing one part can force changes elsewhere.
The Agile Mission Suite Government Reference Architecture (AMS-GRA) organizes the system around explicit functional and procurement boundaries. Its Minimum Procurable Units (MPUs) identify contributions that can be acquired and integrated as defined parts of the architecture. The boundary therefore has both a technical purpose and an acquisition purpose: it identifies what a supplier provides and the interfaces through which that contribution joins the system. [1]
This approach lets a program describe an upgrade in terms of the affected unit. Adding processing capacity, changing a software function, and replacing sensing hardware involve different responsibilities. The architecture provides names and interfaces for those responsibilities so they can be planned separately while remaining part of one system.
Following an observation into usable information
An aperture is the part of a sensor that receives or transmits energy, such as an antenna or optical opening. In AMS-GRA, a Multi-Function Aperture (MFA) provides sensing resources that can support software-defined functions. Processing software needs a defined way to use those resources and interpret the data they supply.
The MFA Encapsulation Layer (MEL) provides the interfaces and interaction patterns at that boundary. Encapsulation places the resource's internal implementation behind an interface that its users can address. In a receiving example, this allows software processing to be described in relation to the aperture data and services it uses rather than in terms of every internal hardware detail.
Processing functions then transform observations into information consumed elsewhere in the mission system. Their execution also needs infrastructure: services for hosting, managing, and connecting the software. The Mission Agnostic Service Infrastructure (MASI) supplies this supporting environment. “Mission agnostic” describes infrastructure that supports software functions without containing the mission-specific processing performed by each one. [1]
At the mission-system interface, Open Mission Systems (OMS) provides integration interfaces and the Universal Command and Control Interface (UCI) provides a common model for mission-level messages. These roles connect processing results to the components that consume them. The aperture interface, execution infrastructure, and mission exchanges describe different relationships within the complete function.
Scroll horizontally to inspect the diagram.
Relating the units to their upgrade cycles
The architecture groups MPUs into three levels according to their relationship to platform development and refresh. The levels describe how changes are organized; they are not three mandatory processing steps. [1]
| MPU level | Typical contributions | Relationship to change |
|---|---|---|
| Level 1 | AMS-GRA services, OMS services, and MFA local functions | Software capabilities that can evolve through frequent development cycles. |
| Level 2 | Processing, storage, and other supporting equipment | Equipment that can be refreshed without a complete platform redesign. |
| Level 3 | Apertures, processor chassis and backplanes, and switches | Elements closely connected to the platform's physical design. |
For example, a new processing method may be introduced as a software change while retaining the available aperture and computing hardware. A workload that exceeds the available computing resources may instead require a processor upgrade. A change to an installed aperture reaches a different physical and integration boundary. The MPU structure lets the program connect each proposal to the parts of the system it actually affects.
The architecture also uses Skills to describe collections of Level 1 MPUs that implement a capability across software boundaries. This gives the functional view and procurement view a connection: a capability may involve several cooperating software contributions even though each contribution retains its own defined role.
Accommodating systems with different boundaries
The version 14.0 documentation records the integration of Big Iron and introduces the Assembly concept. An Assembly provides an entry point for implementations that do not use the full Mission System decomposition, including legacy equipment and systems constrained by size, weight, or power. It contains at least one compliant AMS-GRA Service MPU and supplies the software environment and interfaces required by the applicable Assembly requirements. [1]
This matters when a program wants to introduce a capability into equipment that is already fielded. The procurement can identify an Assembly boundary and its included elements instead of treating the existing equipment as though it had been designed around every MPU boundary from the outset. The applicable architecture volumes then define the responsibilities used for integration and assessment.
Reading AMS-GRA becomes easier when the delivered contribution is identified first. The Mission System and software volumes explain the overall organization; the relevant MPU and interface documents explain the contribution being built. The Big Iron article examines how the integration record relates earlier EW architecture work to this structure.
References
- AFLCMC/WA, AMS-GRA v14.0: Executive Summary, Mission System, Software Architecture, and Assembly volumes, April 2026. Distribution A.