1、 AN DOCUMENT Prepared by AMC Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 GUIDANCE FOR THE MANAGEMENT OF FIELD LOADABLE SOFTWARE ARINC REPORT 667-1 PUBLISHED: November 12, 2010 This document is published information as defined by 15 CFR Section 734.7 of the Ex
2、port Administration Regulations (EAR). As publicly available technology under 15 CFR 74.3(b)(3), it is not subject to the EAR and does not have an ECCN. It may be exported without an export license. DISCLAIMER THIS DOCUMENT IS BASED ON MATERIAL SUBMITTED BY VARIOUS PARTICIPANTS DURING THE DRAFTING P
3、ROCESS. NEITHER AEEC, AMC, FSEMC NOR ARINC HAS MADE ANY DETERMINATION WHETHER THESE MATERIALS COULD BE SUBJECT TO VALID CLAI MS OF P ATENT, COPYRIG HT OR OT HER PRO PRIETARY RIGHTS BY THIRD PARTIES, A ND NO RE PRESENTATION OR WARRANTY, E XPRESS O R IMPLIED, IS MADE IN THIS REGARD. ARINC I NDUSTRY AC
4、T IVITIES US ES RE ASONABLE E FFORTS TO DEVELOP A ND MAINTAIN THESE DOCUMENTS. HOWEVER, NO CERTIFICATION OR WARRANTY IS MADE AS TO THE TECHNICAL ACCURACY OR SUFFICIENCY OF THE DOCUMENTS, THE ADEQ UACY, MERCHANT ABILITY, FITNESS FOR INT ENDED PURPOSE OR SAFETY OF A NY PRODUCTS, COMPONENTS, OR S YSTEM
5、S DESIGNED, TESTED, RATED, INSTALLED OR OPERATED IN ACCORDANCE WITH ANY ASPECT OF THIS DOCUMENT OR T HE ABSENCE OF RI SK OR HAZARD ASSOCIATED WITH SUCH PRODUCTS, COMPO NENTS, OR S YSTEMS. T HE USER OF T HIS DO CUMENT ACKNOWLEDGES THAT IT SHALL BE SOLELY RESPONSIBLE FOR ANY LOSS, CLAIM OR DAMAGE THAT
6、 IT MAY INCUR IN CONNECTION WITH ITS USE OF OR RELIANCE ON T HIS DOCUMENT, AND SHALL HOLD ARINC, AEEC, AMC, F SEMC AND ANY PARTY THAT PARTICIPATED IN THE DRAFTING OF THE DOCUMENT HARMLESS AGAINST ANY CLAIM ARISING FROM ITS USE OF THE STANDARD. THE USE IN THIS DOCUMENT OF AN Y TERM, SUCH AS SHALL OR
7、MUST, IS NOT INTENDED T O AFFECT THE ST ATUS OF T HIS DOCUME NT AS A VOLUNT ARY STANDARD OR IN ANY WAY T O MODI FY T HE ABOVE DIS CLAIMER. NOT HING HEREIN SHA LL BE DE EMED T O REQUIRE A NY P ROVIDER OF EQUIP MENT TO INCORPORATE ANY ELEMENT OF THIS STANDARD IN ITS PRODUCT. HOWEVER, VENDORS WHICH REP
8、RESENT THAT THEIR PRODUCTS ARE COMPLIANT WITH THIS STANDARD SHALL BE DEEMED ALSO TO HAVE REPRESENTED THAT THEIR PRODUCTS CONTAIN OR CONFORM TO THE FEATURES THAT ARE DESCRIBED AS MUST OR SHALL IN THE STANDARD. ANY USE O F OR RE LIANCE ON T HIS DO CUMENT SHALL CONSTITUTE A N ACCEPTANCE THEREOF “AS IS”
9、 AND BE SUBJECT TO THIS DISCLAIMER. 2010 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the AMC Report 667 Adopted by the AEEC Committee April 8, 2002 Summary of Document Supplements Supplement Adopti on Date Published Specification 667-1 October 6, 2010 No
10、vember 12, 2010 A description of the changes introduced by each supplement is included at the end of this document. ARINC REPORT 667-1 GUIDANCE FOR THE MANAGEMENT OF FIELD LOADABLE SOFTWARE Published: November 12, 2010ii FOREWORD Aeronautical Radio, Inc., the AMC, and ARINC Standards ARINC organizes
11、 aviation industry committees and participates in related industry activities that benefit aviation at large by providing technical leadership and guidance. These activities directly support aviation industry goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operation
12、s. ARINC Industry Activities organizes and provides the secretariat for international aviation organizations (AEEC, AMC, FSEMC) which coordinate the work of aviation industry technical professionals and lead the development of technical standards for airborne electronic equipment, aircraft maintenan
13、ce equipment and practices and flight simulator equipment and used in commercial, military, and business aviation. The AEEC, AMC, and FSEMC develop consensus-based, voluntary standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results in substantial ben
14、efits to the aviation industry by allowing avionics interchangeability and commonality and reducing avionics cost by promoting competition. There are three classes of ARINC Standards: a) ARINC Characteristics Define the form, fit, function, and interfaces of avionics and other airline electronic equ
15、ipment. ARINC Characteristics indicate to prospective manufacturers of airline electronic equipment the considered and coordinated opinion of the airline technical community concerning the requisites of new equipment including standardized physical and electrical characteristics to foster interchang
16、eability and competition. b) ARINC Specifications Are principally used to define either the physical packaging or mounting of avionics equipment, data communication standards, or a high-level computer language. c) ARINC Reports Provide guidelines or general information found by the airlines to be go
17、od practices, often related to avionics maintenance and support. The release of an ARINC Standard does not obligate any organization or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does
18、it constitute endorsement of any manufacturers product designed or built to meet the ARINC Standard. In order to facilitate the continuous product improvement of this ARINC Standard, two items are included in the back of this volume: An Errata Report solicits any corrections to the text or diagrams
19、in this ARINC Standard. An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for addition of substantive material to this volume which would be the subject of a new Supplement. ARINC REPORT 667 TABLE OF CONTENTS iii 1.0 INTRODUCTION.1 1.1 Purpose and Goal1 1.2 Vision.
20、1 1.2.1 Scope2 1.2.2 Background.2 1.3 Configuration Management.3 1.3.1 Need for Aircraft Configuration Management.3 1.3.2 Current Practices3 1.3.3 Pre-Loading of Spare Target Hardware4 1.4 Part Numbers4 1.4.1 Software Part Numbers4 1.4.2 Media Set Part Number5 1.4.3 Hardware Part Numbers.5 1.5 Basic
21、 Rules for LSP.6 1.5.1 Aircraft Level Configuration Control6 1.5.2 Replacement of Hardware Parts on-aircraft.6 1.5.3 Software as an Aircraft Part6 1.5.4 Spare Target Hardware6 1.5.5 Aircraft System Function.6 1.5.6 Target Hardware Loadability.7 1.5.7 Logistics of Spare LSPs7 1.5.8 Electronic Transfe
22、r of Software7 1.5.9 Physical Media Processing.7 1.6 Mass Storage Media8 1.6.1 Mass Storage Devices on-aircraft.8 1.6.2 Transport Media Types.8 1.7 Types of Aircraft Controlled Software8 1.8 Process Overview8 1.8.1 Overview of Field Loadable Software Management.13 1.8.1.1 Loadable Software Aircraft
23、Parts Configuration Management.13 1.8.1.2 Signed Electronic Parts Management Process13 1.8.1.3 Unsigned Parts Management Process.15 1.8.2 ARINC Documents.15 1.8.3 Non-ARINC Documents16 1.9 Procedures17 1.9.1 Supply Chain17 1.9.2 Maintenance Handling and Storage.18 1.9.3 Onboard Aircraft Loading19 1.
24、9.4 Off-Aircraft Loading.19 1.10 Airline Rights and Entitlements20 1.10.1 Rights to Copy21 1.10.2 Entitlements21 1.10.3 Authorization to Copy.21 1.10.3.1 Seller Furnished Equipment.22 1.10.3.2 Seller Purchased Equipment22 1.10.3.3 Buyer Furnished Equipment.22 2.0 TYPES OF FIELD LOADABLE SOFTWARE23 2
25、.1 General23 2.2 Airborne Software and Data23 2.2.1 Airborne Support Data24 ARINC REPORT 667 TABLE OF CONTENTS iv 2.2.2 Airborne Software.24 2.2.3 Software Design Assurance Levels24 2.2.4 Hardware Controlled Software24 2.2.4.1 Resident Software24 2.2.4.2 Hardware Controlled Loadable Software Part25
26、2.2.5 Aircraft Controlled Software25 2.2.5.1 Aircraft Controlled Loadable Software Part25 2.2.6 Loadable Software Part25 2.2.7 Types of ACLSP.25 2.2.7.1 LSAP25 2.2.7.1.1 User Modifiable Software26 2.2.7.1.2 User Certifiable Software26 2.2.7.1.3 Supplier Controlled Software.27 2.2.7.1.3.1 Operational
27、 Program Software.27 2.2.7.1.3.2 Option Selectable Software27 2.2.7.2 Aeronautical Databases.28 2.2.7.2.1 Navigation Database.28 2.2.7.2.2 Terrain/Airport Database.29 2.2.7.3 Flight Operations Software.29 2.2.7.4 Maintenance Operations Software.29 2.2.7.5 Technical Publications.30 2.2.7.6 Uncategori
28、zed ACLSPs.30 3.0 SOFTWARE DEVELOPED BY USERS31 3.1 General31 3.1.1 Creation and Modification Methods32 3.1.1.1 User Modifiable Software from Designees.32 3.1.1.2 Operators Acting as Designees.33 3.1.2 Configuration Management33 3.1.2.1 Authorization Documentation.33 3.1.3 Release of UMS34 3.1.3.1 D
29、esign Process34 3.1.3.2 Change Log34 3.1.3.3 Identification.35 3.1.3.4 Quality Assurance Process36 3.1.3.5 Testing.36 3.1.3.6 Storage of Released UMS Parts36 3.1.3.7 Physical Transport Media.36 3.1.3.8 Backups and Archives37 3.1.3.9 Distribution.37 3.1.4 Approval of User Modifiable Software37 3.2 Us
30、er Certified Software.37 3.2.1 UCS Specific Processes.38 3.2.2 Certification of UCS38 4.0 SOFTWARE ACQUISITION AND RECEIVING40 4.1 General40 4.2 Aircraft Acquisition.40 4.3 Target Hardware Acquisition.40 4.3.1 Authorization.40 4.3.2 Tie-on-Tags41 4.4 Physical Media or Electronic Software Acquisition
31、42 ARINC REPORT 667 TABLE OF CONTENTS v 4.4.1 Software Documentation42 4.4.2 Documentation from Suppliers.42 4.4.3 Authorized Sources43 4.5 Responsibilities for Receiving43 4.5.1 Receiving Inspection of Physical Media or Electronic Crate.43 4.5.1.1 Designating a Master Image44 4.5.1.2 Software Stora
32、ge Considerations45 4.5.1.3 Quality Management45 5.0 SOFTWARE DUPLICATION AND DISTRIBUTION46 5.1 General46 5.2 Distribution Methods46 5.2.1 Physical Media Distribution.47 5.2.1.1 Floppy Disks.47 5.2.1.2 High-Density Software Media Sets47 5.2.2 Electronic Distribution.47 5.3 Aircraft Controlled Softw
33、are Distribution48 5.4 Software Control Library Concept.48 5.5 Media Packaging and Handling.49 5.5.1 Labeling49 5.5.2 Storage and Handling.49 5.5.3 Transportation of Media49 5.6 ACS Duplication50 5.6.1 Rights to Copy50 5.6.1.1 Airline Responsibilities.50 5.6.1.2 Airframe Manufacturer Responsibilitie
34、s.51 5.6.1.3 Responsibilities of Other Parties51 5.6.1.4 Designee Responsibilities51 5.6.2 Copyright51 5.6.3 Duplication Process and Tools.51 5.6.3.1 Use of Designated Master Source Parts51 5.6.4 Quality Assurance Program52 5.6.5 Integrity.52 5.6.6 Virus Considerations.52 6.0 SOFTWARE STORAGE53 6.1
35、General53 6.2 On-Aircraft Storage53 6.2.1 Onboard Mass Storage Device.53 6.3 Off-Aircraft Storage54 6.3.1 Ground-Based File Server54 6.3.2 LSP Storage Vault54 6.3.3 Shop Loader MSD55 6.3.4 Portable Loader MSDs.55 6.3.5 Media Storage55 6.4 Binder/Storage Box.55 7.0 AIRCRAFT CONFIGURATION MANAGEMENT O
36、F LSAP56 7.1 General56 7.1.1 Configuration Management Vocabulary.57 7.1.2 Software Relationship to Target Hardware and Aircraft.62 7.1.3 Software Installation Locations.64 7.2 Configuration Accountability64 ARINC REPORT 667 TABLE OF CONTENTS vi 7.2.1 Configuration Authorities CCA and ACA.64 7.2.2 Ai
37、rcraft Life Cycle Accountability65 7.3 Airline Configuration Management Process and System Overview66 7.3.1 Change Management and Approval.66 7.3.2 Installation and Verification.67 7.3.3 EDMS Concepts and Capabilities.67 7.4 Certified Configuration Authority68 7.5 Airline Configuration Authority.69
38、7.5.1 Configuration Data69 7.5.2 Configuration Identification.70 7.5.3 Configuration Change Management.70 7.5.4 Configuration State Management.71 7.5.4.1 Work Flow State Management.71 7.5.4.2 Authorization State Management.72 7.5.4.3 State Management During Change Processing.72 7.5.4.4 State Managem
39、ent During LRU Replacement.74 7.6 Configuration Control Processes.74 7.6.1 Standard Configuration Control Processes74 7.6.2 Rapid Configuration Control Processes74 7.7 Configuration Verification75 7.7.1 Installation Verification75 7.7.2 Aircraft-Level Verification76 7.7.3 Automated Verification76 7.
40、7.4 Verification During Hardware Replacement78 7.7.5 Verification of Pre-Loaded Software.79 7.7.6 Verification of Off-Aircraft-Loaded Software.79 7.8 Configuration Records Retention79 8.0 ACS LOADING METHODS.80 8.1 ACS Loading Philosophy.80 8.2 Loading Resources80 8.3 Software Load Status Informatio
41、n.81 8.4 Software Loading Procedure References81 8.4.1 General Loading Procedure82 8.4.2 Additional Loading Considerations.82 8.5 Hardware Pre-load82 8.6 Software Part Number Verification83 8.7 Software Installation Approval.83 8.8 Onboard Software Load Time.83 8.8.1 Definition of Onboard Software I
42、nstallation and Load Time.84 8.8.1.1 Setup85 8.8.1.2 User Initiation Start85 8.8.1.3 File Transfer.86 8.8.1.4 Integrity Check.86 8.8.1.5 Load Completion86 8.8.2 Verification Configuration display86 8.8.3 End of Task.87 8.8.3.1 Return to Service.87 8.9 Off-aircraft Software Loading.87 9.0 BORROWED AV
43、IONICS AND ASSOCIATED SOFTWARE.88 9.1 General88 ARINC REPORT 667 TABLE OF CONTENTS vii 9.2 Responsibilities of Airlines and Third Party Service Providers88 9.3 Borrowing Avionics Software.88 9.4 Contingency (Get You Home) Maintenance88 APPENDICIES APPENDIX A GLOSSARY.90 APPENDIX B ACRONYM LIST.99 AR
44、INC REPORT 667 Page 1 1.0 INTRODUCTION 1.0 INTRODUCTION 1.1 Purpose and Goal The purpose of this document is to provide guidance for the in-service management of Loadable Airborne Software. The types of Airborne Software are defined in Chapter 2. This document is intended to be broad and apply to al
45、l Aircraft Controlled Software (ACS). The key features of aircraft controlled software are as follows: a. Usually capable of software load on-aircraft. Also covers hardware controlled software to some extent. b. Part number is electronically verifiable on-aircraft. c. Does not change target hardware
46、 part number. d. The software has its own unique identification number. e. The software part may be a type-certified aircraft part. f. The software may be an application. g. The software may be a database. h. The software may be a document or list. COMMENTARY The terminology of ARINC Report 615A and
47、 ARINC Report 665 has been applied to this document in the interest of consistency. However, this document has a broader scope and therefore does not follow the existing terminology in all cases. Appendix A provides a glossary of terms. Target hardware refers to the unit or system that is intended t
48、o host the software. The terms Line Replaceable Unit (LRU) and Line Replaceable Module (LRM) are used sparingly in this document, as they are all considered target hardware. ACS target hardware may be certified on multiple fleet types, or it may be certified in different configurations within the sa
49、me fleet type as long as the correct software part is installed. This document is intended to be as inclusive as possible and does not exclude any software from the configuration control guidance contained herein. Rather, it is intended to encourage all future loadable software implementations to support these guidelines. 1.2 Vision The following sections describe the vision, scope, and background leading the preparation of this document. As a basic premise, airlines desire processes and guidelines that will assure that the correct ACS is loaded into the target hardware on e
