Equipment and Cargo Events

Introduction

Beyond general shipment milestones (like departure/arrival), FMS allows tracking of specific events related to the handling and movement of physical equipment (primarily containers) and the cargo within them. These Equipment and Cargo Events provide granular visibility into the physical logistics process, especially for containerized transport.

These events are often generated automatically based on templates or setup and are typically recorded against specific Equipment Detail records linked to a Shipment or Consolidation Document.

Standard Equipment and Cargo Event Types

FMS typically supports tracking events such as:

Event Type	Description
Gated Out	Equipment has left a terminal or depot.
Gated In	Equipment has entered a terminal or depot.
Loaded	Equipment loaded onboard a vessel/aircraft/truck.
Discharged	Equipment unloaded from a vessel/aircraft/truck.
Pick-up	Equipment picked up (e.g., empty from depot, full from terminal).
Drop-off	Equipment dropped off (e.g., empty at depot, full at terminal).
Available for Pick-up	Equipment is ready for collection by the next party.
Available for Drop-off	Equipment can be returned to a specific location.
Stuffed	Cargo loaded/packed into the equipment (esp. LCL).
Stripped	Cargo unloaded/unpacked from the equipment (esp. LCL).
Inspected	Equipment or cargo has undergone inspection.
Resealed	Equipment resealed after inspection (new seal number often recorded).
Removed	Equipment or specific cargo removed from the planned shipment.

(Note: This list may vary based on specific FMS configuration)

Recording and Tracking Events

Generation: These events are often automatically added to the relevant Equipment Detail record based on setup linked to the Order Type, Means of Transport, or specific Equipment/Cargo Event Setup.
Execution: When an event occurs, a user (or potentially an integrated system via API) updates the status of the corresponding event record, typically by entering the Actual Date/Time and marking it as completed or executed.
History: Executing an event logs an entry in the Equipment Event Entries table, providing a full audit trail. This history can often be viewed from the related Equipment Detail or Equipment Master record.
Relationship to Milestones: These Equipment/Cargo events often function as specific types within the overall Event and Milestone Management framework of the Shipment or Consolidation Document.

Setup

The specific events generated and potentially required references can be configured via:

Equipment/Cargo Event Setup (Defining which events apply in which scenarios).
Equipment Event Reference Assignment (Defining which reference numbers might be mandatory for certain events).

Synchronized event overview

Equipment and cargo events provide a combined view of container movements and the cargo handled within them. Event synchronization keeps the equipment view aligned with the related cargo activity, including work shared by shipments and consolidations.

Configure the applicable event templates and document relationships before relying on synchronization. After executing a test event, check both the shipment and the related equipment/consolidation view to confirm that the correct cargo and container are represented.

Section-line events

Events can be associated with equipment on a document section, so movements on a specific transport leg can be tracked separately from the main shipment. This is useful when the same container participates in pickup, loading and return activities.

Check the equipment and activity links on the section before entering the event. Use the section's events to follow that leg and the recorded event entries to review execution history.

Voyage cargo events

The voyage number on cargo events associates physical handling with the correct sailing. It helps distinguish the same equipment or cargo when movements involve different voyages.

Maintain the voyage and voyage call on the relevant transport documents and verify the voyage on the event before execution. For changes to the sailing itself, see Voyages and Schedules.

Undo events

Undoing an executed equipment/cargo event corrects the recorded handling without treating a mistaken execution as a new physical movement. Undo support also covers stuffing events.

Use the undo action or the configured CFS scan action for the event that was executed incorrectly. Check the affected cargo, equipment and event history before executing the corrected event. Review any subsequent workflow steps that relied on the original event.

For scan configuration, see CFS operations and scanning.

Table of Contents