AIRLINE COMMENTS LOAD PROCESS

FROM AIRN@V SUPPORT TEAM DATE 20 Nov 2012

PAGE 1

SUBJECT: A330/A340 AirN@v Airline comments load generation

ATA CHAPTER: 45-20

AIRCRAFT TYPE: A330/A340

APPLICABILITY: All A330/A340 Aircraft

REFERENCES: -

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

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 A330%2012XX01%<CUS>%AirN@v
Maintenance and click “Export Attachments”
- 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.
© 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 20 Nov 2012
PAGE 2

Note: Due to some discrepancies between the version of ADOC N@vigator used to create
the export package and the version of ADOC N@vigator available onboard, please note that
some modifications will have to be performed on the automatically generated
AirlineComments package:
- Extract the zip file
- Open the sgml file(s) with a text editor and replace all the pathes from
o <OBJECT FORMAT="application/pdf" PATH=".\AMM_AD\n" TITLE="">
to
o <OBJECT FORMAT="application/pdf" PATH=".\AMM_AD\n.pdf" TITLE="">
- Save your modifications
- Rename all pdf files available from n to n.pdf
- Zip your package in order to have the .sgml file(s) at the root of the zip file. In order to
generate the zip file, a tool like 7zip is recommended.

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.

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.
The structure of the load is the following:
Root
CUS_Part_Number.bat
CUS_Part_Number.LUH
CUS_Part_Number_<DATE>_<B>.LSH
airnav-updatessac.tar.gz
data.zip
tool.jar
airnav-updatesac-COLANSU.xml
build.xml
info-load.xml
makeAttachment.xml

2.1 LIST OF ADDITIONAL FILES

Here below are the details of the delivered files:

- install.bat: 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

© 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 20 Nov 2012
PAGE 3

- airnav-updatesac-COLANSU.xml : this file will contain the Functional Designation

of the load as well as the Functional Designation of the targeted hardware. It needs
to be modified by CUS.
- build.xml: Do not need to be modified by CUS
- info-load.xml: Do not need to be modified by CUS
- makeAttachment.xml: Do not need to be modified by CUS.
- tools.jar: Do no need 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
install.bat file.
For our load process, let’s call this Part Number CUS_Part_Number:
- Start by renaming the “install.bat” file as “CUS_Part_Number.bat”
- Open the file “airnav-updatesac-COLANSU.xml” file with a text editor such as
Notepad or Wordpad.
- Replace the occurrence of “%pn%” in airnav-updatesac-COLANSU.xml by
CUS_Part_Number.

2.3 LOAD FINALIZATION

In order to have a complete load, please follow the procedure below:

- Copy the <CUS>_AirlineComments.zip file created earlier in the same folder as the
tool.jar file, archive both file in a file named airnav-updatesac.tar
- Compress the airnav-updatesac.tar into airnav-updatesac.tar.gz

3. CREATING AND SIGNING THE LOAD USING LSBM

Before starting LSBM, check that you have six (6) files as your input:
- airnav-updatesac.tar.gz, containing the data.zip and tool.jar
- airnav-updatesac-COLANSU.xml
- CUS_Part_Number.bat, modified accordingly
- makeAttachment.xml
- info-load.xml
- build.xml

Start LSBM, usually found under Start > Programs > Airbus > LSBM v3.0a > LSBM v3.0a.

3.1 CREATING THE LOAD

To create a load using LSBM, please:

- In the bottom-left side, click “Build“
- In the left navigation pane, click “Build Load“
- Select the input directory where you stored your 6 files (see 3. above)
- 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 COLANSU

© 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 20 Nov 2012
PAGE 4

- 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

As a reference, please find below screenshots of the load creation procedure:

3.2 SIGNING THE LOAD

Once the load has been created, please:

- Click “Secure Load or File” in the left navigation pane
- 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
- Select your P12/PFX in order to sign the load and enter its password in the field
below
- 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 20 Nov 2012
PAGE 5

As a reference, please find below screenshots of the secure load procedure:

3.3 CREATING THE MEDIA

Once the load has been secured, please:

- Click “Build Media Set” in the left navigation pane
- 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

As a reference, please find below screenshots of the media creation procedure:

© 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 20 Nov 2012
PAGE 6

Check the structure of the ouput directory. It should look like 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

© 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 20 Nov 2012
PAGE 7

From the media folder structure, create a CD to load the Airline Comments load in an on-
board 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.