• No results found

LEVEL I - ATA 45 Onboard Maintenance System

N/A
N/A
Protected

Academic year: 2021

Share "LEVEL I - ATA 45 Onboard Maintenance System"

Copied!
40
0
0

Loading.... (view fulltext now)

Full text

(1)

 A380 

 TECHNICAL TRAINING MANUAL 

 MAINTENANCE COURSE - T1 & T2 (RR / Metric) 

 LEVEL I - ATA 45 Onboard Maintenance System 

(2)
(3)

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,

(4)
(5)

LEVEL I - ATA 45 ONBOARD MAINTENANCE SYSTEM

Onboard Maintenance System Introduction (1) . . . . 2

Central Maintenance System Presentation (1) . . . . 6

Data Loading and Configuration System Pres. (1) . . . . 16

Aircraft Condition Monitoring System Pres. (1) . . . . 24

Onboard Maintenance System Maintenance (1) . . . . 32

(6)

General

The Onboard Maintenance System (OMS) is designed to support line and hangar maintenance activities, and engineering follow-up. The OMS is composed of three sub-systems:

- The Central Maintenance System (CMS)

- The Data Loading and Configuration System (DLCS) - The Aircraft Condition Monitoring System (ACMS)

(7)

GENERAL

(8)

OMS Functions

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

(9)

OMS FUNCTIONS

(10)

General

The Central Maintenance System (CMS) is part of the Onboard Maintenance System (OMS), hosted in Network Server System (NSS), in the Open World. The CMS is a system devoted to the centralization of operational and maintenance data associated to both Avionics and some Network Server Systems (NSS) failures. Note that the CMS receives this data from Avionics systems through the Secure Communication Interfaces (SCIs), and directly from Open World systems. The CMS can be operated through several NSS Human Machine Interfaces (HMIs). It can also communicate with operational ground centers and service providers for the exchange of maintenance data upon airline requests.

(11)

GENERAL

(12)

CMS Functions

The CMS operates in two modes, a normal mode and an interactive mode. The functions performed in normal mode are, the:

- systems continuous monitoring, - failure, identification and correlation

- centralization of failures events and parameters sent by the BITEs - report generation

The interactive mode basically enables: - access to e-Logbook, AirN@V and MEL - interactive system tests

- access to system monitoring - access to servicing reports - access to maintenance history

The interactive mode only operates on ground, and always requires an operator action.

Note that all the A/C systems, which have an internal BITE function, are monitored by the CMS.

(13)

CMS FUNCTIONS

(14)

CMS Architecture

Aircraft systems are monitored by:

- The CMS Application which is part of the Avionics Domain

- Right CMS Applications hosted in the Flight Ops and Cabin Domain The CMS Application, hosted in Open World servers, acquires through the SCIs two different types of data from the Avionics World Systems: - Maintenance Data: Systems BITEs

- Operational Data: Warnings and flight phases from the Flight Warning System (FWS), flags and advisories from the Control and Display System (CDS), and e-logbook defects entered either by the pilots or by the cabin crew

Note that these servers also contain other applications dedicated to facilitate maintenance activities (AirN@v, E-Logbook), and also databases to store all maintenance parameters acquired from the Avionics World. The HMIs, which are used to control the CMS, are:

- The CAPT and F/O Onboard Information Terminals (OITs) and their associated keyboards

- The Onboard Maintenance Terminal (OMT)

- The Portable Multipurpose Access Terminal (PMAT) - The Printer 1 (for maintenance reports)

The Right CMS Applications are also hosted in Open World servers, and acquire from the Open World Diode right side connected systems all maintenance data associated to fault messages. The Right-CMS can also be controlled through the OMT, and the CAPT and F/O OITs and their associated keyboards. The printer 2, if installed, enables to print the Right CMS associated maintenance reports.

Note that the CMS and Right CMS can communicate with the operational ground centers and service providers in order to enable maintenance data exchanges.

(15)

CMS ARCHITECTURE

(16)

BITE Philosophy

A system is composed of Line Replaceable Unit (LRUs), which can be: - computers

- sensors - probes

- actuators, etc...

Most of the A/C LRUs are permanently monitored in order to improve the safety and to reduce operation and maintenance costs.

To do that, a failure detection function called Built In Test Equipment (BITE), is integrated in the concerned system. The BITE function performs a permanent system monitoring. It permanently monitors: - the internal functions, components and operation of the system - Inputs / outputs

- Links with other systems

If a failure occurs, the BITE function assumes: - the fault detection

- the fault isolation

- the fault memorization in a non-volatile memory

The BITE information is then sent to the CMS Applications hosted in the Network Server System (NSS). This information enables the CMS to monitor and to detect the systems failures.

Note that it is also possible to initiate manual tests from the CMS in order to interrogate the systems on particular components or function status.

(17)

BITE PHILOSOPHY

(18)

HMI CMS Functions

The "Tool" Menu of the Onboard Maintenance system (OMS) home page gives access to the following Central Maintenance System (CMS) functions:

o Post Flight Report o System Report/Test o System Monitoring o History Clear o Engineering o Item Detail

(19)

HMI CMS FUNCTIONS

(20)

General

The Data Loading and Configuration System (DLCS) is part of the Onboard Maintenance System (OMS), hosted in Network Server System (NSS), in the Open World. The DLCS is composed of four functions, the:

- Data Loading function

- Repository management function - Configuration reporting function - Software Pin Programming function

Note that the DLCS communicates with the Avionics systems through the Secure Communication Interfaces (SCIs), and directly with Open World Systems. The DLCS can be operated through several NSS Human Machine Interfaces (HMIs).

It can also communicate with airline operational ground centers and service providers for the export of configuration data upon airline request.

(21)

GENERAL

(22)

DLCS Functions

The DLCS is composed of four functions, the: - Data Loading function

- Repository management - Aircraft Configuration function - Software Pin Programming function Data Loading function

The Data Loading function manages: - The upload of a software

- The downloading operations Configuration Management function

The Configuration Management function enables: - To compare two configurations of the aircraft - To access configuration history

- To access current aircraft configuration - To customize configuration names

Pre-requisite: note that the Configuration management and control will remain an Airline Responsibility

Repository Management function

The Repository Management function, which enables: - The upload 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

Software Pin Programming Function

The Software Pin Programming to display and to perform the modification of the Software Pin Programming.

(23)

DLCS FUNCTIONS

(24)

DLCS Architecture

Data loading functions are made by:

- The DLCS Application which is part of the Avionics Domain

- Right-DLCS Applications hosted in the Flight Ops and Cabin Domain The DLCS Application, hosted in Open World servers, acquires data from the Line Replaceable Module (LRMs) and the LRUs via the two Secured Communication Interfaces (SCIs). The DLCS Application can communicate with A/C database hosted in the same servers, to store or retrieve any software, and with AirN@v and the E-Logbook 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 associated keyboards

- The Onboard Maintenance Terminal (OMT)

- The Portable Multipurpose Access Terminal (PMAT)

The Right DLCS Applications are also hosted in Open World servers, and manage all activities related to the data loading and the software configuration of Open World Diode right side connected systems. The Right DLCS can also be controlled through the CAPT and F/O Onboard Information Terminals (OITs) and their associated keyboards.

Note that the DLCS and Right DLCS can communicate with the operational ground centers and service providers in order to transmit Configuration Reports.

(25)

DLCS ARCHITECTURE

(26)

HMI DLCS Functions

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

(27)

HMI DLCS FUNCTIONS

(28)

General

The Aircraft Condition Monitoring System (ACMS) is part of the Onboard Maintenance System (OMS), hosted in Network Server System (NSS), in the Open World. The aim of the ACMS is to acquire and process A/C operational data in order to facilitate the preventive maintenance. Note that the ACMS receives this data from Avionics systems through the Centralized Data Aquisition Module (CDAM).

It is also used during troubleshooting procedures, to perform in-depth investigations.

The ACMS can be operated through several NSS Human Machine Interfaces (HMIs).

It can also communicate with airline operational ground centers and service providers for the exchange of maintenance data upon airline requests.

(29)

GENERAL

(30)

ACMS Functions

The ACMS has been designed to achieve three main functions: o A/C systems health monitoring

o Help for troubleshooting

o Data acquisition for NSS Application

First the ACMS performs a permanent A/C systems health monitoring to improve the A/C maintenance efficiency to reduce repairing times and to decrease maintenance costs. To do that, the ACMS:

o Acquires A/C systems parameters o Manages the storage of these parameters

o Performs a real-time systems parameters monitoring o Processes system reports of parameters

o Helps the maintenance crew to anticipate failure and degradations The ACMS is also capable to perform in-depth troubleshooting procedures in order to ease the resolution of technical investigation.

Finally the ACMS is used for the data acquisition and transmission of selected parameters to OPEN WORLD Applications.

(31)

ACMS FUNCTIONS

(32)

ACMS Architecture

The ACMS is mainly composed of a software application hosted in the Avionics Domain, which is part of the NSS.

The ACMS, hosted in Open World servers, acquires data from the LRUs and LRMs located in the Avionics World, through the Centralized Data Acquisition Module (CDAM). Then this data is stored in a dedicated maintenance database hosted in the servers, and are used to generate reports or to enable Real-time parameters display. The servers also contain other applications dedicated to facilitate maintenance activities (AirN@v, E-Logbook).

The data acquired by the CDAM can also be stored in an optional Digital ACMS Recorder (DAR) depending on the airline request.

Note that the communication from the NSS to the CDAM, is made through the Secure Communication Interfaces (SCIs).

The HMIs which is used to control the ACMS are:

- The CAPT and F/O Onboard Information Terminals (OITs) and their associated keyboards

- The Onboard Maintenance Terminal (OMT)

- The Portable Multipurpose Access Terminal (PMAT) - The Printer 1 (for maintenance reports)

Note that ACMS can communicate with the airline operational ground centers and service providers in order to enable maintenance data exchanges.

(33)

ACMS ARCHITECTURE

(34)

ACMS HMI Functions

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.

(35)

ACMS HMI FUNCTIONS

(36)

OMS Safety Items

When you work with the Onboard Maintenance System (OMS), make sure that you obey all the AMM safety precautions. This will prevent to injury persons and/or damage the aircraft. Here is an overview of main safety precautions relative to the OMS.

When you are operating the OMS, and particularly when you perform interactive system tests, you have to be aware that the powerplant systems can be activated and that some mechanical parts can move.

Before any maintenance operations, make sure that all the safety devices and all the warning notices are in position.

For more detailed information, refer to the safety precautions

recommended in the maintenance procedures associated to each aircraft systems.

(37)

OMS SAFETY ITEMS

(38)

OMS Ground Support Equipment

The OMS tasks require some Ground Support Equipment (GSE). As an example, GSEs used for OMS activities are all means, which are used to identify the operator before working with the OMS.

These identifier means may be customizable by the airline (ex: electronic signature, USB key, etc).

Another example of GSE used for OMS activities is the Standalone Identification System (SIS) tool.

This tool, which must be connected directly to the computers, is used to access to the computer identification in terms of equipment and software part numbers. Refer to the illustrated Tool and Equipment Manual (TEM) for the complete list of the tools.

(39)

OMS GROUND SUPPORT EQUIPMENT

(40)

References

Related documents