DELIVERABLES PUBLISHED BY THE PROJECT

D3.1 Mapping against scope_ specification of technical enablers_ high-level use cases_ high-level requirements_ high level design for demonstrators in WPs 4-9

This document constitutes the Deliverable D3.1 “Mapping against scope, specification of technical enablers, high-level use cases, high-level requirements, high-level design for demonstrators in WPs 4-9” in the framework of the Flagship Project FP1-MOTIONAL.

The objective of this deliverable is to align, prepare and deliver the high-level specifications of requirements, high-level design, and high-level use cases for the development of the technical enablers 1 to 7. The high-level specification is done in parallel with more detailed specifications from WP4, WP6 and WP8. Participants from all WPs contributed to the texts.

In the project proposal, seven technical enablers were linked to Workstream 1.1 (Planning work packages), i.e., WP4/WP5 (Integration of Planning Systems and Processes), WP6/WP7 (Decision Support and Optimization) and WP8/WP9 (Simulation and Operational feedback). Here, each of the technical enablers are described in detail, including alignment with previous results, current state of practice, assigned development needs and high-level requirements.

An extensive mapping is also a result that is presented in this deliverable. All demonstrators (that further on will be called demonstrations) in Workstream 1.1 are introduced and described, together with related use cases. There are 13 demonstrations and they are all mapped against technical enablers, TRL levels, use cases and the high-level requirements defined for each technical enabler. They are also mapped against simulation environments and frameworks to be used within WP4/WP5, WP6/WP7 and WP8/WP9. Finally, the alignment and interactions between WP4-WP9 demonstrations and other FA1 WPs, other Flagship Projects and SP Task 3 CMS/TMS and RNE are mapped.

Download

D31.1 Federated data space “Sandbox Environment” description

As stated in its Master Plan, the Europe’s Rail Joint Undertaking (ERJU) public-private partnership “aims to accelerate research and development in innovative technologies and operational solutions supporting the fulfilment of European Union policies and objectives relevant for the railway sector and supporting the competitiveness of the rail sector and the European rail supply industry”; [it] “will foster a close cooperation and ensure coordination with related European, national and international research, innovation deployment and investment activities in the rail sector and beyond, in particular under Horizon Europe, Connecting Europe Facility, and the Digital Europe Programme".

The creation of a Rail Data Space (RDS) as one of the implementation deliverables of the ERJU is a concrete instance of cooperation and coordination with the Digital Europe Program: its ultimate goal is to align data sharing and communication in the Rail Sector to the European Data Strategy, making the Rail Sector both a contributor and a beneficiary of the “single market for data” for a “data-driven” European society:

Leveraging the resources and know-how provided by the Dataspace Support Center, funded by the Digital Europe Programme,
Ensuring at inception and by design compliance with the European legislative acts that complement the establishment of European data spaces (Data Actions)
Ensuring at inception and by design the ability to deploy the Rail Data Space on Next Generation Cloud infrastructure (Cloud Actions)

Download

D15.1 Requirements for the deployment of TMS linked with ATO/C-DAS

This document constitutes the Deliverable D15.1 “Requirements for the deployment of TMS linkedwith ATO/C-DAS” in the framework of Flagship Project FP1 – MOTIONAL as described in the EURAIL MAWP. This deliverable is from Work Package (WP) 15 “Linking TMS to ATO/C-DAS foroptimised operations” and is based on the outcome of task T15.2 and initial results of task T15.3.It is setting up requirements for innovations in TMS – ATO/C-DAS including relevant backgroundinformation.

The focus of WP15 is to study and enhance the link between TMS and ATO/C-DAS in order to, e.g.,enhance operations, improve feedback loops, and increase standardization. This report lays outthe ground for the continued work in WP15/16 of FP1 Motional in EU-RAIL. The objective of thereport is to present the current situation both as “state-of-the-art" and “state-of-practice",describe the needed development and innovations that will be target of future work in WP15/16,and to capture the requirements that are important to consider in the development work.

The “state-of-the-art" study shows that there are important concepts and standards that areevolving in the area, like SFERA, ERTMS\ATO “subsets”, and the RCA. There is importantknowledge to build upon regarding, e.g., energy optimisation, train trajectory optimisation,communication, and data models. The “state-of-practice" overview shows that several countrieshave made important implementations (both trial and “real”) of C-DAS with important conclusionsvalid for both C-DAS and ATO operations. There are fewer implementations and tests regardingATO, but also in that area important experience is made to further build upon.

For the system architecture in the area, design and analysis principles are proposed, both to getharmonization and also to help a common understanding. Communication platforms provideimportant bases, like the Integration Layer and the standardized data format of the ConceptualData Model (CDM). But further developments are necessary to adapt them for the relevant area.

The continued work of WP15/16 will be very much based on the partners’ previous experience inthe area and on the evolving standards. This certifies both that the work will be relevant, reusable,and move the state-of-the-art forward. The planned work has broad base for importantimprovements and includes, e.g., improved RTTP and TPE construction for better ATO/C-DASefficiency, architectural and communication developments for standardization, and betteradaptation to human factor aspects of TMS - ATO/C-DAS systems.

The development work will both consider and contribute to the standards in the area and willadhere to important concepts setting up requirements on the development, such as SFERA,relevant ERTMA\ATO "subsets”, RCA, and concepts under development, such as the IntegrationLayer and Conceptual Data Model, as well as other types of requirements such as human factors,correctness of information, and response times.

Download

D27.1 Data model and format for a harmonised EU planning of railway assests, starting from CCS+

The present document examines how a harmonized set of data can be used to realize the idea of SERA and a Single European Railway Traffic Management system. This vision is based on the concept that a common data model can be used in the supply chain, regardless of the specific domain. The System Pillar CCS-TMS Data Model is a first instance of a common model fully dedicated to CCS-TMS engineering and operations. The potential utilization of such data in other domains besides signalling, such as diagnostics, maintenance, and so forth, is analysed through the presentation of a set of business cases. The business cases allow us to identify key data requirements for the WP27 digital planning toolbox and other applications. The content of this deliverable (D27.1) will be used as input for the task 27.2 to guide the extraction of selected objects from the data sources identified. The extracted objects can be used by both the toolbox and other railway applications as a result of FP1 and other FP interactions and collaborations.

Download

D26.1 Use Case Collection Process

The usage of latest digital technologies (e.g. federated data spaces, CDM, digital twins, etc.) are key enablers to drive the railway industry forward and are mainly responsible for almost any optimization within the last years. That is why Motional-TT (Work Packages 26-32) is focused on the investigation of new technologies as well as the adoption of existing ones that are available on the market to enable these for the railway community; so called: “technical enablers”.

Since, this approach would remain ineffective until these technical enablers are not used in combination with a use case, WP26 is obliged to technically enable as many use cases as possible, that evolve from the other flagship projects. However, only those use cases shall be cooperated with, where’s use case owner are requesting for that sort of support. The usage of WP26 technical enablers is not mandatory to any use case owner.

Main goal of this first task within WP26 (26.1) was to come to a common understanding of how the required use cases that evolve from the other flagship projects shall be identified and interacted with. This interaction shall include the identification of use cases as mentioned above, that envisage the usage of at least one technical enabler technology developed in Motional-FP1-TT. Furthermore it shall set relevant stakeholders (namely use case owners and owners of technical enablers) into contact with each other to join forces within an iterative process, where the use cases and the technical enablers are combined step by step to research on its synergies and effectiveness (Task 26.2). Finally, the outcome of this investigation shall be to come to a consensus of how the set of use cases shall be collected and documented (Task 26.3).

For this purpose, the WP26 working group developed a process within task 26.1 on basis of the “swim lane” methodology that maps all stakeholders and their respective tasks within the use case collection process execution. The process description covers the identification of relevant use cases, the collection of them and - if applicable – their adoption by the System Pillar towards standardization.

This process as well as the common understanding are considered the main outcome of this task and are described in this document.

Download

D2.2 Workplan for collaboration with other EU-RAIL Destinations

The purpose of this document is to present a Workplan for collaboration with other EU-RAIL Destinations for Flagship Project 1: MOTIONAL. The Workplan outlines the objectives, guidelines, collaboration activities, deliverables, outcomes and risk management strategies for the collaboration between Flagship Project 1 and the other participating EU-RAIL Destinations. The objectives of collaboration include improving knowledge sharing, enhancing collaboration and coordination, and increasing efficiency and effectiveness of technical enablers developed by the Flagship projects. The guidelines for collaboration address communication and coordination mechanisms, roles and responsibilities, data sharing and confidentiality, intellectual property rights, and timelines and milestones. The activities include identifying potential collaboration, joint planning and implementation of pilots, and documentation exchange. Overall, this Workplan aims to establish a successful and productive collaboration between Flagship Project 1 and the other EU-RAIL Destinations, with the aim to provide better results in all involved projects.

Download

D17.1 Requirements Specification for Automated Decisions and Decision Support for Traffic Management optimisation

This report is the deliverable of Task 17.1 “Requirements Specification for Automated Decisions and Decision Support for Traffic Management Optimization” of the Flagship Project 1 – “Network management planning and control & Mobility Management in a multimodal environment and digital enablers” of the EU-MAWP. The aim of this work package is to specify European standardized requirements for a system to provide automated decisions and decision support for traffic management optimization.

The main results contained in this document are specified functional, non-functional, and operational requirements that have been agreed upon between all partners involved in the work package. These requirements were developed with a view towards both technical enablers associated with Work Package 17: Technical Enabler 16 “Automation of very short-term train control decisions” as well as Technical Enabler 17 “Real-time conflict detection and resolution for main line and optimization”. The implementation of these technical enablers represents a stepping-stone towards the development of an overall general level system. The requirements delivered here were developed with a focus on the demonstrators developed in Work Package 18. The whole product requirements have only been mentioned and defined where they are needed to understand the setting and scope of the demonstrators’ requirements. The requirements specification for the final product will be developed within the next ERJU calls. The European standardization of the requirements delivered here supports the System Pillar in achieving the interoperability of the European railway networks by 2031. In the last chapter of this report, we provide benchmarking criterion for the development of a testbed for the standardized testing and comparison of methods developed in later stages of the work package.

The requirements delivered in this report are further classified into the following classes and sub-classes:

Functional requirements: System Interaction with User Groups, System Scope, System Forecast and Conflict Detection, System Solutions, System Integration, and User Interaction.
Non-functional requirements: System, Scalability, Performance, and Regulations and Security.
Operational requirements: Compliance and Automation.

These requirements were obtained systematically through the collaboration of three groups of industrial and infrastructure partners: an Author Group, an Expert Group, and a Review Group. The delivered requirements are the result of an iterative querying of the Expert Group by the Author Group using specially designed requirements questionnaires. Subsequent phases of the deliverable were quality controlled by the Review Group – consisting of EU-wide and cross-industry representatives.

Overall, more than 80 requirements have been developed. A special focus has been put on the system scope, the integration into the existing IT-infrastructure and processes, conflict detection, and conflict resolution and mitigation. To reflect the differences in the technical enablers, requirements for Technical Enabler 16 and Technical Enabler 17 were developed separately.

The results of this document are the basis for the later stages of Work Package 17, in which methods for automated decisions and decision support for traffic management optimization are developed on a demonstrator level. Furthermore, these results feed into the subsequent Work Package 18, in which systems with a higher maturity level incorporating Technical Enabler 16 and Technical Enabler 17 are to be developed. There is also a symbiotic interaction between Work Package 17 and Work Package 10: In Work Package 10 high-level requirements and specifications for both technical enablers were developed, which were taken as input here. In turn, the standardized requirements contained in this report will be taken as inputs into Task 10.2 of Work Package 10, in which specifications for high-level Use Cases and demonstrators of Work Packages 11-17 will be developed. The developments of Work Package 17 are also interacting for Work Package 2, which is responsible for technical coordination.

Download