Estimating the cost of a non conformance (NC) is less about finding a single “correct” number and more about defining a consistent, transparent cost model you can apply across events. The goal is to be accurate enough for decisions, comparable across incidents, and defensible during internal and external scrutiny.
Start with a clear purpose and level of precision
Before building a model, decide what the estimate will be used for:
- Prioritization only: relative cost bands (e.g., <$1k, $1k–$10k, >$10k) may be sufficient.
- Management reporting: more detailed, but still based on standard rates and assumptions.
- Business case / CAPEX / customer claims: requires traceable calculations and documented assumptions, often cross-checked by finance.
In regulated environments, higher precision also means higher validation and governance effort. Be explicit about the intended use in your procedure.
Break the cost into standard components
A practical NC cost model usually has these buckets:
- 1. Direct material and labor
- 2. Direct overhead on affected operations
- 3. Investigation and containment effort
- 4. Customer, supplier, and logistics impact
- 5. Regulatory, quality system, and documentation impact
- 6. Special cases and risk-driven adders (e.g., field actions, scrap of unique assets)
Most plants standardize what is always included, what is included only above a threshold, and what is explicitly excluded (for example, long-term reputational impact that cannot be credibly quantified).
1. Direct material and labor
This is usually the most straightforward category and can often be semi-automated if your ERP/MES and QMS are integrated.
- Scrap cost: quantity scrapped × standard material cost (including allocated burden if finance requires it). In brownfield environments, this typically comes from ERP item master or standard cost tables.
- Rework cost: rework labor hours × fully loaded labor rate, plus any extra material or tooling consumed only because of the NC.
- Downgrade / concession cost: difference between planned selling price and actual realized price for downgraded or reworked product.
Dependencies and constraints:
- Requires reasonably accurate routing data and labor rates in ERP/MES.
- If actuals are not available, define standard rework times by defect type and use those consistently.
- Validated systems may limit how quickly you can change rates or costing logic; document assumptions in the NC record.
2. Direct overhead and equipment impact
In high-capital environments, machine time is often more valuable than direct labor.
- Lost capacity: hours of machine time lost × standard machine-hour rate (agreed with finance).
- Changeovers and setups due to NC: extra setups or changeovers that would not have happened without the NC.
- Tooling and fixtures: premature tool wear, broken fixtures, or special tooling made to salvage nonconforming parts.
Be cautious not to double-count overhead if it is already baked into your labor or standard material rates. In many plants, a simple rule is used, for example: overhead as part of standard cost only, unless there is provable extra downtime or capacity loss directly tied to the NC.
3. Investigation, root cause analysis, and containment
These costs are often underestimated and rarely fully captured in transactional systems.
- Containment: sorting, 100% inspection, quarantine management, extra sign-offs, temporary work instructions.
- Investigation / RCA: engineer, quality, and operations time spent on problem solving and documentation.
- Meetings and reviews: MRB, customer reviews, cross-functional war rooms.
Typical approach when detailed time tracking is not feasible:
- Define standard hour ranges per NC severity level or per defect type (for example, Minor = 2 hours, Major = 8 hours, Critical = 40+ hours across functions).
- Apply a blended fully loaded rate per role (operator, engineer, quality, manager).
Document in your NC procedure how these standard times are assigned; this makes the estimates repeatable and auditable even if they are approximate.
4. Customer, supplier, and logistics impacts
These often matter more than internal scrap when the NC affects delivery or field performance.
- Customer returns / complaints: replacement product cost, return freight, processing time.
- Expedite costs: premium freight, overtime, or out-of-sequence builds to recover schedule.
- Penalties and credits: contractual penalties, price concessions, or service credits.
- Supplier issues: inspection of supplier lots, extra qualification testing, and any non-recoverable portion of supplier-caused scrap.
Constraints:
- Financial penalties and credits often sit in separate systems from QMS/MES and may require manual coordination with finance or commercial teams.
- In many plants, these are only included above a certain dollar threshold or for defined NC categories.
5. Regulatory and quality system costs
In regulated sectors, some NCs trigger significant additional effort.
- Additional testing / validation: non-routine tests, protocol writing, review cycles, and reporting.
- Regulatory reporting activities: time to prepare, review, and respond to regulator or customer oversight, where applicable.
- Documentation and system changes: updating controlled documents, revising validated work instructions or software configuration, and associated change control.
These are typically estimated with standard effort buckets by NC category, because tracking every hour in validated systems is rarely practical. Ensure that any changes to calculation logic go through formal change control if they affect validated reports or dashboards.
6. Special cases and risk-based adders
Not every cost is easily quantifiable. For high-risk NCs, some organizations include additional categories:
- Field remediation campaigns: planned hours and logistics for site work, inspections, or retrofits.
- Obsolescence or write-off of unique items: scrapping custom tooling, jigs, or long-lead components with no alternative use.
- Project-level delay costs: only when there is a clear, documented link between the NC and measurable project impact (extra project management, schedule slippage costs agreed with finance).
These should be used sparingly and with documented assumptions, especially where customer or regulatory bodies may review the rationale.
Define a repeatable estimation workflow
To make NC cost estimation practical in brownfield, regulated environments:
- Standardize severity and categories: align NC types and severities with predefined cost logic (for example, via templates in your QMS).
- Use standard rates and times: define and periodically review standard labor rates, machine rates, and typical effort by NC type.
- Automate where data is reliable: pull scrap quantities, standard costs, and labor hours directly from ERP/MES where integration and data quality are adequate.
- Keep manual inputs simple: limit required manual estimates to a small number of fields (for example, extra investigation hours, extra inspections performed).
- Separate estimated vs. actual: allow an initial estimate for prioritization, then a later update if actuals are available and material.
Each step that touches validated or regulated systems should follow formal change control and, where required, revalidation of reports or calculation logic.
Recognize system and data limitations
The accuracy of NC cost estimates is constrained by:
- Data availability: legacy MES/ERP/QMS often do not capture all the time and cost drivers needed for precise calculation.
- Integration quality: misaligned item masters, routings, or cost centers can bias estimates if data is pulled automatically.
- Process maturity: if operators and engineers do not consistently record containment or rework activities, the model will undercount these costs.
In many plants it is better to accept a conservative, clearly documented approximation than to delay action while chasing theoretical precision.
Why not build a single “true cost” system?
In long-lifecycle, regulated environments, a full replacement of costing and quality systems to get perfect NC cost data usually fails or is not economical:
- Qualification and validation burden: cost calculation logic inside validated systems is hard to change and re-qualify.
- Downtime risk: replacing core ERP/MES/QMS for costing purposes alone rarely justifies the risk to production and compliance.
- Integration complexity: different plants, business units, and legacy systems encode cost elements differently.
A more realistic approach is to layer a cost estimation model on top of existing systems, using exports, data marts, or reports, and refine it via continuous improvement.
Practical starting model
If you need a pragmatic starting point, many organizations begin with:
- Direct cost: scrap + rework (material and labor) from ERP/MES.
- Standard investigation/containment adder: severity-based hours × blended rate.
- Expedite / penalty adders: only when above a threshold and confirmed by finance or commercial.
They then review a sample of NCs quarterly with operations, quality, and finance to calibrate the standard assumptions and adjust the model gradually, under change control.
