GARA: A reference for avionics integration
Part of the Open Architecture Field Guide.
The Air Force's Government Avionics Reference Architecture (GARA) provides a reference for applying open-system principles and existing standards. It organizes the relationship between mission interfaces, portable software, and platform-specific implementations.
In this guide
Bringing separate avionics functions into one aircraft
An aircraft's avionics include its navigation, communications, sensing, and mission-processing equipment. Each function can have a well-designed internal architecture and still be difficult to integrate with the others. A navigation unit produces information that other equipment needs; a mission application consumes sensor reports; the platform must support the computers and communication paths that connect them. Someone has to specify those relationships across subsystem boundaries.
The Government Avionics Reference Architecture (GARA) addresses this aircraft-level view. The Air Force describes it as a way to combine standards into an avionics suite, with interfaces both within and between subsystems. A program can apply the parts relevant to its design. The purpose is to give the platform team and equipment suppliers a common basis for deciding how their contributions fit together. [1]
That role explains why a reference architecture sits above individual interface specifications. A standard can define a software interface or a class of messages. The aircraft architecture assigns those interfaces to actual functions, identifies who provides each service, and describes how information moves through the assembled system.
Following a software upgrade across its interfaces
Consider a mission application that receives navigation data and sensor reports, combines them, and sends a result to a display. The program wants to move that application to a replacement computer while retaining the surrounding equipment. This example exposes two different integration problems.
The first concerns the application and its computer. The application needs operating-system services, access to input data, and a way to exchange information with other software. If those dependencies are scattered through device-specific code, the move requires changes throughout the application. The Future Airborne Capability Environment (FACE) organizes software into segments with defined interfaces so that portable application logic can be separated from services tied to the host. [3]
The second problem concerns the application and the rest of the aircraft. Navigation equipment still has to supply usable information, sensor reports still have to reach the application, and the display still has to interpret its output. Open Mission Systems (OMS) addresses this mission-system integration boundary. Its interfaces describe exchanges through which a component participates in the wider system. [2]
The aircraft team needs both views to plan the upgrade. The host-software view identifies the services the replacement computer must provide. The mission-system view identifies the exchanges that must continue to work with the retained equipment. A reference architecture brings these decisions into a common system description, so that changing the computer does not leave the surrounding responsibilities implicit.
Scroll horizontally to inspect the diagram.
Building a new platform and changing an existing one
On a new aircraft, the platform team can define these boundaries before selecting equipment. It can allocate functions to subsystems, choose interface standards for the connections, and give suppliers requirements for the same overall design. Integration then checks whether those separately developed contributions perform their assigned roles together.
A modernization program starts with an installed system. Its equipment already exchanges data through particular interfaces, and its software already depends on particular services. The engineering task begins by tracing those dependencies. That trace shows which interfaces can be preserved, which need adaptation, and which equipment has to change with the upgraded function.
For the application example, a team might preserve the sensor and display interfaces while replacing the host computer and the software that connects the application to it. A later upgrade could change a sensor while keeping the application's input interface stable. The sequence follows the actual dependencies in the aircraft; it becomes easier to plan when the architecture makes those dependencies visible.
Relating GARA to the other reference architectures
The wider guide examines several of the boundaries that appear in this aircraft-level picture. AMS-GRA describes mission-system functions and the units through which they are acquired and integrated. A-GRA describes information exchanged by mission-autonomy software. FACE addresses software dependencies, while OMS addresses participation in a mission system.
Reading these scopes together helps an engineer locate a design question. A question about moving application logic to another computer concerns its host interfaces. A question about exchanging a sensor report concerns the mission interface and message definition. A question about allocating those responsibilities across the aircraft belongs in the platform architecture. GARA provides the avionics context in which those more specific choices are brought together.
References
- Air Force Materiel Command, Architecture models shorter production times, August 27, 2021.
- OACWG / AFLCMC, Open Mission Systems Standard v2.5: Definition and documentation set.
- The Open Group, FACE Technical Standard and approach.