Difference between revisions of "WDI Enhancement for Last Mile"

From RFF Wiki
Jump to: navigation, search
(Use Case)
Line 25: Line 25:
 
** Train composition, providing Hermes 30 as train composition message to the train operating railway undertaking which is taking over the train  
 
** Train composition, providing Hermes 30 as train composition message to the train operating railway undertaking which is taking over the train  
  
 +
The first mile partner should mainly check the information which is provided by the smart service. Only in exceptional cases, he might capture a minimal dataset for a wagon which is not current available.
  
 
=== Last mile ===
 
=== Last mile ===
Line 36: Line 37:
 
** Send and receive Hermes 30
 
** Send and receive Hermes 30
 
** Retrieve wagon status via ISR
 
** Retrieve wagon status via ISR
 +
 +
The last mile partner should mainly check the information which is provided by the smart service. Only in exceptional cases, he might capture a minimal dataset for a wagon which is not current available.
  
  
Line 46: Line 49:
  
 
== Preconditions ==
 
== Preconditions ==
 +
The contractual must provide Electronic Consignment Note information to RailData (based on ECN 1.5).
 +
  
 
=== Basic Services ===
 
=== Basic Services ===
 
+
The smart service needs access to the GCU message broker in order to retrieve current technical wagon information.
  
 
== Dependencies ==
 
== Dependencies ==
  
 
== Planned Steps ==
 
== Planned Steps ==
 +
To be realised in 2021
  
 
== Evaluation ==
 
== Evaluation ==

Revision as of 16:31, 22 March 2021

Under construction - last edit: 2021-03-22 Oliver Kundt

Description

Scenario.jpg

Today's communication between railway undertakings and their service partners for the first and last mile is mainly paper-based: Wagon lists and train pre-advices are exchanged by hand, fax or email. The smart service "WDI Enhancement" aims to achieve the following:

  • The railway undertaking which is operating a train should provide relevant information (concerning consignment, wagons and trains) to his partners which are managing the first and last mile. In return, the partner should be able to provide information concerning wagon and train status in a high quality and via standardised messages and interfaces
  • The first and last mile processes should be supported by appropriate user interfaces (web interface, mobile interface)
  • The service partner should be able to export documents and information via appropriate functions and service AP


Use Case

First mile

FirstMile.jpg

  • First mile partner
    • Create task for picking up wagons
    • Pick up of wagons, wagon status message "Pulled" to ISR
    • Train composition, providing Hermes 30 as train composition message to the train operating railway undertaking which is taking over the train

The first mile partner should mainly check the information which is provided by the smart service. Only in exceptional cases, he might capture a minimal dataset for a wagon which is not current available.

Last mile

LastMile.jpg

  • Last mile partner
    • Create task for delivery wagons
    • Delivery of wagons, wagon status messages "Delivered" to ISR
    • Train decomposition, receiving Hermes 30 as train pre-advice message from the train operating railway undertaking wagons
  • Train operating railway undertaking
    • Send and receive Hermes 30
    • Retrieve wagon status via ISR

The last mile partner should mainly check the information which is provided by the smart service. Only in exceptional cases, he might capture a minimal dataset for a wagon which is not current available.


Transit of a train

Transit.jpg

  • Service partner who is managing a train transit
    • Receive train pre-advice from previous train operating railway undertaking
    • Use the information for managing the transit
    • Send train pre-advices to the next train operating railway undertaking

Preconditions

The contractual must provide Electronic Consignment Note information to RailData (based on ECN 1.5).


Basic Services

The smart service needs access to the GCU message broker in order to retrieve current technical wagon information.

Dependencies

Planned Steps

To be realised in 2021

Evaluation