Difference between revisions of "Train Harmonization Service"
From RFF Wiki
(Created page with " == Description == Design and harmonize the train services among the partner RUs, update with operational actions == Use Case == == Preconditions == === Basic Services ===...") |
|||
| Line 1: | Line 1: | ||
== Description == | == Description == | ||
| + | Tags: Design and harmonize the train services among the partner RUs, update with operational actions | ||
| − | + | 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). | |
== Use Case == | == Use Case == | ||
| + | === Update train service planning === | ||
| + | === Retrieve train service planning === | ||
== Preconditions == | == Preconditions == | ||
Revision as of 09:37, 17 March 2021
Contents
Description
Tags: Design and harmonize the train services among the partner RUs, update with operational actions
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).
