Here is a number: 8.9 mm/s of vibration on a frac pump's power end. Is that a problem?
You can't answer, and neither can an algorithm, until you know what the pump was doing. At idle, 8.9 is alarming. At 80% of rated hydraulic horsepower, mid-stage, with discharge at 9,800 psi, it may be Tuesday. The same reading is two different facts depending on the operating state — and a monitoring system that doesn't know the state will either miss the real failure or cry wolf until the crew stops reading its alerts.
The sensor sees the machine, not the operation
Standalone machine-health platforms are good at what they do: sensors, large failure libraries, expert-validated diagnostics. But their unit of analysis is the machine in isolation. On a frac spread, the operating context changes every few minutes — rate ramps, stage transitions, units idled and brought online, gensets shedding and picking up load. Vibration, temperature, and pressure all move with it. Strip the context away and every baseline is wrong half the time.
What a finding should carry
In the KNOCE platform a diagnostic finding is not a threshold crossing. It carries:
- The failure mode it points to — fluid-end washout, bearing wear, compressor fouling — named in plain language.
- A confidence score, so an engineer knows whether to act now or watch.
- Cited evidence: which signals moved, by how much, since when, against which baseline.
- The operating state it was seen in — the rate, the load, the stage — because that is what makes the evidence mean something.
The evidence is the part we care most about. A finding that says "bearing wear, 88%" is an opinion. A finding that says "power-end vibration up 2.6× over six hours with a growing 1× running-speed component, bearing temperature 218°F and climbing, lube-oil temperature steady — so it isn't cooling" is a case an engineer can check.
Where remaining useful life fits
Remaining useful life — RUL — is the natural next step: fit the degradation trend and project it to the threshold. It is also the easiest number to oversell. A projection of "120 hours" is really a band, and it moves with load: the bearing that has 120 hours at idle has fewer at full rate. When RUL ships in KNOCE it will carry its uncertainty the same way findings carry their confidence, and it will be computed against operating context, not calendar time. Until then it's on our roadmap, and our Why KNOCE page says so.
The chain that matters
Sensor → machine state → operating context → finding → operator decision → maintenance action → equipment history. Every link in that chain is data the platform already has because it sits in the operation, not beside it. That is the difference between monitoring a machine and connecting machine health to operations — and it is the part a vibration sensor alone can never reproduce.