Software design for validation scenarios execution Abstract

This report is the deliverable D5.1 of the H2020 SESAR CREATE project. The purpose of this document is to outline the experimental approach which shall be used to perform the initial “proof-of-concept” experiment of the CREATE concept of operations (CONOPS) and its solutions developed under the previous work packages:

  • CREATE Solution 1: Multi-scale multi-pollutant air quality system (AQS);
  • CREATE Solution 2: Framework for multi-aircraft environmentally-scored weather-resilient optimized 4D-trajectories in the flight execution phase, WAAP = Weather Avoidance for extended ATC planning.

As solution 2 has been embedded within solution 1, the validation of both solutions is part of the same experiment (plan). The main experimental objective is to test the integrated concept of the various computational modules within the solutions, and to investigate if the solutions provide operational benefits for the following use-cases;

  • TMA Naples a` reduced LAQ impacts and efficient thunderstorm evasion;
  • En-Route North-Atlantic tracks extending into the European Civil Aviation Conference (ECAC) areaa`reduced environmental impacts in terms of CO2 and non-CO2 metrics in climate sensitive areas, and efficient contrail and thunderstorm evasion.

For both use-cases a reference run derived from historical data shall be used as a baseline. The solution runs shall have the CREATE solutions activated to measure the differences in operational performance with respect to the baseline runs. The presented experimental plan focuses on TRL1 criteria for the solutions’ maturity assessment.

As the computational modules for the CREATE WAAP framework have been developed by various partners, using various independently operating software tools, it has been decided to perform the validations via a “distributed fast-time simulation (FTS)” method. This method uses a centralised database (i.e. NLR external Sharepoint) where the various inputs and outputs of the modules will be stored. Via a linear process each module will be run individually, taking the inputs from the database, and after the computation storing the output in the database. The downloading/uploading of files to the database is a manual (non-automated) process.

The results of the experiment shall be documented in CREATE deliverable “D5.2 Procedures validation identifying potential benefits and risks and stakeholders implementation suggestions”.