ABCD Tool Prototype Definition - Eurocontrol · 3 SUMMARY This deliverable (D4), presents the results for Work Package 4 “ABCD tool prototype definition”, as part of the ABCD

1

Aircraft Based Concept Developments

ABCD Tool Prototype Definition

SPECIFICATIONS

This document presents a synthesis of information aiming to

support discussions concerning Aircraft Based Concept

Developments. It does not represent the position of

EUROCONTROL Agency.

2

DOCUMENT CHANGE RECORD

The following table records the complete history of the successive editions of the

present document.

EDITION DATE DESCRIPTION OF EVOLUTION MODIFICATIONS

0.1 October 15th 2008 First Draft

0.2 December 19th 2008 Second draft Feedback from ALG

3

SUMMARY

This deliverable (D4), presents the results for Work Package 4 “ABCD tool

prototype definition”, as part of the ABCD project.

The purpose of this Work Package is to refine the description of the ABCD concept

and to define the specifications of the ABCD tool at airline level in order to develop

a prototype in Work Package 5.

The ABCD concept, which is based on the linkage of the individual flight plans

executed by the same aircraft, aims at using the flight planning and flight progress

information available for a given flight in order to detect as soon as possible

potential reactionary delay for the subsequent flights.

The envisaged ABCD tool will be installed as a complementary system to the

existing flight management system of the airline; providing the Airline Operations

Centre (AOC) with assistance to flight planning through an aid to the management

of DLA messages. The ABCD tool will not interact directly with the CFMU: any

interchange of information will be uniquely done with the airline systems and the

user, without interfering with the normal operations of the airline. As input, ABCD

will be provided, via the airline flight management system of the AOC, with the set

of messages exchanged between the airline and the CFMU, and also with additional

data such as the minimum turn-around times and the aircraft registration numbers.

As output, ABCD will provide the AOC with information that allows the user to

decide when to send a new DLA message and with the optimum EOBT proposal.

The ABCD operational services were defined according to 5 levels, which provide

the airline with flexibility to choose the required service for each situation:

- Level 0 allows the user to monitor reactionary delays;

- Levels 1 and 2 detect reactionary delays and propose flight updates

(new EOBT), taking into account or not stability criteria;

- Levels 3 and 4 provide automated DLA management: preparation and

proposal of DLA messages, with the option of sending messages

directly to the CFMU.

A set of functional requirements has been defined to provide the user with those

services: user interface requirements; airline system requirements; requirements

internal to the ABCD system.

They are the minimum specifications required to allow the prototyping of a generic

ABCD tool.

Additionally non-functional requirement are proposed to define a possible lay-out

for the HMI needed between the user and the tool. However the HMI design

depends on the preferences and needs of each airline hence does not have to be

detailed at the generic level.

4

TABLE OF CONTENTS

1111 INTRODUCTIONINTRODUCTIONINTRODUCTIONINTRODUCTION ............................................................................................................................................................................................................................................................................................................................................9999

1.1 BRIEF OVERVIEW OF ABCD ...............................................................................9 1.2 PAST ACHIEVEMENTS ........................................................................................9 1.3 PURPOSE AND SCOPE OF THE DOCUMENT ...........................................................12 1.4 DOCUMENT STRUCTURE ..................................................................................12

2222 ABCD CONCEPTABCD CONCEPTABCD CONCEPTABCD CONCEPT........................................................................................................................................................................................................................................................................................................................................13131313

2.1 ABCD AT A GLANCE........................................................................................13 2.1.12.1.12.1.12.1.1 ABCD ConceptABCD ConceptABCD ConceptABCD Concept ........................................................................................................................................................................................................................................................................................................................................................13131313 2.1.22.1.22.1.22.1.2 From the concept to the tool implementationFrom the concept to the tool implementationFrom the concept to the tool implementationFrom the concept to the tool implementation........................................................................................................................................................13131313 2.1.32.1.32.1.32.1.3 ABCD tool at airlinABCD tool at airlinABCD tool at airlinABCD tool at airline levele levele levele level ....................................................................................................................................................................................................................................................................................14141414 2.2 STAKEHOLDERS ..............................................................................................15

2.2.12.2.12.2.12.2.1 AirlinesAirlinesAirlinesAirlines........................................................................................................................................................................................................................................................................................................................................................................................................15151515 2.2.22.2.22.2.22.2.2 ATFCM SerATFCM SerATFCM SerATFCM Service Providers (CFMU)vice Providers (CFMU)vice Providers (CFMU)vice Providers (CFMU) ........................................................................................................................................................................................................................16161616 2.2.32.2.32.2.32.2.3 ANSPs ANSPs ANSPs ANSPs –––– ATS Providers (incl. Airport Towers) ATS Providers (incl. Airport Towers) ATS Providers (incl. Airport Towers) ATS Providers (incl. Airport Towers) ................................................................................................................................................17171717 2.2.42.2.42.2.42.2.4 Airport Airport Airport Airport –––– Ground handlers Ground handlers Ground handlers Ground handlers ............................................................................................................................................................................................................................................................................17171717 2.2.52.2.52.2.52.2.5 PassengersPassengersPassengersPassengers ....................................................................................................................................................................................................................................................................................................................................................................................18181818

3333 ABCD ENVIRONMENTABCD ENVIRONMENTABCD ENVIRONMENTABCD ENVIRONMENT ............................................................................................................................................................................................................................................................................................19191919

3.1 HUMAN ACTORS.............................................................................................19 3.1.13.1.13.1.13.1.1 Airline Operations Centre StaffAirline Operations Centre StaffAirline Operations Centre StaffAirline Operations Centre Staff ................................................................................................................................................................................................................................................19191919 3.2 SYSTEM ACTORS .............................................................................................20

3.2.13.2.13.2.13.2.1 Flight ManagFlight ManagFlight ManagFlight Management Systemement Systemement Systemement System............................................................................................................................................................................................................................................................................20202020 3.2.23.2.23.2.23.2.2 CFMUCFMUCFMUCFMU SystemsSystemsSystemsSystems ........................................................................................................................................................................................................................................................................................................................................................20202020 3.3 MESSAGES & DATA .........................................................................................24

3.33.33.33.3.1.1.1.1 Types of messages managed by ABCDTypes of messages managed by ABCDTypes of messages managed by ABCDTypes of messages managed by ABCD........................................................................................................................................................................................................24242424 3.3.23.3.23.3.23.3.2 Elementary data associated to messagesElementary data associated to messagesElementary data associated to messagesElementary data associated to messages................................................................................................................................................................................................24242424 3.3.33.3.33.3.33.3.3 Current operational context associCurrent operational context associCurrent operational context associCurrent operational context associated to messagesated to messagesated to messagesated to messages ....................................................................................................................25252525 3.3.43.3.43.3.43.3.4 Messages descriptionMessages descriptionMessages descriptionMessages description....................................................................................................................................................................................................................................................................................................................27272727 3.3.53.3.53.3.53.3.5 Other data managed by ABCDOther data managed by ABCDOther data managed by ABCDOther data managed by ABCD........................................................................................................................................................................................................................................................29292929

4444 ABCD REQUIREMENTSABCD REQUIREMENTSABCD REQUIREMENTSABCD REQUIREMENTS ........................................................................................................................................................................................................................................................................................31313131

4.1 FOREWORD....................................................................................................31 4.2 REQUIREMENTS RELATED TO HUMAN ACTORS ...................................................31

4.2.14.2.14.2.14.2.1 Operational ServicesOperational ServicesOperational ServicesOperational Services ....................................................................................................................................................................................................................................................................................................................31313131 4.2.24.2.24.2.24.2.2 Functional requirementsFunctional requirementsFunctional requirementsFunctional requirements............................................................................................................................................................................................................................................................................................35353535 4.2.34.2.34.2.34.2.3 Non functional reqNon functional reqNon functional reqNon functional requirementsuirementsuirementsuirements................................................................................................................................................................................................................................................................37373737 4.3 REQUIREMENTS RELATED TO SYSTEM ACTORS.....................................................41

4.3.14.3.14.3.14.3.1 Principles and preconditionsPrinciples and preconditionsPrinciples and preconditionsPrinciples and preconditions ................................................................................................................................................................................................................................................................41414141 4.3.24.3.24.3.24.3.2 Functional requirementsFunctional requirementsFunctional requirementsFunctional requirements............................................................................................................................................................................................................................................................................................42424242 4.4 REQUIREMENTS INTERNAL TO ABCD ................................................................44

4.4.14.4.14.4.14.4.1 Functional requiremeFunctional requiremeFunctional requiremeFunctional requirementsntsntsnts............................................................................................................................................................................................................................................................................................44444444 4.4.24.4.24.4.24.4.2 NonNonNonNon----Functional requirementsFunctional requirementsFunctional requirementsFunctional requirements ........................................................................................................................................................................................................................................................50505050

5

LIST OF TABLES

Table 1: Messages potentially handled by ABCD (depending on current airline

message interchange).................................................................................................... 28 Table 2: ABCD database layout .................................................................................... 44 Table 3: Data to extract from the messages to update the database ........................... 47 Table 4: Requirements list ............................................................................................ 69 Table 5: Matrix of dependencies (next page) .............................................................. 70

LIST OF FIGURES

Figure 1; ETFMS functions........................................................................................... 23 Figure 2: The ABCD environment.............................................................................. 30 Figure 3: Example of a possible configuration of the display ..................................... 41

6

GLOSSARY

A/C Aircraft

ACK Acknowledgement message

ADEP Aerodrome of Departure

ADES Aerodrome of Destination

ADEXP ATS Data Exchange Presentation

AFTN Aeronautical Fixed Telecommunication Network

ANSP Air Navigation Service Provider

AO Aircraft Operator

AOC Airline Operation Centre

ARCID Aircraft Identification ARCTYP Aircraft type

ARN ATS Route Network

ARO Air Traffic Service Reporting Office

ARR Arrival Message

ATFCM Air Traffic Flow and Capacity Management

ATFM Air Traffic Flow Management

ATC Air traffic Control

ATM Air Traffic Management

ATS Air Traffic services

ATSU Air Traffic services Unit

CASA Computer Assisted Slot Allocation (CFMU)

CDM Collaborative Decision Making

CFMU Central Flow Management Unit

CHG Change Message

CNL Cancellation message

CTOT Calculated Take-off Time

DEP Departure Message

DLA Delay Message

ELDT Estimated Landing Time

ENV Environment (system)

EOBT Estimated Off-Block Time

EPOBT Earliest Possible Off-Block Time

ETFMS Enhanced Tactical Flow Management System

FMP Flow Management Position (ACC)

FPL Filed Flight Plan

FUM Flight Update Message

GAT General Air Traffic

IFPS Initial Flight Plan Processing System

IFR Instrument flight rules

IRAB Innovative Research Advisory Board

MVT Movements

OPSD Operational Division (of CFMU)

7

REA Ready Message

RPL Repetitive Flight Plan

SAM Slot Allocation Message

SLC Slot Requirement Cancellation Message

SRM Slot Revision Message

TACOT TACT Automated Command Tool

TTLEET Total Estimated Elapsed Time

TIS Time to Insert into the Sequence

TOT Time-Over Target

TRS Time to Remove from the Sequence

TTM Minimum Turn-Around Time

8

REFERENCES

[1] ABCD: Aircraft Based Concept Developments - Work Packages n°1 and n°2

[2] IRAB Evaluation of CARE projects 2007

[3] IFPS Users Manual, Edition 12.3, November 2008

[4] ATFCM Users Manual, Edition 12.0, September 2007

[5] CFMU Flight Progress Messages, Edition 1.5, January 2008

[6] EUROCONTROL Standard Document for Data Exchange Presentation

(ADEXP), Edition 2.1, December 2001

9

1 INTRODUCTION

1.1 Brief overview of ABCD

The Aircraft Based Concept Developments (ABCD) project proposes to improve

flight predictability by linking individual flight plans using the same aircraft for a

given day through the aircraft registration information.

As an aid to flight plan management, the ABCD tool implemented with an airline

should:

- provide the airline with a better picture of aircraft operations on a daily

basis,

- help the airline to detect reactionary delays and to notify them to the CFMU

as early as possible by proposing a new EOBT.

The purpose of ABCD is twofold: on the one hand at a local level to decrease the

total delay of the airline (ATFM and reactionary delay) using an ABCD tool, and on

the other hand at a global level to optimize the use of the available ATC capacity.

1.2 Past achievements

In 2007, ADV Systems and ALG carried out together the description of the ABCD

concept and identified its potential benefits [1]. They stressed the following points:

• Qualitative (interviews and analyzed examples) and quantitative analyses

showed that the ABCD implementation could improve the traffic

predictability and bring tangible benefits to ATM stakeholders (airlines,

CFMU, airports).

• The interviews have established that the implementation of ABCD would

provide low-cost and regional airlines with an efficient tool to recalculate

automatically new EOBT for subsequent flights, using the same aircraft as an

initial delayed flight, once the delay on the initial flight has been detected

and found to be propagated throughout the subsequent flights. Those airlines

therefore consider that ABCD would facilitate and optimise the management

of delays and thus stated their interest in the ABCD concept

implementation.

• However, it has to be acknowledged that the ABCD concept implementation

should not be imposed to all aircraft operators as some of them, in particular

major airlines, have already in operation some tools whose scopes encompass

the ABCD functions and go far beyond the ABCD project objectives.

Moreover, in the case of major disruptions, those airlines have the ability

and the resources to swap aircraft for a given flight incurring too much

10

delay. Thus, they are reluctant to use an ABCD tool when they have their

own ABCD-like tool.

At the end of this first phase, it was decided to carry on the study in order to

undertake a precise analysis of the benefits brought by ABCD and to move on to the

tool development.

The second phase of the ABCD project which started at the beginning of 2008 and

which is planned to end in early 2009 is structured as a set of seven work packages

that develop, simulate and validate the ABCD concept. This study revolves around

two themes:

- the first one, which includes WP3, 4, 5, 6 and 7, focuses on ABCD ABCD ABCD ABCD

developmentdevelopmentdevelopmentdevelopment:

It aims first to assess, through a Cost Benefit Analysis, the economic viability of the

ABCD tool when implemented by an airline (typically a low-cost or regional

airline). In the same way, the technical implementation of an ABCD concept

requires to specify how this concept would technically fit with existing ATM

systems and especially the airline systems. In particular, the way information and

data from existing systems could be used in order to implement this concept, will be

analyzed and a concrete implementation model will be proposed. The study shall

therefore produce some functional and operational specifications which will help to

produce and develop an ABCD prototype PC based tool.

- the second axis, WP8 and WP9, focuses on the impact of the delay message impact of the delay message impact of the delay message impact of the delay message

anticipation on unused ATFM slotsanticipation on unused ATFM slotsanticipation on unused ATFM slotsanticipation on unused ATFM slots.

It was indeed stressed that the overall proportion of missed ATFM slots is not

negligible. And because the lack of anticipation was identified as a possible cause for

unused ATFM slots, and because an ABCD-like tool could improve the anticipation

of its users, a missed slot analysis was recommended in addition to the development

of ABCD [2]. The goal is to demonstrate that improving delay message anticipation

is beneficial to everybody, airspace users, as well as network management. In that

sense, it would point to the virtues induced at central level by the local use of a

distributed system like ABCD.

The set of Work Packages is presented below:

• WP3: Cost Benefits Analysis.

• WP4: ABCD tool prototype definition.

• WP5: ABCD tool prototype development.

• WP6: Tool upgrade at CFMU level.

• WP7: Final ABCD Report.

• WP8: Simulation definition for the unused ATFM slots study.

• WP9: Simulation results analysis for the unused ATFM slots study.

11

Results of Work Package 3 have been recently presented in the deliverable D3, and

the following conclusions were drawn:

� The total ATFM delay incurred by the airline would be lower if

delays were notified earlier than today;

� There is increased value to earn when the level of traffic is high, because 1) more flights are regulated and are in a position to benefit

from the use of ABCD and 2) more flights suffer from long ATFM

delays, which are more sensitive to the anticipation parameter;

� The relationship between ATFM delay reduction and anticipation for

one airline is nonlinear mainly because air transport is stochastic by

essence and the slot allocation mechanism depends on a wide range of

external parameters. As ATFM delays cannot be easily predicted,

benefits cannot be accurately assessed: two cases were therefore

analysed, including a worst-case assuming minimal gains, in order to

be as conservative as possible in the Cost Benefit Analysis;

� In all cases, benefits outstrip costs over the product lifecycle, even in the most adverse situation due to 1) small amount of investment

costs: ABCD is straightforward to develop, implement and operate

and is a standalone product designed to have the minimum impact on

the current environment and 2) ABCD yields substantial benefits

because of the cumulative daily delay reduction effect over the year

resulting from a continuous use of the tool.

Therefore it can be stated with a strong degree of confidence that an ABCD tool is

worth the investment.

The unused ATFM slots study (WP8 and WP9) was carried out in parallel with the

Cost Benefit Analysis, and the results were presented in the deliverables D8 and D9.

TACOT simulations have particularly demonstrated the following points:

� Improving anticipation of the notification of delay messages by

airlines could provide at central level (CFMU) reductions of 20% on

the number of lost slots, reduction on the total daily ATFM delay up

to 30% and decreases on the number of delayed flights by 15%.

� The recommendations drawn from the Analysis of Unused ATFM

Slots (“the sooner, the better”) were therefore validated: the earlier

the notification of delay messages to the CFMU, the lower the

number of unused ATFM slots, the lower the overall ATFM delay,

the better use of available ATM capacity while maintaining the same

level of overloads.

12

1.3 Purpose and scope of the document

The present deliverable (D4) is the result of WP4, intended to refine the description

of the ABCD concept and to specify it, building on last year’s achievements and

taking into account the recommendations from IRAB.

The specifications of the concept aim to drive the development of a prototype

(WP5) that will pave the way for a local implementation of the concept at the level

of a regional or low-cost airline.

The objectives of the present document are as follows:

� Recall the essence of the concept, the stakeholders interested in it and how they could benefit from it;

� Scope the future system as well as its possible implementation from an airline

perspective and define the environment interacting with the system: human

actors, various systems, information flows etc.;

� Define the elementary services provided by the system;

� Define the requirements that the system will have to fulfil in order to provide

these elementary services.

1.4 Document structure

ABCD first deliverables [1], released in 2007, defined the principles of ABCD. The

present deliverable (D4) intends to push further the concept definition. The

document is structured in three parts:

� Section 2 presents the ABCD tool, from the concept to the tool implementation

at airline level, and explains how ABCD could benefit the different ATM

stakeholders.

� Section 3 describes the environment of the ABCD tool at airline level, focusing

on the human actors and systems interfacing with ABCD, and then on the

current messages and data that will be managed by ABCD.

� Section 4 specifies the ABCD concept, providing requirements that will pave the

way for an ABCD prototype development.

13

2 ABCD CONCEPT

2.1 ABCD at a glance

2.1.12.1.12.1.12.1.1 ABCD ConceptABCD ConceptABCD ConceptABCD Concept

The ABCD concept, which is based on the linkage of individual flight plans

executed by a same aircraft, aims at using the flight planning and flight progress

information available for a given flight in order to detect as soon as possible

potential reactionary delay on the subsequent flights.

More precisely, the concept relies on data known by the airlines themselves such as

the aircraft schedule and the minimum turn-around time for each aircraft at each

airport, as well as on the various messages exchanged between airlines and the

CFMU. ABCD uses those data to monitor the propagation of a reactionary delay all

along a given aircraft journey and check if the flights can comply or not with their

current EOBT and possibly their ATFM slot. When a conflict with the current

flight schedule is detected, ABCD proposes an update of the EOBT.

The objectives underlying the concept are manifold:

1. Improve flight predictability and provide a better picture of operations in

real time.

2. Better anticipate reactionary delays, since they can be detected earlier on the

basis of the information available for the previous flight, and consequently:

3. Decrease the ATFM delay and optimize the efficiency of the ATFM slot

allocation process, which enables to:

4. Lessen the delay propagation on the subsequent flights, i.e. reduce

reactionary delays, and therefore better control the knock-on effects due to

an initial delay.

2.1.22.1.22.1.22.1.2 From the concept to the tool implementationFrom the concept to the tool implementationFrom the concept to the tool implementationFrom the concept to the tool implementation

The ABCD concept can be implemented through several strategies:

• Centralised iCentralised iCentralised iCentralised implementamplementamplementamplementation by tion by tion by tion by the the the the CFMUCFMUCFMUCFMU:

The FPL linkage would be centralised within the CFMU database, which would be

provided by airlines with aircraft allocation schedule, as well as minimum turn-

around times. By processing those data, the CFMU would be able to update the

downstream flight plans and to propose new EOBTs to airlines when delays would

have been detected.

The main advantage of this solution lies in the fact that the information is gathered

in a unique central point. However, this strategy is constraining for the CFMU since

14

it would be necessary to modify its database management and processes.

Furthermore, this solution raises juridical issues between CFMU and airlines

(liability for EOBT changes, etc.) which could not be resolved in the scope of the

present project.

� NOT RETAINED IN THE CURRENT SPECIFICATIONS

• Local iLocal iLocal iLocal implementation by airlines: mplementation by airlines: mplementation by airlines: mplementation by airlines:

In that case, the linkage of flight plans would be performed in the airlines’

operations centres. Each airline would be proposed an ABCD tool that would

monitor the delay propagation and calculate a new EOBT if the initial one is not

reachable because of the occurrence of delays. Airlines would then communicate to

the CFMU the new requested EOBTs through DLA messages.

This second strategy, which appears as the most appropriate and simple solution to

implement the ABCD concept, was the one retained to define the tool, given the

juridical and practical complications induced by the centralised implementation.

Furthermore, the requirements, albeit generic, are based on the premise that low-

cost or regional airlines would be the main users of the tool since they already

showed interest in the concept.

� RETAINED IN THE CURRENT SPECIFICATIONS

2.1.32.1.32.1.32.1.3 ABCD tool at airline levelABCD tool at airline levelABCD tool at airline levelABCD tool at airline level

The ABCD concept implementation therefore implies the design of an ABCD tool at

local level, i.e. a tool that is hosted by airlines (especially low-cost and regional

airlines) in the Airline Operations Centre.

The ABCD tool is basically a support system to flight plan management aimed to

assist the user (i.e. the aircraft operator in charge of flight planning) in the

management of DLA messages. As an aid to decision-making, ABCD proposes to the

user a new EOBT when the current EOBT of a flight can not be respected.

Therefore, ABCD provides the user with information enabling him to make a

decision on whether to notify delay messages or not to the CFMU. The tool can be

regarded as a complementary system to the existing flight management system of

the airline.

ABCD will be used on the day of operation to reconcile flight planning and ongoing

operations, through updated EOBT proposals. Thus from a one-flight perspective, it

will be mostly used during the tactical/operational phase, from the time the flight

plan is received and acknowledged by the CFMU till the time the flight is airborne.

It will also be used during the active phase of the flight, to update the next flight

plan on the aircraft schedule.

Like any information management system, ABCD will:

15

1.1.1.1. Receive information Receive information Receive information Receive information

The ABCD tool interfaces with the airline’s existing systems (ABCD input), which

provides ABCD with the messages exchanged between the airline and the CFMU,

possibly third parties like aerodromes. Those messages are particularly useful to

monitor the update of a flight plan and its execution. Other inputs of ABCD consist

of the aircraft schedule, the aerodrome taxi-times and the minimum turn-around

times.

2.2.2.2. Process informationProcess informationProcess informationProcess information

ABCD manages information thanks to an internal database which describes the

linkage of flight plans.

When a new message is received, ABCD extracts the relevant information from this

message and correlates it to a flight in order to update the database. The system

automatically checks if the subsequent flights are impacted or not by a possible

delay of a flight, and if they can comply with their current EOBT and possibly their

ATFM slot.

3.3.3.3. Provide information Provide information Provide information Provide information

The ABCD tool interfaces with the operator in charge of the DLA message

management and provides him with information that allows him to make a decision

on whether to send delay messages (DLA) with the relevant contents (new EOBT

proposal). This information is extracted from the database.

2.2 Stakeholders

Even if the tool will be implemented at airline level, many ATM stakeholders in

addition to the airlines may take advantage of the ABCD local implementation.

The present section therefore intends to provide an overview of the various

stakeholders potentially impacted by ABCD, and shows to what extent each one

could benefit from the concept.

2.2.12.2.12.2.12.2.1 Airlines Airlines Airlines Airlines

As private for-profit companies, airlines strive to satisfy their business objectives

and optimize their operations by determining the optimum flight departure and

arrival times as well as flights routes and levels. Therefore, a prerequisite to any

airline operations consists in convenient take-off, landing and over-flight rights.

This accounts for the importance given by airlines to slot allocation procedures.

16

Different kinds of airlines (flag carriers, low cost, charters) may have different

priorities but in general, the ability to operate to published schedules punctually

and efficiently is essential. These schedules involve a myriad of connecting and

interdependent flights and events. The resources (aircraft and flight-crew) used for

a particular flight form part of a continuous inter-connected process in which delay

can have a serious and growing effect on subsequent flights.

Most airlines place importance on punctuality since it directly contributes to the

image of the company and can be a selection criterion for the passengers. Therefore

airlines endeavour to decrease their delay.

How will ABCD impact this stakeholder?How will ABCD impact this stakeholder?How will ABCD impact this stakeholder?How will ABCD impact this stakeholder?

The ABCD client airline, as the direct user of the tool, is the prime stakeholder in

the concept. As ABCD enables optimizing the use of the available capacity, the

delay incurred by the airline will be reduced.

Moreover, as ABCD helps to control reactionary delays, improving the

predictability of aircraft operations, it should contribute to:

- A gain in ATFM delay due to a better anticipation of DLA messages.

- A reduction in reactionary delay resulting from a lower ATFM delay

incurred by the previous flight.

- The reduction of strategic delay, which is the long-term effect of lower

tactical delay, i.e. increased aircraft utilization.

ABCD will therefore impact the cost effectiveness of airlines operations.

2.2.22.2.22.2.22.2.2 ATFATFATFATFCCCCM Service Providers (CFMU)M Service Providers (CFMU)M Service Providers (CFMU)M Service Providers (CFMU)

In this study, ATFCM providers encompass CFMU along with FMPs. ATFCM main

objective is to contribute a safe, orderly and expeditious flow of air traffic by

ensuring that ATC capacity is used optimally, and that the traffic volume is

compatible with the capacities declared by the appropriate ATS authority.


ABCD would indirectly provide the CFMU with a better view of the traffic, and

therefore improve traffic predictability. Indeed, with the implementation of the

ABCD system, the slot allocation list could be updated earlier than with the current

system. It should consequently impact on the capacity by decreasing the number of

lost slots (i.e. slots that are allocated to an aircraft and that are eventually not used

by this one, or by another one, while they could have been), which will result in

less delay.

ABCD will therefore impact on the predictability and efficiency of network

operations.

17

2.2.32.2.32.2.32.2.3 ANSPs ANSPs ANSPs ANSPs –––– AT AT AT ATS Providers (incl. Airport Towers)S Providers (incl. Airport Towers)S Providers (incl. Airport Towers)S Providers (incl. Airport Towers)

ATC’s main goals are to prevent collisions between aircraft and to expedite and

maintain orderly flow of air traffic while maximizing the use of available capacity.


ATC will benefit at both local and network level. ABCD will provide a better

picture of future traffic flows, improving its management through a better

anticipation of the future ATFM regulations, and better slot management (reduction

of unused ATFM slots). In the long term Air Traffic Control Centres will improve

the balance between their resource allocation and their capacity regarding the

traffic demand as a consequence of the increased confidence in the predictability of

traffic flows.

ABCD could therefore impact on the predictability of ATC operations.

2.2.42.2.42.2.42.2.4 Airport Airport Airport Airport –––– Ground handlers Ground handlers Ground handlers Ground handlers

“Airport” encompasses the different partners at the airport responsible for the

management of the airlines’ turn around activities (i.e. ground handlers).

Each airline has “agents” (airlines’ staff or other staff – ground handlers to which

the tasks are subcontracted), at the airport responsible for the disembarkation and

boarding of the passengers, baggage handling, refuelling, safety checks on aircraft,

etc.

These agents strive to manage their activities and to comply as much as possible

with the “scheduled” flights’ program, the one “sold to the clients”.

Punctuality is objective n°1 of the agents. In case of delays, the procedures to

manage the delays could be different depending on the strategy of the airlines, but

most of them share a common objective: come back to the scheduled flights’

program. This could imply flights’ cancel or aircraft’s permutation strategies, if a

delay implies a risk of significant propagation.

How will ABCD impactHow will ABCD impactHow will ABCD impactHow will ABCD impact this stakeholder? this stakeholder? this stakeholder? this stakeholder?

Ground Handler will be able to improve the use of their resources, saving costs and

providing an improved level of service;

Airport Operator will be able to improve service provision to their customers

through better resource allocation as they could be informed a long time in advance

of the future potential disruption in terms of flight plan schedule consistency. This

applies both at the tactical level, through stability in gate/stand allocation, as well as

at the strategic level, as better use of infrastructures supports greater passenger

throughput. Airports should also be able to provide better information to their

customers. Overall, the airport quality of service should be enhanced.

18

ABCD would improve the parking slot allocation process at the airports and would

enable a better management of this process.

ABCD could therefore impact on the predictability and efficiency of airport

operations.

2.2.52.2.52.2.52.2.5 PassengersPassengersPassengersPassengers

The passengers may be impacted by the flight planning process, even if they do

know neither its existence nor its mechanism. This process creates indeed ATFM

delays, and therefore contributes to degrade the airline punctuality. Owing to a

weighty delay, passengers may complain to the company and demand a

compensation for the delay. Even worse, the delay could impair the passenger’s

view on the airline and make him decide to change operator.


With the use of ABCD, customer satisfaction will increase as the hassle created by

1/ delays and 2/ the lack of information will be reduced (through 1/ lower ATFM

delays 2/ the improved predictability of operations at the departure/destination

airport).

19

3 ABCD ENVIRONMENT

This section aims at depicting the environment in which ABCD will be

implemented, and more precisely at presenting the human actors, the systems

interfacing with the ABCD tool, as well as the operational data handled by the

ABCD tool.

3.1 Human Actors

First are described the human actors currently involved in the flight planning

processes that will potentially interface with the ABCD tool.

3.1.1 Airline Operations Centre Staff

The Airline Operations Centre (AOC) is basically the company’s operational focal

point for coordination and control of flights’ programme. Activities such as aircraft

assignment, schedule, flight planning, ATFM slot management and flight tracking

are usually performed in any AOC. However, the importance given to each activity

depends on the size and type of company (major/ low-cost). For instance, flight

tracking may be reduced to the monitoring of the aircraft actual take-off times.

Furthermore, the number of people in charge of those tasks may completely differ

from an airline to another one: in major airlines there are units specific to each

activity, whereas in smaller companies only one or two persons can be responsible

for several tasks. ABCD as an aid to decision-making for flight plan update will

provide information to the person(s) managing flight plans, who usually notifies

delays, cancels flights, etc. This or these person(s) will be designated by “AOC staff”

in the rest of the document.

What is their role regarding ABCD?

The AOC staff is the system user. The incumbent staff will directly interface with

ABCD. On the one hand, ABCD will warn the user and display the relevant

information when a delay is detected. On the other hand, ABCD will warn the user

in case of missing data in the airline database (in particular data related to the

minimum turn-around time, taxi-time and to the aircraft schedule).

20

3.2 System actors

This section describes the systems that interface with ABCD (directly or indirectly).

3.2.1 Flight Management System

The AOC system responsible for the messages exchange with the CFMU is

designated by “Flight Management system” as it can be very different from an

airline operator to another one, especially between major airlines and low-cost

carriers. Since ABCD will interest mainly budget or regional airlines, the intended

system corresponds to the ones of these types of airlines.

Low-cost, budget, no-frills airlines have generally a very “light” Flight Management

System. As an example:

- Ryanair notifies delays to the CFMU as soon as possible, using only DEP

messages sent by the departure airport.

- Euro Air uses the MVT message sent by the handling company to the

airport to track its flights. They wait till EOBT+10 before sending DLA

message.

What is its What is its What is its What is its role regarding ABCDrole regarding ABCDrole regarding ABCDrole regarding ABCD? ? ? ?

This system will act on the one hand as message message message message transmittransmittransmittransmitterterterter for ABCD, and on the

other hand as data providerdata providerdata providerdata provider (in particular ABCD will be provided with the aircraft

allocation schedule, taxi-time and the minimum turn-around time stored in the

airline system database).

Therefore, the airline’s current system will only play a role of proxy vis-à-vis

ABCD: it will forward to the tool all the messages it has already received from third

parties or exchanged internally, and will also provide data contained in its own

database.

3.2.2 CFMU Systems

The role of the EUROCONTROL Central Flow Management Unit (CFMU) is to

ensure safety and efficiency of all flights by facilitating the management of the

network.

The Central Flow Management Unit primarily provides three operational services:

- Airspace Data Management;

21

- Flight Plan Processing Service, provided by the Integrated Initial Flight

Plan Processing System (IFPS);

- Air Traffic Flow and Capacity Management (ATFCM), whose tool is the

CFMU Enhanced Tactical Flow Management System (ETFMS)

IFPS and ETFMS are described below since they exchange messages with the

airline, and therefore play indirectly a role in ABCD implementation.

� IFPSIFPSIFPSIFPS ---- Integrated Initial Flight Plan Processing System Integrated Initial Flight Plan Processing System Integrated Initial Flight Plan Processing System Integrated Initial Flight Plan Processing System

The IFPS provides a centralized flight plan processing and distribution service for all

IFR GAT flights within the CFMU area.

This system ensures that accurate and consistent flight plan data are available to all

concerned ATSUs and the centralized ATFCM function.

Description of IFPS:

Flight plans (repetitive or singly filed) and associated messages are received by the

IFPS. These messages are checked against a substantial number of static syntactical

and semantic requirements, and the dynamic airspace infrastructure. When

necessary, flight plan messages are submitted for manual processing by IFPS

operators. Flight plan message originators are advised of the status of their messages

via operational reply messages. Processed flight plan messages are subsequently

distributed to the concerned ATS units and to ETFMS.

� ETFMS ETFMS ETFMS ETFMS ---- CFMU Enhanced Tactical Flow Management System CFMU Enhanced Tactical Flow Management System CFMU Enhanced Tactical Flow Management System CFMU Enhanced Tactical Flow Management System

The main tool for ATFCM is ETFMS, a system used by the OPSD and FMPs for

Tactical operations. ETFMS receives data from IFPS, ATC, airline, CDM Airports

and the ENV Systems. Its main missions are the Slot allocation and aircraft

rerouting.

Description of ETFMS:

The Tactical system (ETFMS) contains flight data for the following forty-eight

hours. Initially, it is fed with RPL for that period and later with Flight Plan

Messages in order to present the best picture of air traffic demand. This data is later

updated by ATC information on the actual flight situation or any change to the

initial flight plan (e.g. new route).

The tools for exploiting this data allow examination of the anticipated air traffic

demand for the following day. Aircraft Operators (AOs) and Flow Management

Positions (FMPs) can access the database via a terminal.

22

The ETFMS System has the following sub-functions (Figure 1):

a) Environment Data Capture and Processing

All the basic elements of the ATC environment such as airports, routes, sectors,

capacities are known to the ETFMS and sometimes dynamic updates (e.g. runway

configuration).

b) Flight Data Capture

Merging of long-term data provided by RPL and up-to-date information provided

by IFPS or by CDM Airports.

c) Profile Calculation

For each flight a 4D profile is calculated, taking into account the above 2 sets of

information.

d) Load Calculation

At any point, aerodrome, set of aerodromes, airspace volume or traffic volume. This

is expressed as a number of flights per unit of time (usually one hour) entering an

airspace volume, overflying a point, departing from/arriving at an aerodrome/set of

aerodromes or part of a traffic volume or of one of its flows.

e) Rerouting

Certain facilities exist in the ETFMS (system to simulate the consequences for the

ATFCM/ATC system of rerouting individual flights or groups of flights. The impact

on loads in affected areas is consequently re-calculated.

f) Human Machine Interface

For the display and input of information used or generated by flow managers, ATC

controllers, Aircraft Operators and pilots, i.e. an important part of the ETFMS

system concerns the input and display of the various data previously mentioned

(flight data loads at sectors, overload warnings, etc., …).

This also includes command displays, by means of which the flow manager activates

the ATFCM measures (e.g. CASA - restrictions and rerouting) and monitoring

facilities.

g) The Exchange of Messages

This is an important part of the ETFMS system involving complex address selection

and message routing mechanisms.

h) The Computer Assisted Slot Allocation (CASA)

The algorithm is at the very heart of the interaction between the ETFMS system

and ATC. Traffic volumes to come under CASA control are activated by the flow

manager. This means that he defines a traffic volume, start time, end time and many

other parameters. ETFMS then extracts all flights which are concerned by this

activation, in other words those flying at that location (within that flight level slice)

23

during that restricted period and passes them onto the "CASA algorithm" for

departure time calculation.

Figure Figure Figure Figure 1111;;;; ETFMS functionsETFMS functionsETFMS functionsETFMS functions

The CASA System is largely automatic and centralised, and functions from an

Aircraft Operator’s point of view in passive mode. In other words, the act of filing a

flight plan effectively constitutes a request for a slot. FMPs and CFMU agree on

those locations where ATFCM Measures are necessary. As a consequence the CFMU

activates regulations within ETFMS including the start and the end times, the

description of the location, the entering flow rate and some other parameters.

The system extracts all the flights entering for the specified airspace and sequences

them in the order they would have arrived at the airspace in the absence of any

restriction. On this basis, the Take-Off Time (TOT) for the flight is calculated. It is

this information, Calculated Take-Off Time (CTOT), which is transmitted to the

Aircraft Operator concerned and to the control tower at the aerodrome of

departure. In addition to this fundamental process, a number of other mechanisms

will act to compensate for factors such as late received flight plans and

modifications thereto.

What is their role regarding ABWhat is their role regarding ABWhat is their role regarding ABWhat is their role regarding ABCDCDCDCD? ? ? ?

ABCD and the CFMU will not interface directly, but to some extent indirectly

through the airline’s other systems. On the one hand, some messages sent by the

IFPS (ACK) and the ETFMS (SAM, SRM …) will be used by ABCD. On the other

24

hand, in case of delay, the EOBT calculated by ABCD will be notified to the CFMU

through the airline operation centre.

3.3 Messages & Data

In the previous sections, the different actors (human and system) interfacing with

ABCD were described. Those actors, especially the airline flight plan management

system, will transmit ABCD messages containing elementary data necessary to the

tool. The present section therefore focuses on the different messages and associated

data that ABCD will have to handle, and also presents the current operational

context associated to the use of those messages. The other data used by ABCD but

not conveyed via messages are also described in the last part of the section.

3.3.13.3.13.3.13.3.1 Types of messages managed by ABCDTypes of messages managed by ABCDTypes of messages managed by ABCDTypes of messages managed by ABCD

There are basically three kinds of messages that ABCD will have to manage. Those

messages are exchanged between the airline, the CFMU and possibly third parties:

- Flight Planning messagesFlight Planning messagesFlight Planning messagesFlight Planning messages (FPL, RPL, ACK (FPL, RPL, ACK (FPL, RPL, ACK (FPL, RPL, ACK, DLA, CHG, CNL, REA, DLA, CHG, CNL, REA, DLA, CHG, CNL, REA, DLA, CHG, CNL, REA)))): to file or

update a flight plan and have the initial flight plan validated by IFPS;

- ATFM messagesATFM messagesATFM messagesATFM messages (SAM, SRM (SAM, SRM (SAM, SRM (SAM, SRM, SLC, SLC, SLC, SLC)))): to notify the ATFM measures a flight is

subject to (if any) and update them whenever necessary;

- Flight Progress messagesFlight Progress messagesFlight Progress messagesFlight Progress messages (DEP, ARR, FUM)(DEP, ARR, FUM)(DEP, ARR, FUM)(DEP, ARR, FUM): to update the interested parties

on the progress of an active flight.

3.3.23.3.23.3.23.3.2 Elementary data associated to messagesElementary data associated to messagesElementary data associated to messagesElementary data associated to messages

Those messages exchanged by the airline with the CFMU and third parties contain a

certain number of elementary data, which will feed the database handled by ABCD:

� Flight Flight Flight Flight ARCIDARCIDARCIDARCID::::

Identification of a flight. This data is composed of 3 letters which characterize the

airline (ICAO designator), plus at most 4 figures.

� ARCTYPARCTYPARCTYPARCTYP::::

ICAO designator for the aircraft type

� EOBT (Estimated OffEOBT (Estimated OffEOBT (Estimated OffEOBT (Estimated Off----Block Time): Block Time): Block Time): Block Time):

Estimated time at which an aircraft starts to move from its parking stand. This

information is related with departure.

25

� ADEP (Aerodrome of Departure):ADEP (Aerodrome of Departure):ADEP (Aerodrome of Departure):ADEP (Aerodrome of Departure):

ICAO designator for the aerodrome of departure

� ADES (Aerodrome of Destination):ADES (Aerodrome of Destination):ADES (Aerodrome of Destination):ADES (Aerodrome of Destination):

ICAO designator for aerodrome of destination

� CTOT (Calculated TakeCTOT (Calculated TakeCTOT (Calculated TakeCTOT (Calculated Take----Off Time):Off Time):Off Time):Off Time):

Time at which an aircraft is allowed to take-off in case of the issuance of a

regulation. This information is sent to an airline via a SAM (or SRM) at the earliest

two hours before EOBT. airline/ATC are responsible for complying with it.

� TTLEETTTLEETTTLEETTTLEET (Total Estimated Elapsed Time): (Total Estimated Elapsed Time): (Total Estimated Elapsed Time): (Total Estimated Elapsed Time):

Estimated duration of a flight

� ELDT (Estimated Landing Time): ELDT (Estimated Landing Time): ELDT (Estimated Landing Time): ELDT (Estimated Landing Time):

Estimated time at which an aircraft is supposed to land. This information is

contained in the FUM messages whose purpose is to provide interested parties

(mainly the ADES, possibly the airline) with an estimated landing time.

3.3.33.3.33.3.33.3.3 Current operational context associated to messagesCurrent operational context associated to messagesCurrent operational context associated to messagesCurrent operational context associated to messages

Each type of messages can be correlated to a number of operational events that will

trigger the update of the ABCD database:

� Flight Planning messages Flight Planning messages Flight Planning messages Flight Planning messages

Event n°1:Event n°1:Event n°1:Event n°1: RPL submission (EOBT RPL submission (EOBT RPL submission (EOBT RPL submission (EOBT----20h):20h):20h):20h): The flight RPL, if it exists, is automatically

converted into a FPL.

Why is it a milestone for ABCD?

The flight becomes visible to ABCD.

Event n°2:Event n°2:Event n°2:Event n°2: FPL submission (Before EOBT FPL submission (Before EOBT FPL submission (Before EOBT FPL submission (Before EOBT----3h):3h):3h):3h): The flight FPL is sent by the airline

to the CFMU (if there is no RPL associated to the flight).


The flight becomes visible to ABCD.

Event n°3:Event n°3:Event n°3:Event n°3: FPL FPL FPL FPL vvvvalidation (alidation (alidation (alidation (ACK message ACK message ACK message ACK message sent after an FPL): sent after an FPL): sent after an FPL): sent after an FPL): The FPL is accepted by

the CFMU.


The flight is inserted into the ABCD database.

26

Event n°4:Event n°4:Event n°4:Event n°4: EOBTEOBTEOBTEOBT uuuupdate (pdate (pdate (pdate (After an FPLAfter an FPLAfter an FPLAfter an FPL): ): ): ): The EOBT can be updated thanks to DLA

or CHG messages (to notify a delay), or else thanks to REA (when a regulated flight

is ready to leave before its CTOT).


The ABCD database takes into account any change in the EOBT in order to check if

it impacts or not on the following flights.

Event n°Event n°Event n°Event n°5555:::: Flight Flight Flight Flight ccccancellation (After an FPL): ancellation (After an FPL): ancellation (After an FPL): ancellation (After an FPL): A flight plan can be cancelled thanks

to a CNL message.


The flight is removed from the ABCD database.

� ATFM messages ATFM messages ATFM messages ATFM messages

Event n°Event n°Event n°Event n°6666:::: Slot allocation Slot allocation Slot allocation Slot allocation –––– SAM SAM SAM SAM (EOBT(EOBT(EOBT(EOBT----2h): 2h): 2h): 2h): From that time on, a flight is allocated

a slot as soon as it is regulated by ATFM measures


The CTOT, when it exists, is taken into account by the tool to check that the

aircraft can make its slot.

Event n°Event n°Event n°Event n°7777:::: S S S Slot revision lot revision lot revision lot revision –––– SRM SRM SRM SRM (between EOBT(between EOBT(between EOBT(between EOBT----2h and CTOT2h and CTOT2h and CTOT2h and CTOT –––– min (TRS; TIS)min (TRS; TIS)min (TRS; TIS)min (TRS; TIS)1111 ––––

taxitaxitaxitaxi----timetimetimetime): ): ): ): The ATFM slot may be changed at any time: it can be as well improved

as downgraded.


If the slot improvement is significant, it may happen that an aircraft is no longer in

a position to comply with it (due to the reactionary delay predicted by ABCD),

whereas it could adhere to it before revision. Slot revisions are therefore constantly

monitored by the tool.

Event n°Event n°Event n°Event n°8888:::: Slot frozenSlot frozenSlot frozenSlot frozen (CTOT (CTOT (CTOT (CTOT---- min (TRS; min (TRS; min (TRS; min (TRS; TIS) TIS) TIS) TIS) –––– taxi taxi taxi taxi----timetimetimetime):):):): From that time on, the

slot of the flight is “frozen” and cannot be changed anymore (neither improved, nor

downgraded).


At that time, the predictions made by ABCD regarding the potential reactionary

delay of the following flight will become more accurate and more stable. Therefore

an EOBT proposed by the tool is more likely to remain valid. The timeliness and

trustworthiness of the proposals submitted by the tool are important for the sake of

1 Cf. definition of TRS and TIS in section 3.3.5

27

users’ acceptability. They are taken into account in the specifications, when

defining the preconditions triggering EOBT proposals.

� Flight Progress messagesFlight Progress messagesFlight Progress messagesFlight Progress messages

Event n°7: Flight execution (Flight execution (Flight execution (Flight execution (FromFromFromFrom taketaketaketake----offoffoffoff):):):): From that time on, the flight, regulated

or not, is active in ETFMS, which then receives (and sends) flight progress messages

to monitor the flight execution.


The planning phase is over. Nevertheless the monitoring task will remain active

until flight termination and flight progress messages received by the CFMU (e.g.

FUM) or by third parties (e.g. DEP) will be used by the tool to make a better

prediction for the reactionary delay of the following flight.

Event n°8: Flight terminationFlight terminationFlight terminationFlight termination (ARR message). The flight is over.


The flight will be removed from the ABCD database.

3.3.43.3.43.3.43.3.4 Messages descriptionMessages descriptionMessages descriptionMessages description

Table 1 summarizes the set of messages that could be managed by ABCD and

provides for each one: the type of message, the sender, the recipient, the event

triggering the message, the message purpose, the information that will be extracted

by ABCD, its impact on the ABCD database, and miscellaneous comments.

More information may be found in [3] for flight planning messages, [4] for ATFM

messages and [5] for flight progress messages.

Detailed information about the format (ADEXP format) and the message structure

are annexed to the document (cf. Annex 1)

28

Title Type of message Sent by Sent to Triggering event Role Extracted

Information Impact on

ABCD database Miscellaneous

FPL Flight planning

airline CFMU Submit a Flight Plan to the CFMU

A/C ARCID, TTLEET, EOBT

Followed by ACK man or REJ

ACK Flight planning CFMU airline Validation of a FPL by the CFMU Acceptance of a Flight Plan A/C ARCID Insertion of the

flight in database The airlines should wait for it before sending any other messages

RPL Flight planning

airline CFMU Submit Flight plans for a series of flights which have identical features

Not directly managed by ABCD

Converted into FPL 20 hours before EOBT

DLA Flight planning

airline CFMU A flight will not be able to meet its previous EOBT

Notify a delay to the CFMU A/C ARCID, EOBT

Change the EOBT

- New EOBT > Previous EOBT - New EOBT > msg timestamp - New EOBT no more than 20 hours in the future.

CHG Flight planning

airline CFMU A flight wants to change its flight path

Notify any change compared to the flight plan

A/C ARCID, EOBT, TTLEET

Change the EOBT

CNL Flight planning

airline CFMU Cancel a flight Remove a flight

REA Flight planning

airline via ATC

CFMU Notify to the CFMU that a regulated flight is ready to leave

A/C ARCID, timestamp

Change the EOBT Is not directly sent by the airline, which has to ask local ATC

SAM ATFM CFMU airline Assign a slot to a regulated aircraft

A/C ARCID, CTOT Change the CTOT airline gets a slot at the earliest 2 hours

before EOBT

SRM ATFM CFMU airline The slot of an aircraft has been improved by more than 5 minutes

Assign a slot to a regulated aircraft

A/C ARCID, NEWCTOT Change the CTOT

SLC ATFM CFMU airline Change of regulation parameters, When a slot is missed, After a CNL (cancelled reg)

Slot no longer subject to ATFM measures A/C ARCID Remove the CTOT

FLS ATFM CFMU airline Often after a SMM (Slot Missed Message) Suspend a flight till DLA/CHG A/C ARCID CTOT/EOBT =

+infinite?

FUM Flight progress

CFMU ADES, (Airlines)

- Modification of ELDT > 5 min - Change of the flight status

Give an estimation of the landing time

ELDT Change the ELDT Is sent at the earliest 3 hours before landing time

DEP Flight progress

ADEP CFMU Take-off Activates the flight plan TO time Change the ELDT May not be used by ABCD (sent to the CFMU)

ARR Flight progress

ADES CFMU On landing Allows the flight plan to be closed

Landing time Change the ELDT May not be used by ABCD (sent to the CFMU)

Table Table Table Table 1111: Messages : Messages : Messages : Messages potentially potentially potentially potentially handled by ABCD (depending on current airline message inhandled by ABCD (depending on current airline message inhandled by ABCD (depending on current airline message inhandled by ABCD (depending on current airline message interchange)terchange)terchange)terchange)

29

3.3.53.3.53.3.53.3.5 Other data managed by ABCDOther data managed by ABCDOther data managed by ABCDOther data managed by ABCD

ABCD will also rely on two other information types which are not part of the

standard messages, but nevertheless valuable for ABCD database update. Those data

are described below:

ARN (Aircraft Registration Number): ARN (Aircraft Registration Number): ARN (Aircraft Registration Number): ARN (Aircraft Registration Number):

Unique alphanumeric string that identifies an aircraft

� This data will be used to link flight plans together.

Taxi Time: Taxi Time: Taxi Time: Taxi Time:

Average time an aircraft is supposed to taxi from its parking stand to the runway.

This information is contained in the CFMU environment database which defines a

standard value for each airport, ranging from 0 to 20min. Taxi times are part of

ATFM messages such as SAM or SRM but are not part of Flight Planning Messages

such as FPL. This is why taxi times are regarded as “other data”.

TTM (Minimum Turn Around Time) (for a given airport and a given type of TTM (Minimum Turn Around Time) (for a given airport and a given type of TTM (Minimum Turn Around Time) (for a given airport and a given type of TTM (Minimum Turn Around Time) (for a given airport and a given type of

aircraft):aircraft):aircraft):aircraft):

Minimal time needed by the aircraft to complete turn-around operations at the

airport. It includes activities such as refuelling, baggage handling, boarding and

deplaning of passengers, etc.

The “TTM” is a time window between the “in-block” time of a flight N-1 and the

“off-block” time of a flight N.

Depending on the aircraft type, the TTM may vary from 20 minutes (case of

narrowbodies) to up to one hour and a half (case of widebodies). For example, when

the aircraft is of the “Heavy” type (e.g. Boeing 747), the airlines have to define a

“TTM” of more than one hour.

� This data will be used to calculate the minimum time at which an

aircraft is able to leave its block.

TRS (TimTRS (TimTRS (TimTRS (Time to Remove from e to Remove from e to Remove from e to Remove from the the the the Sequence) and TIS (Time to Insert Sequence) and TIS (Time to Insert Sequence) and TIS (Time to Insert Sequence) and TIS (Time to Insert into thinto thinto thinto theeee

Sequence):Sequence):Sequence):Sequence):

Those parameters can be defined for each aerodrome, with a default value of 5min

for the TRS and 10min for the TIS. They are used by the CFMU as timeout values to

“freeze” the slot allocation for an a/c close to depart, hence prevent a late change of

CTOT and achieve stability.

� The Time to Remove from the Sequence (TRS) prevents a change to a later

CTOT when the flight is already in the departure sequence.

30

� The Time to Insert into the Sequence (TIS) prevents an improvement into

an already organised departure sequence.

� Those data will be used as criteria of stability in the ABCD system in

order to provide to the user with accurate information.

Figure 2 gives the general view of the ABCD environment:

Figure Figure Figure Figure 2222: The ABCD environment: The ABCD environment: The ABCD environment: The ABCD environment

Assistance in DLA management

ABCD

Flight Management System

AIRLINE

CFMU : - IFPS - ETFMS

Provision of messages and data

AOC Staff

Monitoring of flight Planning & Execution Message

Exchange

31

4 ABCD REQUIREMENTS

4.1 Foreword

This section addresses the requirements of the ABCD tool at three different levels:

- Requirements linked to the human actors;

- Requirements linked to the system actors;

- Requirements internal to the ABCD tool.

Requirements are of three types:

- Operational services, defining the services that ABCD shall provide to the

user;

- Functional requirements, defining what ABCD shall do in order to

provide those services. They define the functions and sub-functions that

shall be implemented in order to achieve the goals of the operational

services;

- Non-functional requirements, defining how ABCD should fulfil the

functional requirements.

Each requirement is assigned an identifier which consists of a designator providing

information on the type and features of the requirement, plus a reference number.

The designator is a string made of the following abbreviations:

- Fn refers to a functional requirement

- Non_Fn refers to a Non-Functional requirement

- User_If refers to a requirement related to the User Interface

- Syst_If refers to a requirement related to the System Interface

- Int refers to an internal requirement

- Trig refers to a requirement triggered by an event (e.g. another

requirement)

- Cont to refer to a requirement continuously performed by ABCD

Some requirements are dependent upon others (for instance a function may be

triggered by or trigger another function). The dependencies related to each

requirement are identified after the requirement definition. A list of

functional/non-functional requirements as well as a matrix of dependencies may be

found in annex 2.

4.2 Requirements related to Human Actors

4.2.14.2.14.2.14.2.1 Operational ServicesOperational ServicesOperational ServicesOperational Services

ABCD can be regarded as a basic decision-making support system aiming at the

optimization of flight planning management. This system:

� Accesses all the flight planning and flight progress information available to

the airline;

� Processes the relevant information;

32

� Provides the user (i.e. the operator in charge of flight planning) with

information that allows him to make a decision on whether to update a flight

plan or not.

Therefore, ABCD in the broadest sense fulfils the following highhighhighhigh----level servicelevel servicelevel servicelevel service:

Provide assistance to flight planning

The assistance to flight planning provided by ABCD is directed towards one item of

the flight plan: EOBT. The EOBT is updated thanks to a delay message (DLA) sent

to the CFMU. In that sense, ABCD provides the user with a ffffirstirstirstirst operational service operational service operational service operational service

that can be defined as follows:

Op. Service n°1: ABCD shall assist the user in DLA management

To assist the user in the management of DLA messages for a given flight, ABCD

basically provides the user with information on the reactionary delay that this flight

is likely to incur. The provision of information defines a first service level (Level 0)

for ABCD. It is then possible to upgrade that service and define enhanced service

levels (Level 1 and 2) that progressively enrich the DLA management function.

Ultimately, the DLA management function could be more automated (Level 3 and

4).

However the specifications proposed below will only cover service levels 0, 1, 2 and

3. Level 4 is only proposed to exhaust all the possibilities opened up by the concept.

The implementation of level 4 (full automation of the DLA management function)

is currently not anticipated, due to legal impediments. For the time being, any flight

plan update shall result from a human decision.

The five service levels and their basic operating principles are presented hereunder:

DLA management DLA management DLA management DLA management sssservice ervice ervice ervice llllevel 0: Monitoring Service [Evaluate reactionary delays] evel 0: Monitoring Service [Evaluate reactionary delays] evel 0: Monitoring Service [Evaluate reactionary delays] evel 0: Monitoring Service [Evaluate reactionary delays]

(specified)(specified)(specified)(specified)

At level 0, ABCD only offers a monitoring service allowing the user to track

reactionary delays through the provision of a key piece of information: the EPOBT

(Earliest Possible Off-Block Time) of each flight.

The EPOBT is defined as the minimum off-block time an aircraft is able to make.

This time estimate is a prediction made by ABCD on the basis of the information

available for the previous flights executed by the same aircraft (in particular the

expected arrival time and the minimum turn-around time).

33

It is then up to the user to control the current EOBT (and/or CTOT) and reconcile it

with the EPOBT in case of inconsistencies;

� ABCD displays the last update of the Earliest Possible Off-Block Time

(EPOBT) calculated by taking into account the minimum turn around time

and the expected arrival time of the previous flight.

� ABCD also displays the current EOBT, as well as the current CTOT if the

flight is regulated, in order to know if it will be possible to comply with it.

DLA management Service Level DLA management Service Level DLA management Service Level DLA management Service Level 1: 1: 1: 1: Control & Control & Control & Control & Advisory Advisory Advisory Advisory ServiceServiceServiceService [Detect critical [Detect critical [Detect critical [Detect critical

reactionary delaysreactionary delaysreactionary delaysreactionary delays2222 and propose flight and propose flight and propose flight and propose flight plan plan plan plan update update update update]]]] (specified) (specified) (specified) (specified)

In addition to the service provided at level 0, ABCD at level 1 also provides a

control and advisory service through the detection of inconsistencies between the

flight EPOBT and the current EOBT/CTOT.

ABCD automatically evaluates the EPOBT against:

� EOBT + 15 min if the flight is not regulated;

� CTOT – taxi-time + 10 min and EOBT + 15 min if the flight is regulated.

Indeed, a flight has to comply with its EOBT, according to a tolerance window of -

/+15min. In addition, a regulated flight has to comply with its CTOT, according to a

tolerance window of -5/+10min.

If a flight cannot respect the tolerance window, a message providing a new EOBT

has to be sent to the CFMU by the airline. Therefore, the tolerance windows have

to be taken into account by ABCD to detect critical reactionary delays and make

new proposals.

In case of inconsistencies, the user is warned: the ABCD system proposes a new

EOBT to the operator. The new EOBT is a priori the current EPOBT (maybe with a

tolerance margin, to be defined).

DLA management Service Level DLA management Service Level DLA management Service Level DLA management Service Level 2222: Conditional : Conditional : Conditional : Conditional Control & Control & Control & Control & Advisory Service [Check Advisory Service [Check Advisory Service [Check Advisory Service [Check

information timeliness] (specified)information timeliness] (specified)information timeliness] (specified)information timeliness] (specified)

2 A reactionary delay is said to be critical if it conflicts with the current flight schedule i.e. if the flight is unlikely to make its EOBT (and/or CTOT).

34

ABCD at level 2 provides a conditional control and advisory service in addition to

the service provided at level 1: ABCD does not automatically warn the user as soon

as a critical reactionary delay is detected:

ABCD now tests stability/confidence criteria before proposing a new EOBT for

flight N, in order to provide stable updates:

RRRRule wule wule wule when flight Nhen flight Nhen flight Nhen flight N----1 is not regulated1 is not regulated1 is not regulated1 is not regulated

If flight N-1 is delayed and flight N is impacted, ABCD will wait till EOBT (N)-T1 to

warn the operator. This parameter T1 could be adjusted by the user. It was deemed

necessary given that before there could be too much uncertainty to send a DLA

message for the second flight. The default value could be 2h15 because previous

studies have shown that there may be no point in anticipating more than 2 hours.

Furthermore, a regulated flight receives a SAM 2 hours before departure. Therefore

it would be better to notify the flight update before the slot (if any) is assigned. A

margin of 15min is left to send the DLA message once a proposal is submitted by

ABCD.

RRRRuleuleuleule when flight N when flight N when flight N when flight N----1 is regulated1 is regulated1 is regulated1 is regulated

If flight N-1 is regulated, the slot will not be taken into account by ABCD until it is

frozen: ABCD will wait till CTOT (N-1)-T2. This timeout parameter T2 could be

adjusted by the user. The default value could be {taxi-time + min (TRS; TIS)}

because it is related to the standard timeout parameter used by the ATFM system to

improve slots. However last-minute improvements can be triggered in some cases3.

A conservative value for T2 would therefore be {taxi-time} or even zero.

- Before CTOT (N-1)-T2, the first rule will apply as if the flight was not

regulated, taking into account EOBT (N-1) to derive EPOBT (N) and warn

the user in case of inconsistency with EOBT (N)/CTOT (N).

- After CTOT (N-1)-T2, CTOT (N-1) will be taken into account to derive

EPOBT (N) and warn the user in case of inconsistency with EOBT (N)/CTOT

(N).

ABCD proposes a new EOBT to the operator when those stability criteria are

satisfied.

DLA management DLA management DLA management DLA management Service Service Service Service Level Level Level Level 3333: : : : DLA Message Preparation DLA Message Preparation DLA Message Preparation DLA Message Preparation Service [Prepare DLA Service [Prepare DLA Service [Prepare DLA Service [Prepare DLA

messages] (specified)messages] (specified)messages] (specified)messages] (specified)

3 E.g. in the slot may be improved when a REA (ready) message is sent at short notice by ATC on behalf of flight N-1 because it is ready to depart.

35

In addition to the service provided at level 2, ABCD at level 3 automatically

prepares DLA messages formatted according to the ADEXP standard and proposes

them to the operator.

DLA managementDLA managementDLA managementDLA management ServiceServiceServiceService Level Level Level Level 4444: DLA : DLA : DLA : DLA NotificationNotificationNotificationNotification Service [Prepare and send DLA Service [Prepare and send DLA Service [Prepare and send DLA Service [Prepare and send DLA

messages] (unspecified)messages] (unspecified)messages] (unspecified)messages] (unspecified)

At that level, DLA messages would be sent directly by the system to the CFMU.

This would correspond to a full automation of the DLA management service

provided by ABCD.

To provide the airline with some flexibility regarding the use of the ABCD tool, a

second operational servicesecond operational servicesecond operational servicesecond operational service is defined, related to the selection of the DLA

management service level:

Op. Service n°2: ABCD shall give the user the possibility to choose the

level of service and change service levels at any time.

Lastly, as explained in the following section, ABCD will be provided by the airline’s

system with aircraft schedule and minimum turn-around time. However, when data

are missing, ABCD will interface with the operator and warn him about the

problem in question. Therefore, a third operational servicethird operational servicethird operational servicethird operational service is defined:

Op. Service n°3: ABCD shall warn the user in case of missing data

(aircraft schedule and minimum turn-around time)

To provide those operational services, ABCD shall rely on a set of functional

requirements (cf. 4.2.2) and shall interface with the user thanks to its own Human

Machine Interface (cf. 4.2.3).

4.2.24.2.24.2.24.2.2 Functional requirementsFunctional requirementsFunctional requirementsFunctional requirements

In order to provide the user with the operational services previously presented, the

following functional requirements are needed:

FnFnFnFn----User_IfUser_IfUser_IfUser_If----1111----Choose level of serviceChoose level of serviceChoose level of serviceChoose level of service

ABCD shall provide the user with the possibility to choose the level of DLA

management service (level 0, 1, 2 or 3) and change service levels at any time.

Dependencies:Dependencies:Dependencies:Dependencies:

36

Non_Fn-User_If-2-Service level selection window

Fn-Int-Trig-2-Detect active service level

FnFnFnFn----User_IfUser_IfUser_IfUser_If----2222----Display EPOBT and EOBTDisplay EPOBT and EOBTDisplay EPOBT and EOBTDisplay EPOBT and EOBT

For each flight in the database, ABCD shall continuously display: the flight ARCID,

the ARN, the ADEP, the ADES, the EOBT of the FPL, the current EOBT, the CTOT

(if regulated) and the EPOBT.


Non_Fn-User_If-3-DLA management window at level 0




Fn-Int-Trig-9-Update database

FnFnFnFn----User_IfUser_IfUser_IfUser_If----3333----Warn the operator in case of inconsistency Warn the operator in case of inconsistency Warn the operator in case of inconsistency Warn the operator in case of inconsistency with the with the with the with the

current EOBT current EOBT current EOBT current EOBT

ABCD shall propose to the operator a new EOBT as soon as a reactionary delay on a

flight has been detected by ABCD thanks to the comparison between the EPOBT

and the EOBT (and/or the CTOT in case of regulation). The new EOBT shall be

equal to the current EPOBT. The requirement is only relevant to service level 1.




Fn-Int-Trig-12-Check compatibility between EOBT / CTOT and EPOBT

FnFnFnFn----User_IfUser_IfUser_IfUser_If----4444----Warn the operator in case of inconsistency with the Warn the operator in case of inconsistency with the Warn the operator in case of inconsistency with the Warn the operator in case of inconsistency with the

current EOBT by taking into account current EOBT by taking into account current EOBT by taking into account current EOBT by taking into account the stability criteria the stability criteria the stability criteria the stability criteria

ABCD shall propose to the operator a new EOBT as soon as a reactionary delay on a

flight has been detected by ABCD thanks to the comparison between the EPOBT

and the EOBT (and/or the CTOT in case of regulation), and if one of the two

stability criteria is respected. The new EOBT shall be equal to the current EPOBT.

The requirement is only relevant to service level 2 and 3.






Fn-Int-Cont-2-Check the stability criteria

FnFnFnFn----User_IfUser_IfUser_IfUser_If----5555----Propose DLA message Propose DLA message Propose DLA message Propose DLA message

37

ABCD shall propose to the airline operator a DLA message already prepared. The

requirement is only relevant to service level3.

DependenciesDependenciesDependenciesDependencies:



Fn-Int-Trig-13-Prepare DLA message

FnFnFnFn----User_IfUser_IfUser_IfUser_If----6666----Warn Warn Warn Warn airlineairlineairlineairline in case of missing data in case of missing data in case of missing data in case of missing data

If ABCD can not access a minimum turn-around time or the ARN or the taxi-time

of a flight, the system shall warn the user that this data is missing.


Fn-Syst_If-2-Get Aircraft Registration Number

Fn-Syst_If-3-Get Minimum Turn-Around Time

Fn-Syst_If-4-Get Taxi-Time

Non_Fn-User_If-7-Missing data warning window

4.2.34.2.34.2.34.2.3 Non functional Non functional Non functional Non functional requirementsrequirementsrequirementsrequirements

The non-functional requirements presented below are related to the HMI that

ABCD will need in order to interface with the user. However one has to note that

the HMI design depends on the preferences and needs of each particular airline and

therefore cannot be specified at the level of a generic study. This is why:

- “may” is used for them since they are just options proposed to the user;

- whereas “shall” is used for the other requirements because the provision of

the operational services is subject to their fulfilment.

Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----1111----Structure of the displayStructure of the displayStructure of the displayStructure of the display

The display may be structured in such a way that the relevant information is

presented to the user. It may consist of three main windows:

1.1.1.1. Service level selection window

2.2.2.2. DLA management window

3.3.3.3. Missing Data Warning window

Each part of the display is described below.


Non_Fn-User_If-2-Service level selection window



38



Non_Fn-User_If-7-Missing data warning window.

Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----2222----Service Service Service Service llllevel selection evel selection evel selection evel selection windowwindowwindowwindow

- This window may present four items associated to the four levels of DLA

management service (level 0, level 1, level 2 and level 3)

- The user may have the ability to select the item corresponding to the

wanted level of service.

- The window may highlight the item corresponding to the service level

selected by the user.

Dependencies: Dependencies: Dependencies: Dependencies:

Fn-User_If-1-Choose level of service

Non_Fn-User_If-1-Structure of the display

Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----3333----DLA management window at DLA management window at DLA management window at DLA management window at llllevel 0evel 0evel 0evel 0

At this level, the DLA management window may consist of a matrix of 8 columns

and X rows (X will depend on the display resolution) providing a list of flights with

specific information:

- Each column may correspond to a specific field: ARCID, ARN, ADEP,

ADES, EOBT of the FPL, current EOBT, current CTOT and EPOBT.

- Each row may correspond to a flight.

- The matrix header may provide the name of the 8 fields.

- The values of the fields for each flight may be extracted from the ABCD

database and updated whenever the database is updated.

The flight list should be easy to handle for the user, hence the following

requirements:

- The user may be able to scroll up / down the list of flights.

- The user may be able to sort out the list according to each field.



Fn-User_If-2-Display EPOBT and EOBT


Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----4444---- DLA m DLA m DLA m DLA management window at lanagement window at lanagement window at lanagement window at level evel evel evel 1111

39

At this level, the DLA management window may consist of the matrix defined at

level 0 (but with only X’ rows, with X’ < X) complemented by a second matrix

defined as follows:

- The second matrix may provide the flight list restricted to the flights for

which there is an inconsistency between the EPOBT and EOBT (and/or

CTOT if regulated). (cf. requirement “Check compatibility between

EOBT / CTOT and EPOBT”)

- This restricted list may provide the same fields as in the standard matrix,

except that the field “EPOBT” shall be called “EOBT proposal”. However,

the values of this field shall be equal to the EPOBT values.




Fn-User_If-3-Warn the operator in case of inconsistency with the current EOBT


Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----5555---- DLA management window at DLA management window at DLA management window at DLA management window at llllevel 2evel 2evel 2evel 2

At this level, the DLA management window may be identical to the one defined at

level 1. However, a supplementary condition may be applied to the list of flights

provided by the second matrix: the flight list may also be restricted to the flights for

which the stability criteria are satisfied.




Fn-User_If-4-Warn the operator in case of inconsistency with the current EOBT by

taking into account the stability criteria


Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----6666---- DLA management window at DLA management window at DLA management window at DLA management window at llllevel 3evel 3evel 3evel 3

At this level, the DLA management window may be identical to the one defined at

level 2. However, the window presents an additional feature: the user may access

the DLA message when clicking on a flight of the flight list of the second matrix

(i.e. a flight for which an inconsistency between EOBT (and / or CTOT) and EOBT

has been detected, satisfying the stability criteria).






40

Fn-User_If-5-Propose DLA message


Non_FnNon_FnNon_FnNon_Fn----User_IfUser_IfUser_IfUser_If----7777----Missing data Missing data Missing data Missing data wwwwarning arning arning arning windowwindowwindowwindow

In this part of the display, ABCD may indicate to the user all the data related to the

ARN, the taxi-times and the TTM that ABCD could not get from the AOC system.

For example:

- If an ARN is missing “the ARN related to ARCID XXX is missing”,

- If a taxi-time is missing “the taxi-time related to ADEP XXX is missing”,

- If a TTM is missing: “the TTM related to XXX airport for XXX aircraft is

missing”.

Those warning shall be deleted as soon as ABCD can access the data in question.

Moreover, ABCD may also warn the user through an error message box that appears

on the screen and remains visible until the user has clicked on the box.


Fn-User_If-6-Warn airline in case of missing data


Figure 3 below shows a possible configuration of the display when level 1 is active.

41

Figure Figure Figure Figure 3333: Example of a possible configuration of the display: Example of a possible configuration of the display: Example of a possible configuration of the display: Example of a possible configuration of the display

4.3 Requirements related to system actors

4.3.14.3.14.3.14.3.1 Principles and preconditionsPrinciples and preconditionsPrinciples and preconditionsPrinciples and preconditions

ABCD is basically a flight information management system intended to receive

information, process information, and provide information. Consequently, there

will be information flows between ABCD and the outside world through message

exchanges. In particular, the tool will interface with the airlines’ existing systems.

However the system integration should be “non-invasive” with respect to the

current architecture. Hence, the following principle:

ABCD shall have the minimal impact on the other systems.

42

ABCD will manage information in the form of a database that will be updated

whenever a new message is received or sent by the airline system. The following

pre-condition has to be fulfilled:

ABCD shall have access to all the messages

received or sent by the airline’s system

NB: Some messages useful to ABCD (such as FUM, DEP, ARR) may not be

transmitted to the airline. This could vary from one airline to another and ABCD is

designed to process by default all the messages relevant to it. It is then up to the

airline to decide if new message exchanges, manageable by ABCD, but not currently

implemented should be implemented, depending on the airline business policy. Of

course and a priori: the greater the information source (i.e. the number of message

types actually handled by the system); the better the predictions made by the

system, the higher the performance, the greater the benefits.

For instance, Flight Update Messages (FUM) are quoted as a possible option. They

are currently sent by the CFMU to A-CDM aerodromes. Nevertheless, FUM and

other flight progress messages are of interest for ABCD. In fact, ABCD whatever the

airline will make the most of the standard messages already exchanged by the

airline.

Lastly, in order to accurately update its own database, ABCD will also rely on three

other types of data provided by the airline’s system in addition to the standard

messages: aircraft schedule, taxi-time and minimum turn-around time. It is

therefore assumed that:

ABCD shall access the airline schedule (including ARN), the taxi-time

for each airport and the minimum turn-around time for each airport

and each type of aircraft, which are stored in the AOC system.

4.3.24.3.24.3.24.3.2 Functional requirementsFunctional requirementsFunctional requirementsFunctional requirements

FnFnFnFn----Syst_IfSyst_IfSyst_IfSyst_If----1111----Intercept messageIntercept messageIntercept messageIntercept message

ABCD shall intercept all the messages exchanged between the airline and the

CFMU, without interfering with its environment (i.e. run in a kind of “shadow”

mode of operations, which would be neutral for the existing systems). The messages

shall be transferred to ABCD in ADEXP format.

Detailed information about the format and the message structure are annexed to the

document (cf. Annex 1).

43


Fn-Int-Trig-3-Identify message type

FnFnFnFn----Syst_IfSyst_IfSyst_IfSyst_If----2222----Get Aircraft Registration Number Get Aircraft Registration Number Get Aircraft Registration Number Get Aircraft Registration Number

ABCD shall be able to get from the AOC system the ARN allocated to a given flight

and associate it with the FPL ARCID stored in the buffer. If ABCD cannot get the

ARN, then it shall trigger “Warn airline in case of missing data”.



Fn-Int-Trig-5-Store FPL

FnFnFnFn----Syst_IfSyst_IfSyst_IfSyst_If----3333----Get Minimum TurnGet Minimum TurnGet Minimum TurnGet Minimum Turn----Around time Around time Around time Around time

ABCD shall be able to get from the airline system the minimum turn-around time

defined for a given type of aircraft (ARCTYP) at a given airport (ADES). If ABCD

cannot get the TTM, then it shall trigger “Warn airline in case of missing data”.



Fn-Int-Trig-7-Add flight to the database

FnFnFnFn----Syst_IfSyst_IfSyst_IfSyst_If----4444----Get Get Get Get TaxiTaxiTaxiTaxi----TimeTimeTimeTime

ABCD shall be able to get from the airline system the taxi-time for each flight. This

taxi-time is by convention the taxi-time of the ADEP (taxi-out). If ABCD cannot get

it, then it shall trigger “Warn airline in case of missing data”.




44

4.4 Requirements internal to ABCD

4.4.14.4.14.4.14.4.1 FunctionalFunctionalFunctionalFunctional requirements requirements requirements requirements

FnFnFnFn----InInInIntttt----TrigTrigTrigTrig----1111----Create databaseCreate databaseCreate databaseCreate database

When ABCD is switched on, a database shall be created and be configured as

illustrated by the following table:

Flight ARCID

ARN

Linkage number

ARCTYP ADEP ADES

FPL EOBT

Current EOBT TTLEET

Taxi-time CTOT

Arrival time

TTM EPOBT

Table Table Table Table 2222: ABCD database layout: ABCD database layout: ABCD database layout: ABCD database layout

NB: The TTM associated to a flight arbitrarily corresponds to the minimum

turnaround time at the departure airport (ADEP) for the flight aircraft type

(ARCTYP). The taxi-time associated to a flight arbitrarily corresponds to the taxi-

out time i.e. the taxi-time associated to the departure airport (ADEP).



FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----2222----Detect activeDetect activeDetect activeDetect active service level service level service level service level

ABCD shall detect the active level of service chosen by the user through “Choose

level of service”.


Fn-User_If-1-Choose level of service









FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----3333----Identify message typeIdentify message typeIdentify message typeIdentify message type

After intercepting a message, ABCD shall identify its type in order to determine if

the message is relevant or not to ABCD.

45

Relevant message types are the following ones: FPL, ACK, CNL, DLA, CHG, SAM,

SRM, SLC, FUM, DEP and ARR.


Fn-Syst_If-1-Intercept Message


Fn-Int-Trig-8-Store message (except FPL and ACK)

Fn-Int-Trig-6-Validate FPL

FnFnFnFn----InInInIntttt----TrigTrigTrigTrig----4444----Identify Flight Identify Flight Identify Flight Identify Flight ARCIDARCIDARCIDARCID

Once the type of message has been identified, ABCD shall extract from the message

the flight ARCID.




Fn-Int-Cont-1-Control message

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----5555----Store FPLStore FPLStore FPLStore FPL

If a FPL message is identified through “Identify message type”, ABCD shall:

� store it in a buffer together with the FPL ARCID identified through

“Identify Flight ARCID”

� set the FPL status to “Not yet validated”

� trigger “Get Aircraft Registration Number”

DepeDepeDepeDependenciesndenciesndenciesndencies:



Fn-Int-Trig-4-Identify Flight ARCID

Fn-Syst_If-2-Get Aircraft Registration Number

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----6666----Validate FPLValidate FPLValidate FPLValidate FPL

If an ACK message is identified through “Identify message type”, ABCD shall set to

“Validated” the status of the FPL message associated to the ARCID identified

through “Identify Flight ARCID”.




Fn-Int-Trig-4-Identify flight ARCID


FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----7777----Add flight to the databaseAdd flight to the databaseAdd flight to the databaseAdd flight to the database

46

Once a FPL stored in the buffer is “validated” and is associated to an ARN, ABCD

shall:

1) add a row into the database and fill the first field with the FPL ARCID and the second field with the associated ARN

2) apply “Update database” to the FPL message

3) trigger “Get Minimum Turn-Around Time” with the following input

parameters: ARCTYP, ADEP

4) trigger “Get Taxi-Time” with the following input parameters: ADEP




Fn-Int-Trig-10-Update flight sequence

Fn-Syst_If-3-Get Minimum Turn-Around Time

Fn-Syst_If-4-Get Taxi-Time

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----8888----Store Store Store Store messagemessagemessagemessage (except FPL and ACK) (except FPL and ACK) (except FPL and ACK) (except FPL and ACK)

ABCD shall store each relevant message (except FPL and ACK) in a buffer until all

the relevant information is extracted.




FnFnFnFn----IntIntIntInt----ContContContCont----1111----Control messageControl messageControl messageControl message

ABCD shall continuouslycontinuouslycontinuouslycontinuously control the messages stored in the buffer to check if the

flight ARCID contained in the message already exists in the database. If so, then

ABCD shall trigger “Update database”.


Fn-Int-Trig-8-Store message (except FPL and ACK)

Fn-Int-Trig-4-Identify flight ARCID


Non_Fn-Int-Trig-1-Update rate

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----9999----UUUUpdate databasepdate databasepdate databasepdate database

ABCD shall extract the necessary information depending on each message and

update the database consequently.

Table 3 indicates for each relevant message the information to extract, as well as its

impact on the database.

47

Relevant

messages

Information to

extract n°1

Information to

extract n°2

Field (*) to be updated in the

database / Action to be taken

FPL ARCID ADEP,

ADES,

ARCTYP,

EOBT,

TTLEET

ADEP* = ADEP,

ADES* = ADES

ARCTYP* = ARCTYP

FPL EOBT* = EOBT = current EOBT*

TTLEET* = TTLEET

DLA ARCID EOBT Current EOBT* = EOBT

CHG ARCID EOBT,

TTLEET

Current EOBT* = EOBT

TTLEET* = TTLEET

CNL ARCID Erase flight from the database

SAM ARCID CTOT CTOT* = CTOT

SRM ARCID NEWCTOT CTOT* = NEWCTOT

SLC ARCID CTOT* = “ ”

DEP ARCID ATD Arrival Time* = ATD + TTLEET

ARR ARCID ATA Arrival Time* = ATA

FUM ARCID ELDT Arrival Time* = ELDT

TableTableTableTable 3333: : : : Data to extract from the messages to update the databaseData to extract from the messages to update the databaseData to extract from the messages to update the databaseData to extract from the messages to update the database

After processing these messages ABCD shall erase the messages from the buffer once

the information has been transmitted to the database, except for the FPL, DLA and

CHG. Those messages shall not be erased, but replace the last FPL, DLA or CHG

contained in the buffer for the same ARCID.


Fn-Int-Trig-1-Create database



Fn-Int-Trig-10-Update flight sequence


Fn-Int-Trig-11-Calculate EPOBT

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----10101010----UUUUpdate flight sequencepdate flight sequencepdate flight sequencepdate flight sequence

Each time a flight, its ARN and related data extracted from the FPL are added to the

database (through “Add flight to the database” and “update database”), this flight

and all the flights linked to the same ARN shall be (re)assigned a linkage number

(1,2,3 …) in accordance with the sequence executed during the day of operation.

ABCD shall (re)number those flights (linkage number) in ascending order regarding

the FPL EOBT.

DependenciesDependenciesDependenciesDependencies::::



48

FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----11111111----Calculate EPOBT Calculate EPOBT Calculate EPOBT Calculate EPOBT

Each time the database is updated, ABCD shall calculate for all flights the minimum

time at which flight N is able to leave its block (EPOBT), depending on the

information for flight N-1.

If Arrival Time (N-1) is not blank then flight progress information is available for

flight N and shall be used. EPOBT (N) is then given by:

Arrival Time (N-1) + taxi-time (N) + TTM (N)

If Arrival Time (N-1) is blank then flight progress information is unavailable and

flight planning information should be used instead, depending on the active Service

Level.

If level 0 or 1 is active:If level 0 or 1 is active:If level 0 or 1 is active:If level 0 or 1 is active:

EPOBT (N) is given by:

- If flight N-1 is not regulated: EOBT (N-1) + taxi-time (N-1) + TTLEET (N-1)

+ taxi-time (N) + TTM (N)

- If flight N-1 is regulated: CTOT (N-1) + TTLEET (N-1) + taxi-time (N) +

TTM (N)

If level 2 or 3 is active:If level 2 or 3 is active:If level 2 or 3 is active:If level 2 or 3 is active:

- If flight N-1 is not regulated, EPOBT (N) is given by: EOBT (N-1) + taxi-

time (N-1) + TTLEET (N-1) + taxi-time (N) + TTM (N)

- If flight N-1 is regulated:

• While the 2nd stability criterion is not met EPOBT (N) is given by:

EOBT (N-1) + taxi-time (N-1) + TTLEET (N-1) + taxi-time (N) + TTM

(N);

• Once the 2nd stability criterion is met EPOBT (N) is given by: CTOT

(N-1) + TTLEET (N-1) + taxi-time (N) + TTM (N)

NB: By convention, the taxi-time provided by the database is the taxi-out time (i.e.

the taxi-time associated to the ADEP). The minimum turnaround time is also the

TTM associated to the ADEP (for the aircraft type).

DependenciesDependenciesDependenciesDependencies: : : :



FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----11112222----Check Check Check Check compatibility between compatibility between compatibility between compatibility between EOBT EOBT EOBT EOBT / / / / CTOTCTOTCTOTCTOT and and and and

EPOBTEPOBTEPOBTEPOBT

After each EPOBT update, ABCD shall check that the EPOBT is compatible with:

49

- The current EOBT, i.e. that the EPOBT is earlier than EOBT + 15 min.

- The CTOT if the flight is regulated, i.e. that the EPOBT is earlier than

CTOT – taxi-time (N) + 10 min.

If an incompatibility is detected in at least one case, then:

- If level 1 is active, ABCD shall trigger “Warn the operator in case of

inconsistency with the current EOBT (level 1)”.

- If level 2 is active, ABCD shall trigger “Warn the operator in case of

inconsistency with the current EOBT by taking into account the stability

criteria (level 2)” as soon as the stability criteria are met

- If level 3 is active, ABCD shall trigger “Prepare DLA message” as soon as

the stability criteria are met.


Fn-Int-Trig-11-Calculate EPOBT


Fn-Int-Trig-13-Prepare DLA message




FnFnFnFn----IntIntIntInt----ContContContCont----2222----CheckCheckCheckCheck the the the the stability criteria stability criteria stability criteria stability criteria

For each flight (N) of the database, ABCD shall continuouslycontinuouslycontinuouslycontinuously check that the stability

criteria are met, i.e. that:

- Clock-time4 > EOBT (N)-T1 (1(1(1(1stststst stability criterion) stability criterion) stability criterion) stability criterion);

- Clock-time > CTOT (N-1)-T2 (2(2(2(2ndndndnd stability criterion stability criterion stability criterion stability criterion5555)))).

NB: T1 and T2 are parameters that could be adjusted by the airline (cf. 4.2.1 for

possible default values).



Non_Fn-Int-Trig-1-Update rate



FnFnFnFn----IntIntIntInt----TrigTrigTrigTrig----11113333----Prepare DLA messagePrepare DLA messagePrepare DLA messagePrepare DLA message

ABCD shall prepare DLA messages according to the standard ADEXP format (cf.

Annex 1). The EOBT field value of the message shall be equal to the current EPOBT

4 The clock-time is the current UTC time of the AOC system 5 Applicable if flight N-1 is regulated i.e CTOT-(N-1) is not blank

50

calculated by ABCD. The other field values shall be identical to the one of the last

flight plan (FPL, DLA or CHG), which is stored in the buffer.

When the DLA message is prepared, ABCD shall trigger “propose DLA message”




4.4.24.4.24.4.24.4.2 NonNonNonNon----FunctionalFunctionalFunctionalFunctional requirements requirements requirements requirements

Non_FnNon_FnNon_FnNon_Fn----IntIntIntInt----TrigTrigTrigTrig----1111----Update rUpdate rUpdate rUpdate rateateateate

ABCD shall use a rate of one update per minute to trigger all the functional

requirements continuously performed by the tool (i.e. not triggered by another

requirement).




51

ANNEX 1: ADEXP FORMATANNEX 1: ADEXP FORMATANNEX 1: ADEXP FORMATANNEX 1: ADEXP FORMAT

This annex is a brief overview of the ADEXP format which is the standard used for

information interchange between airlines and the CFMU. More information may be

found in [6].

1) 1) 1) 1) Principle and rules of the ADEXP formatPrinciple and rules of the ADEXP formatPrinciple and rules of the ADEXP formatPrinciple and rules of the ADEXP format

The ATS Data Exchange Presentation (ADEXP) is an agreed standard for the

transmission of ATS message data. The ADEXP has been designed by

EUROCONTROL for the exchange of messages between computers either directly

or via a network. ADEXP is a format, not a protocol. The ADEXP format is a textual one, based on

characters, and no restrictions are imposed on the transmission media or protocols

to be used, other than of the character set. ADEXP provides a format for use

primarily in on-line, computer to computer message exchange.

The ADEXP format has been specified for use within the following areas of message

exchange:

• Flight planning

• Air Traffic Flow and Capacity Management (ATFCM)

• Air Traffic Control co-ordination

• Airspace management

• Civil/military co-ordination

Although ADEXP is designed primarily for automated treatment, it is provided in a

textual format based on characters which allow it to be more open and

understandable, and the messages remain readable to human operator.

The ADEXP format is designed as a computer to computer exchange format which

may be transmitted on different computer networks or on dedicated computer-

computer links. In addition, a requirement exists to be able to exchange some

ADEXP messages, typically flight planning and ATFCM related, on the AFTN,

although messages which may be required to be transmitted via AFTN shall have

their character set restricted.

A message in ADEXP format shall be composed of fields. The maximum message

length is 10K. Identified and retrievable fields in ADEXP shall be delimited by a

special start-of-field character, the hyphen character (‘-‘) and identified by a specific

keyword.

52

The first field shall be the mandatory title field, and the sequence of the subsequent

fields shall not be relevant. If a field is absent or incorrect, it can be skipped, and the

remaining part of the message can still be interpreted

When transmitting messages in the ADEXP format, all flight data messages

distributed by the IFPS shall contain the complete details of that flight, including

the flight profile as calculated by the IFPS and the entire list of addresses to which

that message is to be distributed.

Several layouts are possible to write the messages in ADEXP format:

EXAMPLE 1 below has been presented in a manner which makes it easily readable.

This has been achieved through the use of carriage returns, line feeds, indents etc.

Such a layout however does not form part of the ADEXP format rules.

EXAMPLE 2 is also a valid representation of the same message.

The presentation of a message is therefore at the discretion of the receiving system.

EXAMPLE EXAMPLE EXAMPLE EXAMPLE 1111

–––– TITLE SAM TITLE SAM TITLE SAM TITLE SAM

–––– ARCID ABC101ARCID ABC101ARCID ABC101ARCID ABC101

–––– ADEP EGLLADEP EGLLADEP EGLLADEP EGLL

–––– ADES LIRFADES LIRFADES LIRFADES LIRF

–––– EOBD 000401EOBD 000401EOBD 000401EOBD 000401

–––– EOBT 0945EOBT 0945EOBT 0945EOBT 0945

–––– CTOT 1030CTOT 1030CTOT 1030CTOT 1030

–––– REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01

–––– TAXITIME 0020TAXITIME 0020TAXITIME 0020TAXITIME 0020

–––– REGCAUSE WA84 REGCAUSE WA84 REGCAUSE WA84 REGCAUSE WA84

EXAMPLE 2EXAMPLE 2EXAMPLE 2EXAMPLE 2

–––– TITLE SAM TITLE SAM TITLE SAM TITLE SAM –––– ARCID ABC101 ARCID ABC101 ARCID ABC101 ARCID ABC101 ––––ADEP EGLL ADEP EGLL ADEP EGLL ADEP EGLL ––––ADES LIRF ADES LIRF ADES LIRF ADES LIRF ––––EOBD 000401 EOBD 000401 EOBD 000401 EOBD 000401 –––– EOBT 0945 EOBT 0945 EOBT 0945 EOBT 0945 ––––

CTOT 1030 CTOT 1030 CTOT 1030 CTOT 1030 –––– REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01 –––– TAX TAX TAX TAXITIME 0020 ITIME 0020 ITIME 0020 ITIME 0020 –––– REGCAUSE WA84 REGCAUSE WA84 REGCAUSE WA84 REGCAUSE WA84

2) Particularities to each message:2) Particularities to each message:2) Particularities to each message:2) Particularities to each message:

FPLFPLFPLFPL

The FPL message shall contain:

1) The message title TITLE

2) The aerodrome of departure ADEP

3) The destination aerodrome ADES

4) The aircraft company identification AOARCID

53

5) The aircraft identification ARCID 6) The aircraft type ARCTYP 7) The estimated off-blocks day EOBD

8) The estimated off-blocks time EOBT

9) The filing time of the submitted message FILTIM

10) The route ROUTE 11) The alternate aerodromes ALTRNT1

Example:

----TITLE IFPLTITLE IFPLTITLE IFPLTITLE IFPL

----BEGIN ADDR BEGIN ADDR BEGIN ADDR BEGIN ADDR

----FAC CFMFAC CFMFAC CFMFAC CFMUTACTUTACTUTACTUTACT

----FAC EDDAYGCDFAC EDDAYGCDFAC EDDAYGCDFAC EDDAYGCD

----FAC EDDZYNYSFAC EDDZYNYSFAC EDDZYNYSFAC EDDZYNYS

----FAC EDWWZQZXFAC EDWWZQZXFAC EDWWZQZXFAC EDWWZQZX

----FAC EDDHYQYXFAC EDDHYQYXFAC EDDHYQYXFAC EDDHYQYX

----FAC EDFFZQZXFAC EDFFZQZXFAC EDFFZQZXFAC EDFFZQZX

----FAC EDDAYGLZFAC EDDAYGLZFAC EDDAYGLZFAC EDDAYGLZ

----FAC EDDGZTZGFAC EDDGZTZGFAC EDDGZTZGFAC EDDGZTZG

----FAC EDDSYQYXFAC EDDSYQYXFAC EDDSYQYXFAC EDDSYQYX

----FAC EDDXYIYTFAC EDDXYIYTFAC EDDXYIYTFAC EDDXYIYT

----FAC XXXXXXXXFAC XXXXXXXXFAC XXXXXXXXFAC XXXXXXXX

----FAC EDYYZQZAFAC EDYYZQZAFAC EDYYZQZAFAC EDYYZQZA

----FAC EDYYZQZFAC EDYYZQZFAC EDYYZQZFAC EDYYZQZXXXX

----FAC EDUUZQZAFAC EDUUZQZAFAC EDUUZQZAFAC EDUUZQZA

----END ADDR END ADDR END ADDR END ADDR

----ADEP EDDHADEP EDDHADEP EDDHADEP EDDH

----ADES EDDSADES EDDSADES EDDSADES EDDS

----AOARCID BERAOARCID BERAOARCID BERAOARCID BER

----AOOPR BERAOOPR BERAOOPR BERAOOPR BER

----ARCID BER970ARCID BER970ARCID BER970ARCID BER970

----ARCTYP A320ARCTYP A320ARCTYP A320ARCTYP A320

----CEQPT SGHIPRWXYCEQPT SGHIPRWXYCEQPT SGHIPRWXYCEQPT SGHIPRWXY

----EOBD 081006EOBD 081006EOBD 081006EOBD 081006

----EOBT 0430EOBT 0430EOBT 0430EOBT 0430

----FILTIM 060003FILTIM 060003FILTIM 060003FILTIM 060003

----IFPLID AA68775811IFPLID AA68775811IFPLID AA68775811IFPLID AA68775811

----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN ----FAC EDDTBERXFAC EDDTBERXFAC EDDTBERXFAC EDDTBERX

----SEQPT SSEQPT SSEQPT SSEQPT S

----WKTRC MWKTRC MWKTRC MWKTRC M

----OPR BEROPR BEROPR BEROPR BER

----REG DAREG DAREG DAREG DABDEBDEBDEBDE

----RMK TCAS EQPDRMK TCAS EQPDRMK TCAS EQPDRMK TCAS EQPD

----RVR 075RVR 075RVR 075RVR 075

----SEL BDEPSEL BDEPSEL BDEPSEL BDEP

----SRC FPLSRC FPLSRC FPLSRC FPL

54

----TTLEET 0047TTLEET 0047TTLEET 0047TTLEET 0047

----RFL F330RFL F330RFL F330RFL F330

----SPEED N0434SPEED N0434SPEED N0434SPEED N0434

----FLTRUL IFLTRUL IFLTRUL IFLTRUL I

----FLTTYP SFLTTYP SFLTTYP SFLTTYP S

----ROUTE N0434F330 LBE UL126 OSBIT/N0379F230 G5 TINOD/N0379F220 T726 LBUROUTE N0434F330 LBE UL126 OSBIT/N0379F230 G5 TINOD/N0379F220 T726 LBUROUTE N0434F330 LBE UL126 OSBIT/N0379F230 G5 TINOD/N0379F220 T726 LBUROUTE N0434F330 LBE UL126 OSBIT/N0379F230 G5 TINOD/N0379F220 T726 LBU

----ALTRNT1 LSZHALTRNT1 LSZHALTRNT1 LSZHALTRNT1 LSZH

----EETFIR EDVV 0011EETFIR EDVV 0011EETFIR EDVV 0011EETFIR EDVV 0011

----EETFIR EDUU 0024EETFIR EDUU 0024EETFIR EDUU 0024EETFIR EDUU 0024

----EETFIR EDGG 0035EETFIR EDGG 0035EETFIR EDGG 0035EETFIR EDGG 0035

----BEGIN RTEPTS BEGIN RTEPTS BEGIN RTEPTS BEGIN RTEPTS

----PT PT PT PT ----PTID LBEPTID LBEPTID LBEPTID LBE

----PT PT PT PT ----PTID ESTADPTID ESTADPTID ESTADPTID ESTAD

----PT PT PT PT ----PTID KEGABPTID KEGABPTID KEGABPTID KEGAB

----PT PT PT PT ----PTID TIMENPTID TIMENPTID TIMENPTID TIMEN

----PT PT PT PT ----PTID ROBEGPTID ROBEGPTID ROBEGPTID ROBEG

----PT PT PT PT ----PTID PIROTPTID PIROTPTID PIROTPTID PIROT

----PT PT PT PT ----PTID LARBUPTID LARBUPTID LARBUPTID LARBU

----PT PT PT PT ----PTID WRBPTID WRBPTID WRBPTID WRB

----PT PT PT PT ----PTID ANANOPTID ANANOPTID ANANOPTID ANANO

----PT PT PT PT ----PTID MASEKPTID MASEKPTID MASEKPTID MASEK

----PT PT PT PT ----PTID OSBITPTID OSBITPTID OSBITPTID OSBIT

----PT PT PT PT ----PTID TOSTUPTID TOSTUPTID TOSTUPTID TOSTU

----PT PT PT PT ----PTID TINODPTID TINODPTID TINODPTID TINOD

----PT PT PT PT ----PTID TAKUTPTID TAKUTPTID TAKUTPTID TAKUT

----PT PT PT PT ----PTID GEBNOPTID GEBNOPTID GEBNOPTID GEBNO

----PT PT PT PT ----PTID NOSBUPTID NOSBUPTID NOSBUPTID NOSBU

----PT PT PT PT ----PTID LBUPTID LBUPTID LBUPTID LBU

----END RTEPTS END RTEPTS END RTEPTS END RTEPTS

----SID LBE7GSID LBE7GSID LBE7GSID LBE7G

----ATSRT UL126 LBE OSBITATSRT UL126 LBE OSBITATSRT UL126 LBE OSBITATSRT UL126 LBE OSBIT

----RFL F230 OSBITRFL F230 OSBITRFL F230 OSBITRFL F230 OSBIT

----SPEED N0379 OSBITSPEED N0379 OSBITSPEED N0379 OSBITSPEED N0379 OSBIT

----ATSRT G5 OSBIT TINODATSRT G5 OSBIT TINODATSRT G5 OSBIT TINODATSRT G5 OSBIT TINOD

----RFL F220 TINODRFL F220 TINODRFL F220 TINODRFL F220 TINOD

----SPEEDSPEEDSPEEDSPEED N0379 TINOD N0379 TINOD N0379 TINOD N0379 TINOD

----ATSRT T726 TINOD LBUATSRT T726 TINOD LBUATSRT T726 TINOD LBUATSRT T726 TINOD LBU

ACK ACK ACK ACK

There are two kind of ACK messages: short ACK and long ACK messages

(long ACK message: when the flight plan has been accepted by the IFPS but the

IFPS has made amendments)

The short ACK message shall contain:

55

1) The acknowledgment of successful processing TITLE

2) The title of the original message MSGTYP


4) The unique identifier of the flight plan in the IFPS database IFPLID 5) The filing time of the original message expanded to give the year, month,

date and time ORIGINDT

6) The number of additional addresses which have been sent to the IFPS in the

‘AD’ line

7) The summary fields of the message in ADEXP format

SSSShort ACK messagehort ACK messagehort ACK messagehort ACK message

----TITLE ACK TITLE ACK TITLE ACK TITLE ACK

----MSGTYP FPL MSGTYP FPL MSGTYP FPL MSGTYP FPL

----FILTIM 030830 FILTIM 030830 FILTIM 030830 FILTIM 030830

----IFPLID IFPLID IFPLID IFPLID AA00000102 AA00000102 AA00000102 AA00000102

----ORIGINDT 9710010200 ORIGINDT 9710010200 ORIGINDT 9710010200 ORIGINDT 9710010200

----FAC LHRWUABFAC LHRWUABFAC LHRWUABFAC LHRWUAB

----FAC EGFFABCXFAC EGFFABCXFAC EGFFABCXFAC EGFFABCX

----END ADDREND ADDREND ADDREND ADDR

----EXTADDR EXTADDR EXTADDR EXTADDR ––––NUM 009 NUM 009 NUM 009 NUM 009

----BEGIN MSGSUM BEGIN MSGSUM BEGIN MSGSUM BEGIN MSGSUM

----ARCID ABC567ARCID ABC567ARCID ABC567ARCID ABC567

----ADEP EGLLADEP EGLLADEP EGLLADEP EGLL

----ADES KJFKADES KJFKADES KJFKADES KJFK



----ORGN LHRWUABORGN LHRWUABORGN LHRWUABORGN LHRWUAB

----END MSGSUMEND MSGSUMEND MSGSUMEND MSGSUM

The long ACK message shall contain:

1) The acknowledgment of successful processing TITLE

2) The title of the original message MSGTYP


4) The unique identifier of the flight plan in the IFPS database 5) The filing time of the original message expanded to give the year, month,

date and time ORIGINDT

6) The number of additional addresses which have been sent to the IFPS in the

‘AD’ line EXTADDR

7) The complete message in ICAO format as accepted by the IFPS MSGTXT

Long ACK Long ACK Long ACK Long ACK messagemessagemessagemessage

----TITLE ACK TITLE ACK TITLE ACK TITLE ACK

56

----MSGTYP FPL MSGTYP FPL MSGTYP FPL MSGTYP FPL

----FILTIM 030830 FILTIM 030830 FILTIM 030830 FILTIM 030830

----IFPLID AA0000010IFPLID AA0000010IFPLID AA0000010IFPLID AA00000102 2 2 2

----ORIGINDT 9710010200 ORIGINDT 9710010200 ORIGINDT 9710010200 ORIGINDT 9710010200

----BEGIN ADDRBEGIN ADDRBEGIN ADDRBEGIN ADDR

----FAC LHRWUABFAC LHRWUABFAC LHRWUABFAC LHRWUAB

----FAC EGFFABCXFAC EGFFABCXFAC EGFFABCXFAC EGFFABCX

----END ADDREND ADDREND ADDREND ADDR

----EXTADDR EXTADDR EXTADDR EXTADDR ––––NUM 009NUM 009NUM 009NUM 009

----MSGTXT MSGTXT MSGTXT MSGTXT

----(FPL(FPL(FPL(FPL----ABC567ABC567ABC567ABC567----ISISISIS

----B744/HB744/HB744/HB744/H----SDWIRYHSDWIRYHSDWIRYHSDWIRYH

----EGLL1500EGLL1500EGLL1500EGLL1500

----N0487F330 BUZAD T420 WELIN UN57 TNT UL28 RODOL …N0487F330 BUZAD T420 WELIN UN57 TNT UL28 RODOL …N0487F330 BUZAD T420 WELIN UN57 TNT UL28 RODOL …N0487F330 BUZAD T420 WELIN UN57 TNT UL28 RODOL …

… REG/GCHGR SEL/EGJLRMK/TCAS EQUIPPED DOF/040503)… REG/GCHGR SEL/EGJLRMK/TCAS EQUIPPED DOF/040503)… REG/GCHGR SEL/EGJLRMK/TCAS EQUIPPED DOF/040503)… REG/GCHGR SEL/EGJLRMK/TCAS EQUIPPED DOF/040503)

DLADLADLADLA

The delay message shall contain







9) The route ROUTE

----TITLE IDLATITLE IDLATITLE IDLATITLE IDLA


----FAC CFMUTACTFAC CFMUTACTFAC CFMUTACTFAC CFMUTACT

----FAC LTCGZPZXFAC LTCGZPZXFAC LTCGZPZXFAC LTCGZPZX

----FAC LTCGZAZXFAC LTCGZAZXFAC LTCGZAZXFAC LTCGZAZX

----FAC LTACYCYXFAC LTACYCYXFAC LTACYCYXFAC LTACYCYX

----FAC LTAAZQZXFAC LTAAZQZXFAC LTAAZQZXFAC LTAAZQZX


----ADEP LTCGADEP LTCGADEP LTCGADEP LTCG

----ADES OPRNADES OPRNADES OPRNADES OPRN

----AOARCID ABQAOARCID ABQAOARCID ABQAOARCID ABQ

----AOOPR ABQAOOPR ABQAOOPR ABQAOOPR ABQ

----ARCID ABQ221ARCID ABQ221ARCID ABQ221ARCID ABQ221

----ARCARCARCARCTYP A321TYP A321TYP A321TYP A321

----CEQPT SHIRWYCEQPT SHIRWYCEQPT SHIRWYCEQPT SHIRWY

57

----COMMENT ORIGINATING FROM FILE ABQ01S.08.TXTCOMMENT ORIGINATING FROM FILE ABQ01S.08.TXTCOMMENT ORIGINATING FROM FILE ABQ01S.08.TXTCOMMENT ORIGINATING FROM FILE ABQ01S.08.TXT




----IFPLID BB81490518IFPLID BB81490518IFPLID BB81490518IFPLID BB81490518

----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA ----FAC KHIOVEDFAC KHIOVEDFAC KHIOVEDFAC KHIOVED


----WKTRC MWKTRC MWKTRC MWKTRC M

----COM TCASCOM TCASCOM TCASCOM TCAS

----OPR ABQOPR ABQOPR ABQOPR ABQ

----RMK TYP ISRMK TYP ISRMK TYP ISRMK TYP IS







----ROUTE N0446F330 MECIT G67 LU UN37 ODILI UN644 LAGAS UM747 LUSAL B111 ROUTE N0446F330 MECIT G67 LU UN37 ODILI UN644 LAGAS UM747 LUSAL B111 ROUTE N0446F330 MECIT G67 LU UN37 ODILI UN644 LAGAS UM747 LUSAL B111 ROUTE N0446F330 MECIT G67 LU UN37 ODILI UN644 LAGAS UM747 LUSAL B111

SAGIL A912 RODAR N644 ABDAN B371 LEMOD M696 GERAN G796 LAJAK HANGUSAGIL A912 RODAR N644 ABDAN B371 LEMOD M696 GERAN G796 LAJAK HANGUSAGIL A912 RODAR N644 ABDAN B371 LEMOD M696 GERAN G796 LAJAK HANGUSAGIL A912 RODAR N644 ABDAN B371 LEMOD M696 GERAN G796 LAJAK HANGU

----ALTRNT1 OPLAALTRNT1 OPLAALTRNT1 OPLAALTRNT1 OPLA

----ALTRNT2 OPPSALTRNT2 OPPSALTRNT2 OPPSALTRNT2 OPPS

----EETFIR UGGG 0014EETFIR UGGG 0014EETFIR UGGG 0014EETFIR UGGG 0014

----EETFIR UBBA 0036EETFIR UBBA 0036EETFIR UBBA 0036EETFIR UBBA 0036

----EETFIR UTAK 0116EETFIR UTAK 0116EETFIR UTAK 0116EETFIR UTAK 0116

----EETFIR UTAA 0EETFIR UTAA 0EETFIR UTAA 0EETFIR UTAA 0142142142142

----EETFIR UTAV 0220EETFIR UTAV 0220EETFIR UTAV 0220EETFIR UTAV 0220

----EETFIR OAKX 0237EETFIR OAKX 0237EETFIR OAKX 0237EETFIR OAKX 0237

----EETFIR OPLR 0318EETFIR OPLR 0318EETFIR OPLR 0318EETFIR OPLR 0318


----PT PT PT PT ----PTID MECITPTID MECITPTID MECITPTID MECIT

----PT PT PT PT ----PTID SARPIPTID SARPIPTID SARPIPTID SARPI

----PT PT PT PT ----PTID *LU3PTID *LU3PTID *LU3PTID *LU3

----PT PT PT PT ----PTID ODILIPTID ODILIPTID ODILIPTID ODILI

----PT PT PT PT ----PTID TETROPTID TETROPTID TETROPTID TETRO

----PT PT PT PT ----PTID LAGASPTID LAGASPTID LAGASPTID LAGAS

----PT PT PT PT ----PTID BARADPTID BARADPTID BARADPTID BARAD

----PT PT PT PT ----PTID LIMTIPTID LIMTIPTID LIMTIPTID LIMTI

----PT PT PT PT ----PTID LUSALPTID LUSALPTID LUSALPTID LUSAL

----PT PT PT PT ----PTID *AU1PTID *AU1PTID *AU1PTID *AU1

----PT PT PT PT ----PTID GINETPTID GINETPTID GINETPTID GINET

----PT PT PT PT ----PTID SAGILPTID SAGILPTID SAGILPTID SAGIL

----PT PT PT PT ----PTID RODARPTID RODARPTID RODARPTID RODAR

----PT PT PT PT ----PTID TUGARPTID TUGARPTID TUGARPTID TUGAR

----PT PT PT PT ----PTID TUGTAPTID TUGTAPTID TUGTAPTID TUGTA

----PT PT PT PT ----PTID BABUMPTID BABUMPTID BABUMPTID BABUM

----PT PT PT PT ----PTID ABEKOPTID ABEKOPTID ABEKOPTID ABEKO


----SID MECIT1USID MECIT1USID MECIT1USID MECIT1U

58

----ATSRT G67 MECIT *LU3ATSRT G67 MECIT *LU3ATSRT G67 MECIT *LU3ATSRT G67 MECIT *LU3

----AAAATSRT UN37 *LU3 ODILITSRT UN37 *LU3 ODILITSRT UN37 *LU3 ODILITSRT UN37 *LU3 ODILI

----ATSRT UN644 ODILI LAGASATSRT UN644 ODILI LAGASATSRT UN644 ODILI LAGASATSRT UN644 ODILI LAGAS

----ATSRT UM747 LAGAS LUSALATSRT UM747 LAGAS LUSALATSRT UM747 LAGAS LUSALATSRT UM747 LAGAS LUSAL

----ATSRT B111 LUSAL SAGILATSRT B111 LUSAL SAGILATSRT B111 LUSAL SAGILATSRT B111 LUSAL SAGIL

----ATSRT N644 RODAR ABEKOATSRT N644 RODAR ABEKOATSRT N644 RODAR ABEKOATSRT N644 RODAR ABEKO

CNLCNLCNLCNL

The CNL message shall contain:








Example:

----TITLE ICNLTITLE ICNLTITLE ICNLTITLE ICNL



----FAC EDDAYGCDFAC EDDAYGCDFAC EDDAYGCDFAC EDDAYGCD

----FAC LOVVZQZXFAC LOVVZQZXFAC LOVVZQZXFAC LOVVZQZX

----FAC LJLAZQZBFAC LJLAZQZBFAC LJLAZQZBFAC LJLAZQZB

----FAC LJUGAXHFAC LJUGAXHFAC LJUGAXHFAC LJUGAXH

----FAC LJLJZPZXFAC LJLJZPZXFAC LJLJZPZXFAC LJLJZPZX

----FAC LJLAZQZXFAC LJLAZQZXFAC LJLAZQZXFAC LJLAZQZX

----FAC LJLJZTZXFAC LJLJZTZXFAC LJLJZTZXFAC LJLJZTZX

----FAC EHAAZQZXFAC EHAAZQZXFAC EHAAZQZXFAC EHAAZQZX

----FAC EHAAZRAAFAC EHAAZRAAFAC EHAAZRAAFAC EHAAZRAA

----FAC EDMMZQZXFAC EDMMZQZXFAC EDMMZQZXFAC EDMMZQZX

----FAC LJLACFBFFAC LJLACFBFFAC LJLACFBFFAC LJLACFBF

----FACFACFACFAC EDDXYIYT EDDXYIYT EDDXYIYT EDDXYIYT


----FAC EDDAYGLZFAC EDDAYGLZFAC EDDAYGLZFAC EDDAYGLZ

----FAC EDUUZQZAFAC EDUUZQZAFAC EDUUZQZAFAC EDUUZQZA

----FAC EDYYZQZXFAC EDYYZQZXFAC EDYYZQZXFAC EDYYZQZX

----FAC EDYYZQZAFAC EDYYZQZAFAC EDYYZQZAFAC EDYYZQZA

59

----FAC EHAMZTZXFAC EHAMZTZXFAC EHAMZTZXFAC EHAMZTZX


----ADEP LJLJADEP LJLJADEP LJLJADEP LJLJ

----ADES EHAMADES EHAMADES EHAMADES EHAM

----AOARCID ADRAOARCID ADRAOARCID ADRAOARCID ADR

----AOOPR ADRAOOPR ADRAOOPR ADRAOOPR ADR

----ARCID ADR434ARCID ADR434ARCID ADR434ARCID ADR434

----COMMENT ORIGINATING FROM FILE ADR01S.TXTCOMMENT ORIGINATING FROM FILE ADR01S.TXTCOMMENT ORIGINATING FROM FILE ADR01S.TXTCOMMENT ORIGINATING FROM FILE ADR01S.TXT





----ORGNID ADRAOCCORGNID ADRAOCCORGNID ADRAOCCORGNID ADRAOCC

----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA ----FAC LJUODJPFAC LJUODJPFAC LJUODJPFAC LJUODJP


SAMSAMSAMSAM

The SAM message shall contain:


2) The aircraft identification ARCID 3) The departure aerodrome ADEP

4) The arrival aerodrome ADES

5) The estimated off-blocks day EOBD


7) The calculated take-off time CTOT

8) The regulation name REGUL

9) The taxi time TAXITIME

10) The cause of the regulation REGCAUSE

Example:

––––TITLE SAM TITLE SAM TITLE SAM TITLE SAM ––––ARCID ABC101 ARCID ABC101 ARCID ABC101 ARCID ABC101 ––––ADEPADEPADEPADEP EGLL EGLL EGLL EGLL ––––ADESADESADESADES LIRF LIRF LIRF LIRF ––––EOBD 000401 EOBD 000401 EOBD 000401 EOBD 000401 ––––EOBT 094EOBT 094EOBT 094EOBT 0945 5 5 5 ––––

CTOT 1030 CTOT 1030 CTOT 1030 CTOT 1030 ––––REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01 REGUL LIRFA01 ––––TAXITIME 0020 TAXITIME 0020 TAXITIME 0020 TAXITIME 0020 ––––REGCAUSE WA84REGCAUSE WA84REGCAUSE WA84REGCAUSE WA84

SRMSRMSRMSRM

The SRM message shall contain:


2) The aircraft identification ARCID

60

3) The departure aerodrome ADEP


5) The initial off-blocks day IOBD 6) The initial off-blocks time IOBT



9) The new calculated take off time NEWCTOT

10) The regulation name REGUL

11) The taxi time TAXITIME

12) The cause of the regulation REGCAUSE

Example:

––––TITLE SRM TITLE SRM TITLE SRM TITLE SRM ––––ARCID ABC101 ARCID ABC101 ARCID ABC101 ARCID ABC101 ––––ADEP ADEP ADEP ADEP EGLL EGLL EGLL EGLL ––––ADES LIRF ADES LIRF ADES LIRF ADES LIRF ––––IOBD 000401 IOBD 000401 IOBD 000401 IOBD 000401 ––––IOBT 2350 IOBT 2350 IOBT 2350 IOBT 2350 ––––

EOBD 000501 EOBD 000501 EOBD 000501 EOBD 000501 ––––EOBT 0020 EOBT 0020 EOBT 0020 EOBT 0020 ––––NEWCTOT 0050 NEWCTOT 0050 NEWCTOT 0050 NEWCTOT 0050 ––––REGUL LIRFREGUL LIRFREGUL LIRFREGUL LIRFA01 A01 A01 A01 ––––TAXITIME 0020 TAXITIME 0020 TAXITIME 0020 TAXITIME 0020 ––––

REGCAUSE WA84REGCAUSE WA84REGCAUSE WA84REGCAUSE WA84

SLCSLCSLCSLC

The SLC message shall contain:






7) The reason REASON 8) The taxi time TAXITIME

Example:

––––TITLE SLCTITLE SLCTITLE SLCTITLE SLC ––––ARCIDARCIDARCIDARCID ABC101 ABC101 ABC101 ABC101 ––––ADEP EGLL ADEP EGLL ADEP EGLL ADEP EGLL ––––ADES LIRF ADES LIRF ADES LIRF ADES LIRF ––––EOBD 000401 EOBD 000401 EOBD 000401 EOBD 000401 ––––EOBT 0945 EOBT 0945 EOBT 0945 EOBT 0945 ––––

REASON REASON REASON REASON VOIDVOIDVOIDVOID ––––TAXITIME 0020TAXITIME 0020TAXITIME 0020TAXITIME 0020

FLSFLSFLSFLS

The FLS message shall contain:



61




7) Comments COMMENT

8) The taxi time TAXTIME

Examples:

----TITLE FLS TITLE FLS TITLE FLS TITLE FLS ––––ARCID ABC101 ARCID ABC101 ARCID ABC101 ARCID ABC101 ––––ADEP EGLL ADEP EGLL ADEP EGLL ADEP EGLL ––––ADES LIRF ADES LIRF ADES LIRF ADES LIRF –––– EOBD 000401 EOBD 000401 EOBD 000401 EOBD 000401 ––––EOBT 0945 EOBT 0945 EOBT 0945 EOBT 0945 ––––

COMMENT SMM RECEIVED COMMENT SMM RECEIVED COMMENT SMM RECEIVED COMMENT SMM RECEIVED –––– TAXITIME 0020 TAXITIME 0020 TAXITIME 0020 TAXITIME 0020

----TITLE FLS TITLE FLS TITLE FLS TITLE FLS ––––ARCIDARCIDARCIDARCID ABC101 ABC101 ABC101 ABC101 ––––ADEP EGLL ADEP EGLL ADEP EGLL ADEP EGLL ––––ADES LIRF ADES LIRF ADES LIRF ADES LIRF ––––EOBD 000423 EOBD 000423 EOBD 000423 EOBD 000423 ––––EOBT 0945 EOBT 0945 EOBT 0945 EOBT 0945 ––––

COMCOMCOMCOMMENT NOT REPORTED AS AIRBORNE MENT NOT REPORTED AS AIRBORNE MENT NOT REPORTED AS AIRBORNE MENT NOT REPORTED AS AIRBORNE ––––TAXITIME 0020TAXITIME 0020TAXITIME 0020TAXITIME 0020

DEPDEPDEPDEP

The departure message shall contain:


2) The actual day of departure ADD 3) The departure aerodrome ADEP

4) The departure aerodrome ADES

5) The aircraft operator identification AOARCID 6) The aircraft identification ARCID 7) The aircraft type ARCTYP 8) The estimated off-blocks day EOBD



11) The route ROUTE

Examples:

----TITLE IDEPTITLE IDEPTITLE IDEPTITLE IDEP

----ADD 081006ADD 081006ADD 081006ADD 081006


----FAC EVRRZDZXFAC EVRRZDZXFAC EVRRZDZXFAC EVRRZDZX

----FAC UUUWZDZXFAC UUUWZDZXFAC UUUWZDZXFAC UUUWZDZX

----FAFAFAFAC UUUUYGYXC UUUUYGYXC UUUUYGYXC UUUUYGYX

----FAC ULLLZDZXFAC ULLLZDZXFAC ULLLZDZXFAC ULLLZDZX

----FAC ULLLZRZXFAC ULLLZRZXFAC ULLLZRZXFAC ULLLZRZX

----FAC ULLIZTZXFAC ULLIZTZXFAC ULLIZTZXFAC ULLIZTZX

----FAC ULLLPOXXFAC ULLLPOXXFAC ULLLPOXXFAC ULLLPOXX

----FAC DTMBZTZXFAC DTMBZTZXFAC DTMBZTZXFAC DTMBZTZX

----FAC DTMBZPZXFAC DTMBZPZXFAC DTMBZPZXFAC DTMBZPZX

62

----FAC DTTCZQZXFAC DTTCZQZXFAC DTTCZQZXFAC DTTCZQZX

----FAC ULLLPLKZFAC ULLLPLKZFAC ULLLPLKZFAC ULLLPLKZ

----FAC ULLVZAZXFAC ULLVZAZXFAC ULLVZAZXFAC ULLVZAZX

----FAC DTTCYWYXFAC DTTCYWYXFAC DTTCYWYXFAC DTTCYWYX

----FAC EVRRZQZXFAC EVRRZQZXFAC EVRRZQZXFAC EVRRZQZX

----FAC LQFAC LQFAC LQFAC LQSBZQZXSBZQZXSBZQZXSBZQZX

----FAC LZBBZQZXFAC LZBBZQZXFAC LZBBZQZXFAC LZBBZQZX


----FAC LDZOZQZXFAC LDZOZQZXFAC LDZOZQZXFAC LDZOZQZX

----FAC EYKAYWYXFAC EYKAYWYXFAC EYKAYWYXFAC EYKAYWYX

----FAC EYVLIFPSFAC EYVLIFPSFAC EYVLIFPSFAC EYVLIFPS

----FAC LHBPZEZXFAC LHBPZEZXFAC LHBPZEZXFAC LHBPZEZX

----FAC LIRRZQZXFAC LIRRZQZXFAC LIRRZQZXFAC LIRRZQZX

----FAC LIBBZQZXFAC LIBBZQZXFAC LIBBZQZXFAC LIBBZQZX

----FAC LIIRZEZXFAC LIIRZEZXFAC LIIRZEZXFAC LIIRZEZX

----FAC EETTZQZXFAC EETTZQZXFAC EETTZQZXFAC EETTZQZX


----FAC EPWWZQFAC EPWWZQFAC EPWWZQFAC EPWWZQZXZXZXZX


----ADEP ULLIADEP ULLIADEP ULLIADEP ULLI

----ADES DTMBADES DTMBADES DTMBADES DTMB

----AOARCID SDMAOARCID SDMAOARCID SDMAOARCID SDM

----ARCID SDM9531ARCID SDM9531ARCID SDM9531ARCID SDM9531

----ARCTYP B763ARCTYP B763ARCTYP B763ARCTYP B763

----ATD 0010ATD 0010ATD 0010ATD 0010

----CEQPT SDIRWYCEQPT SDIRWYCEQPT SDIRWYCEQPT SDIRWY





----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN ----FAC ULLVZTZXFAC ULLVZTZXFAC ULLVZTZXFAC ULLVZTZX


----WKTRC HWKTRC HWKTRC HWKTRC H

----REG EIEARREG EIEARREG EIEARREG EIEAR

----RMK ITALY W/N TUNISIA DGAC RMK ITALY W/N TUNISIA DGAC RMK ITALY W/N TUNISIA DGAC RMK ITALY W/N TUNISIA DGAC NR :08/268/09 FAWT 7/0210 08 TCAS EQUIPPEDNR :08/268/09 FAWT 7/0210 08 TCAS EQUIPPEDNR :08/268/09 FAWT 7/0210 08 TCAS EQUIPPEDNR :08/268/09 FAWT 7/0210 08 TCAS EQUIPPED






----FLTTYP NFLTTYP NFLTTYP NFLTTYP N

----ROUTE N0464F360 KO B141 RANVA/N0464F360 UP863 GONOS UN619 SOKVA ROUTE N0464F360 KO B141 RANVA/N0464F360 UP863 GONOS UN619 SOKVA ROUTE N0464F360 KO B141 RANVA/N0464F360 UP863 GONOS UN619 SOKVA ROUTE N0464F360 KO B141 RANVA/N0464F360 UP863 GONOS UN619 SOKVA

UM857 PODAN UZ200 TPS UM986 PUSTA UY552 VEBAL/N0468F350 UL196 SPL UM857 PODAN UZ200 TPS UM986 PUSTA UY552 VEBAL/N0468F350 UL196 SPL UM857 PODAN UZ200 TPS UM986 PUSTA UY552 VEBAL/N0468F350 UL196 SPL UM857 PODAN UZ200 TPS UM986 PUSTA UY552 VEBAL/N0468F350 UL196 SPL

UM725 SOR/N0462FUM725 SOR/N0462FUM725 SOR/N0462FUM725 SOR/N0462F370 UM725 PININ UM738 CBN G727 DIDON370 UM725 PININ UM738 CBN G727 DIDON370 UM725 PININ UM738 CBN G727 DIDON370 UM725 PININ UM738 CBN G727 DIDON

----ALTRNT1 DTTAALTRNT1 DTTAALTRNT1 DTTAALTRNT1 DTTA

----EETFIR EETT 0016EETFIR EETT 0016EETFIR EETT 0016EETFIR EETT 0016

----EETFIR EVRR 0041EETFIR EVRR 0041EETFIR EVRR 0041EETFIR EVRR 0041

----EETFIR EYVL 0055EETFIR EYVL 0055EETFIR EYVL 0055EETFIR EYVL 0055

63

----EETFIR EPWW 0114EETFIR EPWW 0114EETFIR EPWW 0114EETFIR EPWW 0114

----EETFIR LZBB 0159EETFIR LZBB 0159EETFIR LZBB 0159EETFIR LZBB 0159

----EETFIR LHCC 0213EETFIR LHCC 0213EETFIR LHCC 0213EETFIR LHCC 0213

----EETFIR LDZO 0237EETFIR LDZO 0237EETFIR LDZO 0237EETFIR LDZO 0237

----EETFIR LQSB 0244EETFIR LQSB 0244EETFIR LQSB 0244EETFIR LQSB 0244

----EETFIR LDZO 0253EETFIR LDZO 0253EETFIR LDZO 0253EETFIR LDZO 0253

----EETFIR LIBB 0304EETFIR LIBB 0304EETFIR LIBB 0304EETFIR LIBB 0304

----EETFIR LIRR 0315EETFIR LIRR 0315EETFIR LIRR 0315EETFIR LIRR 0315

----EETFIREETFIREETFIREETFIR DTTC 0353 DTTC 0353 DTTC 0353 DTTC 0353


----PT PT PT PT ----PTID *KO2PTID *KO2PTID *KO2PTID *KO2

----PT PT PT PT ----PTID RANVAPTID RANVAPTID RANVAPTID RANVA

----PT PT PT PT ----PTID GONOSPTID GONOSPTID GONOSPTID GONOS

----PT PT PT PT ----PTID SOKVAPTID SOKVAPTID SOKVAPTID SOKVA

----PT PT PT PT ----PTID RIAPTID RIAPTID RIAPTID RIA

----PT PT PT PT ----PTID ATRAKPTID ATRAKPTID ATRAKPTID ATRAK

----PT PT PT PT ----PTID GUNTAPTID GUNTAPTID GUNTAPTID GUNTA

----PT PT PT PT ----PTID VAKALPTID VAKALPTID VAKALPTID VAKAL

----PT PT PT PT ----PTID BOKSUPTID BOKSUPTID BOKSUPTID BOKSU

----PT PT PT PT ----PTID SUWPTID SUWPTID SUWPTID SUW

----PT PT PT PT ----PTID BULEPPTID BULEPPTID BULEPPTID BULEP

----PT PT PT PT ----PTID SIEPTID SIEPTID SIEPTID SIE

----PT PT PT PT ----PTID VENESPTID VENESPTID VENESPTID VENES

----PT PT PT PT ----PTID RILABPTID RILABPTID RILABPTID RILAB

----PT PT PT PT ----PTID PODANPTID PODANPTID PODANPTID PODAN

----PT PT PT PT ----PTID DEMOPPTID DEMOPPTID DEMOPPTID DEMOP

----PT PT PT PT ----PTID TPSPTID TPSPTID TPSPTID TPS

----PT PT PT PT ----PTID BALUXPTID BALUXPTID BALUXPTID BALUX

----PT PT PT PT ----PTID PUSTAPTID PUSTAPTID PUSTAPTID PUSTA

----PT PT PT PT ----PTID VEBALPTID VEBALPTID VEBALPTID VEBAL

----PT PT PT PT ----PTID VBAPTID VBAPTID VBAPTID VBA

----PT PT PT PT ----PTPTPTPTID NOVLOID NOVLOID NOVLOID NOVLO

----PT PT PT PT ----PTID KOMARPTID KOMARPTID KOMARPTID KOMAR

----PT PT PT PT ----PTID DRVARPTID DRVARPTID DRVARPTID DRVAR

----PT PT PT PT ----PTID UNIPAPTID UNIPAPTID UNIPAPTID UNIPA

----PT PT PT PT ----PTID SPLPTID SPLPTID SPLPTID SPL

----PT PT PT PT ----PTID TIBLAPTID TIBLAPTID TIBLAPTID TIBLA

----PT PT PT PT ----PTID XOLTAPTID XOLTAPTID XOLTAPTID XOLTA

----PT PT PT PT ----PTID RUPAXPTID RUPAXPTID RUPAXPTID RUPAX

----PT PT PT PT ----PTID MOLUXPTID MOLUXPTID MOLUXPTID MOLUX

----PT PT PT PT ----PTID SORPTID SORPTID SORPTID SOR

----PT PT PT PT ----PTID PEVIRPTID PEVIRPTID PEVIRPTID PEVIR

----PT PT PT PT ----PTID GIANPTID GIANPTID GIANPTID GIANOOOO

----PT PT PT PT ----PTID PININPTID PININPTID PININPTID PININ

----PT PT PT PT ----PTID TUNEXPTID TUNEXPTID TUNEXPTID TUNEX

----PT PT PT PT ----PTID CBNPTID CBNPTID CBNPTID CBN

----PT PT PT PT ----PTID DIDONPTID DIDONPTID DIDONPTID DIDON


64

----ATSRT B141 *KO2 RANVAATSRT B141 *KO2 RANVAATSRT B141 *KO2 RANVAATSRT B141 *KO2 RANVA

----ATSRT UP863 RANVA GONOSATSRT UP863 RANVA GONOSATSRT UP863 RANVA GONOSATSRT UP863 RANVA GONOS

----ATSRT UN619 GONOS SOKVAATSRT UN619 GONOS SOKVAATSRT UN619 GONOS SOKVAATSRT UN619 GONOS SOKVA

----ATSRT UM857 SOKVA PODANATSRT UM857 SOKVA PODANATSRT UM857 SOKVA PODANATSRT UM857 SOKVA PODAN

----ATSRT UZ200 PODAN TPSATSRT UZ200 PODAN TPSATSRT UZ200 PODAN TPSATSRT UZ200 PODAN TPS

----ATSRT UM986 TPS PUSTAATSRT UM986 TPS PUSTAATSRT UM986 TPS PUSTAATSRT UM986 TPS PUSTA

----ATSRT ATSRT ATSRT ATSRT UY552 PUSTA VEBALUY552 PUSTA VEBALUY552 PUSTA VEBALUY552 PUSTA VEBAL

----RFL F350 VEBALRFL F350 VEBALRFL F350 VEBALRFL F350 VEBAL

----SPEED N0468 VEBALSPEED N0468 VEBALSPEED N0468 VEBALSPEED N0468 VEBAL

----ATSRT UL196 VEBAL SPLATSRT UL196 VEBAL SPLATSRT UL196 VEBAL SPLATSRT UL196 VEBAL SPL

----ATSRT UM725 SPL SORATSRT UM725 SPL SORATSRT UM725 SPL SORATSRT UM725 SPL SOR

----RFL F370 SORRFL F370 SORRFL F370 SORRFL F370 SOR

----SPEED N0462 SORSPEED N0462 SORSPEED N0462 SORSPEED N0462 SOR

----ATSRT UM725 SOR PININATSRT UM725 SOR PININATSRT UM725 SOR PININATSRT UM725 SOR PININ

----ATSRT UM738 PININ CBNATSRT UM738 PININ CBNATSRT UM738 PININ CBNATSRT UM738 PININ CBN

----ATSRT G727 CBN DIDONATSRT G727 CBN DIDONATSRT G727 CBN DIDONATSRT G727 CBN DIDON

ARRARRARRARR

The arrival message shall contain:


2) The actual day of arrival ADA 3) The departure aerodrome ADEP


5) The actual time of arrival ATA


7) The aircraft identification ARCID 8) The actual time of arrival ATA




Examples:

----TITLE IARRTITLE IARRTITLE IARRTITLE IARR

----ADA 081005ADA 081005ADA 081005ADA 081005


----FAC EPWWZQZXFAC EPWWZQZXFAC EPWWZQZXFAC EPWWZQZX


----FAC LBSFSTATFAC LBSFSTATFAC LBSFSTATFAC LBSFSTAT

----FAC ENOSZQZXFAC ENOSZQZXFAC ENOSZQZXFAC ENOSZQZX

----FAC ENGMZTZXFAC ENGMZTZXFAC ENGMZTZXFAC ENGMZTZX

----FAC LHBPZEZXFAC LHBPZEZXFAC LHBPZEZXFAC LHBPZEZX

----FAC ESMMZQZXFAC ESMMZQZXFAC ESMMZQZXFAC ESMMZQZX

65

----FAC ESMMADXPFAC ESMMADXPFAC ESMMADXPFAC ESMMADXP

----FAC LRBBZQZXFAC LRBBZQZXFAC LRBBZQZXFAC LRBBZQZX


----FAC LZBBZQZXFAC LZBBZQZXFAC LZBBZQZXFAC LZBBZQZX

----FAC LTACYCYXFAC LTACYCYXFAC LTACYCYXFAC LTACYCYX

----FAC LTBAZIZXFAC LTBAZIZXFAC LTBAZIZXFAC LTBAZIZX

----FAC LTBBOVFLFAC LTBBOVFLFAC LTBBOVFLFAC LTBBOVFL

----FAC LTBJZPZXFAC LTBJZPZXFAC LTBJZPZXFAC LTBJZPZX

----FAC LTBJZAZXFAC LTBJZAZXFAC LTBJZAZXFAC LTBJZAZX

----FAC LTAAZQZXFAC LTAAZQZXFAC LTAAZQZXFAC LTAAZQZX

----FFFFAC LTAIZAZXAC LTAIZAZXAC LTAIZAZXAC LTAIZAZX

----FAC LTAIZGZXFAC LTAIZGZXFAC LTAIZGZXFAC LTAIZGZX


----ADEP ENGMADEP ENGMADEP ENGMADEP ENGM

----ADES LTAIADES LTAIADES LTAIADES LTAI

----AOARCID PGTAOARCID PGTAOARCID PGTAOARCID PGT

----ARCID PGT824ARCID PGT824ARCID PGT824ARCID PGT824

----ATA 2354ATA 2354ATA 2354ATA 2354




----IFPLID AA68766309IFPLID AA68766309IFPLID AA68766309IFPLID AA68766309

----ORGNID AROLTAIORGNID AROLTAIORGNID AROLTAIORGNID AROLTAI

----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN NETWORKTYPE AFTN ----FAC LTAIZPZXFAC LTAIZPZXFAC LTAIZPZXFAC LTAIZPZX


CHGCHGCHGCHG

The change message shall contain:


2) The departure aerodrome ADEP

3) The departure aerodrome ADES

4) The aircraft operator identification AOARCID 5) The aircraft identification ARCID 6) The aircraft type ARCTYP 7) The estimated off-blocks day EOBD



10) The route ROUTE

TITLE ICHGTITLE ICHGTITLE ICHGTITLE ICHG


----FAC KZMAZQZXFAC KZMAZQZXFAC KZMAZQZXFAC KZMAZQZX

66

----FAC LFFBTESTFAC LFFBTESTFAC LFFBTESTFAC LFFBTEST

----FAC LPZZFPLOFAC LPZZFPLOFAC LPZZFPLOFAC LPZZFPLO


----FAC LFFFSTIPFAC LFFFSTIPFAC LFFFSTIPFAC LFFFSTIP

----FAC LFPBYRYDFAC LFPBYRYDFAC LFPBYRYDFAC LFPBYRYD

----FAC LIRRZQZXFAC LIRRZQZXFAC LIRRZQZXFAC LIRRZQZX

----FAC LIRFZPZXFAC LIRFZPZXFAC LIRFZPZXFAC LIRFZPZX

----FAC LIIRZEZXFAC LIIRZEZXFAC LIIRZEZXFAC LIIRZEZX

----FAC LPAMYCYXFAC LPAMYCYXFAC LPAMYCYXFAC LPAMYCYX

----FAC LPAMYWYAFAC LPAMYWYAFAC LPAMYWYAFAC LPAMYWYA

----FAC LPPCZQZXFAC LPPCZQZXFAC LPPCZQZXFAC LPPCZQZX

----FAC LESCYFPXFAC LESCYFPXFAC LESCYFPXFAC LESCYFPX



----ADEP LIRFADEP LIRFADEP LIRFADEP LIRF

----ADES KMIAADES KMIAADES KMIAADES KMIA

----AOARCID AZAAOARCID AZAAOARCID AZAAOARCID AZA

----ARCID AZA63KARCID AZA63KARCID AZA63KARCID AZA63K

----ARCTYP B772ARCTYP B772ARCTYP B772ARCTYP B772

----CEQPT SDHIPRWXYZCEQPT SDHIPRWXYZCEQPT SDHIPRWXYZCEQPT SDHIPRWXYZ



----FFFFILTIM 060014ILTIM 060014ILTIM 060014ILTIM 060014


----ORIGIN ORIGIN ORIGIN ORIGIN ----NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA NETWORKTYPE SITA ----FAC FCOOWAZFAC FCOOWAZFAC FCOOWAZFAC FCOOWAZ


----WKTRC HWKTRC HWKTRC HWKTRC H

----NAV RNP10NAV RNP10NAV RNP10NAV RNP10

----RALT LPLA TXKFRALT LPLA TXKFRALT LPLA TXKFRALT LPLA TXKF

----REG IDISEREG IDISEREG IDISEREG IDISE

----RMK TCASRMK TCASRMK TCASRMK TCAS

----RVR 100RVR 100RVR 100RVR 100

----SEL CJAESEL CJAESEL CJAESEL CJAE







----ROUTE N0487F330 ESINO UZ924 KOLUS ROUTE N0487F330 ESINO UZ924 KOLUS ROUTE N0487F330 ESINO UZ924 KOLUS ROUTE N0487F330 ESINO UZ924 KOLUS UM603 ALG UM601 CHELY/N0482F350 UM603 ALG UM601 CHELY/N0482F350 UM603 ALG UM601 CHELY/N0482F350 UM603 ALG UM601 CHELY/N0482F350

UM601 BCN UN975 ESP/N0480F380 UM744 BUSEN DCT VERAM/M084F380 DCT UM601 BCN UN975 ESP/N0480F380 UM744 BUSEN DCT VERAM/M084F380 DCT UM601 BCN UN975 ESP/N0480F380 UM744 BUSEN DCT VERAM/M084F380 DCT UM601 BCN UN975 ESP/N0480F380 UM744 BUSEN DCT VERAM/M084F380 DCT

MANOX/M084F380 DCT 35N020W 32N030W 31N040W 30N050W DCT AYTTE M595 MANOX/M084F380 DCT 35N020W 32N030W 31N040W 30N050W DCT AYTTE M595 MANOX/M084F380 DCT 35N020W 32N030W 31N040W 30N050W DCT AYTTE M595 MANOX/M084F380 DCT 35N020W 32N030W 31N040W 30N050W DCT AYTTE M595

MILLE M330MILLE M330MILLE M330MILLE M330

DONEZ A555 ZQA FLIPR1 DONEZ A555 ZQA FLIPR1 DONEZ A555 ZQA FLIPR1 DONEZ A555 ZQA FLIPR1

----ALTRNT1 KFLLALTRNT1 KFLLALTRNT1 KFLLALTRNT1 KFLL

----EETFIR LIRR 0010EETFIR LIRR 0010EETFIR LIRR 0010EETFIR LIRR 0010

----EETFIR LFFF 0032EETFIR LFFF 0032EETFIR LFFF 0032EETFIR LFFF 0032

----EETFIR LEETFIR LEETFIR LEETFIR LECB 0052ECB 0052ECB 0052ECB 0052

67

----EETFIR LECM 0124EETFIR LECM 0124EETFIR LECM 0124EETFIR LECM 0124

----EETFIR LPPC 0204EETFIR LPPC 0204EETFIR LPPC 0204EETFIR LPPC 0204

----EETFIR LPPO 0258EETFIR LPPO 0258EETFIR LPPO 0258EETFIR LPPO 0258

----EETFIR KZNY 0539EETFIR KZNY 0539EETFIR KZNY 0539EETFIR KZNY 0539

----EETFIR KZMA 0925EETFIR KZMA 0925EETFIR KZMA 0925EETFIR KZMA 0925

----EETPT MANOX 0258EETPT MANOX 0258EETPT MANOX 0258EETPT MANOX 0258

----EETPT *3520 0327EETPT *3520 0327EETPT *3520 0327EETPT *3520 0327



----EETPT AYTTE 0752EETPT AYTTE 0752EETPT AYTTE 0752EETPT AYTTE 0752

----EETPT VINSO 0840EETPT VINSO 0840EETPT VINSO 0840EETPT VINSO 0840

----EETPT RABAL 0855EETPT RABAL 0855EETPT RABAL 0855EETPT RABAL 0855

----EETPT OLEDU 0906EETPT OLEDU 0906EETPT OLEDU 0906EETPT OLEDU 0906

----EETPT MLSAP EETPT MLSAP EETPT MLSAP EETPT MLSAP 0928092809280928

----EETPT ALUTE 0931EETPT ALUTE 0931EETPT ALUTE 0931EETPT ALUTE 0931

----EETPT WITOB 0933EETPT WITOB 0933EETPT WITOB 0933EETPT WITOB 0933

----EETPT KRTIS 0936EETPT KRTIS 0936EETPT KRTIS 0936EETPT KRTIS 0936

----EETPT DIAZZ 0938EETPT DIAZZ 0938EETPT DIAZZ 0938EETPT DIAZZ 0938

----EETPT MUVOD 0941EETPT MUVOD 0941EETPT MUVOD 0941EETPT MUVOD 0941

----EETPT DONEZ 0946EETPT DONEZ 0946EETPT DONEZ 0946EETPT DONEZ 0946

----EETPT BOSAR 0951EETPT BOSAR 0951EETPT BOSAR 0951EETPT BOSAR 0951

----EETPT LEPAS 0952EETPT LEPAS 0952EETPT LEPAS 0952EETPT LEPAS 0952

----EETPT ZQA 0956EETPT ZQA 0956EETPT ZQA 0956EETPT ZQA 0956


----PT PT PT PT ----PTID ESINOPTID ESINOPTID ESINOPTID ESINO

----PT PT PT PT ----PTID GITRIPTID GITRIPTID GITRIPTID GITRI

----PT PT PT PT ----PTID KOLUSPTID KOLUSPTID KOLUSPTID KOLUS

----PT PT PT PT ----PTID MOROBPTID MOROBPTID MOROBPTID MOROB

----PT PT PT PT ----PTID ALGPTID ALGPTID ALGPTID ALG

----PT PT PT PT ----PTID DESOGPTID DESOGPTID DESOGPTID DESOG

----PT PT PT PT ----PTID GOBISPTID GOBISPTID GOBISPTID GOBIS

----PT PT PT PT ----PTID LUTTAPTID LUTTAPTID LUTTAPTID LUTTA

----PT PT PT PT ----PTID BALENPTID BALENPTID BALENPTID BALEN

----PT PT PT PT ----PTID MURENPTID MURENPTID MURENPTID MUREN

----PT PT PT PT ----PTID CHELYPTID CHELYPTID CHELYPTID CHELY

----PT PT PT PT ----PTID VERSOPTID VERSOPTID VERSOPTID VERSO

----PT PT PT PT ----PTID SULIDPTID SULIDPTID SULIDPTID SULID

----PT PT PT PT ----PTID SADEMPTID SADEMPTID SADEMPTID SADEM

----PT PT PT PT ----PTID *BCNPTID *BCNPTID *BCNPTID *BCN

----PT PT PT PT ----PTID ANTONPTID ANTONPTID ANTONPTID ANTON

----PT PT PT PT ----PTID SELVAPTID SELVAPTID SELVAPTID SELVA

----PT PT PT PT ----PTID SALASPTID SALASPTID SALASPTID SALAS

----PT PT PT PT ----PTID RAMONPTID RAMONPTID RAMONPTID RAMON

----PT PT PT PT ----PTID *TOBAPTID *TOBAPTID *TOBAPTID *TOBA

----PT PT PT PT ----PTID ADUXOPTID ADUXOPTID ADUXOPTID ADUXO

----PT PT PT PT ----PTID CJNPTID CJNPTID CJNPTID CJN

----PT PT PT PT ----PTID PALIOPTID PALIOPTID PALIOPTID PALIO

----PT PT PT PT ----PTID VISONPTID VISONPTID VISONPTID VISON

68

----PT PT PT PT ----PTID GOTORPTID GOTORPTID GOTORPTID GOTOR

----PT PT PT PT ----PTID TPTID TPTID TPTID TLDLDLDLD

----PT PT PT PT ----PTID MELONPTID MELONPTID MELONPTID MELON

----PT PT PT PT ----PTID CCSPTID CCSPTID CCSPTID CCS

----PT PT PT PT ----PTID ELVARPTID ELVARPTID ELVARPTID ELVAR

----PT PT PT PT ----PTID BIRBAPTID BIRBAPTID BIRBAPTID BIRBA

----PT PT PT PT ----PTID TAGUXPTID TAGUXPTID TAGUXPTID TAGUX

----PT PT PT PT ----PTID ATECAPTID ATECAPTID ATECAPTID ATECA

----PT PT PT PT ----PTID ESPPTID ESPPTID ESPPTID ESP

----PT PT PT PT ----PTID BUSENPTID BUSENPTID BUSENPTID BUSEN

----PT PT PT PT ----PTID VERAMPTID VERAMPTID VERAMPTID VERAM

----PT PT PT PT ----PTID MANOXPTID MANOXPTID MANOXPTID MANOX

----PT PT PT PT ----PTID *3520PTID *3520PTID *3520PTID *3520




----PT PT PT PT ----PTID AYTTEPTID AYTTEPTID AYTTEPTID AYTTE

----PT PT PT PT ----PTID MILLEPTID MILLEPTID MILLEPTID MILLE


----ATSRT UZ924 ESINO KOLUSATSRT UZ924 ESINO KOLUSATSRT UZ924 ESINO KOLUSATSRT UZ924 ESINO KOLUS

----ATSRT UM603 KOLUS ALGATSRT UM603 KOLUS ALGATSRT UM603 KOLUS ALGATSRT UM603 KOLUS ALG

----ATSRT UM601 ALG CHELYATSRT UM601 ALG CHELYATSRT UM601 ALG CHELYATSRT UM601 ALG CHELY

----RFL F350 CHELYRFL F350 CHELYRFL F350 CHELYRFL F350 CHELY

----SPEED N0482 CHELYSPEED N0482 CHELYSPEED N0482 CHELYSPEED N0482 CHELY

----ATSRT UM601 CHELY *BCNATSRT UM601 CHELY *BCNATSRT UM601 CHELY *BCNATSRT UM601 CHELY *BCN

----AAAATSRT UN975 *BCN ESPTSRT UN975 *BCN ESPTSRT UN975 *BCN ESPTSRT UN975 *BCN ESP

----RFL F380 ESPRFL F380 ESPRFL F380 ESPRFL F380 ESP

----SPEED N0480 ESPSPEED N0480 ESPSPEED N0480 ESPSPEED N0480 ESP

----ATSRT UM744 ESP BUSENATSRT UM744 ESP BUSENATSRT UM744 ESP BUSENATSRT UM744 ESP BUSEN

----DCT BUSEN VERAMDCT BUSEN VERAMDCT BUSEN VERAMDCT BUSEN VERAM

----RFL F380 VERAMRFL F380 VERAMRFL F380 VERAMRFL F380 VERAM

----MACH M084 VERAMMACH M084 VERAMMACH M084 VERAMMACH M084 VERAM

----DCT VERAM MANOXDCT VERAM MANOXDCT VERAM MANOXDCT VERAM MANOX

----RFL F380 MANOXRFL F380 MANOXRFL F380 MANOXRFL F380 MANOX

----MACH M084 MANOXMACH M084 MANOXMACH M084 MANOXMACH M084 MANOX

----DCT MANOX *3520DCT MANOX *3520DCT MANOX *3520DCT MANOX *3520

----DCT *3050 AYTTEDCT *3050 AYTTEDCT *3050 AYTTEDCT *3050 AYTTE

69

ANNEX ANNEX ANNEX ANNEX 2: REQUIREMENTS REFERENCE TABLES2: REQUIREMENTS REFERENCE TABLES2: REQUIREMENTS REFERENCE TABLES2: REQUIREMENTS REFERENCE TABLES

Table 4 features the list of functional and non-functional requirements and Table 5

the matrix of dependencies that may exist among them (the cell is greened if the

dependency does exist between two requirements).

ABCD Requirements

User Requirements Fn-User_If-1 Choose level of service Fn-User_If-2 Display EPOBT and EOBT

Fn-User_If-3 Warn the operator in case of inconsistency with the current EOBT

Fn-User_If-4

Warn the operator in case of inconsistency with the current EOBT by taking into account the stability criteria

Fn-User_If-5 Propose DLA message Fn-User_If-6 Warn AO in case of missing data Non_Fn-User_If-1 Structure of the display Non_Fn-User_If-2 Service level selection window Non_Fn-User_If-3 DLA management window at level 0 Non_Fn-User_If-4 DLA management window at level 1 Non_Fn-User_If-5 DLA management window at level 2 Non_Fn-User_If-6 DLA management window at level 3 Non_Fn-User_If-7 Missing data warning window System Requirements Fn-Syst_If-1 Intercept message Fn-Syst_If-2 Get Aircraft Registration Number Fn-Syst_If-3 Get Minimum Turn-Around Time Fn-Syst_IF-4 Get Taxi-Time Internal Requirements Fn-Int-Trig-1 Create database Fn-Int-Trig-2 Detect active service level Fn-Int-Trig-3 Identify message type Fn-Int-Trig-4 Identify flight ARCID Fn-Int-Trig-5 Store FPL Fn-Int-Trig-6 Validate FPL Fn-Int-Trig-7 Add flight to the database Fn-Int-Trig-8 Store message (except FPL and ACK) Fn-Int-Cont-1 Control message Fn-Int-Trig-9 Update database Fn-Int-Trig-10 Update flight sequence Fn-Int-Trig-11 Calculate EPOBT

Fn-Int-Trig-12 Check compatibility between EOBT / CTOT and EPOBT

Fn-Int-Cont-2 Check the stability criteria

Fn-Int-Trig-13 Prepare DLA message Non_Fn-Int-Trig-1 Update rate

Table Table Table Table 4444: Requirements list: Requirements list: Requirements list: Requirements list

70

Table Table Table Table 5555: Matrix of dependencies: Matrix of dependencies: Matrix of dependencies: Matrix of dependencies (next page) (next page) (next page) (next page)

71

Fn-U

ser_If-1

Fn-U

ser_If-2

Fn-U

ser_If-3

Fn-U

ser_If-4

Fn-U

ser_If-5

Fn-U

ser_If-6

Non_Fn-

User_If-1

Non_Fn-

User_If-2

Non_Fn-

User_If-3

Non_Fn-

User_If-4

Non_Fn-

User_If-5

Non_Fn-

User_If-6

Non_Fn-

User_If-7

Fn-Syst_If-1

Fn-Syst_If-2

Fn-Syst_If-3

Fn-Int-Trig-1

Fn-Int-Trig-2

Fn-Int-Trig-3

Fn-Int-Trig-4

Fn-Int-Trig-5

Fn-Int-Trig-6

Fn-Int-Trig-7

Fn-Int-Trig-8

Fn-Int-Cont-1

Fn-Int-Trig-9

Fn-Int-Trig-10

Fn-Int-Trig-11

Fn-Int-Trig-12

Fn-Int-Cont-2

Fn-Int-Trig-13

Non_Fn-Int-

Trig-1

Fn-User_If-1

Fn-User_If-2

Fn-User_If-3

Fn-User_If-4

Fn-User_If-5

Fn-User_If-6

Non_Fn-User_If-1

Non_Fn-User_If-2

Non_Fn-User_If-3

Non_Fn-User_If-4

Non_Fn-User_If-5

Non_Fn-User_If-6

Non_Fn-User_If-7

Fn-Syst_If-1

Fn-Syst_If-2

Fn-Syst_If-3

Fn-Int-Trig-1

Fn-Int-Trig-2

Fn-Int-Trig-3

Fn-Int-Trig-4

Fn-Int-Trig-5

Fn-Int-Trig-6

Fn-Int-Trig-7

Fn-Int-Trig-8

Fn-Int-Cont-1

Fn-Int-Trig-9

Fn-Int-Trig-10

Fn-Int-Trig-11

Fn-Int-Trig-12

Fn-Int-Cont-2

Fn-Int-Trig-13

Non_Fn-Int-Trig-1

72

END OF THE DOCUMENT

Documents

ABCD Tool Prototype Definition - Eurocontrol · 3 SUMMARY This deliverable (D4), presents the results for Work Package 4 “ABCD tool prototype definition”, as part of the ABCD