- Knowledge Base
- Ocean Freight
- Container Level Tracking
Which event types shall I select for an ocean tracking plan?
Triggering events from ocean carriers are consolidated in Scope. You will only need one event per category in your tracking plan.
Syntax and examples
For example the Departure Events OCEANINSIGHTS_VDL, INTTRA_VD, CARGOSMART_VD and more are consolidated to ACT_DEPARTURE. ACT: Actual time stamp of the vessel leaving the port.
List of new consolidated types
Arrival
- ACT_ARRIVAL
- EST_ARRIVAL
Departure
- ACT_OCEAN_DEPARTURE
- EST_DEPARTURE
- ACT_DISCHARGE
- EST_DISCHARGE
Delivery/Drop-off
- ACT_DELIVERY
- EST_DELIVERY
Pickup
- ACT_PICKUP
- EST_PICKUP
Terminal in/Gate in
- ACT_TERMINAL_IN
- EST_TERMINAL_IN
Terminal out/Gate out
- ACT_TERMINAL_OUT
- EST_TERMINAL_OUT
Empty Pickup/Pickup Equipment
- ACT_EMPTY_PICKUP
- EST_EMPTY_PICKUP
Empty Return/Return Equipment
- ACT_EMPTY_RETURN
- EST_EMPTY_RETURN
Onboard/Loaded on Board
- ACT_ONBOARD
- EST_ONBOARD
Recommendations and notes
The generic ocean codes can replace most of the ocean carrier codes, but not all of them. Carrier event codes will still be obtainable and can be used in Scope.
Generic ocean codes are backwards compatible, there is no need to update old tracking plans. Also, the old events won’t be deleted in old tracking plans without further notice.
Add a location to the event type
We recommend adding the event attribute location to the event type. This is useful to ensure that departure or arrival of a vessel is correctly assigned, especially on multi leg routes.
Example (DEPARTURE_ACT):
- Click New... in the Event Type configuration window.
- Select the event attribute location, Operator Any and for "value from order attribute" select Port of Loading Main Carriage.
