Future Airborne Capability Environment

Last updated

The Open Group Future Airborne Capability Environment (FACE Consortium) was formed in 2010 to define an open avionics environment for all military airborne platform types. Today, it is a real-time software-focused professional group made up of industry suppliers, customers, academia, and users. The FACE approach is a government-industry software standard and business strategy for acquisition of affordable software systems that promotes innovation and rapid integration of portable capabilities across programs. The FACE Consortium provides a vendor-neutral forum for industry and government to work together to develop and consolidate the open standards, best practices, guidance documents, and business strategy necessary to result in: [1]

Contents

The FACE Technical Standard is an open real-time standard for making safety-critical computing operations more robust, interoperable, portable and secure. Although the consortium started with a focus on avionics, the applicability of the technical standard and its associated data model have become much broader. The standard enables software developers to create and deploy a wide catalog of applications for use across the entire spectrum of real-time systems through a common operating environment. The latest edition of the standard further promotes application interoperability and portability with enhanced requirements for exchanging data among FACE components, including a formally specified data model, and emphasis on defining common language requirements for the standard.

Membership

Until 2022, individual members were required to be US persons. In 2022, the consortium moved to open membership to the countries of Canada, Australia, New Zealand, the United Kingdom, and the United States. Individuals can only become members if they are employed by a company that is a member.

Corporate membership is at different levels. The sponsor-level members are Boeing, Collins Aerospace, Lockheed Martin, US Air Force LCMC, and US Army PEO Aviation, and US Naval Air Systems Command.

Background

The FACE effort sprang from US Navy open architecture programs, [2] promoted by the US Naval Air Systems Command (NAVAIR), to enhance interoperability and software portability for avionics software applications across DoD aviation platforms. Both the US Army and US Air Force have been participating in the consortium. NAVAIR led the pack with early acquisitions, followed later by Army and Air Force. [3] [4] [5]

The FACE Consortium was formed by The Open Group as a "Voluntary Consensus Standards Body", as defined by the National Technology Transfer Act and OMB Circular A-119. This facilitates government participation in the consortium. [6] One goal of the effort is to reduce the typical development and deployment cycle of new capabilities in military airborne platforms from as long as six years under the current methodology to as little as six months. [7]

The FACE reference architecture ecosystem includes software product conformance verification and certification processes. [8] In October 2016, a suite of flight management software earned the first FACE certificate of conformance. [9] One may view information on all certified FACE conformant products at the FACE Registry

Technical approach

The FACE technical approach tackles barriers to software modularity, portability, and interoperability by defining a Reference Architecture and employing design principles to enhance software portability. To meet the objectives of the technical approach, the FACE Technical Standard uses a standardized architecture describing a conceptual breakdown of functionality, called the FACE Reference Architecture, to promote the reuse of software components able to share common functionality across disparate systems. This architecture defines standardized interfaces to allow software components to be moved between systems, including those developed by different vendors. The standardized interfaces follow a data architecture to ensure the data communicated between the software components is fully described to facilitate their integration on new systems.

FACE Reference Architecture FACE Reference Architecture.png
FACE Reference Architecture

The FACE Reference Architecture is composed of logical segments where variance occurs. The structure created by connecting these segments together is the foundation of the FACE Reference Architecture. The five (5) segments of the FACE Reference Architecture are the Operating System Segment (OSS), Input/Output Services Segment (IOSS), Platform-Specific Services Segment (PSSS), Transport Services Segment (TSS), and Portable Components Segment (PCS).

The FACE Reference Architecture defines a set of standardized interfaces providing connections between the FACE architectural segments. The standardized interfaces within the FACE Reference Architecture are the Operating System Segment Interface (OSS Interface), the Input/Output Services Interface (IOS Interface), the Transport Services Interfaces, and Component-Oriented Support Interfaces.

The FACE Reference Architecture defines three FACE OSS Profiles tailoring the Operating System (OS) Application Programming Interfaces (APIs), programming languages, programming language features, run-times, frameworks, and graphics capabilities to meet the requirements of software components for differing levels of criticality. The three Profiles are Security, Safety, and General Purpose. The Security Profile constrains the OS APIs to a minimal useful set allowing assessment for high-assurance security functions executing as a single process. The Safety Profile is less restrictive than the Security Profile and constrains the OS APIs to those that have a safety certification pedigree. The General Purpose Profile is the least constrained profile and supports OS APIs meeting real-time deterministic or non-real-time, non-deterministic requirements depending on the system or subsystem implementation.

The FACE Data Architecture defines the FACE Data Model Language (including the language binding specification), Query and Template language, FACE Shared Data Model (SDM) and the rules of construction of the Unit of Portability (UoP) Supplied Model (USM). Each PCS Unit of Conformance (UoC), PSSS UoC, or TSS UoC providing using TS Interfaces is accompanied by a USM consistent with the FACE SDM and defines its interfaces in terms of the FACE Data Model Language. A Domain-Specific Data Model (DSDM) captures content relevant to a domain of interest and can be used as a basis for USMs.

Related Research Articles

<span class="mw-page-title-main">Object Management Group</span> Computer industry standards consortium

The Object Management Group (OMG) is a computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a range of technologies.

Interoperability is a characteristic of a product or system to work with other products or systems. While the term was initially defined for information technology or systems engineering services to allow for information exchange, a broader definition takes into account social, political, and organizational factors that impact system-to-system performance.

An open standard is a standard that is openly accessible and usable by anyone. It is also a prerequisite to use open license, non-discrimination and extensibility. Typically, anybody can participate in the development. There is no single definition, and interpretations vary with usage.

Health Level Seven or HL7 refers to a set of international standards for transfer of clinical and administrative data between software applications used by various healthcare providers. These standards focus on the application layer, which is "layer 7" in the OSI model. The HL7 standards are produced by Health Level Seven International, an international standards organization, and are adopted by other standards issuing bodies such as American National Standards Institute and International Organization for Standardization.

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complexity of developing applications that span multiple operating systems and network protocols. The middleware creates a distributed communications layer that insulates the application developer from the details of the various operating systems and network interfaces. APIs that extend across diverse platforms and networks are typically provided by MOM.

OpenMAX, often shortened as "OMX", is a non-proprietary and royalty-free cross-platform set of C-language programming interfaces. It provides abstractions for routines that are especially useful for processing of audio, video, and still images. It is intended for low power and embedded system devices that need to efficiently process large amounts of multimedia data in predictable ways, such as video codecs, graphics libraries, and other functions for video, image, audio, voice and speech.

The Khronos Group, Inc. is an open, non-profit, member-driven consortium of 170 organizations developing, publishing and maintaining royalty-free interoperability standards for 3D graphics, virtual reality, augmented reality, parallel computation, vision acceleration and machine learning. The open standards and associated conformance tests enable software applications and middleware to effectively harness authoring and accelerated playback of dynamic media across a wide variety of platforms and devices. The group is based in Beaverton, Oregon.

Representational state transfer (REST) is a software architectural style that describes a uniform interface between physically separate components, often across the Internet in a client-server architecture. REST defines four interface constraints:

Aeronautical Radio, Incorporated (ARINC), established in 1929, was a major provider of transport communications and systems engineering solutions for eight industries: aviation, airports, defense, government, healthcare, networks, security, and transportation. ARINC had installed computer data networks in police cars and railroad cars and also maintains the standards for line-replaceable units.

Joint Architecture for Unmanned Systems (JAUS), formerly known as Joint Architecture for Unmanned Ground Systems (JAUGS), was originally an initiative started in 1998 by the United States Department of Defense to develop an open architecture for the domain of unmanned systems.

The Software Communications Architecture (SCA) is an open architecture framework that defines a standard way for radios to instantiate, configure, and manage waveform applications running on their platform. The SCA separates waveform software from the underlying hardware platform, facilitating waveform software portability and re-use to avoid costs of redeveloping waveforms. The latest version is SCA 4.1.

SensorML is an approved Open Geospatial Consortium standard. SensorML provides standard models and an XML encoding for describing sensors and measurement processes. SensorML can be used to describe a wide range of sensors, including both dynamic and stationary platforms and both in-situ and remote sensors.

<span class="mw-page-title-main">BioAPI</span> Biometric Interworking Protocol

BioAPI is a key part of the International Standards that support systems that perform biometric enrollment and verification. It defines interfaces between modules that enable software from multiple vendors to be integrated together to provide a biometrics application within a system, or between one or more systems using a defined Biometric Interworking Protocol (BIP) – see below.

Allied Standards Avionics Architecture Council, or ASAAC, is an effort to define and validate a set of Open Architecture Standards for Avionics Architecture, particularly in the field of Integrated Modular Avionics.

<span class="mw-page-title-main">View model</span>

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of a whole system from the perspective of a related set of concerns.

<span class="mw-page-title-main">Open-system environment reference model</span>

Open-system environment (OSE) reference model (RM) or OSE reference model (OSE/RM) is a 1990 reference model for enterprise architecture. It provides a framework for describing open system concepts and defining a lexicon of terms, that can be agreed upon generally by all interested parties.

<span class="mw-page-title-main">Open Geospatial Consortium</span> Standards organization

The Open Geospatial Consortium (OGC), an international voluntary consensus standards organization, originated in 1994. In the OGC, more than 500 commercial, governmental, nonprofit and research organizations collaborate in a consensus process encouraging development and implementation of open standards for geospatial content and services, sensor web and Internet of Things, GIS data processing and data sharing.

<span class="mw-page-title-main">Application Portability Profile</span>

The Application Portability Profile (APP) is a 1990s framework for Open-System Environment designed by the NIST for use by the U.S. Government. It contains a selected suite of specifications that defines the interfaces, services, protocols, and data formats for a particular class or domain of applications.

<span class="mw-page-title-main">UGV Interoperability Profile</span>

UGV Interoperability Profile , Robotics and Autonomous Systems – Ground IOP or simply IOP was originally an initiative started by the United States Department of Defense (DoD) to organize and maintain open architecture interoperability standards for Unmanned Ground Vehicles (UGV). A primary goal of this initiative is to leverage existing and emerging standards within the Unmanned Vehicle (UxV) community such as the Society of Automotive Engineers (SAE) AS-4 Joint Architecture for Unmanned Systems (JAUS) standard and the Army Unmanned Aircraft Systems (UAS) Project Office IOPs.

MPEG-G is an ISO/IEC standard designed for genomic information representation by the collaboration of the ISO/IEC JTC 1/SC 29/WG 9 (MPEG) and ISO TC 276 "Biotechnology" Work Group 5. The goal of the standard is to provide interoperable solutions for data storage, access, and protection across different possible implementations for data information generated by high-throughput sequencing machines and their subsequent processing and analysis. The standard is composed of different parts, each one addressing a specific aspect, such as compression, metadata association, Application Programming Interfaces (APIs), and a reference software for data decoding. Together with the reference decoder software, commercial and open source implementations started to be available in 2019, covering progressively more of the published parts of the standard.

References

  1. FACE Consortium Information, uploaded with permission
  2. FACE initiative takes aim at improved interoperability and standards among future military avionics platforms
  3. AV-8B, C-130T Will Be First To Meet Navy’s FACE Avionics Software Standards
  4. "Joint Multi Role Program is preparing for Future Vertical Lift Mission Systems Architectures | Article | The United States Army".
  5. https://www.opengroup.us/face/documents/18467/Infinite_Dimensions_Prototype_Paper_Air_Force_FACE_TIM_v6.pdf [ bare URL PDF ]
  6. FACE Consortium : Frequently Asked Questions
  7. U.S. Navy, Army Seek Open-Airborne Computing
  8. "FACE Conformance | The Open Group". www.opengroup.org. Retrieved 2016-11-22.
  9. TeamAirsoc. "ROCKWELL COLLINS RECEIVES THE FIRST FACE CONFORMANCE CERTIFICATE FOR RNP RNAV CAPABLE FMS - airsoc.com". Airsoc.com. Retrieved 2016-11-22.