HARTS AI connects vehicle tracking, yard activity and transport plans in one configured workspace.
Spot movement exceptions as they happen, coordinate a response across drivers, controllers and yard staff, and follow a structured workflow from gate arrival through to departure. It sits over the systems you already run, part of our wider connected operations platform.
One workflow
Gate arrival through to departure, linked to each visit and task.
Outside tolerance
Flagged and sent for review with the supporting records attached.
Each source keeps its role. HARTS AI relates them so controllers act on exceptions, not raw feeds.
Relate planned routes, destinations and schedules to live and historical movement. Configured geofences and time thresholds surface off-route activity, unplanned stops and arrival or departure delays as a prioritised list.
Bring access validation, bay allocation, vehicle inspections, dwell tracking and exit clearance into the configured arrival-to-departure process. Each milestone links to its visit and task.
Send drivers, controllers and yard staff structured WhatsApp task cards, instructions and status requests. Acknowledgements and delay reasons are captured against the same record.
The decision stays with the controller. The system gathers context, routes the question and keeps the evidence.
A vehicle exceeds an agreed dwell threshold at a bay.
The controller receives the visit context automatically and sends a structured WhatsApp card to the yard team to confirm the reason.
The response is logged against the visit record.
When the vehicle departs, the movement record closes and is available for review alongside similar events from the same period.
Recorded milestones and confirmed reasons let you review performance with context. The shared record helps teams identify recurring delays and decide where to investigate. See how this applies across other industries we support.
Time at bays, with the confirmed reason.
Gate arrival to exit clearance.
Off-route activity and unplanned stops.
Where delays recur over a period.
Start by scoping and validating a single high-value workflow, such as bay dwell or arrival delays, then scale from there. No rip-and-replace: your tracking, yard and transport planning systems keep their role.
