Domino: The structure

Author: Luis Delgado

Domino’s project is structured in 6 workpackages as shown in the following image:

WP3 will analyse the current and future structure of the ATM system and define the mechanisms and the case studies that will be tested by Domino. These first case studies are the investigative case studies which will set the first set of scenarios to be tested. WP4 will develop an Agent Based Model (ABM) which will be able to execute the different scenarios. In Domino, we understand the different actors in the system as agents which try to optimise their utility functions subject to the system constraint and the environment. The system constraints are changed when different mechanism are implemented as different options arise; and the environment in ATM is subject to uncertainty that the actors need to manage.

The metrics generated by the ABM will cover the impact on both flight and passengers. These outcomes will be analysed by WP5 where a Complexity Science toolbox will be used in order to generate knowledge on the status of the system. Traditional and complex metrics will be generated but also specific network analysis to understand how the elements in the system are coupled and where the bottlenecks are generated. Once again this dual view flight an passenger perspective of the system is core in these analyses.

WP2 will provide support to the other technical packages in terms of data requirements, acquisition and preparation. Domino will model a past day of operations with new mechanisms applied to it.

Finally, Domino requires close collaboration and feedback from stakeholders and experts. This will be achieved with the interactions in WP6. The mechanisms will be subject to a consultation, the model developed in WP4 will be calibrated with the help of stakeholders and the results of the investigative case studies shared in a workshop (to be run in Spring 2019). This workshop be the forum where adaptive case studies will be selected. These case studies try to mitigate some of the network issues identified on the investigative case studies results. The adaptive case studies will be run again from WP3 to WP5 to develop the Domino's methodology: you have a new mechanism (technological or operational change) and you'd like to learn about its impact in the ATM system; this mechanism is modelled within the ABM framework; tested with the Complexity Science toolbox; and once hotspots are identified can be mitigated creating new scenarios to test!

Keep in touch to learn more or provide feedback to Domino and follow our updates regarding the preliminary results and the workshop!

See for more info on the project.

Domino: The knock-on effect

AUTHOR: Luis Delgado

The objective of Domino is to analyse the coupling of elements in the ATM system and how changes (for example, by implementing different mechanism) have an impact on the interrelationships between elements. In order to achieve this, Domino will develop a set of tools, a methodology and a platform to assess the coupling of ATM systems from a flight and a passenger perspective.

Different actors in the ATM system might have different views of its elements and their criticality. For this reason, Domino adds the passenger's view to the more classic flight-centred vision.

In Domino, the ATM system is seen as a set of elements that are related to each other by how the different actors (airlines, flights, passengers, airports, etc.) use them. The behaviour of these actors depend on the available rules of the system. These rules are defined, partially, by the mechanisms that are in place. Complexity Science tools will allow us to understand how the elements in the system are interconnected and how these connections change when the system is modified.

Domino will develop an Agent Based Modelling platform to capture the different systems' relations, and it will focus on three mechanism, implemented and deployed with different scope: Dynamic Cost Indexing (DCI), User Driven Prioritisation Process (UDPP) and Extended Arrival Manager (E-AMAN). Domino will provide a view of the effect of deploying solutions in different manners, e.g., harmonised vs. local/independent deployment.

If a piece in the system is knocked which others are going to be affected? Let Domino tell us!

See for more info on the project.

Connect with us!