Difference between revisions of "DS 08 UC 05"
From RFF Wiki
| Line 6: | Line 6: | ||
= Workflow = | = Workflow = | ||
# Set notification: A RU subscribes to a information service based on (for the POC) Train HandOver. He sets | # Set notification: A RU subscribes to a information service based on (for the POC) Train HandOver. He sets | ||
| − | + | ## the necessary triggers, | |
| − | + | ## the suitable notification schema and | |
| − | + | ## the appropriate delivery channel. | |
# Collect RU: The logic calculates based on the provided data | # Collect RU: The logic calculates based on the provided data | ||
the next RU partners along the train run. | the next RU partners along the train run. | ||
Revision as of 16:32, 14 September 2021
UC05 Inform involved partner about status
Input
- hand over information, provided by RailData
Workflow
- Set notification: A RU subscribes to a information service based on (for the POC) Train HandOver. He sets
- the necessary triggers,
- the suitable notification schema and
- the appropriate delivery channel.
- Collect RU: The logic calculates based on the provided data
the next RU partners along the train run.
- Notify RU: The logic scans the provided notification patterns and initiates the RU user information based on the fired trigger.
Output
- Message channels like
- mobile push notifications
- social media channels
Dependencies
- Input HandOver information from RailData (or RU's)
- the use case is an additional service in the digital theme of Digital Train Handover from which the MARS POC realizes several other use cases.
