Why defect frequencies are the giveaway
Every rotating fault has a signature frequency, and the useful thing about bearings is that theirs are not whole multiples of shaft speed. Imbalance shows at 1× shaft speed. Misalignment typically at 1× and 2×. Looseness produces a run of harmonics. Bearings, by contrast, produce four characteristic frequencies determined by the geometry — number of elements, element diameter, pitch diameter, contact angle:
- BPFO — ball pass frequency, outer race: an element passing a defect on the stationary outer race.
- BPFI — ball pass frequency, inner race: a defect on the rotating inner race, usually with sidebands at shaft speed because the fault moves in and out of the load zone.
- BSF — ball spin frequency: a defect on a rolling element itself, often appearing at twice BSF because the flaw strikes both races.
- FTF — fundamental train frequency: the cage, which rotates at well below shaft speed. A rare but serious finding.
Because these fall at non-integer multiples of shaft speed, a spectrum that shows raised energy at, say, 4.37× shaft speed is saying something quite specific — and it is saying it in a language that imbalance and misalignment cannot speak. Bearing manufacturers publish these multipliers per part number, which is why knowing which bearing is actually installed is not administrative detail; it is the difference between a diagnosis and a guess.
What envelope analysis is for
Bearing impacts are sharp, small and fast — high frequency, low energy. In an ordinary vibration spectrum they sit underneath the far larger low-frequency energy of rotation, mesh and process noise. Envelope analysis (also called demodulation) filters to the high-frequency band where those impacts excite structural resonances, then extracts the envelope of that signal — the repetition rate of the knocking rather than the ringing itself. The result moves a fault that was invisible at stage 2 into plain view.
It is worth understanding the limitation as well: envelope analysis is sensitive to the band you choose and to how the sensor is mounted. A magnetically mounted sensor on a painted surface will not deliver the high-frequency fidelity that a properly stud-mounted one will — which is one of the reasons apparently identical monitoring programmes produce very different results, a theme we cover in why most vibration monitoring projects fail.
Where we draw our own line, plainly: addanode's condition monitoring provides continuous vibration, temperature and motor-current trending — it is built to tell you, reliably and without a site visit, that an asset's behaviour has changed and when it started. Naming a specific defect from a spectrum is specialist analysis work, and on a critical asset it is worth commissioning. The two are complements, not competitors: continuous trending decides which machine deserves an analyst's afternoon, and an analyst turns "this changed three weeks ago" into "outer race, plan the swap". A plant that buys the second without the first pays a specialist to walk past healthy machines.
How much warning do you actually get?
Honestly: it varies more than vendors like to admit. Detection at stage 2 typically buys weeks to months on a moderately loaded asset at steady speed — enough to order the part, plan the outage and change it on your terms. But that window compresses under load, contamination, poor lubrication or high speed, and it can collapse quickly once stage 3 sets in.
Which argues for the discipline rather than the promise: trend continuously, act on change rather than on absolute thresholds, and treat the alarm as the start of a planning conversation rather than an emergency. The value is not that the machine gets fixed — it would have been fixed either way. The value is that it gets fixed during a planned window, with the right part on site, instead of at 02:00 on a Sunday with a production line behind it. We put numbers to that in the cost of unplanned downtime.
Where to start on a real plant
- Rank by consequence, not by count. Instrument the bearings whose failure stops production, floods a level or parks a fleet — usually a much shorter list than the asset register suggests.
- Record what is installed. Bearing part numbers on the monitored assets, so defect frequencies can be calculated when it matters.
- Get the mounting right. Sensor location and mounting method determine whether stage 2 is visible at all. This is where most of the technical quality of a programme is decided.
- Establish a baseline before drawing alarm lines. Machines differ; a level that is alarming on one pump is normal on its twin. Change from that machine's own baseline is the reliable signal.
- Write down what happens on an alarm. Who looks, within how long, and what authority they have to schedule work. A programme with no agreed response is a data collection exercise, not maintenance.