The GATE4Rail project will start with the definition of the railway and GNSS scenarios and requirements together with reference test cases.
With a clear definition of the context in terms of railway and GNSS scenarios, requirements and test cases, the GATE4Rail project will define methodology and tools both for GNSS characterization in the railway and tests environment automated update, and will compare these tools in terms of expected (theoretical) performances and trade-offs descending from a SWOT analysis, in order to select the common reference architecture blocks for implementing a virtualized simulation and verification infrastructure.
At this stage, the project will set up a “Proof-of-Concept”, in the form of a virtualized demonstrator of the reference architecture connecting GNSS and railway blocks. Starting from the defined detailed requirements and interfaces of each module with the others, Key Performance Indicators will be defined and evaluated to verify the effectiveness of the reference architecture taking into account the safety approval procedure. The defined tools for automated test repetition, integration and evaluation will be tested and evaluated.
In the last phase, the GATE4Rail project will evaluate, in a final demo on selected railway tracks in Italy and in Spain according to the identified scenarios of interest, the performance of the simulation and verification infrastructure connecting the different GNSS modules and the railway CEDEX laboratory both in nominal and fault conditions, taking into account the global (satellite clock and ephemeris error, anomalous ionospheric conditions) and local hazards (severe multipath, unintentional and intentional interferences).
The defined tools for automated update, integration and test repetition will be evaluated, taking into account the links to the safety approval. An innovation plan will be elaborated considering the main achievements and results carried out in the project. A roadmap will be defined not only for the system by itself but also for the discussion of the results with the proper standardization authorities. The GATE4Rail project will start with the definition of the railway and GNSS scenarios and requirements together with reference test cases. With a clear definition of the context in terms of railway and GNSS scenarios, requirements and test cases, the GATE4Rail project will define methodology and tools both for GNSS characterization in the railway and tests environment automated update, and will compare these tools them in terms of expected (theoretical) performances and trade-offs descending from a SWOT analysis, in order to select the common reference architecture blocks for implementing a virtualized simulation and verification infrastructure.
At this stage, the project will set up a “Proof-of-Concept”, in the form of a virtualized demonstrator of the reference architecture connecting GNSS and railway blocks. Starting from the defined detailed requirements and interfaces of each module with the others, Key Performance Indicators will be defined and evaluated to verify the effectiveness of the reference architecture taking into account the safety approval procedure. The tools defined for automated test repetition, integration and evaluation will be tested and evaluated.
In the last phase, the GATE4Rail project will evaluate, in a final demo on selected railway tracks in Italy and in Spain according to the identified scenarios of interest, the performance of the simulation and verification infrastructure connecting the different GNSS modules and the railway CEDEX laboratory both in nominal and fault conditions, taking into account the global (satellite clock and ephemeris error, anomalous ionospheric conditions) and local hazards (severe multipath, unintentional and intentional interferences).
The defined tools for automated update, integration and test repetition will be evaluated, taking into account the linking links to the safety approval. An innovation plan will be elaborated taking intoconsidering the main achievements and results carried out in the project. A roadmap will be defined not only for the system by itself but also for the discussion of the results with the proper standardization authorities.
| WP | Goal |
| WP1 – Project Management |
- to ensure efficient coordination of the project together with the Technical Management Team
- to coordinate the technical work of the various WPs in order to keep the alignment with the overall objectives of the project
- to ensure efficient management of common consortium activities;
- to ensure efficient overall administrative and financial management of the project
- to manage the internal and external communication, assessing and reporting on the progress made to S2R JU and to partners
- to perform risk management, defining the risk mitigation strategies in order to achieve the complete project objectives in time
- to achieve a stringent collaboration with S2R-CFM-IP2-01-2018 call since beginning of the project to align objectives and maximise results
|
| WP 2 – Railway Scenarios Requirements and Test Cases Definition |
- to identify use cases in the railway environment and the related scenarios of interest. Main requirements will be defined in terms of geo-localization performances and key elements to be modelled in the simulations
- to identify use cases in the railway environment and the related scenarios of interest. Main requirements will be defined in terms of geo-localization performances and key elements to be modelled in the simulations
|
| WP 3 – Methodology Development of the GNSS Characterization in the Railway |
- Identify the main Gate4Rail simulation blocks required for assessing the GNSS performance in the railway operational environment and then the end impact on virtual balise detection, considering the real train mission profiles
- define the high level interfaces between the different blocks
- Identify and model the GNSS global and local hazards in order to feed the GNSS simulation block according to the railway scenario
|
| WP 4 – Geo-distributed Verification Infrastructure Set-up |
- to identify the functional and operative requirements of the geographically distributed simulation and verification infrastructure, in terms of main blocks and interfaces among them, able to exploit the features of partners GNSS and ETCS/ERTMS laboratories
- to design, develop and test of the interfaces among the different the geo-distributed simulation and verification infrastructure connecting GNSS labs (GUIDE, M3SB, IFSTTAR and RDL) and ETCS/ERTMS ones (CEDEX). The design and development of the main modules of the GATE4Rail architecture will start from the tools already available in each GATE4Rail laboratory
|
| WP 5 – Methodology and Tools Definition for Automated Update of Test Environment |
to define the methodology and tools needed to allow GATE4Rail simulation infrastructure upgrade and the functionalities extension in line with future evolution of the ‘GNSS for rail’ context.
Since the whole context (including regulation, use case) is subject to continuous evolution, it is crucial to develop and deliver a simulation infrastructure able to follow these changes according to future needs and requirements. |
| WP 6 – Concept and Methodology Definition for Continuous Integration, Automated Test Repetition and Evaluation |
to define the approach to ensure a continuous integration, automation of test repetition (including automatic analysis of the test results).
Use cases will be defined and described in a structured way through modelling formal languages (such as UML or SysML). The test scenarios will be automatically derived from these use-cases, so allowing the tests to be defined and performed automatically. |
| WP 7 – Project Dissemination and Promotion |
This WP seeks to ensure proper dissemination and promotion of the project, providing the highest visibility and raising public awareness of ETALON framework, objective, content and results to all the important actors and stakeholders of the European railway sector, , in a way that is consistent with the wider dissemination and promotion activities of Shift2Rail.
A further objective of this WP is to collect feedback on the project’s preliminary outcomes to increase the quality and acceptance of the final results. |
