1. Work Package 3 Data Management
Giovanni Andreatta, Lorenzo Capanna, Luigi De Giovanni, Luca Righi
CFR – CONSORZIO FUTURO IN RICERCA
Lancaster, March 24th 2017

2. WP3 Data Management
OptiFrame Tools from WP4, WP5, WP6: mathematical models, optimisation algorithms, scenario design, simulation procedures, validation modules etc.
WP3 goal: to provide ATM instance data required by the OptiFrame Tools for testing and validation purposes
WP3 role: to act as an interface between ATM data sources and OptiFrame tools, through the Data Management Platform
WP3 - Data Management

3. WP3 tasks Task 3.1: Design of the DMP
Analysis of preliminary requirements from WP2 (state-of-the-art), WP4 (preliminary models) and WP6 (preliminary simulation scenarios)
Analysis of data sources (mainly from EUROCONTROL)
Modular design of DMP
Task 3.2: Implementation of DMP
Basic data extraction routines
Procedures for instance generation
PERL – text files
Task 3.3: Validation of DMP
Methodology: cross-checking, instance coherence
Correctness, operational performance, network performance
WP3 - Data Management

4. OptiFrame Data Management Platform
WP3 - Data Management

5. DMP design Data sources’ side Different data sources
Different data formats
Modular extension to new datasets: text files!
Common data-extraction routines
Tools’ side
Different data required
Different levels of detail
Different interface functions (tools specific)
DMP guarantees separation between data sources and OptiFrame Tools and modular extension to new tools
WP3 - Data Management

6. Data sources
DDR2 [EUROCONTROL]: data on traffic demand, on a daily basis, for whole ECAC area, since January 2006
Historical data
Filtered data
Airline trajectories
Forecast traffic (STATFOR – Statistics and Forecast)
Dataset files (Airspace description, Route charges)
Tools (SAAM, NEVAC, NEST)
Events
Reports
NEST (Network Strategic Tool), among other features, provides an interface towards DDR2: data download and filtering through text files
WP3 - Data Management

7. Data sources: airspace description
Air block: 2D closed polygon. 2D tessellation of the airspace
Elementary sector: 3D connected space airblock(s) + min/max FL
WP3 - Data Management

8. Clustered sectors
Clustered sectors: aggregate elementary/clustered sectors, may overlap
WP3 - Data Management

9. Control areas Control Area (CTA) Dynamic airspace configuration
Opening schemes - day-of-the-week - hour of the day (peak/off-peak)
Enabled sectors: sectors are defined in 4D
WP3 - Data Management

10. CTA dynamic configuration
1 sector
2 sectors
3 sectors
4 sectors
WP3 - Data Management

11. Capacities
Maximum number of aircraft that can enter a sector per time unit
Airports: maximum declared number of A/D at an airport per time unit (limited data available from DDR2)
Described by Traffic Volumes associated to airspace entities
Enabled sectors (include in current CTA configuration)
Active traffic volumes
Exceptions (e.g. flows)
Capacities are dynamic: depend on traffic - control resources
Sector capacity profile (enabled/not enabled, active traffic volumes)
WP3 - Data Management

12. Network description
Navigation points: 2D positions (waypoints, standard waypoints)
Segments
WP3 - Data Management

13. Traffic data Historical data on flight 4D trajectories
Filed Tactical Flight Model (FTFM)
Regulated Tactical Flight Model (RTFM)
Current Tactical Flight Model (CTFM)
Available information:
Flight ID (date, airports, times, callsign …)
Aircraft type
Crossed airspace elements (sector, waypoint …; FL; time enter/exit)
WP3 - Data Management

14. Routines for data extraction
AIRAC (Aeronautical Information Regulation and Control) archives
Each archive contains data on one AIRAC cycle (28 days)
Information available from several text files (available directly from DDR2 or from NEST exporting utilities)
Routines developed in PERL (Practical Extraction and Reporting Language)
Parsing via regular expressions
Free utility packages (e.g. geometrical manipulation of airspace elements)
Main procedures
Sector network text files
ExtractSectNet
AIRAC text files
Routines for data extraction organized into three main procedures
LoadAIRAC : AIRAC text files  memory data structures
ExtractSectNet : memory  sector network text files
ExtractNetTraffic : memory  waypoint network + flights text files
Memory data structures
LoadAIRAC
Waypoint network + flight text files
ExtractNetTraffic
WP3 - Data Management

15. Cross-validation
LoadAIRAC, ExtractSectNet and ExtractNetTraffic determine overlapping information
Sectors (airspace description / crossed)
Adjacencies (geometry / observed connections)
Relations among airspace elements
Sector network
Validation through cross-checking, e.g.:
ExtractSectNet network contains ExtractNetTraffic network
Inclusion of waypoints into sectors coherent with 3D sector shapes
WP3 - Data Management

16. Example: EGLL – EDDF network
AIRAC Oct 2016
38 flights
~ 30 standard waypoints per route
Base networks includes all crossed sectors and standard waypoints
2 airports
32 sectors
47 sector adjacency-edges
63 standard waypoints
76 standard waypoints-arcs
WP3 - Data Management

17. Example: EGLL – EDDF network
Expanded network all standard waypoints in crossed sectors
2 airports
32 sectors
113 sector adjacency-edges
501 standard waypoints
1266 standard waypoints -arcs
WP3 - Data Management

18. Issues about data requirements
Modular design open to different tools (mathematical models, optimization algorithms, simulators etc.)
Tools require the same information with different levels of detail
Mathematical models need compact network representation; simulators need detailed network
Map highly detailed elements into more aggregate ones (and vice versa)
Tools require different data
e.g. mathematical models do not need geometrical information; simulators need the geometry of airspace elements
Data not directly available from data sources
e.g. min/max vertical/horizontal speed, allowable FLs, airport capacities
tools give specifications on how to estimate information from extracted data (e.g. estimate from historical data, datasheets etc.)
WP3 - Data Management

19. Conclusions and future work
WP3 develops the Data Management Platform (DMP) to populate instance data needed by OptiFrame tools (WP4, WP5 and WP6)
Modular design of the DMP
Adapt to different data requests
Interface based on text files
Three main procedures for data extraction implemented
Information available at different levels of detail (sector network, waypoint network)
Current and future work:
Data extraction from several AIRAC archives
Integration with OptiFrame tools for testing and validation purposes
DMP will follow the evolution of WP4, WP5 and WP6 (data requirements, file format)
WP3 - Data Management

20. Thank you very much for your attention!
WP3 – Data Management
Thank you very much for your attention!