There is no single universal formula for the cost of a non-conformance in aerospace. What you can build is a structured, repeatable model that uses your existing MES/ERP/QMS data and a set of assumptions. The goal is not perfect accuracy, but a consistent way to compare and prioritize issues and investments.
1. Start with a clear cost-of-poor-quality structure
Most aerospace plants use a COPQ-style breakdown as a starting point:
- Internal failure costs: scrap, rework, MRB, inspections triggered by the NCR.
- External failure costs: returns, concessions, field repairs, penalties, program reputation impact.
- Appraisal/containment costs: extra inspections, special audits, temporary checks put in place to contain the issue.
- Prevention costs (optional in this estimate): engineering changes, training, fixture redesigns. These are often tracked separately from the NCR itself.
Decide which buckets you will always include in an NCR cost estimate and make that policy explicit. In regulated environments, consistency and traceability of assumptions matter more than precision on any one event.
2. Quantify the direct "visible" costs first
Direct costs are typically the easiest to estimate and to pull from existing systems.
- Scrap material cost
Use your ERP/finance item cost: unit cost × quantity scrapped. Include special processes or coatings if they cannot be salvaged.
Dependencies: accurate BOM costs and scrap booking practices.
- Rework labor
Estimate hours spent on rework × loaded labor rate (wages + burden). Hours should include:
- Operators doing rework
- Inspectors re-verifying
- Setups required only because of the NCR
Dependencies: time-tracking discipline, realistic standard times for rework operations, or at least a documented estimating guideline.
- Rework materials and consumables
Special tooling, replacement components, consumables (abrasives, chemicals, hardware) that are used only because of the NCR. These are usually small per event but can be significant for complex assemblies.
- MRB / engineering / quality analysis time
Estimate time spent by MRB, quality, and engineering on:
- Dispositioning the NCR
- Risk assessments
- RCCA / 8D or similar activities attributable to this issue
Multiply total hours by appropriate loaded rates or by a standard blended rate for "technical problem-solving hours."
For many plants, putting in place a simple template for these four elements already improves NCR cost visibility dramatically.
3. Add internal disruption and schedule impact where material
Internal disruption is harder to quantify, but for significant NCRs it often dominates the actual economic impact.
- Line stoppage / lost capacity
When an NCR halts a cell, line, or key machine, estimate:
- Duration of effective stoppage or slowdown
- Typical value-add per hour (often from OEE, revenue per capacity hour, or a proxy)
Cost impact ≈ hours of lost capacity × value per capacity hour.
Constraint: This is a model, not a GAAP number. Make its use explicit and use it mostly for prioritization.
- Expediting and rescheduling
Include extra changeovers, overtime, or premium freight specifically caused by the NCR. These are often visible already as separate cost codes in ERP or finance if your plant uses them.
- Work-in-process disruption
When the NCR affects assemblies already in flow, include:
- Extra handling / segregation operations
- Additional inventory days in WIP (if you cost inventory holding)
These are often rough-order estimates unless you have a mature value-stream accounting model.
4. Include external and customer-facing costs when applicable
In aerospace, the risk of external non-conformance is often far more consequential than internal scrap. You should distinguish between:
- Confirmed external events (e.g., field finding, return, or OEM escape):
- Direct repair or replacement cost (parts, labor, travel if field repair)
- Customer charges, fees, or penalties documented in contracts
- Additional inspections mandated by customer or regulator
- Potential external impact (e.g., escapes caught before flight or before delivery):
- Recall or containment activities in downstream plants or depots
- Data reviews and documentation updates required to demonstrate continued airworthiness or compliance
Many organizations choose to separate "accounting" cost from "risk" cost. For example:
- Use actuals (documented invoices, chargebacks, travel expenses) for the NCR cost record.
- Track potential or avoided cost in a separate risk/lessons-learned log, rather than in the NCR cost field itself.
This avoids mixing speculative risk numbers into financial reporting while still acknowledging the real exposure.
5. Use your existing systems, but accept brownfield limits
In most aerospace plants, NCR cost data is spread across multiple systems:
- ERP: material cost, scrap postings, labor bookings, freight, overtime codes.
- MES / digital travelers: where and when the defect occurred, rework operations, routing changes.
- QMS / NCR system: MRB decisions, defect classification, containment actions, 8D / RCCA records.
- PLM / change control: engineering changes, redesigned tooling or process updates.
Replacing these systems outright just to improve NCR costing is rarely realistic in regulated, long-lifecycle environments due to validation burden, qualification, and downtime risk. A more practical approach is:
- Define a standard NCR cost model (what to include, at what level of precision).
- Implement lightweight integrations or reports that pull a minimal data set from ERP/MES into the NCR record.
- Use standard fields and picklists in the QMS or MES NCR module so data can be analyzed over time.
- Validate only the data flows that matter for decisions and audit trails, not a fully automated costing engine from day one.
Expect some manual inputs to remain, especially for engineering and MRB labor time, disruption estimates, and special customer actions.
6. Make assumptions explicit and repeatable
Whatever model you use, document it. In regulated aerospace environments, auditors and customers will often ask "how did you come up with these cost numbers?" You should be able to show:
- Which cost elements must be filled out for every NCR.
- Which elements are only for major NCRs (e.g., line-stoppage cost, external impact).
- Standard rates and rules, such as:
- Loaded labor rate assumptions by role
- Default time estimates for typical MRB review steps, if actual time is not tracked
- How you assign disruption cost to a specific NCR when many issues occurred in a period
- Who can override or adjust estimates and how changes are documented.
This both improves internal decision-making and reduces friction during audits and customer reviews.
7. Use NCR cost data for trends and prioritization, not just "true cost"
Even with a disciplined approach, single-event NCR cost numbers will always be approximations. They are most powerful when used in aggregate:
- Identify top cost drivers by defect type, product, process, supplier, or cell.
- Compare internal vs external failure mix and track shift over time.
- Build a business case for automation, fixturing, digital work instructions, or supplier development using trend data rather than anecdote.
Be careful not to over-rotate on a single dramatic NCR cost. Focus on patterns supported by consistent data.
8. Practical starting template for an aerospace NCR
If you do not yet have a structured method, a simple, implementable template for each NCR is:
- Scrap cost: material + special process cost.
- Rework labor cost: rework hours × loaded rate.
- Rework material / tooling cost: parts and consumables.
- MRB / engineering / quality time: hours × blended technical rate.
- Disruption cost (if applicable): model-based estimate of lost capacity or premium freight.
- External / customer cost (if applicable): documented charges, returns, travel, or mandated inspections.
Sum 1–4 for a baseline internal NCR cost. Add 5–6 for full impact on significant events. Use clear flags in your system so you can analyze "baseline" and "full impact" separately.
9. Dependencies and limitations to acknowledge
When communicating NCR cost numbers internally, be transparent about:
- Data quality limits: missing labor bookings, inaccurate routings, or inconsistent scrap coding will reduce precision.
- Scope decisions: whether you exclude prevention costs or long-term reputation/contract impacts.
- Attribution challenges: when multiple issues affect the same schedule slip or disruption, cost allocation is a management decision, not a precise science.
- Validation boundaries: which parts of your costing approach are validated or relied on in formal reporting versus used only for operational decision support.
Being explicit about these constraints usually improves confidence in the data, because stakeholders understand what the numbers are and are not.