Ata 45 Central Maintenance System

ATA 45 CENTRAL MAINTENANCE SYSTEM
Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only
45.10 GENERAL Presentation
The Centralized Maintenance System (CMS) groups the maintenance of the avionic suite (AVS) and the maintenance systems of other aircraft
systems (A/C systems).
- The Avionic Suite (AVS) maintenance function is managed by the Centralized Maintenance Application (CMA ) of CAC.
- The maintenance function of the other aircraft systems is managed by the Data Management Unit (DMU) software part of the Multi-Purpose
Computer (MPC).
The DMU manages also:
- MFC maintenance function
- EEC maintenance function (Engine)
- PEC maintenance function (Propeller)
MW45.10_.01.G1L1 Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only Page 2
- FCU maintenance function (Fuel)
The CMS allows the maintenance operator to access the following information through a single interface (MCDU):
- Failures detected during the last flight
- Failures currently detected (aircraft on ground)
Note: This access can be performed through both MCDU but not simultaneously
The AVS Maintenance System provides additional features:
- System test and report
- System identification and AVS configuration report
- Class 2 failures report
Note: Failures are classified in two classes depending on the severity of effect on system operation:
- Class 1: Failure with flight deck effects.
- Class 2: Minor failure without flight deck effects.
The maintenance function of the MPC provides additional features:
- display and record various A/C parameters
- Customize various functions
- manage A/C parameters
- report various A/C systems
It is also possible to provide, through ACMS menu, the maintenance functions directly under control of MPC (PEC/EEC, MFC, FCU).
In addition to pilot remarks recorded in the aircraft logbook, the operator can rely on the "LAST FLIGHT REPORT" (in CMC menu) to identify any
warning and caution occurred during the last flight.
This report should be the main point of entry into the maintenance system.
45.10 GENERAL Cockpit Location
The Aircraft Centralized Maintenance System (ACMS) allows the maintenance operator to access information through a single interface, the
Multipurpose Control and Display Unit (MCDU)
45.10 GENERAL Interfaces
The Centralized maintenance system (CMS) fulfills the two followings function:
- Maintenance of new avionic systems (AVS) is managed by the Centralized Maintenance Application (CMA ) of CAC.
- Maintenance of aircraft systems (A/C System) is managed by the Data Management Unit (DMU) software part of the Multi-Purpose Computer
(MPC).
The electrical supply provides power for the Centralized Maintenance System (CMS)
The CMS acquires the current date and time from electronic clocks.
Note: in case of failure from the clocks, the current date and time are provided by the Flight Management System (FMS1 or FMS2), embedded on
Display Unit 2 and 4.
The CMS acquires the AVS configuration from the Flight Data Acquisition embedded on Display Unit.
The CMS exchange several information with A/C systems.
The CMS acquires the CCAS information from the Flight Warning Application (FWA) of CAC and from the MFC.
The CMS dialogue with:
- PCMCIA card
- MCDU (1/2)
- Printer
- ACARS (If installed)
45.10 GENERAL Exercises
MW45.10_.05.E1L1 Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only Page 11
45.11 CENTRAL MAINTENANCE SYSTEM (CMS) System Description
The Centralized maintenance Application (CMA) purpose is to offer to the maintenance operator a set of services via MCDU pages (through MPC).
It make a diagnostic that permits to identify as clearly as possible the root cause of a problem occurred in the avionics system.
These services are:
- Display of configuration report
- Display failures reports (current failures and historic)
- Possibility to initiate interactive tests
The CMA is activated in the CPM1 of the Core Avionic Cabinet 1 only (CAC1).
Note: it is also hosted in CAC 2 but not activated.
The side is established through a pin programming.
MW45.11_.01.S1L1 Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only Page 16
The basic Bite-CMA architecture is a direct connection between the CMA and the Bite part of the system.
However, the diversity of LRU BITE technology and the general AVS architecture constraints lead to implement 5 other kinds of architecture.
The CMA is interfaced with the MPC to:

- acquire the flight phase
- send alert computed by the FWA to the MPC
- transmit MCDU pages and receive operator commands.
The CMA acquires the current date and time according to the following priority:
- Electronic clock 1,
- Electronic clock 2,
- FMS 1,
- FMS 2.
The CMA acquires the AVS configuration (AVS equipment installed or not and aircraft version) from the Flight Display Application (FDA) of DUs.
From the flight phase (managed by MPC), the CMA computes the maintenance phase.
The maintenance phase is used to:
- Establish the CMA operational mode,
- manage leg reports.
The CMA can operate in two modes, the "normal" mode while the aircraft maintenance phase is "flight" and the "interactive" mode while the aircraft
maintenance phase is "ground".
In normal mode, the CMA performs:
- Collection and transmission of maintenance data resulting from system monitoring.
- Storage of failure in Non Volatile Memory (NVM).
- Construction of LAST LEG report, PREVIOUS LEGS report, and MAINT reports.
In interactive mode, the CMA performs:

- Interaction with operator through MCDU
- Construction of a report containing Avionic options and A/C configuration
- Construction of an Avionics status report
- Interactive tests
- AVS alarm transmission.
The CMA failures are classified in two classes depending on the system operation effects severity:
- Class 1: Failure with flight deck effects which prevent continued system operation and classified as critical (highest class).
- Class 2: Minor failure without flight deck effects classified as non critical (lowest class).
It will only require deferred maintenance.
The Class 1 failure can be of 2 kind:
- Internal failures: failures related to a part of a system and reported by this one (memory failure for instance)
- External failures: also called interface failures, these failures are reported by a system that do not "see" another one.
For instance system A receives data from system B through an A429 bus.
If B fails or if the bus is disconnected, system A will report an external failure accusing the interface with system B.
Through an ATA data base associated to each equipment and each system, CMA failures are classified with an ATA chapter code.
In order to reduce the amount of failure reported by the maintenance system and also to avoid spurious failures detection, the CMA performs 3
different calculations in the following order:
Calculation 1:
The CMA correlates AVS component failure with their electrical power bus bars status by using electrical distribution network design. A reported
failure accusing an AVS component not powered due to a bus bar failure will be filtered and will not appear in the different reports.
Calculation 2:
The CMA uses data from the AVS configuration file to prevent the display of failures messages accusing LRU not fitted on the aircraft.
Calculation 3:
The CMA uses an ATA based correlation algorithm to identify as far as possible the root failure.
The principle is the following, a first failure is associated to a correlation window and a timeout of 1 minute.
When a new failure occurs following a previous one, the CMA determines if both failures can be correlated together.
Their ATA code are compared.
- If no correlation is possible (different ATA codes) a new correlation window associated to the failure is opened for 1 minute.
- If a correlation is possible (same ATA code) the failure is considered as induced by the initial failure and does not appear in the different
reports.
When maintenance phase is "flight", both class 1 and 2 failures selected by the correlation process are stored in a None Volatile Memory (NVM).
The CMA can store up to 300 class 1 failures occurred during the last 63 legs and up to 50 class 1 occurred during the last leg.
The CMA can store up to 300 class 2 failures occurred during the last 64 legs.
The NVM is managed in order to:
- offer the possibility to store at least one message for each subsystem
- replace oldest failures by the newest ones, if the maximum storage capacity is detected during the leg.
- prevent redundant failure storage within a given leg.
- store the date, time and ATA code of concerned system for each failure.
- Make a fault data copy in the PCMCIA card or through the printer
The MCDU AVS menu provides several services to the maintenance operator.
45.11 CENTRAL MAINTENANCE SYSTEM (CMS) System Operation
Access to the AVS maintenance main menu is done through the ACMS key on the MCDU main menu and than by the AVS key.
AVIONICS STATUS:
The AVIONICS STATUS report provides the list of AVS LRU affected by at least one internal failure detected during maintenance phase "ground"
(in real time).
The LRU list is displayed from class 1 failure first then class 2 failures
Note: If no failure is detected "NO FAULT REPORTED" is displayed.
LAST LEG REPORT:
The LAST LEG report provides AVS Class 1 failures stored in None Volatile Memory (NVM) that occurred during the last leg when maintenance
phase was "flight" (up to 50 failures).
PREVIOUS LEG REPORT:
The PREVIOUS LEG report displays Class 1 failures from AVS, stored in NVM, and occurred during the previous 63 legs when maintenance
phase was "Flight" (up to 300 failures).
SYSTEM REPORT / TEST:
The selection of SYSTEM REPORT / TEST item displays the list of all AVS sub system managed by the CMA.
MAINT:
The MAINT report displays Class 2 failures from AVS, stored in NVM, and occurred during the 64 last legs when maintenance phase was "Flight".
LRU IDENT:
The LRU IDENT report enables to display the Part Number (Hardware and Software) of fitted LRU (CAC's and DU's) .
The first page provides the list of AVS LRU family.
This layout allows an easy comparison and a check of LRU data in case of LRU replacement or dataloading.
AVS AND A/C OPT CONF:
This report provides the list of AVS and aircraft option with their current status.
AVS Sub-System main menu:
The AVS sub-system main menu provides access to the same services as those proposed on the main AVS page but dedicated to the selected
system.
System Last Test Report:

Main failures messages given in the various reports are of two types:
- RAI (Removal And Installation)
- CHK WRG (CHecK WiRinG)
- RAI
Generally RAI message precise a single FIN (Functional Item Number ) to be replaced.
For example, the "RAI 3WK1" message means the DU2 has encountered a failure and need to be replaced.
This message is also displayed if the software is not appropriate or failed.
- CHK WRG may not be understood as "Check Wiring" between two equipments but indicates an interface issue between one or several emitter
and one receiver. The principle is to indicate only both end of the chain. But any LRU implied in the interface can be the source of the failure.
Software are delivered on 3 CD-ROM with the aircraft.

There is one software for CPM, one for SWM and one for DU.
The CPM and SWM software are loaded via a laptop equipped with the PMAT application and through a direct Ethernet connection to the CAC via
the "CAC Ethernet Bus" plug on 702 VU (this connection is done with an RJ45 type cable).
The DU software is loaded via a Compact Flash card connected on the dedicated DU front face plug. The PMAT application is required to load the
CD-ROM content to the Compact Flash card.
The AVS configuration file is loaded in the AVS via a Compact Flash card plugged in dedicated plug on DU front face (same plug as for
dataloading described above).
45.11 CENTRAL MAINTENANCE SYSTEM (CMS) Exercises
45.11 CENTRAL MAINTENANCE SYSTEM (CMS) Exercises level 2
45.12 CENTRAL MAINTENANCE SYSTEM (CMS) MCDU Description
The maintenance Aircraft System is mainly composed of the Multi Purpose Computer (MPC).
The Data Management Unit (DMU), included in the MPC, is dedicated to the aircraft maintenance.
The DMU has been designed to allow the user to customize the system according to its specific application, requirements, operating environment
and logistics.
Most of the functions are configurable or programmable by GSE (Ground Support Equipment), based on a Laptop.
The GSE software customizes the ACMS function of the DMU part.
Modifications are uploaded through a PCMCIA card.
The purposes of the DMU functions are:
- Management of reports,
- Management of maintenance functions
- MCDU, Printer, ACARS dialogue,
- Intercommunication between CAC1 and MCDU (for avionics system access)
- Aircraft parameters acquisition
- software and database Upload from a PCMCIA interface.
- QAR/DAR/SAR recording
- Management of Alpha Call-up
- Determination of flight mode
The MCDU MPC menu provides several services to the maintenance operator:
45.12 CENTRAL MAINTENANCE SYSTEM (CMS) MCDU Operation
Access to MPC main menu is done through ACMS key on MCDU main menu and than by the MPC key.
MPC PARAM Call-up :

The "MPC PARAM Call-up" menu provides access to call-up parameters.
It allows to display in real time all MPC input data (ARINC, analog, discrete).
ACMS QAR/DAR/SAR:
The "ACMS QAR/DAR/SAR " menu provides access to:
- The QAR PCM menu enables the operator to display the QAR PCM output data and all the data recorded in the QAR.
QAR content is a copy of recorded data in Flight Data Recorder.
ACMS PCMCIA MENU:
This menu provides operator with PCMCIA card data and allows to record QAR/DAR parameters in real time.
MPC REPORT MENU:
This menu gives access to ACMS report pages, mainly dedicated to the customer for reports.
Reports are automatically stored in a NVRAM (None Volatile Random Access Memory) and/or manually in the PCMCIA card.
15 standard reports are predefined and additional reports can be programmed by GSE.
G-METER MENU:
This menu allows to display at the end of each flight a specific report with vertical acceleration values reached during flight and during landing.
This report helps the operator to determine if structural inspections are needed following hard landing or turbulence in flight.
STATUS MENU:
This menu give access to DMU internal BITE data, for trouble shooting purpose.
It is useful to join a print of this menu when computer is sent to a repair shop.
Note: According to the maintenance procedure, select on the selector on the MPC front face to memorize the BITE data when the MPC is
removed.
VERSION:
This menu identify the data versions containing the maintenance messages used for the troubleshooting according to the system Bite.
IDENT MENU
This menu enables to display the various MPC software configuration loaded and to indicate the A/C configuration.
INIT TIME & FLT MENU:
This menu allows to display or initialize date, time and flight number.
INIT PARAM MENU:.
The A/C PARAM INIT page allows the operator to initialize aircraft parameters:
- A/C number
- Engine S/N
- Air valves configuration for ECTM recording.
The ETHERNET PARAM INIT page (Optional).
The PEC/EEC menu provides 8 sub-menus in order to allow operator to read fault code and to proceed the trim procedure of each PEC and EEC.
The MFC Maintenance menu provides 3 sub-menus:
- The Basic Memories and the Flight fault Memory
- The Memory Erasing
- The Copy to the PCMCIA card.
The FCU maintenance menu allows the following functions:
- Display fault codes stored in FCU memories.
- Reset the codes in FCU fault memories.
The CMC menu is used to manage alarm reports coming from the MFC and CAC.
The LAST FLIGHT REPORT page is used to display the last flight alarm report. This report is automatically generated at the end of each flight
after landing.
When an operator request the generation of a GND TEST REPORT, the DMU monitors Master Caution and Master Warning discrete to detect an
alarm. When one of this discrete is activated, associated alarm presents in MFC and CAC are gathered by the DMU and the report is generated.
For Aircraft equipped with ACARS, the DMU is able to manage different functions to:
- Send data via ACARS to the ground (downlink)
- Receive data via ACARS from the ground (uplink)
The ACARS function is used to downlink ACMS reports.
The DMU dialogues with the PRINTER in order to:
- Print of reports,
- Hard copy of MCDU screens.
MCDU screens are stored on PCMCIA disk when the "PRINT" key is pressed, whatever the state of the PRINTER.
45.REV SYSTEM REVISIONS Normal Operation
Access to the AVS maintenance main menu is done through the MCDU.
Select ACMS menu.
Then select AVS menu.
MW45.REV.01.V1L2 Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only Page 52
Select AVIONICS STATUS.

The AVIONICS STATUS report provides the list of AVS LRU affected by at least one internal failure detected during maintenance phase "ground"
(in real time).
The LRU list is displayed from class 1 failure first then class 2 failures.
Select now LAST LEG REPORT menu.
The LAST LEG REPORT provides AVS class 1 failures stored in NVM that occurred during the last leg when maintenance phase was "FLIGHT"
(up to 50 failures).
Select now PREVIOUS LEG REPORT menu.
The PREVIOUS LEG REPORT displays Class 1 failures from AVS, stored in NVM, and occurred during the previous 63 legs when maintenance
phase was "FLIGHT" (up to 300 failures).
Select now SYSTEM REPORT/TEST menu.
The SYSTEM REPORT TEST displays the list of all AVS sub system managed by the Centralized Maintenance Application.
The AVS sub-system main menu provides access to the same services as those proposed on the main AVS page but dedicated to the selected
system.
Select now MAINT menu.
The MAINTENANCE report displays Class 2 failures from AVS, stored in NVM and occurred during the 64 last legs when maintenance phase was
"FLIGHT".
Select now LRU IDENT menu.
The LRU IDENT report enable to display the Part Number (Hardware and Software) of fitted LRU (CAC and DU).
Select now AVS AND A/C OPT CONF menu.
This report provides the list of AVS and A/C option with their current status.
The "LAST LEG REPORT" gives two types of message:

- Removal And Installation (RAI) which precise a single Functional Item Number (FIN) to be replaced. This message is also displayed if the
software is not appropriate or failed.
- Check Wiring (CHK WRG) which indicates an interface issue between one or several emitter and one receiver (CHK WRG may not be
understood as "CHECK WIRING" between two equipments).
Software are delivered on 3 CD-ROM with the A/C. There is one software for CPM, one for SWM and one for Display Unit.
The CPM and SWM software are loaded via a laptop equipped with the PMAT application and through a direct Ethernet connection to the CAC via
the "CAC ETHERNET BUS" plug on 702 VU.
The DU software is loaded via a Compact Flash card connected on the dedicated DU front face plug. The "PMAT" application is required to load
the CD-ROM content to the Compact Flash card.
The AVS configuration file is loaded in the AVS via a Compact Flash Card on the same plug.
END OF PROCEDURE OF AVS
Access to the MPC maintenance main menu is done through the MCDU.
Select ACMS menu.
Select MPC menu.
Select PARAM Call-up menu.

The "MPC PARAM Call-up" menu allows to displays in real time all MPC input data (ARINC, analog, discrete).
Select now the QAR/DAR/SAR RECORDING menu.
The ACMS QAR/DAR/SAR menu provides access to display the QAR/DAR output data in real time and recording capability.
Select now the PCMCIA menu.
The PCMCIA menu provides operator with PCMCIA card data and allows to record QAR/DAR parameters in real time.
Select now the REPORTS menu.
The REPORTS menu gives access to ACMS report pages, mainly dedicated to the customers for reports. Reports are automatically stored in a
NVRAM and/or manually in the PCMCIA card.
Select now the G-METER menu.
The G-METER menu allows to display at the end of each flight a specific report with vertical acceleration values reached during flight and during
landing. This reports helps the operator to determine if structural inspections are needed following hard landing or turbulence in flight.
Select now the STATUS menu.
The STATUS menu give access to DMU internal BITE data, for trouble shooting purpose. It is useful to join a print of this menu when computer is
sent to a repair shop.
Select now the VERSION menu.
The VERSION menu identify the data versions containing the maintenance messages used for troubleshooting according to the system bite.
Select now the IDENT menu.
The IDENT menu displays the various MPC software configuration loaded and indicates the A/C configuration.
Select now the INIT TIME & FLIGHT menu.
The INIT TIME & FLT menu allows to display or initialize date, time and flight number.
Select now the INIT PARAM menu.
The INIT PARAM menu allows to the operator to initialize aircraft parameters (A/C number, Engine S/N, Air valves configuration for ECTM
recording).
The PEC/EEC page is accessible from the ACMS page.

Select PEC/EEC menu.
The PEC/EEC menu provides 8 sub-menus in order to allow operator to read fault code
and to proceed the trim procedure of each PEC and EEC.
Now, select MFC menu.
The MFC Maintenance menu provides 3 sub-menus:
- The BASIC MEMORY menu gives access to MFC fault codes stored since the last erase (no chronological information)
- The FLT FAULT MEMORY menu gives access to MFC fault codes which occurred during the 9 previous flight.
- The MAINT MEMORY ERASING menu allows the operator to erase the MFC basic memory or MFC flight memory.
Note: The MFC maintenance indicator on F/O maintenance panel (702VU) must be erased manually.
- The "* COPY TO PCMCIA" tab allows to download all faults data from MFC and copy these faults on the PCMCIA disk.
Select this menu.
Now select the FCU menu
The FCU maintenance menu allows to display fault codes stored in Fuel Control Unit memories and to reset these codes.
Select now the CMC menu.
The CMC menu is used to manage alarm reports coming from MFC and CAC.
The "LAST FLIGHT REPORT" page is used to display the last flight alarm report. This report is automatically generated at the end of each flight
after landing.
When a operator request the generation of a GND TEST REPORT, the DMU monitors Master Caution and Master Warning discrete to detect an
alarm. When one of this discrete is activated, associated alarm presents in MFC and CAC are gathered by the DMU and the report is generated.
For aircraft equipped with ACARS, the DMU is able to manage different functions to:
- Send data via ACARS to the ground (downlink)
- Receive data via ACARS from the ground (uplink)
The ACARS function is used to downlink ACMS reports.
The DMU dialogues with the PRINTER in order to:
- Print of reports,
- Hard copy of MCDU screens.
MCDU screens are stored on PCMCIA disk when the "PRINT" key is pressed, whatever the state of the PRINTER.
END OF PROCEDURE OF DMU
Table of contents
45.10 GENERAL .............................................................................................................................................................................................................................................................

2
Presentation .............................................................................................................................................................................................................................................................
2
Cockpit Location ......................................................................................................................................................................................................................................................

7
Interfaces ................................................................................................................................................................................................................................................................
8
Exercises ................................................................................................................................................................................................................................................................
11
45.11 CENTRAL MAINTENANCE SYSTEM (CMS) .......................................................................................................................................................................................................

16
System Description ..................................................................................................................................................................................................................................................

16
System Operation ....................................................................................................................................................................................................................................................

28
Exercises ................................................................................................................................................................................................................................................................
34
Exercises level 2 ......................................................................................................................................................................................................................................................

36
45.12 CENTRAL MAINTENANCE SYSTEM (CMS) .......................................................................................................................................................................................................

38
MCDU Description ...................................................................................................................................................................................................................................................

38
MCDU Operation .....................................................................................................................................................................................................................................................

41
Exercises ................................................................................................................................................................................................................................................................
48
Exercises level 2 ......................................................................................................................................................................................................................................................

50
45.REV SYSTEM REVISIONS .......................................................................................................................................................................................................................................

52
Normal Operation .....................................................................................................................................................................................................................................................

52
Copyright © 2011-2012 - ATR Training Centre - All right reserved For Training Only

Ata 45 Central Maintenance System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ata 45 Central Maintenance System

Uploaded by

Copyright:

Available Formats

ATA 45 CENTRAL MAINTENANCE SYSTEM

The CMA is interfaced with the MPC to:

In interactive mode, the CMA performs:

System Last Test Report:

Software are delivered on 3 CD-ROM with the aircraft.

MPC PARAM Call-up :

Select AVIONICS STATUS.

The "LAST LEG REPORT" gives two types of message:

Select PARAM Call-up menu.

The PEC/EEC page is accessible from the ACMS page.

45.10 GENERAL .............................................................................................................................................................................................................................................................

Cockpit Location ......................................................................................................................................................................................................................................................

45.11 CENTRAL MAINTENANCE SYSTEM (CMS) .......................................................................................................................................................................................................

System Description ..................................................................................................................................................................................................................................................

System Operation ....................................................................................................................................................................................................................................................

Exercises level 2 ......................................................................................................................................................................................................................................................

45.12 CENTRAL MAINTENANCE SYSTEM (CMS) .......................................................................................................................................................................................................

MCDU Description ...................................................................................................................................................................................................................................................

MCDU Operation .....................................................................................................................................................................................................................................................

Exercises level 2 ......................................................................................................................................................................................................................................................

45.REV SYSTEM REVISIONS .......................................................................................................................................................................................................................................

Normal Operation .....................................................................................................................................................................................................................................................

You might also like