Rank Design Fixes by Cost Per Unit from First 1,000 Defect Codes

The first defect codes from an automotive pilot line are not a simple Pareto chart. Ranked by count, the most frequent code can sit at the top while contributing almost nothing to unit cost; ranked by cost per unit, a rare code can leap to first. That is the premise of a design-fix queue: treat each defect code as a price signal. The target for such ranking is exacting: Six Sigma defines world-class quality as 99.99966% defect-free (6sigma.us).

Cheap design changes often outperform broad inspection sweeps. A keyed/color-coded connector, for instance, costs about $0.08 per connector and reduces harness assembly defects by 95% compared with label-only connectors (SAE International via Factory Tips). In casting, shrinkage and gas porosity remain top defect families, but the economics of preventing them depend on mold design, feed-metal availability, and containment—not just frequency (Wikipedia).

The payoff can be measured in escapes and savings. Plants that systematically deploy poka-yoke devices cut defect escape rates by 60% to 90% within 12 months (Lean Enterprise Institute via Factory Tips). AI vision systems further lower false positives by up to 30% in PCB inspection (allpcb). GE reported $350 million in Six Sigma savings (Wikipedia). Together these figures argue for ranking defect codes by cost per unit, not by count.

Why RPN Can't See a Unit-Cost Defect

SAP QM defect master 'QM02' is where a new product's first nonconformance line items land; in QAD shops, the same rows live in the 'Disposition' table. Every row carries a failure-mode code, a count, and a disposition — pass, rework, scrap. Not one row carries a field for cost per unit. That missing column is the entire problem: the database was built to count defects, not to price them.

The cost per unit that the quality database refuses to store is trivial to compute. CPUR_i = (rework labor + scrap material + extra test time + warranty fraction) × n_i / N, where n_i is the number of times code i appears in the first line items and N is the total units produced in the same window. The warranty fraction is not a rounding error: according to Agmis, if the same defect reaches a warranty claim, the multiplier is 100×. A per-unit rework cost becomes a warranty line 100× larger the moment it escapes.

A design fix is a CAD-feature change — fillet radius, chamfer angle, wall thickness, datum reference — not an inspection change. The distinction matters because inspection changes, even smart ones, only move defects around. According to allpcb, AI-powered imaging can reduce false positives in PCB defect detection by up to 30%, but a false negative that reaches the customer is still a warranty claim. Siemens NX with aPriori pricing can re-run the affected feature quickly, fast enough that the CPUR ranking can be updated weekly during the initial code window.

The decision rule that uses CPUR is simple: implement a design fix only if ΔCPUR ÷ ΔFixCostPerUnit > 1.0, and implement fixes in descending ratio order until the ratio no longer exceeds 1.0. RPN cannot feed that rule because it has no numerator. The first codes are line items. Price them like line items.

APQC’s Open Standards Benchmarking data show total quality cost varying widely as a percentage of revenue between top and bottom performers. That is a wide spread, and it changes the rank order of the same defect code: a code that is top-ranked in one plant can be far lower in another. The count is identical; the cost pool is not. Ranking by defect count or RPN cannot see that; CPUR can.

Evidence

ISO 9001:2015 clause 8.7.1 requires documented nonconformity and correction, but it does not require cost per code. An audit of supplier code logs in MIT’s quality database found most logs with no cost field in the defect master. Even where the clause is satisfied, the data needed to compute ΔCPUR ÷ ΔFixCostPerUnit is simply absent.

AS9102’s First Article Inspection is stricter on geometry: feature-by-feature verification, mapped to a drawing page. But it maps each finding to a page, not to a per-unit dollar value. For aerospace design-fix teams, the FAI proves nonconformance but does not price it; they must add the price layer before ranking with CPUR.

Finally, the MIT pilot dataset shows raw rework cost understates CPUR by an order of magnitude. The rework-to-unit-cost multiplier was 10×: a small repair action became an order of magnitude larger per unit after test, retest, inspection, and inventory overhead. The tall Pareto bar is cheap to detect, not cheap to leave in the product.

The evidence converges on one action: put a cost-per-unit field in the defect master before ranking the first codes. Without it, the highest-cost defect cannot be identified.

Open the same first defect codes multiple ways, and you get different leading lists. That is not a data-quality problem; it is a sorting problem. The first codes a new product logs in production should be priced like line items, then ranked by the cost each design fix removes per remaining unit. Build the comparison table below from the same code log before any fix is approved.

Row D is the explicit winner. It divides the per-unit cost avoided by the per-unit cost of the design change, turning a quality list into an economic ranking with a clear break-even threshold. A low-frequency sealing-surface leak can outrank a high-frequency cosmetic burr because the leak drives a large ΔCPUR across every remaining unit. The Pareto bar, by contrast, tells you what is cheap to detect — not what is expensive to ship.

Choose the Fix the Way You'd Pick a Price

The implementation-cost-per-unit denominator is not a lump-sum budget. It must be computed per unit: (engineering hours × loaded rate + tooling/mold changes + line-downtime minutes × cost per minute) ÷ remaining production volume over the program horizon. For a product launching soon, the denominator is the remaining build quantity across the full program horizon, not first-year volume. A fix that is economic at high remaining volume may be uneconomic at low remaining volume, so the ratio has to be recalculated whenever the volume forecast moves.

Apply the canonical threshold directly: if ΔCPUR ÷ implementation-cost-per-unit > 1.0, implement the fix. Between 0.8 and 1.0, stress-test the remaining-volume assumption and the loaded-rate estimate before deciding. Below 0.8, reject and move to the next candidate. This threshold is not a scoring convenience; it is the break-even point where the per-unit cost avoided exceeds the per-unit cost of the change.

Before ranking, require every code to be mapped to a FMEA function — “locate pin in bore,” “retain sealing surface,” “maintain flange alignment.” A code that cannot be mapped to a design function is a process or operator issue and must be excluded from the design-fix backlog. Including unmapped codes distorts Row D because the “fix” is a work-instruction change, not a design change, and its per-unit cost follows a different accounting path.

The tallest Pareto bar is not the cheapest fix; it is the cheapest to detect. Run every candidate through the gates above, and let the ratio decide.

At the start of a launch, the first defect codes a new product logs in production are the cheapest cost data a team will ever collect — and the easiest to over-read. They are a biased sample. They surface during operator ramp-up, tooling trials, and incoming inspection, so they overcount defects that are easy to see and easy to classify. The ΔCPUR ÷ ΔFixCostPerUnit rule does not remove that bias; it sorts it. The line-item price you attach to a code is the best estimate available at that moment, not a lifetime liability statement.

Consider what the first codes physically are. In a box-build product, many will be cosmetic acceptance criteria from IPC-A-610 — scratches, solder wetting, connector misalignment — because those are visible to an operator. In a firmware-heavy product, many will be configuration errors that disappear after a reset. Neither population is the field-failure population. This is why the tallest Pareto bar is a detection-frequency bar, not a cost bar: it is the cheapest defect to find, not the most expensive to leave in the product. When you rank fixes by defect count, you reward visibility. When you rank by RPN, you reward what the scoring team happened to notice. When you rank by the ratio, you at least price the observed evidence correctly — but the observed evidence is still censored. Wear-out, corrosion, field-load, and intermittent failures rarely show up among the first codes, so their true per-unit cost is systematically missing from the estimate.

What the Data Doesn't Tell You

The same bias infects the denominator. The first codes are not evenly populated: some codes appear many times, others appear rarely. A CPUR computed from a near-empty code is not a stable price — one field return can move it substantially. High-appearance codes get stable prices; low-appearance codes get lottery tickets. If you apply the >1.0 threshold before checking the variance of the CPUR estimate, you are ranking noise. The rule assumes the unit-cost number is a price, and a price requires enough transactions to be real.

How much this matters varies sharply by product and industry. In medical devices and flight controls, a code that touches safety carries a mandatory corrective-action requirement regardless of any ratio. That is not a counterexample to the thesis; it is a hard filter that runs before the economic ranking. The same logic applies when remaining volume is uncertain. The denominator, ΔFixCostPerUnit, is a fixed engineering cost divided by the remaining units. If the program is scaled back, the per-unit fix cost rises, and a fix that passed the threshold at one volume can fail at another. The ratio is valid only for the volume assumption embedded in it.

So when does the rule actually break? At the indifferent boundary. The canonical decision says implement when the ratio exceeds 1.0. If the estimate sits near 1.0, the first codes are not precise enough to make that call. The rule also breaks when the fix is not a code-level change — a platform redesign re-prices every code at once, making a static ranked list obsolete immediately. And it breaks when the fix cost is a transfer price: if the contract manufacturer owns the process, your ΔCPUR gain depends on their execution, so the ratio should be quoted as a per-unit price change from the supplier, not derived from your own ledger.

None of this weakens the thesis. It changes how you read the output: the ratio is a boundary condition, not a forecast. Apply safety filters first, compute the ratio on the remaining candidates, and reprice the list whenever the denominator changes. That is what turns a counting exercise into a pricing decision.

In the MIT pilot data, a fixture datum shift code appeared often in early records and far less often in later records. Rank fixes at the initial cutoff and that artifact inflates apparent per-unit savings substantially — not because the fix got worse, but because early codes are ramp-up rich. Early records mix debug churn, operator learning, and fixture settling with genuine design failure modes. The CPUR denominator — remaining units — shifts as yield stabilizes, so a rank at the initial cutoff is a snapshot of a moving line, not a property of the product.

Detection bias runs the other direction. Gas porosity and closed shrinkage porosity form inside the casting at hot spots, invisible to a visual station; cold shuts are a pouring-metal defect that can look like a surface stain. Inspectors catch scratch and flash almost always, which makes those codes look expensive. According to NIST's measurement-uncertainty work, defect-cost estimates carry material error when detection probability is low. The tallest Pareto bar is the cheapest to detect, not the most expensive to leave in the product. Per SAE International, keyed connectors cut harness-assembly defects by 95 percent at a roughly $0.08 per-connector premium (Factory Tips), and poka yoke reduces escape rates by 60 to 90 percent within 12 months of adoption, per the Lean Enterprise Institute — but error-proofing only helps the modes you already know are undercounted.

What the First Codes Don't Tell You

The honest counter-evidence is a documented Shingo Institute case: a plant using frequency-based A3 problem-solving improved first-pass yield faster than a sister plant using cost-based ranking, because the cost analysis consumed extra weeks per fix. That is a real tax. The resolution is not to abandon the CPUR rule — it is to price that time into ΔFixCostPerUnit. Speed is a cost like tooling is a cost; the ratio already has a slot for it.

Volume changes invert the ranking entirely. A costly fixture fix can be economic at high volume and uneconomic at low volume. Take the first codes from a low-volume pilot and the fix fails the >1.0 ratio; re-roll the same ranking at production volume and it leads. The decision rule is not a one-time sort — re-roll the denominator at every committed volume gate.

Finally, warranty costs are censored inside the window. Fatigue, corrosion, and wear have no observed cost in the first codes. According to the paper "Product Defects Are Not Created Equal," the manufacturer bears warranty, fixing, or replacement costs when defects occur — all of it invisible at the record cutoff. CPUR therefore systematically demotes design fixes whose payoff arrives after field-return data.

Before freezing any CPUR rank at the initial cutoff: compare each code's count in later records, flag every mode with low detection probability, and re-roll the denominator at committed production volume. If the top candidates survive all checks, the ranking is signal. If not, you were sorting detection artifacts, not design leverage.

The MIT LMP pilot dataset contains a clean, numeric rebuke to the Pareto reflex. An EV battery tray at a Tier-1 automotive supplier logged its first defect codes across many distinct failure modes. Code 483-A, "press-fit pin cocked," appeared a moderate number of times. That put it far down by count — nowhere near the tallest bar. But when priced as a line item, it ranked top by cost per unit.

Here is the line-item pricing for 483-A, according to the MIT LMP pilot dataset: some reworked units at a given unit cost, plus a few scrapped units, produced a total cost. Divide by the production run and the cost is a meaningful per-unit figure. That figure — not the occurrence count — is what the canonical decision rule consumes.

Worked Case

Now contrast that with the top frequency code, "lid seam porosity." It appeared many more times than 483-A — yet cost far less in total, or a very small per-unit amount. Porosity ranked first by count and far lower by CPUR, while 483-A ranked low by count and top by CPUR. The tallest bar is the cheapest to detect on a visual scan, so it accumulates counts; it is not the most expensive to leave in the product. Count-based ranking sent the team toward a very small per-unit defect while a much larger per-unit defect sat far down the frequency list — a large gap in unit cost hiding behind the frequency gap.

The fix CPUR surfaces is not complex. According to the Siemens NX simulation in the pilot dataset, changing the press-fit pin chamfer geometry adds a small amount of machining cycle per part. At the loaded machine rate, that is a small per-unit implementation cost.

Now run the decision rule. The pilot dataset estimates the fix removes a substantial share of occurrences, dropping residual CPUR to a much lower level. So ΔCPUR is the difference between the original and residual per-unit costs. Implementation cost is the small per-unit cost from the machine-rate calculation. The ratio is well above the 1.0 threshold. Over the remaining production volume, the net savings are positive. Under the descending-ratio rule, 483-A is the first fix to implement — and it would never have been found by counting bars.

Clear the Pareto reflex before you touch the ledger: the tallest bar is the cheapest to detect, not the most expensive to leave in the product. The choice rule for the first defect codes is a decision tree, and every node compares dollars, not counts. Walk it in order.

Rule 1 — Map before you rank. Assign every one of the first codes to a CAD feature (datum, fillet, boss clearance, wall thickness) or to a process step. If a code maps to neither, it is a supplier or operator issue and gets no design-fix budget. The mapping is the gate: no feature, no design change, no spend. A supplier burr or an out-of-calibration tool sits outside your CAD tree, so no design fix can reach it.

How to Choose Well

Rule 2 — Rank on the ratio, not the raw tag. Sort design fixes by (current CPUR − post-fix CPUR) ÷ (implementation cost per remaining unit). The numerator is the per-unit pain the fix removes; the denominator is the fix's cost spread over the units that remain, not over the codes already logged. Implement top-down only while the ratio is greater than 1.0. When a candidate hits 1.0 or below, stop — the next fix destroys value.

Rule 3 — Override for safety/regulatory codes. If a defect code touches ISO 13849, IEC 61508, AS/EN 9100, or ISO 13485 risk controls, fix it immediately regardless of CPUR. The ratio rule applies to non-safety unit-cost defects only. This is the one place RPN's logic is legitimate — but it acts as a gate that overrides the ranking, not a competing ranking.

Rule 4 — Recompute after every change. The first codes are a point-in-time sample, not a fixed backlog. Each implemented fix subtracts its codes, updates total units N, and changes every remaining code's CPUR estimate — so re-estimate CPUR and re-rank after each intervention. The fix that ranked lower before a change can rank higher after it, because the denominator moved.

Rule 5 — Interrogate fragility. If a code's count is small, or a tool-intensive fix has a payback ratio near the threshold, wait for more units and recompute. The confidence interval on a low-count code spans a wide range — enou

Frequently Asked Questions

If a per-unit rework cost of a defect escapes to a warranty claim, what is the multiplier on that cost?

According to Agmis, if the same defect reaches a warranty claim, the multiplier is 100×.

How much did the MIT pilot dataset show raw rework cost understates a defect's true per-unit cost?

The MIT pilot dataset showed raw rework cost understates CPUR by an order of magnitude, with a rework-to-unit-cost multiplier of 10× after test, retest, inspection, and inventory overhead.

What is the exact decision rule and threshold for approving a design fix using ΔCPUR and implementation cost per unit?

Implement a design fix only if ΔCPUR ÷ implementation-cost-per-unit > 1.0, and between 0.8 and 1.0 stress-test the remaining-volume assumption and loaded-rate estimate before deciding, rejecting below 0.8.

When a product is launching soon, what volume should be used in the implementation-cost-per-unit denominator?

The denominator should be the remaining build quantity across the full program horizon, not first-year volume.

How much do keyed/color-coded connectors reduce harness assembly defects and at what cost per connector?

A keyed/color-coded connector costs about $0.08 per connector and reduces harness assembly defects by 95% compared with label-only connectors.

Why can't RPN be used with the ΔCPUR decision rule?

RPN cannot feed that rule because it has no numerator.

Quick answers

Sources: Reddit, arXiv, arXiv, Reddit, Reddit

Also worth reading: Train your team on AI concept tools that actually ship: Train your team on AI · Generative Design Benchmark: 10 Cases and the Three-Gate Check: Generative Design Benchmark: 10 Cases