Fleet Pulse is a real-time fleet monitoring dashboard by Envue Telematics, built on the Geotab MyGeotab API. It connects directly to your database and gives every fleet manager an instant, actionable view of all vehicles — no navigation through MyGeotab required. Data refreshes automatically every 10 seconds in the background with no visual disruption.
Each vehicle is color-coded based exclusively on vehicle-sourced fault codes (OBD-II / J1939 / J1708). Telematics device faults never affect health color — they are shown as informational only.
Each bubble shows the vehicle name, engine state, speed, fault count, and health badge. Hover over any bubble to see a detailed popup with all selected data fields. Click to open the full Fault Detail panel for that vehicle.
Fault codes are shown in standard OBD-II format (e.g. P1101) — the same code a mechanic reads with a scan tool. The fault panel has three tabs:
Click ⊞ Fleet Overview in the header to switch to a detailed list view with full stats and expandable fault tables. Use ↓ Export CSV to download a spreadsheet of current filtered vehicles and their fault codes.
Fleet Pulse silently refreshes all data every 10 seconds. The bubble grid updates in-place — no flash, no reload. The "Last Update" tag shows when data was last received from Geotab.
Every enabled rule produces a score: 100 = perfect, 0 = worst possible. The formula depends on what the rule measures:
Penalty grows with event frequency relative to how far the driver travelled. Occasional events over long distances barely affect the score; frequent events on short runs have a large impact.
The multiplier increases as the speeding % rises — from ×6 (at <0.3%) up to ×20 (at 5%). This means chronic speeders are penalised sharply: spending 5% of a trip over the limit scores 0.
Blends how long the belt was off (distance %) with how often it was off (event count). One long unbuckled stretch is treated differently from many short ones.
Each rule score is multiplied by its weight (the % you set), then the totals are summed and divided by 100:
Weights must total exactly 100%. You control which behaviours matter most — e.g. assign 35% to Speeding if that is your fleet's biggest concern.
Distance source: Total km is taken from Geotab Trip records for the selected period, not from exception event distances. Exception distances (how far the vehicle travelled during a violation) are used only as numerators in the Speeding and Seat Belt formulas.
Each coloured blob marks a location where violations happened. The bigger and brighter the blob, the more violations occurred there. Every blob matches the colour of the rule that caused it — so you can instantly tell whether an area has a speeding problem, a harsh braking problem, or something else.
Think of it like a weather heat map — the "hottest" spots are where your drivers are triggering the most alerts.
A Danger Zone is a specific location where violations keep repeating. Fleet Pulse automatically groups nearby events and ranks the worst spots. The top 10 are listed in the sidebar on the right.