Difference between revisions of "Train Harmonization Service"
(→Evaluation) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| 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 == | ||
| + | *TAF TSI Train ID | ||
| + | *RNE TTR program | ||
== Planned Steps == | == Planned Steps == | ||
== Evaluation == | == Evaluation == | ||
| + | * Frak Kschonsak on 25 June | ||
| + | Remark: The service is about “planning”, probably “service” should be replaced by “planning”. | ||
| + | Essential for planning are the deadlines to accept/not accept changes for the coming period (a week)? This time-periods and deadlines should be defined first to have a common understanding of “planning”. Short term, long term? Changes/adaptions? | ||
| + | * Answer from Core team | ||
| + | Right, the name should rather be Train Service Harmonization, changed. | ||
| + | The time period for the Service planning spans from the early planning before the yearly time table planning to the last planned changes before starting the day of operation. | ||
Latest revision as of 10:49, 6 July 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.
Use Case
Create train service planning
Update train service planning
Retrieve train service planning
Preconditions
Basic Services
Dependencies
- TAF TSI Train ID
- RNE TTR program
Planned Steps
Evaluation
- Frak Kschonsak on 25 June
Remark: The service is about “planning”, probably “service” should be replaced by “planning”. Essential for planning are the deadlines to accept/not accept changes for the coming period (a week)? This time-periods and deadlines should be defined first to have a common understanding of “planning”. Short term, long term? Changes/adaptions?
- Answer from Core team
Right, the name should rather be Train Service Harmonization, changed. The time period for the Service planning spans from the early planning before the yearly time table planning to the last planned changes before starting the day of operation.
