[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"legacy:insights\u002Fmes-oee-three-rates:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":71},"insights\u002Fmes-oee-three-rates","OEE disagrees with the boss’s gut—split availability, performance, and quality definitions - JEDP Digital Platform","The root cause of the OEE disputes is the inconsistency between planned production time, downtime classification, and first-pass yield count. Starting from the sense of 'something feels off,' break down availability, performance, quality, and points of water injection, explain micro-stops, ideal cycle time, cross-line benchmarking, as well as the implementation sequence of aligning MES data collection with shifts.","OEE calculation definition, equipment overall efficiency, MES OEE, downtime management, MTBF","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-insights","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fmes-slide6.webp",[13,31,45],{"@context":14,"@type":15,"@id":16,"headline":17,"description":6,"inLanguage":18,"datePublished":19,"dateModified":20,"articleSection":21,"keywords":22,"image":11,"author":23,"publisher":25,"isPartOf":26,"mainEntityOfPage":28},"https:\u002F\u002Fschema.org","Article","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-oee-three-rates#article","OEE disagrees with the boss’s gut—split availability, performance, and quality definitions","zh-CN","2026-06-11","2026-10-17","MES · Manufacturing","OEE calculation basis, overall equipment effectiveness, MES OEE, downtime management, MTBF",{"@id":24},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":24},{"@id":27},"https:\u002F\u002Fwww.jedp.cn\u002Finsights#collection",{"@type":29,"@id":30},"WebPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-oee-three-rates",{"@context":14,"@type":32,"itemListElement":33},"BreadcrumbList",[34,39,43],{"@type":35,"position":36,"name":37,"item":38},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":35,"position":40,"name":41,"item":42},2,"Insights","https:\u002F\u002Fwww.jedp.cn\u002Finsights",{"@type":35,"position":44,"name":17,"item":30},3,{"@context":14,"@type":46,"@id":47,"mainEntity":48},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-oee-three-rates#faq",[49,55,59,63,67],{"@type":50,"name":51,"acceptedAnswer":52},"Question","Is a model change considered downtime or planned maintenance?",{"@type":53,"text":54},"Answer","If the type change is scheduled, it can be included in the planned loss during the planned production time and classified separately; if the type change is forced due to quality abnormalities, it should be unplanned downtime. The key is stable classification and weekly review, not \"who decides\" temporary change.",{"@type":50,"name":56,"acceptedAnswer":57},"What type of loss does a micro-stop count as?",{"@type":53,"text":58},"A microstop that is shorter than the threshold (e.g., less than 5 minutes) usually leads to a loss of performance rather than availability. Apply the reason code above the threshold to record the downtime. Thresholds are written into the system to avoid verbal discretion on site.",{"@type":50,"name":60,"acceptedAnswer":61},"Can the automated line and the manual line use the same OEE?",{"@type":53,"text":62},"The formula can be the same, and the standard tempo and loss classification templates should be divided into production line family configurations. With a \"universal beat\" hard sleeve, the performance rate is inevitably distorted.",{"@type":50,"name":64,"acceptedAnswer":65},"What does it indicate if OEE is high but delivery times are poor?",{"@type":53,"text":66},"It may be that only a single device is optimized, ignoring complete sets, quality gates, and logistics. OEE is an efficiency specification, not a sufficient condition for delivery; it should be viewed together with APS dispatch and poor code scanning reporting.",{"@type":50,"name":68,"acceptedAnswer":69},"What is the relationship between MTBF and OEE?",{"@type":53,"text":70},"OEE looks at the loss structure within the shift, MTBF\u002FMTTR looks at the fault interval and repair. The two share the source of the downtime event; only OEE does not do the fault closed loop, and preventive maintenance cannot be pushed.","\u003Carticle class=\"insight-article\">\n    \u003Cdiv class=\"insight-container\">\n      \u003Cnav class=\"breadcrumb\" aria-label=\"Breadcrumb\">\n        \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Ca href=\"\u002Finsights\">Insights\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Cspan>MES · Manufacturing\u003C\u002Fspan>\n      \u003C\u002Fnav>\n\n      \u003Cheader class=\"insight-hero\">\n        \u003Cdiv class=\"insight-tags\">\u003Cspan class=\"r-tag\">OEE\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Equipment efficiency\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Shutdown\u003C\u002Fspan>\u003Cspan class=\"r-tag\">MES\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Ch1>OEE disagrees with the boss’s gut—split availability, performance, and quality definitions\u003C\u002Fh1>\n        \u003Cp class=\"insight-lede\">In the same production line, the Equipment Department reported that OEE was 82%, and the Production Department felt that it was \"waiting for materials for half a day\". Before the digital battle, first ask the planned production time to the end of the package does not contain the type change, etc. and to be inspected - the denominator of OEE is not the calendar time.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-meta\">\n          \u003Cspan>Updated 2026-06-11\u003C\u002Fspan>\n          \u003Cspan class=\"dot\" aria-hidden=\"true\">\u003C\u002Fspan>\n          \u003Cspan>~9 min read\u003C\u002Fspan>\n          \u003Cspan class=\"dot\" aria-hidden=\"true\">\u003C\u002Fspan>\n          \u003Cspan>Manufacturing digitalization · MES · Manufacturing\u003C\u002Fspan>\n        \u003C\u002Fdiv>\n      \u003C\u002Fheader>\n      \u003Csection class=\"insight-takeaways\">\n        \u003Ch2>What you'll take away\u003C\u002Fh2>\n        \u003Cul>\u003Cli>OEE = availability rate × performance rate × quality rate, the three rates must be separately explainable, not just one composite score\u003C\u002Fli>\u003Cli>The denominator is planned production time, not calendar power-on time; kicking wait-for-material out of planned time is the most common inflation.\u003C\u002Fli>\u003Cli>Ideal cycle time for performance rate comes from engineering\u002Fprocess standards—not 'felt good today' or inflated shift output back-solved.\u003C\u002Fli>\u003Cli>The quality rate is first pass, and the rework counting rules must be agreed in advance.\u003C\u002Fli>\u003Cli>Don't simply average the percentages of multiple lines; hold one line steady for 4 weeks before talking about horizontal benchmarking\u003C\u002Fli>\u003C\u002Ful>\n      \u003C\u002Fsection>\n\n      \u003Cdiv class=\"insight-layout\">\n        \u003Cdiv class=\"insight-body\">\n\u003Ch2 id=\"设备部说八十二-车间主任说半天在等料\">The Equipment Department said eighty-two, but the workshop supervisor said they have been waiting for materials for half a day.\u003C\u002Fh2>\n\u003Cp>The comprehensive OEE on the morning meeting screen looks great, but the boss frowned: 'I clearly saw the line stop.' Neither side is wrong — the mistake lies in lumping the three types of loss into one score for appearances, while quietly changing the denominator. OEE is not a ranking game where bigger numbers are better; it is a manual that explains the three types of loss: availability, performance, and quality. If the denominator uses calendar power-on time, minor stops are erased, ideal cycle time is inflated, quality uses final inspection pass rates to replace first-pass yield, or percentages from several lines are averaged into a 'plant-wide OEE,' then any rewards, penalties, or benchmarks are a waste of time.\u003C\u002Fp>\n\u003Cp>To make OEE a management tool, first make the three rates individually explainable: does the maximum loss occur in downtime, speed, or quality? A combined score that cannot be broken down can only be used for arguing in meetings. Align the definitions first, then talk about data collection and ranking—if the order is reversed, the dashboard will only accelerate disputes over standards.\u003C\u002Fp>\n\u003Ch2 id=\"分母战争-计划生产时间里藏了什么\">Denominator War: What Is Hidden in the Planned Production Time\u003C\u002Fh2>\n\u003Cp>The denominator of OEE is\u003Cstrong>Planned production time\u003C\u002Fstrong>——The scheduled production periods in the shift calendar are based on what should be produced——not how long the equipment has been powered on, and certainly not the full 24 hours of the calendar. Statutory breaks and planned maintenance windows can be excluded; if waiting for materials, waiting for tooling, or pending decisions occur during the scheduled production period, it is assumed to be a loss, and you cannot make it look better by changing the denominator. Removing waiting for materials from planned time is the most common form of inflating numbers: both the numerator and denominator of availability appear \"better,\" but the boss's impression will immediately not match.\u003C\u002Fp>\n\u003Cp>How to classify changeovers: having a fixed classification is more important than debating it. Changeovers scheduled in the plan can be classified separately as planned losses; changeovers forced by quality issues go into unplanned downtime. Keep the classification stable and review it weekly; it is forbidden to change it on a whim based on 'who says so.' For production lines with very frequent multi-product changeovers, if the loss criteria for changeovers have not yet been defined separately, first treat changeovers independently before discussing overall OEE—otherwise, availability and performance will constantly compete with each other.\u003C\u002Fp>\n\u003Ch2 id=\"三率各自在说什么损失\">What loss is each of the three rates talking about\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rate\u003C\u002Fth>\u003Cth>Recommended definition\u003C\u002Fth>\u003Cth>Benchmark\u003C\u002Fth>\u003Cth>Common water injection\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Availability\u003C\u002Ftd>\u003Ctd>Actual Operating Time \u002F Planned Production Time\u003C\u002Ftd>\u003Ctd>Planned production time\u003C\u002Ftd>\u003Ctd>Waiting materials for inspection are kicked out of the denominator; malfunctions are recorded as planned stops\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Performance rate\u003C\u002Ftd>\u003Ctd>Actual Output × Ideal Cycle Time \u002F Operating Time\u003C\u002Ftd>\u003Ctd>Ideal rhythm for engineering calibration\u003C\u002Ftd>\u003Ctd>Slow down the tempo; slightly pause and hide into 'normal operation'\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Quality rate\u003C\u002Ftd>\u003Ctd>Number of acceptable units \u002F Number of units input\u003C\u002Ftd>\u003Ctd>Whether the input includes rework return must be agreed upon in advance\u003C\u002Ftd>\u003Ctd>Only report final inspection qualified; defects are recorded separately\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Randomly take a shift and see if you can break down three rates within two minutes and point out the category with the largest loss—if you can't break it down, the overall score should not be used for management, nor should it be considered for rewards and penalties. The loss structure is recommended to be read like a waterfall: planned time → subtract downtime to get operating time → subtract speed loss to get net operation → subtract quality loss to get valuable output. Meetings only show the overall OEE, but on-site you must learn to adjust the top denominator of the waterfall.\u003C\u002Fp>\n\u003Ch3 id=\"班次拆解-把争议算成数\">Shift breakdown: Count disputes as numbers\u003C\u002Fh3>\n\u003Cp>Assume the bottleneck workstation is scheduled to produce for 480 minutes; breakdown downtime 40, waiting for materials 30 (both during scheduled production time); operating time 410 minutes; ideal cycle time 1.0 minute\u002Fpiece; output 350, of which first-pass good 330, reworked and then good 15, scrapped 5.\u003C\u002Fp>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Calculate\u003C\u002Fth>\u003Cth>Outcomes\u003C\u002Fth>\u003Cth>Explanation\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Availability\u003C\u002Ftd>\u003Ctd>410 \u002F 480 ≈ 85.4%\u003C\u002Ftd>\u003Ctd>Waiting materials and faults are all left on the denominator side loss\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Performance rate\u003C\u002Ftd>\u003Ctd>(350 × 1.0) \u002F 410 ≈ 85.4%\u003C\u002Ftd>\u003Ctd>Micro-stops and speed loss are reflected here\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Yield Rate (First Pass Yield)\u003C\u002Ftd>\u003Ctd>330 \u002F 350 ≈ 94.3%\u003C\u002Ftd>\u003Ctd>After rework, if it passes again, do not count it as a qualified unit\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>OEE\u003C\u002Ftd>\u003Ctd>≈ 68.8%\u003C\u002Ftd>\u003Ctd>The comprehensive score is used for communication, and actions focus on three areas of loss\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Someone kicked the 30-minute material waiting time out of the planned schedule, and the availability immediately 'rose'—this is a typical scenario of the definition war. When the boss 'feels something is wrong,' nine times out of ten it's not that the formula is wrong, but that the denominator has been tampered with. Only by stopping the tampering can the numbers qualify to enter the improvement meeting.\u003C\u002Fp>\n\u003Ch2 id=\"微停-节拍-一次合格-三个注水口\">Slight pause, rhythm, one pass: three water injection ports\u003C\u002Fh2>\n\u003Cp>Set a threshold (e.g., ≥5 minutes) to record downtime reason codes, and accumulate durations below the threshold as a speed loss performance rate. If the thresholds are not consistent, availability and performance rate will conflict with each other. Eight to twelve reason codes are usually enough; if there are hundreds, eventually everyone just selects 'Other'.\u003C\u002Fp>\n\u003Cp>Ideal takt comes from process\u002FIE calibration, and any changes go through a change order with an effective date; historical shifts are recalculated according to the takt at that time. It is forbidden to 'reverse-calculate takt from this week's target output' — padding takt is a classic method of inflating performance rates. When the process hasn't changed but the performance rate soars, the first reaction should be to check whether the takt has been 'optimized', not to give out bonuses.\u003C\u002Fp>\n\u003Cp>Quality First, One-Time Pass: After rework, if the product passes, it can be included in the production statistics. However, if the final inspection pass is used to replace a one-time pass, it will mask process loss of control. Whether rework is counted as input must be fixed in the specification table and must share the same source as the failure codes for scanning and reporting work. Having separate sheets and standards for output and defects, no matter how good the quality rate looks, is just for show. Formulas can be the same for automated and manual lines, but standard cycle time and loss classification templates must be configured according to the production line family—rigidly applying a \"universal cycle time\" will inevitably distort performance results.\u003C\u002Fp>\n\u003Ch2 id=\"MES-怎么采-才采得成管理工具\">How to collect MES data in order for it to become a management tool\u003C\u002Fh2>\n\u003Cp>Compare with the equipment ledger, operation monitoring, scanning report, and OEE\u002FMTBF in the manufacturing execution plan:\u003C\u002Fp>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Ability\u003C\u002Fth>\u003Cth>Key points for implementation\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Resources and Shifts\u003C\u002Ftd>\u003Ctd>Equipment—production line—process mapping is clear; shifts and dispatched shifts share the same source\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Status Collection\u003C\u002Ftd>\u003Ctd>Operation\u002FPlanned Stop\u002FFailure\u002FWaiting for Materials can be acquired or switched via scan, reason code must be provided\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Output and Rhythm\u003C\u002Ftd>\u003Ctd>The numerator of the completion reporting write-back performance rate; the ideal takt is assigned to the process operations\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Mass spectrometry\u003C\u002Ftd>\u003Ctd>A pass or defect comes from the process\u002Ffinal inspection closed loop; two sheets of paper are prohibited\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>MTBF\u002FMTTR\u003C\u002Ftd>\u003Ctd>Fault incidents serve both OEE and reliability at the same time; the fault timing only ends when the maintenance work order is closed\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Benchmark Unit\u003C\u002Ftd>\u003Ctd>Calculate the three rates by production line family and equipment family; simple averaging across the entire plant is prohibited\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>If a summary must be made, use time-weighted or output-weighted methods, and indicate the method on the board. Comparing percentages directly between automated lines and manual lines has no management significance. \"Both lines are 78%\" is almost impossible to compare between fully automated and multi-product manual lines. MTBF and OEE share failure events: if a maintenance work order is not closed before the failure time ends, MTBF will be inflated, and preventive maintenance will also be distorted. Inspection maintenance and maintenance work orders should enter the same ledger and originate from the same reporting source as downtime, otherwise reliability indicators and efficiency indicators will speak for themselves. JEDP-MES emphasizes splitting OEE into three rates, micro-stops, and cause codes that can be managed—precisely to avoid \"only one overall score that doesn’t match the feeling.\"\u003C\u002Fp>\n\u003Cp>When OEE is high but delivery times are still poor, it often means that only individual equipment has been optimized, neglecting completeness, quality gates, and logistics. OEE is an efficiency manual, not a sufficient condition for delivery times, and should be viewed together with work dispatch completion and defective reporting. If the overall score of the bottleneck equipment looks good, but upstream and downstream materials are waiting or pending inspection in batches, it indicates that the improvement meeting was focusing on the wrong target.\u003C\u002Fp>\n\u003Ch2 id=\"样板线先稳四周-再谈横向对标\">Stabilize the surroundings of the model line first, then discuss horizontal benchmarking.\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Order\u003C\u002Fth>\u003Cth>Do it first\u003C\u002Fth>\u003Cth>Sign of effectiveness\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>1\u003C\u002Ftd>\u003Ctd>Freeze the planned production time and shift calendar of the model line\u003C\u002Ftd>\u003Ctd>Denominator debate converges\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>2\u003C\u002Ftd>\u003Ctd>Shutdown reason code 8–12   Micro-stop threshold\u003C\u002Ftd>\u003Ctd>Availability\u002Fperformance no longer blame each other\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>3\u003C\u002Ftd>\u003Ctd>Enter ideal rhythm into process master data, keep change records\u003C\u002Ftd>\u003Ctd>Block the beat of the pad\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>4\u003C\u002Ftd>\u003Ctd>Quality counting aligned once qualified\u003C\u002Ftd>\u003Ctd>Quality rate can be explained\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>5\u003C\u002Ftd>\u003Ctd>After stabilizing for four weeks, then benchmark laterally; simultaneously monitor MTBF\u003C\u002Ftd>\u003Ctd>Benchmarking is meaningful\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The first two steps usually allow the 'feeling' and the 'numbers' to realign within two weeks — what is being changed is the definition, not the algorithm. Ranking the entire factory before the sample line is stable will only force on-site staff to change the denominator. Recommended pace: Weeks 1–2, review and sign the specification; Weeks 3–6, shadow boards only analyze, no ranking; Weeks 7–10, replicate to similar production line groups; Weeks 11–12, conditionally disclose the three rates and loss structure, with overall OEE not being the sole criterion for rewards or penalties. Thresholds for publishing rankings: timestamps of reported work are not clustered at the end of shifts; random checks pass on equipment-to-line mapping; cycle time changes have documentation. If any of the three thresholds are not met, only internal shadow reports are released.\u003C\u002Fp>\n\u003Cp>Work reporting and equipment status are inaccurate, human-machine binding is not established, equipment master data and production line mapping are chaotic, management only cares about rankings rather than loss structure, changeovers happen very frequently but changeover losses are not separately defined, and production lines are still frequently undergoing debugging and verification (planned production time is rewritten weekly)—in these situations, stabilize or fix data collection first, then talk about OEE. Fixing work reporting before pushing OEE is the hard sequence: if the numerator is inaccurate, any ranking is just noise.\u003C\u002Fp>\n\u003Ch2 id=\"先贴口径表-再谈奖罚\">First post the definition table, then discuss rewards and punishments.\u003C\u002Fh2>\n\u003Cp>Choose the production line with the most disputes, post the three-rate definition sheet on the team board, and run it for four full weeks before discussing benchmarking and rewards\u002Fpunishments. Two things are enough for spot checks: whether waiting materials have been removed from the denominator, and whether the cycle time has been 'optimized' recently. If reason codes are long-term concentrated in 'others,' first streamline the code table and train on entries, rather than tightening the ranking. The overall score can be kept as a communication shorthand; management actions should always focus on the area with the biggest loss—downtime should be handled by addressing downtime, speed by addressing cycle time and micro-stops, quality by addressing first-pass yield. This is the path for OEE to return from being a vanity metric to a practical tool; if you only show a percentage, the shop floor will always learn to just change the denominator.\u003C\u002Fp>\n\u003Cul>\u003Cli>MES Manufacturing Solution: Scheduling and Dispatching \u002F Barcode Work Reporting \u002F Process Quality \u002F Traceability \u002F OEE·MTBF\u003C\u002Fli>\u003Cli>Scan code to report work: Collection point placed incorrectly, OEE numerator dies first\u003C\u002Fli>\u003Cli>APS Scheduling and Material Readiness: Look Here When Efficiency Is High But Deliveries Can't Be Made\u003C\u002Fli>\u003Cli>Workshop Reporting and Process Traceability Self-Test (No Data Required)\u003C\u002Fli>\u003C\u002Ful>\n        \u003C\u002Fdiv>\n        \u003Caside class=\"insight-toc\" aria-label=\"On this page\">\n          \u003Ch2>Contents\u003C\u002Fh2>\n          \u003Ca class=\"h2\" href=\"#设备部说八十二-车间主任说半天在等料\">The Equipment Department said eighty-two, but the workshop supervisor said they have been waiting for materials for half a day.\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#分母战争-计划生产时间里藏了什么\">Denominator War: What Is Hidden in the Planned Production Time\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#三率各自在说什么损失\">What loss is each of the three rates talking about\u003C\u002Fa>\n          \u003Ca class=\"h3\" href=\"#班次拆解-把争议算成数\">Shift breakdown: Count disputes as numbers\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#微停-节拍-一次合格-三个注水口\">Slight pause, rhythm, one pass: three water injection ports\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#MES-怎么采-才采得成管理工具\">How to collect MES data in order for it to become a management tool\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#样板线先稳四周-再谈横向对标\">Stabilize the surroundings of the model line first, then discuss horizontal benchmarking.\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#先贴口径表-再谈奖罚\">First post the definition table, then discuss rewards and punishments.\u003C\u002Fa>\n        \u003C\u002Faside>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"insight-cta\">\n        \u003Cp>\u003Cstrong>Want to apply this in your plant?\u003C\u002Fstrong>Resources has matching self-assessments and templates—or book a live demo.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-cta-actions\">\n          \u003Ca href=\"\u002Fresources?from=mes#selftest\" class=\"btn btn-outline\">Self-assessment in Resources\u003C\u002Fa>\n          \u003Ca href=\"\u002Fcases#case-mes\" class=\"btn btn-outline\">MES acceptance case\u003C\u002Fa>\n          \u003Ca href=\"\u002Fcontact?from=mes\" class=\"btn\">Get a demo\u003C\u002Fa>\n        \u003C!-- next-step:BEGIN -->\u003Ca class=\"btn\" href=\"\u002Fproduct\u002Fmes\">Product solution: \u003Cspan>JEDP-MES Smart Manufacturing Execution\u003C\u002Fspan>\u003C\u002Fa>\u003Ca class=\"btn btn-outline\" href=\"\u002Fres\u002Fresources\u002Fkits\u002F08-mes-equipment-oee.html\">Matching resource kit: \u003Cspan>Equipment inspection & maintenance + OEE calculation sheet\u003C\u002Fspan>\u003C\u002Fa>\u003C!-- next-step:END -->\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n      \u003Csection class=\"insight-faq\" id=\"faq\">\n        \u003Ch2>FAQ\u003C\u002Fh2>\n        \u003Cp class=\"insight-faq-sub\">Quick answers on this topic—still stuck?\u003Ca href=\"\u002Fcontact?from=mes\">Contact\u003C\u002Fa>\u003C\u002Fp>\n        \u003Cdiv class=\"faq-list\">\n        \u003Cdetails class=\"faq-item\" open>\n          \u003Csummary>Is a model change considered downtime or planned maintenance?\u003C\u002Fsummary>\n          \u003Cp>If the type change is scheduled, it can be included in the planned loss during the planned production time and classified separately; if the type change is forced due to quality abnormalities, it should be unplanned downtime. The key is stable classification and weekly review, not \"who decides\" temporary change.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What type of loss does a micro-stop count as?\u003C\u002Fsummary>\n          \u003Cp>A microstop that is shorter than the threshold (e.g., less than 5 minutes) usually leads to a loss of performance rather than availability. Apply the reason code above the threshold to record the downtime. Thresholds are written into the system to avoid verbal discretion on site.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Can the automated line and the manual line use the same OEE?\u003C\u002Fsummary>\n          \u003Cp>The formula can be the same, and the standard tempo and loss classification templates should be divided into production line family configurations. With a \"universal beat\" hard sleeve, the performance rate is inevitably distorted.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What does it indicate if OEE is high but delivery times are poor?\u003C\u002Fsummary>\n          \u003Cp>It may be that only a single device is optimized, ignoring complete sets, quality gates, and logistics. OEE is an efficiency specification, not a sufficient condition for delivery; it should be viewed together with APS dispatch and poor code scanning reporting.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What is the relationship between MTBF and OEE?\u003C\u002Fsummary>\n          \u003Cp>OEE looks at the loss structure within the shift, MTBF\u002FMTTR looks at the fault interval and repair. The two share the source of the downtime event; only OEE does not do the fault closed loop, and preventive maintenance cannot be pushed.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n      \u003Csection class=\"insight-related\">\n        \u003Ch2>Related reading\u003C\u002Fh2>\n        \u003Cdiv class=\"insight-related-grid\">\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">MES · Manufacturing\u003C\u002Fdiv>\n            \u003Ch3>Scan reporting is live but data is still wrong—put capture points where status actually changes\u003C\u002Fh3>\n            \u003Cp>The root cause of inaccurate work reporting data is usually not that employees are uncooperative, but that the data collection point was chosen in the wrong location. How far the data is collected determines how deep the traceability, OEE, and work dispatch feedback can go; if the location is wrong, the subsequent links in the chain all break together...\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-05-07 · ~9 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">MES · Manufacturing\u003C\u002Fdiv>\n            \u003Ch3>Schedules rewritten on the floor? APS must land in dispatch and kitting—not just a pretty Gantt\u003C\u002Fh3>\n            \u003Cp>Production scheduling implementation failure is commonly caused by lack of constraint on material readiness, work orders being freely changeable, and feedback not being returned. Starting from the daily chalkboard sequence adjustment, it explains the closed-loop of planning—material readiness—work dispatch—feedback, visibility of order insertion authorization and impact, as well as prioritizing limited production capacity…\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-04-02 · About 9 minutes\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">MES · Manufacturing\u003C\u002Fdiv>\n            \u003Ch3>Skipped operations still report complete? Anti-skip and SOP station binding must join the execution chain\u003C\u002Fh3>\n            \u003Cp>The system shows completion, but the site skips key processes—problems often arise from routes not requiring mandatory station passes and SOPs not being linked to workstations. Starting from customer complaints for reverse inspection, it explains how key station gates, WI versions, and in-process change rules…\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-05-06 · ~8 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  \u003C\u002Farticle>",1793937990495]