OEE — Overall Equipment Effectiveness

Getting a trustworthy OEE number is less about the formula and more about the discipline behind it — and that's where most plants either win or lose the metric.

How AssetAI Computes It

Inside the Downtime Cost, OEE & Analytics module, AssetAI calculates full OEE — Availability × Performance × Quality — for every asset that has a production log against it, then sorts the asset list worst-first so the biggest loss surfaces at the top rather than getting buried in a spreadsheet. The calculation sits inside the same rolling window used across the platform — 30, 90, 180 or 365 days, defaulting to 90 — alongside availability, MTTR, MTBF, and PM compliance, so you can flip between windows to see whether a low OEE score is a one-off bad week or a persistent pattern. On the same screen, a downtime cost Pareto ranks the top 8 assets by downtime cost per hour × downtime hours, which lets you cross-check whether a machine with poor OEE is also the one bleeding the most rupees — a quick way to decide where to send a technician first. This is not a live dial ticking on a dashboard; it's a computed report over a historical window, which suits a review meeting or a shift-handover discussion better than a continuous monitor.

Why the Number Is Only as Good as Your Logs

OEE in AssetAI is not pulled automatically from PLCs, SCADA or sensors. Availability, performance and quality figures depend entirely on production data and downtime hours entered against the asset — and downtime hours in turn come from breakdown and corrective work orders, which in AssetAI cannot be closed without a recorded failure cause and remedy. That gate exists precisely so the availability half of the OEE equation isn't guesswork. If a plant hasn't gotten into the habit of closing work orders properly, or isn't logging production runs at all, the OEE report will reflect that gap rather than paper over it: assets with no production log are skipped from the ranking entirely, with no default or estimated score shown. In practice this means OEE is a good fit for teams that are already disciplined about logging production and closing work orders with cause and remedy — for a broader look at that discipline, see what a CMMS actually enforces. It is not a fit for a plant expecting automatic, sensor-fed real-time OEE without doing that groundwork first.

Where OEE Fits Alongside Other Practices

OEE as a metric predates any software — it comes out of the Total Productive Maintenance tradition, and the formula itself is documented in detail on Wikipedia's OEE page. AssetAI doesn't benchmark your plant against an industry "world-class" figure or flag thresholds — any such number you see elsewhere is generic context, not something the product asserts about your plant. What it does give you is a consistent, per-asset, worst-first view you can act on repeatedly. To see how OEE sits alongside the rest of the platform's rolling KPIs and work-order discipline, browse all features, check relevant industries, or book a 30-minute demo on your own production data rather than a slide deck.

OEE measures how much of a machine's planned production time was truly productive — a concept formalised under Total Productive Maintenance and widely referenced as Overall Equipment Effectiveness. This page looks at where the metric fits into day-to-day plant practice, and where it deliberately stops.

What the Ranking Does Not Cover

The worst-first asset list in AssetAI is a per-asset view over a chosen date window — it is not a shift-level, product-level or line-level breakdown. If two shifts run the same machine very differently, that difference is folded into a single number for the window rather than split out. Similarly, an asset with no production log entered against it is skipped entirely from the ranking — there is no default or estimated OEE shown in its place, so a gap in the list usually means a gap in logging discipline, not a well-performing machine. Plants used to a real-time OEE dial on the shop floor should also note this is a computed report, refreshed over 30/90/180/365-day windows, not a continuously streaming figure — better suited to a weekly review or shift-handover than a live wall display.

Using the Metric Well in an Indian Plant Context

Most Indian manufacturing plants running AssetAI already carry a mix of legacy machines and newer lines, and OEE tends to be most useful as a triage tool rather than a scorecard for its own sake:

• Start with the worst-first list, not an average — a single badly performing asset can distort a plant-wide OEE figure and hide the fact that most of the fleet is running fine.
• Cross-check a low-OEE asset against the downtime cost Pareto on the same screen — a machine with poor OEE but low downtime cost may be a lower priority than a machine with moderate OEE but heavy rupee losses.
• Toggle the rolling window before acting — a bad 30-day OEE could be a one-off breakdown; a bad 180-day trend usually points to a chronic issue worth a root-cause investigation.
• Treat OEE as a symptom, not a diagnosis — the number tells you which asset to look at, not why it's underperforming; that answer sits in the cause/remedy fields on the underlying work orders.

Note that AssetAI does not benchmark your plant's OEE against an industry "world-class" threshold or flag targets automatically — any such figure quoted elsewhere is generic industry context, not something the product computes or displays for you. For sector-specific context on how Indian manufacturing is evolving, IBEF's industry data is a reasonable independent reference point.

Before You Rely on the Number

Because OEE here is built entirely from what's logged, it's worth confirming the basics are in place before treating the metric as authoritative:

• Every relevant asset has a production log being entered consistently, not just the machines someone remembers to update.
• Breakdown and corrective work orders are actually being closed with a failure cause and remedy — this is the same discipline described on what a CMMS does, and it underpins the availability figure inside OEE.
• Someone owns the review — OEE surfacing a problem asset is only useful if a plant manager or engineer acts on it in the next maintenance cycle.

If your plant is still building this logging discipline, it's worth exploring the broader features available in AssetAI, seeing how other plants in your sector use it via industries and use cases, or booking a walkthrough via contact to see the OEE screen against your own asset list before rolling it out plant-wide.