OEE (overall equipment effectiveness) is an efficiency metric that shows how much of a machine's or line's planned production time is used to make good product at full speed. It is calculated as the product of three ratios: availability, performance and quality. This guide is for production, maintenance and continuous improvement teams that want to define OEE correctly, measure it with reliable data and turn the measurement into real improvement.
The value of OEE is not in a single number but in making the losses behind that number visible. A poorly defined OEE can look high and teach nothing; a well-defined OEE tells the team which loss to focus on first.
The three components of OEE
OEE answers three questions: Did the machine run when it was supposed to? When it ran, did it run at the speed it should? How much of what it made was good the first time?
- Availability = run time / planned production time. Breakdowns, setups and material waits reduce this ratio.
- Performance = (ideal cycle time × total count) / run time. Minor stops and slow running reduce this ratio.
- Quality = good count / total count. Scrap, rework and startup rejects reduce this ratio.
- OEE = availability × performance × quality. The same result can also be calculated as (good count × ideal cycle time) / planned production time.
The second formula is a good cross-check: if the OEE you get by multiplying the three ratios doesn't match the OEE you get directly from good count and ideal cycle time, one of your inputs is inconsistent.
OEE in the context of ISO 22400
ISO 22400 is an international standard series that defines key performance indicators (KPIs) for manufacturing operations management. Part two of the series (ISO 22400-2) defines many KPIs, including OEE, together with their formulas, time models and context of use. Terms in the standard can differ slightly from common shop floor names; for example, the performance ratio is called “effectiveness”.
The practical benefit of the standard is a shared language. If different sites, software or teams calculate OEE with the same time model, results become comparable. When you build your own definition, use the ISO 22400 time model as a reference and document any deviations in writing. For exact definitions, refer to the current text of the standard.
Planned production time and ideal cycle time
Most OEE calculation errors come from two definitions: what planned production time includes and how ideal cycle time is set. Make these two definitions once, in writing and approved, and apply them with the same rule on every line.
- Fully productive timeGood parts only, at ideal speed
- Net run timeSpeed losses removed
- Run timeDowntime losses removed
- Planned production timePlanned stops removed
- Total calendar timeAll time in shifts and calendar
Planned production time
- Subtract only genuinely planned stops from shift time: meal and tea breaks, planned meetings, time not in the production plan.
- Decide whether planned maintenance counts as a planned stop or a loss, and apply the decision the same way on every line.
- Track time with no orders outside OEE, in a separate “no orders” category; it is a capacity utilisation question, not an equipment loss.
- Don't treat setup and changeover time as planned stops; they are losses you can improve.
Ideal cycle time
- Ideal cycle time is the fastest sustainable cycle time the equipment is designed for or has proven for that product.
- Use the machine builder's nameplate speed, the best proven actual speed or an engineering study as the source, and write down which one you chose.
- Don't use average or “usual” speed as ideal cycle time; it hides performance losses.
- Define ideal cycle time per product; different products on the same line can run at different speeds.
- On lines with a bottleneck machine, line speed is set by the bottleneck machine's ideal speed.
Downtime reason code tree
A downtime reason code tree is a classification that records, with standard codes, which loss type and which root cause group each stop belongs to. A good code tree has two or three levels, is short enough for an operator to choose from in seconds and doesn't allow frequent use of an “other” option.
| Level 1 (loss type) | Level 2 (group) | Level 3 (example reason) |
|---|---|---|
| Breakdown | Mechanical | Bearing, belt, jam |
| Breakdown | Electrical / automation | Sensor, drive, PLC fault |
| Setup and adjustment | Changeover | Mould change, cleaning |
| Setup and adjustment | Adjustment | First article approval, parameter tuning |
| Waiting | Material | No raw material, WIP late |
| Waiting | Staff | No operator, waiting for approval |
| Quality | Process deviation | Out of tolerance, readjustment |
| Planned stop | Break / meeting | Meal, shift handover |
Data collection: manual or automatic?
OEE data can be collected in different ways, from paper forms to PLC signals. The right method depends on the number of lines, how machines can be connected and the level of detail you need. In most plants the best results come from a mixed approach, where machine state is collected automatically and the operator selects the downtime reason.
- L1Paper formWritten by hand at shift end
- L2Operator terminalStops and counts entered on screen
- L3Machine signalRun / stop state and count automatic
- L4Connected and analyticalSignal, reason code and analysis together
- Quick to start
- Low initial cost
- Misses minor stops
- Rounded durations
- Second-level durations
- Catches minor stops
- Needs connection and setup
- Still needs reason codes
- PLC or sensor: run / stop state and counter signal are collected automatically; standard protocols such as OPC UA make integration easier.
- Operator terminal: downtime reason, scrap count and work order details are entered on a screen at the line.
- Quality data: good and defective counts come from the inspection point or the quality system.
- Planning data: work order, product and ideal cycle time come from the production planning system.
In OREL MRP, work orders, machine state and downtime reasons come together in the same record, so OEE can be broken down by product, shift and work order. Breakdown stops can be passed to OREL IMS as maintenance work orders.
When moving to automatic data collection, don't try to connect every line at once. Pick the bottleneck or most critical line first, compare the machine signal with manually kept records over a few shifts, and settle settings such as the counter, run / stop state and the minor stop threshold. A system scaled out without this validation produces bad data faster and in greater volume. Turn what you learn on the first line into a short installation standard and apply the same standard to the next lines.
The six big losses
In the total productive maintenance (TPM) approach, losses are grouped into six main categories. Each one falls under one OEE component; this mapping is also a good starting point for the level 1 structure of your downtime reason code tree.
| Loss | OEE component | Typical example |
|---|---|---|
| Breakdowns | Availability | Equipment failure, unplanned maintenance |
| Setups and adjustments | Availability | Changeover, warm-up, adjustment |
| Minor stops and idling | Performance | Jams, sensor trips |
| Reduced speed | Performance | Running below ideal speed |
| Process defects | Quality | Scrap, rework |
| Startup rejects | Quality | Scrap while settling in |
Worked example
The numbers below are made-up example values used only to show the calculation method; they are not results from any plant or ORELSIS project.
| Item | Example value | Note |
|---|---|---|
| Shift length | 480 min | One shift |
| Planned stops | 30 min | Breaks |
| Planned production time | 450 min | 480 − 30 |
| Unplanned downtime | 50 min | Breakdowns and setup |
| Run time | 400 min | 450 − 50 |
| Ideal cycle time | 0.5 min/part | Per product |
| Total count | 700 parts | Counter |
| Good count | 665 parts | First time right |
- 1.Availability = 400 / 450 ≈ 88.9%
- 2.Performance = (0.5 × 700) / 400 = 350 / 400 = 87.5%
- 3.Quality = 665 / 700 = 95.0%
- 4.OEE = 0.889 × 0.875 × 0.950 ≈ 73.9%
- 5.Cross-check: (665 × 0.5) / 450 = 332.5 / 450 ≈ 73.9%
In this example the largest losses sit on the availability and performance side. The next step is to break down the 50 minutes of unplanned downtime and the speed loss within run time by downtime reason code. OEE itself doesn't give you an improvement plan; breaking down the losses does.
Dashboards and shift reviews
An OEE dashboard lets everyone, from the team at the line to management, look at the same data. But each level asks a different question: the operator asks “what is happening right now?”, the shift supervisor asks “what did we lose most this shift?”, and management asks “which loss group should we invest in?”
- Line board: live machine state, shift target versus actual count, active stop and its duration.
- Shift summary: the three components separately, the top five downtime reasons, scrap count.
- Weekly view: loss Pareto, trend chart, open actions.
- Management view: trends by line and site, distribution of loss groups, status of improvement projects.
- 01Review the last shift
Read the three OEE components and the gap to target in a few minutes; don't settle for a single OEE number.
- 02Pick the biggest losses
Discuss the top two or three items in the downtime Pareto; confirm that each one is actually coded correctly.
- 03Assign actions
Set an owner, a next step and a date for each loss; keep actions in a shared list.
- 04Check open actions
Ask for the status of actions from previous meetings; escalate the ones that aren't closing.
- 05Keep it short
Hold the meeting at the board, standing up and with a fixed duration; leave detailed analysis for a separate session.
The improvement loop
OEE measurement creates value when it is tied to an improvement loop such as PDCA (Plan, Do, Check, Act). The loop starts by measuring the loss and closes by making the improvement the new standard.
- 01MeasureRecord losses with their codes
- 02PrioritiseUse Pareto to pick the biggest loss
- 03Find the root cause5 Whys, fishbone
- 04ImproveSMED, autonomous maintenance, process tuning
- 05StandardiseUpdate instructions and checklists
- 01
- Pareto analysis: rank downtime reasons by duration; most of the loss is often concentrated in a small number of reasons.
- SMED (single-minute exchange of die): split setup steps into those that must happen while the machine is stopped and those that can happen while it runs, and move every step you can into the second group.
- Autonomous maintenance: give operators basic upkeep tasks such as cleaning, lubrication, tightening and visual checks with a standard checklist; the maintenance team focuses on more complex work.
- Minor stop analysis: frequent minor stops look trivial one by one but can add up to a large loss; count them with automatic data.
- Quality losses: link scrap and rework to product, parameters and shift and review them with the quality team.
Seeing planned maintenance and breakdown records alongside OEE data makes it easier to get to the root cause of breakdown losses. OREL IMS provides this link by keeping maintenance work orders and equipment history.
Common mistakes
Gaming the metric: if OEE becomes a bonus or penalty tool, teams code stops as planned stops, loosen ideal cycle times or record scrap later. The number goes up, the factory doesn't improve. Use OEE to evaluate losses, not people.
- Comparing lines unfairly: ranking the OEE of lines with different product mixes, automation levels and definitions side by side is misleading. Compare each line with its own history first.
- Looking at one number: the same OEE can come from very different loss profiles; always show the three components separately.
- Taking ideal cycle time from average speed: performance loss looks close to zero and the improvement opportunity disappears.
- Counting “no orders” time as a loss: it mixes up equipment effectiveness and capacity utilisation.
- Accepting the “other” code: if a significant share of stops is coded as “other”, the code tree or the training is inadequate.
- Measuring without acting: without regular meetings and action tracking, the dashboard stays just a screen.
Conclusion
When defined correctly and measured with reliable data, OEE is a simple tool that makes hidden losses in production visible. First write down the time model and ideal cycle time, then build the downtime reason code tree together with the shop floor, collect data automatically wherever possible and turn losses into actions every shift. Lasting results come not from the number itself but from a regular improvement loop built on the losses the number reveals.