ISO 20816 — Mechanical Vibration

What ISO 20816 covers

ISO 20816 sets out the general framework for evaluating machine vibration through measurements on rotating and reciprocating parts, replacing the older ISO 10816 series. It does not certify software — it certifies measurement practice — so the real question for a maintenance team is how vibration data gets captured, stored, and turned into a decision. That is the layer AssetAI is built to support.

Building a Vibration Monitoring Routine

Most plants that attempt vibration-based monitoring stall not because the physics is hard, but because the data collection habit breaks down within a few weeks. A workable routine typically includes:

• A defined reading schedule per asset — critical rotating equipment (motors, pumps, compressors) read more frequently than static assets.
• Consistent units and locations for each measurement point, so readings taken months apart are actually comparable.
• A named source for every reading — technician, sensor, or contractor — so anomalies can be traced back and questioned.
• Photo evidence attached to readings, useful both for audit trails and for catching transcription errors before they distort a trend line.

AssetAI's Meter Readings screen and public QR scan page are designed around exactly this kind of routine: a technician scans an asset, logs the vibration value against its unit and any note, and the system timestamps and stores it as part of that asset's permanent history — without needing a dedicated vibration analyst on staff.

What This Data Is Actually For

Logged vibration readings only earn their keep once they're used, not just archived. In practice, plants use the history AssetAI stores to:

• Compare against internal limits — plotting recent readings against a threshold set by engineering or OEM guidance.
• Spot drift over time — a slow upward trend across weeks is often more actionable than any single reading.
• Cross-reference with breakdown history — checking whether elevated vibration preceded past failures on the same asset class.
• Feed predictive maintenance planning — using the trend, not a single alarm, to schedule inspection or replacement before failure.

None of this requires AssetAI to interpret the physics itself. It does not perform automatic vibration analysis, does not evaluate readings against ISO 20816 severity zones, and does not connect directly to vibration sensors or handheld analyzers — those remain separate, deliberate decisions your engineering team makes. What AssetAI does is remove the friction around capturing, organizing, and retrieving that data reliably, including through photo OCR that auto-fills a reading when a technician photographs a meter face, cutting down manual entry errors at the point of capture.

Where This Fits in a Broader Strategy

Vibration monitoring rarely stands alone — it usually sits alongside other condition indicators as part of a wider reliability or TPM program. Plants that connect vibration trends to downtime and output metrics often find it easier to justify further investment in monitoring, particularly when tied back to OEE figures that leadership already tracks. If you're evaluating how vibration logging fits your specific line of business, the industries and use-cases pages outline how Indian manufacturers across different sectors structure this within AssetAI, and the standards hub covers how other ISO frameworks interact with day-to-day maintenance work.

What ISO 20816 help

ISO 20816 tells you how vibration severity should be judged; it says nothing about how that data should be stored, reviewed, or acted on across dozens of assets and shifts. That gap — between a single measurement and a usable maintenance record — is where AssetAI sits, and it is worth being precise about what the platform actually does in that gap versus what it leaves to instruments and people.

Where AssetAI Draws the Line

AssetAI logs, timestamps, and compares vibration readings against limits you define — it does not take the measurement itself. That distinction matters for procurement and audit conversations:

• No automatic sensing. Someone (a technician, a contractor, or a fixed sensor feeding a value in) still has to produce the reading. AssetAI does not integrate with specific vibration measurement devices, so any instrument — handheld probe, fixed accelerometer, or a simple app — can feed the system as long as a person or process enters the value.
• No evaluation engine. AssetAI does not interpret waveform or spectral data or issue an ISO 20816 zone classification. What it does is hold the threshold you set, flag readings that cross it, and keep the trend line intact.
• No certification claim. Nothing on this page or in the product should be read as AssetAI certifying compliance with ISO 20816. It supports the record-keeping practices that a compliance-minded program depends on.

Being clear about this upfront saves a plant from discovering it during an audit — the standard certifies measurement practice, not software, and AssetAI's role is to make that practice easier to sustain.

Why This Matters for Indian Manufacturing Plants

Many mid-sized Indian manufacturing plants run critical rotating equipment — compressors, motors, pumps — without a dedicated vibration analyst on staff, and readings often get taken by whichever technician is on shift that week. As the manufacturing sector referenced in IBEF's industry data continues to scale up capacity, the gap between "we occasionally check vibration" and "we have a defensible history of vibration data" becomes a real operational risk, not just a paperwork one.

• A named source on every reading means a plant manager can trace an anomaly back to a specific technician, sensor, or contractor visit.
• Photo attachments catch the common failure mode of a correct reading typed incorrectly, before it distorts months of trend data.
• A shared record across shifts means the person reading a gauge on Monday and the person reviewing the trend on Friday are looking at the same data set — which matters more in multi-shift Indian plants than in single-shift operations.

These are the mechanics that make vibration monitoring survive past the first few weeks, which is typically where it breaks down.

Getting Vibration Monitoring Running

Adopting ISO 20816-aligned practices inside AssetAI does not require a separate rollout project. It fits into the same asset and PM setup covered across AssetAI's features:

• List the rotating assets you consider critical and set a reading frequency for each.
• Define the vibration limits you want flagged, in whatever units your instruments already report.
• Start capturing readings through the QR scan page or Meter Readings screen, using photo capture where a technician is not confident transcribing values by hand.
• Review flagged readings during the same cycle you already use for PM plan reviews, rather than as a separate task.

If you want to see how this sits alongside the rest of an asset register and PM workflow, book a demo or browse pricing to find the plan that matches your asset count.