Vibration analysis is the go-to tool for figuring out what’s happening inside rotating equipment—if you collect it the same way, at the right time, and actually act on what it’s telling you.
What is Vibration Analysis?
Vibration analysis measures how a machine is moving. Motors, pumps, fans, gearboxes—everything rotating creates vibration. Some vibration is normal. The useful part is separating “normal for this asset” from “something changed and it’s not headed anywhere good.”
Most vibration programs use a handheld data collector (route-based) or permanently mounted sensors (online). Route-based is common because it’s affordable, flexible, and works with real staffing levels—assuming you can keep the route consistent and get access without turning every reading into a production negotiation.
What Can We Get From It?
What it tells you well
- Imbalance: often shows up strongly at running speed (1×) and responds to balancing when confirmed.
- Misalignment: can show at 1×/2× and axial vibration (depending on coupling and machine type).
- Mechanical looseness: can create broadband energy, harmonics, and unstable readings.
- Bearing issues: early to mid-stage defects show up as high-frequency content and bearing fault frequencies when the data quality is there.
- Gear issues: gear mesh frequencies, sidebands, and changes over time (especially with good speed reference).
- Resonance and structural problems: when vibration changes dramatically with speed/load or mounting condition.
What it does NOT tell you reliably
- Exact root cause from a single number: “overall vibration is high” is not a diagnosis; it’s a reason to look deeper.
- Problems when the machine isn’t behaving normally: if the asset is unloaded, cycling, or running an unusual recipe, the reading may be valid but not comparable.
- Everything, everywhere: if you can’t safely access the right points (guards, heat, height, permit constraints), your dataset will have blind spots.
- Truth without context: speed, load, mounting, and recent maintenance matter. Without them, trends can lie convincingly.
How Does That Work In Our Plant?
Vibration analysis is powerful, but it’s not “set it and forget it.” It needs repetition and consistency—two things plants don’t naturally hand you on a silver platter.
- Production vs. reliability: you want stable operating conditions; production wants throughput. You’ll rarely get both perfectly.
- Resource constraints: when the maintenance team is buried, the vibration route is an easy target to skip—right up until a failure forces everyone into overtime.
- Budget pressure: vibration tools and training cost money, and leadership loves cutting “invisible” work. The best defense is converting findings into planned work that prevents unplanned downtime.
- Change resistance: a new vibration program can feel like “extra paperwork.” Keep it practical: focus on critical assets and defects that lead to actions, not a library of unread spectra.
- Access windows are tight: if you can only get near certain assets during changeover or a narrow maintenance window, design the route around reality, not ideals.
“There’s Gotta Be A Reasonable Explanation”
Vibration data is usually viewed in two ways:
- Overall level: a single value (often velocity) that’s useful for screening and trending.
- Spectrum (FFT): a frequency “fingerprint” that helps identify the likely fault type (imbalance, misalignment, bearing, gear, looseness, etc.).
The most useful mindset is: trend first, diagnose second. Trending tells you something changed. The spectrum helps you decide what kind of change it is and what work makes sense.
“This Is How We Do It”
Route-based collection
A route typically includes defined measurement points (drive end/non-drive end, horizontal/vertical/axial) and consistent settings (sample time, frequency range, filters). Consistency is the whole game.
- Same points: paint mark or tag the location; “close enough” becomes “worthless trend” over time.
- Same mounting method: magnet vs. stud vs. probe matters. Pick one per point and stick with it.
- Same operating state (as close as practical): note speed/load/recipe when it’s different. If you don’t, you’ll blame the machine for production variability.
Safety and access are constraints, not excuses
Guards, hot surfaces, rotating couplings, elevated points, and permit requirements are real. A good program designs around them:
- Use safe access points and permanent targets where needed.
- Don’t normalize risky behavior to “get the reading.”
- Accept that some points require a planned window—and treat those as higher-value data events.
“What’s Good?”
Good deliverables
- Asset list + point map: what was measured, where, and how.
- Baseline + trend: trend plots for key points that show direction, not just a one-time snapshot.
- Exception report: assets with meaningful change, likely fault type, and recommended next action.
- Notes that matter: operating state, recent maintenance, and any access limitations that affect interpretation.
Valid references (so the data means something)
Vibration values must be compared to a valid reference:
- Asset baseline: establish “normal” for this machine at this speed/load and this measurement point.
- Like-for-like comparison: identical machines can be compared, but don’t assume they’re identical in mounting, load, or process conditions.
- Change over time: a stable machine with a clear upward trend is more concerning than a machine that’s always been “loud” but stable.
Severity that matches maintenance decisions
Keep severity tied to action windows:
- Watch: slight increase; recheck next route; verify operating conditions were comparable.
- Plan: clear trend or identifiable fault developing; plan parts/tools and coordinate access.
- Schedule: strong fault indicators; schedule repair in the next available window before it becomes unplanned.
- Immediate: rapid change, extreme vibration, or signs pointing toward imminent failure or secondary damage.
Common pitfalls & false positives
- Inconsistent points: moving an inch can change the result on small bearings and thin structures.
- Bad mounting: a loose magnet or shaky probe can fake “high vibration.”
- Ignoring speed: if speed changes, the spectrum shifts. Without speed reference, diagnosis gets sloppy fast.
- Collecting data on unstable operation: cycling loads, cavitating pumps, or variable-speed transitions can produce messy spectra that aren’t comparable to steady-state baselines.
- Over-trusting a single alarm: one flagged reading should trigger a recheck or deeper test, not an automatic bearing swap.
- Too much scope, too soon: huge routes collapse under real staffing. Start with critical assets and expand only when the plant is actually acting on findings.
What Am I Supposed To Do With This?
The value of vibration analysis is turning “we saw something” into planned, executable work that fits the plant’s constraints.
Realistic plant vignette
It’s Wednesday afternoon. Production is behind. You finally get the pump room door opened, but the line is running a different product and the pump is at a different speed than last month. The vibration number is higher. Is the pump worse—or is the process different? Good notes and a quick recheck at a comparable operating condition can prevent you from chasing ghosts (or missing a real trend).
Examples of practical work-order actions
- Suspected misalignment: “Pump P-14/motor set shows elevated axial vibration and 2× running speed component vs. baseline. Inspect coupling condition and base/foot integrity. Schedule laser alignment check during next window; correct soft foot if found.”
- Suspected looseness: “Fan F-7 shows increasing overall velocity and harmonics vs. baseline. Inspect hold-downs, base cracks, and guard contact. Verify torque on mounting hardware to spec; recheck vibration after correction.”
- Bearing defect developing: “Motor M-33 DE bearing shows rising high-frequency vibration and bearing fault indicators vs. baseline. Verify lubrication condition and contamination risk. Plan bearing replacement in next outage if trend continues; recheck in 2 weeks or sooner if critical.”
- Process-driven issue (pump): “Pump P-22 vibration increase aligns with cavitation-like broadband pattern during current operating condition. Coordinate with operations to verify suction conditions (valve position, strainer condition, NPSH margin). Inspect suction restrictions; recheck after correction.”
Short checklist (do-able)
- Confirm safe access and keep guards/LOTO rules intact.
- Record operating state: speed, load, and anything “different than normal.”
- Use the same measurement point and mounting method every time.
- Trend overall values, but use spectra to identify likely fault type.
- If a reading is surprising, recheck before launching a major repair.
- Write actions with clear scope: what to inspect, what to verify, and when to recheck.
“Just The FAQs”
Do we need vibration on every rotating asset?
No. Start with critical assets, chronic problem machines, and equipment where failure has real production or safety consequences. The goal is fewer surprises, not perfect coverage.
Is route-based vibration “good enough” compared to online sensors?
Often, yes—especially early on. Online monitoring can be great for critical assets, but it adds complexity. Route-based data can deliver strong results if collected consistently and acted on.
What’s the most common reason vibration programs fail?
Too much data and not enough action. If findings don’t turn into planned work, the route gets skipped, and the program quietly dies.
How often should we collect vibration data?
Monthly is common for many assets. Critical or fast-degrading assets may need more frequent checks. Stable, low-criticality equipment can be less frequent. The right interval is the one you can sustain and still act on.
Should we confirm vibration findings with other methods?
Often, yes. Ultrasound can help with lubrication/bearing triage, thermography can highlight heat from friction or electrical issues, and a good inspection can catch looseness, soft foot, or coupling problems. Use the tool that matches the decision you need to make.