Rail JU logo in white
European Union flag

A body of the
European Union

FP1 – MOTIONAL - Project Outputs

D11.1 Specification of selected Processes and Communication between applications

Mar 17, 2026

Output type:

This report constitutes the deliverable D11.1 Specification of selected Processes and Communication between applications of the work package WP 11 Development – Integration of TMS and processes including cross-border traffic management. It is based on input from the activities performed in the tasks of WP 11 providing the specification of Use Cases, requirements and interfaces to support and improve the traffic management process facilitated by Traffic Management Systems (TMS) used by the Railway Infrastructure Managers (IM) in Europe. The specifications are used for development and set-up of the demonstrations 12.1 to 12.9 of Workstream 1.2. In this context, it will serve as an input document required for the activities performed in the future WP 12 of the MOTIONAL project and the future activities in the next EU-Rail calls to strive for higher TRL and large-scale demonstrations regarding the Technical Enablers:

  • TE 8 Real-time connection of rail networks as managed by TMS and involved actors;
  • TE 9 Modelling and decision support for cross-border traffic management; and
  • TE 10 Integration of TMS with a) yard management system and processes; b) station management system and processes; c) energy management (Electric Traction System); d) real-time crew / rolling stock dispatching.

Within the context of the WP 11, each partner contributed to the writing of deliverable D10.1 by describing a set of high-level Use Cases and high-level requirements for integration of planning systems with other systems including planning systems of neighbouring rail networks. The D10.1 has been used as the starting point for further analysis, and the resulting Use Case description work in WP 11 is documented in this D11.1. Interaction meetings and exchange of material with the System Pillar Task 3 and RNE experts as well as with the Flagship Projects of Destinations 3, 5 and 6 helped to achieve the required alignment level. As a result, one or more Use Cases referring to each high-level Use Case of D3.1 were specified based on further analysis. Similarly functional and non-functional requirements were identified and specified which were mapped against the high-level requirements associated with the Technical Enablers 8, 9 and 10. Hence, this document represents a detailed study in addition to D2.3 and D10.1 including the basis for the development of the WS 1.2 demonstrations:

  • Demo 12.1 (ATSA) – Interfaces TRL 5 from the communication Platform to the Timetable Management Applications and to the Traffic Control (RBC, Interlocking).
  • Demo 12.2 (PKP) – Integration solution for the data exchange and storage system (Data Lake) allowing the exchange through interfaces, data quality assessment, and metadata generation. This solution will be used for integrating disparate decision support systems.
  • Demo 12.3 (STS) – Interface from TMS Planning system to ATO-TS control module to maximise the energy efficiency of the train operation in a short-term action.
  • Demo 12.4 (INDRA) – Interfaces from the communication Platform to wayside C-DAS operation system, focusing on speed profiles functionalities.
  • Demo 12.5 (MERMEC) – Demonstrator based on the interfaces coming from subtask 11.3.5 (implementing interfaces between neighbouring TMS and IM) to provide a TMS and IM real-time connection of rail networks focused on cross border traffic management.
  • Demo 12.6 (HACON) – TRL 6 interfaces and TRL 5 decision support module for integration and traffic management of two neighbouring TMS and IM including cross-border operations (supporting Destination 5 activities).
  • Demo 12.7 (HACON) – Interfaces for integration of TMS with other services such as station and yard management systems (supporting Destination 5 activities), digital maintenance systems supporting Destination 3 activities), Passenger Information Services (supporting Destination 6) as well as electric traction systems and crew/ rolling stock management systems.
  • Demo 12.8 (TRV) – Interface of TMS to Yard Coordination System 2.0 in Malmö node. Work connects to WP 4.
  • Demo 12.9 (CEIT) – Interface in view of the future autonomous inspection vehicle for the infrastructure (Destination 3) and its integration with the Intelligent Asset Management System (IAMS). To receive information about asset status and planned interventions and deliver allocated paths to execute inspections and interventions.

Europe's Rail