Vibration Monitoring: Reading What Your Machines Are Telling You

A machine talks before it fails. Vibration is the loudest language it speaks — and the earliest. By the time a bearing is hot enough to feel, the damage is hours from a catastrophic stop. By the time it shows in vibration, you still have weeks.

Vibration monitoring is the backbone of condition-based maintenance, and it is the sensing layer that makes predictive maintenance possible. Here is how to read it.

Why Vibration, Not Temperature or Oil

Every rotating-machine fault changes the vibration signature in a specific, recognizable way — often long before any other symptom. Temperature lags: it measures the consequence of damage, after friction has built up. Oil analysis catches particle debris but needs lab turnaround. Vibration responds in milliseconds and can be measured continuously.

The signal is information-dense: a single accelerometer captures unbalance, misalignment, looseness, bearing defects, gear faults, resonance, and structural issues — each in a different part of the spectrum.

What You Are Actually Measuring

Three waveform quantities matter:

• Velocity (mm/s or in/s) — the best overall indicator of fatigue severity. ISO 10816 and ISO 20816 set alarm bands based on RMS velocity. This is the number you threshold on for general machine health.
• Acceleration (m/s² or g) — most sensitive to high-frequency impacts. The right metric for bearing and gear defects, which produce sharp impulses.
• Displacement (µm or mils) — emphasizes low-frequency movement. Used for low-speed machines and shaft-orbit analysis.

Most condition monitoring uses RMS velocity for the overall alarm and acceleration envelope / peak for early bearing detection.

The Spectrum: Where Each Fault Lives

An FFT turns the time waveform into a frequency spectrum, and each fault has an address:

• 1× running speed (1X) dominant — unbalance. The rotor is heavier on one side. Fix: balancing.
• 2× (2X) with a 180° phase shift across the coupling — misalignment (angular or parallel, shaft-to-shaft). Fix: laser alignment.
• Integer harmonics (1X, 2X, 3X, 4X…) with a high 1X — mechanical looseness: soft foot, loose bolts, cracked foundation. (Yes — bolt looseness shows here too.)
• Non-integer, sub-synchronous — oil whirl, rub, or sleeve-bearing instability.
• High-frequency, non-synchronous peaks — bearing defect frequencies (BPFO, BPFI, BSF, FTF). These are predictable from bearing geometry. Their appearance is the classic early warning of spalling.
• Gearmesh frequency and sidebands — gear wear. Sideband spacing reveals which gear.

You do not memorize every frequency. You trend them. A new peak that was not there last month is the signal — whatever its exact address.

Route-Based vs Continuous Monitoring

• Route-based (periodic): A technician walks a route monthly with a handheld collector. Cheap, covers many machines. Gap: a failure that develops between rounds is missed. Good for non-critical assets.
• Continuous (permanent sensors): Accelerometers wired to a gateway, sampled constantly. Catches incipient faults the day they appear. Required for critical machines where downtime is very expensive.

The cost of permanent monitoring has collapsed — a tri-axial IEPE sensor plus gateway is now a few hundred dollars per point. The barrier is no longer hardware; it is data interpretation.

When Vibration Is Not Enough: The Bolt-Looseness Problem

Not every fault announces itself in obvious spectrum lines. Bolt looseness is the hard case — its signature is subtle and distributed, overlapping heavily with normal operation. Traditional FFT features (RMS, kurtosis, individual peaks) struggle to separate loose from tight with confidence.

This is where vibration analysis crosses into machine learning. Our research on shaft vibration data shows that raw-signal convolutional networks with channel attention can detect bolt looseness at 87% faulty recall — where hand-crafted features plateau around 68%. Read the full study →

The takeaway: standard vibration monitoring handles the 80% of faults cleanly. The remaining subtle faults need smarter signal processing — and the data you are already collecting is enough.

Getting Started

1. Pick your 5 most critical machines — the ones where failure stops production.
2. Mount a tri-axial accelerometer on each bearing housing, radial and axial.
3. Establish a baseline — 2 to 4 weeks of normal operation. Everything is judged against this.
4. Set ISO 10816 velocity alarms as the first layer, then add trend-based alerts for specific fault frequencies.
5. Review spectra monthly until the patterns are familiar, then move to exception-based review.

See how OpexMX turns vibration data into work orders →

---

About OpexMX

OpexMX (Opex Maintenance eXecution System) is a cloud CMMS for manufacturing maintenance teams. OpexMX replaces WhatsApp-driven maintenance with structured work orders, workload balancing, asset history, and real-time dashboards. Built by Opex Consulting Group in Singapore, OpexMX is designed so technicians will actually use it. Learn more about OpexMX.