Difference between revisions of "Observe Train Run"
From RFF Wiki
| (One intermediate revision by one other user not shown) | |||
| Line 13: | Line 13: | ||
== Preconditions == | == Preconditions == | ||
| − | + | == Basic Services == | |
| + | RNE TIS | ||
== Dependencies == | == Dependencies == | ||
| Line 20: | Line 21: | ||
== Evaluation == | == Evaluation == | ||
| + | * Frank Kschonsak on 25 June | ||
| + | This was the plan for small RU without huge IT backend systems. | ||
Latest revision as of 13:43, 6 July 2021
Contents
Summary
No/little integration of small RUs in the train processing. Information on first and last mile mostly handed over manually.
Small RUs, Terminals, Ports and operative staff use a mobile app and web portal to pull and push Train Run Information. Border crossings and handover of trains - document check, customs - are conducted digitally based on train file and support a seamless train run through Europe.
Description
Observe the train run and provide notifications, if a measurement point is overdue. In case of overdue measurement point, use GPS location to know the train location
Use Case
Preconditions
Basic Services
RNE TIS
Dependencies
Planned Steps
Evaluation
- Frank Kschonsak on 25 June
This was the plan for small RU without huge IT backend systems.
