In Service Information

Ref: ISI 45.00.00001

Issue: April 2015

A380 family
maintenance
concept

1 Cockpit effects Local warning on

the overhead panel Dispatch guidelines and troubleshooting process (Map of the Poster) Proactive and preventive maintenance REPORTS TRANSMITTED
TO THE GROUND
EFIS
Control Panel
CAPTAIN FIRST OFFICER
(Symmetrical side) _ _
Proactive maintenance PFR contains all correlated fault
Master warning 1 Cockpit effects Definition: The proactive maintenance allows to treat failures in real time before the landing of the A/C. messages (all types).
& caution lights Determine Safety and OPS impact Objectives: The maintenance team on ground can anticipate troubleshooting operations before the next dispatch by analyzing
CFR transmitted to AIRMAN WEB. CFR contains new FWS alarms
ND (Use ECAM warning as entry point into the MEL)
PFD The eLogbook can also be used to send pilot reports (PiRep) in real-time to the MCC, so the maintenance team receives them on ground and new cockpit and cabin faults
YES as a confirmation of the failure. Then the team on ground can decide and anticipate priorities for maintenance actions. that have been identified as fault
EFIS
Switching panel origin (correlation results) since
3RD ENGINE START + 3 MIN 80 Kts + 150s 3RD ENGINE
OIT (or CAS>80 Kts if no flight number) (or 2 engines shut down) START + 3 MIN last CFR.
Control panel LOGBOOK Fault covered by ECAM warning? GO IF MEL status? GO
CRUISE (or CAS>80 Kts PiRep: Pilot Report.
OIT Flags: FD, MAINTENANCE if no flight number)
(E_logbook or A/C returns CRS
speed, limit,
NO Logbook deferred item in-service MaRep: Maintenance Report.
etc. Paper Logbook) PILOT A/C LIFT TOUCH PILOT FLIGHT
Continuous
ACCEPTANCE OFF DOWN CLOSURE IN CRS Report contains all closed
Repetitive Chime (CRC) Determine commercial impact /
LOW IN eLOGBOOK eLOGBOOK items since the last maintenance
or Single Chime (SC) depending on airline policy
or Specific sound release, all deferred items and
or Synthetic voice associated maintenance release
Loudspeaker
A/C CMS LEG X parameters depending on the
ECAM / EWD HIGH NO GO airline customization.
A/C configuration, ELOGBOOK FLIGHT LEG
memos, limitations, A/C Acceptance Report is sent by
slats/flaps/turn position 3 E_Logbook Troubleshooting process the pilot before departure including
A/C Flight
Vertical Zone (VZ): WXR ECAM / SD CRS Acceptance CFRs PiRep CFRs PiRep CFRs PFR Closure MaRep A/C status and pre-flight data.
info, terrain vertical info Flight Closure Report gathers
YES Fault recorded NO
Combined with the
vertical synthetic situation in E_logbook?
2 PFR description 6 Deep troubleshooting the whole eLogbook delta entered
since the last A/C acceptance.
MFD ECAM / CP YES NO Ground
Fault recorded Airman WEB
KCCU in PFR?
4 Cockpit Alert page 5 System Monitoring Facilities
Airline engineering AIRBUS Operator MCC Airbus
(ACMS data) (Troubleshooting data, ACMS Preventive
Airbus Indication philosophy Access to item Check if fault is in Check if failure is in System labels, Engineering Data…) maintenance Pending time limited fault message Pending fault message
_ detail page YES COCKPIT ALERT page? NO Monitoring page?
Indications Colours Interpretation Definition The preventive maintenance allows to manage failures which not have an immediate impact on the A/C.
SD NO YES
Warning/Flag RED Configuration or failure requiring immediate action Logbook Objectives To secure A/C OR by avoiding (or at least reducing) logbook entries and flight crew complaints for which maintenance actions are not immediately required.
closed item Enable A/L to manage repair or faults within an airworthiness compatible time limit. Enable A/L to anticipate warning in the cockpit and to be aware of their potential dispatch conditions.
Caution/Flag AMBER Configuration or failure requiring immediate attention but not immediate action Select BITE message
Fault Code Use AirN@v to find the corresponding Select relevant BITE Means Provide the maintenance operator with adequate maintenance information. Including: Allow anticipate maintenance activities to be planned from the ground, thanks to:
GREEN Normal operation = memo Information in procedure or on STATUS page specific procedure message Fault Code Identification of the fault. Identification of the fault.
NO Time remaining before flight crew is alerted (flight phase 1 and 12 only). Possible effect.
Associated TSM/AMM procedure. Priority field (high, low).
WHITE Action completed in a procedure / conditional items Permanent
Data Associated TSM/AMM procedure.
CYAN Action to be carried out in a procedure / checklist items to be checked Apply TSM procedure Failure YES Repair/spare YES Maintenance Airbus General With the pending time limited fault messages, Airbus provides flexibility to the operator The troubleshooting can be prioritised by the airlines thanks to the Possible Effect field
provided by AirN@v isolated? available? action final fix to schedule a maintenance task at best opportunity within the airworthiness limit. and the Priority field accessible for each pending fault message and by considering
Specific memo (e.g. takeoff or landing inhibition) Recommendations
MAGENTA Automatic mode The scenario starting The faults shall be corrected before the end of the timer max value in order to avoid the associated dispatch condition of the possible effect.
ATC NO implementation the more effective constraints due to a warning (rectification cat C = 10 days). The faults shall be corrected at best opportunity depending on the priority and possible
Items not valid - not active / title and items of a completed normal checklist Mail Box Manual mode Can be performed by the OPS
GREY effect dispatch conditions.
Automatical or manual mode Required maintenace action
Advisory Parameter out of normal operating value Fault messages can be managed on-board of each A/C with the CMS or in AIRMAN-web for the complete fleet with a specific pending item tracking function. In addition,
GREEN PULSING Depending on airline policy the customizable AIRMAN-web Severity field can be used in order to fine tune priorization matching airline policy.
Spare center

2 PFR 3 eLogbook functionalities 4 Cockpit Alerts 80 Kts + 150s

or 2 engines
3 ENGINE
START + 3 MIN
Cabin Logbook Maintenance Logbook PILOT LOGBOOK
FAPs (at least 2 OITS (Captain, shut down (or CAS>80 Kts if
Access to PFR page PFR home page AirN@v ON-BOARD 2 per deck) Several First officer) no flight number)
PMATs 3 ENGINE PFR/CFR
Info Box Main functionalities START + 3 MIN calculation
Logbook Entry _ Certificate of Release to Service (CRS) report. (or CAS>80 Kts if starting
no flight number)
Access to Access to Tabs Assistance for Defect/Snag report.
the PFR eLogbook Icon bar Menu bar 1 OMT
TOC Assistance for Maintenance Action report.
PFR objective: Give efficient information at the end Correlated FDCEs
Serviced report.
of the flight to help maintainers restore the A/C
Link to MEL/CDL documentation. Board DB
Items
Updating (synchronization with ground) Maintenace Phase Flight Phase Maintenace Phase
Correlated faults Fault origin displayed in bold of the eLogbook data on the aircraft.

• Each tab contains groups of PFR items (Set of correlated data) Cockpit Alert function coverage Phase only covered by Cockpit Alert function PFR Coverage CFR computation (sent if new event appears)
• Each line corresponds to a PFR item and displays summarized information
Maintenance action management
• To get all information on one item, click on the corresponding line
A/L INFRASTUCTURE If the fault case is not in the PFR make
Links to documention _ The reference database for the eLogbook Synchronization through ACARS a search in Cockpit Alerts page to find it.
is on ground. Therefore, the maintenance A/L MIS
team shall make sure to work on the updated Cockpit Alerts covering
Ground Logbook push data for
Status confirmed = eLogbook database. • ELB administration _
Cockpit Alerts function covers:
Go to Fault isolation part of the TSM task Main view • Maintenance reporting legal repository
Secondary window Once the maintenance team actions have
Maintenance phase (A/C on ground, out of PFR).
been performed, they are recorded and
CMS Filtering and correlation linked to the eLogbook entry. Ground DB Flight phases (PFR).
_ 5 types of links can launch applications from the documentation
in Airn@v (only available on board). An eLogbook item is closed or deferred Serviced report creation
by electronical signatures of the report
Objective
LOAD link to DLCS application for data loading. (ID, password).
_ The maintenance team can record the serviced actions, _ Selected Effect
DURING FLIGHT Provide the maintainer with the A/C status whatever
which are entirely customizable, based on the airline’s need. the phase of the A/C (Flight or Maintenance):
IDENT link to DLCS application for equipment identification. Each maintenance report may include
one or several actions. At the end, the report is electronically signed (ID, password). Ease ECAM troubleshooting on ground,
C/B link to PDCS application with corresponding circuit breaker selection. out of PFR coverage.
All C/B link to PDCS application with all table content. Selection of one FDCE shows all fault messages Faults messages Correlated
DB CMS BITE links to CMS application for interactive mode operation.
associated to this FDCE and currently sent by to the selected effect above
the A/C.
Direct access
to TSM
A380 PFR philosophy Use case
_ _ Mainly for failure that occurred on ground Acces to MEL
Warnings and BITE
Filtering PFR TAB Cockpit items Cabin items Pending items Minor items (after PFR closure and before next PFR opening).
messages recording _Objective: Fault type Cockpit Cabin Pending time limited Pending Minor Classless Status of failure that occurred in-flight
(uplink request).
• To Filter out a BITE message or an Effect (FDCE) Impact Flight operational impact Cabin operational impact No operational impact Possible FDE when com- Degaded functioning Not applicable
PFR BUILDING (passengers comfort only) as long as the time period bined with one or several not related to operations
when not relevant for maintenance (i.e. spurious). is not exceeded additional failures nor passengers comfort

• Filtering is applied before correlation (pre-correlation

5 System Monitoring
Warnings / BITE Messages to take List of items: Correlated Warnings / BITE filtering) and after correlation (post-correlation filtering):
CORRELATION Description Any detected failure Any detected failure Any detected failure to be Any detected failure with Any detected failure Any detected failure
messages messages A/C PFR
into account ALGORITHMS Warnings and messages
BITE messages & FDE occurrences are filtered and generating a Flight generating a Cabin Effect fixed within a certain time neither immediate FDE with neither Flight Deck for which an operational
FILTER BEFORE FILTER AFTER not taken into account in correlation.
Deck Effect (FDE) period nor Cabin Effect and time effect nor Cabin Effect effect is not known
limitation, but generating and without time limitation by te monitoring unit
a Flight Deck and Cabin
DB CMS Effect (FDCE) when If the fault is neither in PFR nor in Cockpit Alerts,
FDCE/Failure messages correlation Note: combined with one or then launch System monitoring to find it.
Filter before Filter after The CMS filter file is delivered by Airbus and it’s two additional failure(s)
_ _
Before correlation After correlation applied on the PFR, CFR, System monitoring System monitoring main objectives
(pre correlation filtering): (post correlation filtering): and Cockpit ALERTs. Indication FLIGHT DECK EFFECT CABIN EFFECT NO FDE (Deferred) NO FDE NO FDE NO FDE _ To check the status of selected systems,
Messages are filtered and Failure/Failure correlation (FDE) NO CABIN EFFECT (when not combined) NO CABIN EFFECT NO CABIN EFFECT
The whole PFR item is filtered after a lot of maintenance activities.
are not taken into account • Specific correlation (Specific msg, if one fault origin message is
NO CABIN EFFECT
in the correlation. A filtered To check the presence of a failure with no visual effects.
pending, IMA, ADCN, NSS) defined to be filtered and there
message is not present
in the PFR. • Correlation by fraternity is no associated logbook entry. Correlation Dispatch (MEL) MEL ENTRY ACCORDING NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE
The System Monitoring provides operators with all the current
active BITE messages for pre-selected avionics system
and paternity _Objective: Consequences GO, GO IF or NO GO TO AIRLINE POLICY Move to "Cockpit Items"
tab at the end of the
Move to "Cockpit Items"
tab when combined
(ATA identified and then system).

• Correlates FDCEs and Failures Messages. deferred time period

Association (logbook report, TSM) Note: Possible pro-active PRO-ACTIVE MAINTENANCE PREVENTIVE PREVENTIVE ACCORDING NOT APPLICABLE
and preventive via AIRMAN-web MAINTENANCE MAINTENANCE TO AIRLINE POLICY
The most important message (“fault origin”) maintenance Shall be solved within A correction is recom-
of the fault case is the first message in the PFR. the time period (to antici- mended to improve
pate on future warning) dispatch reliability

6 Deep Troubleshooting DLCS DLCS Environment Annexes

System Page Reports
(access from PFR page):
Snapshots of the parameter values are
_
Purpose
AVIONICS
WORLD
OPEN
WORLD CD/DVD
ROM
_
CMS Architecture
Allows Software repair and upgrade on target Standard A uses a combination of A429 data buses FWC - Flight Phases/System Display
automatically recorded when the two following
hardware from a centralized system. Avionics World Open World and discrete connections between the CMS and
conditions are fulfilled: a system failure occurs LRU’s NSS NSS Avionics domain A flight is divided into twelve phases which are computed according
Access to ACMS page: Display on OMT/OIT A/C systems. There are 2 types of standard A:
and a CMS request is sent to the ACMS Eases A/C configuration reporting and management. ARINC 429 DLCS to parameters which are typical for the configuration of the A/C.
(“System page” link in the PFR). A recording ANSU-OPS CDAM ACMS STD-A type 1 systems:
HMI Filght Warning System
Real Time Monitoring Dataset: is also possible following a manual request These systems are characterized by bi-directional
(ACMS button in cockpit, OMT / OIT interface, DLCS MAIN FUNCTION DLCS digital communication with the CMS.
ACARS uplink). LRU’s OMT Control Display System List of STD-A type 1 systems on A380:
SCI
System page report is especially useful Data loading AFDX ADF, SATCOM, CVRS, MMR, RA, RAIMS,
in cases, where the standardized CAPT & eLogbook DME, VHF, VOR.
Uploading loading: REPOSITORY F/O OITS
troubleshooting procedure is not Data transfer (software or batch file) from the STD-A type 2 systems:
successful for any reason. LRU BITE CMS Documentation
repository or from portable media to a target. LRM Maintenance PMAT These systems are characterized by uni-directional
Enter an alpha STD-B
Shared Database (Optional) digital communication to the CMS.
Downloading operation: Systems SCI DLCS
call up in order
to see the real Data transfer from an avionics target to a portable List of STD-A type 2 systems on A380: 1 2 3 4 5 6 7 8 9 10 11 12
time values media (CD/DVD-ROM). ACARS LRU BITE ISIS, OANS and HUD.

NSS un-installation:
STD-A Type1 AFDX Standard B is a new standard, allowing dynamical
Systems Ethernet monitoring of the failures messages (even on ground)
© AIRBUS S.A.S. 31707 Blagnac Cedex, France, 2017. All rights reserved. Airbus, its logo and the product names are registered trademarks. Printed in France. Photo by Airbus. Concept design by Airbus Multi Media Support 20172314. REF.. ISI 45.00.00001 - issue April 2015

Operation used to uninstall software from the NSS

Network BITE and additional information.

wn

r
r

ff

ft

ft

ft

wn
t
target (equipment) to be performed prior to new GROUND ARINC 429

ar
we

te
ar
LRU BITE

tO
On

KT
KT

00

0
Function

af
st

st

do

do
40

80
po
This standard primarily uses AFDX data buses and

Lif
NSS load uploading.

15
V

80
80
e

n
e
Discrete

gin

m
h

ut
gin

+
c
STD-A Type2

uc
Ele

sh
uses a bidirectional digital communication interface

5
ff
En

En

To
tO
Systems

e
gin
to the CMS.

Lif
2
Configuration Reporting Worklfow

En
st
La
After upload mandatory to do a check of real-time
software configuration target. 1 Repository management 2 Target & Load Selection 3 Uploading System BITE schematic function PFR fault message dating
Physical On On On A fault is displayed on PFR if it is received
Flight 1 Flight 2 at least once by the CMS between
Repository Management
Media ground ground ground
Peripherals the start and the end of the PFR.
In accordance with data loading policy & airwor-
thiness authorities: repository has to reflect A/C Cockpit effect
configuration (delete previous SW version). Note:
Message PFR 1 PFR 2
Avoid to install by error an old software version. According to the above figure, continuous fault may
Service Engine / Centralized PFR be dated with date prior to the current PFR
Copy Load P/N provided Cross check Load P/N Start LRU upload according Warning display Maintenance System
Bulletin with SB into Repository displayed with SB content to SB procedure
(it can be 2 or 3 days, or more).
Software Pin Programming (SPP) Continuous
fault
Hardwares Pin Programming are still use for Pin Operational data Operational data Maintenance data
Real-Time System Pages: Programming dealing with safety related data.
DLCS – Data loading workflow - Uploading:
(Cockpit effects) (Cockpit effects) (BITE message) CMS – Table of correspondence
5 Equipment Identification 4 Repository management Intermittent
One or two page(s) exist per main aircraft system which are line maintenance-oriented. For all other data, A380 uses Software Pin SB application Service Bulletin provides user fault STD/PN/Mod/SB
Each page contains the most relevant parameters for a system in real-time on OMT/OIT. Programming data. with Uploading procedure description Function Anomaly Analysis Fault msg
Detection / construction CMS NSS CMC Operational
These pages can be used for a quick overview of the system during ground tests or for troubleshooting. (P/N off vs. P/N on). Computation (Fault component Mod
Reconfiguration Intermittent Standards Standards Software PN
Notes: isolation)
Memorisation fault
• SPP data are broadcasted by SCI (Secured Notes: L3D 2B+ Step 2 ABF3AA8FNEL0007 70850
Communication Interface) to all LRUs. • This use case is the maximum operating workflow. Monitor Manuel Tests
• DLCS acquires the SPP and can display them. Test request Intermittent 2B+ Step 3
• For the general DLCS workflow step 1 and step 4 Operational Part Stimuli Bite Part fault L3E1.1 ABF33A8FNCL0008 72879
• SPP loads must be stored in DLCS Repository are not used. Check that LRU new configura- Delete previous Load P/N 3.0
Complementary data: (for DLCS display). tion comply with S/B content from Repository Aircraft System Fault date in PFR 1 Fault date in PFR 2 2.4.1
L3E1.2 ABF30A8FNAL0009 75695
A fault message and maintenance data related to the fault are available through the CMS 3.0.4
Engineering function in the "Fault detail" CMS page.

ALPHA CALL-UP NAMES Glossary

The ACMS gives the possibility to define short names for A/C parameters
and to display these parameters in real time.
_
A/C: Aircraft
ACARS: Aircraft Communication Addressing
and Reporting System
CAPT: Captain
CAS: Calibrated Air Speed
C/B: Circuit Breaker
EFIS: Electronic Flight Instrument System
ELB: E-Logbook
EWD: ECAM Warning Display
KCCU: Keyboard and Cursor Control Unit
KTS: Knots
OMT: On-board Maintenance Terminal
OIS: On-board Information System
OIT: On-board Information Terminal
SC: Single Chime
SCI: Secure Communication Interface
SD: System Display
The Airbus definition includes Alpha Call-Up names for parameters which CDL: Configuration Deviation List LRM: Line Replaceable Module OPS: Operators
ACMS: Aircraft Condition Monitoring System CDAM: Centralized Data Acquisition Module SIL: Service Information Letter
are used in the Airbus standard database ACMS functions (ACMS Reports, FAP: Flight Attendant Panel LRU: Line Replaceable Unit OR: Operational Reliability
ADCN: Advanced Data Communication Network CFR: Current Flight Report FD: Flight Directory SPP: Software Pin Programing
SAR, System pages). Airlines can specify other or new Alpha Call-Up CMS: Central Monitoring System
ADR: Air Data Reference FDE: Flight Deck Effect MCC: Maintenance Control Center PDCS: Power Distribution Control System SW: Software
names through the ground Tool. CP: Control Panel
AFDX: Avionics Full DupleX FDCE: Flight Deck and Cabin Effects MEL: Minimum Equipment List PFD: Primary First Display
Alpha Call-Up name structure: CRC: Continuous Repetitive Chime PFR: Post Flight Report TOC: Table of Contents
AIRMAN: Aircraft Maintenance Analysis FWC: Flight Warning Computer MFD: Multi Function Display
CRS: Certificate of Release to Service
A/L: Airline CVRS: Cockpit Voice Recorder System MIS: Management Information Services PMAT: Portable Maintenance Access Terminal TSM: Trouble Shooting Manual
AAAAAAAAAA.S1.S2 AMIS: Airline Maintenance Information System GLD: Ground Logbook Data MMR: Multi Mode Receiver PN: Part Number
AMM: Aircraft Manual Maintenance DB: Data Base VHF: Very High Frequency
DLCS: Data Loading and Configuration System HMI: Human Machine Interface ND: Navigation Display RA: Resolution Advisory
Redundancy suffix, if required ARINC: Aeronautical Radio Incorporated HUD: Head-Up Display NSS: Network Server System VOR: VHF Omnidirectional Range
DME: Distance Measuring Equipment
The instance suffix, if required ATC: Air Traffic Control SAR: Smart ACMS Report VZ: Vertical Zone
Master name, which can have ECAM: Electronic Centralized Aircraft IMA: Integrated Modular Avionics OANS: On-board Airport Navigation System SATCOM: Satellite Communications
up to 10 characters BITE: Built In Test Equipment Monitoring System ISIS: Integrated Standby Instrument System OMS: On-board Maintenance System SB: Service Bulletin WXR: Weather