Who Owns the Fleet Data

The installation is a project. What follows is a permanent part-time job, and it is routinely unassigned.

The recurring work

Device register: fittings, swaps, removals, disposals.

Data quality: the four quarterly checks.

Alert tuning, and turning off the ones nobody acts on.

The fault code triage list, reviewed annually.

Service thresholds, adjusted as vehicles and work change.

Reporting: the cost figures, quarterly and annually.

Totalled, a part-time role, usually absorbed by whoever runs the depot and was not asked.

What goes wrong without it

The register drifts, so per-vehicle history becomes unreliable — and replacement decisions get made on the wrong vehicle's data.

Alerts accumulate and stop being read.

Devices fail and nobody notices, because a vehicle reporting nothing looks like a vehicle not moving.

Service triggers stay at their initial settings as the fleet's work changes.

And the cost reporting stops, which is how a deployment quietly becomes a map subscription.

Naming the owner

One person, named, with allocated time.

With authority over configuration, or every threshold change is a request to someone busier.

With a deputy, because quarterly checks do not pause for annual leave.

And with the standing to decline the requests in the refusal note, which arrive from people more senior.

The runbook

How a device is fitted, recorded and verified.

The four data quality checks and what each means.

How an alert is tuned or retired.

How the triage list is updated.

Written so the deputy can follow it, which is the test.

What to report

Monthly: alerts acted on, devices not reporting, codes by group.

Quarterly: the four data quality checks, utilisation, unscheduled maintenance proportion, days off road.

Annually: whole-life cost by cohort, replacement candidates, and whether the deployment delivered what the case promised.

The measure of whether the role exists

When a device stops reporting, how long before someone notices?

If the answer is "at the next service", the deployment is unowned — and everything above is already drifting.

Watch for devices that stopped reporting

The failure that hides in plain sight.

A vehicle transmitting nothing looks identical to a vehicle not moving.

Which means a dead device can go unnoticed for months, taking that vehicle's history with it.

A weekly list of non-reporting devices, checked against the vehicles in use, is a two-minute task and the single best indicator that the role exists.

Follow the difficult record

Use transparent employee screen monitoring to frame one representative case. The useful evidence is the record created when a value is corrected, approved and exported.