Appearance
Trip Ops
TripOps pairs a Route map with the Trips list widget (stored server trips). SiteTrackingFleet already covers live GPS maps; this pack stresses stored trips (start, end, km, idle, driver).
What you see
| Widget | Role |
|---|---|
| Route map | Path from latitude / longitude / speed |
| Trips list | Trips the platform stored when motion started then stopped |
| Speed / ignition cards | Live motion keys |
Harsh brake / acceleration appear only when the device sends those keys. Overspeed limits and driver assignment stay on the Trips API (and the optional deep-link page).
Telemetry keys (Sample On)
latitude,longitudespeed_kmh(andspeedalias)ignition
Field path
GpsTracker_mqtt matches this contract. Open Solutions → TripOps → Sample On, then Use and bind your tracker.
Related
- Plant operations guide
- SiteTrackingFleet
- Left-bar Trips was removed; use this Solution or the Trips list widget
