Overall equipment effectiveness (OEE) compares effective good production with planned production time. Keep availability, performance and quality visible so the combined percentage does not hide the type of loss.
Formula
- Availability = running time ÷ planned production time.
- Performance = ideal cycle time × total units ÷ running time, using matching time units.
- Quality = good units ÷ total units.
- OEE = availability × performance × quality.
Vorne’s OEE calculation reference explains these factors and the equivalent good-count calculation. Define your planned window and first-pass good output consistently before comparing shifts.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Worked shift example
This illustrative shift has 400 planned minutes, 320 running minutes, a 30-second ideal cycle, 600 total units and 570 good units.
| Factor | Calculation | Result |
|---|---|---|
| Availability | 320 ÷ 400 | 80% |
| Performance | 30 × 600 ÷ (320 × 60) | 93.75% |
| Quality | 570 ÷ 600 | 95% |
| OEE | 0.8 × 0.9375 × 0.95 | 71.25% |
The direct check is 570 × 30 ÷ (400 × 60) = 71.25%. Enter these values in the calculator on this page and export the source record. The example is not a customer benchmark or a promised improvement.
Read the loss before choosing the action
For this shift, 80 planned minutes were not running. Investigate the stop log to separate breakdowns, changeovers and other recorded reasons. The performance factor then asks whether production while running matched the declared ideal cycle. The quality factor isolates the difference between total and first-pass good units.
A maintenance task may address a repeated mechanical stop. A quality issue may instead require process investigation. Assign actions from the evidence rather than assuming every lost unit is a maintenance failure.
Avoid common calculation errors
Do not mix ideal seconds with running minutes without converting. Do not count reworked output as first-pass good production if your definition excludes it. Do not divide by a full calendar day when only one production window was planned. Preserve the original inputs when correcting a shift record.
Performance above 100% is a review flag: check the ideal cycle and counts. The calculator exposes the result rather than silently capping it. If there are no units, quality is unavailable; effective good output and OEE are zero when a positive production window was planned. If planned time is zero, there is no valid denominator.
Do not average shift percentages blindly. To combine runs with different cycle times, sum their effective good-production time and divide by total planned time. Keep the source runs available so changes in product mix remain visible.
AI-generated editorial illustration; not a customer photograph or product screenshot.
OEE is different from reliability
MTBF uses operating exposure and failures. MTTR uses repair or restoration duration. OEE also includes speed and quality losses. A machine can have no recorded breakdowns and still produce slowly or generate rejects.
Save a reviewable production record
PreventiveHQ’s production workflow saves the asset, date, run label, planned and running minutes, cycle seconds, total units and good units. Review the factors before saving. Void an incorrect record with a reason and enter its replacement so the evidence is retained.
Production values are entered manually. A saved run does not establish automatic machine connectivity or a complete production-planning system. Use the public demo first, then test one real shift in a workspace. Pair it with a manufacturing maintenance checklist if the loss review identifies equipment work.
Set the measurement boundary before the shift
OEE needs a defined production process and a defined period when production was intended. A machine, a packaging cell and an entire connected line can have different boundaries. Decide which output count, stop events and operating time belong to the selected process. Otherwise the numerator may describe one machine while the denominator describes a whole shift or department.
For a connected line, choose a measurement point that represents the required output and document how upstream or downstream interruptions are handled. Counting finished units at the end of the line while measuring runtime on an unrelated intermediate machine can produce a result that is difficult to interpret. The calculation should follow a coherent production boundary.
Keep planned production time distinct from all calendar time. A weekend when the line was not scheduled to produce is a different question from a stop during a scheduled run. Document the planned-time rule before reviewing the result, especially where breaks, changeovers or planned maintenance may be treated differently by different teams.
The purpose is consistent measurement, not selecting exclusions that make the percentage look favorable. If the business wants to understand losses across all available calendar time, use a measurement designed for that question alongside OEE. Do not quietly change the OEE denominator to answer a different question.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Check availability inputs against a simple timeline
Availability compares runtime with planned production time under the stated convention. Build a shift timeline showing when production was intended and which stops reduced runtime. The timeline gives operators and analysts a shared way to reconcile the calculation rather than debating a percentage without seeing its inputs.
An illustrative period contains 450 minutes of planned production and 45 minutes of recorded stops within that window. Runtime is 405 minutes, so availability is 405 divided by 450, or 90 percent. This example assumes the stop records are complete and do not overlap in a way that causes double counting.
If two stop reasons are recorded for the same interval, they cannot both be subtracted in full from the elapsed timeline. A line can be waiting for a part and for access at the same time. Preserve both contributing constraints where useful, but use a consistent method for the actual stopped duration.
Check events that cross the beginning or end of the reporting period. Only the portion inside the selected window belongs in that window's elapsed-time calculation. Retain the full event elsewhere so the operational investigation does not lose context when the reporting system divides it between shifts.
Establish a defensible ideal cycle time
Performance compares the output achieved during runtime with the ideal cycle time used for the selected product and process. That reference needs a documented basis. An arbitrary target copied from another line or an old product can distort performance even when the time and count records are accurate.
Record the product, equipment configuration and unit represented by the ideal cycle time. A value expressed in seconds per individual item cannot be applied directly to a count of cases unless the conversion is made explicitly. Multi-cavity or multi-lane processes also need a clear relationship between machine cycles and the counted output unit.
When performance exceeds 100 percent, investigate the inputs instead of clipping the value without explanation. The ideal cycle time may be too slow, the count may include units from outside the interval or the time unit may be wrong. A percentage above the intended upper boundary is a useful signal that the measurement needs review.
Review changes to the ideal cycle reference through an agreed process. Keep the previous value and the effective date. If the product mix or machine configuration changes, the trend should disclose that context. An improved percentage caused solely by a looser reference is not evidence that the process became faster.
Define total and good counts consistently
Quality uses good output and total output measured at a compatible boundary. Define what makes a unit good for the calculation and how rejects, rework and later discoveries are recorded. The production team should be able to reconcile the counts with its quality records using the same units and reporting window.
Do not count a reworked item twice as two independent good units when it represents one original unit. Equally, do not make rejected production disappear from total output just because it cannot be shipped. The chosen method should preserve the distinction between production effort and acceptable output.
For an illustrative run with 900 total units and 855 good units, quality is 855 divided by 900, or 95 percent. The remaining 45 units require a clear classification in the source record. This arithmetic says nothing by itself about why those units failed or whether they can be recovered.
When quality decisions occur after the shift, explain how later information updates the production record. A preliminary count may need correction after inspection. Preserve the change and its reason through the supported recordkeeping process so an earlier management report can be reconciled with the final result.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Reconcile the two common calculation forms
The factor form multiplies availability, performance and quality using decimal ratios. Under compatible definitions, the simplified form divides ideal production time for good units by planned production time. The two forms should agree when they use the same boundary and inputs.
Take an illustrative run with 450 planned minutes, 405 runtime minutes, an ideal cycle time of 0.4 minutes per unit, 900 total units and 855 good units. Availability is 0.9. Performance is 360 divided by 405. Quality is 0.95. Multiplying the three factors gives 0.76, or 76 percent.
The simplified calculation gives 855 multiplied by 0.4, divided by 450. That is 342 ideal minutes divided by 450 planned minutes, again 76 percent. The agreement is a useful arithmetic check. It does not independently verify that the cycle reference, stop log or output counts are correct.
The Vorne OEE calculation guide explains the factor and simplified forms. Use that reference for the calculation relationship, then retain your own input definitions and worked record so colleagues can understand what your site's result actually measures.
Aggregate runs using compatible totals
A simple average of run percentages can give a short run the same influence as a long run. If the question is overall effectiveness across the selected planned production time, retain the time-weighted inputs. For each run, calculate ideal production time for good output, then divide the sum of those ideal times by the sum of planned production times.
For an illustrative example, a 60-minute planned run produces 48 ideal minutes of good output, while a 240-minute planned run produces 144 ideal minutes. The individual results are 80 and 60 percent. The combined result is 192 divided by 300, or 64 percent, rather than the unweighted average of 70 percent.
Different products require their own valid ideal cycle references before aggregation. Adding raw unit counts across products with different cycle times can conceal the actual production opportunity. Convert each run's good count into its associated ideal production time using the appropriate reference.
Aggregation should still preserve the underlying runs. A whole-line or whole-month result can hide a product-specific problem, an unusual changeover or a single long interruption. Keep the summary useful for reporting while allowing the team to inspect the runs that contributed the most lost opportunity.
Choose an action from the loss mechanism
An OEE percentage identifies a measurement outcome, not a repair instruction. A lower availability factor suggests examining stops and their causes. A performance gap suggests examining rate loss, minor stops and the validity of the ideal cycle reference. A quality gap suggests examining rejected output and the associated process conditions.
Those categories can interact. A machine setting might change both speed and quality. An intervention that raises output rate while creating more rejects may not improve good output. Review the factors together and connect them with the physical process before recommending a change.
For a practical loss review, select a consequential event or run and gather its time record, product, settings context, operator observations and maintenance findings. Distinguish confirmed causes from hypotheses. A maintenance ticket raised during a poor run does not automatically prove that an equipment defect caused every recorded loss.
Assign the next investigation to the appropriate function. Some losses require maintenance work; others involve material, process setup, staffing or quality decisions. OEE can support that conversation, but the ownership should follow the evidence rather than routing every poor result into the maintenance backlog.
AI-generated editorial illustration; not a customer photograph or product screenshot.
Keep OEE separate from employee ranking
A production result reflects equipment, product, operating conditions, preparation and the measurement method. Ranking individual operators by an unadjusted OEE percentage can create incentives to change classifications, avoid difficult products or hide stops. It can also obscure constraints outside the operator's control.
Use the record to understand the process first. Invite operators to explain the observed conditions and compare those explanations with the source data. A gap between a stop log and an operator's account may expose a measurement problem or an unrecorded interruption that deserves attention.
Targets should follow the process and the business decision. A universal benchmark is not a substitute for understanding your own losses, product mix and feasible improvements. Keep the raw inputs visible so the team can distinguish a real operating change from a revised denominator or cycle reference.
The most useful review produces a specific, testable next action. It might improve a changeover preparation step, investigate a recurring stop or correct a count boundary. A higher headline number without an understood change in the underlying process provides weaker evidence of improvement.
Pilot the measurement before expanding it
Choose a bounded production process where the team can reconcile time and counts manually. Define the planned-time rule, stop handling, ideal cycle reference, good-count rule and reporting window. Test the measurement across ordinary conditions and at least one meaningful exception before extending it to more equipment.
Include a deliberately invalid example in the validation exercise. A good count above total count, a negative runtime or a cycle time in the wrong unit should require correction. This checks whether the workflow helps people recognize an error rather than accepting every number that produces a percentage.
Review the resulting record with production, maintenance and quality staff. Each group may notice a different boundary problem. Resolve those disagreements in the measurement definition and preserve the agreed rule where future users can find it. A dashboard tooltip alone may be insufficient for a complicated production process.
Expand only when the inputs can be explained and the result supports a useful action. Retain the pilot's lessons, known limitations and ownership. Manual measurement can be valuable when it is consistent and reviewable; adding automated collection does not remove the need to define what the signals and counts mean.
Preserve the assumptions when exporting a result
Check unit conversion explicitly when importing a run. A cycle reference of 24 seconds per unit is 0.4 minutes per unit. Multiplying a count by 24 and dividing by a production window measured in minutes creates a unit mismatch, even if every individual field contains a plausible number. Convert the time basis before calculating and preserve the original unit in the source record.
Counts need the same attention. A tally of boxes containing several units is not interchangeable with a tally of individual units. Specify the counted item, establish any conversion from the production record and use that convention for both total and good output. If the packaging quantity changes between products, apply the correct conversion to each run before combining their results. These checks are particularly useful when the same report receives manual entries from several shifts or equipment areas.
A useful OEE export should retain more than the final percentage. Include the production boundary, reporting window, planned production time, runtime, ideal cycle time and its unit, total count and good count. Identify the product or configuration associated with the cycle reference. These details let another analyst reproduce the arithmetic and assess whether aggregation is appropriate.
Attach the relevant interpretation rules or a reference to their controlled location. A recipient should not have to infer whether a planned break was excluded or whether a later quality decision changed the good count. If the result is preliminary, label it accordingly and explain what information is still outstanding.
Keep an example calculation in the team's training material using clearly fictional inputs. Ask a second person to reproduce both the factor calculation and the simplified form. Disagreement usually reveals an input, unit or boundary problem that is easier to correct during training than after the number becomes a management target.
When sharing an improvement claim outside the team, separate the measured change from its proposed explanation. A later period may have a different product mix, schedule or operating condition. Use a documented evidence method to evaluate those differences before attributing the change to software, a maintenance intervention or a particular employee.
AI-generated editorial illustration; not a customer photograph or product screenshot.