LEVEL III - AIRBUS Maintenance Philosophy

A380
TECHNICAL TRAINING MANUAL

MAINTENANCE COURSE - T1 & T2 (RR / Metric)
LEVEL III - AIRBUS Maintenance Philosophy
This document must be used for training purposes only
Under no circumstances should this document be used as a reference
It will not be updated.
All rights reserved

No part of this manual may be reproduced in any form,
by photostat, microfilm, retrieval system, or any other means,
without the prior written permission of AIRBUS S.A.S.
A380 TECHNICAL TRAINING MANUAL
LEVEL III - AIRBUS MAINTENANCE PHILOSOPHY

E-Logbook Description (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
AIRMAN General Description (3) . . . . . . . . . . . . . . . . . . . . . . . . . . .14
AIRBUS Documentation-Trouble Shooting
Documentation-Trouble Shooting (3) . . . . . . . . . . . . . . . . . . . . . . . .38
L1W06161 - L0KT0T0
MAINTENANCE COURSE - T1 & T2 (RR / Metric) TABLE OF CONTENTS Apr 21, 2006
LEVEL III - AIRBUS Maintenance Philosophy Page 1
E-LOGBOOK DESCRIPTION (3)

e-Logbook Functions
The Electronic Logbook is an onboard application, which will replace
paper aircraft Logbook but offering much more possibilities thanks to
digital links with the A/C systems, ground database and digital
documentation, plus customization and computation capability.
The Electronic Logbook supports the following aircraft oriented processes:
- Flight data reporting such as Pre-flight and post-flight reports
- Defect reporting by the maintenance, cabin and flight crew.
- Maintenance action reporting
- Servicing actions reporting
- Aircraft Maintenance release report.
- Check aircraft status
- consult any data logged in the past (History report)
- follow-up of deferred maintenance actions
A standard electronic reporting gives more clarity and consistency plus
automatic links such as to OMS data and MEL/CDL documentation.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
MAINTENANCE COURSE - T1 & T2 (RR / Metric) E-LOGBOOK DESCRIPTION (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
E-LOGBOOK FUNCTIONS

e-Logbook Profiles
There are mainly three user's profiles to access the e-logbook to read and
write reports:
- flight crew profile, to get access to the technical logbook,
- cabin crew profile, to get access to the digital cabin logbook,
- maintenance profile, to get access to the maintenance logbook. On-board
or on-ground maintenance will log in under this profile.
All three user's profiles share a common database, which is synchronized
with AIRMAN database on ground. Inside the AIRMAN database, there
is a part dedicated to logbook data. AIRMAN is used as a ground tool
and is the legal repository of Logbook data.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
E-LOGBOOK PROFILES

e-Logbook Architecture
The Technical and Maintenance Logbook applications run in the cockpit
terminals (OITs and OMT) and will exchange data with the server
(ANSU-OPS1&2).
The Digital Cabin Logbook application runs in the server (ANSU-OPS
1&2). FAP is the cabin logbook interface.
Pilot, cabin and on-board maintenance can simultaneously write in the
e-logbook database, which is included into the OMS shared database.
All profiles have a complete access to the e-Logbook database, except
for Digital Cabin Logbook, which has a limited access. Thus, the Private
Logbook Views database includes only cabin items and all cabin-visible
logbook entries. All DCL data is stored in the Digital Cabin Logbook
Private Database.
Logbook defects data is sent to the CMS.
Technical and Maintenance Logbooks retrieve data from the different
OMS applications through their databases.
From the CMS the following information is retrieved:
- information about the tests done for a Logbook entry
- information about a documentation access done for a Logbook entry
- the Flight Deck and Cabin Effects (FDCE) displayed during the flight
- and information about the flights.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
P/N and FIN data for dataloading of logbook items are retrieved from
the DLCS.
MEL dispatch conditions are retrieved from the MEL.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
E-LOGBOOK ARCHITECTURE

Ground maintenance cannot trigger information upload, from AIRMAN
e-Logbook Data Exchange and Synchronization database to e-Logbook database. Once ground maintenance ends the
updates and changes under the Logbook data of AIRMAN database,
Data exchange between e-Logbook and AIRMAN databases is done to
should release control, thus pilots, cabin crew or on-board maintenance
update the eldest database with the differences added to the last updated
will be able to upload modifications into e-Logbook database by triggering
database. This communication process is done manually or automatically
synchronization. At any moment on-board profiles can get the latest
depending on the type of exchanged information.
updates by clicking on "Synchro ground" or "Data Synchronization" icon,
During flight, e-Logbook control is always on-board. Pilots and cabin
this action will upload the latest information without retrieving control
crew can enter and validate defects. Pilot or cabin profiles can trigger a
from ground maintenance.
manual download of information, that means send data to AIRMAN
When the maintenance release is done by on-ground maintenance through
database, by clicking on "Synchro ground" icon.
AIRMAN, on-ground maintenance is asked if they want to keep or release
If pilots find a defect after closing the flight or before aircraft acceptance,
e-logbook control. Maintenance Release data exchange from AIRMAN
they can enter, validate and finally send it to AIRMAN database by
database to e-logbook database waits until synchronization is triggered
clicking on "Synchro ground" icon. E-Logbook control should previously
by any on-board profile.
be on-board.
Meanwhile control is on-board; on-ground maintenance through AIRMAN
On-board maintenance can manually transfer the maintenance actions
cannot enter, validate or modify any operational entry. They can only
report by clicking on "Data Synchronization" icon via OMS. E-Logbook
visualize them. For example, if ground maintenance needs to enter new
control should previously be on-board.
work orders after control being lost, it must contact onboard maintenance
An automatic sending of the last updates brought on the e-logbook
(using VHF or GSM for instance) and ask them to release control. For
database is triggered on the A/C in case of opening/closing flight and
this, on-board maintenance will release control of the A/C by quitting
when the maintenance release is done on-board.
e-Logbook and CMS.
Close Flight data contain post flight parameters, validated defects not
sent during flight and the pilot's signature. When pilot closes the flight,
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
he is asked if he wants to release or keep control.

On-board maintenance will validate and sign the maintenance release
report, which contains certificate status, flight data, employee
ID/signature, maintenance entries and list of maintenance actions. After
sending it, on-board maintenance can keep or release e-logbook control.
After on-board maintenance closes the e-Logbook and CMS applications,
e-logbook control is automatically released.
Opening Flight data contain acceptance, pre-flight data and pilot's
signature. Then an acknowledgement is sent from ground database to the
A/C, indicating that ground maintenance did receive the A/C acceptance
sent by the pilot.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
E-LOGBOOK DATA EXCHANGE AND SYNCHRONIZATION
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
L1W06161 - L0KT0T0 - LM00D1LEVEL0301

e-Logbook Customization
The maintenance administrator profile is defined to let the airline
configure and customize the application, and manage the database to
match airline needs. All functions are available for these users, that means,
ability to read and write reports, customization, create and delete users
etc....
Maintenance administrator profile can customize e-Logbook through
AIRMAN on-ground without having control on e-Logbook. This
customization is uploaded into the aircraft or complete fleet at next
synchronization.
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
L1W06161 - L0KT0T0 - LM00D1LEVEL0301
E-LOGBOOK CUSTOMIZATION
AIRMAN GENERAL DESCRIPTION (3)

What is AIRMAN
AIRMAN is a ground-based software dedicated to optimize the
maintenance of AIRBUS fly-by-wire aircraft composed of:
On Board Maintenance System (OMS)
Real-Time Communication System
AIRMAN is also used for the identification and management of
unscheduled and scheduled maintenance events.
AIRMAN's data analysis, synthesis and presentation has the following
benefits:
Simpler, more effective troubleshooting
Preventive maintenance recommendations
More effective engineering support.
These benefits can be used by the airlines to:
Improve aircraft Dispatch Reliability
Reduce operational costs
Reduce maintenance costs.
AIRMAN will be delivered as a basic feature with the A380.
L1W06161 - L0KT0T0 - LM00D3AIRMAN001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) AIRMAN GENERAL DESCRIPTION (3) Apr 18, 2006
WHAT IS AIRMAN

Functional Overview
AIRMAN is a ground-based software dedicated to the identification and
the management of unscheduled maintenance.
AIRMAN receives and analyses the aircraft status information generated
by the Onboard Maintenance System (OMS) and also e-logbook data.
The information is automatically transmitted to the ground by the aircraft's
communication system.
These information sources are synthesized, combined with Airbus's and
the Airline's own technical documentation and presented through a
user-friendly interface. Aircraft status information is sent to AIRMAN
while the aircraft is both in flight and on ground. Message analysis also
takes place in real-time.
These capabilities maximize the time available for appropriate
maintenance actions to be determined and preparations to be made.
AIRMAN is capable of analyzing an aircraft's fault history and
consequently identifying and prioritizing preventive maintenance actions.
FUNCTIONAL OVERVIEW

Maintenance Philosophy
The aircraft maintenance philosophy is based on the following steps:
fault detection made by the computers BITEs
cockpit effects as flags on Display Units, and warning generated by the
Flight Warning System (FWS)
centralization and correlation by the Onboard Maintenance System
(OMS) of BITE faults, cockpit effects and related maintenance procedures
generation of Post Flight Report (PFR)
fault event data reporting through the e-logbook
fault event data and reports transmission to AIRMAN for maintenance
support on ground
MAINTENANCE PHILOSOPHY

AIRMAN Data Sources
AIRMAN Links
AIRMAN maintenance analysis is based on the following received
data:
Aircraft data
Airbus data
Airline data
Aircraft data:
cockpit and cabin effects
fault messages
logbook entries
operational reports (CFR, PFR, ACMS Reports)
Airbus data is made of an aircraft knowledge database build up with
the airline worldwide feedback and aircraft documentation:
TFUs
SILs
MMEL/MEL
AirN@V
Airlines data can be:
technical entries (related to A/C events)
work orders
AIRMAN DATA SOURCES - AIRMAN LINKS

o Load report
AIRMAN Data Sources (continued) Note that AIRMAN centralizes the aircraft data of the entire Airline
fleet.
Downlink Data
AIRMAN operation is based on the centralization of aircraft
operational and maintenance data.
Operational data sent by the aircraft are:
- the OOOI (OUT/OFF/ON/IN):
o OUT: "Out of gate"
o OFF: "Lift off"
o ON: "On ground"
o IN: "In gate"
- particular events:
o touch and go
o return to gate
- flight data:
o flight identifiers
o departure time and airport
o destination time and airport
- current fuel onboard
- departure delay
- estimated time arrival
Maintenance data sent by the aircraft are:

- fault messages
- cockpit effects
o warnings/cautions
o flags/advisories
- cabin effects
sent in fault codes, and:
- Current Flight Report (CFR)/Post Flight Report (PFR)
- Logbook entries (in fault code if standardized)
- Aircraft Condition Monitoring System (ACMS) reports:
o Auxiliary Power Unit (APU) report
o Environmental Control System (ECS) report
AIRMAN DATA SOURCES - DOWNLINK DATA

AIRMAN Data Sources (continued)
Airline Data
Some Airline's data is also implemented in the AIRMAN database.
This Airline's data are:
- maintenance actions reporting
- work orders
- technical entries
- the MEL
- engineering data
- administration data
AIRMAN DATA SOURCES - AIRLINE DATA

AIRMAN Data Sources (continued)
Airbus Data
The third data source used by AIRMAN to make the maintenance
easier is Airbus data. Airbus data is made of an aircraft knowledge
database build up with the airline worldwide feedback and aircraft
documentation:
- TFUs
- SILs
- MEL
- AirN@V
This data are implemented in the AIRMAN database and correlated
to a unique fault event. They can be accessed directly from the "Defect
Advisor".
AIRMAN DATA SOURCES - AIRBUS DATA

AIRMAN Functions
The AIRMAN tool covers three principle areas of activity within the
airline:
- gate maintenance (fault identification and management),
- hangar maintenance (preventive maintenance identification and
prioritization),
- engineering services (line and hangar maintenance support).
AIRMAN FUNCTIONS

AIRMAN Functions (continued)
AIRMAN Gate Function
Whether the aircraft is at the gate, on the runway or in-flight,
AIRMAN gives the user direct access to:
- An overview of the fleet's operational and technical status
- On-board Maintenance System (OMS) information automatically
transmitted in real-time from the aircraft
- Technical documents from both AIRBUS and the airline
- e-Logbook data transmitted from the aircraft
- Work orders and logbook entries transmitted to the aircraft from
AIRMAN
- Dedicated maintenance action assistants to let the user enter the
detailed maintenance actions and manage the A/C parts
AIRMAN gives a centralized synthesis of all available information
related to any aircraft event including previous occurrences of that
event. Analysis of the fault will automatically identify the most
appropriate trouble shooting procedure. This analysis makes sure that
the correct maintenance action is taken within the minimum delay.
AIRMAN FUNCTIONS - AIRMAN GATE FUNCTION

AIRMAN Hangar Function
In-depth analysis of aircraft event using the aircraft and fleet history
will rectify a fault before it becomes visible to the pilot. In this way
pilot defect reports and potential delays can be avoided.
Using algorithms based on statistical analysis, AIRMAN checks all
OMS reports to identify systems that are most likely to fail and would
cause a pilot report and eventually a technical delay. The results of
this analysis are shown in AIRMAN Job List.
In order to focus on the most important problems, each job can be
assigned with a priority level.
Maintenance Work Orders management and scheduling can also be
done through AIRMAN to prepare and optimize the scheduled
maintenance.
AIRMAN FUNCTIONS - AIRMAN HANGAR FUNCTION

AIRMAN Engineering Function
AIRMAN is used for detailed investigations of un-scheduled
maintenance issues.
For complex troubleshooting, users can access reports that list all
recorded occurrences of a specific fault. These lists give rapid access
to all the information stored during the flights where the specified
fault occurred.
AIRMAN automatically gives a highly consistent report function that
lets users monitor the:
- evolution of fleet technical status in terms of outstanding maintenance
actions,
- fault occurrence rates for any or all systems on any or all aircraft.
Moreover the Engineering through technical entries can support
maintenance actions by giving specific information like technical
notes.
An automatic creation of Reports gives statistics, ratios and trends
available through tables.
AIRMAN FUNCTIONS - AIRMAN ENGINEERING FUNCTION

AIRMAN Synchronization with the Ground
So synchronization is necessary to update these databases each time a
new logbook entry or a work order is issued for the aircraft..
Synchronizations are only made when the aircraft is on ground. A
synchronization can be done:
- before opening the flight
- at the end of the flight
- during maintenance operations
- automatically at the maintenance release
Note that AIRMAN database also receives data when the aircraft is in
flight (operational and fault events).
AIRMAN SYNCHRONIZATION WITH THE GROUND
DOCUMENTATION-TROUBLE SHOOTING (3)

General
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
MAINTENANCE COURSE - T1 & T2 (RR / Metric) DOCUMENTATION-TROUBLE SHOOTING (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
GENERAL

Trouble Shooting Philosophy
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING PHILOSOPHY

Trouble Shooting Philosophy (continued)
PFR Messages
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING PHILOSOPHY - PFR MESSAGES

Trouble Shooting Philosophy (continued)
Trouble Shooting Access
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING PHILOSOPHY - TROUBLE SHOOTING ACCESS

Trouble Shooting Functions
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING FUNCTIONS

Trouble Shooting Functions (continued)
Navigation
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING FUNCTIONS - NAVIGATION
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING FUNCTIONS - NAVIGATION
This Page Intentionally Left Blank

L1W06161 - L0KT0T0 - LM00O1LEVEL0301

Trouble Shooting Manual (TSM)
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
L1W06161 - L0KT0T0 - LM00O1LEVEL0301
TROUBLE SHOOTING MANUAL (TSM)
AIRBUS S.A.S.
31707 BLAGNAC cedex, FRANCE
STM
REFERENCE L1W06161
APRIL 2006
PRINTED IN FRANCE
AIRBUS S.A.S. 2006
ALL RIGHTS RESERVED
AN EADS JOINT COMPANY

WITH BAE SYSTEMS

LEVEL III - AIRBUS Maintenance Philosophy

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LEVEL III - AIRBUS Maintenance Philosophy

Hochgeladen von

Copyright:

Verfügbare Formate

A380

TECHNICAL TRAINING MANUAL

Under no circumstances should this document be used as a reference

It will not be updated.

All rights reserved

LEVEL III - AIRBUS MAINTENANCE PHILOSOPHY

E-LOGBOOK DESCRIPTION (3)

E-LOGBOOK DESCRIPTION (3)

E-LOGBOOK DESCRIPTION (3)

E-LOGBOOK DESCRIPTION (3)

he is asked if he wants to release or keep control.

E-LOGBOOK DATA EXCHANGE AND SYNCHRONIZATION

E-LOGBOOK DATA EXCHANGE AND SYNCHRONIZATION

E-LOGBOOK DATA EXCHANGE AND SYNCHRONIZATION

E-LOGBOOK DESCRIPTION (3)

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN DATA SOURCES - AIRMAN LINKS

AIRMAN GENERAL DESCRIPTION (3)

Maintenance data sent by the aircraft are:

AIRMAN DATA SOURCES - DOWNLINK DATA

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN DATA SOURCES - AIRLINE DATA

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN DATA SOURCES - AIRBUS DATA

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN FUNCTIONS - AIRMAN GATE FUNCTION

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN FUNCTIONS - AIRMAN HANGAR FUNCTION

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN FUNCTIONS - AIRMAN ENGINEERING FUNCTION

AIRMAN GENERAL DESCRIPTION (3)

AIRMAN SYNCHRONIZATION WITH THE GROUND

DOCUMENTATION-TROUBLE SHOOTING (3)

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING PHILOSOPHY

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING PHILOSOPHY - PFR MESSAGES

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING PHILOSOPHY - TROUBLE SHOOTING ACCESS

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING FUNCTIONS

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING FUNCTIONS - NAVIGATION

TROUBLE SHOOTING FUNCTIONS - NAVIGATION

This Page Intentionally Left Blank

DOCUMENTATION-TROUBLE SHOOTING (3)

TROUBLE SHOOTING MANUAL (TSM)

AN EADS JOINT COMPANY

Das könnte Ihnen auch gefallen