Run the container journey against the clocks that actually cost money.
An import logistics control tower for ocean arrivals, terminal availability, drayage, appointments, chassis, free time, detention, demurrage, and warehouse receiving.
Scale and interface figures on this page are illustrative.
Every container is governed by more than one clock.
Availability, last free day, appointments, equipment return, warehouse receiving, and customer commitments overlap. The product makes those clocks visible before they become charges.
Fragmented context
ETA alone was insufficient; operators need availability, customs status, terminal holds, last free day, appointment and delivery commitments together.
Decision logic
Demurrage and detention are different clocks with different owners and mitigation actions.
Operational handoff
A container can be “arrived” but still unavailable because of customs, freight, terminal or exam holds.
Milestones are the operating model.
Carrier, terminal, broker, drayage, and warehouse events reconcile into a single container journey with source confidence.
Journey
Booking, vessel, discharge, availability, pickup, delivery, empty return.
Free-time board
Last free day, per-diem start, terminal storage risk and ownership.
Drayage
Carrier assignment, appointment, driver/chassis, pickup and POD.
Exceptions
Holds, rolled vessels, missed appointments, exam, congestion and warehouse rejection.
Cost audit
Accruals, accessorial evidence, dispute package and recovered/approved charge.
Exceptions need an owner before they need a chart.
A hold, missed slot, or free-time deadline immediately becomes an actionable operating case.
Representative application states.
Representative application states from the product. Figures shown on screen are illustrative.
Import containers
NY/NJ gateway
| Container | Journey | Last free day | Status |
|---|---|---|---|
| MSCU 883104-2 MSC · PNCT | Sep 26 | Pickup booked | |
| OOLU 221498-7 OOCL · APMT | Sep 27 | Customs hold | |
| TCLU 775301-9 ONE · APMT | Sep 28 | No chassis | |
| MAEU 590221-6 Maersk · Maher | Sep 29 | Not available | |
| HLXU 644012-1 Hapag-Lloyd · PNCT | Sep 22 | Empty due Sep 27 | |
| CMAU 108440-3 CMA CGM · Maher | Sep 21 | Detention: 86 min | |
| ZIMU 207448-3 ZIM · PNCT | Sep 26 | Appt missing | |
| EGHU 331906-0 Evergreen · Maher | Oct 01 | Vessel arrived |
Showing 8 of 284. Steps: Vessel → Discharged → Available → Gate-out → Delivered → Empty.
Cost exposure
Containers by clock
Demurrage exposure, next 7 days Saturday is the peak
| Container | Clock | Ends |
|---|---|---|
| MSCU 883104-2 | 4 of 5 days | Sat 23:59 |
| HLXU 644012-1 | Empty due Sun | Sun 17:00 |
| CMAU 108440-3 | Driver detention | Documented |
Dispatch board
Today · 32 moves
32 moves · 6 trucks
Hold case
OOLU 221498-7
OOLU 221498-7 · Customs hold
Event log
- CBP hold event receivedEDI 309 · customs09:14
- Terminal availability still falseAPMT feed09:16
- Broker notified and task openedBroker desk09:20
- Broker response dueOwner: Broker desk14:00
Do the sources agree?
| Source | Says |
|---|---|
| Carrier | Clock running |
| Terminal | Hold, clock paused |
| Broker | No answer yet |
Two sources disagree, so the free-time clock is marked unverified until the broker replies.
Accessorial review
Charge AC-7712
AC-7712 · MSCU 771204-8
| Billed | Supported | |
|---|---|---|
| Days | 6 | 4 |
| Rate per day | $210 | $210 |
| Amount | $1,260 | $840 |
| Dispute | $420 |
Evidence
- Terminal LFD source
- Sep 20 23:59
- Gate-out event
- Sep 24 08:11
- Invoice billed through
- Sep 26
The clock stops at gate-out; two days after it are not chargeable.
Failure states are part of the product model.
The cases below are intentionally modeled because real operating software is defined by what happens when data, people, or dependencies do not line up.
Carrier ETA and terminal ETA diverge
Keep both sourced milestones, rank confidence, and avoid silently overwriting one feed.
Container is discharged but unavailable
Represent hold/availability separately; do not start a pickup-ready state from vessel milestone alone.
Accessorial invoice conflicts with events
Build a dispute packet from terminal/gate/appointment evidence and preserve billed vs supported amount.
The data model behind the interface.
The interface follows the domain relationships and rules below.