LEVEL III - ATA 45 Onboard Maintenance System

A380
TECHNICAL TRAINING MANUAL

MAINTENANCE COURSE - T1 & T2 (RR / Metric)
LEVEL III - ATA 45 Onboard Maintenance System
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 - ATA 45 ONBOARD MAINTENANCE SYSTEM

Onboard MAINT SYS & Central Maint. SYS
Theory System
Onboard Maintenance System Description (3) . . . . . . . . . . . . . . . . . .2
OMS Human-Machine Interface (HMI) Description (3) . . . . . . . . . .10
Central Maintenance System Description (3) . . . . . . . . . . . . . . . . . . .44
Central Maintenance System HMI Description (3) . . . . . . . . . . . . . .74
Data Loading & Configuration System
Theory System
Data Loading & Configuration System Desc. (3) . . . . . . . . . . . . . . .94
Data Loading & Configuration System HMI Desc. (3) . . . . . . . . . .118
Right-OMS
Theory System
Right-Onboard Maintenance System Description (3) . . . . . . . . . . .132
Right-Onboard Maintenance System HMI Desc. (3) . . . . . . . . . . . .144
Aircraft Condition Monitoring System
Theory System
Aircraft Condition Monitoring System Desc. (3) . . . . . . . . . . . . . . .152
Aircraft Condition Monitoring SYS HMI Desc. (3) . . . . . . . . . . . .174
L1W06161 - L0KT0T0
MAINTENANCE COURSE - T1 & T2 (RR / Metric) TABLE OF CONTENTS Apr 21, 2006
LEVEL III - ATA 45 Onboard Maintenance System Page 1
ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

General
The Onboard Maintenance System (OMS) is designed to support line
and hangar maintenance activities, and engineering follow-up.
The OMS main purpose is to easily make the:
- Failure detection/reporting
- Dispatch
- Repair
- Servicing
- Maintaining continued Airworthiness
- Storage or return into service
- Managing A/C configuration
L1W06161 - L0KT0T0 - LM45D1OMS000001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM45D1OMS000001
GENERAL

OMS Architecture
The OMS is part of the Network Server System (NSS) and is hosted in
the Aircraft Network Server Units-OPerationS (ANSUs-OPS) in the
Avionics Domain. The OMS is composed of maintenance related
applications and maintenance shared database, which are applications
used to record or share data. These maintenance data are acquired mainly
from the aircraft systems in the Avionics World, through the Centralized
Data Acquisition Module (CDAM) and the Secure Communication
Interfaces (SCIs).
The OMS applications can be accessed from the following
Human-Machine Interfaces (HMIs):
- Onboard Maintenance Terminal (OMT)
- CAPT and F/O Onboard Information Terminals (OITs)
- Portable Multipurpose Access Terminals (PMATs)
- Main and Upper deck Forward Attendant Panels (FAPs)
- Printer 1 (for data/reports retrieval)
The OMS can communicate with the operational ground centers via
service providers in order to get maintenance data exchanges.
Note that the OMS monitors the Avionics World and NSS Avionics
Domain systems and manages their maintenance functions.
Flight Operations and Communication and cabin domain are monitored
L1W06161 - L0KT0T0 - LM45D1OMS000001
by right-OMS functions hosted in the Open World Diode (OWD) right

side.
L1W06161 - L0KT0T0 - LM45D1OMS000001
OMS ARCHITECTURE

OMS Applications
The OMS is composed of several applications dedicated to the support
of aircraft maintenance tasks:
- The Central Maintenance System (CMS) Application
- The Data Loading and Configuration System (DLCS) Application
- The Aircraft Condition Monitoring System (ACMS) Application
- The Power Distribution Control System (PDCS) Application
- The electronic-Logbook (e-Logbook)
- The electronic documentation: AirN@V and Flight Operations
Consultation Tool (FOCT)
L1W06161 - L0KT0T0 - LM45D1OMS000001
L1W06161 - L0KT0T0 - LM45D1OMS000001
OMS APPLICATIONS

OMS Air-Ground Datalink Capabilities
The OMS can communicate with the operational ground centers to enable
maintenance data exchanges. In order to send and receive data, the OMS
can use communication means from the Avionics World or Open World
systems.
In the first case data are transmitted via the SCIs and the Avionics Data
Communication Network (ADCN), and sent through the Avionics
Communication Router (ACR) to the:
- High Frequency Data Radio (HFDR)
- VHF Data Radio (VDR)
- SATCOM
OMS data can also transmit through the Open World right-side systems:
- High Speed Data Unit (HSDU) which is part of the SATCOM
- Wireless Airport Communication System (WACS: Gatelink
communications)
L1W06161 - L0KT0T0 - LM45D1OMS000001
L1W06161 - L0KT0T0 - LM45D1OMS000001
OMS AIR-GROUND DATALINK CAPABILITIES
OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

Open World Shell Login Screen
This screen is the first screen that appears on the Onboard Maintenance
Terminal (OMT) after starting. It lets the operator log on and get access
to the Network Server System (NSS) Applications related to his profile.
Depending on the airline policy, it can be mandatory to enter the user
name and password to log on. If the operator logs on as maintainer, he
will then access to the Onboard Maintenance System (OMS) home page.
L1W06161 - L0KT0T0 - LM45D2OMSHMI001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3) Apr 18, 2006
OPEN WORLD SHELL LOGIN SCREEN

OMS Home Page and Main Functions Screens
The OMS home page is the main entry point, for maintenance staff, to
get access to all A380 onboard maintenance functions.
The OMS interface is always composed of a general header that shows
aircraft and flight identifications and gives access to all maintenance
functions from several menus.
It also integrates an information window for navigation or software events,
and contextual buttons (print, export, back, close). In addition the OMS
home page gives access directly to particular OMS functions:
- "data synchronization" that ensures consistency between ground and
onboard data
- "logbook data" that gives access to the logbook
- "Post Flight Report"
- "Servicing Report" that gives servicing items status and related
procedures
- "Serviced Report" for servicing actions reporting
- "Maintenance Release" to report all maintenance actions done on the
aircraft and to before dispatch
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS

OMS Home Page and Main Functions Screens (continued)
Data Synchronization Screen
The synchronization ensures the consistency between Air and Ground
Logbook database
The synchronization enables to take control of the logbook (writing
rights).
During a synchronization, all new entries both from the aircraft and
the ground are updated in the OMS and AIRMAN database.
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - DATA SYNCHRONIZATION SCREEN

Logbook Data Screen
When you click on the "Logbook data" button on the OMS home
page, you get access to the "Logbook Entries" page.
This page shows all "Open" and "Deferred" entries.
Each logbook entry is identified by:
- Entry date
- Context, type
- Crew Observation
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - LOGBOOK DATA SCREEN

Post Flight Report Screen
When selected on the OMS home page, the Post Flight Report shows
the faults occurred during the last flight.
These faults are classified depending on several criteria that can be
customized by the Airline.
Depending on their classification, the fault can be accessed using tabs.
Note that two display modes are possible:
- Full display mode: all faults are shown
- Smart display mode: faults are shown depending on a filter rule
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - POST FLIGHT REPORT SCREEN

Servicing Report Screen
When selected on the OMS home page, the Servicing Report page
gives:
- the status of servicing items
- directly access through hyperlinks to related servicing procedures
in the electronic documentation
- access to the Serviced Report through hyperlinks
The following systems can generate servicing reports:
- Engines
- Tire pressure
- Oxygen
- Supplemental cooling
- Avionics ventilation
- Hydraulic
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - SERVICING REPORT SCREEN

Serviced Report Screen
When you click on the "Serviced Report" button on the OMS home
page, you get access to the Serviced Report page which is used for
report and validation of all servicing actions done on the aircraft. The
reporting is kept in a scratchpad until validation.
After validation the page is frozen and the content of the report cannot
be modified.
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - SERVICED REPORT SCREEN

Maintenance Release Screen
When selected on the OMS home page, the Maintenance Release page
is used for the validation of all maintenance actions done on the
aircraft. The reporting is kept in a scratchpad until validation. When
the Maintenance Release is validated, the aircraft can be dispatched.
OMS HOME PAGE AND MAIN FUNCTIONS SCREENS - MAINTENANCE RELEASE SCREEN

OMS Tools Menu Screen
When you click on the "Tool" Menu, you can get access to the following
functions
- DLCS - A/C Configuration
- DLCS - Data Loading
- DLCS - Repository Management
- DLCS - SPP
- DLCS - System Identification
- DLCS - Customization
- CMS - Post Flight Report
- CMS - System Report/Test
- CMS - System Monitoring
- CMS - History clear
- CMS - Engineering
- CMS - Item Detail
- Logbook - Maintenance Release
- AOC
- Refuel
- Power Distribution Control
Note that all functions related to Central Maintenance System (CMS)
and Data Loading and Configuration System (DLCS) Applications are
presented in other dedicated chapters. In this chapter, we will focus on

Airline Operational Control (AOC), Refuel, and Power Distribution
control functions.
OMS TOOLS MENU SCREEN

OMS Tools Menu Screen (continued)
AOC Application Screen
When selected the Airline Operational Control (AOC) page you can
consult all messages exchanged between the aircraft and the ground.
OMS TOOLS MENU SCREEN - AOC APPLICATION SCREEN

Refuel Application Screen
When you get access to the "Refuel" function from the "Tool " Menu,
you get access to the "Refuel" page to manage the refueling of the
aircraft. From this page you can get access precisely to all data related
to refueling actions.
OMS TOOLS MENU SCREEN - REFUEL APPLICATION SCREEN

PDCS Application Screen
When you select the "Power Distribution control" from the "Tool"
Menu, you get access to the Power Distribution control Page.
The Power Distribution Maintenance Interface (PDMI) is used for
maintenance tasks on ground. The PDMI is used for the monitoring
of all protective devices, classical electromechanical protection devices
included, and RCCBs and SSPCs programmable control.
The basic functions of the Power Distribution Control are to:
- display the status of all protective devices,
- change the status of a Solid State Power controller (SSPC) channel
or programmable Remote Control circuit Breaker (RCCB),
- reset a trip of a SSPC channel or programmable RCCB,
- create maintenance tags for SSPC channels and programmable
RCCBs,
- download the database for SSPCs and programmable RCCB,
- sort protective devices by a given criteria,
- and manage up to six different accesses.
OMS TOOLS MENU SCREEN - PDCS APPLICATION SCREEN

OMS Data Menu Screen
When you click on the "Data" Menu, you can get access to the following
functions:
- CMS - Maintenance History
- CMS - Configuration
These functions are detailed in the Central Maintenance System (CMS)
Application Chapter.
OMS DATA MENU SCREEN

OMS Documents Menu Screen
When you click on the "Documents" Menu, you can get access to the
onboard electronic documentation:
- Flight Operations Consultation Tool (FOCT) for flight crew related
manuals
- AirN@V for maintenance related manuals
OMS DOCUMENTS MENU SCREEN

OMS Documents Menu Screen (continued)
FOCT Screens
The FOCT Application gives access to flight crew manuals.
OMS DOCUMENTS MENU SCREEN - FOCT SCREENS

OMS Documents Menu Screen (continued)
AirN@V Screens
AirN@V Application gives access to the following Maintenance
manuals:
- TSM
- AMM
- IPC
- ASM
- AWM
- ESPM
either directly or from the troubleshooting function.
OMS DOCUMENTS MENU SCREEN - AIRN@V SCREENS

OMS Utilities Menu Screen
When you click on the "Utilities" Menu, you can get access to the
following Aircraft condition Monitoring System (ACMS) functions:
- Real-time Monitoring
- Data Recording
- Condition Monitoring
These functions are detailed in the Aircraft Condition Monitoring system
(ACMS) Application chapter.
OMS UTILITIES MENU SCREEN
CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

General
The purpose of the Central Maintenance System (CMS) is to centralize
the data related to A/C fault events.
The Central Maintenance System (CMS) acquires aircraft fault symptoms
from the aircraft systems and in particular from the BITEs of the Line
Replaceable Units (LRUs) and the Line Replaceable Modules (LRMs).
The CMS has two operating modes:
- the normal mode (on ground and in flight)
- the interactive mode (only on ground)
In normal mode, the CMS:
- performs system continuous monitoring
- detect and identify failures
- centralize failure events and parameters sent by the BITEs
- generate reports
The CMS interactive mode lets:
- access the e-logbook, AirN@V and the MEL
- launch interactive system tests
- access to system monitoring
- access to servicing reports
- access to maintenance history
L1W06161 - L0KT0T0 - LM45D3CMS000001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM45D3CMS000001
GENERAL

CMS Architecture
CMS General Architecture
The CMS centralizes the fault symptom data of the Avionics World
and of the Avionics Domain in the NSS. The CMS has a CMS
Application hosted in the Aircraft Network Server Units-OPerationS
(ANSUs-OPS). This CMS Application acquires aircraft systems
BITEs, flags and advisories from the Control and Display System
(CDS), warnings and flight phases from the Flight Warning System
(FWS).
It also acquires logbook entries and servicing parameters.
The CMS is also linked to the onboard documentation for
troubleshooting procedures and has the capability to share data with
other Onboard Maintenance System Applications through the shared
database.
The HMIs which are used to control the CMS are:
- The CAPT and F/O Onboard Information Terminals (OITs)
- The Onboard Maintenance Terminal (OMT)
- The Portable Multipurpose Access Terminal (PMAT)
- The Printer 1 (for maintenance reports)
Note that the CMS can communicate with the operational ground
centers via service providers in order to enable maintenance data
L1W06161 - L0KT0T0 - LM45D3CMS000001
exchange.
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS ARCHITECTURE - CMS GENERAL ARCHITECTURE

CMS Architecture (continued)
CMS Detailled Architecture
The CMS 1 (2) Applications are fully redundant and hosted in the
ANSUs-OPS 1 (2). Each CMS Application communicates to the other
its status in order to determine which application must write in its
associated database. By default, CMS 1 in ANSU 1 is responsible for
CMS functions achieving.
Then a synchronization ensures the consistency between the two
ANSUs shared database.
Then in terms of NSS architecture, note that:
- The OMT is connected to the Aircraft Router Unit OperationS
(ARU-OPS) 2
- The OIT CAPT is connected to ARU-OPS 1
- The OIT F/O is connected to ARU-OPS 2
- The printer is connected to ARU-OPS 1
- There are nine PMAT plugs connected to the Secure Interface Router
Unit (SIRU)
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS ARCHITECTURE - CMS DETAILLED ARCHITECTURE

Avionics World BITE Philosophy
Standard A and B BITEs
The A380 system BITEs integrate two different standards:
- Standard A BITEs
- Standard B BITEs
The Standard A BITE is already implemented on Single Aisle and
Long Range aircraft. Note that on the A380 computers, mainly ATA
23 and 34 system computers integrate Standard A BITEs.
The Standard A BITE has the following specificities:
- the fault messages are transmitted in plain English to the CMS
- it concerns only A429 subscribers
- up to four interactive tests can be launched at the same time
The new features introduced by Standard B BITEs are:
- the fault messages are transmitted to the CMS using fault codes
- system status are continuously monitored
- it concerns both A380dedicated A429 and AFDX subscribers
- up to six interactive tests can be launched at the same time
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
AVIONICS WORLD BITE PHILOSOPHY - STANDARD A AND B BITES

Avionics World BITE Philosophy (continued)
LRU BITE Philosophy
In LRUs with A429 interface, the BITE process is based on the
following steps:
- LRU and connected equipments fault detection
- Fault isolation
- Memorization
- Storage in a non-volatile memory
Then, depending on the BITE Standard (A or B) faults are sent to the
CMS via the SCIs either in plain English or in coded values.
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
AVIONICS WORLD BITE PHILOSOPHY - LRU BITE PHILOSOPHY

LRU (with an AFDX Interface) BITE Philosophy
LRUs with an AFDX interface only integrate Standard B BITEs. The
BITE process of these LRUs consists in the following steps:
- LRU and connected equipments fault detection
- Computer BITE
- Network BITE (BITE dedicated to the detection and isolation of
network communication loss)
Computer BITEs data are directly sent to the CMS via the SCIs.
Network BITE information are first sent to the Network BITE Function
(NBF) via the SCI.
The NBF purpose is to centralize and process Network BITEs data
which are then sent to the CMS.
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
AVIONICS WORLD BITE PHILOSOPHY - LRU (WITH AN AFDX INTERFACE) BITE PHILOSOPHY

IOM BITE Philosophy
The Input/Output Modules (IOMs) integrate only Standard B BITEs.
The BITE process of IOMs has:
- IOM core software and hardware fault detection
- Both hardware and core software fault identification by means of
Ressource and Network BITEs
The Ressource BITE is similar to a computer BITE; it manages the
fault detection and identification of the IOM (including software and
hardware levels).
The Network BITE is dedicated to the detection and isolation of
network communication loss.
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
AVIONICS WORLD BITE PHILOSOPHY - IOM BITE PHILOSOPHY

CPIOM BITE Philosophy
The Core Processing Input/Output Modules (CPIOMs) integrate only
Standard B BITEs. The BITE process of CPIOMs has:
- CPIOM core software and hardware fault detection
- Both hardware and core software fault identification by means of
Ressource and Network BITEs
- LRU and connected equipments and system application fault
detection by the System Application BITE
Then the System Application BITE data are sent to both the Resource
BITE and to the CMS via the SCIs. Resource BITE makes a first
correlation, and data are then also sent to the CMS.
Network BITE information are sent to the NBF and after centralization
and Network BITEs correlation, the NBF sends correlated BITEs data
to the CMS.
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
AVIONICS WORLD BITE PHILOSOPHY - CPIOM BITE PHILOSOPHY

NSS Avionics Domain BITE Philosophy
NSS Avionics Domain BITE Function
The NSS BITE obeys to the same philosophy than the computers
standard BITEs:
- a fault detection: software and hardware fault detection
- then faults are identified and correlated
- after correlation, the BITE fault codes are sent to the CMS.
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
NSS AVIONICS DOMAIN BITE PHILOSOPHY - NSS AVIONICS DOMAIN BITE FUNCTION

NSS Avionics Domain BITE Philosophy (continued)
NSS Avionics Domain BITE Architecture
The NSS BITE function is to centralize the BITEs of Avionics Domain
LRUs and some other connected systems like the Centralized Data
Acquisition Module (CDAM) and Human Machine Interfaces (HMIs).
The NSS BITE is an application hosted in ANSU-OPS 1 and 2.It
monitors and receives BITE information from:
- the CDAM (which is out of the NSS domains)
- the SCIs
- the Secure Interface Router Unit (SIRU)
- the NSS Control Units (NCUs)
- Part of NSS HMIs:
The Onboard Maintenance Terminal (OMT)
CAPT and F/O Onboard Information Terminals (OITs)
Main and upper deck Forward Attendant Panels (FAPs)
Printer 1
The NSS BITE Application receives the BITE information of the
above equipments through the Aircraft Router Unit-OPerationS
(ARU-OPS), which also sends its own BITE data. The NSS BITE
also monitors the failures which can be detected inside the
ANSU-OPS: it receives BITE data from:
L1W06161 - L0KT0T0 - LM45D3CMS000001
- the ANSU-OPS itself

- all Onboard Information System (OIS) software applications hosted
in the ANSU-OPS
Finally the NSS BITE has the capability to detect failures related to
the Open World Diode (OWD). Note that the OWD is also monitored
from its other side, by the right-OMS.
So after the centralization of BITE data, the NSS makes a correlation
and sends the correlated fault codes to the CMS.
L1W06161 - L0KT0T0 - LM45D3CMS000001
NSS AVIONICS DOMAIN BITE PHILOSOPHY - NSS AVIONICS DOMAIN BITE ARCHITECTURE

CMS Correlation
Fault Code Description
Standard B BITEs messages are not sent in plain English like Standard
A BITEs fault messages, but in fault codes. A fault code is the unique
identifier for a failure event. A fault code is composed as follows:
- the four first digits agrees with the ATA chapter related to the event
- the middle letter indicates the type of the event
- the three last digits are dedicated to the event number for
memorization in CMS database
A fault code, and in particular its middle letter is identified as follows:
- W: an ECAM warning
- N: an ECAM Inoperative Status
- F: a fault message
- G: a flag on Display Unit (DU)
- A: an advisory on DU
- D: other flight deck or cabin effect on CDS
- X: a local effect monitored
- L: a local effect + a CDS effect non monitored
- C: an observation non monitored and not localized
- B: an observation out of TSM scope for e-logbook
- E: a cabin malfunction
L1W06161 - L0KT0T0 - LM45D3CMS000001
Note that the fault codes are used by the CMS for correlation purposes.
They also appear in the Fault Item Detail Page related to the PFR on
the OMS tool/application.
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS CORRELATION - FAULT CODE DESCRIPTION

- servicing report (if applicable): the airline maintenance team will
CMS Correlation (continued) use these report in order to trigger servicing actions, according to the
parameters measured values and related customizable thresholds
Malfunctions/Documentation Correlation
- maintenance history (maintenance database related to the faulty
The CMS receives all fault symptoms related to system failures. These equipment)
fault symptoms can be aircraft systems malfunctions or logbook - action report (logbook) in order to report the maintenance actions
entries. From aircraft systems, the CMS can receive the following that have been applied for the failure repairing
data:
- fault messages from Standard A BITEs (in plain English)
- fault messages from Standard B BITEs (fault codes)
- warning and cautions from the FWS
- flags or advisories from the CDS
- cabin failure effects
The CMS also receive logbook entries for its correlation process;
these logbook entries are associated:
- either monitored equipment (related to a fault message, a warning
or a flag/advisory)
- or non-monitored (ex: windshield cracks, equipment vibration, etc)
The CMS centralizes all these data in order to correlate them. Before
correlation, the CMS associates a fault code to each fault message
from Standard A BITE, in order to proceed the correlation for these
data. Then, the CMS does the correlation process based on fault codes.
The CMS correlates fault events and related symptoms (fault messages,
L1W06161 - L0KT0T0 - LM45D3CMS000001
warning and caution, flag and advisory) in order to determine the

origin of the fault: only one failure identifier for the mechanics.
Then this failure identifier is related to the unique dedicated:
- fault item detail: detailed list and description of all correlated fault
symptoms related to a failure event
- maintenance documentation: it determines precisely the correct
MEL/TSM/AMM procedure to follow to repair the failure and to
dispatch the aircraft. This procedure can be directly reached through
a hyperlink available in the fault related item detail page.
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS CORRELATION - MALFUNCTIONS/DOCUMENTATION CORRELATION

CMS Data Recording During a Flight
During a flight, maintenance data received by the CMS are recorded in
a time frame defined by several criteria.
CMS data recording is launched if:
- three or more engines are running plus 180 sec and,
- Calculated Air Speed (CAS) higher than 80 kts or a new flight number
has been entered by the pilots
CMS data recording is stopped when:
- Less than 3 engines running
- CAS lower than 80 kts confirmed during 150 sec
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS DATA RECORDING DURING A FLIGHT

Servicing Report Generation
The Servicing report function is to retrieve servicing parameters sent by
different avionics systems to the ACMS-Real Time (ACMS-RT)
Application (through CDAM), in order to show them in the PFR and in
the servicing report. The airline maintenance team will use these
parameters to launch servicing actions.
Systems requiring servicing monitoring and reporting are:
- Engine Electronic Controller (EEC)
- Hydraulic System Monitoring Unit (HSMU)
- Fuel Quantity and Management System (FQMS)
- Landing Gear Management System (LGMS)
- Oxygen System Control Unit (OSCU)
- Supplemental Cooling System (SCS) and Avionics Ventilation system
(AVS)
Different values of parameters can be displayed:
- The current value
- The value when the flight has ended
- The value at a specific moment during the flight, particularly relevant
for the considered parameter
The airline is able to customize the thresholds for each servicing parameter
through the ACMS. For each threshold, an allowed range and a default
L1W06161 - L0KT0T0 - LM45D3CMS000001
value shall be taken into account.
L1W06161 - L0KT0T0 - LM45D3CMS000001
SERVICING REPORT GENERATION

CMS Customization
Three main CMS functions can be customized:
- the PFR display: PFR tab name (failures classification) and display
mode (smart or full display)
- the filtering: it is possible to add or to remove fault events from the PFR
filter. The filter, once programmed, can be activated or disabled from the
OMS HMI
- aircraft to ground transmissions: it is possible to select the type, the
moment and the mode of the Current/Post Flight Report (CFR/PRF)
transmission
CMS functions can be customized:
- onboard, through the CMS HMI (CMS engineering page)
- from the ground through ACARS
L1W06161 - L0KT0T0 - LM45D3CMS000001
L1W06161 - L0KT0T0 - LM45D3CMS000001
CMS CUSTOMIZATION
CENTRAL MAINTENANCE SYSTEM HMI DESCRIPTION (3)

OMS Tools Menu Screen
The "Tool" Menu of the Onboard Maintenance system (OMS) home page
gives access to the following Central Maintenance System (CMS)
functions:
- Post Flight Report
- System Report/Test
- System Monitoring
- History Clear
- Engineering
- Item Detail
L1W06161 - L0KT0T0 - LM45D4CMSHMI001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) CENTRAL MAINTENANCE SYSTEM HMI DESCRIPTION (3) Apr 18, 2006
OMS TOOLS MENU SCREEN

CMS - Post Flight Report
When you click on the "Post Flight Report" button on the OMS home
page, you get access to the Post Flight Report.
This page shows faults occurred during the last flight. These faults
are classified depending on several criteria which can be customized
by the Airline. Note that two display modes are possible:
- Full display mode: all faults are displayed
- Smart display mode: faults are displayed depending on a filter rule
Faults can be classified upon the several criteria:
- Type
- Severity
- Airline policy
The faults are characterized by:
- The related number
- The context (occurrence time, and date, flight phase)
- Fault case description (cockpit/cabin effect)
OMS TOOLS MENU SCREEN - CMS - POST FLIGHT REPORT

CMS - System Report / Test Screen
The System/Report test function is used for the system tests. To get
access to the dedicated test, you must go through the following steps:
- first ATA selection
- then system/die selection
- finally test selection
OMS TOOLS MENU SCREEN - CMS - SYSTEM REPORT / TEST SCREEN

CMS - System Monitoring Screen
The system monitoring function lets consult in real time the status of
the aircraft systems.
Three selection windows:
- ATA selection
- System selection
- System to monitor selection
- Then start monitoring
Note that the system monitoring of A/C systems is refreshed in
real-time.
OMS TOOLS MENU SCREEN - CMS - SYSTEM MONITORING SCREEN

CMS - History Clear Screen
The CMS History Clear function is used to clear all CMS history data
from the maintenance shared database. Note that a password is required
to get access to this function.
OMS TOOLS MENU SCREEN - CMS - HISTORY CLEAR SCREEN

CMS - Engineering Screen
When you select the "CMS Engineering" function from the "Tools"
Menu in the OMS home page, you get access to the CMS advanced
functions. This function is used to:
- make a maintenance data extended search
- get access to CMS customization functions
From the customization functions, you can modify:
- the transmission to ground
- the reports organization
- the PFR fault classification (customizable tabs)
OMS TOOLS MENU SCREEN - CMS - ENGINEERING SCREEN

CMS - Item Detail Screen
To get access to the Item detail page related to a particular fault event:
- click on the fault event on the PFR or
- click on the related logbook entries
- or directly select the item detail function related to a this fault event
in the "Tools" Menu
Depending on the fault event, this page can display:
- fault correlated logbook entries
- correlated cockpit effects
- correlated fault messages
- correlated servicing events
This page also gives access to:
- the maintenance history related to the fault event
- the related MEL procedure
- the related TSM procedure
- the action report fault maintenance action reporting (if any)
OMS TOOLS MENU SCREEN - CMS - ITEM DETAIL SCREEN

OMS Data Menu Screen
When you click on the "Data" Menu, you can get access to the following
functions:
- CMS - Maintenance History
- CMS - Configuration
These functions are detailed in the Central Maintenance System (CMS)
Application Chapter.
OMS DATA MENU SCREEN

OMS Data Menu Screen (continued)
CMS - Maintenance History Screen
The Maintenance History function is used of the searches in the
maintenance database to retrieve particular data which can be:
- logbook entries
- fault messages
- cockpit effects
- PFR
- Tests results
The data retrieved can be very useful to make easy the troubleshooting
of failures, and also to gain time using previous maintenance
experience.
OMS DATA MENU SCREEN - CMS - MAINTENANCE HISTORY SCREEN

OMS Data Menu Screen (continued)
CMS - Configuration
The CMS Configuration page is used for the consultation of:
- the current CMS configuration installed in the servers
- the CMS Configuration history
- the CMS configuration updates
OMS DATA MENU SCREEN - CMS - CONFIGURATION
DATA LOADING & CONFIGURATION SYSTEM DESC. (3)

General
The Data Loading and Configuration System (DLCS) manages all data
loading and configuration functions of the Avionics World and of the
Network Server System (NSS) Avionics Domain.
The DLCS has four sub-functions:
- the Data Loading management for up/down loading procedures
- the aircraft configuration monitoring
- the Repository (onboard software database) Management
- the Software Pin Programming (SPP) Management
These functions manage the field loadable software stored in aircraft
computers and/or in the Repository.
All DLCS functions are accessible from onboard maintenance terminals,
via the OMS Human Machine Interface (HMI).
L1W06161 - L0KT0T0 - LM45D7DLCS00001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) DATA LOADING & CONFIGURATION SYSTEM DESC. (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM45D7DLCS00001
GENERAL

DLCS Architecture
DLCS General Architecture
The DLCS has an Application hosted in the two Aircraft Network
Server Units-OPerationS (ANSUs-OPS) of the Avionics Domain
(NSS). This DLCS Application is used to manage software data
loading and configuration.
The DLCS Application stores and retrieves software to/from the
Repository in the shared database hosted in ANSU-OPS, and in A/C
computers as:
- Line Replaceable Units (LRUs)
- LRUs with Avionics Full Duplex Switched Ethernet (AFDX)
interface
- Line Replaceable Modules (LRMs)
The DLCS Applications are also connected to the e-Logbook and to
the aircraft documentation (ex: AirN@V), to ease maintenance
procedures.
The HMIs which are used to control the DLCS are:
- The CAPT and F/O Onboard Information Terminals (OITs) and
their related keyboards
L1W06161 - L0KT0T0 - LM45D7DLCS00001

Note that the DLCS can communicate with the operational ground
centers and service providers in order get maintenance data exchanges.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
DLCS ARCHITECTURE - DLCS GENERAL ARCHITECTURE

DLCS Architecture (continued)
DLCS Detailed Architecture
The DLCS 1 (2) Applications are fully redundant and are hosted in
ANSU-OPS 1 (2). The applications are activated only on one ANSU
but the database are uploaded on both ANSUs mass memory all the
time. Then a synchronization ensures the consistency between the
two ANSUs shared database. If a DLCS Application stops running,
the ANSU core software will trie to relaunch three times the DLCS.
If it fails, the other DLCS Application will be launched on the other
ANSU.
(ARU-OPS) 2
There are nine PMAT plugs connected to the Secure Interface Router
Unit (SIRU)
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
DLCS ARCHITECTURE - DLCS DETAILED ARCHITECTURE

DLCS Functions
The DLCS is composed of four functions, the:
- Data Loading function
- Repository management
- Aircraft Configuration function
- Software Pin Programming function
The Data Loading function manages:
- The upload of a software from CDs or DVDs
- The downloading operations
The Configuration Management function lets:
- compare two configurations of the aircraft
- access configuration history
- access current aircraft configuration
- customize configuration names
Note that the Configuration management and control is an Airline
Responsability
The Repository Management function which lets:
- The addition of software in the database
- The deletion of software from the database
- The display of the software loaded in the database
- Integrity checks of repository
L1W06161 - L0KT0T0 - LM45D7DLCS00001
The Software Pin Programming shows and makes the modification of

the Software Pin Programming.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
DLCS FUNCTIONS

Dataloading Function
Uploading of a Software
An upload procedure is a data transfer from the Repository or from
another media, to the "target hardware".
An uploading can be carried out:
- from the Repository to an aircraft computer
- from a dedicated source (CD, DVD, etc) to the Repository
- or directly from a CD/DVD to an aircraft computer
This loading operation can be needed to load a new software issue,
to update a software in the frame of a Service Bulletin.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
DATALOADING FUNCTION - UPLOADING OF A SOFTWARE

Dataloading Function (continued)
Downloading of a Software
A downloading procedure is a data transfer from a computer or from
the Repository to a transport or storage media. First the operator must
select the software to download, and then the transport or storage
media. The operator can download two types of software:
- a software running on a computer, directly from the computer
- previous or next issue of a software, not running on a computer,
from the Repository
The downloaded software can be:
- stored on a transport or storage media
- sent to the ground using Avionics World or from Open World
communications means
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
DATALOADING FUNCTION - DOWNLOADING OF A SOFTWARE

Repository Management Function
The media containing software loaded in aircraft computers are not kept
onboard the aircraft. The Repository has been defined to store a copy of
the loads and batch files running on the aircraft. Note that the Repository
may contain only some of the currently loaded software. It is also used
to store previous or new versions of computer software not actually
running on the aircraft.
The Repository is only accessible by the DLCS for read and write
functions. The Repository management function lets the addition or
deletion of software.
The deletion of software from the Repository lets save storage area. Note
that it is possible to delete from the Repository a software which is
installed in a target computer.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
REPOSITORY MANAGEMENT FUNCTION

Configuration Management Function
Configuration Function
Aircraft configuration data are stored in a dedicated part of the
maintenance-shared database: the aircraft configuration database. The
DLCS manages the content of this part of the maintenance database.
This part of database can be read by other functions than the DLCS.
The configuration database stores:
- the current configuration data, which is the configuration of the
aircraft at the consultation moment
- the configuration at a determined previous time
The database is updated automatically by the configuration data
periodically sent by the electronic equipment. The main information
contained in the configuration table is the hardware part and serial
numbers and the software part numbers.
Note that it is also possible to load other configuration databases for
comparisons.
The configuration management function also implements a retrieval
function which allows to give access to several reports.
Reports can be printed or exported to the airline ground station or to
the media drive available on the NSS.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
CONFIGURATION MANAGEMENT FUNCTION - CONFIGURATION FUNCTION

- an amendment number, as at most 63 alphanumerical characters
Configuration Management Function (continued) - usual line feed/carriage return characters.
A date time line is composed of:
Equipment Identification / Configuration
- current date
The LRU identification or configuration reports are defined as follows: - current UTC time
- a LRU identification section - usual line feed/carriage return characters.
- zero to several software identification sections
- a date and time line
A LRU identification section is composed of:
- a LRU name line
- a serial number line
- a part number line
- an amendment line (optional)
- a section separator
A software identification section is composed of:
- a identification line
- a part number line
- an amendment line (optional)
- a section separator
A date time section is composed of:
- a date time line
A LRU name line is composed of:
- the name of the LRU, as at most 63 alphanumerical characters
L1W06161 - L0KT0T0 - LM45D7DLCS00001
- usual line feed/carriage return characters

A serial number line is composed of:
- a serial number, as at most 15 alphanumerical characters
- usual line feed/carriage return characters.
A part number line is composed of:
- a part number, as at most 15 alphanumerical characters
An amendment line is composed of:
- an amendment number, as at most 31 alphanumerical characters
An identification line is composed of:
L1W06161 - L0KT0T0 - LM45D7DLCS00001
CONFIGURATION MANAGEMENT FUNCTION - EQUIPMENT IDENTIFICATION / CONFIGURATION

Soft Pin Programming Function
Soft Pin Programming General Phylosophy
The A380 Software Pin Programming (SPP) function objective is to
complete the Hard Pin Programming, when consequences of erroneous
data are not major. Systems for which the consequence of erroneous
data is more than major still remain hard pin programmable.
For SPP applicable systems, the DLCS Application is used to upload
the SPPs and their history and current status.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
SOFT PIN PROGRAMMING FUNCTION - SOFT PIN PROGRAMMING GENERAL PHYLOSOPHY

Soft Pin Programming Function (continued)
Soft Pin Programming Architecture
The SPP function is used for the storage and the distribution of SPP
to all potential AFDX subscribers and ARINC 429 LRUs connected
to the SCIs and to the NSS Applications. Only data managed by Airbus
are applicable to the SPP capabilities. The options, which are left to
the discretion of the Airline, are not in Soft Pin Programmable.
Pin Programmed data is in several loads, which are in the Repository
in the SPP configuration database. The loads are uploaded in the SCIs,
using the DLCS. This uploading is possible only in flight phase 1.
The SCI is in charge of broadcasting every second the Pin Programmed
data to all subscribers of the SPP function on ground and in flight.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
SOFT PIN PROGRAMMING FUNCTION - SOFT PIN PROGRAMMING ARCHITECTURE

Safety Aspects Related to DLCS
On the aircraft the load authentication is integrated in the data loading
process. When the operator initiates an uploading procedure, the DLCS
first triggers the load authentication process thanks to the authentication
certificate hosted in the SCIs. When authenticated, the DLCS lets the
data files loading toward the target computers. The SCIs segregate
datafiles upon their destination (AFDX or A429 subscribers) and send
them via specific gateways.
When received by the target computers, a final integrity check is applied
to the loads: if the Cyclic Redundant Checks (CRCs) are successfully
done, the load can be definitively loaded in target computers.
L1W06161 - L0KT0T0 - LM45D7DLCS00001
L1W06161 - L0KT0T0 - LM45D7DLCS00001
SAFETY ASPECTS RELATED TO DLCS
DATA LOADING & CONFIGURATION SYSTEM HMI DESC. (3)

DLCS - OMS Tools Menu Screen
When you click on the "Tool" Menu, you can get access to the following
Data Loading and configuration System (DLCS) functions:
DLCS - A/C Configuration
DLCS - Data Loading
DLCS - Repository Management
DLCS - SPP
DLCS - System Identification
DLCS - Customization
L1W06161 - L0KT0T0 - LM45D8DLCSHMI01
MAINTENANCE COURSE - T1 & T2 (RR / Metric) DATA LOADING & CONFIGURATION SYSTEM HMI DESC. (3) Apr 18, 2006
DLCS - OMS TOOLS MENU SCREEN

DLCS - Repository Management Screen
When you select the Repository Management function in the "Tools"
Menu, you can get access to the following sub-functions:
- display of Repository content
- removal of software from the Repository
- copy of software into the Repository
- check of Repository validity
DLCS - REPOSITORY MANAGEMENT SCREEN

DLCS - Data Loading Screen
When you select the Data Loading function from the "Tools" Menu, you
get access to the following sub-functions:
- Software upload
- Batch file upload
- NSS uninstall
- Download data
DLCS - DATA LOADING SCREEN

DLCS - Configuration Data Screen
The aircraft configuration function can be accessed from the "Tools"
Menu. This function gets access to the following functions:
the aircraft configuration history
the comparison between two aircraft configurations
the reference name management
the Repository status configuration management
DLCS - CONFIGURATION DATA SCREEN

DLCS - System Identification Screen
The purpose of the System Identification function is used by the operator
to have access to its hardware and software configuration. System
Selection from a search window is based on the following criteria:
- FIN
- Name
- ATA
- System
The equipment identification can be consulted from two identification
reports:
- report from information request
- system identification report
Note that these reports must be consulted before and after each
uploading/downloading procedure.
DLCS - SYSTEM IDENTIFICATION SCREEN

DLCS - Software Pin Programming Screen
The Software Pin Programming (SPP) function is used for Pin
Programming status consultation of aircraft systems at a given previous
time or at the current time. Software Selection from a search window is
based on the following criteria:
- P/N
- Name
- ATA
Date and Time selection is made from the following criteria:
- Reference name
- Date
- Time
DLCS - SOFTWARE PIN PROGRAMMING SCREEN

DLCS - Customization
The DLCS Customization function gives access to the following DLCS
customization capabilities:
- report printing configuration customization
- ground transmission configuration customization
DLCS - CUSTOMIZATION
RIGHT-ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

General
The A380 has two onboard maintenance systems in order to monitor
system status:
- the conventional Onboard Maintenance system (OMS)
- the Right-OMS (R-OMS)
Both OMS and R-OMS are hosted in the Open World in the Network
Server System (NSS) servers, but they have their own specificities:
- the OMS monitors and centralizes failures of systems part of the
Avionics World and the Avionics Domain (NSS) only
- the R-OMS monitors and manages failure of systems connected to the
right side of the Open World Diode (OWD)
Note that the R-OMS is composed of several Local Maintenance
Functions (LMFs), which integrate R-CMS and R-DLCS capabilities.
L1W06161 - L0KT0T0 - LM45D5LMS000001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) RIGHT-ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM45D5LMS000001
GENERAL

Local Maintenance Functions Descriptions
R-CMS functions Description
Each monitored equipment LMF integrates R-CMS capabilities. The
R-CMS functions enables:
- the failure detection and identification
- the centralization of failure events at the equipment level
- reports generation
- interactive system tests
- the access to system monitoring
- the access to maintenance history linked to the related equipment
L1W06161 - L0KT0T0 - LM45D5LMS000001
L1W06161 - L0KT0T0 - LM45D5LMS000001
LOCAL MAINTENANCE FUNCTIONS DESCRIPTIONS - R-CMS FUNCTIONS DESCRIPTION

Local Maintenance Functions Descriptions (continued)
R-DLCS functions Description
Each monitored equipment integrates R-DLCS capabilities. The
R-DLCS functions are used to:
- upload and update software in the equipment
- download software
- upload software in the repository
- delete software from the repository
- access to the equipment configuration history
- display the current configuration
L1W06161 - L0KT0T0 - LM45D5LMS000001
L1W06161 - L0KT0T0 - LM45D5LMS000001
LOCAL MAINTENANCE FUNCTIONS DESCRIPTIONS - R-DLCS FUNCTIONS DESCRIPTION

R-OMS Architecture
R-OMS General Architecture
The OMS (Conventional OMS), connected to the left hand side of the
OWD monitors all systems connected to the left hand side of the
OWD.
This monitoring has the centralization of fault messages transmitted
by:
- the BITE of each system of the Avionics World, via the Secured
Communication Interfaces (SCIs)
- the NSS BITE which centralizes the fault messages parts of the
Avionics Domain (NSS), plus Centralized Data Acquisition Module
(CDAM) fault messages
The R-OMS is dedicated to the monitoring of the fault messages of:
- Flight OperationS (Flight OPS) Domain equipments (NSS)
- Communication and Cabin Domain equipments (NSS)
- Equipments out of NSS but connected to the OWD Right-side in the
NSS
These faults messages are not centralized comparing to the
conventional OMS operation and architecture. Fault messages are
managed by a LMF related and hosted in the equipment itself. That
is the reason why we talk about "Local Maintenance Function".
L1W06161 - L0KT0T0 - LM45D5LMS000001
L1W06161 - L0KT0T0 - LM45D5LMS000001
R-OMS ARCHITECTURE - R-OMS GENERAL ARCHITECTURE

R-OMS Architecture (continued)
R-OMS Detailled Architecture
The systems, which host and are monitored by a LMF are:
- the CAPT and F/O Airframer (AFMR)-laptops in the Flight OPS
Domain
- the Cabin Server Network System-Passengers (CNSU)-PAX in the
Communication and Cabin Domain
- the SATCOM
- the Cabin Video Monitoring System (CVMS)
- the In-Flight Entertainment (IFE) including the Cabin
Telecommunications Unit (CTU)
Each system is in charge of the generation of the Human Machine
Interface (HMI), which is used by the operator to manage the faults
events and dataloading capabilities.
Note that:
- the CAPT and F/O AFMR-laptops HMI is accessible from the SCIs
- the CNSU-PAX, the SATCOM, the CVMS and the CTU HMIs can
be interrogated from the airline cabin laptop
- the other IFE equipments monitoring can be interrogated from the
IFE terminal
L1W06161 - L0KT0T0 - LM45D5LMS000001
L1W06161 - L0KT0T0 - LM45D5LMS000001
R-OMS ARCHITECTURE - R-OMS DETAILLED ARCHITECTURE

Right-side Systems / OMS Functions allocation for EIS
To summarize, the R-OMS integrates maintenance functions dedicated
to:
- the Flight OPS Domain System
- the Communication and Cabin Domain
- the SATCOM
- the CVMS
- the IFE including the CTU
All these systems can be monitored by the R-OMS. There is neither
system test nor fault history related to CVMS and Flight OPS systems.
The workstation or hardware resources used for dataloading are:
- the Onboard Information Terminal (OIT) via USB stick for Flight OPS
Domain system
- the airline laptop via USB stick or RJ145 plug for Communication and
Cabin Domain System, SATCOM and CVMS
- the IFE Terminal for IFE systems
L1W06161 - L0KT0T0 - LM45D5LMS000001
L1W06161 - L0KT0T0 - LM45D5LMS000001
RIGHT-SIDE SYSTEMS / OMS FUNCTIONS ALLOCATION FOR EIS
RIGHT-ONBOARD MAINTENANCE SYSTEM HMI DESC. (3)

Login Screen
Login Screen Home Page
The Right-Onboard Maintenance System (R-OMS) functions are
achieved by Local Maintenance functions (LMFs) hosted in each
monitored equipment. These LMF are also in charge of generating an
equipment dedicated maintenance interface to let the operator use
maintenance features. When the operator wants to get access to this
interface, he first has to log on and to indicate:
- his user group
- his password (depending on the airline policy)
L1W06161 - L0KT0T0 - LM45D6LMSHMI001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) RIGHT-ONBOARD MAINTENANCE SYSTEM HMI DESC. (3) Apr 18, 2006
LOGIN SCREEN - LOGIN SCREEN HOME PAGE

Login Screen (continued)
User group Selection Screen
In order to log on to the right-side systems maintenance interface, the
operator first has to enter his user group.
Clicking on the user group selection button, through a dedicated popup,
gives the following user group selection:
- crew
- purser
- maintenance
- expert
LOGIN SCREEN - USER GROUP SELECTION SCREEN

LMF Home Page Screen
To enter a right-side maintenance function, choose a system from the
navigation bar. The maintenance system you can access depends on the
terminal that has been used to get access to the maintenance functions.
LMF HOME PAGE SCREEN

LMF Pull down Menu
For a dedicated equipment, the R-OMS functions which can be carried
out are:
- access to recorded fault reports
- system status overview
- system monitoring
- system report/test
- load uploading
- equipment identification
LMF PULL DOWN MENU
AIRCRAFT CONDITION MONITORING SYSTEM DESC. (3)

General
The Aircraft Condition Monitoring System (ACMS) main purpose is to
support scheduled and preventive maintenance by monitoring the
efficiency and degradation of the aircraft systems and environment.
The ACMS monitors:
- engines
- aircraft systems
- A/C performances
and to perform in-depth troubleshooting
To achieve these functions, the ACMS is able to:
- generate reports (automatically or manually)
- record data
- display aircraft parameters in real-time
L1W06161 - L0KT0T0 - LM45D9ACMS00001
MAINTENANCE COURSE - T1 & T2 (RR / Metric) AIRCRAFT CONDITION MONITORING SYSTEM DESC. (3) Apr 18, 2006
L1W06161 - L0KT0T0 - LM45D9ACMS00001
GENERAL

ACMS Data Sources
The ACMS monitors and acquires data mainly from the following
systems:
- Engines
- APU
- Fuel
- Bleed
- Flight control
- Hydraulics
- Landing gears
- Braking and steering
- Doors controls
- Environmental control
- Navigation
- Communication
- Autopilot
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS DATA SOURCES

ACMS Functions
The ACMS functions are:
- Aircraft data acquisition via Centralized Data Acquisition Module
(CDAM)
- Data recording in:
Server (NSS)
Recorder (DAR)
Portable media (CD/DVD)
- Data retrieval from Human-Machine Interface (HMI):
Condition Monitoring function
Real-time monitoring function
Recorded data retrieval function
- Data transmission to the ground (reports, etc...)
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS FUNCTIONS

ACMS Architecture
ACMS General Architecture
The ACMS architecture is split up in two parts:
- The ACMS Data Acquisition part dedicated to the acquisition and
the real-time monitoring of aircraft data. This acquisition part is hosted
in the CDAM in the Avionics World, and acquires data from aircraft
system including the engines and the Auxiliary Power Unit (APU).
- The second part of the ACMS is an ACMS Application hosted in
each Aircraft Network Server Units-OPerationS (ANSUs-OPS). This
ACMS Application acquires data directly from the CDAM. This
application performs post-processing as well as storage and output
management of ACMS data. It also has the capability to share data
with other Onboard Maintenance System (OMS) applications through
the shared database.
The ACMS Applications are also linked to the onboard documentation
(AirN@V) to support troubleshooting procedures.
The CDAM provides also data to the Avionics Data Broadcast
Collector (ABDC) Application hosted in each ANSU-OPS 1 and 2.
The data are post-processed by the ABDC and sent to other Network
Server System (NSS) Applications (ex: Airshow). Data requests
L1W06161 - L0KT0T0 - LM45D9ACMS00001
(parameters, reports) from ACMS or ABDC Applications are

transmitted to the CDAM via the Secured Communication Interfaces
(SCIs).
The HMIs which are used to control the ACMS are:
- The CAPT and F/O Onboard Information Terminals (OITs)
Note that the ACMS can communicate with the operational ground
centers and service providers in order to enable maintenance data
exchanges.
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS ARCHITECTURE - ACMS GENERAL ARCHITECTURE

ACMS Architecture (continued)
ACMS Detailed Architecture
The ACMS 1 (2) Applications are fully redundant and are hosted in
ANSU-OPS 1 (2). The applications are activated only on one ANSU
but the database are uploaded on both ANSUs mass memory all the
time. Then a synchronization ensures the consistency between the
two ANSUs shared database. If an ACMS Application stops running,
the other ACMS Application has to be launched on the other ANSU.
(ARU-OPS) 2
There are nine PMAT plugs connected to the Secure Interface Router
Unit (SIRU)
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS ARCHITECTURE - ACMS DETAILED ARCHITECTURE

CDAM Description
- generation of reports (Airbus defined or Airline programmed)
- generation of Smart Access Recorder (SAR) and Digital ACMS
Recorder (DAR) files
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS ARCHITECTURE - CDAM DESCRIPTION

Data Recording
The ACMS Application does a post-processing of data acquired from
the CDAM. It acquires the following data from the CDAM:
- real-time parameters
- Airbus or airline reports
- The SAR and DAR files
From this data, the ACMS Applications do:
- the display of real-time parameters
- the report files management
- the SAR and DAR files management
In addition, the ACMS Application manages the storage of this data:
- ACMS reports are stored in a dedicated area in the shared database
- SAR Files are also stored in the shared database
- DAR files can be stored either in the DAR directly from the CDAM,
or in the virtual DAR (VDAR) in the shared database, via the VDAR
Application
Note that all this data can also be printed or sent to the ground.
Moreover, the RSA data, acquired by the ABDC Application, can be
stored in a dedicated area in the shared database before transmission
L1W06161 - L0KT0T0 - LM45D9ACMS00001
to other NSS Applications.
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS ARCHITECTURE - DATA RECORDING

ACMS Reports Description
ACMS Reports
The ACMS can generate two kinds of reports:
- Airbus defined reports: Standard reports
- Airlines programmed reports: Airline Reports
About 100 reports can be generated by the ACMS:
- 30 already predefined by Airbus
15 for each type of engine
about 10 for system reports
- up to 64 airline programmable reports
Standard reports have only limited customization capability (threshold
adjustment).
Airline engineering is also able to program SAR and DAR content
and trigger logic.
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS REPORTS DESCRIPTION - ACMS REPORTS

ACMS Reports Description (continued)
ACMS Reports Layout
An ACMS report is divided in two main parts:
- a permanent standard header part which indicates the report
identification (it is a header)
- a data part dedicated to the report content
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS REPORTS DESCRIPTION - ACMS REPORTS LAYOUT

ACMS Reports Description (continued)
ACMS Reports Manual Trigger
An ACMS Remote trigger button is installed in the center pedestal
(1116VU). If activated by the flight crew this button triggers
predefined reports for post flight investigation depending on the flight
phase.
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS REPORTS DESCRIPTION - ACMS REPORTS MANUAL TRIGGER

ACMS Reports and Data Retrieval
L1W06161 - L0KT0T0 - LM45D9ACMS00001
L1W06161 - L0KT0T0 - LM45D9ACMS00001
ACMS REPORTS AND DATA RETRIEVAL
AIRCRAFT CONDITION MONITORING SYS HMI DESC. (3)

OMS Utilities Menu Screen
When you click on the "Utilities" Menu, you can get access to the
following functions:
- the Real-time Monitoring
- the Data Recording
- the Condition Monitoring
These functions are detailed in the Aircraft Condition Monitoring system
(ACMS) Application chapter.
L1W06161 - L0KT0T0 - LM45DAACMSHMI01
MAINTENANCE COURSE - T1 & T2 (RR / Metric) AIRCRAFT CONDITION MONITORING SYS HMI DESC. (3) Apr 18, 2006
OMS UTILITIES MENU SCREEN

Real Time Monitoring Screen
The ACMS Real-Time Monitoring function can be accessed from the
"Utilities" Menu, and lets select and monitor A/C parameters in real time
either through numerical or through graphical way for trend monitoring.
Note that it is possible to display and monitor several parameters at the
same time.
REAL TIME MONITORING SCREEN

Data Recording Screen
When you select the ACMS Data Recording function from the "Utilities"
Menu, you can get access to:
- stored SAR files
- manual SAR control function
DATA RECORDING SCREEN

Condition Monitoring Screen
When you select the ACMS Condition Monitoring function from the
"Utilities" Menu, you can get access to the following functions:
- Generated and stored reports
- Manual report generation
- Report reprogramming
CONDITION MONITORING SCREEN
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 - ATA 45 Onboard Maintenance System

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LEVEL III - ATA 45 Onboard Maintenance System

Caricato da

Copyright:

Formati disponibili

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 - ATA 45 ONBOARD MAINTENANCE SYSTEM

ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

by right-OMS functions hosted in the Open World Diode (OWD) right

ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

ONBOARD MAINTENANCE SYSTEM DESCRIPTION (3)

OMS AIR-GROUND DATALINK CAPABILITIES

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OPEN WORLD SHELL LOGIN SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HOME PAGE AND MAIN FUNCTIONS SCREENS

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

presented in other dedicated chapters. In this chapter, we will focus on

OMS TOOLS MENU SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS TOOLS MENU SCREEN - AOC APPLICATION SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS TOOLS MENU SCREEN - REFUEL APPLICATION SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS TOOLS MENU SCREEN - PDCS APPLICATION SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS DATA MENU SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS DOCUMENTS MENU SCREEN

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS DOCUMENTS MENU SCREEN - FOCT SCREENS

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS DOCUMENTS MENU SCREEN - AIRN@V SCREENS

OMS HUMAN-MACHINE INTERFACE (HMI) DESCRIPTION (3)

OMS UTILITIES MENU SCREEN

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CMS ARCHITECTURE - CMS GENERAL ARCHITECTURE

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CMS ARCHITECTURE - CMS DETAILLED ARCHITECTURE

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

AVIONICS WORLD BITE PHILOSOPHY - STANDARD A AND B BITES

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

AVIONICS WORLD BITE PHILOSOPHY - LRU BITE PHILOSOPHY

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

AVIONICS WORLD BITE PHILOSOPHY - IOM BITE PHILOSOPHY

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

AVIONICS WORLD BITE PHILOSOPHY - CPIOM BITE PHILOSOPHY

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

- the ANSU-OPS itself

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

CMS CORRELATION - FAULT CODE DESCRIPTION

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)

warning and caution, flag and advisory) in order to determine the

CMS CORRELATION - MALFUNCTIONS/DOCUMENTATION CORRELATION

CENTRAL MAINTENANCE SYSTEM DESCRIPTION (3)