Skip to content
Noether Analytics

Illustrative use case · Predictive maintenance

Know what needs attention.

The decision

A ranked list of equipment with expected failure windows and the sensor signals behind each.

Illustrative scenario. No measured client result.

Pump fleet healthInteractive example

Needs attention first

Pump P-03

Failure in 2 to 9 days

Alert threshold 4.5
Anomaly scoreDaily scoreAlert thresholdFailure levelExpected failure

P-03, today: score 11.8. Vibration +15.6σ, temperature +17.6σ, current +4.4σ.

Backtest at threshold 4.5: 14 of 16 failures caught, 3 pumps with a false alarm, median warning 9.5 days.

Synthetic data: 6 pumps, 3 sensors, 90 days. Score: five-day median of the combined deviation from each pump's own baseline. Backtest: 40 simulated pumps with known outcomes.

Synthetic anomaly scores: how far each pump's sensors deviate from its own baseline. A score is not a failure probability. Changing the threshold changes which readings trigger an alert.

Situation

Unexpected downtime is costly. Fixed maintenance intervals miss changing conditions, while unreliable alerts overwhelm the team.

What we built

Learn from sensor and maintenance records where available. Distinguish anomaly detection from failure prediction, and evaluate warning time alongside false alarms and missed failures.

All use cases

Tell us about your problem

The first conversation is free. If we don't think we can help, we will say so.

Talk to us