[et_pb_section fb_built=”1″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” sticky_enabled=”0″]<\/p>\n
The reality is stark: the average overall efficiency of equipment in the manufacturing industry is 55-60%, and only 6% of plants reach the World Class of 85%+.<\/strong> This often comes as a rude shock to production managers, who discover that their manual OEE calculation masks 10-30% of hidden productive capacity.<\/p>\n In 2025, with the OEE solutions market set to reach USD 12 billion by 2033, the priority is no longer “should we measure?” but “how can we guarantee the reliability of our data?”. In this article, we break down the 7 fatal errors that distort your metrics, with numerical examples from McKinsey, Evocon and Symestic studies. <\/p>\n OEE (Overall Equipment Effectiveness) combines three critical dimensions of production time:<\/p>\n OEE = Availability \u00d7 Performance \u00d7 Quality<\/strong><\/p>\n McKinsey documents substantial gains linked to a precise calculation:<\/p>\n Case in point<\/strong>: a pharma plant moving from 37% to 60% OEE generates an annual return of 14-16 million USD<\/strong> (McKinsey, 250 days\/year, 16h\/day, 40% margin).<\/p>\n The facts<\/strong>: Most factories operate 20-30 points below World Class, often without realizing it.<\/p>\n The problem<\/strong>: These stoppages of a few seconds (jams, sensors, adjustments) escape manual collection. 50 micro-stops of 3 minutes = 2h30 lost. <\/p>\n Impact in figures<\/strong>: DBR77 Robotics establishes that microstops account for 15-20% of lost time<\/strong>. Symestic documents: <\/p>\n Nutriset case study<\/strong>: the agri-food customer eliminated these 3-4-second “irritants” occurring 50-100 times\/station, resulting in +11% OEE in 8 years<\/strong>.<\/p>\n Solution<\/strong>: IoT sensors capture every event from the very first second, without human intervention.<\/p>\n The problem<\/strong>: Using historical average speed instead of manufacturer’s nominal speed artificially inflates scores.<\/p>\n Symestic example<\/strong>: Manufacturer specifies 3 sec\/part, real time observed 4 sec. Production of 1,000 parts in 3,300 seconds: <\/p>\n Correct calculation (manufacturer’s speed)<\/strong>:<\/p>\n Miscalculation (average speed)<\/strong>:<\/p>\n Impact<\/strong>: Worximity warns that this error masks opportunities for improvement. Correcting it reveals 5-25% improvement potential<\/strong>. <\/p>\n The problem<\/strong>: Counting reworked parts as “good” in the quality rate distorts the index.<\/p>\n Symestic example<\/strong>: Production of 1,000 pieces :<\/p>\n Incorrect calculation<\/strong>: (900 + 80) \/ 1,000 = 98%<\/strong> Correct calculation (First Pass Yield)<\/strong>: 900 \/ 1,000 = 90%<\/strong> Difference<\/strong>: 8 points<\/strong><\/p>\n Principle<\/strong>: Worximity specifies: “Only parts that are flawless from the first pass count. Including rework masks problems in the production process.”<\/p>\n The problem<\/strong>: Evocon identifies incorrect categorization of stops as error #1<\/strong>. Unplanned stops become “planned” to improve scores. <\/p>\n Stick culture<\/strong>: TipTeh explains, “When data is used as a disciplinary stick, teams incorrectly classify stops to mask problems.”<\/p>\n Classic confusion<\/strong>:<\/p>\n Impact<\/strong>: Masks opportunities for improvement and gives a false impression of optimization.<\/p>\n The problem<\/strong>: Scytec warns: “Manual data entry leads to human error.” The classic “Have you filled in your sheet?” produces approximate data. <\/p>\n 5 causes of inaccuracy<\/strong>:<\/p>\n PSA Stellantis case study<\/strong>: Christophe Pasquet confirms the considerable time freed up for operators, who can concentrate on production.<\/p>\n The problem<\/strong>: Mixing minutes, seconds and hours produces absurd results.<\/p>\n Symestic example<\/strong>: 390 min runtime, 45 sec\/part, 500 parts<\/p>\n Incorrect (mixed units)<\/strong>: (45 \u00d7 500) \/ 390 = 57.7 (absurd)<\/strong> Correct (seconds)<\/strong>: (45 \u00d7 500) \/ (390 \u00d7 60) = 96.2%<\/strong> .<\/strong> <\/p>\n Recommendation<\/strong>: “Check unusual results for unit errors” (Symestic).<\/p>\n The problem: Evocon identifies lack of standardization as critical error #7. Without a single methodology, it’s impossible to compare sites. <\/p>\n 4 sources of inconsistency<\/strong>:<\/p>\n Pitfall<\/strong>: Worximity warns of inappropriate comparisons (1 change\/day vs. 4-5 changes\/day).<\/p>\n Eolane case study<\/strong>: Vincent Perrault uses a standard multi-site tool for uniform monitoring, with significant cost savings.<\/p>\n IoT sensors capture every event in real time. Eliminates errors #1 (micro-stops) and #5 (inaccurate data). <\/p>\n Automatically applies the right formula, right categories, right units. Eliminates errors #2, #3, #6, #7. <\/p>\n Stops classified according to configurable rules, applied 24\/7. Eliminates error #4. <\/p>\n Pareto-transformed data, trends, correlations. Automatic root cause analysis. Proactive drift detection. <\/p>\n McKinsey earnings<\/strong>:<\/p>\n Documented cases<\/strong>:<\/p>\n Typical ROI<\/strong>: 6-18 months depending on installation size.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout” custom_margin=”29px|auto||auto||”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” sticky_enabled=”0″]<\/p>\n [\/et_pb_text][et_pb_accordion _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” sticky_enabled=”0″][et_pb_accordion_item title=”How to calculate OEE correctly?” open=”on” _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” sticky_enabled=”0″]<\/p>\n OEE = Availability \u00d7 Performance \u00d7 Quality<\/strong><\/p>\n Availability<\/strong> = Actual time \/ Planned time Performance<\/strong> = Actual part quantity \/ Theoretical (manufacturer’s speed) Quality<\/strong> = Good parts (First Pass) \/ Total produced<\/p>\n Example<\/strong>: Shift 8h (480 min), breaks 30 min, stops 45 min<\/p>\n Availability = 405\/450 = 90%.<\/p>\n<\/li>\n Performance = 385\/405 pieces = 95%.<\/p>\n<\/li>\n Quality = 377\/385 = 98<\/p>\n<\/li>\n OEE = 83.8<\/strong><\/p>\n<\/li>\n<\/ul>\n [\/et_pb_accordion_item][et_pb_accordion_item title=”Why is my manual OEE superior to the automated one?” _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” open=”off” sticky_enabled=”0″]<\/p>\n Normal! Automated is typically 5-15 points lower<\/strong> because it captures : <\/p>\n Micro-interest (15-20% hidden losses)<\/p>\n<\/li>\n Actual vs. average speeds (5-25% potential)<\/p>\n<\/li>\n Touch-ups excluded (8-point spread)<\/p>\n<\/li>\n Correct classification of stops<\/p>\n<\/li>\n All input errors eliminated<\/p>\n<\/li>\n<\/ul>\n [\/et_pb_accordion_item][et_pb_accordion_item title=”What makes a good OEE?” _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” open=”off” sticky_enabled=”0″]<\/p>\n General standards<\/strong>:<\/p>\n < 60%: Insufficient (world average 55-60%)<\/p>\n<\/li>\n 60-75%: Acceptable SME<\/p>\n<\/li>\n 75-85%: Good level<\/p>\n<\/li>\n > 85% : World Class<\/p>\n<\/li>\n<\/ul>\n By sector<\/strong>:<\/p>\n Pharma: 35-37% average, 70% World Class<\/p>\n<\/li>\n Agri-food: 70-80% average, 80-85% leaders<\/p>\n<\/li>\n Automotive: 75% average, 84-86% lean<\/p>\n<\/li>\n<\/ul>\n Important<\/strong>: Only 6% reach 85%+ (Evocon). Aim for continuous improvement: +5 points\/year. <\/p>\n [\/et_pb_accordion_item][\/et_pb_accordion][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”et_body_layout”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”et_body_layout” sticky_enabled=”0″]<\/p>\n Only 6% of manufacturers reach World Class<\/strong>, with the majority operating at 55-60%<\/strong> and thinking they are at 70-75%. This difference represents hundreds of thousands of euros of hidden capacity during the production period. <\/p>\n Automation costs less than manual work<\/strong>:<\/p>\n Documented rapid ROI<\/strong>:<\/p>\n Next steps<\/strong>:<\/p>\n Free tools for taking action<\/span><\/p>\nWhy OEE Calculation is Essential<\/h2>\n
\n
Benchmarks by sector<\/h3>\n
\n
The 7 Fatal Errors in Manual Calculation<\/h2>\n
Error #1 <\/span>– Invisible Micro-Stops: 15-20% Losses in Availability<\/h3>\n
\n
Mistake #2<\/span> – Average Speeds: 5-25% Hidden Potential in the Company<\/h3>\n
\n
\n
Error #3<\/span> – Counted touch-ups: 8 Quality Deviation Points<\/h3>\n
\n
Error #4<\/span> – Classification of Stops: Impact on Availability<\/h3>\n
\n
Error #5<\/span> – Inaccurate manual data<\/h3>\n
\n
Error #6<\/span> – Confusion of Time Units<\/h3>\n
Error #7<\/span> – Lack of Multi-Site Standardization<\/h3>\n
\n
Solution: The 4 Pillars of Automation<\/h2>\n
1. Automatic Collection<\/h3>\n
2. Standardized calculation<\/h3>\n
3. Intelligent categorization<\/h3>\n
4. Analysis of Causes and Alerts<\/h3>\n
Documented ROI<\/h2>\n
\n
\n
FAQ – Frequently asked questions about OEE<\/b><\/h2>\n
\n
\n
\n
\n
Conclusion<\/h2>\n
Key points<\/h3>\n
\n
\n
\n