Periodic Reporting for period 2 - FP2 - R2DATO (Europe’s Rail Flagship Project 2 - Rail to Digital automated up to autonomous train operation)
Période du rapport: 2024-01-01 au 2024-12-31
The FP2 R2DATO project focuses on leveraging digitalization and automation to enhance rail operations, particularly through the development of next-generation Automatic Train Control (ATC) systems, including fully autonomous train operations (GoA4).
The project integrates multiple clusters to achieve these goals:
1. Automation Processes: Focuses on achieving automated to autonomous train operations, developing the related core technologies in connexion with other initiatives such as System Pillar and Flagship Project 5 and 6.
2. Optimized Headway: Aims to validate prototypes for the European Rail Traffic Management System (ERTMS) game changers in different operational environments, improving train control and braking performance in various operational environments, with mixed radio based ETCS levels with Hybrid Level 3, ETCS L3 moving block, absolute train position, train integrity and train length management, as well as optimized and reproducible braking performance under low adhesion conditions..
3. Enabling Digital Technologies: Develops specifications and validates prototypes related to connectivity (both for train-to-ground communication and onboard communications), modular IT platforms, and the Digital Register to provide the future-proof connectivity, IT and data platforms required for the automation of rail operations.
4. Fast and Efficient Deployment: Assesses technology for Digital Automatic Train Operation (DATO), aiming for quick deployment and developing guidelines for migration and certification, using innovative modelling techniques for automatic approval and certification.
5. Innovative Operational Solutions: Explores the added values of innovative concepts such as Autonomous Route Setting and Virtually Coupled Train Sets to enhance network capacity and autonomous operations.
6. Demonstrators: Validates the benefits of DATO technologies through demonstrations in controlled environments, focusing on achieving specific Technology Readiness Levels and preparing for future full-system demonstrations.
The project integrates multiple clusters to achieve these goals:
1. Automation Processes: Focuses on achieving automated to autonomous train operations, developing the related core technologies in connexion with other initiatives such as System Pillar and Flagship Project 5 and 6.
2. Optimized Headway: Aims to validate prototypes for the European Rail Traffic Management System (ERTMS) game changers in different operational environments, improving train control and braking performance in various operational environments, with mixed radio based ETCS levels with Hybrid Level 3, ETCS L3 moving block, absolute train position, train integrity and train length management, as well as optimized and reproducible braking performance under low adhesion conditions..
3. Enabling Digital Technologies: Develops specifications and validates prototypes related to connectivity (both for train-to-ground communication and onboard communications), modular IT platforms, and the Digital Register to provide the future-proof connectivity, IT and data platforms required for the automation of rail operations.
4. Fast and Efficient Deployment: Assesses technology for Digital Automatic Train Operation (DATO), aiming for quick deployment and developing guidelines for migration and certification, using innovative modelling techniques for automatic approval and certification.
5. Innovative Operational Solutions: Explores the added values of innovative concepts such as Autonomous Route Setting and Virtually Coupled Train Sets to enhance network capacity and autonomous operations.
6. Demonstrators: Validates the benefits of DATO technologies through demonstrations in controlled environments, focusing on achieving specific Technology Readiness Levels and preparing for future full-system demonstrations.
CL 1: Significant progress was made, with WP6 finalizing functional specifications for TE. This enabled architectural and modeling work using MBSE Arcadia-Capella. Updated X2Rail-4 results set a new baseline for the cluster, supported by strong coordination from the Technical Coordination Team.
CL 2: WP13 delivered three of five planned releases of the System Definition and Safety Analysis for Moving Block ETCS L3. WP14 advanced prototype development and testing. WP15 finalized all Hybrid L3 specifications and submitted deliverables. WP16 continued prototype and system updates. WP17 progressed with NG Brake demonstrator preparation. WP18 launched in December 2024 with initial activities. WP20 continued work on train integrity demonstrators. In ASTP, WP21 resolved issues and submitted updated deliverables. WP22 completed its design, consolidated solutions, and began lab testing. Deliverables D22.1 and D22.7 were submitted, with validated RAMS including ERJU feedback. Collaboration with EGNOS stayed strong.
CL 3: This cluster built upon S2R and prior results to define key foundations for FRMCS. Advanced specs were completed for the Onboard Communication Network, Modular Platform, and Data Repository. Strong collaboration was ensured with SP, other FPs, and demonstrators within FP2 R2DATO.
CL 4: WP29 delivered D29.3 and D29.4. Resource constraints delayed progress at the end of Period 2 but have since been resolved. WP30 achieved results in model translation, validation frameworks, and ontology for automated authorization. WP31 and WP32 delivered drafts and developed an initial interface matrix connecting technical indicators and value drivers, key for BuCa guidelines. WP33 launched in M24. WP34 completed all tasks, defining a testing strategy around ASTP and creating a digital twin validation procedure. WP35 began in March 2024, held regular meetings, and progressed on D35.3 with review planned for February 2025.
CL 5: WP48 progressed well across tasks. In Task 48.1 (Autonomous Route Setting), use cases were defined, and lab test planning completed. D48.1 is finalized for early 2025 submission. Task 48.2 (Virtually Coupled Train Sets) developed technical test specs, overcoming early delays from Capella model limits. D48.2 is ready for submission. Task 48.3 worked on use cases and control architectures for the Self-Driving Freight Wagon, collaborating with other FPs. Results are compiled in D48.3. Task 48.4 completed test planning for SRC and RP, aligned with demonstrations in Amersfoort.
CL 6: WP36 completed and tested the first user stories in a virtual environment, with phase 2 and lab setup underway. WP37 held workshops and analyzed ETCS HTD standardization and deployment challenges. WP38 integrated the New Generation Brakes into a demonstrator and secured authorization. WP39 advanced test specs for ATO on mainline bottlenecks, including the DATO-TMS interface, documented in D39.3. WP40 and WP41 demonstrated remote tram operations. WP42 continued developing autonomous driving use cases in Oslo. WP43 was cancelled due to locomotive unavailability, with tasks reassigned. WP44 and WP45 progressed in developing, testing, and ensuring safety for the Moving Block ETCS Level 3 demonstrator. WP46 completed use case analysis for GoA4, advanced component integration and interface.
CL 2: WP13 delivered three of five planned releases of the System Definition and Safety Analysis for Moving Block ETCS L3. WP14 advanced prototype development and testing. WP15 finalized all Hybrid L3 specifications and submitted deliverables. WP16 continued prototype and system updates. WP17 progressed with NG Brake demonstrator preparation. WP18 launched in December 2024 with initial activities. WP20 continued work on train integrity demonstrators. In ASTP, WP21 resolved issues and submitted updated deliverables. WP22 completed its design, consolidated solutions, and began lab testing. Deliverables D22.1 and D22.7 were submitted, with validated RAMS including ERJU feedback. Collaboration with EGNOS stayed strong.
CL 3: This cluster built upon S2R and prior results to define key foundations for FRMCS. Advanced specs were completed for the Onboard Communication Network, Modular Platform, and Data Repository. Strong collaboration was ensured with SP, other FPs, and demonstrators within FP2 R2DATO.
CL 4: WP29 delivered D29.3 and D29.4. Resource constraints delayed progress at the end of Period 2 but have since been resolved. WP30 achieved results in model translation, validation frameworks, and ontology for automated authorization. WP31 and WP32 delivered drafts and developed an initial interface matrix connecting technical indicators and value drivers, key for BuCa guidelines. WP33 launched in M24. WP34 completed all tasks, defining a testing strategy around ASTP and creating a digital twin validation procedure. WP35 began in March 2024, held regular meetings, and progressed on D35.3 with review planned for February 2025.
CL 5: WP48 progressed well across tasks. In Task 48.1 (Autonomous Route Setting), use cases were defined, and lab test planning completed. D48.1 is finalized for early 2025 submission. Task 48.2 (Virtually Coupled Train Sets) developed technical test specs, overcoming early delays from Capella model limits. D48.2 is ready for submission. Task 48.3 worked on use cases and control architectures for the Self-Driving Freight Wagon, collaborating with other FPs. Results are compiled in D48.3. Task 48.4 completed test planning for SRC and RP, aligned with demonstrations in Amersfoort.
CL 6: WP36 completed and tested the first user stories in a virtual environment, with phase 2 and lab setup underway. WP37 held workshops and analyzed ETCS HTD standardization and deployment challenges. WP38 integrated the New Generation Brakes into a demonstrator and secured authorization. WP39 advanced test specs for ATO on mainline bottlenecks, including the DATO-TMS interface, documented in D39.3. WP40 and WP41 demonstrated remote tram operations. WP42 continued developing autonomous driving use cases in Oslo. WP43 was cancelled due to locomotive unavailability, with tasks reassigned. WP44 and WP45 progressed in developing, testing, and ensuring safety for the Moving Block ETCS Level 3 demonstrator. WP46 completed use case analysis for GoA4, advanced component integration and interface.
CL1: Generally speaking, in RP2 a step forward beyond the state of the art could be made. Having the results of Shift2Rail (namely from X2Rail-4 and TAURO), the generated use cases in WP5 and their latter prioritisation in (WP6 & MS3), it was possible to progress towards ATO GoA3/4 by providing a set of requirements for the cluster’s technical enablers and for the said use cases, to be later validated in the laboratory and demonstrated in the field.
CL2: During this reporting period the first specification was provided for a system that combines a Radio Block Center (RBC) and Interlocking, built on geometric safety logic, with minimal pre-configuration, and leveraging a small safety core.
CL3: A first proposal for Subset 147 of the next TSI CCS was provided. The definition of scope of the study on modular certification and acceptance was started. Steady progress has been made in aligning of R3/4 requirements for Digital Register -Moving Block Demonstrator Interface. For the Connectivity Development, the main reached results are the design of four prototypes based on the common architecture defined in FP6WP4.3.
CL4: Key outcomes include testing strategies, formal modeling processes, a lab demonstrator for exploration of architecture patterns & DevOps building blocks, and an updated value-based framework to support stakeholder decision-making..
CL5:The technical and operational requirements for the autonomous Route Setting (anRS) and Self-driving Freight (SDFW) have been further developed in Order to prepare Lab Tests. The Virtual coupling has been further specified and the Technical requirements for Short Range Communication and relative positioning have been derived.
CL6: During RP2, major progress was achieved in preparing several demonstrators, including the successful execution of the urban autonomous tram demonstrator in Oslo up to TRL7 including development of automatic System.
CL2: During this reporting period the first specification was provided for a system that combines a Radio Block Center (RBC) and Interlocking, built on geometric safety logic, with minimal pre-configuration, and leveraging a small safety core.
CL3: A first proposal for Subset 147 of the next TSI CCS was provided. The definition of scope of the study on modular certification and acceptance was started. Steady progress has been made in aligning of R3/4 requirements for Digital Register -Moving Block Demonstrator Interface. For the Connectivity Development, the main reached results are the design of four prototypes based on the common architecture defined in FP6WP4.3.
CL4: Key outcomes include testing strategies, formal modeling processes, a lab demonstrator for exploration of architecture patterns & DevOps building blocks, and an updated value-based framework to support stakeholder decision-making..
CL5:The technical and operational requirements for the autonomous Route Setting (anRS) and Self-driving Freight (SDFW) have been further developed in Order to prepare Lab Tests. The Virtual coupling has been further specified and the Technical requirements for Short Range Communication and relative positioning have been derived.
CL6: During RP2, major progress was achieved in preparing several demonstrators, including the successful execution of the urban autonomous tram demonstrator in Oslo up to TRL7 including development of automatic System.