RebotaREBOTA/Works Search tools, standards, templates… Ctrl K Rebota →
Calculators Standards Templates Checklists Estimators Learn Community Search Rebota (business platform) →
Manufacturing Intelligence · Production

OEE Calculator

Overall Equipment Effectiveness breaks total loss into three independent categories — Availability, Performance, and Quality — so you know exactly which one to fix first, not just that output is low.

Project Snapshot
This sets the context for every benchmark, health score and recommendation below — a residential project in Maharashtra and a government road project in Bihar do not share the same "normal."
Engineering Calculator
Your inputs are remembered on this device only — never sent to Rebota.
Engineering Analysis
Current Cost / Exposure
₹0
Industry Average
₹0
Recoverable Amount
₹0
WhatsApp LinkedIn
Professional Practices

Why Contractors Lose Money Here

OEE (Overall Equipment Effectiveness) is the standard manufacturing metric — defined in ISO 22400-2 and originating from the SEMI E10/E79 equipment-performance standards — that separates total production loss into three independent, multiplicative components: Availability (is the machine running when it should be?), Performance (is it running at full speed?), and Quality (is it producing good parts?). Most plants track output volume or downtime hours separately, which hides which of the three is actually driving the loss. Because the three multiply together rather than add, a plant running at 90% on all three components is not at 90% OEE — it is at 72.9%, because each stage compounds against what the previous stage already lost. This is why isolated fixes ("reduce downtime by 10%") often produce disappointing OEE gains if Performance or Quality were the real constraint.

Real Site Example

A line runs an 8-hour (480 min) shift with 60 min planned downtime (breaks), leaving 420 min Planned Production Time. 45 min of unplanned downtime (a jam and a short material wait) leaves 375 min Run Time — Availability = 375/420 = 89.3%. The line produces 700 units against an ideal cycle time of 30 sec/unit, meaning 350 min of theoretical run time was achieved in 375 actual minutes — Performance = 93.3%. Of those 700 units, 25 were rejected — Quality = 96.4%. OEE = 89.3% x 93.3% x 96.4% = 80.3%, not the 93%+ any single component might suggest in isolation.

Professional Best Practices

Well-run manufacturing operations track all three OEE components separately per shift, not just a blended OEE percentage — because the fix for low Availability (maintenance scheduling, changeover procedure) is completely different from the fix for low Performance (speed loss, micro-stops) or low Quality (setup, tooling wear, material issues). The Ideal Cycle Time reference is reviewed periodically against actual demonstrated best-case performance, since a stale (too conservative) reference silently inflates the calculated Performance score.

Engineering Checklist

  • Log unplanned downtime by cause and duration, not just total minutes — event count and average stop length point to different root causes
  • Verify the Ideal Cycle Time against the fastest reliably-demonstrated rate for the current product/tooling — not a stale spec-sheet figure
  • Track rejects by timing (shift start vs. mid-shift vs. after changeover) to identify setup vs. wear vs. material root causes
  • Calculate OEE per shift, not just per week or month — a monthly average hides which specific shift or changeover is driving the loss
  • Never treat OEE as one number to improve directly — always decompose to Availability, Performance, and Quality first
  • Recheck the multiplicative relationship (A x P x Q = OEE) whenever any component is updated, to catch data entry errors

Government & Standards References

  • ISO 22400-2:2014 — Automation systems and integration: Key performance indicators for manufacturing operations management
  • SEMI E10 — Specification for Definition and Measurement of Equipment Reliability, Availability, and Maintainability
  • SEMI E79 — Specification for Definition and Measurement of Equipment Productivity

How Experienced Contractors Handle This

Manufacturing engineering teams review the three OEE components separately every shift, investigate the single largest loss category first (rather than spreading effort evenly across all three), and re-verify the Ideal Cycle Time reference whenever tooling, material, or product specification changes — since Performance is the component most vulnerable to a stale reference value silently distorting every subsequent calculation.

Common Mistakes
Patterns we see repeatedly across Indian construction sites — worth checking against your own process.
1
Tracking only total downtime hours or output volume, never the full three-component decomposition
Without separating Availability, Performance, and Quality, it is impossible to tell whether a low output shift was caused by breakdowns, slow running, or scrap — leading to fixes aimed at the wrong root cause.
2
Using a supplier spec-sheet cycle time as the Ideal Cycle Time without verifying it against actual demonstrated performance
If the line has ever run faster than the spec sheet claims, every Performance calculation using that stale reference will show impossible values above 100%, silently signalling a data problem rather than a real production trend.
3
Averaging OEE across a week or month instead of calculating it per shift
A single catastrophic shift (major breakdown, bad material batch) gets diluted into a monthly average that looks only moderately concerning, hiding the specific event that needs investigation.
4
Treating OEE as an additive metric ("we're only 10% below target, so we need 10% more output")
Because Availability, Performance, and Quality multiply rather than add, a 10-percentage-point OEE gap can require a much larger single-component improvement than intuition suggests — the multiplicative math must be worked through explicitly.
5
Not distinguishing between planned and unplanned downtime
Scheduled breaks and planned maintenance are not Availability losses — counting them as downtime understates Availability and misdirects improvement effort toward time that was never meant to be productive.
6
Comparing calculated OEE against an unverified "industry average" figure
Published "world class OEE = 85%" figures come from specific manufacturing contexts (discrete high-volume production) and may not be the right comparison for every process type — using it as a hard target without context can set an unrealistic or irrelevant goal.
7
Ignoring reject/rework units in the Total Count used for Performance calculation
Performance is calculated against Total Count (including rejects) specifically because the machine spent real time producing those units — excluding rejects from Total Count would understate the actual Performance loss and double-penalize Quality for the same units.
How Rebota Automates This

Rebota's Equipment Monitoring and Daily Site Logs modules can capture shift-level run time, downtime events with cause codes, and production counts directly from the floor — feeding the same Availability/Performance/Quality decomposition used here automatically, shift over shift, without manual data entry at month-end.

Equipment Monitoring
Daily Site Logs
QC Checklists
Reports
AI Alerts
Estimated Loss (This Shift)
₹8,500
Estimated Recovery at World-Class OEE
₹5,200
Annual Cost
₹36,000
Est. ROI
6X
Start Free Trial — See This Inside Rebota →
Related Resources
Frequently Asked Questions
What is OEE and how is it calculated?
OEE (Overall Equipment Effectiveness) = Availability × Performance × Quality. Availability = Run Time ÷ Planned Production Time. Performance = (Ideal Cycle Time × Total Count) ÷ Run Time. Quality = Good Count ÷ Total Count. All three are ratios between 0 and 1 (0–100%), and they multiply together — they do not average or add.
Why is OEE multiplicative rather than additive?
Each stage of production depends on the one before it: you can only run at full speed (Performance) during the time the machine was actually available (Availability), and you can only count good output (Quality) from the units that were actually produced during that available, running time. This chained dependency is why the three factors multiply — a 90% score on all three compounds to 72.9%, not 90%.
What is a good OEE score?
This calculator does not display a Rebota-verified "industry average" because no such sourced benchmark exists in our database for OEE. The widely-published reference figure from TPM (Total Productive Maintenance) and SEMI E10/E79 literature is 85% as "world class" for discrete manufacturing — shown here as an external published reference, clearly separate from any Rebota benchmark claim. Your own internal target, if you set one, is shown separately and takes priority in the comparison.
Why did my Performance score come out above 100%?
This happens when the actual achieved run rate was faster than the Ideal Cycle Time you entered. It almost always means the Ideal Cycle Time reference is stale or overly conservative — not that the machine genuinely exceeded its own physical limit. The calculator flags this explicitly as a data-quality finding rather than silently capping or hiding the number.
What counts as planned vs. unplanned downtime?
Planned downtime is time deliberately excluded from the production schedule — breaks, shift changes, scheduled preventive maintenance. It is subtracted before calculating Availability and is not treated as a loss. Unplanned downtime is any stoppage during scheduled production time — breakdowns, changeovers, material waits, waiting for an operator — and this directly reduces the Availability score.
How is the rupee cost of OEE loss calculated?
Each of the three loss categories (Availability, Performance, Quality) is converted to an equivalent number of lost minutes, then multiplied by your entered machine+labour hourly rate. This cost figure does not affect the OEE percentage itself — it exists purely to translate the abstract percentage into a concrete shift-level rupee impact.
Can OEE be calculated for a partial or very short shift?
Yes — the formulas work for any time period as long as Planned Production Time is greater than zero. For very short periods, treat the result with more caution: a single unusual event (one long stoppage, one bad batch) has a much larger proportional effect on a short shift's OEE than it would over a full week of shifts.
Should I track OEE per machine, per line, or per plant?
Per machine or per bottleneck resource is the standard practice, since averaging OEE across multiple machines with different constraints (some Availability-limited, some Quality-limited) hides exactly the information OEE is designed to surface. Plant-level OEE is useful as a summary trend but should never replace machine-level tracking for root-cause work.
Still tracking this on Excel and WhatsApp?See how Rebota monitors this automatically across every live project.
See How Rebota Monitors This Automatically
Save & Access Anywhere
Save your favorite tools & resources
Smart Search (Ctrl+K)
Find what you need in seconds
Community Support
Ask questions & get real answers
Regularly Updated
New tools, templates & guides added