TE06 Enabler 6


Perception (TRL5/6) – Detailed design, development, and validation of the Perception system defined in the Perception Architecture and System Specification, including signal reading and obstacle detection, supporting cooperative awareness, supported by virtual certification.

Project: - FP2 - R2DATO (01/12/2022 - 31/05/2026)

logo

Work Packages

Currently available work packages:

WP05 Automation Processes Use Cases and User Requirements

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. 

WP06 Automation Processes Specifications

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. 

WP08 Safety Analysis & Risk Assessment

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.

WP11 Prototype development of perception system

This Work Package will focus on the detailed design, development, and validation of the Perception system (TE-06) defined in the Perception Architecture and System Specification up to TRL4/5. The scope shall also include the interfaces between the Perception System and its dependent technical enablers. At the validation side of the V-model, the interface testing will require coordination with the various technical enablers. 

WP38 Automatic Stabling, Shunting, and Non-commercial runs Demonstrator

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.

WP39 ATO over ERTMS demonstration on mainline

Mainline, is here defined as the most complex kind of operations in a network, mostly around large nodes that can't be demonstrated in full service by 2026. Therefore, modelling  ATO and its operational concept as well the linkage of TMS to ATO dynamically anticipating in these complex nodes will  be developed, tested and designed.   Furthermore, showing the relevant advantages deriving from the synergy between the digital automatic train operation up to GoA 4 and the CCS evolution, increasing the capacity and punctuality of railway lines, by enabling ETCS L3 moving block with minimum infrastructure elements.

WP42 Tramway autonomous movements in depot demonstrator

Identify use cases to be implemented in the second demonstrator, development, implementation, and validation through a specific demonstrator in Oslo. The objective of this third work package is to implement an AUTONOMOUS MOVEMENTS demonstrator up to TRL6.

WP43 Freight Demonstrator

To allow a smooth deployment of GoA 4 technology with different possible technological solutions, the systems need to be tested in real conditions in a demonstrator. The freight demonstrator will be equipped with sub-systems studied in the Technical Enablers. Tests will be performed, enhancing autonomous freight train operations.

WP46 Regional line demonstrations

The main objective of this WP is to provide the bridge between FP2-R2DATO and FA6 demonstrations by supporting validation and testing of technical enablers in regional line environment before they are handed over to FA6 for further adaptation and integration. The improved CCS and automation functions will be the main technologies tested and validated, building on the activities already performed in the scope of Shift2Rail ATO (up to GoA4) tests (the very same line and vehicle). Further, the line will be used to support development process of technical enablers, even on lower TRL levels, due to simplified operational environment and flexible demonstrations planning (no regular commercial service, the line fully dedicated to tests) and approval process. Minimal set of technical enablers needed: 

  1. Automating functions 
  2. ATO 
  3. Perception systems 
  4. Digital register
  5. Absolute safe-train positioning

Public Deliverables

Currently available deliverables:

D11.3 PoC of Perception Systems
D38.1 Training guidelines, operational guidelines and instructions, training material
D38.2 Results of GoA1 remote controlled stabling and bringing a train to the station
D38.3 Results of remotely monitored stabling and bringing a train to the station with remote monitoring
D38.4 Results of automatically stabling a train and bringing a train to the station in GoA4
D38.6 Results of automatic coupling and uncoupling
D38.7 Results of remotely controlled shunting (in cooperation with FA5)
D38.8 Use of an ATO-specific TMS in stabling and shunting operation, and in non-commercial runs
D38.9 Analyses of all data collected during the tests, including expected benefits and contributions to KPIs
D39.1 Test specification for DATO and TMS interface fit-for-use in mainline operations
D39.2 Best practices report from mainline capacity assessment, including testing Operational Concept (OC) for mainline operations
D39.3 Demo specifications
D39.4 Report of DATO test results
D39.5 Report of L3 Moving Block test results
D39.6 Report of DATO over ERTMS L3 test results
D42.1 Collection of test cases and validation criteria (WP42)
D42.2 Autonomous movements of trams in depot
D42.3 Testing reports & assessment (WP42)
D43.1 Testing plan
D43.7 Preparatory studies for FRMCS integration
D46.1 Testing scenarios and Regional line demonstrations planning
D5.1 Documentation of use cases for automating functions
D5.1 Documentation of use cases for automating functions - 20/06/2024
This deliverable will contain a report about actual existing and specified automated functions, tasks or related use cases with annotated target component as scope, a draft release for set of documents including analysis based on first input from SP and related Fas (e. regarding demonstrators) and definition for relevant use cases, operational parameters and scenarios in scope of passenger/freight and tramway applications.
D5.2 Documentation of use cases for perception system
D5.3 ATO GoA3/4 Specifications review documentation
D5.3 ATO GoA3/4 Specifications review documentation - 20/06/2024
This deliverable will contain a review of existing specifications and previous projects outcome. Analysis of gaps (e.g. for freight) and inputs from the System Pillar will be part of the deliverable too.
D5.4 Documentation of Use Cases for remote driving
D5.4 Documentation of Use Cases for remote driving - 20/06/2024
This deliverable will contain a set of documents including analysis based on first input from SP and related Fas (e.g., regarding demonstrators) and definition for relevant use cases, operational parameters and scenarios in scope of passenger/freight/inspection vehicles and tramway applications.
D5.5 Documentation of Freight specific user requirements for automation process
D5.6 Documentation of urban user cases and operational rules for automation process
D5.6 Documentation of urban user cases and operational rules for automation process - 21/06/2024
This deliverable will contain a set of documents defining harmonized urban use cases and operational rules for all automation process subproject TE.
D6.1 Report on sets of non-functional and functional requirements (SRS) for automating functions
D6.2 Report on System Architecture Specification and Interface Specification (FFFIS) for automating functions
D6.4 Proposal for Certification Process for Perception Systems
D6.5 ATO GoA3-4 Specifications and modelling
D6.6 Documentation of Use cases, requirements & Specification autonomous operations for tramways
D6.7 Report on set of non-functional and functional requirements (SRS) for remote driving
D6.8 System Architecture Specification and Interface Specification (FFFIS) for remote driving
D8.1 Safety analysis for automating functions
D8.3 Safety analysis for ATO functions
D8.4 Safety analysis for remote driving
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.