DATA LOADING SPECIFICATIONS FOR AIRCRAFT COMPONENTS
|Publication Date:||6 July 2017|
Scope and Purpose
Airlines require the capability to load software into avionic components within the shop maintenance environment. They need the ability to load all types of software as required to perform maintenance of components at all three Component Maintenance Levels (CMLs) as defined in ARINC Report 663: Data Requirements for Avionics Component Maintenance, which are indicated as CML-1, CML-2, and CML-3.
Operators of avionics components should have the option to develop a data load solution for their chosen components as an alternative to purchasing supplier produced equipment. History has shown that there can be a large cost to operators associated with acquiring and maintaining ground equipment when its functional fit, or interface characteristics are not documented as an open standard and are instead treated as proprietary. Information and specifications for communications between aircraft components and data loading equipment is essential for having cost effective support during the entire life cycle of an aircraft.
Specifications and requirements for data loading at all component maintenance levels should be included in the Technical Support Data Package (TSDP) as defined in ARINC Report 625: Industry Guide for Component Test Development and Management. This includes information required to design and implement a data load solution specific to a single component or family of components.
Data loading instructions should also be included in the Component Maintenance Manual (CMM) for each component as required during the performance of shop environment testing and maintenance.
The loading equipment in the CMM may be listed as unique OEM or third party supplied items; however, each item should always include the words "or equivalent" as a qualifier for each piece of data loading equipment listed. This enables the usage of organic or operator-approved data loading equipment.
The focus of this standard is to list and describe the types of information that should be provided as part of the avionics component documentation and the ARINC 625 Technical Support Data Package (TSDP) in regards to loading airborne software into components, subcomponents, and parts.
The current generations of aircraft usually employ airborne data networks for communications between onboard avionics system components. Components that communicate within switched network architectures require clear definitions for shop environment loading when removed from the onboard aircraft network.
This document defines three levels of load processes performed within the shop environment. Several terms that are associated with data loading are defined in Section 1.2. Many of these terms should be understood in order to comprehend some of text that follows in later sections.
This document describes the information required to develop solutions for shop environment loading, including component specific bus interface protocol specifications and software communications protocol specifications. If suppliers and OEMs choose to adhere to these requirements, it will enable custom shop loaders to be developed and maintained by operators or their agents as required. Operators will be able to maintain components throughout the lifecycle of their aircraft fleets.