Search Results

This document is intended to be contractually binding when specifically called out in a specification, Statement of Work (SOW), or when required by a Data Item Description (DID). Any and all contractor changes, alterations, or testing deviations to this section shall be separately listed for easy review.

This document sets forth guidance for life-cycle management of public/private (i.e., asymmetric) keys that are used to secure interactions among systems.

This document contains guidance for using SAE publications, AS4112 through AS4117 (MIL-STD-1553 related Test Plans). Included herein are the referenced test plan paragraphs numbers and titles, the purpose of the test, the associated MIL-STD-1553 paragraph, commentary concerning test methods and rationale, and instrumentation requirements.

This test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise tests.

This test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.

Includes the protocol and timing characteristics for a synchronous backplane data bus capable of transferring data at 60 Mbps using a data path that is two bits wide. The electrical characteristics and behavior expected of the participating modules are defined. ...Defines standards for the transfer of digital data between components within an IMA cabinet. Includes the protocol and timing characteristics for a synchronous backplane data bus capable of transferring data at 60 Mbps using a data path that is two bits wide.

The Flight Data Recorder will be utilized with a Flight Data Acquisition Unit (FDAU) (ARINC Characteristic 573) or a Digital Flight Data Acquisition Unit (DFDAU) (ARINC Characteristic 717) to accommodate mandatory flight data recording and other flight data acquisition needs. ...The Flight Data Recorder will be utilized with a Flight Data Acquisition Unit (FDAU) (ARINC Characteristic 573) or a Digital Flight Data Acquisition Unit (DFDAU) (ARINC Characteristic 717) to accommodate mandatory flight data recording and other flight data acquisition needs. ...The Flight Data Recorder will be utilized with a Flight Data Acquisition Unit (FDAU) (ARINC Characteristic 573) or a Digital Flight Data Acquisition Unit (DFDAU) (ARINC Characteristic 717) to accommodate mandatory flight data recording and other flight data acquisition needs. The document provides guidance and information to ensure customer controlled interchangeability of equipment in a standard aircraft installation and in data retrieval.

This standard sets forth the air transport industry's recommended standards for a digital frequency selection system. This standard addresses two opposite ends of the DFS integration possibilities: a totally centralized and a federated system.

ARINC Characteristic 755 defines a multi-mode receiver capable of providing flight path deviation guidance (corrections) to the aircraft during the approach and landing phase. The data source may be from an Instrument Landing System (ILS), a Microwave Landing System (MLS) or an GNSS Landing System (GLS). ...Supplement 5 adds annunciations defined in RTCA/DO-253D – MOPS for GPS LAAS Airborne Equipment. GNSS Data and GLS Config Validity ARINC 429 Labels are also updated. The range for Selected Glide Path Angle is corrected.

This standard specifies the form, fit and functional definitions for a VHF transceiver capable of voice and data communications. The VHF transceiver supports, 8.33 kHz AM and 25 kHz AM voice, and VDL-2 (31.5 kbps) data link communications as defined by ICAO. ...The VHF transceiver supports, 8.33 kHz AM and 25 kHz AM voice, and VDL-2 (31.5 kbps) data link communications as defined by ICAO. ARINC 631 is a companion standard.

This document defines the steps and documentation required to perform a digital fiber optic link loss budget. This document does not specify how to design a digital fiber optic link. ...This document does not specify the parameters and data to use in a digital fiber optic link loss budget.

As an integral part of the evolution to ANSI/GEIA-859 and the new environment, data management ensures that appropriate information support is available. Data requirements are established that ensure that data are properly timed and accessible, and provide the necessary visibility. ...Data management, originally instituted to address the information needs for the Department of Defense (DoD), has been adopted widely, not only in the defense industrial base, but in insurance, medicine, and other businesses with complex data environments. DM’s purpose has always been to ensure that data are available for any legitimate use whenever needed, for the least cost. ...Data requirements are established that ensure that data are properly timed and accessible, and provide the necessary visibility. The integrity of the data must be ensured regardless of their physical location.

This standard describes the desired characteristics of a data loader intended for use with airborne computers installed on commercial transport aircraft. The data loader transfers data from a tape cartridge to an avionics computer via an ARINC 429 data bus. ...This standard describes the desired characteristics of a data loader intended for use with airborne computers installed on commercial transport aircraft.

The characteristics of a High Frequency Data Link (HFDL) communications system are defined by this standard. It defines avionic system components and the associated HF ground system.

This standard describes the functions to be performed by the airborne components of the HFDL to successfully transfer messages between HF ground stations and avionics systems on aircraft where the data is encoded in a bit-oriented format. ARINC 634 and ARINC 753 are companion standards.

This document specifies the diagnostic data which may be required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. ...This document specifies the diagnostic data which may be required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. SAE J1979 was originally developed to meet U.S. OBD requirements for 1996 and later model year vehicles.

., time-boxed work periods), multiple increments producing Minimum Viable Products (MVP) and synchronized with Model Based Systems Engineering (MBSE) while being digitally transformed? MBSE initiatives drive the jump from “2D” data to “3D” data, thereby becoming a Model-Centric practice. ...The purposeful integration of existing and emerging technologies into CM practice will enable collaboration with supporting systems and provide stakeholders access to authoritative and trusted data in a timely fashion at their desktop to help drive educated decision making. This lays to rest the misguided myth that CM and supporting systems operate at cross-purposes.

This document describes the functions to be performed by airborne and ground components of the VDLM2 to successfully transfer messages from VHF ground networks to avionics systems on aircraft and vice versa where the data are encoded in a code and byte independent format. The compatibility of VDLM2 with OSI is established by defining a set of services and protocols that are in accordance with the OSI basic reference model.

This document describes the functions to be performed by airborne and ground components of the VDLM2 to successfully transfer messages from VHF ground networks to avionics systems on aircraft and vice versa where the data are encoded in a code and byte independent format. The compatibility of VDLM2 with OSI is established by defining a set of services and protocols that are in accordance with the OSI basic reference model.

This document provides background and detailed technical information on existing methods to secure loadable software parts.