Difference between revisions of "Port Terminal Communication"

From RFF Wiki
Jump to: navigation, search
Line 1: Line 1:
 +
== Description ==
 +
 +
Port and In-Land Communication including standardized consignment notes fro all transportation modes (sea, intermodal (containers, swap-body), SWL, block trains). One common trasportation
 +
 +
Capability enabling Europe-wide standardized communication with ports, terminals and inland transport (including processes, technical specifications and data exchange) and , supported by IT workflows for data exchange, platform services or marketplace.
  
  
== Description ==
 
Port and In-Land Communication including standardized consignment notes fro all transportation modes (sea, intermodal (containers, swap-body), SWL, block trains). One common trasportation
 
  
Capability enabling Europe-wide standardized communication with ports, terminals and inland transport (including processes, technical specifications and data exchange) and built into an operational workflow including all relevant transportation modes (sea, intermodal (containers, swap-body), SWL, block trains), supported by IT workflows for data exchange, platform services or marketplace.
+
To simplify the communication between the RU and Local Operators (ports, terminals, ...) a standardized data exchange (including processes, technical specifications and data exchange) needs to be defined and implemented.
 +
This standard enables the Local Operator to communicate with the railway service partners
 +
* along the standardized process
 +
* with standardized messages and data formats
 +
* over a defined and stable interface
 +
* in a transparent mode.
 +
 
 +
This inter-modal workflow encompasses all relevant transportation modes
 +
* railway
 +
* sea
 +
* road
 +
* air
 +
* and their mode changes
 +
It tackles all traffic types.
 +
* intermodal (containers, swap-body),  
 +
* SingleWagonLoad (SWL)
 +
* block trains
 +
 
 +
This Broker service (-> [https://rff.wiki.interconnective.ch/index.php/Architecture#Integration_with_partners Partner Integration Broker]) offers
 +
* to third parties to connect to the railway ecosystems for data exchange, platform services or marketplace participation for inter-modal transports.
 +
* to the railway partners to simplify the communication with Local Operators and to facilitate the inter-modal traffic.
 +
 
 +
== Use Case ==
 +
=== Local Operator participates in the transport ===
 +
The Local Operator participates in the transport planning together with the RU, Inter-modal Operator and Local service partners.
 +
The Local Operator handles this communication with the railway leg partners over the connectivity package.
 +
 
 +
=== Local Operator assists in the transport replanning ===
 +
The Local Operator contribute to the transport replanning to adjust his own local plannings accordingly.
 +
The Local Operator handles this communication with the railway leg partners over the connectivity package.
 +
 
 +
=== Local Operator operates the transport ===
 +
The Local Operator operates the transport to cope with operational events at his location .
 +
The Local Operator handles this communication with the railway leg partners over the connectivity package.
  
 
== Use Case ==
 
== Use Case ==

Revision as of 10:38, 16 June 2021

Description

Port and In-Land Communication including standardized consignment notes fro all transportation modes (sea, intermodal (containers, swap-body), SWL, block trains). One common trasportation

Capability enabling Europe-wide standardized communication with ports, terminals and inland transport (including processes, technical specifications and data exchange) and , supported by IT workflows for data exchange, platform services or marketplace.


To simplify the communication between the RU and Local Operators (ports, terminals, ...) a standardized data exchange (including processes, technical specifications and data exchange) needs to be defined and implemented. This standard enables the Local Operator to communicate with the railway service partners

  • along the standardized process
  • with standardized messages and data formats
  • over a defined and stable interface
  • in a transparent mode.

This inter-modal workflow encompasses all relevant transportation modes

  • railway
  • sea
  • road
  • air
  • and their mode changes

It tackles all traffic types.

  • intermodal (containers, swap-body),
  • SingleWagonLoad (SWL)
  • block trains

This Broker service (-> Partner Integration Broker) offers

  • to third parties to connect to the railway ecosystems for data exchange, platform services or marketplace participation for inter-modal transports.
  • to the railway partners to simplify the communication with Local Operators and to facilitate the inter-modal traffic.

Use Case

Local Operator participates in the transport

The Local Operator participates in the transport planning together with the RU, Inter-modal Operator and Local service partners. The Local Operator handles this communication with the railway leg partners over the connectivity package.

Local Operator assists in the transport replanning

The Local Operator contribute to the transport replanning to adjust his own local plannings accordingly. The Local Operator handles this communication with the railway leg partners over the connectivity package.

Local Operator operates the transport

The Local Operator operates the transport to cope with operational events at his location . The Local Operator handles this communication with the railway leg partners over the connectivity package.

Use Case

Preconditions

Basic Services

Dependencies

SM12 Intermodal Alignment must be established to unify the communication with intermodal change point operators like ports, terminal, hubs.

Planned Steps

Evaluation