Avionics programs run into the same problems repeatedly: code welded to one board, one OS, one vendor. Every hardware refresh drags re-certification work along with it. Getting components from different suppliers to behave together still eats into the schedule. And the platforms need to remain in service for 20 or 30 years, long after the original processors reach the end of life.

FACE – Future Airborne Capability Environment was designed around these realities. It defines a layered software architecture with standardized interfaces between the layers. Application logic lives at the top. Operating system services, platform adaptation, and hardware I/O sit below. When the board or the RTOS changes, only the affected layers need to be reworked. The application code stays untouched.

This paper walks through the FACE reference architecture and its four segments: PCS, PSSS, OSS, and IOSS. It explains the three FACE profiles, General-Purpose, Safety, and Security, and how each one maps to different assurance needs. It also covers where FACE fits alongside DO-178C, DO-297, DO-326A, and ARINC 653, and how real-time operating systems like LynxOS and VxWorks plug into the architecture.

FACE is not a certification standard in and of itself. It does not replace DO-178C or any of the safety and security guidance that still applies in full. What it does is give programs a cleaner architectural foundation, better traceability, tighter change isolation, and a realistic path to reusing certified software when the platform underneath changes.

The paper also covers practical use cases, mission system modernization, UAV software reuse, and multi-vendor avionics integration, along with a phased adoption roadmap and the success factors that matter most when rolling FACE into a real program.