Knowing Whether the Data Is Any Good
Four checks that show whether the records will bear weight, and what each one means when it moves.
Procedure
Running it
The project ends at go-live; the system generates work indefinitely, and in most deployments nobody was assigned to it.
8 notes, in reading order
Collisions and Incidents
The situation where location and telematics data is genuinely valuable, and the handling that keeps it usable.
Procedure
Whether It Paid For Itself
Vendor savings figures assume things that are rarely true. What to measure before and after, and the costs that appear later.
Procedure
Using It in an Emergency
The moment the system justifies itself, and the preparation that decides whether it actually helps.
Procedure
Securing the Location Data
A database of where your staff are, live, is attractive to people other than you. What a breach here means and what it needs.
Procedure
Turning It Off
Ending a deployment, changing vendor, or disposing of vehicles. The data outlives all three unless someone handles it.
Procedure
Who Runs It Afterwards
The recurring work a location deployment generates, and what happens in the usual case where nobody was assigned to it.
Analysis
When the Vendor Adds a Feature
Hosted telematics changes underneath you, and new capabilities arrive switched on. The check that catches it.
Procedure