Predictive maintenance has become the dominant paradigm in bearing condition monitoring. The premise is compelling: by continuously monitoring vibration, temperature, and other physical parameters, you can detect degradation early enough to schedule replacement before failure occurs. Downtime is planned rather than unplanned. Costs are predictable. The bearing never reaches catastrophic failure.
Except when it does.
Predictive maintenance systems are designed to prevent failures. They are not designed to document failures that occur despite prediction — or failures that were never predictable in the first place. When a bearing fails and the question shifts from “how do we fix this?” to “who pays for this?”, predictive maintenance data is structurally inadequate for the task. Understanding why requires examining what predictive systems actually capture, what they discard, and what they were never intended to record.
What Predictive Maintenance Systems Capture
A typical predictive maintenance system for bearing monitoring collects data on a scheduled or continuous basis:
- Periodic vibration spectra — FFT snapshots taken at regular intervals (hourly, daily, or weekly), stored as frequency-domain representations. These show the distribution of vibration energy across frequencies at a single point in time.
- Trend data — Time-series of derived metrics such as overall vibration amplitude (velocity RMS, acceleration peak), bearing condition indicators (envelope spectrum amplitudes at defect frequencies), and temperature. These are stored as scalar values over time.
- Alarm events — Timestamped records of when a monitored parameter exceeded a configured threshold. These include the parameter name, the threshold value, and the measured value at the time of the alarm.
- Health scores — Composite indices computed by proprietary algorithms that combine multiple parameters into a single “health” value, often on a 0–100 or traffic-light scale.
This data is well suited to its intended purpose. A maintenance planner can observe a bearing’s health score declining from 95 to 72 over three months, correlate this with rising BPFO amplitudes in the vibration spectra, and schedule replacement during the next planned outage. The system has done its job: failure was predicted and prevented.
What Predictive Maintenance Systems Discard
To maintain storage efficiency and analytical clarity, predictive systems routinely discard the data that would be most valuable in a forensic investigation:
Raw Time-Domain Waveforms
The FFT spectrum that gets stored is computed from a raw vibration waveform — a time-series of acceleration values sampled at high frequency (typically 10–50 kHz for bearing applications). This waveform is the primary physical measurement. The FFT is a derived representation that discards phase information and temporal structure. Most systems compute the FFT at the edge or gateway level and transmit only the spectrum. The raw waveform is overwritten.
In a forensic investigation, the raw waveform is often more informative than the spectrum. Impulse patterns, modulation characteristics, transient events, and the temporal relationship between different vibration sources are all visible in the time domain and invisible — or ambiguous — in the frequency domain. Once the waveform is discarded, this information is permanently lost.
High-Frequency Content
Many predictive systems sample at rates sufficient for routine monitoring (5–10 kHz) but insufficient for forensic analysis of high-speed bearings or early-stage defects. The characteristic frequencies of an incipient spall on a high-speed bearing can exceed 20 kHz. Envelope analysis, which demodulates the high-frequency resonance excited by bearing impacts, requires even higher sampling rates. Standard monitoring systems often lack the bandwidth to capture these signals, meaning the earliest physical evidence of the defect was never recorded.
Continuous Pre-Event Data
Predictive systems capture data at intervals — once per hour, once per day, or in response to triggered events. Between captures, the bearing’s physical state is unrecorded. If a failure occurs between scheduled measurements, the last available data point may be hours or days old. The progression of the failure from its final detectable state to catastrophic failure — the most forensically critical interval — falls in the gap between measurements.
The Three Failure Modes That Predictive Systems Cannot Document
1. The Unpredicted Failure
Not all bearing failures are predictable. A foreign object drawn into the bearing, a sudden loss of lubrication due to a seal failure, a transient overload from a process upset, or a manufacturing defect that manifests as a sudden fracture rather than progressive fatigue — these events do not produce the gradual degradation signature that predictive systems are designed to detect. The first indication of failure is the failure itself.
When this happens, the predictive maintenance record shows a healthy bearing right up to the moment of catastrophic failure. The data proves that prediction was attempted and that no degradation was detected — but it says nothing about what actually caused the failure. The forensic gap is total.
2. The Disputed Failure
When multiple parties contest a failure, the question is not just “what happened?” but “can the data be trusted?” Predictive maintenance data is stored on systems controlled by one of the parties to the dispute. The equipment operator controls the local SCADA system and historian. The monitoring vendor controls the cloud analytics platform. Neither party can provide data that the other party is obligated to accept as unaltered.
Even when the data is perfectly accurate, its provenance is suspect. A bearing manufacturer accused of a product defect will question whether the operator’s monitoring data was collected correctly, stored properly, and exported completely. An operator accused of abuse will question whether the vendor’s analytics algorithm was properly calibrated. The data becomes a new axis of dispute rather than a basis for resolution.
3. The Infrastructure-Correlated Failure
Catastrophic bearing failures often correlate with infrastructure disruptions. The same event that destroys the bearing — a power surge, a coolant system failure, a structural overload — often disrupts the monitoring infrastructure. Sensors lose power. Network connections drop. Cloud uploads fail. The monitoring system goes blind at the precise moment when recording matters most.
Predictive maintenance systems are designed to operate within normal infrastructure conditions. They are not designed to survive the conditions that accompany catastrophic failures. A battery-less vibration sensor that relies on facility power and Wi-Fi connectivity will capture nothing during a power-loss event — which is exactly the type of event most likely to cause or accompany a bearing failure.
What Failure Evidence Requires Instead
Documenting bearing failures for forensic and dispute-resolution purposes requires a fundamentally different architecture than predictive maintenance. The system must be designed around the assumption that failure will occur and that the recording must survive it.
- Continuous high-frequency buffering. Raw vibration data must be captured continuously at sample rates sufficient for forensic analysis (25+ kHz), not at periodic intervals. The data is continuously overwritten in a circular buffer — no long-term storage burden — but at the moment a terminal event is detected, the buffer contents are frozen and preserved.
- Event-triggered, single-shot capture. The trigger is the failure itself. The system detects a terminal physical event (impact above threshold, vibration amplitude exceeding a catastrophic limit, sudden temperature excursion) and immediately seals the buffer contents — typically several seconds to minutes of pre-event data and a fixed post-event window. This is a one-time, irreversible capture.
- Power and infrastructure independence. The capture system must operate on battery power, store data locally, and function with zero dependency on facility power, network connectivity, or cloud services. If the lights go out and the network drops, the recorder keeps running.
- Tamper-evident sealing. Captured data must be cryptographically sealed at the moment of capture and stored under multi-party access controls. No single party can access, modify, or delete the data unilaterally.
This is not an enhanced monitoring system. It is a different instrument with a different purpose. Predictive maintenance and failure evidence capture are complementary — the first prevents failures; the second documents the failures that prevention cannot stop.
The Complementary Architecture
The strongest position for any critical asset is to deploy both:
- A predictive maintenance system that monitors the bearing continuously, detects degradation trends, and enables planned replacement before failure. This system prevents the majority of bearing failures and reduces unplanned downtime.
- A forensic evidence recorder that operates independently, captures the failure event if and when it occurs, and preserves a tamper-evident physical record for dispute resolution. This system addresses the failures that prediction cannot prevent — the rare, catastrophic, disputed events where ambiguity is the most expensive outcome.
The predictive system optimizes uptime. The forensic recorder preserves truth. Together, they address both the operational and the adversarial dimensions of bearing failure — which, for critical assets, are the two dimensions that matter most.