[{"data":1,"prerenderedAt":71},["ShallowReactive",2],{"legacy:insights\u002Fmes-andon-downtime-codes:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":70},"insights\u002Fmes-andon-downtime-codes","Andon is on but nobody owns the stop? Downtime codes must close with the shift—not as “Other” later - JEDP Digital Platform","Andon failure is mostly due to call no-response time limit, optional reason code, and no verification on shutdown. Downtime must proceed from call → response → reason → shutdown into the shift, sharing the same source as OEE availability, restricting 'Others'.","Andon downtime, downtime reason code, OEE downtime management, MES exception call","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-insights","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fmes-slide6.webp",[13,30,44],{"@context":14,"@type":15,"@id":16,"headline":17,"description":6,"inLanguage":18,"datePublished":19,"dateModified":20,"articleSection":21,"keywords":7,"image":11,"author":22,"publisher":24,"isPartOf":25,"mainEntityOfPage":27},"https:\u002F\u002Fschema.org","Article","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-andon-downtime-codes#article","Andon is on but nobody owns the stop? Downtime codes must close with the shift—not as “Other” later","zh-CN","2026-07-23","2026-10-17","MES · Manufacturing",{"@id":23},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":23},{"@id":26},"https:\u002F\u002Fwww.jedp.cn\u002Finsights#collection",{"@type":28,"@id":29},"WebPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-andon-downtime-codes",{"@context":14,"@type":31,"itemListElement":32},"BreadcrumbList",[33,38,42],{"@type":34,"position":35,"name":36,"item":37},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":34,"position":39,"name":40,"item":41},2,"Insights","https:\u002F\u002Fwww.jedp.cn\u002Finsights",{"@type":34,"position":43,"name":17,"item":29},3,{"@context":14,"@type":45,"@id":46,"mainEntity":47},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fmes-andon-downtime-codes#faq",[48,54,58,62,66],{"@type":49,"name":50,"acceptedAnswer":51},"Question","Are more downtime reason codes better?",{"@type":52,"text":53},"Answer","No. Classes 8–12 are usually sufficient for Class 1, and Class 2 is deployed on a device-by-device basis. After the category expands, only \"Other\" is selected on-site.",{"@type":49,"name":55,"acceptedAnswer":56},"Does waiting for material count as downtime?",{"@type":52,"text":57},"Count it as availability loss, with the cause attributed to 'material\u002Flogistics', and try to automatically pull up work orders with missing materials. Do not mix it with 'broken' due to equipment failure.",{"@type":49,"name":59,"acceptedAnswer":60},"Is changeover counted as downtime?",{"@type":52,"text":61},"Planned model changes enter scheduled downtime; losses occur if overtime. The planning window must be visible in the system, and it is forbidden to change overtime into planned afterward.",{"@type":49,"name":63,"acceptedAnswer":64},"How do Andon and maintenance work orders relate?",{"@type":52,"text":65},"Long stops should be able to switch to maintenance with one click; closing maintenance should write back the end of the stoppage. Each side records its own, MTTR is definitely false.",{"@type":49,"name":67,"acceptedAnswer":68},"How to prevent fake closes?",{"@type":52,"text":69},"The roles of closing person and calling person can be separated; key equipment requires production confirmation to restore. Only maintenance personnel are allowed to close, which may result in the light turning off while no one has arrived.","\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\">Andon\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Reason for shutdown\u003C\u002Fspan>\u003Cspan class=\"r-tag\">OEE\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Ch1>Andon is on but nobody owns the stop? Downtime codes must close with the shift—not as “Other” later\u003C\u002Fh1>\n        \u003Cp class=\"insight-lede\">The red light on the display board flashed for twenty minutes while the team leader was handling emergencies on another line; after recovery, the reason was recorded as 'Other.' Half of the loss categories in the weekly meeting go into 'Other' — improvements are unsure which area to tackle.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-meta\">\n          \u003Cspan>Updated 2026-07-23\u003C\u002Fspan>\n          \u003Cspan class=\"dot\" aria-hidden=\"true\">\u003C\u002Fspan>\n          \u003Cspan>~8 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>Call has a response time limit and escalation; if not answered within the time limit, a record is left; key equipment may require on-site confirmation\u003C\u002Fli>\u003Cli>Turn off mandatory reason codes; limit the proportion of 'Other' and require secondary explanation\u003C\u002Fli>\u003Cli>The reason codes share the same source as OEE availability; creating a separate downtime supplementary recording table is prohibited.\u003C\u002Fli>\u003Cli>Short stops can be combined (rules are public); long stops can be converted into a maintenance order with one click, closing and writing back ends the downtime\u003C\u002Fli>\u003Cli>First manage the dictionary and upgrade chain of a single line, then rank the entire factory and replace hardware.\u003C\u002Fli>\u003C\u002Ful>\n      \u003C\u002Fsection>\n\n      \u003Cdiv class=\"insight-layout\">\n        \u003Cdiv class=\"insight-body\">\n\u003Ch2 id=\"红灯很热闹-数据三个月后死亡\">Red lights look busy—the data dies in three months\u003C\u002Fh2>\n\u003Cp>Andon online: pull cord, light up, big screen. Three months later, operators found that even if they pulled it, no one came; team leaders discovered that reasons could be submitted blank; the maintenance hours of the equipment engineers were in another Excel sheet. The light is still on, but the data is dead.\u003C\u002Fp>\n\u003Cp>Shutdown management should be able to answer four questions:\u003Cstrong>Who responds, how long will it take, which category does the damage fall under, is there any prevention for recurrence\u003C\u002Fstrong>The four Q&A modules do not integrate into the system, and the Andon screen is just for decoration. Hardware can be purchased later; if the dictionary, time limits, and shutdown rules are not established, even replacing with a larger screen won’t save the 'others'.\u003C\u002Fp>\n\u003Ch2 id=\"呼叫链-时限写进规则\">Call chain: put SLAs into rules\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Step\u003C\u002Fth>\u003Cth>Minimum rule\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Call\u003C\u002Ftd>\u003Ctd>Workstation\u002FEquipment\u002FPhenomenon optional; timestamp automatic\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>response\u003C\u002Ftd>\u003Ctd>Target minutes; timeout escalation to team leader\u002Fdevice\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Arrive at the scene\u003C\u002Ftd>\u003Ctd>Key equipment can be confirmed by scanning the code, and 'remote click counts as attendance' is prohibited.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Close\u003C\u002Ftd>\u003Ctd>Reason code is required; long stop is associated with a maintenance order\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Verify\u003C\u002Ftd>\u003Ctd>Key workstations require the production line to confirm that production can start\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The night shift response time is configured according to the shift, and escalations go to the actual on-duty person, not the department's daytime email. If the duty roster is not entered into the organization, escalations will go to a dead number—this is a system issue, not entirely about attitude. Response timeouts must be recorded: without a 'timeout not answered' record, the weekly meeting can only scold people based on feelings.\u003C\u002Fp>\n\u003Cp>Pseudo shutdown management: The roles of the person shutting down and the caller can be separated; key equipment requires production confirmation for restoration. Only the maintenance side is allowed to turn off the light, which may result in the light being off while the person has not arrived and the line has not been activated.\u003C\u002Fp>\n\u003Ch2 id=\"其他-超过约-15-先停考核\">If “Other” exceeds ~15%, pause ranking first\u003C\u002Fh2>\n\u003Cp>Governance Signals:\u003C\u002Fp>\n\u003Cul>\u003Cli>\"Others\" proportion;\u003C\u002Fli>\u003Cli>Secondary blank rate;\u003C\u002Fli>\u003Cli>Repeated defect codes on the same device;\u003C\u002Fli>\u003Cli>Deviation between downtime duration and maintenance work order duration.\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>\"The 'other' category is often high because the dictionary cannot map the on-site language. First, co-create the dictionary with the team for two weeks, then discuss assessment. If assessment comes first, it will only train everyone to choose the easiest code to fill in.\"\u003C\u002Fp>\n\u003Cp>Dictionary changes must have versions: clearly specify the announcement effective date and whether historical data is reclassified. Changing the dictionary while ranking will lead the site to believe the rules are negotiable. It is recommended that primary codes have 8–12 categories, and secondary codes expand according to devices. The more categories there are, the higher the 'others' category tends to be—expansion itself is a sign of failure.\u003C\u002Fp>\n\u003Ch2 id=\"原因码示例骨架-可裁剪\">Sample downtime-code skeleton (trim as needed)\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Level 1\u003C\u002Fth>\u003Cth>Typical Grade II\u003C\u002Fth>\u003Cth>Frequent actions\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Equipment failure\u003C\u002Ftd>\u003Ctd>Electrical \u002F Mechanical \u002F Tooling\u003C\u002Ftd>\u003Ctd>Transfer to repair order\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Changeover \u002F Machine Adjustment\u003C\u002Ftd>\u003Ctd>On schedule \u002F Overdue\u003C\u002Ftd>\u003Ctd>Compare Plan Window\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Material \u002F Logistics\u003C\u002Ftd>\u003Ctd>Waiting for materials \u002F Wrong materials\u003C\u002Ftd>\u003Ctd>Related material shortage or called material list\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Quality stop line\u003C\u002Ftd>\u003Ctd>Batch Defective \u002F Pending Judgment\u003C\u002Ftd>\u003Ctd>Associated NCR\u002FIsolation\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Personnel\u003C\u002Ftd>\u003Ctd>Staff Shortage \u002F Skills\u003C\u002Ftd>\u003Ctd>Scheduling and Authorization\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Energy \u002F Environment\u003C\u002Ftd>\u003Ctd>Air Pressure \u002F Temperature and Humidity\u003C\u002Ftd>\u003Ctd>Facility Work Order\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Other\u003C\u002Ftd>\u003Ctd>A secondary explanation is required\u003C\u002Ftd>\u003Ctd>Weekly meeting zero pressure\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>This table is not the standard answer, but a reference scale for the 'Other' category when it expands. The on-site terminology is mapped into the second level, while the first level remains stable, so that history can be compared. Planned model changes must be checked against the system's planned window; retroactively changing overdue items to 'within plan' is a classic method of manipulating statistics.\u003C\u002Fp>\n\u003Ch2 id=\"与-OEE-排产-报工吃同一套停机\">Share one downtime record with OEE, dispatch, and labor booking\u003C\u002Fh2>\n\u003Cp>Availability loss must roll up from Andon\u002Fdowntime records—no separate OEE “downtime pad sheet.” Microstops (e.g. <2 min) may merge under published rules; kicking all microstops out of the denominator is how definition wars start.\u003C\u002Fp>\n\u003Cp>When waiting for materials causes a shutdown, try to automatically link it to line-side material shortage — otherwise, logistics losses may be recorded as equipment losses, causing the two departments to correct in the wrong direction. Long stoppages should be readable by the dispatch board: if equipment is unavailable, limit new dispatches, or have the shift leader confirm \"repair while working\" (explicit exception).\u003C\u002Fp>\n\u003Cp>Mutual undercutting between reporting work completion: It is still allowed to report completion normally during downtime, causing both progress and OEE to lie. At least one of the two rules should be chosen: either completion reporting is prohibited during downtime for that equipment; or reporting work must include the 'repairing while working' exception code. If neither is set, the red light is just for show.\u003C\u002Fp>\n\u003Cp>Long stop one-click conversion to maintenance order; maintenance closure backwrites stop end — recorded separately on both sides, MTTR must be false. There is a long-term deviation between downtime duration and maintenance hours, first check whether each records its own start and end times, then check whether anyone turned off the lights early.\u003C\u002Fp>\n\u003Ch2 id=\"班结-未关闭的停机不能-好看\">Shift close: open downtime must not look “clean”\u003C\u002Fh2>\n\u003Cp>If there are still Andons not closed at the end of a shift: block or strongly remind the end-of-shift process. Otherwise, the next shift inherits the red light, and the reason is left for the next shift to guess. The shift-end report lists: number of unclosed Andons, number of overdue responses, and the proportion of 'others' — three figures go into the morning meeting, which is more useful than buying a bigger screen.\u003C\u002Fp>\n\u003Cp>Top-level cause codes should be able to link to actions: maintenance countermeasures, process changes, and spare parts safety stock. If there is only a category without an action, filling in the code will be regarded as a discrepancy, and the data will collapse back to 'Other'. Duplicate defect codes should go to the equipment and process joint meeting, rather than only appearing in the shift leader's personal notes.\u003C\u002Fp>\n\u003Ch2 id=\"一条线-两周-三张数\">One line, two weeks, three metrics\u003C\u002Fh2>\n\u003Cp>Choose the most contested production line: enable overtime upgrades, disable mandatory reason codes, restrict 'Other'. Look at average response, the proportion of 'Other', and the downtime-maintenance correlation. If the three numbers don’t change, don’t replace hardware across the whole plant for now — hardware can be bought later, but the dictionaries and upgrade chain must be properly run first.\u003C\u002Fp>\n\u003Cp>Acceptance sample one shift: pick three long stops and confirm responder, arrival, reason code, work-order ID, and production clear-to-run; also check that shift’s “Other” share and open count. If they do not line up, stop expanding lines—a bigger board is only decoration.\u003C\u002Fp>\n\u003Ch2 id=\"与人员-备件-工艺变更的回链\">Link back to people, spares, and process changes\u003C\u002Fh2>\n\u003Cp>When the reason for downtime falls under 'personnel\u002Fskills,' it should be possible to pinpoint gaps in on-duty qualifications and authorizations—otherwise, the training plan will still be decided arbitrarily on an annual basis. When it falls under 'spare parts,' it should be possible to see whether there is a lack of safety stock or any open purchase requests; merely classifying it as 'equipment failure' without linking back to spare parts keeps improvements stuck at verbal commitments to replacing parts.\u003C\u002Fp>\n\u003Cp>In the first week after a process change, changeover\u002Fsetup overtime often increases. The dictionary should be able to distinguish between 'change implementation period' and 'steady-state overtime' to avoid permanently recording the implementation cost as poor team capability. The change order number can be attached to the downtime record, so that in weekly meetings, teams compete for resources rather than just passing the blame to each other.\u003C\u002Fp>\n\u003Cp>The reason for being Top has remained unchanged for two consecutive weeks with no action orders, indicating that Andon is still stuck at 'code filling.' The action order can be rough, but it must have a responsible person and a due date; without action, code filling will revert to been considered delayed.\u003C\u002Fp>\n\u003Ch2 id=\"计划停机与损失停机的边界\">Planned downtime vs loss downtime\u003C\u002Fh2>\n\u003Cp>Planned shutdowns (maintenance, planned model changes, energy inspections) must have a planned target and a time window; activities within the window are recorded as planned, while those outside the window are recorded as losses. A 'planned shutdown' without a planned target is hiding losses behind the back door of the plan.\u003C\u002Fp>\n\u003Cp>If maintenance exceeds the time and automatically reverts to the plan, the equipment department will lose the pressure to improve. Overflow minutes incur losses and allow associated maintenance order numbers — both retaining the plan semantics and not erasing the overtime.\u003C\u002Fp>\n\u003Ch2 id=\"多线共用维修力量时的升级\">Upgrade when multiple lines share maintenance resources\u003C\u002Fh2>\n\u003Cp>When two lines go red together, a per-line-only SLA pulls maintenance into “whoever yells loudest.” Shared pools need queueing and priority (safety stop > bottleneck > normal) with ETA on the Andon board. Without a visible queue, operators re-call, data fills with duplicate noise, and response time looks worse than it is.\u003C\u002Fp>\n\u003Ch2 id=\"数据可信的最低门禁\">Minimum gate for trustworthy data\u003C\u002Fh2>\n\u003Cp>Within two weeks of go-live, if codes can submit blank, close needs no arrival confirm, or OEE keeps a separate downtime sheet—any one of the three—turn off ranking boards first. Ranking on untrusted codes trains worse coding. Pass the gate before plant-wide benchmarking; until dictionary and escalation clear the gate, hardware spend can wait. Better buy the big board two weeks later than open rankings on untrusted codes.\u003C\u002Fp>\n\u003Cul>\u003Cli>MES manufacturing solution\u003C\u002Fli>\u003Cli>OEE three rates\u003C\u002Fli>\u003Cli>Scan code to report work collection point\u003C\u002Fli>\u003Cli>Line-side logistics docking WMS\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=\"#红灯很热闹-数据三个月后死亡\">Red lights look busy—the data dies in three months\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#呼叫链-时限写进规则\">Call chain: put SLAs into rules\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#其他-超过约-15-先停考核\">If “Other” exceeds ~15%, pause ranking first\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#原因码示例骨架-可裁剪\">Sample downtime-code skeleton (trim as needed)\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#与-OEE-排产-报工吃同一套停机\">Share one downtime record with OEE, dispatch, and labor booking\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#班结-未关闭的停机不能-好看\">Shift close: open downtime must not look “clean”\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#一条线-两周-三张数\">One line, two weeks, three metrics\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#与人员-备件-工艺变更的回链\">Link back to people, spares, and process changes\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#计划停机与损失停机的边界\">Planned downtime vs loss downtime\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#多线共用维修力量时的升级\">Upgrade when multiple lines share maintenance resources\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#数据可信的最低门禁\">Minimum gate for trustworthy data\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\u002F25-mes-aps-andon.html\">Matching resource kit: \u003Cspan>APS dispatch + Andon reason-code list\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>Are more downtime reason codes better?\u003C\u002Fsummary>\n          \u003Cp>No. Classes 8–12 are usually sufficient for Class 1, and Class 2 is deployed on a device-by-device basis. After the category expands, only \"Other\" is selected on-site.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Does waiting for material count as downtime?\u003C\u002Fsummary>\n          \u003Cp>Count it as availability loss, with the cause attributed to 'material\u002Flogistics', and try to automatically pull up work orders with missing materials. Do not mix it with 'broken' due to equipment failure.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Is changeover counted as downtime?\u003C\u002Fsummary>\n          \u003Cp>Planned model changes enter scheduled downtime; losses occur if overtime. The planning window must be visible in the system, and it is forbidden to change overtime into planned afterward.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How do Andon and maintenance work orders relate?\u003C\u002Fsummary>\n          \u003Cp>Long stops should be able to switch to maintenance with one click; closing maintenance should write back the end of the stoppage. Each side records its own, MTTR is definitely false.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How to prevent fake closes?\u003C\u002Fsummary>\n          \u003Cp>The roles of closing person and calling person can be separated; key equipment requires production confirmation to restore. Only maintenance personnel are allowed to close, which may result in the light turning off while no one has arrived.\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>OEE disagrees with the boss’s gut—split availability, performance, and quality definitions\u003C\u002Fh3>\n            \u003Cp>The root cause of OEE disputes is the inconsistency between planned production time, downtime classification, and first-pass yield count. Starting from the feeling that something is wrong, break down availability, performance rate, quality rate, and points of manipulation, and explain micro-stoppages, ideal cycle time, line transfers...\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-06-11 · ~9 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\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        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  \u003C\u002Farticle>",1793937990468]