Presentation Eurocontrol CDM Project - Airport Collaborative ...

CDM TF/11 

29th & 30th November 2005 

Airport CDM Project 

by the 

EUROCONTROL CDM Team



Frequent Asked Questions 

(Elisabeth Lagios - Airport CDM Project Manager)


Frequently Asked Questions (FaQ) – IP2 

General – Information Sharing, Turn-round 

procedures and VTTTs - were based on CDM TF/9 & 

10 WG Conclusions 

FUM / DPI Collaborative Management of Flight 

Updates – Current Airport Trials & CDM TF/12 WG in 

May 2006 

CDM in Adverse Conditions & Predepature 

Sequencing – will be based on CDM TF/9-11 

Conclusions and for inclusion in Implementation 

Manual by June 2006



Airport CDM Level 3 

OCD & FRD 

(Roger Lane – EEC Airport CDM Project Manager)


CDM LEVEL 3 - (COLLABORATIVE PREDEPARTURE 

SEQUENCE AND CDM IN ADVERSE CONDITIONS) IP3 

Operational Concept / Functional Requirement Documents 

OCDs discussed/reviewed in subgroup at Task Force 10. 

Revised version sent to a limited group of TF members for 

further review prior to a final internal review. 

FRDs were drafted once the OCDs were completed and had 

been internally reviewed. 

The documents will now be included in the main OCD/FRD 

documents – which in turn will be used to produce an update of 

the CDM Implementation Manual in July 2006



Cost & Benefit Analysis 

(Maria Christina Meyer - Airport CDM Project team)

First CBA available 

Progress Report - Airport CDM Project CBA 

Current Status: 

Scope: Airport CDM Level 1 applications 

Airport Information Sharing 

Turn-Round Processes 

You can find the final CBA report at 

our website: www.euro-cdm.org 

What are the next steps?


Develop and deliver in 2006: 

Next Steps: 

CBA for Level 2 / 3 applications 

Collaborative Management of Flight Updates 

Variable Taxi-Time Calculations 

Collaborative Predeparture Sequence based on 

Preferences 

CDM in Adverse Conditions 

Consolidated Airport CDM CBA including 

results for Level 1 / 2 / 3 applications 

External sub-contractor selection process currently in its 

final phase

Challenges: 

Uncertainties 

Many airport profiles 

Different nature of airport 

problems and eventual CDM 

benefits 

Many stakeholder groups involved 

Double counting avoidance 

Confidentiality of data 

Use lessons learnt from first CBA 

Take advantage of the maturity 

obtained in past years 


Critical Success Factors: 

Transparency of CBA process: 

it should be clear « how » results are 

achieved 

Each stakeholder group should get a 

clear view on their own individual 

costs & benefits 

Results presented should be 

comprehensive and user friendly 

Stakeholders involvement from the 

beginning and throughout the 

complete process


Objectives: 

Provide a robust and reliable « tool » to support 

decisions on further investments 

Provide good guidance to perform Airport CDM 

CBA at local airport level using standard 

guidelines 

Airport CDM must be valued – This CBA should 

help! 

How will we achieve this?


A New Approach: 

The quality of the process is key to obtain 

transparency 

Eurocontrol EMOSIA methodology will be followed: 

European MOdel for ATM Strategic Investment Analysis 

A standard approach, an structured methodology, a set of tools for 

Cost & Benefit Analysis 

Based on industry best practice and stakeholders’ contribution 

Applied to a number of EUROCONTROL and EC programmes, 

e.g. Link2000+, CASCADE, CAMES, C-ATM, SEAP, 

Nordic SWIM, SENSE

EMOSIA strengths: 


A New Approach: 

Management of uncertainties (Risk Analysis) 

Focus on what really matters by identifying the most critical 

variables to success of the project 

(Sensitivity Analysis) 

Use of standard inputs (knowledge from past CBAs) 

Consistent, transparent and flexible 

The approach lends itself to working closely 

with stakeholders

Level 1 Level 2 

Level 3 


Airport CDM Information Sharing 

CBA performed ! 


CDM Turn-round Process 

Collaborative Management of 

Flight Updates 

Variable Taxi Time Calculation 

Collaborative Predeparture 

Sequence 

CDM in Adverse Condition 

Stakeholders Involvement: 

Workshops, visits to airports, local data analysis and regular validations 

Airports in general 

CBA Level 1 

Applications 

Generic 

CBA 

Generic 

CBA 

Generic 

CBA 

Generic 

CBA 

Generic CBA – all levels 

EMOSIA Methodology 

Airport 

1 Airport 

2 

Specific Airports 


3 

Parallel activities during 2006 


4 

Site Specific 

CBAs 

Other 

Airports 

(optional)

Standard framework 

definition to be used as a 

start-point for Site Specific 

CBAs 

Not directly dependent 

on data from 

local airport trials 

Stakeholders 

will be involved 

through workshops 

(trial airports 

and others) 

Top-down approach 


Identify expectations, 

potential benefits 

and costs 

Qualify and quantify 

as much as possible 

Ensure 

uncertainties are 

well considered 

Based on 

expert judgement, 

experience, 

results from studies 

and from trials 

conducted so far 

Generic 

CBAs 

Results serve as 

validation for 

Generic CBAs 

Site 

Specific 

CBAs 

Local 

stakeholders 

will be involved 

through workshops , 

data collection 

and 

analysis 

Evaluate 

local airport 

specific 

costs & benefits 

Local data is 

the main 

source of 

information 

We want 

to ensure diversity of 

airport profiles


Planning & Milestones: 

Jan 2006 – Kick-off meeting with sub-contractor 

End Feb 2006 – Workshop Level 3 Applications Generic CBA 

Q1 2006 – Level 3 Applications Generic CBA 

Q2 2006 – Workshop Level 2 Applications Generic CBA 

Q2 2006 - Level 2 Applications Generic CBA 

Q3 2006 – Workshop for Consolidation of CBA results 

Q4 2006 – Generic CBA all levels 

Airports interested to participate in Site Specific 

CBAs, please, contact Elisabeth Lagios or myself


Strategic fit of Airport CDM 

& 

OATA Architecture 

(Milen Detchev - OATA Project Manager)

Navigation 

Aids 

PSR, 

SSR 

Mode-S 

Radar 

CNS 

ADS 

Air 

Surveillance 

Aircraft 

Navigation 

Multilateration 

Ground 

Surveillance 

Air/Ground DL Services 

Pilot 

Aircraft 

Surveillance 

Aircraft 

Autonomous 

Sensors 


Surveillance 

Detection 

Equipment 

ADS - B 

OATA Clusters 

Executive & Planner 

Controller 

ACC Supervisor 

Multi Sector Planner 

Tactical Load Mng 

ATM 

En-route/APP 

ATC 

Flight 

Management 

Tower Ground 

Controller 

Tower Runway 

Controller 

Tower Supervisor 

Aerodrome 

ATC 

Aerodrome 

Shared 

Elements 


Operator 


Operations 

Airspace 

Shared 

Elements 

Pilot 

Aircraft 

Operator 

Airspace 

User 

Operations 

Communications and Distributed System Services 

Aircraft 

Shared 

Elements 

Flow 

Manager 

Network 

Manager 

ATFCM 

Shared Elements (Cross-Domain Modules) 

Meteo 

Service 

Provider 

Aeronautical 

Information 

Service 

Provider 

Airspace 

Manager 

Airspace 

Organisation & 

Management 

Meteo 

Shared 

Elements

Cross-Domain Modules 

(built in interoperability) 

Identification of data and functionality common to 

different ATM domains 

Ensure that everybody has the same information 

System-Wide Information Management (SWIM) 

Communicate updates immediately, everywhere 

Ensure data ownership rights, etc. 

Are not just data stores but provide services 

standardise the services that will access the shared data, 

rather than standardising the data, avoiding the risk that data will be 

used in a different way. 

Consequently everybody interprets the data in the same way

Flow Manager 

Network Manager 

Air Traffic 

Controllers 

Aeronautical 

Information 

Management 

Aeronautical 

Information 

Management 

Decision 

Support etc. 

Modules 

Use of Cross-Domain Modules 

Configuration 

Management 

Configuration 

Management 

Decision 

Support etc. 

Modules 

Flight 

Management 

Flight 

Management 

ATC Constraint 

Management 

Aircraft 

cross-domain synchronisation – common view shared by ATC and ATFCM 

Aircraft

ACC1 

ACC2 

ACC3 

Cross-Domain Module Specialisation 

ATC 

Common 

Core 

Specialisation 

CFMU/Brussels 

Common 

Core 

ATFCM 

Common 

Core 


CFMU/Brétigny 


Common 

Core 


Airport 2 

Airport 1

Levelling of Current Activities 

SWIM a Framework for all Requirements needed to be able to fulfil Operational 

Concepts like CDM, e.g. legal, institutional, business, organisational, operational and 

technical. 

CDM, part of the Operational Concept, who is co-operating with whom and which 

information is required to co-operate effectively. 

OATA Cross Domain Modules (SPECIFICATION), the information and corresponding 

services which will be shared. 

Level used by the ATM Developers of the other ATM functions (MTCD, Coordination and Transfer, 

Departure Management, Demand Capacity Balancing). 

They do not have to worry about geographical and system boundaries. The cross domain modules 

will take care, that they get the information they need in time, even when it is stored elsewhere. 

IMPLEMENTATION, two current directions for solutions 

FOIPS the implementation of the Flight Manager. Based on the Flight Manager Services, they will 

define the data to be shared and all requirements for that data sharing. 

For AIM the EAD is the centralised solution for data sharing, The XML based interface of the EAD 

will probably be used by the AIM cross domain modules to collect the iformation to provide the 

services to the AFTCM and ATC applications. 

Industry is looking at COTS mechanisms to support information sharing. (System and 

Middleware Support). 

Principles for Cross Domain Synchronisation addresses this level and investigates possible 

solutions based on Distributed Databases (Relational, OO and/or Real Time), CORBA and/or XML 

based publish/subscribe mechanism etc.



Airport CDM Training 

& 

Athens Data Analysis 

(Velissarios Eleftheriou - Airport CDM Project team)


Airport CDM Training Course 

Free of charge (for AOP, AO, ATC, GH) 

2 successful courses in 2005 

IANS (Luxembourg): 17-19 May and Nov 2006 

Locally at Airports: upon request (already LHR, BRU) 

Contact: velissarios.eleftheriou@eurocontrol.int

Athens Airport Data Analysis 

Busy Period 01 AUG – 15 SEPT 2004 (approx. 14,000 dep.) 

2004 Summer Olympic Games – Special procedures in place 

Data sets: local CDM Tool (not operational) and CFMU 

Objective: Predictability 

“… Predictability is of major importance in airline and airport 

scheduling. Cutting 5 min. off 50% of schedules would be worth 

some € 1000 million per annum in better use of airline & airport 

resources...” PRR 8 

Report on www.euro-cdm.org 

Airport CDM Project


Athens Airport Data Analysis



• Local Data – flights with actual delay 30-60 min. 

• CDM warning 1-5 hrs in advance for 77.5% of these flights



• Local Data – flights with actual delay 60-90 min. 

• CDM warning 1-5 hrs in advance for 75.9% of these flights



• Comparing CFMU & Local Data – flights with DLA msg 

• CDM warning before the DLA was sent for 71.9% of them



• CFMU vs Local Data – flights with actual delay > 15 min 

• Left: Flights without a DLA msg 44.7% 

• Right: Flights with CDM warning 73.7%



• Comparing CFMU & Local Data – flights missing their CTOT 

• CDM warning for 72% of them


DMAN & CDM 

(Volker Huck – DMAN Project Manager)

DMAN & CDM - History 


DMAN was in ASA (Automated Support to ATS) project 

ASA projects’ life-cycle: Initiation, Development, Validation >> 

Deliverables included validated OCD / ORD 

DMAN is half through validation, that means nearly finished 

ASA dissolved >> Projects now in TMA2010+ and FASTI (Fast 

Implementation) 

DMAN split between TMA2010+ (adv. DMAN) and airport CDM 

(basic DMAN)


DMAN & CDM – Basic vs Advanced DMAN 

Basic DMAN translates ready push-start into availability at RWY 

with tables. Then creates a good sequence and delivers MTOT 

and MOBT. 

Basic DMAN is in final stages of validation 

Adv DMAN (now called “Departure Metering”) works on airport 

clusters and tries to avoid uneven loading of exit fixes, probably 

with “mini-slots” 

Departure Metering is between initiation phase and development 

Both functions can and shall work together and independently 

Basic DMAN >> airport CDM 

Adv DMAN >> TMA2010+

DMAN & CDM - Validation 


Fast time simulations: Executed on two sequencers, based on 

traffic observations at EBBR, EGLL, EGKK, LEMD, LOWW. 

Measured: throughput, slot-compliance, predictability, 

environment. 

Impact: Done 

Real time simulations: RTS1, RTS2, RTS3 on ESSA (5 weeks 

total), part of G2G. 

Measured: controller acceptance, workload, throughput, 

environment 

Impact: Nearly done

DMAN & CDM – Field Trials 

EBBR and maybe more... 


Initial set-up at EBBR: life, but needs improvement on the 

interface to the AMS (ATC) system 

Objectives: 

Integration into Airport CDM procedures 

Automatic generation of A-DPI 

Implementation support (guidance, performance standards, 

simulations) 

Airport specific and traffic specific benefit assessment 

Implementation incentives? (some benefits x-feed to downstream 

units, dest. airports and CFMU)



Implementation Manual, Distribution & Updates 

(Dave Booth - Airport CDM Project team)



Distribution Status: 

150 Manuals distributed so far 

On going distribution to Airlines (organised in close 

collaboration with IATA) 

On going coordination with ACI EUROPE for distribution 

to airports (Raising Awareness of CDM at Airports)



Updates Planning: 

Version 2 – Q1 2006 

Generic MOU to be added 

FAQ to be added 

Updated List of Acronyms 

KPI’s Guidelines 

New Animations CD 

Any sample documents



Updates Planning: 

Version 3 – Q3 2006 

Level 3 Applications 

Generic Procedures 

CBA Guidelines 

Version 4 – Q4 2006 (Optional)



Raising Awareness 

& 

Promoting CDM Implementation 

at Airports 

(Dave Hogg - Airport CDM Project team)

Raising Awareness & Promoting CDM 

Implementation at Airports 

The roll out CDM Implementation at Airports: 

30+ Airports 2006 – CODA List of critical Airports 2005 

Standard cycle applied: 

Convince Higher Management on Airport CDM potential 

Assist with the initial setup (how, what, when… etc) and the execution of 

CDM implementation locally e.g. Implementation Manual 

Disseminate best practice, lessons learnt and offer remote facilitation for 

successful implementation 

Potential optional support: 

Facilitate WG sessions, local training sessions 

All subject to Management Approval, 

budget and resource availability 

Airport CDM Project

Thank you

Presentation Eurocontrol CDM Project - Airport Collaborative ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?