R-EGI: An open architecture for resilient navigation
Part of the Open Architecture Field Guide.
Resilient-Embedded GPS/INS (R-EGI) is an Air Force navigation architecture that combines GPS and inertial navigation with provisions for additional aiding sources. It separates a common core from platform-specific integration.
In this guide
Combining navigation sources with different strengths
The Global Positioning System (GPS) uses satellite signals to determine position and time. An inertial navigation system (INS) uses onboard measurements of acceleration and rotation to update estimates of position, velocity, and orientation. Because small inertial measurement errors accumulate, the estimate benefits from other observations that help correct its drift.
Using another source for that correction is called aiding. GPS can provide aiding information, and additional sensors can contribute observations when satellite measurements are unavailable or degraded. A navigation system must relate these different observations to a common estimated state while accounting for their timing, meaning, and uncertainty.
Resilient-Embedded GPS/INS (R-EGI) is an Air Force navigation architecture that organizes this combination of sources within an embedded system. The January 2026 program overview describes a reusable common core and a platform interface, separating navigation functions from the connections required by a particular aircraft. [1]
Following a measurement to the aircraft
Consider an additional source that supplies a navigation measurement. The system first needs a defined description of that observation. Fusion software then relates it to the current navigation state and uses it in the estimation process. The resulting navigation information must be delivered in the form required by the aircraft's consumers.
The common core concentrates navigation functions intended for reuse. The platform interface connects those functions to the specific aircraft. This distinction allows a team to work on the navigation implementation while keeping the aircraft's integration requirements visible at a separate boundary.
Scroll horizontally to inspect the diagram.
The figure follows information through these responsibilities. Measurements support the navigation calculation, and the platform interface connects its output to the aircraft. The architecture gives a place to describe both how a new source enters the solution and how that solution is used by the host.
Why the architecture uses several open standards
The R-EGI overview brings together standards that address different parts of this path. ASPN defines navigation measurement information. pntOS provides interfaces for organizing fusion software. These two standards connect the meaning of an observation to the components that process it. [1]
The surrounding software and communication environment has its own interfaces. The Future Airborne Capability Environment (FACE) organizes software dependencies on host services, while Data Distribution Service (DDS) provides data distribution. OpenVPX addresses modular embedded hardware connections. The overview describes the hardware approach in relation to future adoption of the Sensor Open Systems Architecture (SOSA). Each standard therefore contributes to a different boundary within the navigation system.
This division makes an upgrade easier to trace. Introducing a measurement source begins at the data interface and its processing support. Replacing a computer reaches the software-host and hardware interfaces. Changing the connection to an aircraft reaches the platform interface. The architecture relates those changes without treating them as one undifferentiated replacement of the whole system.
Managing navigation functions with different responsibilities
The program overview also distinguishes safety-critical navigation from mission-capability navigation. These functions have different responsibilities within the aircraft, so changes must be managed according to the role of the affected software and the outputs it supplies. [1]
This matters when a program introduces a new aiding method or estimation component. The integration record needs to show where the contribution enters, which functions use it, and which outputs depend on it. That trace connects the proposed navigation improvement to the part of the aircraft system whose behavior may change.
R-EGI thus provides a concrete example of several open-interface ideas used together. The ASPN chapter explains the measurement boundary, and the pntOS chapter explains the software organization used for sensor fusion. The platform view shows how those contributions become part of an aircraft navigation capability.
References
- AFLCMC/ESC MAR JPO, The R-EGI MOSA Overview, January 2026. Public-release approval AFLCMC-2024-0112.