Why most condition monitoring goes unread

Plants collect oceans of sensor data and act on almost none of it. The bottleneck was never collection. It was attention.

Walk any modern plant and you will find sensors on nearly everything: temperature, vibration, current, pressure, flow. The data lands in a historian, fills a disk, and is quietly forgotten. The collection problem was solved a decade ago. The attention problem was not.

The firehose nobody drinks from

A single vibration sensor sampling at a few kilohertz produces more numbers in an hour than a maintenance engineer will read in a career. Hand that engineer a raw trend chart and you have not helped them. You have moved the haystack, not found the needle.

So the data sits. Teams fall back on a calendar: grease this bearing every ninety days, swap that filter every quarter, whether it needs it or not. Calendar maintenance is expensive when it is too frequent and catastrophic when it is too late.

Attention is the product

What a team actually needs is a short, ranked list: these three machines are drifting, here is the trace that proves it, here is how long you have. That list is a design problem before it is a data problem. It requires deciding what is worth a human's glance and ruthlessly hiding the rest.

Warping treats that decision as the whole job. Detection runs at the edge so only meaningful events travel up. Visualisation is built so an operator can fall from the whole fleet to one bearing in a single motion. The raw numbers are still there when you want them. They are just no longer the thing you start with.

Where to start

Pick one failure mode that has bitten you twice. Instrument it properly, set a threshold you trust, and route the alert to a person who can act. One honest signal that someone reads beats a thousand that nobody does.

← All field notes

Keep reading