Back to Blog
Smart Factory

Rework Never Shows Up in the Numbers: Managing Rework, Repair, and Scrap History with MES Routing

Final yield hides the labor and material spent on rework done beside the line. This post explains how to define rework, repair, concession, and scrap as formal MES routing paths, and how to use first pass yield and lot history to find and reduce the loss.

POLYGLOTSOFT Tech Team2026-10-187 min read2
Rework ManagementFirst Pass YieldScrap ControlMES RoutingHidden Factory

Why High Yield Doesn't Always Mean Profit

Some plants report a 99% final yield and still struggle to make money. Final yield only counts units that ended up good. It makes no distinction between a unit that passed the first time and one that was touched two or three times. The metric that exposes the difference is First Pass Yield (FPY).

If four processes each run at 95% FPY, the cumulative figure is 0.95 multiplied four times, or about 81.5%. Even with a reported final yield of 99%, roughly 18 out of every 100 units were handled again at least once somewhere on the line. That gap is often called the "hidden factory."

  • Invisible cost: Touch-up work done informally at a bench beside the line leaves no record of labor or material, so it never reaches the cost sheet.
  • Traceability risk: When reworked units ship mixed in with normal ones, a customer claim cannot be narrowed down, and you may have to recall the entire lot.
  • Designing Routing That Treats Rework as a Process

    The starting point is to put rework into the MES routing as a formal operation rather than an exception.

    Disposition paths after a defect

    When a unit is rejected, define four dispositions, each with its own next step.

  • Rework: Bring the unit back into specification, then return it to the original operation or to inspection.
  • Repair: Make the unit usable even though it does not fully meet specification, and record whether the customer approved it.
  • Concession (use as is): Accept the unit conditionally without further action, and record the approver and the scope.
  • Scrap: Deduct from inventory after approval.
  • Linking work orders and limiting rework

    Issue a dedicated rework order that references the original work order as its parent. The original order's results stay clean, and the labor and material spent on rework are collected separately. Add two rules on top of that.

  • Rework count limit: For example, a unit that exceeds two rework cycles for the same defect is routed automatically to scrap review.
  • Mandatory re-inspection: An interlock prevents a reworked unit from entering the next operation until it passes re-inspection.
  • What to Record

    The more fields you ask for, the more the shop floor avoids entering them. These are the essentials.

  • Defect data: defect type code, the operation where it occurred, and the operation where it was found
  • Rework data: action code, operator, labor time, and any additional material consumed
  • Identification: lot or serial number, and the rework cycle count
  • Once lot- and serial-level history is tied to shipment records, you can see immediately which customer received units that went through a given rework, and when.

    For scrap, timing is what matters. If parts have been physically discarded but remain in inventory, counts will not reconcile. If scrap is posted in bulk at month end, the loss lands in a different period from the one in which it occurred. Design the flow so that inventory deduction and loss posting happen at the moment scrap is approved.

    Using the Data to Reduce Rework

    As records accumulate, the location of the loss becomes visible.

  • FPY by operation and Rolled Throughput Yield (RTY): See which operation drags the cumulative figure down the most.
  • True profitability by item: Take an item with a standard labor time of 12 minutes per unit. If 15% of units are reworked at 8 minutes each, that adds an average of 1.2 minutes per unit, which is 10% of standard labor that was missing from the cost.
  • Prioritization: Rank defect types by rework labor hours, not by number of occurrences. The hours usually concentrate in the top two or three types, and those become your improvement projects.
  • Rollout Sequence and the POLYGLOTSOFT Approach

    Applying this to every operation at once tends to provoke resistance on the floor. We recommend the following order.

  • Reduce the entry burden: Identify lots by barcode scan and let operators pick defect and action codes from touch buttons, so a single entry takes only a few seconds.
  • Start with one operation: Pilot for a month or two at the operation with the most rework, and refine the code structure and disposition rules there.
  • Expand: Extend the proven rules to upstream and downstream operations and to shipment traceability.
  • POLYGLOTSOFT MES provides defect registration, disposition branching, rework orders, and lot traceability as its foundation. Routing rules and approval flows that match your process, along with ERP and accounting integration, are delivered through custom development. If you want to see the rework cost hiding behind your yield figure, contact POLYGLOTSOFT. We will work with you from shop-floor assessment through pilot deployment.

    Need Technical Consultation?

    Our expert consultants in smart factory, AI, and logistics automation will analyze your requirements.

    Request Free Consultation