At the executive level, cost of poor quality (COPQ) must connect directly to financials, program risk, and capacity, not just defect counts. That requires disciplined definitions, reliable data sources, and controlled reporting structures that can survive audits and leadership changes.
Start with a finance-aligned COPQ structure
Executives care about how quality issues affect margins, cash, and program risk. A practical COPQ structure in aerospace typically groups cost into a handful of stable buckets:
- Internal failure costs: scrap, rework, reinspection, MRB disposition effort, re-certification, extra NDT, unplanned overtime due to defects.
- External failure costs: returns, concessions, warranty work, service bulletins, field retrofits, customer chargebacks, penalties, liquidated damages.
- Appraisal & containment costs: extra inspection, temporary sort, layered process audits triggered by issues, additional test cycles driven by defects or escapes.
- Systemic & prevention investments: corrective actions, process requalification, tooling rework, supplier development, training explicitly tied to CAPA or risk reduction.
These buckets should be developed jointly by finance, quality, operations, and program management so that COPQ reporting ties cleanly into the P&L and program cost baselines. If finance does not recognize the COPQ numbers, executives will discount them.
Define what is in and out of COPQ
In regulated aerospace environments, arguments about what “counts” can destroy credibility. Before scaling reporting, document:
- In-scope examples: rework hours booked to specific NCs, scrapped hardware with traceable lot/serial, customer returns with RMA numbers, penalty invoices, field retrofit campaigns.
- Out-of-scope examples: baseline qualification testing, planned inspection for regulatory compliance, planned training, and standard overhead that would exist even with zero defects.
- Allocation rules for shared work: e.g., MRB engineer time tagged to NCs vs generic engineering support.
- Capital vs expense: how you treat new fixtures, test equipment, or software purchased in response to quality problems.
Treat these definitions like controlled documents, with revision history and sign-off from finance, quality, and operations. Changing them without governance will break trend analysis and damage trust.
Use a small executive metric set
Executives do not need every detail. They need a stable metric set with clear interpretation and traceable drill-down. A common pattern is:
- Total COPQ as % of revenue (or % of program sales), trended.
- Internal vs external failure split, as % of COPQ and as absolute values.
- Top 3–5 COPQ drivers by cost (e.g., scrap on process family, major customers, key programs, or major suppliers).
- Structural indicators: e.g., rework hours as % of total direct labor, MRB backlog, rate of new significant nonconformances.
These should be consistent across business units whenever possible, even if the underlying processes, systems, and product mixes differ.
Anchor COPQ in traceable data sources
In brownfield aerospace operations, COPQ data usually lives across MES, ERP, PLM, QMS, and point tools. Executive reporting should be explicit about where numbers come from and where they are incomplete. Typical sources include:
- ERP: scrap value, write-offs, rework labor bookings, debits/credits, customer penalties.
- MES / shop-floor systems: defect codes, rework cycles, work-center-level rework hours, re-inspection activity.
- QMS / NC & CAPA system: nonconformance counts and severities, MRB outcomes, escape events.
- Field / service systems: warranty claims, service bulletins, retrofit campaign costs.
- Timekeeping / labor systems: MRB time, quality engineering time, inspection overtime tied to events.
Do not claim COPQ is “comprehensive” if you are only capturing what flows through one system. Instead, clearly label coverage (for example, “current COPQ view includes internal scrap and rework in machining and assembly; external field costs not yet integrated”).
Show trend, not just a single COPQ number
A single COPQ figure for a year or quarter is of limited value. Executives need to see:
- Trends over time: 12–24 months minimum, by total COPQ and by key buckets.
- Mix shifts: internal vs external failures, by program, by facility, by supplier tier.
- Change events: major new programs, production ramp-ups, transfers, system go-lives, or regulatory findings that affect comparability.
Mark on the timeline where you changed definitions, integrated a new system, or closed a major CAPA. This is critical context when interpreting apparent improvements or regressions.
Link COPQ to programs, customers, and constraints
In aerospace, COPQ is as much a program and customer issue as a plant issue. Executive reporting should:
- Break out major programs and customers: show which programs carry disproportionate COPQ and why (HTOL, new technology, immature supply chain, qualification churn).
- Highlight contractual exposure: damages, concessions, and reliability metrics where poor quality translates quickly into cash or reputation risk.
- Connect to capacity and schedule: show rework and MRB time as a constraint on rate, not just a cost line. Executives need to see where quality is limiting deliveries.
Avoid “blame charts” focused on a single plant or supplier without acknowledging design complexity, qualification requirements, and customer-driven changes that drive COPQ.
Explain what you are doing about it
COPQ at the executive level must be tied to meaningful action, not just monitoring. Each reporting cycle should connect:
- Top cost drivers to specific CAPAs, process improvements, or supplier interventions.
- Expected vs realized impact of major actions: what COPQ components you expect to move, by when, and what has actually moved.
- Residual risk: where you expect COPQ to stay elevated due to design maturity, customer change tempo, or upcoming regulatory changes.
Be explicit when actions are constrained by regulatory validation, required requalification, long tooling lead times, or customer sign-offs. Executives need to see which levers are realistically available.
Be honest about measurement limits and brownfield realities
Most aerospace organizations cannot calculate a perfect, all-in COPQ number because of:
- Fragmented systems: multiple ERPs, legacy MES, local Access/Excel tools, manual logs, and disconnected QMS instances.
- Poor historic tagging: labor and material not consistently booked against NCs or CAPAs.
- Long product lifecycles: field costs appear years after production, and attribution to original causes is often partial.
At the executive level, it is better to present a clearly bounded view (for example, “these figures cover 80% of revenue and internal failures only”) than to inflate numbers based on aggressive estimates. Overstated or opaque COPQ undermines both credibility and decision-making.
How to phase in COPQ reporting without a full system replacement
Trying to build “perfect COPQ” by replacing ERP, MES, or QMS in one move is usually unrealistic in regulated aerospace. Qualification burden, validation cost, downtime risk, and integration complexity make big-bang replacement strategies high risk and slow.
A more workable approach for executive-level COPQ reporting is:
- Pilot on a critical value stream: choose one plant or program where data is reasonably structured; define COPQ categories and extraction methods there first.
- Stabilize definitions: get finance and quality to sign off on what counts, how you value scrap, how you book rework, and how you treat shared engineering/QA time.
- Integrate minimally: start with controlled extracts or interfaces from existing ERP/MES/QMS rather than replacing them. Validate every transformation step.
- Scale by pattern, not by system: reuse the metric structure and data mapping logic across sites and systems, accepting some local variation where legacy constraints are immovable.
This keeps COPQ reporting aligned with existing validated systems and change-control practices, rather than introducing a parallel shadow stack that cannot withstand audit or certification scrutiny.
What executives should ask when reviewing COPQ
To keep measurement and reporting rigorous, aerospace leaders can consistently ask:
- Which systems and plants are included and excluded in these COPQ numbers?
- How do these numbers tie to our financial statements and program baselines?
- What changed in definitions or data sources this period compared with last?
- What 3–5 structural drivers are responsible for most of this COPQ, and what is the concrete plan and timeline to address them?
- Where are we constrained by regulation, qualification, or customer approvals in reducing COPQ quickly?
Consistently using these questions helps keep COPQ reporting grounded in traceable facts, realistic levers, and the actual constraints of aerospace production.
