Search Results

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.

ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.

Per SAE J3016 (2021), the Operational Design Domain (ODD) for a driving automation system is defined as “Operating conditions under which a given driving automation system, or feature thereof, is specifically designed to function, including, but not limited to, environmental, geographical, and time-of-day restrictions, and/or the requisite presence or absence of certain traffic or roadway characteristics.”; in short the ODD defines the limits within which the driving automation system is designed to operate, and as such, will only operate when the parameters described within the ODD are satisfied.. This information Report serves to provide terminology, definitions and taxonomy for use in describing an ODD and respective elements for a driving automation system. This classification and definition of a harmonized set of ODD elements is based on the collection and analysis of existing information from multiple sources.

This document is a list with definitions of terms and taxonomies related to ADS V&V.

This recommended practice provides users with raw GNSS measurements to facilitate positioning, navigation, or timing solutions.

This standard provides recommended practices to significantly enhance the ability of PNT users to defend against a range of interference, jamming, and spoofing phenomena.

This standard establishes the inertial and health monitoring data interface requirements for inertial measurement units used for military and aerospace vehicle applications.

This standard establishes the SAE2020 compliant inertial data interface requirements for simulator integration with inertial navigation systems used for military and aerospace vehicle applications.

This standard defines a test plan to verify an inertial measurement unit interface meets the requirements of SAE2020.

There are numerous GNSS user equipment interface standards in use that provide some form of timing and/or positioning information. This document incorporates their essential content into a uniform array that will enable seamless interoperation with eLoran.

There are numerous GNSS user equipment interface standards in use that provide some form of timing and/or positioning information. This document incorporates their essential content into a uniform array that will enable seamless interoperation with eLoran.

This standard provides guidelines for resilient GNSS receivers.

This standard defines how a resilient GNSS receiver provides enough information for an alternative PNT source to be selected when the GNSS receiver does not meet the required levels of accuracy, availability, integrity, or continuity even when the GNSS signals are subject to interference

This document identifies the essential components required to receive the transmitted eLoran signal. This standard works in concert with the SAE9990 family of standards.

This specification covers resin-bonded glass fibers in the form of felted pads, flat or in rolls.

This specification covers resin-bonded glass fibers in the form of felted pads, flat or in rolls.