W DOC AIRBUS | AMM A320F

ATIMS - AIRLINE INFORMATION SERVICES - DESCRIPTION AND OPERATION

** ON A/C NOT FOR ALL
1. General
F Airline Operation Control (AOC) Overview - Aircraft Architecture ** ON A/C NOT FOR ALL
F Airline Operation Control (AOC) Overview - Ground Station Architecture ** ON A/C NOT FOR ALL

The Airline Operational Control (AOC) applications are datalink applications used by the airline maintenance center, airline flight operations and airline passenger services (administrative purposes).
They are uploaded into the Air Traffic Services Unit (ATSU) by means of software disks composed of the AOC software (22TX) and the AOC database (24TX) which are located in the storage box.
The AOC applications have access to the following equipment through the services provided by the ATSU A/C Interface software:
  • VDR3, HFDR (optional) and SDU (optional) for air/ground message transmission/reception
  • printer, MCDUs and FWCs for Human/Machine Interface (HMI) purpose
  • CFDIU, ACMS DMU, Cabin Terminals for sending/receiving some data in ARINC 619 format.
A. Remote AOC Applications
(1) General
The remote AOC applications are integrated in the following equipments:
(2) Function
These applications are composed of Airline Operational Control and Airline Administrative Communication (AAC) applications.
(a) AOC applications
  • AOC applications concern operations directly related to flight and maintenance purposes.
  • Maintenance applications are integrated in the CFDIU and in the ACMS DMU.
  • Flight operations applications are integrated in the FMGCs.
  • Flight performance applications are integrated in the ACMS DMU.
(b) AAC applications
  • AAC applications concern administrative communications for the cabin crew and are integrated in the Cabin Terminals (CPMU and DIU).
NOTE: For these reasons, the CFDIU, FMGCs, ACMS DMU and Cabin Terminals are named "remote AOC peripherals".

B. Hosted AOC Applications
(1) General
The AOC applications hosted within the ATSU give the AOC configuration and the structure of the AOC system pages which are available on the MCDUs.
(2) Function
The AOC software package is a software component consisting of hosted AOC applications. An AOC database software enables to customize the AOC applications. In this package, is defined the list of labels used by the AOC applications and which have to be extracted by the ATSU.
The main ground users of these applications are the Airline maintenance center, the Airline flight operations and the airline passenger services.
For the AOC applications, the ATSU is an airborne router in charge of:
  • receiving the airline uplink messages and routing them to the corresponding remote AOC peripheral,
  • acquiring the downlink messages from the remote AOC peripherals and sending them to the ground according to the airline routing policy.
** ON A/C NOT FOR ALL
2. System Description
A. AOC Reports Transmission
As soon as the ATSU initialization is achieved and the ATSU router is active, the AOC applications become operational.
(1) Mode of transmission
The reports are either pre-defined, pre-formatted or free text.
They can be generated:
  • automatically: the automatic mode is programmed into the peripheral (event, frequency,...). When the conditions are met for automatic transmission, the peripheral sends the required report to the ATSU. The remote AOC peripheral periodically attempts to send the message until the transmission is successful. In case of ATSU failure, the peripheral gives up the transmission.
  • upon crew request on one MCDU
  • upon reception of an uplink request: an uplink report request is received from the ground and transmitted by the ATSU to the concerned peripheral. An uplink request contains the type of the report to be generated and transmitted (report number) and sometimes, additional information such as trigger conditions. Only one transmission attempt is made.
(2) Datalink communication status
As no buffering capacity is offered by the ATSU, each remote AOC peripheral only transmits another message when the ATSU has completed the sending of the previous message to the ground. For this reason, the remote AOC peripheral continuously monitors the activity of the ATSU datalink communication to determine the status.
This status has two states: Ready or Not Ready depending on:
  • the validity of the communication link status
  • the correct operation of the ATSU
  • the Satcom or VHF datalink status (one communication network available).
NOTE: If the peripheral datalink status is Not Ready then, the peripheral is considered unable to communicate with the ATSU and the related selection stars are not displayed on the appropriate MCDU pages of the peripheral for manual command.
(3) AOC message structure
(a) Uplink message structure for hosted AOC application
The ARINC 618 datalink message is divided into blocks.
There can be up to sixteen blocks, each block being composed as follows:
START OF HEADING (1 character)
ADDRESS (7 characters)
Technical Acknowledgment (1 character)
LABEL (2 characters)
Uplink Block Identifier (1 character)
Start of Transmission (1 character)
APPL TEXT (220 characters max.)
SUFFIX (1 character)
Block Check Sequence (2 characters)
BCS SUFFIX (1 character)

(b) Uplink message structure for remote AOC application
The ARINC 618 datalink message is divided into blocks.
There can be up to sixteen blocks, each block being composed as follows:
START OF HEADING (1 character)
ADDRESS (7 characters)
Technical Acknowledgment (1 character)
LABEL (2 characters)
Uplink Block Identifier (1 character)
Start of Transmission (1 character)
SUBLABEL (4 characters)
APPL TEXT (216 characters max.)
SUFFIX (1 character)
Block Check Sequence (2 characters)
BCS SUFFIX (1 character)


The ATSU Router processes a new message froms this ARINC 618 uplink message in order to send it to the corresponding remote AOC peripheral.
The structure of the Router message is as follows:
ORIGIN (1 character)
PURPOSE/NATURE (1 character)
DESTINATION (1 character)
APPL TEXT (3456 characters max.)

(c) Downlink message from hosted AOC application
The ARINC 618 datalink message structure is divided into blocks.
There can be up to sixteen blocks, each block being composed as follows:
START OF HEADING (1 character)
ADDRESS (7 characters)
Technical Acknowledgment (1 character)
LABEL (2 characters)
Downlink Block Identifier (1 character)
Start of Transmission (1 character)
MSN (4 characters)
Flight ID (6 characters)
APPL TEXT (210 characters max.)
SUFFIX (1 character)
Block Check Sequence (2 characters)
BCS SUFFIX (1 character)

(d) Downlink message from remote AOC peripheral
The ATSU Router receives from the remote AOC peripheral the message to be transmitted. The structure of the message is as follows:
ORIGIN (1 character)
PURPOSE/NATURE (1 character)
DESTINATION (1 character)
APPL TEXT (1 character)


The ATSU Router modifies the message structure into blocks.
There can be up to sixteen blocks, each one being composed as follows:
START OF HEADING (1 character)
ADDRESS (7 characters)
Technical Acknowledgment (1 character)
LABEL (2 characters)
Downlink Block Identifier (1 character)
Start of Transmission (1 character)
MSN (4 characters)
Flight ID (6 characters)
SUBLABEL (4 characters)
APPL TEXT (206 characters max.)
SUFFIX (1 character)
Block Check Sequence (2 characters)
BCS SUFFIX (1 character)

(4) Codes definition
(a) Origin code
1 For the uplink messages, the origin code indicates the air/ground medium of transmission.
There are four origin codes for the datalink messages:
G for ground policy
H for HF policy
M for the ATSU Router
S for Satcom policy
V for VHF policy.

2 For the downlink messages, the origin code indicates the remote AOC peripheral.
This table gives the correspondance between the origin code and the label/sublabel for downlink messages.
---------------------------------------------------------
! ORIGIN CODE ! REMOTE AOC PERIPHERALS ! LABEL/SUBLABEL !
---------------------------------------------------------
! A ! FMGC1 ! H1/M1 !
---------------------------------------------------------
! B ! FMGC2 ! H1/M2 !
---------------------------------------------------------
! F ! CFDIU ! H1/CF !
---------------------------------------------------------
! 1 ! CPMU ! H1/T1 !
---------------------------------------------------------
! 2 ! DIU ! H1/T2 !
---------------------------------------------------------
! D ! ACMS DMU ! H1/DF !
---------------------------------------------------------

(b) Purpose/nature code
The purpose/nature code indicates the message type.
----------------------------------------
! CODE ! TYPE OF MESSAGE !
----------------------------------------
! A ! FLIGHT NUMBER !
----------------------------------------
! B ! AIRCRAFT REGISTRATION !
----------------------------------------
! V ! UPLINK !
----------------------------------------
! W ! DOWNLINK !
----------------------------------------
! T ! DABS/ASAS UPLINK !
----------------------------------------
! N ! NOT A RESPONSE !
----------------------------------------
! K ! ACKNOWLEDGMENT !
----------------------------------------
! Q ! BUSY !
----------------------------------------
! D ! DOCUMENTARY DATA !
----------------------------------------
! E ! ENGINE DATA !
----------------------------------------
! F ! FAILED MESSAGE !
----------------------------------------
! Z ! HF DOWNLINK "NO COMM" !
----------------------------------------
! C ! DATA BUS CHECK !
----------------------------------------
! G ! FUEL DATA !
----------------------------------------
! L ! LANDING DATA !
----------------------------------------
! P ! POSITION REPORT !
----------------------------------------
! X ! USER DEFINED !
----------------------------------------
! S ! STATUS !
----------------------------------------

(c) Destination code
1 For the uplink messages, the destination code indicates the destination system (remote AOC peripheral).
----------------------------------------
! ORIGIN CODE ! REMOTE AOC PERIPHERALS !
----------------------------------------
! A ! FMGC1 !
----------------------------------------
! B ! FMGC2 !
----------------------------------------
! D ! ACMS DMU !
----------------------------------------
! F ! CFDIU !
----------------------------------------
! M ! ATSU !
----------------------------------------
! Y ! FMGC COM MASTER !
----------------------------------------
! 1 ! CPMU !
----------------------------------------
! 2 ! DIU !
----------------------------------------

2 For the downlink messages, the destination code indicates the air/ground medium of transmission.
There are four destination codes for the datalink messages:
G for ground policy
H for HF policy
S for Satcom policy
V for VHF policy.

(d) Label codes
The label code indicates the type of message.
----------------------------------------
! LABEL ! TYPE OF MESSAGE !
----------------------------------------
! C1 ! PRINTER MESSAGE !
----------------------------------------
! H1 ! REMOTE AOC !
----------------------------------------
! RA ! CREW MESSAGE !
----------------------------------------
! 3A ! AOC ALERT !
----------------------------------------
! 3B ! AOC CALL !
----------------------------------------
! 3M ! AOC MESSAGE !
----------------------------------------
! 3P ! AOC PRINT !
----------------------------------------
! 3W ! WX REPORT !
----------------------------------------
! 54 ! VOICE GO-AHEAD !
----------------------------------------

B. AOC Applications Description

There are three types of AOC applications:
(1) AOC Type 1
Most of the AOC applications belong to this category.
The main functions of these applications are to:
  • collect information from on-board systems
  • transmit and receive air/ground ARINC 618 messages
  • allow the crew to enter information through the MCDU
  • display and print messages and information collected from on-board systems or messages received from the ground
  • transmit reports manually through the MCDU, automatically or on ground request.
NOTE: Some specific AOC Type 1 applications also generate ARINC 429 broadcast data, such as OOOI data (Out/On/Off/In indicates the aircraft situation: at gate, A/C moving before takeoff, takeoff or touch-down).
These transmissions to on-board systems are restricted to the Cabin Terminals.
(a) Flight operations applications
The following table describes the different flight operations applications:
-------------------------------------------------------------------------------
! Flight Ops ! Description ! Downlink (DN) ! Report Description !
! Application ! ! or ! !
! ! ! Uplink (UP) ! !
! ! ! messages ! !
-------------------------------------------------------------------------------
! Downlink reports ! Enables crew ! DN: Refueling ! This report contains a !
! transmission ! to enter ! report ! set of pre-defined !
! ! information ! (Label 15/ ! parameters (units, fuel!
! ! through MCDU ! automatic ! type, supplier...) and !
! ! (free text ! transmission) ! parameters calculated !
! ! and/or pre- ! ! during the flight. !
! ! defined ! ! Trigger at entry into !
! ! information, ! ! Cruise, flight phase 6.!
! ! acquired from -------------------------------------------
! ! peripherals ! DN: OUT report ! Trigger at OUT event !
! ! from on-board ! (Label QP/ ! !
! ! systems, or ! automatic ! !
! ! received from ! transmission) ! !
! ! the ground), -------------------------------------------
! ! and initiate ! DN: OFF report ! Trigger at OFF event !
! ! the transmis- ! (Label QQ/ ! !
! ! -sion of a ! (Automatic ! !
! ! specific ! transmission) ! !
! ! downlink -------------------------------------------
! ! report. ! DN: ON report ! Trigger at ON event !
! ! ! (Label QR/ ! !
! ! ! Automatic ! !
! ! ! transmission) ! !
! ! -------------------------------------------
! ! ! DN: IN report ! Trigger at IN event !
! ! ! ( Label QS/ ! !
! ! ! Automatic ! !
! ! ! transmission) ! !
! ! -------------------------------------------
! ! ! DN: Return IN ! Trigger at Return IN !
! ! ! report ! event !
! ! ! (Label QT/ ! !
! ! ! Automatic ! !
! ! ! transmission) ! !
! ! -------------------------------------------
! ! ! DN: Free text ! This report contains a !
! ! ! message - ! free text to the !
! ! ! operations ! company operations. !
! ! ! (Label 81/ ! !
! ! ! Initiated on ! !
! ! ! MCDU) ! !
! ! -------------------------------------------
! ! ! DN: Free text ! This report contains a !
! ! ! message - SITA ! free text to a specific!
! ! ! address ! SITA address. !
! ! ! (Label 80/ ! !
! ! ! Initiated on ! !
! ! ! MCDU) ! !
! ! -------------------------------------------
! ! ! DN:Delay report! Informs the ground of !
! ! ! (Label Q7/ ! an enroute delay. !
! ! ! Initiated on ! !
! ! ! MCDU) ! !
! ! -------------------------------------------
! ! ! DN: Diversion ! Informs the ground that!
! ! ! or ETA change ! the A/C is diverted!
! ! ! report ! to an alternate airport!
! ! ! (Label 5Y/ ! or the estimated time !
! ! ! Initiated on ! of arrival !
! ! ! MCDU) ! !
-------------------------------------------------------------------------------
! Uplink messages ! ! DN: Connecting ! This message is sent at!
! requests/analysis ! ! gate request ! the beginning of the !
! ! ! (Label 13/ ! descent to require a !
! ! ! Automatic ! connecting gate !
! ! ! transmission) ! (Flight phase 7) !
! ! -------------------------------------------
! ! ! DN: Loadsheet ! !
! ! ! request ! !
! ! ! (Label 14/ ! !
! ! ! Request MCDU) ! !
! ! ! UP: Loadsheet ! !
! ! ! information! !
! ! -------------------------------------------
! ! ! DN: Weather ! The crew initiates a !
! ! ! request - ! specific weather !
! ! ! Actual ! request for specific !
! ! ! (Label 5U/ ! airports. !
! ! ! Request MCDU) ! !
! ! ! UP: Weather ! !
! ! ! information -! !
! ! ! Actual ! !
! ! -------------------------------------------
! ! ! DN: Weather ! The crew initiates a !
! ! ! request - ! specific weather !
! ! ! Forecast ! request for specific !
! ! ! (Label 5U/ ! airports. !
! ! ! Request MCDU) ! !
! ! ! UP: Weather ! !
! ! ! information -! !
! ! ! Forecast ! !
! ! -------------------------------------------
! ! ! DN: Weather ! The crew initiates a !
! ! ! request - ! specific weather !
! ! ! Actual and ! request for specific !
! ! ! forecast ! airports. !
! ! ! (Label 5U/ ! !
! ! ! Request MCDU) ! !
! ! ! UP: Weather ! !
! ! ! information -! !
! ! ! Actual and ! !
! ! ! forecast ! !
! ! -------------------------------------------
! ! ! DN: NOTAMS ! The crew initiates a !
! ! ! request ! NOTAMS request downlink!
! ! ! (Label 11/ ! for specific airports. !
! ! ! Request MCDU) ! !
! ! ! UP: NOTAMS ! !
! ! ! information ! !
! ! -------------------------------------------
! ! ! DN: Winds aloft! The crew initiates a !
! ! ! request ! wind request downlink !
! ! ! (Label 12/ ! for specific airports. !
! ! ! Request MCDU) ! !
! ! ! UP: Winds aloft! !
! ! ! information ! !
! ! -------------------------------------------
! ! ! DN: Voice ! The crew can be !
! ! ! contact request! contacted by the !
! ! ! - Operations! operations via a !
! ! ! (Label 21/ ! specific media (VHF/HF/!
! ! ! Request MCDU) ! SATCOM). !
! ! ! ! !
-------------------------------------------------------------------------------

(b) Maintenance applications
The following table describes the different maintenance applications:
-------------------------------------------------------------------------------
! Maintenance ! Description ! Downlink ! Report Description !
! application ! ! DN or ! !
! ! ! Uplink UP ! !
! ! ! messages ! !
-------------------------------------------------------------------------------
! Downlink reports ! Enables crew ! DN: AOC S/W ! AOC software or !
! transmission ! to enter ! Load or ! database changed or !
! ! information ! Reset report ! AOC has reset due to !
! ! through MCDU ! (Label 1L/ ! very long power cut or !
! ! (free text ! Automatic ! software problem. !
! ! and/or pre- ! transmission) ! !
! ! defined -------------------------------------------
! ! information) ! DN: Free text ! This report contains a !
! ! and to ! message - ! free text to the !
! ! initiate the ! Maintenance! company maintenance. !
! ! transmission ! (Label 82/ ! !
! ! of a specific ! Request MCDU) ! !
! ! downlink -------------------------------------------
! ! report. ! DN: Voice ! The crew can be !
! ! ! contact request! contacted by the !
! ! ! - Maintenance ! operations via a !
! ! ! (Label 22/ ! specific media (VHF/HF/!
! ! ! Request MCDU) ! SATCOM).. !
! ! ! !
-------------------------------------------------------------------------------
! Crew access to ! ! AOC ! The crew requires the !
! AOC information ! ! configuration ! display of the AOC !
! ! ! ! software part numbers !
! ! ! ! on MCDU. !
! ! -------------------------------------------
! ! ! Sensors ! A specific MCDU page, !
! ! ! ! SENSORS page, is !
! ! ! ! available to review !
! ! ! ! the status of all OOOI !
! ! ! ! sensors. !
! ! -------------------------------------------
! ! ! Received 429 ! A specific MCDU page, !
! ! ! data ! AOC 429 RCV DATA page, !
! ! ! ! is available to the !
! ! ! ! operator to view the !
! ! ! ! status of a specific !
! ! ! ! 429 broadcast label. !
-------------------------------------------------------------------------------

(c) Airline administrative applications
The following table describes the different airline administrative applications:
-------------------------------------------------------------------------------
! Administrative ! Description ! Downlink ! Report Description !
! Applications ! ! DN or ! !
! ! ! Uplink UP ! !
! ! ! messages ! !
-------------------------------------------------------------------------------
! OOOI phase ! This ! DN: OOOI report! This application: !
! processing ! application: ! - Return in ! - acquires sensor !
! Downlink reports ! - acquires ! - In event ! information !
! transmission ! sensor ! - Out event ! - uses this information!
! ! information ! - On event ! to determine the !
! OOOI means ! - computes ! - Off event ! present state of the !
! Out= A/C on ground! the current ! - OOOI ! aircraft (In, Out, !
! taxiing ! OOOI state ! information ! Off, On) !
! (ground speed! - sends ! response ! - after each state !
! greater than ! automati- ! UL: OOOI ! change, sends !
! zero) ! -cally ! information! automatically a !
! Off= A/C in flight! downlink ! request ! specific report: !
! On = A/C landed, ! reports ! ! . In event report !
! taxiing to ! or upon ! ! . On event report !
! gate ! request from! ! . Out event report !
! In= A/C on ground! the ground ! ! . Off event report !
! at gate, at ! - broadcasts ! ! - transmits the current!
! least one ! information ! ! OOOI state on a !
! door open ! inside and ! ! specific ARINC 429 !
! Return in= A/C has! outside ATSU! ! label, and broadcasts!
! returned to ! - displays ! ! this information !
! the terminal ! information ! ! within the ATSU. !
! without ! on MCDU ! ! - displays the present !
! taking off. ! ! ! state on MCDU FLIGHT !
! ! ! ! LOG page. !
-------------------------------------------------------------------------------

(d) Printer applications
The following table describes the different printable menus and the associated printable reports.
-------------------------------------------------------------------------------
! MCDU Menus ! Description ! Transmission ! Associated Reports !
! Management ! ! initiated on ! !
-------------------------------------------------------------------------------
! AOC FLIGHT INIT ! ! MCDU ! !
-------------------------------------------------------------------------------
! AOC FREE TEXT ! AIRLINE ! MCDU ! DN: Free text message -!
! ! MAINTENANCE ! ! Maintenance !
! -----------------------------------------------------------
! ! AIRLINE ! MCDU ! DN: Free text message -!
! ! OPERATIONS ! ! Operations !
! -----------------------------------------------------------
! ! SITA ADDRESS ! MCDU ! DN: Free text message -!
! ! ! ! SITA address !
-------------------------------------------------------------------------------
! AOC REC MSGS ! AOC MSG ! MCDU ! UP: All received !
! ! DISPLAY ! ! messages - !
! ! ! ! AOC PRINT message !
-------------------------------------------------------------------------------
! AOC REFUELING ! ! MCDU ! !
! REPORT ! ! ! !
-------------------------------------------------------------------------------
! AOC CONFIGURATION ! ! MCDU ! !
-------------------------------------------------------------------------------
! AOC OOOI STATUS ! ! MCDU ! DN: OUT report !
! ! ! ! OFF report !
! ! ! ! ON report !
! ! ! ! IN report !
! ! ! ! Return IN report !
-------------------------------------------------------------------------------
! AOC CFDIU PROG ! ! MCDU ! !
-------------------------------------------------------------------------------
! AOC 429 RCVD DATA ! ! MCDU ! !
-------------------------------------------------------------------------------

(2) AOC Type 2 applications
This application consists in collecting information from on-board systems, compiling specific data files and sending them on request or upon internal trigger event to the remote AOC ARINC 619 peripherals (CPMU and DIU).
(3) AOC Type 3
The type 3 AOC applications configure the ATSU A/C Interface with internal parameter values:
  • the routing policy used for downlink messages for hosted AOC applications
  • the VHF3 voice directory screen managed by the air/ground communication management function
  • CFDIU programming: activation or inhibition of the transmission of CFDIU downlink reports such as the CFDIU BITE Data report, the ECAM warning report, the Failure report and the POST-FLIGHT REPORT.
NOTE: This configuration is sent to the CFDIU by the ATSU interface services.
(a) Routing policy
For each message transmitted by the AOC application to the ATSU, the ATSU router analyses the destination code and checks the air/ground media availability, one Service Provider (SP) after the other and in order.
Then, the message is sent through the first valid Service Provider. If no available medium is found, the message remains in the router buffer.
(b) Service Provider
The datalink message is sent through the Service Provider (SP) applicable to the present airspace which corresponds to a given frequency. There are seven Service Providers:
SP 1 ARINC VHF
SP 2 SITA EUROPE
SP 3 SITA PACIFIC
SP 5 AVICOM
SP 6 CANADA
SP 30 SATCOM
SP 40 HF

(c) VHF3 voice directory configuration
This application configures the ATSU Communication Manager with a VHF voice directory.
This voice directory contains a list of frequencies titles and values.
The ATSU COMM Manager uses this configuration table to manage a specific MCDU menu, allowing the selection and the activation of a given voice frequency on VHF 3.
(d) CFDIU programming
The CFDIU programming activates or inhibits the generation of the following reports:
  • BITE report: YES
  • ECAM warning report: YES
  • Failure report: NO
  • POST-FLIGHT REPORT: YES
C. Remote AOC Applications

The interface between the ATSU and the remote AOC peripherals conforms to ARINC 619 Specifications.
(1) DMU AOC application
The ATSU downlinks these DMU reports to the ground:
  • Engine cruise report (01)
  • Cruise performance report (02)
  • Engine take off report (04)
  • Engine report on request (05)
  • Engine gas path advisory report (06)
  • Engine mechanical advisory report (07)
  • Engine divergence report (09)
  • Engine start report (10)
  • Engine run up report (11)
  • APU MES/IDLE report (13)
  • APU shut down report (14)
  • Free programmable report N°1 (16)
  • Free programmable report N°2 (17)
  • Free programmable report N°3 (18)
  • Load report (15)
  • ECS report (19)
  • RAT report (20)
NOTE: The report number adjacent to the report designation is that defined in the ACMS specification.
After a message is sent, the DMU waits for the acknowledgement from the ATSU indicated by the Imbedded Message Identifier (IMI):
  • the first transmitted character is A
  • the two other characters are the report number.
(2) CFDIU AOC application
The CFDIU active functions enable the generation and the transmission of the following reports to the ATSU:
(a) POST-FLIGHT REPORT (on ground) or Current Flight Report (in flight)
The CFDIU automatically transmits the POST-FLIGHT REPORT to the ATSU at the end of the flight leg.
(b) Real-Time Failure (in flight)
The failure messages are automatically transmitted by the CFDIU to the ATSU.
(c) Real-Time Warning (in flight)
The ECAM warnings are automatically transmitted by the CFDIU to the ATSU.
(d) BITE Data Messages
A BITE data represents one or more MCDU page, so the CFDIU transmits the BITE data messages to the ATSU on manual request from the MCDU.
(e) Class 3 Report (on ground)
The CFDIU transmits the Class 3 reports to the ATSU on uplink or on manual request.
(f) Servicing Report (optional)
To generate this report, the CFDIU requires Documentary Data from the ATSU at power-up and at flight phase transition 9 to 10. It then transmits the Servicing Report to the ATSU automatically, on uplink request . The format of the message is as follows:
---------------------------------------------------
! OCTET NUMBER ! CONTENT !
---------------------------------------------------
! 1 ! "M" Origin Code = ATSU !
---------------------------------------------------
! 2 ! "D" Purpose Code = !
! ! Documentary Data !
!--------------------------------------------------
! 3 ! "F" Destination Code = CFDIU!
---------------------------------------------------
! 4-5 ! "0" !
---------------------------------------------------
! 6-9 ! OUT (HH/MM) !
---------------------------------------------------
! 10-13 ! OFF (HH/MM) !
---------------------------------------------------
! 14-17 ! ON (HH/MM) !
---------------------------------------------------
! 18-21 ! IN (HH/MM) !
---------------------------------------------------
! 22-25 ! Actual Departure !
---------------------------------------------------
! 26-29 ! Actual Arrival !
---------------------------------------------------
! 30-37 ! Captain Name !
---------------------------------------------------
! 38-45 ! First Officer Name !
---------------------------------------------------


(3) FMGC AOC application
The AOC application is called ACARS functions in the FMGC.
The ATSU downlinks FMGC reports to inform the airline of the configuration of the aircraft (flight plan reports, position reports,etc...).
The ATSU Router determines which FMGC is intended to receive the uplink message by reference to the sub-label characters.
(4) Cabin Terminals AOC application
The transmission of the downlink reports is only automatic or on ground request.
** ON A/C NOT FOR ALL
3. Interface
A. On-Board Systems Interface
The hosted AOC applications are loaded into the ATSU and are interfaced with the following on-board peripherals:
  • Clock
  • CFDIU
  • CPMU
  • DIU
  • DMC 1, 2 & 3
  • FMGC 1 & 2
  • FWC 1 & 2
  • LGCIU
  • SDAC 1 & 2
(1) Input parameters
The Standard AOC application acquires the following parameters from on-board peripherals:
-------------------------------------------------------------------------------
! PARAMETER NAME ! FROM ! COMMENTS !
-------------------------------------------------------------------------------
! FLIGHT IDENTIFICATION ! ATSU ! Two characters for A/L ID and !
! ! ! four characters for flight !
! ! ! number !
-------------------------------------------------------------------------------
! AIRCRAFT REGISTRATION NUMBER ! ATSU ! Seven characters !
-------------------------------------------------------------------------------
! SENSOR INPUTS ! ! !
-------------------------------------------------------------------------------
! DOORS ! SDAC ! AOC acquires the status (open/!
! ! ! closed) of all types of doors !
-------------------------------------------------------------------------------
! PARKING BRAKE STATUS ! SDAC ! !
-------------------------------------------------------------------------------
! ENGINES RUNNING ! FWC ! !
-------------------------------------------------------------------------------
! NOSE STRUT ! LGCIU ! Discrete signal !
-------------------------------------------------------------------------------
! FUEL ON BOARD ! FMGC ! !
-------------------------------------------------------------------------------
! GROUND SPEED ! DMC, FWC ! !
-------------------------------------------------------------------------------
! ACTIVE NAV DATABASE ! FMGC ! !
-------------------------------------------------------------------------------
! ACTIVE WAYPOINT ! FMGC ! !
-------------------------------------------------------------------------------
! FMC FLIGHT PHASE ! FMGC ! Discrete signal !
-------------------------------------------------------------------------------
! AIRCRAFT CONFIGURATION ! CFDIU ! Discrete signal !
-------------------------------------------------------------------------------
! ALTERNATE DESTINATION ! FMGC ! !
-------------------------------------------------------------------------------
! APU RUNNING ! SDAC ! Discrete signal !
-------------------------------------------------------------------------------
! BAROMETRIC ALTITUDE ! FWC ! !
-------------------------------------------------------------------------------
! BLOCK FUEL ! FMGC ! !
-------------------------------------------------------------------------------
! CABIN ALTITUDE ! SDAC ! !
-------------------------------------------------------------------------------
! COMPANY ROUTE ! FMGC ! !
-------------------------------------------------------------------------------
! COMPUTED AIRSPEED ! FWC ! !
-------------------------------------------------------------------------------
! DATE ! CFDIU, CLOCK ! !
-------------------------------------------------------------------------------
! DESTINATION RUNWAY ! FMGC ! !
-------------------------------------------------------------------------------
! ENGINE OIL PRESSURE ! FWC ! Discrete signal !
-------------------------------------------------------------------------------
! ETA ! FMGC ! !
-------------------------------------------------------------------------------
! FUEL FLOW ! FWC ! !
-------------------------------------------------------------------------------
! FUEL PANEL STATUS AND ! FWC ! !
! REFUELING IN PROGRESS ! ! !
-------------------------------------------------------------------------------
! GROSS WEIGHT ! FMGC , SDAC ! !
-------------------------------------------------------------------------------
! LATITUDE ! FMGC , DMC ! !
-------------------------------------------------------------------------------
! LONGITUDE ! FMGC , DMC ! !
-------------------------------------------------------------------------------
! RADIO HEIGHT ! FWC ! !
-------------------------------------------------------------------------------
! ROLL ANGLE ! FMGC ! !
-------------------------------------------------------------------------------
! STATIC AIR TEMPERATURE ! FWC, DMC ! !
-------------------------------------------------------------------------------
! STRUT SWITCH ! SDAC ! Discrete signal !
-------------------------------------------------------------------------------
! UTC ! CLOCK, CFDIU ! !
-------------------------------------------------------------------------------
! TOTAL AIR TEMPERATURE ! FWC ! !
-------------------------------------------------------------------------------
! TRACK ANGLE ! DMC ! !
-------------------------------------------------------------------------------
! WIND DIRECTION TRUE ! FMGC ! !
-------------------------------------------------------------------------------
! WIND SPEED ! FMGC ! !
-------------------------------------------------------------------------------
! WING ANTI ICE ! SDAC ! Discrete signal !
-------------------------------------------------------------------------------
! ZERO FUEL WEIGHT ! SDAC, FMGC ! !
-------------------------------------------------------------------------------
! FLIGHT NUMBER RUNWAY ! FMGC, CFDIU ! !
-------------------------------------------------------------------------------
! ORIGIN/DESTINATION STATIONS ! CFDIU ! !
-------------------------------------------------------------------------------
! FWC FLIGHT PHASE ! FWC ! Used for OOOI calculations !
-------------------------------------------------------------------------------

(2) Output parameters
The Standard AOC application generates the following parameters to on-board peripherals:
-------------------------------------------------------------------------------
! PARAMETER NAME ! TO ! COMMENTS !
-------------------------------------------------------------------------------
! OOOI STATE ! CPMU, DIU ! !
-------------------------------------------------------------------------------
! CFDIU PROGRAMMING ! CFDIU ! Activation /inhibition of the !
! ! ! transmission of the CFDIU !
! ! ! downlink reports !
-------------------------------------------------------------------------------
! STATIONS CHARACTER ! CPMU, DIU ! Contains the origin/ !
! ! ! destination airports !
-------------------------------------------------------------------------------

** ON A/C NOT FOR ALL
4. Operation
A. Operation and Control of the AOC Standard Application
(1) General
This paragraph describes the interaction of the ATSU with the Multipurpose Control and Display Unit (MCDU).
The three Multipurpose Control and Display Unit (MCDU) are used as interface between the crew and the Air Traffic Services Unit (ATSU).
They provide the means necessary to enter the text for data storage, data review and transmission-system status.
There are six line select-keys on each side of the display.
When the ATSU is given control of a MCDU, the ATSU DATALINK menu is displayed.
The AOC MENU page is the root page through which the different pages may be accessed.
(2) Structure of the AOC menus
F AOC - Pre-Flight Menu Architecture ** ON A/C NOT FOR ALL
F AOC - In-Flight Menu Architecture ** ON A/C NOT FOR ALL
F AOC - Post-Flight Menu Architecture ** ON A/C NOT FOR ALL
F AOC - Miscellaneous Menu Architecture ** ON A/C NOT FOR ALL
F AOC - MCDU Menu ** ON A/C NOT FOR ALL
The AOC application presents a main AOC MENU page in correspondance with the flight phase:
  • PRE-FLIGHT MENU at the start of a new flight leg
  • IN-FLIGHT MENU after the Take-Off phase
  • POST-FLIGHT MENU after the touchdown phase.
(3) AOC FLIGHT INIT page
F AOC FLIGHT INIT Page ** ON A/C NOT FOR ALL
This MCDU page enables to enter or display the flight initialization parameters. Most of these parameters are automatically filled from the flight plan entered into the FMGC.
(4) AOC WEATHER REQUEST page
F AOC WEATHER REQUEST Page ** ON A/C NOT FOR ALL
F AOC WEATHER REQUEST Page ** ON A/C NOT FOR ALL
This MCDU page enables to receive a weather report from a specific airport.
(5) AOC NOTAMS REQUEST page
F AOC NOTAMS REQUEST Page ** ON A/C NOT FOR ALL
This MCDU page enables to receive a NOTAMS report from a specific airport.
(6) AOC WINDS ALOFT REQUEST page
F AOC WINDS ALOFT REQUEST Page ** ON A/C NOT FOR ALL
This MCDU page enables to receive a WINDS ALOFT report from a specific airport.
(7) AOC FREE TEXT ADDRESS menu
F AOC FREE TEXT ADDRESS Page ** ON A/C NOT FOR ALL
(a) AIRLINE OPERATIONS page
This MCDU page enables to enter airline operations information (free text messages) and downlink airline operations reports.
(b) AIRLINE MAINTENANCE page
This MCDU page enables to enter airline maintenance information (free text messages) and downlink airline maintenance reports.
(c) SITA ADDRESS page
This MCDU page enables to enter a valid SITA address and downlink a free text.
(8) AOC REC MSGS page
F AOC REC MSGS Page ** ON A/C NOT FOR ALL
All the messages, since the last AOC software or database were loaded or the ATSU computer was reset, are stored in memory in the order they are received, with the last received message at the top of the list.
This MCDU page enables to review and print any uplink message.
The time the message was received is printed above each title.
Messages that have not been printed or displayed are listed in large font.
Once the message has been printed or displayed, its title will change to small font.
The color of the message title reflects the urgency of the message (amber is the most important).
To delete a message, press the CLR key, then press the line key adjacent to this message.
(9) AOC DIVERSION page
F AOC DIVERSION Page ** ON A/C NOT FOR ALL
This MCDU page enables to send a diversion report.
(10) AOC DELAY REPORT page
F AOC DELAY REPORT Page ** ON A/C NOT FOR ALL
This MCDU page enables to send a delay report.
(11) AOC REFUELING REPORT page
F AOC REFUELING REPORT Page ** ON A/C NOT FOR ALL
This MCDU page enables to enter and display fuel information included in the automatic fuel report.
(12) AOC VOICE CONTACT menu
F AOC VOICE CONTACT Page ** ON A/C NOT FOR ALL
This MCDU page enables to send a request message for voice contact to the airline operations on a specific frequency.
(13) AOC MISCELLANEOUS menu
F AOC MISCELLANEOUS Page ** ON A/C NOT FOR ALL
(a) AOC CONFIGURATION page
F AOC CONFIGURATION Page ** ON A/C NOT FOR ALL
This MCDU page enables to display the software configuration information (Part Number).
(b) AOC OOOI STATUS page
F AOC OOOI STATUS Page ** ON A/C NOT FOR ALL
This MCDU page enables to display the status information of the Out On Off In events.
(c) AOC CFDIU PROG page
F AOC CFDIU PROG Page ** ON A/C NOT FOR ALL
This MCDU page enables to set and clear the CFDIU reports.
(d) AOC 429 RCV DATA page
F AOC 429 RCV DATA Page ** ON A/C NOT FOR ALL
This MCDU page enables to display the bit values of ARINC 429 data for any label.
(e) AOC PARAMETER DISPLAY page
This MCDU page enables to display the value of any parameter in the parameter table.
B. AOC Standard Application Indicating
(1) ACARS MSG memo
This green memo comes into view on the EWD, pulsing during 60 seconds and then becomes steady.
ACARS MSG memo is activated when the following messages are received:
  • Crew message (label RA),
  • AOC message (label 3M),
  • AOC Call (label 3B),
  • AOC Print (label 3P).
(2) Advisories
Advisories are visual messages displayed on the MCDU scratchpad:
-------------------------------------------------------------------------------
! MESSAGE TEXT ! TRIGGER CONDITION ! RESET CONDITION !
-------------------------------------------------------------------------------
! NOT ALLOWED ! Data entry in an ! After five seconds or !
! ! unmodifiable field ! CLR mode key pressed or!
! ! ! data entry !
-------------------------------------------------------------------------------
! INVALID ENTRY ! LSK associated with a ! CLR mode key pressed or!
! ! data entry is pressed ! data entry !
! ! and the scratchpad ! !
! ! content do not corres- ! !
! ! -pond to the associated ! !
! ! criteria ! !
-------------------------------------------------------------------------------
! MANDATORY DATA MISSING ! ! !
-------------------------------------------------------------------------------
! PARAMETER OUT OF RANGE ! ! !
-------------------------------------------------------------------------------
! PRINTER FAIL ! PRINT LSK is pressed ! After five seconds or !
! ! and the printer cannot ! CLR mode key pressed or!
! ! accept the request ! data entry !
-------------------------------------------------------------------------------
! WX UPLINK ! Reception of a weather ! After five seconds or !
! ! report (label 3W) ! CLR mode key pressed or!
! ! ! data entry !
-------------------------------------------------------------------------------
! VHF VOICE MODE ! LSK that initiates a ! After five seconds or !
! MSG NOT GEN ! VHF only downlink is ! CLR mode key pressed or!
! ! pressed while VHF is in ! data entry !
! ! VOICE mode ! !
-------------------------------------------------------------------------------
! VHF NO COMM ! LSK that initiates a ! After five seconds or !
! MSG NOT GEN ! VHF downlink is pressed ! CLR mode key pressed or!
! ! while VHF is unavailable! data entry !
-------------------------------------------------------------------------------
! SAT NO COMM ! LSK that initiates a ! After five seconds or !
! MSG NOT GEN ! satellite downlink is ! CLR mode key pressed or!
! ! pressed while satellite ! data entry !
! ! is unavailable ! !
-------------------------------------------------------------------------------
! NO COMM ! LSK that initiates a ! After five seconds or !
! MSG NOT GEN ! downlink is pressed ! CLR mode key pressed or!
! ! while ATSU is ! data entry !
! ! unavailable !
-------------------------------------------------------------------------------
! First 23 characters of ! Reception of label 3V ! CLR mode key pressed or!
! an uplink message ! ! data entry !
-------------------------------------------------------------------------------
! BUFFER FULL ! LSK that initiates a ! After five seconds or !
! MSG NOT GEN ! downlink is pressed ! CLR mode key pressed or!
! ! and the buffer is full ! data entry !
-------------------------------------------------------------------------------

[Rev.10 from 2021] 2026.04.02 06:26:05 UTC
"WTRUIB" 2025