Spectral Autonomy

Open Architecture Field Guide

Open architectures divide systems at interfaces that can be specified, implemented, and tested independently. This guide explains the main defense standards and reference architectures by the engineering problem each addresses.

In this guide

What makes a system easier to change

Consider replacing a processor while retaining the sensor that supplies its data and the application that uses its results. The replacement has to connect to the sensor, interpret the data, and provide the services expected by the application. If these relationships are documented, another supplier can design against them. If they exist only inside the original implementation, the upgrade begins by discovering how the system works.

An architecture describes a system's parts and their relationships. An interface specifies the rules at one of those connections: a physical connector, the meaning of a message, or a service one software component can request from another. An open architecture makes selected interface specifications available for use by the organizations developing and integrating those parts.

The intended change gives the interface a purpose. A processor boundary supports a hardware replacement. A software-service boundary supports a change in the implementation behind that service. The component can still contain proprietary hardware or software; openness concerns the information and rights needed to use the selected interface.

The Modular Open Systems Approach (MOSA) connects these design choices to acquisition and sustainment. It asks the program to consider modularity, key interfaces, standards, data rights, and evidence of conformance together. Those activities determine whether the planned technical boundary can support the future competition or replacement the program intends. [1]

How standards and reference architectures contribute

A standard defines shared technical rules. OpenVPX, for example, describes profiles for the connections among plug-in modules, slots, and backplanes. A reference architecture organizes functions and interfaces for a class of systems and can select standards for its connections. An implementation is the equipment and software built to the selected requirements.

These descriptions can apply to the same system at different levels of detail. The platform architecture assigns a processing role to a component. A hardware profile specifies its connections. A software interface defines the services used by its application. Reading them together explains both where the component belongs and how it participates in the system.

Scopes of open-architecture specificationsFour independent groups describe hardware, software interfaces, mission architecture, and navigation. No arrows imply a mandatory sequence.HardwareCards · slotsBackplane connectionsSoftware interfacesApplication servicesMessage definitionsMission architectureSystem functionsIntegration boundariesNavigationSensor measurementsState estimation

Scroll horizontally to inspect the diagram.

Figure 1. The four groups organize specifications by engineering boundary. A program selects interfaces from these domains according to its system requirements.

Following the interface that matters to your design

For a hardware change, start with the physical path between components. OpenVPX explains the relationships among a card, its slot, and the backplane. SOSA places selected profiles within a wider sensor architecture, where timing, management, and processing interfaces also matter. The hardware connection becomes one part of a complete sensing function. [3]

For a software change, begin with the information or service the component needs. UCI explains shared mission-message meaning, while DDS explains how applications publish and receive data. FACE examines the services a portable application uses from its host. These are distinct dependencies, and an upgrade may affect more than one of them.

At mission-system scale, the question becomes how those contributions are allocated and acquired. AMS-GRA organizes sensing, processing, and supporting functions into defined units and interfaces. GARA examines the avionics integration view, and A-GRA describes exchanges around mission-autonomy software. Their scopes help locate a design question within the wider platform. [2]

Navigation offers a concrete example of the same separation. ASPN describes what a measurement means; pntOS organizes software that uses measurements to estimate navigation state. A new sensor enters through the data boundary, while a new estimation method changes the processing behind it. The two can evolve separately because their relationship is explicit. [4]

The chapter list groups the remaining entries around these engineering subjects. Each article follows a particular boundary through an example, so that the standard's name can be related to the equipment, software, and decisions it actually describes.

References

  1. OUSD(R&E), Implementing a Modular Open Systems Approach in DoD Programs, February 2025.
  2. AFLCMC/WA, AMS-GRA v14.0: Executive Summary, Mission System, Software Architecture, and Assembly volumes, April 2026. Distribution A.
  3. The Open Group, Sensor Open Systems Architecture Consortium and Technical Standard.
  4. Kauffman, Carson, and Raquet, ASPN and pntOS: An Open-Source Ecosystem for Building Navigation Systems, ION GNSS+ 2026, pp. 3161–3185.