Accuracy, or how close you are to the truth

Data quality

A measurement is accurate when it reflects what is actually happening out in the operation, not what a drifting sensor or a stale conversion says is happening. Everything downstream — the report, the model, the decision — inherits that gap.

What it means

Close enough to the truth to bet on

Accuracy is the distance between a recorded value and the real condition it describes. It is not the same as precision; a reading can be precise to four decimal places and still be wrong by a wide margin.

It degrades quietly. Sensors drift, calibrations expire, a unit conversion gets applied twice, a replacement instrument is wired with a different scale. None of that announces itself.

What it costs

What an inaccurate number actually costs

Nobody budgets for inaccuracy, because the invoice arrives somewhere else — in a decision that went the wrong way, or in the weeks spent proving a figure that was never in doubt.

Decisions built on sand

A drifting reading does not look wrong, it looks like a trend. Teams respond to the trend, schedule work against it, and only discover the instrument was the problem after the intervention.

Trust, once it is spent

It takes one figure being visibly wrong for people to stop trusting the whole system. After that they go back to their own spreadsheets, and the platform quietly stops being the place the answer comes from.

The audit you cannot answer

When a regulator or an auditor asks where a reported figure came from, "the system produced it" is not an answer. Without a way to show the inputs behind a number, defending it turns into a manual reconstruction.

Our approach

How we think about accuracy

Accuracy is not something you bolt on at the end. It comes from keeping a measurement attached to everything that gives it meaning.

Context travels with the measurement

A reading is kept together with the asset that produced it, what that asset does, and where it sits in the operation. A value that is implausible for that context stands out instead of blending in.

The unit is part of the value

Every measurement carries the unit it was recorded in, so a conversion is a deliberate act rather than an assumption someone made years ago. Mixed scales become visible instead of silent.

Nothing is overwritten

Derived values are kept alongside the raw signals they came from, never on top of them. When a number is questioned, the original is still there to check it against.

The other dimensions

Six dimensions, one standard

Quality is not a single number. Each dimension fails in its own way, and each one is worth understanding on its own terms.

Timeliness Consistency Completeness Uniqueness Validity

Want to see this against your own data?