The Question to Ask First

Most disagreements in this subject are about which feature to buy. One question moves past that.

The question

Which decision would this data change, and who takes it?

Ask it of every field, every alert and every report.

What the answers mean

"A service booking." A named decision, taken by a named person, informed by odometer and hours. Proceed.

"Whether to repair or replace." A decision, informed by whole-life cost and condition. Proceed.

"Whether we need this vehicle." A decision, informed by utilisation across a year. Proceed.

"Whether to send someone to a breakdown or a booking." A decision, informed by fault codes. Proceed.

"We'd know what the drivers are doing." Ask what would be done differently. Usually nothing, which means the request is about reassurance rather than a decision — and it carries obligations the rest of the deployment does not.

Why it works

It separates the operational from the anxious without anyone having to say which they are.

It identifies which fields are needed, which is the configuration decision, the retention decision and the legal analysis all at once.

And it usually reduces the specification, because most of what a platform offers informs no decision anyone actually takes.

The second question

Is this read from the vehicle or estimated?

Because a decision taken on an estimated odometer or a calculated consumption figure is taken on a model rather than a measurement.

Ask it of every field before relying on it, and record the answer in the field list.

Using both

The first decides what to collect.

The second decides how much weight it can carry.

Neither requires buying anything, and both are harder to answer than any question a vendor will ask.

The collection in one line

Read what the vehicle knows about itself, act on it where a named decision exists, and let the position data expire.

Everything else here is the detail of doing that.

Record the answer in the field list

So the decision survives the person who took it.

Every field: what decision it informs, and whether it is read or estimated.

Two columns against a list you already need for procurement.

It becomes the retention policy, the access policy and the legal analysis at once, which is why it is worth the afternoon.

Turn the boundary into a test

For a concrete product reference, visit the official website can help turn this boundary into a test. Verify the current behaviour with representative fields and record what reaches the destination.