Difference between revisions of "Train Harmonization Service"
| Line 10: | Line 10: | ||
== Use Case == | == Use Case == | ||
| + | === Create train service planning === | ||
=== Update train service planning === | === Update train service planning === | ||
=== Retrieve train service planning === | === Retrieve train service planning === | ||
| Line 15: | Line 16: | ||
== Preconditions == | == Preconditions == | ||
| − | + | == Basic Services == | |
== Dependencies == | == Dependencies == | ||
Revision as of 10:57, 20 May 2021
Contents
Description
Tags: Design and harmonize the train services among the partner RUs, update with operational actions
No/little digital support for all RUs in the train service planning. Information exchange is mostly handed bilaterally and manually.
The RUs need to harmonize a cooperative train service among each other. Today this happens individually between the different partners. In future with automated path ordering and slot allocation (e.g. TTR) at the IM side and automated ressource planning and optimization systems on the RU side the need increases for a harmonized train planning. Each partner should be able to retrieve the last planning state of a train service and should upload any update on his leg of the train journey. This should include the connecting services too (loading, shunting, unloading).
All RUs use a cooperation service to setup, manage, update and reference the train service planning. This can happen by system interface, web portal to exchange Train Service Information. This process starts with the initial (yearly) train service planning and continues until the operational phase.
