Alerts That Get Acted On
A telematics system can generate hundreds of notifications a day. The design that keeps them useful is mostly subtraction.
Procedure
Running it
The installation is a project; what follows is a permanent part-time job that is routinely unassigned.
11 notes
Whether the Data Is Any Good
Four checks that show whether vehicle data will bear weight, and what each means when it moves.
Procedure
Theft, Recovery and Insurance
One of the few uses where position data genuinely earns its retention, and the arrangements that make it work on the night.
Analysis
More Than One Depot
Fleet data becomes comparative, which is useful and is the point at which comparisons start being made badly.
Analysis
Parts, Workshops and Who Does the Work
Where maintenance is done determines what data you get back, and most fleets never make that a selection criterion.
Analysis
Hired and Leased Vehicles
Vehicles you do not own still cost you, and the data arrangements are different in ways that matter at return.
Analysis
How These Deployments Fail
The recurring failures, each visible in the first quarter, each with a specific correction.
Analysis
Who Owns the Fleet Data
The recurring work a telematics deployment generates, and what happens in the usual case where it belongs to nobody.
Analysis
After a Collision
The data exists and is useful. Preserving it, using it fairly, and the handling that keeps it usable.
Procedure
Whether the Numbers Are Believed
A deployment producing data nobody acts on has failed silently. How that happens and what rebuilds it.
Analysis
The Annual Review
What to look at once a year, in what order, and the questions that decide whether any of it is working.
Reference