[{"data":1,"prerenderedAt":71},["ShallowReactive",2],{"legacy:insights\u002Fmes-rework-scrap-status:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":70},"insights\u002Fmes-rework-scrap-status","Rework raised but progress still shows complete? Scrap and rework must enter the WO state machine—not only yield - JEDP Digital Platform","If only the quantities are changed for rework and scrapping, the progress, completeness, and cost will all be misleading. Nonconforming disposition must drive the work order status and the whereabouts of work-in-progress, and closure must be verified; when combined with QMS, isolate conclusions to write back to the execution chain.","MES rework, scrap flow, nonconforming disposition, WIP status","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-rework-scrap-status#article","Rework raised but progress still shows complete? Scrap and rework must enter the WO state machine—not only yield","zh-CN","2026-08-20","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-rework-scrap-status",{"@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-rework-scrap-status#faq",[48,54,58,62,66],{"@type":49,"name":50,"acceptedAnswer":51},"Question","Do minor floor reworks need a document?",{"@type":52,"text":53},"Answer","Set the threshold. Below the threshold, fast rework codes can be used, but still change the state in short cycles; everything relies on verbal communication, and progress is bound to fluctuate.",{"@type":49,"name":55,"acceptedAnswer":56},"Whose cost center takes rework hours?",{"@type":52,"text":57},"Default incoming work order cost, responsibility code distinguishes operation\u002Fmaterial\u002Fdesign. Rework that does not enter the cost will evaporate in the profit.",{"@type":49,"name":59,"acceptedAnswer":60},"Is first-piece inspection required after rework?",{"@type":52,"text":61},"Mandatory after key feature changes or process jumps are recommended. The first piece is qualified for repositioning to avoid \"rework completed one-time overstation\".",{"@type":49,"name":63,"acceptedAnswer":64},"Can scrapped material be reused?",{"@type":52,"text":65},"Only by concession\u002Fdowngrade. Downgraded products should be kept separate from regular stock, and scanning them as regular products is prohibited.",{"@type":49,"name":67,"acceptedAnswer":68},"How does this relate to CAPA?",{"@type":52,"text":69},"Repeated defect codes should trigger a quality escalation. The execution chain handles the current disposition, and the CAPA chain reissues it; if both sides are missing, it will only result in repeated rework.","\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\">Return to work\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Scrap\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Nonconformance Handling\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Ch1>Rework raised but progress still shows complete? Scrap and rework must enter the WO state machine—not only yield\u003C\u002Fh1>\n        \u003Cp class=\"insight-lede\">The final inspection judged it for rework, but the work order still showed 'Completed' on the reporting screen. The plan scheduled the next process as if it were completed, the warehouse prepared packaging as if it were completed, and quality counted the physical items in the isolation area. When the customer urged shipment—the system said it was fine, but the site said it was still being repaired.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-meta\">\n          \u003Cspan>Updated 2026-08-20\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>Unqualified judgments must change the work order\u002Fin-process status; it is forbidden to only change the number of good products.\u003C\u002Fli>\u003Cli>The rework route is short and rigid, and it passes through the rework process gate again before reporting work; the anti-skip station is also effective in the rework state.\u003C\u002Fli>\u003Cli>Scrap frozen batches\u002Ffrozen SN, block shipment and incorrect warehousing; when combined with QMS, isolate conclusions and write back to the execution chain\u003C\u002Fli>\u003Cli>Rework hours are by default included in the original work order cost; the assessment simultaneously considers both the rework occurrence rate and hidden rework audits\u003C\u002Fli>\u003Cli>First complete a closed-loop status for a high-frequency defect code, then expand to the entire process network.\u003C\u002Fli>\u003C\u002Ful>\n      \u003C\u002Fsection>\n\n      \u003Cdiv class=\"insight-layout\">\n        \u003Cdiv class=\"insight-body\">\n\u003Ch2 id=\"良率好看-发货照样拖\">Yield looks fine—shipments still slip\u003C\u002Fh2>\n\u003Cp>The weekly quality report shows an increase in the pass rate for each inspection, but the plan completion rate has declined. Breaking down the work orders: many 'completed' ones are actually 'pending rework' that were manually marked as finished, with the rework recorded in another log. The warehouse prepares boxes according to the system, but the physical items are still in the rework area.\u003C\u002Fp>\n\u003Cp>If rework\u002Fscrap is only a statistical field for quality purposes, the execution chain will pretend that the process is still progressing. Planning, warehousing, and costing are all reading the same lie. When first-pass yield is inflated by 'verbally fixing it before reporting completion,' the direction of improvement will also be skewed—the problem is pushed out of the system rather than being solved.\u003C\u002Fp>\n\u003Ch2 id=\"判定是事件-必须改状态\">Disposition is an event—it must change status\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Judgment\u003C\u002Fth>\u003Cth>Work Order \u002F Work in Progress Entry\u003C\u002Fth>\u003Cth>It must happen downstream\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Return to work\u003C\u002Ftd>\u003Ctd>Rework in progress \u002F Process awaiting rework\u003C\u002Ftd>\u003Ctd>Generate rework tasks or routing; original completion rollback\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Scrap\u003C\u002Ftd>\u003Ctd>Scrapped \u002F Isolated\u003C\u002Ftd>\u003Ctd>Freeze batch or freeze SN; prohibit shipping; material handling\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Concession acceptance\u003C\u002Ftd>\u003Ctd>Concession and passage\u003C\u002Ftd>\u003Ctd>Client\u002FQuantity\u002FTerm Structuring; Maturity Review\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Re-examination\u003C\u002Ftd>\u003Ctd>Pending re-examination\u003C\u002Ftd>\u003Ctd>After passing, exit the rework state and return to the designated main process node\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Only changing the 'nonconforming quantity' without changing the status is equivalent to telling the plan 'it can still be scheduled further.' Making concessions permanent and without a time limit is equivalent to writing the nonconformance strategy into the master data. Quick rework codes below the threshold can exist, but the status still needs to be changed for a short cycle—relying entirely on word of mouth, progress will definitely drift. 'Return to main process' is an exit condition, not a sixth type of long-term hanging business state.\u003C\u002Fp>\n\u003Ch2 id=\"返工路由-短-硬-可闸\">Rework route: short, hard, gated\u003C\u002Fh2>\n\u003Cp>Common breakpoints:\u003C\u002Fp>\n\u003Cul>\u003Cli>Still follow the original process, omitting necessary steps such as disassembly\u002Fcleaning\u002Frepair welding;\u003C\u002Fli>\u003Cli>The work reporting point is still at the original collection point, and the progress instantly jumps to full;\u003C\u002Fli>\u003Cli>Rework is automatically marked as completed without quality confirmation.\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Rework routing should be short and strict: the gate should be clear, and after completion, it should return to the designated main process node. Directly jumping to the endpoint is prohibited. Anti-jump stations are also effective in the rework state—otherwise, rework becomes a legitimate jump station path. After key feature changes or jumping stations, the first piece must be forced to go through production again before mass production.\u003C\u002Fp>\n\u003Cp>The reporting screen directly shows the next step: which station to go to, what to scan, and who will check it. Only issue quality notifications without changing the UI; rework status will be returned via verbal instructions. Rework must pass re-inspection or quality confirmation before returning to the main routing; 'complete rework and pass the station at once' is a hidden bypass.\u003C\u002Fp>\n\u003Ch2 id=\"报废与隔离-执行链咬住质量链\">Scrap and hold: execution must bite the quality chain\u003C\u002Fh2>\n\u003Cp>MES standalone scrap: At least freeze execution and inventory disposition. Combined with QMS: NCR isolation conclusions should be able to block station and outbound. MES scrapped, WMS can still ship — is one of the most expensive cracks across systems.\u003C\u002Fp>\n\u003Cp>Serialized items: The SN status follows the work order. It is prohibited for the same SN to be in \"Completed and Ready to Ship\" and \"Under Rework\" at the same time. Partial rework of batch items: split the quantum batch or mark the work-in-progress batch to avoid the entire batch being considered ready to ship. In case of conflict with the isolation strategy, the stricter freeze shall prevail.\u003C\u002Fp>\n\u003Cp>Downgrading and reuse must follow the concession\u002Fdowngrade process. Inventory attributes should be separated from genuine products, and scanning as genuine products is prohibited. Concessions must be structured with the customer scope, quantity, and term specified, and reviewed upon expiration—concessions without a term will become 'why is this batch still being shipped?' after six months.\u003C\u002Fp>\n\u003Ch2 id=\"与计划齐套-发货的接口\">Interfaces to planning kit and ship\u003C\u002Fh2>\n\u003Cp>Materials and capacity occupied by rework orders should be visible in the completeness and commitment calculations—otherwise, the plan will stock and package materials based on 'completion,' and missing parts will be discovered again once rework ends. Pre-shipment task verification: SN\u002Fbatch must not be in rework or scrap isolation.\u003C\u002Fp>\n\u003Cp>When a batch fails the random inspection and triggers the isolation of the entire batch: the in-process items that have not yet been inspected must also go into isolation or be temporarily held, and it is forbidden for some quantities to continue being reported as completed to affect the yield rate. If the promised delivery date is still externally based on the 'system completion,' sales will take the blame for the site — the state machine does not write back to the plan, which is the upstream of a reputation incident.\u003C\u002Fp>\n\u003Ch2 id=\"位置与成本-别留无主-WIP\">Location and cost: leave no orphan WIP\u003C\u002Fh2>\n\u003Cp>Rework items must have a system location (rework warehouse\u002Fline-side rework position); scrap items should go to the quarantine warehouse or scrap warehouse. The execution ledger and the storage ledger can be in separate systems, but the location semantics must be aligned—quality may say it is in the quarantine area, while the warehouse may say it is still at the line side, which will inevitably result in ownerless WIP during inventory.\u003C\u002Fp>\n\u003Cp>Rework hours by default go into the original work order cost, with responsibility codes divided into Operation\u002FMaterial\u002FDesign. Hours not included in cost, the team tends to 'complete the repair before reporting completion.' If the first-pass yield assessment does not take hidden rework into account, the data will push rework out of the system. At the same time, observe: rework occurrence rate, closure duration, and differences in verbal rework audits.\u003C\u002Fp>\n\u003Cp>Customer site rework: still write back to the original work order or create an after-sales rework order, and freeze the corresponding SN\u002Fbatch before resending. If the site repair is not written back, traceability and quality statistics will be systematically underestimated. Include the boundary between after-sales and MES in the scope description to avoid both saying 'closed'.\u003C\u002Fp>\n\u003Cp>Repeated defect codes should trigger a quality escalation into CAPA: the execution chain handles it immediately, and CAPA management handles recurrence. If both sides are missing, the production line will only rework repeatedly, and the first-pass yield looks very good on the report.\u003C\u002Fp>\n\u003Ch2 id=\"反模式清单-现场对照\">Anti-pattern checklist (shop-floor check)\u003C\u002Fh2>\n\u003Cul>\u003Cli>Verbal rework, system still completed;\u003C\u002Fli>\u003Cli>Return to the original process collection point for rework, progress jumps to full;\u003C\u002Fli>\u003Cli>Scrapping only changes the quality statistics, WMS can still issue;\u003C\u002Fli>\u003Cli>Concessions have no time limit and no customer scope;\u003C\u002Fli>\u003Cli>Rework hours are not included in the cost, and the first-pass yield looks very good;\u003C\u002Fli>\u003Cli>Rework status is not integrated with shipment verification, and the plan is to prepare boxes according to completed work.\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2 id=\"一个缺陷码-跑通闭环\">One defect code—close the loop\u003C\u002Fh2>\n\u003Cp>Select the most frequent defects: judgment → rework status → rework process → reinspection → return to main process. Check the number of false reports after completion, overdue rework work orders, and interceptions caused by scrap being erroneously issued. If the false reports cannot be reduced, do not roll out the 'intelligent rework recommendation' across the entire plant yet.\u003C\u002Fp>\n\u003Cp>Re-inspecting and sampling one batch for scrapping: both execution through the station and outbound were intercepted; sampling one batch for concession: the deadline and customer scope are readable, and there is a pending review when it expires. If both samples fail, don’t expand the line yet—expanding the line will only copy verbal rework to more work orders.\u003C\u002Fp>\n\u003Ch2 id=\"多工序串线与外协返工\">Multi-op lines and outsourced rework\u003C\u002Fh2>\n\u003Cp>If rework involves crossing workshops or outsourcing: the status must still be visible on the main work order, and the outsourcing section is handled using related tasks. Rework outsourced has no back-to-factory re-inspection checkpoint, which is equivalent to giving the 'completion right' of non-conforming products to external parties. Upon returning to the factory, a mandatory re-inspection point is implemented, and only if it passes will it return to the main routing.\u003C\u002Fp>\n\u003Cp>In a scenario of process chaining, if the upstream process has reported completion and the downstream process finds defects: the upstream completion should be rolled back or transferred to 'Pending Rework Association,' and the downstream process is prohibited from continuing to pull for completion as if the items are good. If both sides pretend to be complete, WIP and commitments will expand simultaneously.\u003C\u002Fp>\n\u003Cp>Cost: outsourced rework fees default to the original WO or a dedicated charge, but must roll up to defect and responsibility codes. Parking fees in “misc” with no defect key leaves quality improvement and supplier claims with nothing to grab.\u003C\u002Fp>\n\u003Ch2 id=\"隐藏返工怎么稽核\">How to audit hidden rework\u003C\u002Fh2>\n\u003Cp>Weekly抽certain proportion of 'one-time station' work orders: check whether the physical items have ever entered the rework area and whether the quality records show any signs of verbal rework. Audit differences should be reviewed with the team, rather than just being reported in the quality notice.\u003C\u002Fp>\n\u003Cp>If the pass rate rises while the rework rate and audit discrepancies also increase, it indicates that the assessment is rushing data into the system. At this point, first stop the 'pass rate ranking pressure' and first get the state machine and working hours into the system running properly—otherwise, applying pressure will only train people to falsify data.\u003C\u002Fp>\n\u003Ch2 id=\"让步放行的到期与追溯\">Concession expiry and traceability\u003C\u002Fh2>\n\u003Cp>Concessions that expire without review: automatically return to quarantine or block new shipments, and generate a quality to-do task. Upon expiration, only an email reminder is sent without preventing execution, turning the concession into a perpetual pass. The trace query must be able to list the issued SN\u002Fbatch by concession order number—when a customer complaint occurs and 'who approved this batch and which customer is limited' cannot be found, the frontline will bear the responsibility.\u003C\u002Fp>\n\u003Ch2 id=\"状态机最小集合\">Minimum status-machine set\u003C\u002Fh2>\n\u003Cp>There is no need to implement complex mesh processes all at once. A minimal set of states is sufficient:\u003Cstrong>To be reworked, Reworking, Pending re-inspection, Scrapped\u002FQuarantined, Concession release\u003C\u002Fstrong>; After qualifying, exit the rework state and return to the main process node. These five states cannot run properly; adding more recommendation algorithms just gives a verbal facelift to the rework. Weld the smallest set first, then discuss branching processes — if it cannot be drawn, do not expand the defect code range for now.\u003C\u002Fp>\n\u003Cul>\u003Cli>MES manufacturing solution\u003C\u002Fli>\u003Cli>Process Anti-Skip Station and SOP\u003C\u002Fli>\u003Cli>Non-compliant isolation cold storage stopped at the station\u003C\u002Fli>\u003Cli>Scan code to report work collection point\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=\"#良率好看-发货照样拖\">Yield looks fine—shipments still slip\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#判定是事件-必须改状态\">Disposition is an event—it must change status\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#返工路由-短-硬-可闸\">Rework route: short, hard, gated\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#报废与隔离-执行链咬住质量链\">Scrap and hold: execution must bite the quality chain\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#与计划齐套-发货的接口\">Interfaces to planning kit and ship\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#位置与成本-别留无主-WIP\">Location and cost: leave no orphan WIP\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#反模式清单-现场对照\">Anti-pattern checklist (shop-floor check)\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#一个缺陷码-跑通闭环\">One defect code—close the loop\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#多工序串线与外协返工\">Multi-op lines and outsourced rework\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#隐藏返工怎么稽核\">How to audit hidden rework\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#让步放行的到期与追溯\">Concession expiry and traceability\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#状态机最小集合\">Minimum status-machine set\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\u002F07-mes-work-order-dispatch.html\">Matching resource kit: \u003Cspan>Work order reporting exceptions + dispatch rule template pack\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>Do minor floor reworks need a document?\u003C\u002Fsummary>\n          \u003Cp>Set the threshold. Below the threshold, fast rework codes can be used, but still change the state in short cycles; everything relies on verbal communication, and progress is bound to fluctuate.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Whose cost center takes rework hours?\u003C\u002Fsummary>\n          \u003Cp>Default incoming work order cost, responsibility code distinguishes operation\u002Fmaterial\u002Fdesign. Rework that does not enter the cost will evaporate in the profit.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Is first-piece inspection required after rework?\u003C\u002Fsummary>\n          \u003Cp>Mandatory after key feature changes or process jumps are recommended. The first piece is qualified for repositioning to avoid \"rework completed one-time overstation\".\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Can scrapped material be reused?\u003C\u002Fsummary>\n          \u003Cp>Only by concession\u002Fdowngrade. Downgraded products should be kept separate from regular stock, and scanning them as regular products is prohibited.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How does this relate to CAPA?\u003C\u002Fsummary>\n          \u003Cp>Repeated defect codes should trigger a quality escalation. The execution chain handles the current disposition, and the CAPA chain reissues it; if both sides are missing, it will only result in repeated rework.\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>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          \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\">QMS · Quality\u003C\u002Fdiv>\n            \u003Ch3>NCR raised but goods still move? Isolation must freeze bins and block station pass\u003C\u002Fh3>\n            \u003Cp>Recoloring an NCR cannot stop picking or station pass. Start from the warehouse and line floor: how an isolation decision writes back once to the WMS lot\u002Fbin and the MES order, how concession is labeled under control, and how the inbound and in-process chains…\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-04-27 · ~10 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  \u003C\u002Farticle>",1793937990503]