ARINC IA Project Initiation/Modification (APIM)
Name of proposed project APIM #: __15-102_
FLS Working Group
Supplement 2 to ARINC Report 667: Guidance for the Management of
Field Loadable Software
Suggested Subcommittee assignment
The purpose of this document is to open a project for update of ARINC 667.
The ARINC specification covers guidance for the management of software
that is loadable aboard aircraft, referred to as Field Loadable Software
(FLS).
New technologies, shifts in maintenance practices, policies in handling and
management of Field Loadable Software (FLS), comprising both Loadable
Software Aircraft Parts (LSAP) and Aeronautical Data Bases or (ADBs) and
recent update to Electronic Distribution of Software, drive the need for this
specification to be re-opened.
Project Scope
ARINC 667 was last updated November 12, 2010. Several standards relating
to airborne software management have been updated. This has been a
continuous evolutionary process to foster and maintain common terminology,
management practices, communications standards, storage formats, and
distribution methods related to aircraft software configuration management.
Aircraft software management requires common understanding and guidance
to remain in sync with all operators, suppliers, OEMs, and airframe
manufacturers. ARINC Report 667 has continued to be the industry guide and
reference document for high level aspects of software management. It
provides standardized language and terms, software categorization and
criticality, software security guidance, etc.
It is very important to update this document to be in sync with evolved
technology, methodology, and terminology that has changed in several other
ARINC standards related to aircraft software management. Several documents
have been updated since the current supplement 1 of ARINC 667 was
published. Examples of ARINC standards that are related to aircraft software
management are as follows:
ARINCNumber Sup Title PublishDate Note
ARINCReport614 0 StandardFirmwareLoaderforAvionics September30,1989
Shops
ARINCReport6153 3 AirborneComputerHighSpeedData August15,1992
Loader
ARINCReport6154 4 AirborneComputerHighSpeedData May6,2002
Loader
ARINCReport666 0 ElectronicDistributionofSoftware May17,2002
ARINCReport6653 3 LoadableSoftwareStandards August12,2005
ARINCReport615A3 3 SoftwareDataLoaderUsingEthernet June30,2007
Interface
ARINCReport827 0 ElectronicDistributionofSoftwareby September15,2010
Crate(EDSCrate)
ARINCReport6671 1 GuidancefortheManagementofField November12,2010 AMCStandard
LoadableSoftware
ARINCReport835 0 GuidanceforSecurityofLoadable November23,2011
SoftwarePartsUsingDigitalSignatures
ARINCReport8261 1 SoftwareDataLoaderUsingCAN December20,2013
Interface
ARINCReport8351 1 GuidanceforSecurityofLoadable January2,2014 Supplementonly
SoftwarePartsUsingDigitalSignatures forpatentissue
ARINCSpecification838 0 LoadableSoftwarePartDefinition January2,2014
Format
ARINCSpecification641 0 LogicalSoftwarePartPackagingfor July31,2015
Transport
ARINCSpecification843 0 ARINCSpecification843:Aircraft July31,2015
SoftwareCommonConfiguration
Reporting
ARINCSpecification844 0 EnhancedARINC429DataLoading,and April1,2016 StillInWork.Soon
Targetimplementationconsiderations tobePublished.
forARINC6153andARINC6154targets
ARINCReport849 0 SoftwareDataLoadingSpecification April1,2016 StillInWork.Soon
RequirementsfortheAvionicsShop tobePublished.
Environment.
Project Benefit
Benefits for Airlines:
Airlines, and this industry as a whole, benefit tremendously by having this
standard that defines the common terminology and processes used in the wide
scope of aircraft software & data management. The document provides the
high level overview of data loading issues related to format, distribution,
storage, security, definitions of software types and process standards for each,
and aircraft software configuration management.
This document also provides reference to other ARINC documents regarding
specific aspects of software data loading.
Benefits for Airframe Manufacturers:
Airframe manufacturers use this document to keep their processes in sync
with those of their customers, the Airlines. This document is developed by
consensus with the airframe manufacturer representative. It defines the
common expectations, requirements, and language of their customer in regard
to software data loading and management.
Benefits for Avionics Equipment Suppliers:
Avionics Equipment Suppliers use this document to keep their processes in
sync with those of their customers, the Airlines. This document is developed
by consensus with the airframe manufacturer representative. It defines the
common expectations, requirements, and language of their customer in regard
to software data loading and management.
Airlines supporting effort
Proposed Chairman:
o Ted Patmore Delta Air Lines
Lead Air Line:
o Delta Air Lines Ted Patmore
Supporting Air Lines:
o American Air Lines Rod Gates
Air Lines:
o
Airframe Manufacturers:
o Airbus Anne Frayssignes
o Boeing Todd Gould
o
Avionics Vendors:
o Honeywell Steve Darr
o Teledyne Controls Chris Kuske
o Sagem Denis Delville
o Techsat William McRae
o Aero Instruments
o Avionics Interface Technology Troy Troshynska
o Auvation Ian Vinnicombe
Issues to be worked
Update terms, part number formats, and other methods as a result of new
technology.
Support changes due to A838, A665-4/5, A641
UMS Need better guidance for installing on AC for troubleshooting.
Easier way to get UMS part on a plane. Improve airline process for putting
UMS on aircraft.
Software configuration management
Configuration management tools.
USB security and usage
PDL Security Guidance
Recommended Coordination with other groups
This project should be closely coordinated with the AEEC Software Data
Loading (SDL) WG
AEEC NIS regarding security issues.
Projects/programs supported by work
Software data management is an continuous effort by the industry to maintain
the continuing airworthiness of airline fleets. Changing technology that
requires new methods and terminology require standards that are in sync with
the latest processes that maintain compliant aircraft software configuration.
Timetable for projects/programs
02/2018
Documents to be produced and date of expected result
Supplement 2 to ARINC Report 667: Guidance for the Management of
Field Loadable Software
Comments
Anything else deemed useful to the committees for prioritization of this work.
Meetings
Activity Mtgs Mtg-Days
ARINC 667 Supp 2 6 12
Document b # of mtgs # of mtg days
For IA Staff use
Date Received: IA Staff Assigned:
Potential impact:
(A. Safety B. Regulatory C. New aircraft/system D. Other)
Forward to committee(s) (AEEC, AMC, FSEMC): Date Forward:
Committee resolution:
(0 Withdrawn 1 Authorized 2 Deferred 3 More detail needed 4 Rejected)
Assigned Priority: Date of Resolution:
A. High (execute first) B. Normal (may be deferred for A.)
Assigned to SC/WG:
