Difference between revisions of "Intermodal Connectivity Package"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Description == | == Description == | ||
| + | To simplify the communication between external Operators a standardized data exchange needs to be defined and implemented. The Operator can use a software package to integrate railway legs in their own transport chains. This connectivity package enables the Operator to communicate with the railway service partners | ||
| + | * along a standardized process | ||
| + | * with standardized messages and data formats | ||
| + | * over a defined and stable interface | ||
| + | * in a transparent mode. | ||
| + | |||
| + | an offering to third parties to connect to our ecosystems for data exchange, platform services or marketplace participation in regards with intermodal transports. | ||
| − | |||
== Use Case == | == Use Case == | ||
| + | === Operator plans the transport === | ||
| + | The Operator plans a transport with the cooperation of railway leg partners (RU, Local service partners). | ||
| + | The Operator handles this communication with the railway leg partners over the connectivity package. | ||
| + | |||
| + | === Operator manages the transport === | ||
| + | The Operator manages the transport to adjust his plannings along the transport chain. | ||
| + | The Operator handles this communication with the railway leg partners over the connectivity package. | ||
| + | |||
| + | === Operator operates the transport === | ||
| + | The Operator operates the transport to cope with operational events along the transport run. | ||
| + | The Operator handles this communication with the railway leg partners over the connectivity package. | ||
== Preconditions == | == Preconditions == | ||
| Line 10: | Line 27: | ||
== Dependencies == | == Dependencies == | ||
| − | SM12 [[Intermodal Alignment]] must be established to enable the grouping of those basic services into this package. | + | SM12 [[Intermodal Alignment]] must be established to enable the grouping of those basic services into this connectivity package. |
== Planned Steps == | == Planned Steps == | ||
== Evaluation == | == Evaluation == | ||
Latest revision as of 09:28, 16 June 2021
Contents
Description
To simplify the communication between external Operators a standardized data exchange needs to be defined and implemented. The Operator can use a software package to integrate railway legs in their own transport chains. This connectivity package enables the Operator to communicate with the railway service partners
- along a standardized process
- with standardized messages and data formats
- over a defined and stable interface
- in a transparent mode.
an offering to third parties to connect to our ecosystems for data exchange, platform services or marketplace participation in regards with intermodal transports.
Use Case
Operator plans the transport
The Operator plans a transport with the cooperation of railway leg partners (RU, Local service partners). The Operator handles this communication with the railway leg partners over the connectivity package.
Operator manages the transport
The Operator manages the transport to adjust his plannings along the transport chain. The Operator handles this communication with the railway leg partners over the connectivity package.
Operator operates the transport
The Operator operates the transport to cope with operational events along the transport run. The Operator handles this communication with the railway leg partners over the connectivity package.
Preconditions
Basic Services
Dependencies
SM12 Intermodal Alignment must be established to enable the grouping of those basic services into this connectivity package.
