AIRLINE COMMENTS LOAD PROCESS

FROM AIRN@V SUPPORT TEAM DATE 08 Dec 2013

PAGE 1

SUBJECT: A380 AirN@v Airline comments load generation

ATA CHAPTER: 45-20

AIRCRAFT TYPE: A380

APPLICABILITY: All A380 Aircraft

REFERENCES: AMM 45-20-00-616-801-A

PURPOSE
This SIL intends to describe how to generate Airline comment loads.
The Airline Comments load process is divided into 3 parts:
- Creating the Airline Comments package
- Preparing the on-board specific files
- Creating and signing the load using LSBM
Please refer to the AMM task 45-20-00-616-801-A - Uploading of Software to Equipment - to
upload the airline comments on board.

1. CREATING THE AIRLINE COMMENTS PACKAGE

There are but a few constraints with the way an Airline Comments package is built:
- The on-board platform accepts only PDF format as files for the Airline Comments
package
- There are no limitations as to how many PDF files are in the Airline Comments
package
- The Airline Comments package can have any name
- The Airline Comments package must respect a specific structure for it to attach
correctly on an on-board platforms

We strongly advise you to test your Airline Comments package on-ground before going
further on parts 2 and 3 on this load process. This will prevent potential errors while loading
the signed package on-board.

1.1 EXPORTING AIRLINE COMMENTS PACKAGE

The easiest solution to get an Airline Comments package for on-board is to use the export
attachments feature provided by ADOC N@vigator.
This export attachments feature:
- Retrieves your airline comments documents: all your PDF files are zipped
- Retrieves the associated anchoring locations: every association between the actual
files and their locations within the documentation are picked up by the feature
- Creates an anchoring file: the result of the above association is saved into a file
- Creates a single zip file, much like an Airbus TR, that can be used for the next parts
of this load process

On an on-ground ADOC N@vigator server:

- Connect to the AirN@v Administrator Panel using the Administrator profile. Use the
password *awn- (star, a, w, n, dash)
- Select “Attachment Management” > “Zip attachments” in the Administration panel
- Select the source database, usually A380%20100X01%<CUS>%AirN@v
Maintenance and click “Export Attachments”
© AIRBUS FRANCE S.A.S. 2008. All rights reserved. Confidential and proprietary document. This document and all information contained herein
is the sole property of AIRBUS FRANCE S.A.S. No intellectual property rights are granted by the delivery of this document or the disclosure of its
content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS FRANCE S.A.S. This
document and its content shall not be used for any purpose other than that for which it is supplied.
 AIRLINE COMMENTS LOAD PROCESS
FROM AIRN@V SUPPORT TEAM DATE 08 Dec 2013
PAGE 2

- Save the generated zip anywhere on your computer

Rename the zip file into a more suitable name such as <CUS_AirlineComments>.zip
This naming will be used for the next parts of the load process.

Note: For A380 program, due to an issue between onboard and on-ground environment, the
zip file created (chapter 1.1) has to be edited and modified to be compatible with AirN@v
onboard. All the modifications needed are described in the FAQ #AIRNAV-3685

This limitation will be corrected in a future version of AirN@v on-ground.

1.2 TESTING THE AIRLINE COMMENTS PACKAGE

On an on-ground ADOC N@vigator server:

- Connect to the AirN@v Administrator Panel using the Administrator profile. Use the
password *awn- (star, a, w, n, dash)
- Select “Attachment Management” > “Attach documents” in the Administration panel
- Browse for the <CUS_AirlineComments>.zip file and click OK
- In the next screen, select the database on which you have to attach the Airline
Comments zip file and click Add
- Check in the next screen that all attachments were anchoring successfully by looking
at the “Action” column for “Success: Add anchor”

It is advised then to open an AirN@v session and check that all attached documents are
successfully anchored in the correct sections of the manuals that you specified on the
anchoring file. To do this, AirN@v is accessible directly from administration console by using
“Data browsing” button. When the verification is finished you are able to return to the
administration console by using the menu “System > Quit And Open Admin …”

2. PREPARING THE ON-BOARD SPECIFIC FILES

On an on-board configuration, the Airline Comments zip file is not enough for the attachment
to work and some files, compliant with ARINC 665 requirements, are necessary. These files
are accessible on the DVD under …\On-Board\A380

2.1 LIST OF ADDITIONAL FILES

Here below are the details of the delivered files:

- airnav-updates.tar.gz: this file includes the XML description file, giving the target
LRU(s) for the Part Number, and the functional designation of the FIN software
corresponding to the final Part Number. Both targeted LRUs and functional
designation are managed by Airbus, included into the DLCS mapping table, the AIR
and the IPC. Included also are the silent installation files for the installation on both
pEIS2a and pEIS2b configurations.
This file is mandatory and does not need to be modified
- PartNumber.sh: the silent installation file, this file references a 15-character Part
Number for which <CUS> will have the responsibility of defining and managing. This
file is mandatory and needs to be modified by <CUS>

2.2 PART NUMBER CONFIGURATION

Once <CUS> has defined a 15-character Part Number for the load, they shall use it in the
PartNumber.sh file

© AIRBUS FRANCE S.A.S. 2008. All rights reserved. Confidential and proprietary document. This document and all information contained herein
is the sole property of AIRBUS FRANCE S.A.S. No intellectual property rights are granted by the delivery of this document or the disclosure of its
content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS FRANCE S.A.S. This
document and its content shall not be used for any purpose other than that for which it is supplied.
 AIRLINE COMMENTS LOAD PROCESS
FROM AIRN@V SUPPORT TEAM DATE 08 Dec 2013
PAGE 3

For our load process, let’s call this Part Number <CUS_Part_Number>:
- Start by renaming the PartNumber.sh file by <CUS_Part_Number>.sh
- Open the newly renamed .sh file with a text editor such as Notepad++ or WordPad
- In the opened file, replace all occurrences of PartNumber.sh by
<CUS_Part_Number>.sh
With Notepad ++, you should find two occurrences of this text string on lines 109 and 152
- Save the <CUS_Part_Number>.sh file

3. CREATING AND SIGNING THE LOAD USING LSBM

Before starting LSBM, check that you have three (3) files as your input:
- airnav-updates.tar.gz
- <CUS_Part_Number>.sh, modified accordingly
- <CUS_AirlineComments>.zip, the zip package created and tested on 1.

Start LSBM, usually found under Start > Programs > Airbus > LSBM vXX > LSBM vXX

3.1 CREATING THE LOAD

To create a load using LSBM:

- In the bottom-left side, click “Build“ tab.
- In the left navigation pane, click “Build Load“
- Select the input directory where you stored your 3 files (see 3. above)
- In the “Load P/N” field enter the Part Number you defined in 2.2. Make sure that the
CRC checks out and click the exclamation mark in the yellow triangle to autocorrect
the Part Number. If the management of Part Numbers is done properly, you should
never to click the triangle
- In the Target HwID field, click the “...” button and select SFI_ANSU-OPS
- Select a different output folder for the creation of the .LUH file or let the LSBM create
it in the same folder as your input files (recommended)
- Finally, click Build in the bottom-right part of the screen to build the load

For more information concerning the fields, use the Online Help

3.2 SIGNING THE LOAD

Signing on-board loads must be done in High Trust Dual Mode.

You also need a SmartCard reader along with its PIN code and certificate.

To enable the High Trust Dual Mode signing mode in LSBM:

- Click “Tools” > “Options” in the top menu
- Select “Security” tab
- Select “Dual mode (Basic Trust PKI phase 1 + High Trust PKI phase 2)” in the
Signature phase list. Leave the other options as-is.
- If you have changed the “Signature phase” field, click “Update” button to save the
new configuration. LSBM will be restarted.

Afterwards, for the load signing:

- Click “Secure Load or File” in the left navigation panel
- In the “Load list” section of the right-hand side screen, click the yellow folder icon and
select the generated .LUH file from 3.1
- Enter the SmartCard PIN code
- Refresh the SmartCard status to account for the certificate
- Click “Build” to secure the load

© AIRBUS FRANCE S.A.S. 2008. All rights reserved. Confidential and proprietary document. This document and all information contained herein
is the sole property of AIRBUS FRANCE S.A.S. No intellectual property rights are granted by the delivery of this document or the disclosure of its
content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS FRANCE S.A.S. This
document and its content shall not be used for any purpose other than that for which it is supplied.
 AIRLINE COMMENTS LOAD PROCESS
FROM AIRN@V SUPPORT TEAM DATE 08 Dec 2013
PAGE 4

Once built, the load directory contents should look like:

Make sure to check for the two .LSH files generated by LSBM.

3.3 CREATING THE MEDIA

Once the load has been secured:
- Click “Build Media Set” in the left navigation panel
- In the “Media P/N” field enter a Part Number for the media. Make sure that the CRC
checks out and click the exclamation mark in the yellow triangle to autocorrect the
media Part Number
- Select the output directory where the media will be created
- In the “Load list” section of the right-hand side screen, click the yellow folder icon and
select the generated .LUH file from 3.1
- Finally, click Build in the bottom-right part of the screen to build the media

Note that it is possible to create the media before the load signing.

Check the structure of the output directory. It should include as follows:

- Files: an empty directory
- <CUS_Part_Number>: the directory for the load created and signed in 3.1 and 3.2
- FILES.LUM and LOADS.LUM: files created by LSBM in 3.3

From the media folder structure, create a CD to load the Airline Comments load in an
onboard environment.

© AIRBUS FRANCE S.A.S. 2008. All rights reserved. Confidential and proprietary document. This document and all information contained herein
is the sole property of AIRBUS FRANCE S.A.S. No intellectual property rights are granted by the delivery of this document or the disclosure of its
content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS FRANCE S.A.S. This
document and its content shall not be used for any purpose other than that for which it is supplied.