The number in each ring = all vehicles there now (standing + moving + offline), so all cards together add up to the whole fleet. "No geofence" = every vehicle outside all geofences, including vehicles on the road and vehicles without a location. Each vehicle is counted in one card only (if geofences overlap, loading/unloading wins, then the nearest). Click a card for km run and engine hours of those vehicles in the last 3, 7, 12 hours and yesterday.

Stopped and idling vehicles that are not inside any loading/unloading geofence. "≥" means the vehicle had already stopped before tracking started (or a data gap), so the real time is longer.

Location names come from the location text sent by Trakzee. Mark loading or unloading places with "Create point". This also applies to past history.

Completed stops outside points that exceeded the threshold: when it stopped, when it moved, and how long.

Route stop: vehicle stopped outside plant, queue and mine for more than the route limit. Call the driver or supervisor. Loading delay: vehicle inside a mine (Loading geofence) longer than the loading limit. Call that mine's loading manager (the in-charge saved on the geofence in Places and people). Unloading delay: inside the unloading point or its queue longer than the unloading limit. After a call, the case stays "Called" until the follow-up time passes; if the vehicle is still standing it comes back as "Follow-up due". Limits are in Settings.

Every alert in the period that needed a call, rebuilt from the timeline with the current limits (route stop, loading, unloading). A call counts if it was logged for that vehicle while it was standing (or within 1 hour after it moved). "Missed" = no call logged. Response time = from the moment the alert started until the first call.

Vehicles marked "GPS not working" from the probable breakdown list, with the expected GPS repair time. When the repair time passes and the GPS is still not fixed, the row turns red. "Signal back" means fresh GPS data has arrived after the report: check and press "Mark fixed".

Vehicles that work inside the plant. They are kept out of Call center and Probable breakdown. Remove a vehicle to bring it back to normal tracking.

Vehicles that have not moved for more than 24 hours, whether stopped or offline, and are not yet marked as breakdown. Press "Confirm breakdown", choose the reason and enter the repair time (ETA). If the vehicle is not repaired by then, it shows in Alerts as "Repair overdue".

To mark a breakdown, search the vehicle number at the top, or press "Breakdown" next to a vehicle in any list. When the repair ETA passes, a red alert appears here and at the top.

Stops of 5+ minutes outside plant, queue and loading geofences, grouped within a 300 m radius (period follows the Trips section above). "Create group" makes a named geofence for that place. To combine several nearby places into one group, draw one large polygon on the map and choose type "Named place".

Red bar = total time the vehicle stood still in stops longer than the minutes above (engine off or idling, not moving). Offline time is not counted. One chart per site; a vehicle belongs to the site it is in now. Click a bar to see that vehicle's stops.

A trip starts when the vehicle leaves the From geofence (last reading inside) and ends when it next reaches the To geofence (first reading inside). If it goes back into From first, the trip restarts from there. When From and To are the same, it shows how long and how many km the vehicle took to come back to that geofence. km = GPS km between the two readings; stops on the way = stopped or idling on the road. Very short hops (under 10 min and under 0.3 km, GPS jumping at the edge) are left out. Geofences drawn later count for past data only after select public.rebuild_segments(48);.

A loading is counted when a tipper stands (stopped or idling) for at least two readings next to an excavator or loader whose engine is on. The excavator's position is the median of its last 20 minutes, so GPS jumps do not move it. When two excavators are close, the nearer one gets the loading. For the first 7 days every excavator uses 50 m; after that its radius is set automatically to the distance within which 90% of its loadings happened (admin can override below).

A tipper's next loading counts only when it has travelled at least the minimum trip km since its previous counted loading. A shorter visit is the same trip: it is not counted again and its km are carried into the next trip. A loading also needs the tipper to stand next to the loader for at least the minimum loading time. The tables show how the real data of the last 14 days is spread, so these limits can be tuned. Suggested values appear once there are 30+ real trips.

P50 / P90 = distance within which half / 90% of the excavator's loadings (last 7 days) happened. Learned radius is set once a day after 7 days and at least 15 loadings, between 15 m and the learning radius. A manual value (admin) always wins; clear it to go back to automatic.

Machines are the vehicle types listed in Settings (Excavator, Loader, Roller…). Engine on = engine running (a machine working in one place at under 3 km/h counts as engine on). Running = time spent moving. Machine efficiency = Engine on ÷ total time passed in the selected period × 100 (Today: hours passed since 12:00 AM; Yesterday: 24 hours; 7 days: the last 168 hours). Off = engine off; No signal = GPS not sending. Time is counted from the 2-minute readings, so gaps when the poller was down are left out. Loadings come from the Loading pairs page.

No signal = Trakzee shows the device as InActive, or no data for 3+ hours. Drops = how many times the device stopped sending in the last 7 days. "Back" = the device started sending again after a gap.

Arrows point where the vehicle is heading (Trakzee angle). Green = moving, amber = idling, purple = stopped, grey = no signal. "To plant / away" compares the distance to the reference plant now and ~10 minutes ago. ETA is straight-line distance × 1.3 at the current speed (at least 20 km/h), so treat it as a rough guide.