ARINC SdlRptJan21

Software Distribution and Loading (SDL) Subcommittee Meeting Report, January 2021

Last Published: 
Wednesday, February 10, 2021

Software Distribution and Loading (SDL) Subcommittee Meeting Report. Meeting held January 20, 2021, online meeting.

The AEEC Software Distribution and Loading (SDL) Subcommittee met to discuss airborne software and data management. Current and proposed projects include:

ARINC Project Initiation/Modifications (APIM)

The group reviewed two proposed projects from industry:

  • Initiate work on Supplement 4 to ARINC 615A: Software Data Loader Using Ethernet Interface. The work would add material to the standard to facilitate concurrent (parallel) loading to one or more aircraft component targets
  • Begin a new project on design guidance for aircraft components to maximize the potential of modern multicore processors and hardware architecture

All meeting participants supported each proposal and provided comments to enhance the APIMs’ acceptance by industry.

Supplement 1 to ARINC Specification 645: Common Terminology and Functions for Software Distribution and Loading Ground Systems for e-Enabled Aircraft

The SDL Subcommittee reviewed inputs from MBS Electronic Systems and Boeing. Consensus was reached on all submitted material. The document is expected to be offered for adoption at the 2021 AEEC General Session.

ARINC Project Paper 851: Software Ground Systems for e-Enabled Aircraft

In accordance with the meeting agenda, the group did not discuss new material for this document. This project is chartered by APIM 16-015A. The document may be mature in late 2021.

Future Work

The next SDL Subcommittee meeting is scheduled for February 24, 2021. Details for future meetings for each of these topics can be found here:  https://www.aviation-ia.com/activities/software-distribution-and-loading-sdl-subcommittee

Non-Member Price:
$127.00

Need Help with an Order?

Customer Service Illustration

Customer Service

telephone: +1 443.534.7439
[email protected] 

Notice an Error?

Report it using our errata form.