Difference between revisions of "Port Terminal Communication"
From RFF Wiki
| Line 3: | Line 3: | ||
== Description == | == 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 | 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. | ||
== Use Case == | == Use Case == | ||
Revision as of 21:16, 27 May 2021
Contents
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.
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.
