Applications / Operations Intelligence
Load-Out & Dispatch Verification
Detects what was loaded, onto which vehicle, at which bay and when, and flags loads that leave outside their planned slot or against the wrong dock.
See it in action
A trailer that left a bay it was never booked into
Video slot — awaiting upload.
What it detects
A dispatch error is cheap to catch at the dock and expensive to catch at the customer. Fogsphere logs the load-out as it happens and correlates it with what the WMS expected.
Loading start and finish detection
Detects when loading begins and ends at each bay, and how many pallets moved between those two points.
Loading against planned slots
Flags loading activity that happens outside its scheduled slot, or at a dock the plan did not assign.
Wrong-dock and wrong-bay detection
Identifies trailers positioned at the wrong dock, and unloading delays measured against the production window.
Trailer and container door events
Logs trailer and container door openings, and flags doors opened outside a scheduled window.
Seal check evidence
Captures visual seal state where the seal is in view, as timestamped evidence attached to the departure.
Unauthorised coupling and departure
Detects a trailer coupled or moved without dispatch authorisation, or departing before the load is complete.
Loading and unloading verification
Confirms that loading or unloading actually took place at a bay, against the delivery record.
Gate events without system correlation
Surfaces gate and door events with no matching WMS or badge record, as a reconciliation exception.
Dispatch readiness
Reports which bays and staged loads are ready to go, and which are still waiting on material.
Tanker connection supervision
Monitors tanker loading and unloading, hose connection, and vehicle movement while a hose is connected.
Late dispatch and turnaround
Measures trailer dwell and turnaround by bay, and flags dispatches running behind their slot.
Where it applies
Every Q3 paper with a dock face describes the same reconciliation gap between the system record and the physical movement. The bay changes; the exception does not.
How it works
Edge inference on the cameras you already have
Detection of vehicles, pallets, doors and loading activity runs on the edge device next to the cameras already covering the dock face. Bay, trailer and movement are resolved from the same frames.
Zones, thresholds and schedules you configure
Draw each bay and approach lane, set the slot schedule loads are checked against, and set what counts as a complete load-out. Ambient docks, reefer bays and tanker bays can each hold different rules.
Every event carries its own evidence
Each detection is logged with a timestamp, the camera and zone it came from, and a short clip. The record can be reviewed, exported or attached to an investigation without trawling through hours of footage.
Feeds the systems already in place
Events surface in Fogsphere Manager and route outward to the WMS, TMS, yard-management system, security desk or messaging channel operators already watch.
Risk & control objective
The control objective is a defensible record of what left the site. Paperwork and scans record what was supposed to happen; they do not show the pallet that went onto the wrong trailer at 03:40.
The value is in the reconciliation. A gate event with no matching WMS record, a door opened outside a slot, a departure before the load finished — each is an exception a person can close out in minutes, given the clip. Without the clip it becomes an investigation weeks later, against a customer claim.
The same record supports chain-of-custody obligations. Timestamped dock, gate and dispatch evidence is what a security standard, a customs query or a supplier dispute actually asks for.
Related solutions
Know what left the dock, and on which trailer
We will show you load-out timing, slot-adherence checks and dock evidence capture on your own camera estate.