On 2–3 December, the Europe's Rail General Assembly 2025 took place, providing a valuable occasion to look back at the...
Currently available work packages:
The goal of this work package is to identify already specified functions, use cases, user requirements or operational scenarios that must be considered in the rail automation processes (e.g., from S2R). Especially, items should be linked with components (e.g., ATO, ATP, TCMS, APM) and operational scenarios (e.g., Urban, Passenger, Freight). Based on input from the System Pillar, the definition of use cases, user requirements and operational parameters and scenarios must be consolidated, analysed, and extended. The purpose of the WP is to capture the current rail operator behaviour, high level user requirements and use those to design the automation system.
WP6 will focus on the specification generation for the four technical enablers involved in Automation Processes. It involves taking the deliverables of the WP5 and performing a thorough Safety & Hazard Analysis to ensure all considerations are made in WP7 for a safe operation in ATO mode. Based on the analysis, this WP will define and develop an architecture and a system specification for the technical enablers. This work package addresses the evolution of DATO in railway and tramway sectors from a rolling stock perspective; by using outcomes from WP5 ensuring the harmonisation with other FP(s) and System Pillar.
The objective of WP8 is to centrally cover aspects of safety in the Automation Processes subproject. This activity requires close cooperation with System Pillar and the System Coherence (WP3). It covers the five Technical Enablers (Automating functions, ATO technologies, Perception & Data Factory and Remote Driving, and the activities carried out in previous Shift2Rail projects, such as X2Rail series of projects and TAURO will be considered as a relevant baseline.
In this task, functional prototypes for remote control will be developed, tested, and validated against the defined system architecture specification. There should be at least one prototype in relation to the proposed demonstrators and the relevant scopes and in cooperation with other FAs (e.g., FA5 for Freight and Depot/Yard, FA6 Regional lines), to have an interim step towards demonstration of the technology.
The objectives of the demonstrator are testing the performance of the technical enabler(s) incorporated in the demonstrator, providing feedback to the TE-developer, in order to improve the functioning of the TE, or to enhance/improve/modify the specifications and performing measurements to show the improvement of the new (sub)system over the existing system, to contribute to the realisation of the KPIs defined in the call.
Identification of use cases for the first demonstrator, development, implementation, and validation through a specific demonstrator in Oslo. The objective of this second work package is to implement a REMOTE DRIVING AND TELECOMMAND demonstrator up to TRL7.
Currently available deliverables:
All deliverables, results and publications herewith provided reflects only the author's view and the EURAIL is not responsible for any use that may be made of the information it contains.