LEONARDO - Linking Existing ON Ground, ARrival and Departure Operations
Overview
Background & policy context:
Nowadays airports are facing the challenge of constantly increasing air traffic. A challenge that requires procedures and systems that can guarantee the safety and the efficiency of the operations. Better prediction of flight behaviour and enhanced management of available resources becomes essential.
The main problem that LEONARDO intends to solve is the lack of coordination and efficiency in the context of Airport Arrival, Departure and Ground movement and operations, which leads to unacceptable amounts of delays and operating costs. It is foreseen that the airport and its surroundings will become the main limiting factor of the whole ATM system.
Objectives:
The main objective of LEONARDO is to define the method and demonstrate the feasibility of integrating existing tools for arrival, surface and departure planning management, together with those derived from the stand allocation management and the turn-around management. This objective will be achieved by performing a full-scale integration of these tools at Barajas and Charles de Gaulle airports under real operating conditions.
This integration will enable:
- Exchange of information between tools. Already existing information somewhere in the system will be distributed to additional actors / tools.
- Co-operation between tools and actors to improve individual planning processes and its estimates as well as the global efficiency of airport operations. As far as possible, tools will take into account requests and constraints from their 'neighbours'.
The implementation of tool negotiation processes through a Collaborative Decision Making Multi Agent (CDMMA) benchmark will complement the study and will be a step further towards an integrated system. Existing planning processes will be modified to take into account priorities of other actors. If all actor priorities can not be taken into account, the negotiation process will be launched.
Methodology:
The solutions proposed by LEONARDO, as explained in the previous section, include an integration of airport systems that will be used by different actors and a set of procedures that impulse the collaboration between such actors. The objective, as stated above, is to demonstrate the feasibility of the proposed solutions.
Thus, the approach defined by the LEONARDO Project to achieve its objectives is a twofold approach. On the one hand, there is a need to define the scope of the validation, i.e. the
expected benefits that will be investigated to demonstrate the feasibility of the proposed solution and the means that will be used for it. On the other hand there is a need to define, specify the integrated systems and the procedures that are proposed as solutions to the stated problems, and to develop the systems. Both approaches have to be in parallel, and co-ordination and interchange of information are needed:
- The benefits expected depend on the solution (system and procedures) that is proposed.
- The definition of the validation scope will help to decide the validation techniques to be used and, thus if there is need to develop any system.
- The validation design and the development of the needed systems for the trials have to be co-ordinated.
LEONARDO project has been structured in seven work packages:
- The concept and system definition and the system specification have been performed by WP1 Requirements and tool specifications:
The operational concept defined by LEONARDO (see section 2.1) was defined from a general point of view. Taking into account the operational concept proposed by LEONARDO a 'Common Integration Model for Experimentation' was defined and specified [D1.1]. This model should be considered as a medium-term (2005-2010) integration model of the different airport planning tools. From the common integration model a description of the local implementations at each site were performed, adapting the common model to the different contexts and circumstances of the two selected airports [D1.2]. The objective was to detail the functional requirements specifications of such integrations, at Madrid-Barajas and Paris-CDG airports, and to compare each functional requirement specifications between each others and with the Common Model. Finally, the technical specifications for the two airports implementations were identified [D1.3]. - The definit
Share this page