ACMS System Description - ACMS reports

ATA: 45-31 FIN: 2TU1SW4 Ref: 45.31.00003

A/C Type: A350 A/C Serie: Topic: First Issue 29-JUL-2015
Date:
Part SFI52S0123S0187 Last 11-OCT-
Number: Publication 2017
Date:
Supplier: SAFRAN
ELECTRONICS &
DEFENSE
Linked Articles: ISI 05.51.00019 Linked
ISI 45.31.00007 Documentation:
ISI 46.00.00037
ISI 46.00.00040

[11/10/2017] Addition of the Reports description document for ACMS

standard RR7/FSA4.2.

Purpose of this Article:

Provide with the full description of A350 ACMS reports layouts, contents and
triggering logic.

NOTE: This article is applicable for ACMS RR6.1.1/FSA3.1, ACMS RR6.2/FSA4.1

and ACMS RR7/FSA4.2.

e E gi e C i e Re
e Ai c af C i e Pe f a ce Re
e E gi e C i b Re
e E gi e Ta e ff Re
E gi e Ga Pa h Ad i Re Ab a
e C di i
e E gi e Ga Pa h Ad i Re Li i E ceeda ce
e E gi e Mecha ica Ad i Re
e E gi e S a S a Re
e E gi e Ab a S a Re
e E gi e F igh P fi e Re
e E gi e F igh S a Re
e Th Re e e Re
e Ai c af C i e S abi i S a i ic Re

e APU Ab a Sh d Re
e APU S a MES C d Re
e AGS TCS CPCS Re
e TMR B a e Te
e F igh C EHA Acc a F id Le e Re
e IGGS E e Re
e BAS TEMPERATURE MONITORING REPORT
 e BAS PRESSURE LOCKUP MONITORING REPORT
e Se ici g Re
e BAS WARNINGS REPORT
e TMR BCS a e ea Re
e AFDX Ne Fai e Re
e DSCS

e La di g Gea P i i Se Re
e La di g Gea E e i Re ac i Re
e N e Whee A g e Re
e Sa I eda ce a d Ce e i e e i a e
e CBV TIME MONITORING REPORT
e H d a ic Re Fi e Re
e HPV MONITORING REPORT
e APU LOW B eed P e e
e TMR BCS Acc a Re
e TMR BCS P e La d Te Re
e WIPS

NOTE: This article is available pending the release of the document in AirnavX
My Library on Airbus World portal.

NOTE: The below reports are introduce with release of SB 46-P004 applicable for
ACMS RR7/FSA4.2

e CSAS Re
e RAT Sheddi g Re
e P e i i a F igh L ad Re
e P e i i a La di g L ad Re

You can refer to ISI article 05.51.00019 for detailed description of use of
Preliminary load reports 056 & 057 through SOMF.

Engineering Support
First Issue Date: 29-JUL-2015
Model: Last Publication Date: 11-OCT-2017
Manufacturer:

1. OVERVIEW

The Aircraft Condition Monitoring System (ACMS) is an on-board

maintenance system.
The ACMS collects data to supply the flight crew and maintenance
personnel with performance and trend information about engines and
other aircraft systems.

With the ACMS data, the users can get access to the fault indications in
the aircraft systems before a system failure occurs.
This helps maintenance personnel to do troubleshooting procedures.

2. FUNCTION/DESCRIPTION

The functions of the ACMS are to collect, transmit and store data from
many aircraft systems for maintenance and troubleshooting.

The ACMS applications are the ACMS-Real Time (ACMS-RT) and the
ACMS-Server Application (ACMS-SA).

The ACMS transmits and stores the related data on the ACMS-SA
(reports,recordings, etc.) and/or shows it on the system displays.

The ACMS-SA uses the Avionics Messages Exchanger (AMEX) service

to send the related data to the ground (downlink) or to receive and
manage this data from the ground (uplink).

The ACMS-RT interchanges data with the ACMS-SA through two Secure
Communication Interfaces (SCIs).
The SCIs are an Ethernet gateway between the two ACMS applications.

The Avionics Broadcast Data Collector (ABDC) receives data through

the Avionics Full Duplex Switched Ethernet (AFDX) network.
The ABDC is an application hosted on the Avionics Server Function
Cabinet (ASFC).
The ABDC application receives data and then sends it to other aircraft
component applications from the ASFC which do not have a connection
to the AFDX network.

The ACMS-RT receives aircraft data from many aircraft components.

There are four groups of ACMS parameter displays:

• Airbus standard displays

The Airbus standard displays are the system pages. They also store the
descriptions of alpha call-ups. Alpha call-ups are acronyms which identify
each parameter.

The ACMS system pages are Airbus-approved pages and quickly give
access to the most important serviceable parameters of the aircraft
systems.

• Customer support displays

The customer support displays show specified displays and alpha call-
ups.
Airbus customer support and approved personnel can use the ground
programming tool to set the displays and alpha call-ups in the customer
support database.

• Airline displays
The airline displays show specified displays and alpha call-ups.
Approved maintenance personnel can use the ground programming tool
to set the displays and alpha call-ups in the airline database.

• Onboard programmed displays

The onboard programmed displays show specified displays. Approved
maintenance personnel can use the onboard Human-Machine Interface
(HMI) to set the displays and alpha call-ups.

3. ACMS REPORTS

The ACMS constantly monitors aircraft system & performance

parameters.
If there is an incident, the ACMS reports can help to do an analysis of the
incident and subsequently do the necessary troubleshooting procedures.

The ACMS reports are very important for the aircraft monitoring function,
which collects parameters of pre-specified system conditions (trigger
conditions).
The airline can program ACMS reports to start at different times during
aircraft operation to monitor aircraft performance. But an event which is
unusual automatically starts an ACMS report.
This data might be useful for subsequent troubleshooting procedures.
The ACMS reports use data that comes from many aircraft systems.
Each ACMS report collects specified data and changes this data into a
specified output format.

There are three types of ACMS reports:

• Airbus Standard reports

These reports are Airbus-approved.
They include engine reports and system reports for trend monitoring and
incident analysis.
Also, they include a servicing BITE contextual reports and a
servicing trend-monitoring report.

• AIRBUS Customer-support programmed-reports

AIRBUS approved personnel can change these reports.
They can change a copy of an Airbus ACMS report.
Also, they can create new customer-support programmed-reports and
new triggers.

• Airline programmed reports/modifications

In this type of ACMS report, the user can enable/disable some of the
Airbus ACMS reports.
Approved personnel can also change a copy of the Airbus ACMS report.
And they can make new Airline-support programmed-reports and new
triggers.
It is possible to make temporary changes to reports onboard or to do this
through an uplink from the ground. To do this, use the HMI and an
Aircraft Communication Addressing and Reporting System (ACARS)
upload procedures.
For each different report only one report can be recorded.

3.1 PROGRAMMABLE MONITORING REPORTS

Approved maintenance personnel can use the ground programming tools

to set the programmable monitoring reports. This makes it possible to
change the set of parameters and trigger logics.

3.2 AIRBUS STANDARD REPORTS

The Airbus standard reports supply one or more received or calculated

parameters.
These reports can contain pre-event data.
The Airbus standard reports are:

A. Event Reports:
• <006> - Engine Gas Path Advisory Report - Abnormal
Condition
• <007> - Engine Gas Path Advisory Report - Limit Exceedance
• <008> - Engine Mechanical Advisory Report
• <010> - Engine Abnormal Start Report
• <016> - APU Abnormal Shutdown Report
• <019> - AGS/TCS/CPCS Report
• <032> - Flight Controls EHA Actuators Refilling Report
• <034> - IGGS Event Report
• <038> - BAS Temperature Monitoring Report
• <039> - BAS Pressure Lockup Monitoring Report
• <047> - BAS Warnings Report
• <049> - APU Low Bleed Pressure Report
• <054> - AFDX Network Failures Report
• <055> - DSCS Event Report

B. Trend Monitoring Reports:

• <001> - Engine Cruise Report
• <002> - Aircraft Cruise Performance Report
• <003> - Engine Climb Report
• <004> - Engine Takeoff Report
• <009> - Engine Start Summary Report
• <012> - Engine Flight Profile Report
• <013> - Engine Flight Summary Report
• <014> - Thrust Reverser Report
• <015> - Aircraft Cruise Stability Statistic Report
• <017> - APU Start/MES/Cool Down Report
• <018> - Landing Gear Proximity Sensors Report
• <020> - Landing Gear Extension/Retraction Report
• <023> - LGMS Brake Monitoring Report
• <024> - Nose Wheel Steering Report
• <036> - Salt Impedance and Centre Wire Resistant Report
• <037> - CBV Time Monitoring Report
• <040> - Servicing Report
• <043> - Hydraulic Return Filter Report
• <046> - HPV Monitoring Report
• <051> - BCS Valve Wear Report
• <052> - BCS Accumulator Report
• <053> - BCS Pre-Land Test Report

C. Bite Contextual Reports:

• <130> - WIPS BITE Contextual Report.

NOTE: The automatic trigger of this report is not available

on this standard.

3.3 TREND MONITORING REPORTS

The trend monitoring reports are reports used for preventive

maintenance. They have a set of parameters which are always
recorded at the same point in time during flight or during system
operation. The analysis of these reports after flight gives a report of the
system condition and system failures that will possibly occur in the
future.

3.4 EVENT REPORTS

If an incident occurs, an ACMS logic starts an event report. The event

report gives records and stores other data which can help to make an
analysis of the incident.

3.5 REPORT DEFINITION

3.5.1 Types of Reports

There are two different types of reports:

• Routine reports
• On-event reports.
The difference refers to the logic elements of trigger codes 4000
and up.
The routine reports start in normal condition regularly.
The on-event reports only start when pre-defined abnormal
conditions occur.

3.5.2 Report Generation Cycle

The procedure for the generation of a report has different steps

which are in a specified sequence.
These steps occur in this sequence:

3.5.2.1Report triggering

A trigger condition is a pre-defined logical condition on

engine and/or aircraft parameters. When a trigger condition
is identified, the system opens a report and starts to collect
specified data.
When the report creation conditions are fulfilled, the system closes the
report and makes the data available.

3.5.2.2Data acquisition

Specified sets of engine and aircraft parameters are acquired

according to pre-defined logics.

3.5.2.3Abort condition

If some pre-defined conditions occur while the report logics

are in operation, the generation of the report is stopped. The
recorded data is discarded and the ACMS does not generate
the report.

3.5.2.4Report generation

This is the moment when all data necessary for a report is

collected and the report is closed and stored on the server
application. Some additional conditions can be necessary
to generate the report.

3.5.2.5Report Layout

After report generation, it is possible to send the report to

the ground for analysis. Also you can see the report on the
on-board HMI.

3.5.3 Report Trigger Definition

A unique trigger code, which shows the particular trigger

conditions, is given to each generated ACMS report.
A trigger code has 4 digits.

3.5.3.1First digit

The first digit identifies the general category of the trigger logic:
• Code 1xxx: manual request on the HMI
• Code 2xxx: manual request on the ACMS trigger button
• Codes 4xxx: and up: Airbus standard trigger logics

3.5.3.2Second digit

The second digit of the trigger code has these:

• Trigger code 1xxx:

When triggered with ACARS request, the second digit is ’9’
(19xx). If not, it is ’0’ (10xx).

• Trigger code 2xxx:

The second digit of trigger code 2xxx is always ’0’ (20xx).

• Trigger codes 4xxx and up:

The second digit of Trigger codes 4xxx and up give sub-categories of the
trigger conditions.
The second digit is ’8’ when the report comes after a manual HMI
request.
The second digit is ’9’ when the report comes after an ACARS request.

3.5.3.3Third digit

The third digit agrees with the component or distinction of

cases that triggered the report.

3.5.3.4Fourth digit

The fourth digit of the trigger code has these:

• Trigger codes 1xxx and 2xxx:

Usually, the fourth digit of trigger codes 1xxx and 2xxx is ’0’.

• Trigger codes 4xxx and up:

The fourth digits a counter for reports triggered in a sequence.

3.5.4 Report Trigger Conditions

A trigger condition is a pre-defined logical condition which uses

engine and/or aircraft parameters.
When a trigger condition is identified, the system opens a report and
starts to collect specified data.
When the report creation conditions are fulfilled, the system closes the
report and makes the data available.
 3.5.5 Manual and ACARS Requests

A report can start as a result of a manual request, on-board (HMI

or ACMS trigger button) or on the ground, after an ACARS uplink.
It is possible to trigger a report as a result of an on-board or ACARS
request although the maximum number of reports per flight leg is
reached for the related report.

3.5.6 Data Acquisition

There are three types of parameters which are used for ACMS
reports:

• Snapshot parameters
• Average values
• Parameters calculated by the ACMS in relation with the aircraft
parameters.

Parameters acquired according to the same logic are grouped into

parameter sets.

3.5.6.1Snapshot parameters

Only one value of each parameter is recorded.

All parameter values of a "snapshot" parameter set are recorded one
second after the trigger event for that parameter set.

3.5.6.2Average values

The recorded parameter value is an average, which is calculated over a

specified period of time.
The samples, which are used to calculate the average value of a
parameter, are acquired at a specified rate.
The average value is invalid if more than 1/5 of the collected samples are
invalid.

3.5.7 Report Generation

A trigger condition is not fulfilled when a parameter which is necessary to

define this trigger condition is not available or is invalid.

3.5.7.1Maximum number of ACMS reports

The maximum number of ACMS reports is:

• The maximum number of reports that can be stored on the ASFC

• Programmed individually for each ACMS report
• Independent of the trigger codes
• Re-programmable.
For each ACMS report, the maximum number of the related ACMS
reports is for all instances and all trigger codes.

You can also refer ISI article ref '45.31.00002' for additional information
on this subject

3.5.7.2Report generation frequency

The report generation frequency:

The reports are generated upon specific triggering condition for each
report.
Some constant limits can be customized; as such, number/frequency of
generated reports can be reduced or increased.
Customization through OMS/OMT remains applicable for maximum 99
legs or 99 days.

3.5.7.3Maximum number of reports per flight leg

The maximum number of reports per flight leg:

• Agrees with the maximum number of times a given report can be

generated during a single flight leg
• Is programmed individually for each ACMS report
• Is re-programmable for all ACMS reports to any value between "every
flight leg" and "every 100 flight legs".

3.5.7.4Report abort condition

If applicable, the abort is defined individually for each report

instance.

3.5.8 Definition of generally-calculated parameters

The ACMS calculates the following parameters:

• Aircraft type - ACTYP
• Engine type - ENG
• Flight Phase - FP
• Flight leg
• Rejected Takeoff identification - REJTO
• Bleed Status – BLDSTATUS*
• Hexadecimal words
• Cross Bleed Valve Status - CBV
• APU Bleed Valve Status - APUBV
• Flight Leg Counter - FLTCNTxxx (xxx shows the number of the
ACMS report)
• Report Triggering Indicator - TRGxxx (xxx shows the number of
the ACMS report).
*Bleed Status (BLDSTATUS)
The Bleed Status word is a series of digits reflecting bleed extraction from the
engines.

The Bleed Status word contains the following series of digits:

A350 A350 Parameter Descri Format source True/Fal

Parameter ption se
(Alpha call
up)
HPVPOS.1 BAS_HPV_POSITION_CLOSED_1 HPV1 1 BAS CLSD/O
(High PEN
Pressure
Valve)
MPVPOS.1 BAS_MPV_POSITION_CLOSED_1 MPV1 1 BAS CLSD/O
(Manifo PEN
ld
Pressure
Valve)
NAI.1 NAI_CTL_SIGx_NAI1 Nacelle 1 AICF ON/OFF
Anti-ice
position
engine 1
WAI.L WIPS_CTL_VLV_LEFT_POS WIPS 1 WIPS ON/OFF
CTL
Left
Valve
Pos
PACKF.1 PACK1_Absolute_Flow PACK1 9.99 AGS
_Absolu
te_Flow
C000_CBV C000_CBV CBV 1 ACMS OPEN/C
position LSD
PACKF.2 PACK2_Absolute_Flow PACK2 9.99 AGS
_Absolu
te_Flow
WAI.R WIPS_CTL_VLV_RIGHT_POS WIPS 1 WIPS ON/OFF
CTL
Right
Valve
Pos
NAI.2 NAI_CTL_SIGx_NAI2 Nacelle 1 AICF ON/OFF
Anti-ice
position
engine 2
HPVPOS.2 BAS_HPV_POSITION_CLOSED_2 HPV2 1 BAS CLSD/O
(High PEN
Pressure
Valve)
MPVPOS.2 BAS_MPV_POSITION_CLOSED_2 MPV2 1 BAS CLSD/O
(Manifo PEN
ld
Pressure
Valve)
C000_APUBV C000_APUBV APU 1 ACMS OPEN/C
Bleed LSD
Valve
Position
These parameters correspond respectively to the below digits:

A 1 1 B L D S T A T U S : 1 1 1 1 9 . 9 9 1 9 . 9 9 1 1 1 1 1

3.5.8.1Flight phase detection

There are two types of flight phases:

• The phases identified by the Flight Warning System (FWS)

• The ACMS flight phases

The FWS Flight Phases (FPFWS) are received through the AFDX
network. The ACMS Flight Phases (FP) are internal parameters.
The flight phases that are used in the report specifications are
the ACMS flight phases. These are based on the FPFWS and some
additional logic.

Table 1: ACMS Flight Phases

When the flight phase information from the FWS is not available or is
invalid, the last valid flight phase is used.
If no "last valid" value is available, the default value FP = 1 is used.

A new flight leg starts when the ACMS shows a change from:
• FP = 13 to FP = 1
• FP = 13 to FP = 1.1
• FP = 13 to FP = 2
• FP = 12 to FP = 2
• FP = 11 to FP =2
• FP = 2 to FP = 1.

4. REPORT SPECIFICATIONS

4.1 ALPHA CALL-UPS

Alpha call-ups are acronyms used to identify the parameters necessary

to define the reports.

4.2 REPORTS SPECIFICATION FORMAT

4.2.1 Report Objective

This part gives a short overview of the aim of the report. It also indicates
the type of data acquired, acquisition logic and where you can use the
report

4.2.2 General Report Information

This section shows the number of instances and the trigger codes.
A report instance gives some default settings of the report. These
settings are:

• Report trigger condition

• Parameter set acquisition logic
• Report generation condition.

4.2.3 Report Instances

4.2.3.1Manual instance

Report instances triggered manually are optional. If applicable, this

instance will always contain the same set of trigger activations: manual
HMI selection, uplink request and ACMS trigger button.
No abort condition and no event detections are available for manual
instances.

4.2.3.2Routine instance

One basic trigger code is defined. If applicable, an abort condition and

some event detection trigger codes are defined.

4.2.3.3Event instance

All the Trigger codes that can trigger an instance are defined.
If applicable, an abort condition is defined.

4.2.4 Internal Limits and Constants

The table included in this paragraph shows all the parameters

that are used only for the specified report. These parameters are
typically numeric limits and time intervals.
The table contains these columns:

• Description – short description of the parameter

• Parameter – name of the internal variable
• Units – units of the parameter value
• Type – type of the parameter (Boolean, float, integer)
• Range – allowed range when reprogramming the parameter
value
• Default value – default value of the parameter.
The internal limits and constants paragraph gives details about:
• Enabling variables:
– These variables are the settings necessary to activate and
de-activate the whole related report, the report instance
and the individual trigger logics. The user can modify
these variables through the onboard HMI or the ground
programming tool.
• Modifiable limits:
– These are the user-modifiable values used in the report
logics. The user can modifies these limits through the
onboard HMI, uplink or the ground programming tool.
• Constants:
– These are non-modifiable values used in the report logics.
• Special limits:
– These are non-modifiable limits, but their values are not the same for
all the reports.

4.2.5 Recorded Parameters

There are three types of recorded parameters:

• Snapshot parameters
• Average parameters
• Calculated parameters.

4.2.6 Report Layout

The display conventions of the parameters use these symbols:

• ’9’ for any digit between 0 and 9

• ’1’ for a Boolean value (0 or 1)
• ’A’ for any character (alphabetical plus special characters)
• ’X’ for hexadecimal values
• ’#’ indicates that leading zeroes or decimal zeroes should not
be displayed
• ’-’ indicates that the value can be negative. In this case ’-’
must come into view, if the value is positive ’+’ must not come into view.

5. OUTPUT exportable files: FORMAT and naming rule

The files of exportable ACMS reports names follow the rule below:
1) For USB export:
(ReportNumber REPrrrr)(trigger code tttt)(Date of triggeringYYMMDDhhmnss)(Date of
exportYYYYMMDD) (UTC of recordingHHMNSS).(Tail ID).pmf

.
2) For other export :

(ReportNumber REPrrrr)(trigger code tttt)(Date of triggeringYYMMDDhhmnss)

NOTE: exportable ACMS report file format contained in the pmf

archive is XML; readout of subject xml file can be performed
through SAGEM ground tools.

For more information on PMF files please refer to ISI article

46.00.00040 IPCOM COOKBOOK for A350XWB.
--------------- END OF DOCUMENT----------------

Survey for the Engineering Support section

© Airbus SAS, 2018. All rights reserved. Confidential and proprietary document.The technical information
provided in this article is for convenience and information purposes only. It shall in no case replace the
official Airbus technical or Flight Operations data which shall remain the sole basis for aircraft
maintenance and operation. These recommendations and information do not constitute a contractual
commitment, warranty or guarantee whatsoever. They shall not supersede the Airbus technical nor
operational documentation; should any deviation appear between this article and the Airbus or airline's
official manuals, the operator must ensure to cover it with the appropriate document such as TA, FCD,
RDAS. Access to WISE is supplied by Airbus under the express condition that Airbus hereby disclaims any
and all liability for the use made by the user of the information contained in WISE. It shall be used for
the user's own purposes only and shall not be reproduced or disclosed to any third party without the
prior consent of Airbus.