[et_pb_section fb_built=”1″ _builder_version=”4.27″][et_pb_row][et_pb_column type=”4_4″][et_pb_text]<\/p>\n
Most plants reporting OEE of 70-80% are actually measuring 55-62% when calculation is done to standard definitions. The 10-18 point inflation is not intentional dishonesty; it is the cumulative effect of five specific calculation mistakes that have crept into reporting over years or decades. Each mistake individually sounds minor and defensible. Combined, they produce a systematic upward bias that misleads leadership, corrupts benchmarking, and misdirects improvement investment. This article catalogs the five most common mistakes with specific examples, quantifies their typical impact, and walks through the remediation path for each.<\/p>\n
The value of identifying these mistakes is not to blame the teams who made them \u2014 they usually inherited the calculation method from predecessors and never had reason to question it. The value is that correcting the mistakes produces a realistic baseline from which actual improvement becomes possible. Plants that correct their OEE calculation typically see reported OEE drop 10-18 points in the first 30 days, then rebuild real improvements from the honest baseline over the subsequent 6-12 months. The honest baseline produces 2-3x more actual improvement than the inflated baseline because it targets real problems.<\/p>\n
Typical inflation: 4-8 OEE points.<\/strong> The standard MESA definition counts changeover as unplanned stop time within Availability. Many plants have drifted into treating it as planned downtime, excluded from OEE calculation. The rationale often sounds reasonable : “we know we need to change over, it’s planned production activity, not a loss.” The math treats it as a loss because it reduces actual running time against scheduled production time, which is what OEE measures.<\/p>\n How to diagnose: ask whoever produces the OEE report how the denominator of Availability is calculated. If the answer includes “minus scheduled changeover time,” you have this mistake. How to remediate: switch to the standard definition (Planned Production Time = scheduled time minus breaks\/meetings\/no-demand, but not minus changeovers), and separately report changeover time as a loss category within Availability. Most plants see Availability drop 5-10 points when this is corrected.<\/p>\n Typical inflation: 3-7 OEE points.<\/strong> Performance = (Ideal Cycle Time \u00d7 Total Count) \/ Run Time. The correct Ideal Cycle Time is the nameplate speed \u2014 what the equipment was designed to achieve at optimal conditions. The mistake is using the historical average cycle time as the denominator, which makes Performance appear close to 100% because it compares actual to actual.<\/p>\n How to diagnose: check your reported Performance numbers. If Performance is consistently above 95% across different product types and the line has known speed losses during routine operation, the Ideal Cycle Time definition is probably wrong. The remediation is to establish Ideal Cycle Time from engineering specifications or from the fastest demonstrated cycle time observed during pilot runs. This is a one-time engineering review, not an ongoing adjustment.<\/p>\n Plants fixing this mistake typically see Performance drop 8-15 points. The drop is real measurement, not performance change. The line runs at the same speed it did yesterday; the number is now honest instead of inflated.<\/p>\n Typical inflation: 2-5 OEE points, concentrated in Availability.<\/strong> Short stops (2-5 minutes for brief adjustments, 1-3 minutes for small fixes) are individually minor but cumulatively substantial. A line averaging 12 micro-stops per shift at 3 minutes each loses 36 minutes per shift \u2014 roughly 7.5% Availability impact on a 480-minute shift. Most plants do not capture these because operator manual logs have a threshold (“only log stops over 5 minutes”) and PLC event capture has filters that miss them.<\/p>\n How to diagnose: compare your logged stop count per shift to what operators report when directly asked. If logged stops are under 5 per shift but operators describe a dozen or more small issues during the shift, the logging is missing micro-stops. The remediation depends on measurement infrastructure: manual-log plants need operator process changes (tablet-based quick-logging with preset reason codes); MES-captured plants need to review their event filter settings; direct-sensor IoT plants typically capture micro-stops accurately already.<\/p>\n Typical inflation: 1-3 OEE points.<\/strong> Quality = Good Count \/ Total Count. Good Count should include only parts that pass first-time without rework. Many plants count reworked parts as good because they ultimately ship to customers. This is reasonable commercially but inflates OEE because it hides the quality loss that rework represents.<\/p>\n How to diagnose: check whether your Quality denominator is consistent with Good Count measured before rework. If rework is common and Quality reports are consistently above 98%, you may have this mistake. The remediation is to separate Good Count (first-pass good) from Shipped Count (including rework). OEE Quality uses Good Count; commercial reporting uses Shipped Count. Both numbers are useful for different purposes.<\/p>\n Typical inflation: variable, 2-5 OEE points of cross-line variance.<\/strong> Different shifts or lines define planned stops differently \u2014 one shift treats preventive maintenance as planned, another as scheduled time with unplanned stop. Weekend overtime shifts sometimes use different break definitions than weekday shifts. These inconsistencies make cross-line comparisons unreliable and tend to inflate the reporting of whichever line has more generous planned-stop definitions.<\/p>\n How to diagnose: request the detailed calculation methodology from each shift and line, and look for discrepancies. Common issues are preventive maintenance treatment, break time duration, quality-hold time treatment, startup warm-up time treatment. The remediation is to publish a standard definition, align all lines and shifts to it, and audit monthly for drift.<\/p>\n Instant download. No email confirmation needed.<\/p>\n \n Mistake 2: Using historical average cycle time as Ideal Cycle Time<\/h2>\n
Mistake 3: Missing micro-stops under 5 minutes<\/h2>\n
Mistake 4: Counting reworked parts as Good Count<\/h2>\n
Mistake 5: Inconsistent planned-stop definitions across shifts or lines<\/h2>\n
Download the free Excel calculator<\/h3>\n