OEE & efficiency tracking: Availability × Performance × Quality

A plant can hit its output target and still be quietly bleeding capacity. The machine ran all shift — but it broke down twice, ran ten per cent slow after lunch, and two in every hundred pieces went to the reject bin. None of that shows up in a single "we made 4,000 pieces" number. It shows up when you measure the shift the way OEE does: not as one figure, but as three — how much the machine ran, how fast, and how many pieces were good — multiplied together into one honest score.

This guide is for planners and production managers who want the plan to be measured, not just made. It covers plan-vs-actual, the difference between utilization and efficiency, OEE and its three factors with a worked example, and how Fast Planning Software captures it all from the floor. Every number below is illustrative. For the wider picture — how the plan is built in the first place — start with the pillar guide, what is production planning software?

1. Why an unmeasured plan never improves

The point of measuring production is not a wall of dashboards for their own sake. It is that a plan built on the same optimistic numbers every cycle repeats the same misses. If a job is planned for its standard cycle time and always takes longer, but nobody books what actually happened, the next plan assumes the standard again — and is late again, for the same invisible reason.

Three habits separate a plant that measures from one that guesses:

• It captures actuals at source. Actual start and end times, setting and cycle times, stoppages and OK-versus-not-OK quantity are recorded on the floor as work happens — not reconstructed from memory at month-end.
• It compares actual to plan. Every job's real time and quantity are set against what the plan assumed, so the gap — and its cause — is visible.
• It feeds the gap back. The times the floor actually hits become the standards the next plan uses, so plans get steadily more realistic instead of staying hopeful.

OEE, utilization and efficiency are simply the lenses that turn those raw bookings into decisions. See Plan vs Actual & OEE.

2. Plan vs actual — the honesty check

Plan versus actual is the simplest and most important measure, and everything else builds on it. It compares what the plan assumed — planned quantity, standard time, promised completion date — against what the floor actually produced and when.

• Quantity — planned pieces against good pieces produced, so short output is visible and attributable.
• Time — standard time against actual time booked, so a job that ran over its standard cycle shows the overrun and where it occurred.
• Date — promised completion against actual completion, so slippage is caught as it happens, not at delivery.

The value is not the gap itself but what it teaches. A job that consistently runs 15% over its standard time is telling you the standard is wrong, the tooling is worn, or the setup is longer than assumed — and each of those is a fixable cause once the plan-vs-actual report makes it visible. Feeding that back is what turns planning from a repeated guess into a system that learns.

3. Utilization vs efficiency — two different questions

These two get used interchangeably and mean quite different things. Confusing them hides problems; separating them finds them.

A worked contrast makes it concrete (illustrative): a machine that produces for 7 of 8 available hours is ~88% utilized — but if in those 7 hours it made only what the standard says 6 hours should produce, it is roughly 86% efficient. High utilization hid a real efficiency loss. The reverse also happens: a machine that runs fast when it runs but sits idle half the shift is efficient yet badly under-utilized. You need both numbers to know which lever to pull — fill the idle time, or fix the slow running.

4. OEE and its three factors

OEE — Overall Equipment Effectiveness — folds those ideas, plus quality, into one strict number. It is the product of three factors, each a percentage:

The multiplication is what makes OEE honest. Because the factors multiply rather than average, a machine that is strong on two and weak on one still scores low — three factors of 90% give an OEE of only about 73%, not 90%. That strictness is the point: it stops a plant hiding a reject problem behind good uptime, and it tells you exactly which factor to attack first — the lowest one.

5. A worked OEE example

Take one machine over one shift. All figures illustrative, chosen to show the arithmetic:

Read it as a diagnosis, not a grade. Here the lowest factor is Availability at 90% — so the biggest single gain comes from cutting the breakdown and setup time, not from chasing the last two per cent of quality. Change the numbers and the priority changes: a machine at 98% availability but 85% quality has a reject problem to solve first. That is the working value of OEE — it points, every shift, at the factor with the most to give back.

6. Where effort leaks — rework and idle time

Two losses sit behind the OEE factors and deserve their own attention, because they are where a shift's effort quietly drains away.

Rework is the hidden tax behind the Quality factor. A reworked piece is counted, machined, inspected — and then done again. It consumes capacity twice while adding output once, so a rising rework rate pulls Quality down and steals Availability from the next job. Tracking rework by work centre and operation shows where it concentrates, so the recurring cause can be fixed rather than the symptom repeatedly salvaged.

Idle time is the loss behind Availability — a machine that could be running but is not, because it is waiting for material, a setter, a tool, or the next job. Separating idle time from genuine breakdown matters: breakdown is a maintenance problem, but idle time is usually a planning and scheduling problem — the very thing a good plan and a levelled load exist to prevent. Booking idle time and its reason turns "the machine was down" into an actionable list of causes.

Both are captured the same way the OEE factors are — as reasoned bookings on the floor — and both feed the efficiency and OEE dashboards, alongside utilization and plan-vs-actual.

7. How barcode time booking feeds the metrics — and the next plan

None of these measures is worth anything if the data behind it is guessed. The reason OEE, utilization and efficiency are credible is that every input is captured at source, by scanning barcodes on the floor as work happens.

The loop closes at the end. Because the floor books the times it actually hit, those times can update the standards the next plan uses — so machine loading is calculated from real cycle and setting times, the schedule is built on durations the floor can meet, and the plan-vs-actual gap narrows cycle after cycle. Progress is captured through barcode and IoT machine-data capture, and Dhruv AI can summarise OEE and plan-vs-actual and cluster recurring breakdown and idle-cause remarks into named themes — so the measurement doesn't just report, it points at what to fix.

8. How Fast Planning Software implements OEE and efficiency

Fast Planning Software is the MRP and production-planning product of the Fast Suite, built in Pune by Improsys under the Fast Technology brand, deployable cloud or on-premise for manufacturers across India and worldwide. It captures and reports the whole picture with real, named screens:

9. Frequently asked questions