Container & vessel tracking + last-free-day watch
Stage 2 · Dispatch & Drayage Operations
P1Core Operations
Four-Lane View
Software Function
- ›Terminal/ocean data ingest (Terminal49-class APIs + direct terminal feeds): vessel ETA, discharge, holds, availability LFD countdown on every container with risk scoring Hold alerts (customs, freight, TMF) pushed the moment they clear or appear Auto re-plan: LFD risk re-prioritizes the dispatch board
Service Provider / Admin
- ›Ops watches a risk-ranked container board, not a spreadsheet Escalation runbook per hold type; client notified with the fix, not just the problem
User — Driver / IOO
- ›Never sent for a container that isn’t available — availability verified before dispatch Terminal, appointment and chassis info attached to the leg
Customer — Client / FF / NVOCC
- ›Live container status from vessel to gate-out — the "where is my freight" answer without a phone CLIENT/FF/NVOCC call Proactive LFD/demurrage risk warnings with our mitigation plan attached
Software Function
- ›Terminal/ocean data ingest (Terminal49-class APIs + direct terminal feeds): vessel ETA, discharge, holds, availability LFD countdown on every container with risk scoring Hold alerts (customs, freight, TMF) pushed the moment they clear or appear Auto re-plan: LFD risk re-prioritizes the dispatch board
Competitors
Terminal49 (tracking API — buy-don’t-build candidate), project44 Ocean/Terminal (enterprise-priced), BlueCargo (D&D analytics)
Differentiation
Visibility vendors sell the alarm. We own the truck, so our alarm comes with the response: re-planned dispatch before the client ever sees the risk.
Make It Better
Zero surprise demurrage: every at-risk container is flagged ≥48h before LFD with a dispatch plan already in motion — $0 demurrage as a published service standard.