Standards Development

Scope

This document defines events and associated information elements that are used for tracking and tracing of all types of cargo in the maritime domain. This does not include passengers or crew.

The document also defines information exchanges and information elements based on the ISO 28005 framework.

The document is an elaboration of the UNECE “Business Requirements Specification for Integrated Track and Trace for Multi-Modal Transportation” with its inherent assumptions, which are:

—     All transportation is related to a trade transaction between a seller and a buyer of goods that results in one or more shipments. Therefore, all tracking and tracing and events described in this document ultimately also “link” with these shipments.

—     There is no present need for additional data identifiers to facilitate multi-modal tracking and tracing of trade shipments or the linked transportation in scope for this document. See below this bullet list.

—     Identifiers for trade items, cargo, their packaging or container, or means of transport will support multi-modal tracking and tracing, if the identifiers are globally unique.

—     Linkages can be made between the different identifiers using various existing technologies.

—     The model supports tracking and tracing using various existing technologies by using the most relevant waypoints for the transport journey (as agreed among stakeholders).

—     Standardized exchange processes may be used, without the need to create new class diagrams or new message structures.

The operational scope covers the voyage of the ship, via the terminal, up to and including the gate-in event or gate-out event in the terminal. Gate-in and gate-out events include transfers between the maritime terminal and hinterland modes of transport such as road vehicles, feeder ships, inland waterway barges or rail wagons. The document aims to cover all kinds of cargoes carried on maritime ships.

Cargo moves through ports in two main directions:

—     Coming in from sea to be transported to destinations in the hinterland of the port.

—     Coming in from the hinterland to be transported to overseas destinations on maritime ships.

For the purposes of this document, we will ignore the transshipment scenario where the cargo comes in on maritime ships and also leaves on maritime ships from and to destinations that are not considered part of the hinterland of the port.

The supply chain events that occur outside the boundaries of gate in and gate out mentioned above are not in scope for this document. It is recognised that the transport-related operations covered in the scope of this document are an integral part of the end-to-end supply chain between seller and buyer. Therefore, the requirements outlined in this document will follow standards and "best practices" already in use in the supply chain. This is also driven by the fact that there are critical hand-overs between the wider supply chain and the operations in scope for this document at the gate in and gate out processes that require unambiguous exchange of information related to the critical events in those processes.