Difference between revisions of "DS 08 UC 05"
From RFF Wiki
| Line 18: | Line 18: | ||
** mobile push notifications | ** mobile push notifications | ||
** social media channels | ** social media channels | ||
| + | |||
| + | = Objects = | ||
| + | * Subscription | ||
| + | * TrainHandOverAdvice | ||
| + | * NotificationProtocol | ||
= Dependencies = | = Dependencies = | ||
* Input HandOver information from RailData (or RU's) | * 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. | * 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. | ||
Latest revision as of 21:46, 15 September 2021
Contents
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
Objects
- Subscription
- TrainHandOverAdvice
- NotificationProtocol
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.
