Three factors, three different problems.

Each OEE factor has its own cause, owner and fix — and the product of the three conceals all of them. What a poor score in each actually means.

Three separate diagnosticsISO 22400-2 termsSetup is not downtimePattern, not product
OEE SPLIT · ONE MACHINE, ONE WEEKEXAMPLE
Availability
Performance
Quality
OEE56.5%

Low A, high P, high Q: it stops a lot but runs well when running. Look at changeovers, breakdowns, materials and manning, not feeds and speeds.

IllustrativeREAD THE PATTERN, NOT THE PRODUCT
Key takeaways
  1. Availability, performance and quality are three separate diagnostics with different causes, owners and fixes; the OEE product conceals which one you have.
  2. Performance is only as good as the ideal cycle time behind it, and a quality figure of exactly 100% usually means rejections are not being captured.
  3. Low availability means stops, low performance means slow running or micro-stops, and low quality with high A and P means scrap produced efficiently.

The three OEE factors are usually presented as parts of one calculation. They are better understood as three separate diagnostics that happen to be multiplied together — because each has a different cause, a different owner and a different fix, and the product conceals all three.

This article takes each in turn: what it measures, what corrupts it, and what a poor score actually means.

Availability — did it run?

ISO: actual production time ÷ planned production time. MachineWise variant: machine on-time ÷ reporting time.

Availability is the factor most plants find easiest to accept and most often compute wrongly, for one reason: the boundary between planned and unplanned. Scheduled breaks, planned maintenance and a shift you chose not to run are not availability losses. Setup is the contested case — a machine being changed over is not broken, and treating it as downtime produces a figure the shop floor rejects on sight.

A poor availability score means the machine is stopping. The fix lives with maintenance, scheduling and materials, and the diagnosis is a Pareto of stop reasons rather than anything about the machine's speed. If availability is your weak factor, cycle times and tooling are not your problem this month.

Performance — did it run fast enough?

ISO Effectiveness: (produced quantity × ideal cycle time) ÷ actual production time. MachineWise variant: productive time ÷ machine on-time, a time-in-cut proxy.

Performance is the factor most often meaningless, because it depends entirely on the ideal cycle time — and on most Indian job-shop floors that standard is absent, stale or was optimistic when it was set. An ISO Effectiveness figure computed from a bad standard is precise and worthless, and it is frequently the figure quoted because it tends to look flattering.

A poor performance score means the machine is running but not producing at rate. Causes divide into speed losses — conservative feeds and speeds, worn tooling, material variation — and small stops too brief to have been classified as downtime. The two have different owners, which is why short-stop detection matters: without it, micro-stops silently become a performance problem and are investigated as a speed problem.

Quality — was it any good?

ISO: good quantity ÷ produced quantity. The MachineWise variant is identical, because there is nothing to improve on here.

Quality is the simplest factor and the one most often reported as exactly 100%, which should be read as a warning rather than an achievement. A machine control counts cycles, not acceptable components. Unless rejections are captured and subtracted, Quality reads perfect and Performance is flattered by the time spent producing scrap.

A poor quality score is the most expensive of the three, because a rejected part consumed availability, performance, material and labour before being discarded. It is also the factor where the first rework pass should be decided explicitly: a component reworked to acceptance is not a good part first time, and whether you count it as one changes both the number and the behaviour it encourages.

Reading the three together

PatternWhat it indicatesWhere to look
Low A, high P, high QThe machine stops a lot but runs well when runningChangeovers, breakdowns, material and manning
High A, low P, high QThe machine runs almost continuously but slowlyFeeds and speeds, tooling, micro-stops, or a wrong standard
High A, high P, low QProducing scrap efficiently — the most costly patternProcess capability, tool condition, incoming material
Low A, low PUsually one cause presenting twiceInvestigate availability first; performance often recovers with it
All three high, dispatch still missedOEE is not the problemScheduling and sequence — see production monitoring
Definitions in full

FactorISO 22400-2 — the standardMachineWise variant — internal only
AvailabilityActual production time ÷ planned production timeMachine on-time ÷ reporting time
Performance / Effectiveness(Produced quantity × ideal cycle time) ÷ actual production timeProductive time ÷ machine on-time — a time-in-cut proxy
QualityGood quantity ÷ produced quantityIdentical to ISO
Needs a maintained standard?Yes — an ideal cycle time per partNo
Comparable to published benchmarks?YesNo — treat as your own baseline

The variant exists because a floor running fifty part numbers a month often has no trustworthy ideal cycle time, and an OEE that cannot be computed until standards are maintained is an OEE that never gets computed. It is useful internally and it is not the ISO definition. Quote the ISO figure externally, and say which one you used.

Ready when you are

See your own availability, performance and quality

Measured per machine and per shift, on the ISO 22400-2 basis or the internal variant, with the definition stated beside every figure.

Get a call back within one working day
No spam, no call centre. An engineer calls you.
Questions

Straight answers.

What is availability in OEE?
The share of planned production time in which the equipment actually produced. On the ISO basis it is actual production time over planned production time; the MachineWise variant uses machine on-time over reporting time.
What is performance in OEE?
How close the machine ran to its best demonstrated rate while producing. ISO computes it from produced quantity and ideal cycle time; the MachineWise variant uses productive time over machine on-time, which needs no standard.
What is quality in OEE?
Good parts as a share of parts produced. It is identical on both definitions. A quality figure of exactly 100% usually means rejections are not being captured rather than that none occurred.
Should setup count against availability?
No. A machine in setup is not broken. Treating setup as downtime produces a figure the shop floor rejects on sight, and the dispute discredits the rest of the data.
Which factor should we fix first?
Read the pattern rather than the product. Low availability with good performance is a stopping problem for maintenance and scheduling; high availability with low performance is a speed, tooling or standards problem.
Why is a low quality score the most expensive?
Because a rejected part consumed availability, performance, material and labour before being thrown away. It is the only factor where the loss is incurred three times over.
FREE 2-MACHINE PILOT
Live OEE on two of your machines — this week. ₹0 to start.
Software-first setup in under an hour each · your data stays on-premises · plant-specific ROI model included.