First-pass yield (FPY) should be a primary signal of process health and cost of poor quality in aerospace dashboards, but not the only or dominant performance metric. In regulated, high-mix aerospace environments, FPY is most useful when it is:
- Defined consistently across plants and systems
- Traceable to nonconformances and rework records
- Segmented by product, process, and supplier
- Explicitly connected to cost, schedule risk, and compliance exposure
Use FPY as a leading indicator, not a scoreboard
FPY belongs on executive and area-level dashboards as a leading indicator of process capability and stability. It helps answer:
- Where are we bleeding time and capacity due to rework and scrap?
- Which routes, cells, or suppliers generate the most nonconformances?
- Are recent changes (program ramp, new NC programs, updated work instructions) degrading capability?
FPY should complement, not replace, metrics such as on-time delivery, NPT, NCR rates, and COPQ. Overweighting FPY can push teams to under-report issues or push defects downstream to protect the metric.
Anchor FPY to NCRs, rework, and traceability
In aerospace, FPY only has real value if it aligns with formal quality records and traceability:
- Link FPY to NCR data: Every failure that breaks “first-pass” should have a corresponding nonconformance, concession, or repair record. If FPY trends improve while NCR volume, escapes, or MRB workload stay flat or rise, your FPY data is not trustworthy.
- Distinguish rework vs. scrap: FPY alone hides severity. A dashboard should show FPY alongside scrap rate, rework rate, and disposition mix (use-as-is, rework, repair, scrap).
- Maintain genealogy: FPY should be traceable at least to work order, lot/batch, and serial number levels, so you can drill from a bad FPY trend to specific operations, machines, programs, or shifts.
This typically requires integration between MES, QMS/NCR systems, and sometimes PLM (for revision context). In brownfield environments, incomplete interfaces and manual workarounds often break this link; dashboards should make that limitation visible rather than hiding it.
Segment FPY to reflect aerospace reality
High-level plant FPY in aerospace is usually misleading. To make FPY actionable, dashboards should segment it by:
- Program / platform: New, complex programs (or rate increases) will naturally have lower FPY than stable legacy work. Mixing them obscures risk.
- Operation / process family: E.g., machining vs. special processes vs. assembly vs. test. This allows targeted problem solving.
- Part family / criticality: Distinguish FPY on high-criticality or key characteristics from non-critical hardware, even if formal classification lives in PLM or FAI data.
- Supplier vs. in-house: For make/buy mixes, separate FPY for internal processes vs. incoming quality from key suppliers.
- Planned vs. unplanned work: Overhauls, BER (beyond economical repair), or developmental hardware will show very different FPY profiles than repeatable production.
Without this segmentation, FPY can look “acceptable” while masking pockets of severe scrap, late NCRs, or repeated concessions on specific programs.
Expose the tradeoffs: cost, schedule, and compliance
On aerospace dashboards, FPY should be interpreted in the context of three major risk dimensions:
- Cost: Show FPY together with scrap cost, rework hours, and MRB backlog to quantify cost of poor quality. A slight FPY improvement that requires extensive inspection or extra handling may not be a net win.
- Schedule: Low FPY on bottleneck processes or critical paths has disproportionate impact. Dashboards should highlight FPY at capacity constraints, not just overall averages.
- Compliance and escapes: Artificially high FPY driven by weak detection or pressure to “keep parts moving” increases escape risk. FPY should never be improved by bypassing controls, soft dispositions, or misclassifying rework as normal work.
Operators and supervisors should see enough detail to understand these tradeoffs, while leadership views should summarize them in a way that drives realistic decisions on investment, staffing, and process changes.
Beware behavior distortion and data quality issues
In regulated environments, FPY metrics can easily drive unintended behavior.
- Under-reporting: If FPY is tied to bonuses or supplier scores without safeguards, teams may avoid logging NCRs or categorize defects as minor to protect FPY.
- Hidden rework: Technicians may “fix on the fly” without recording rework operations, overstating FPY and undermining traceability.
- Gaming routing definitions: Plants may add or remove operations, or re-label steps, to make FPY look better rather than fixing the underlying process.
Dashboards should explicitly surface data quality signals: FPY should be reconciled against cycle time, material usage, and NCR volume. Incongruities should trigger review, not be ignored.
Make FPY coexist with legacy MES, ERP, and QMS
Most aerospace sites cannot replace core MES or QMS systems just to fix FPY reporting. Dashboards need to handle messy reality:
- Multiple data sources: FPY may require combining operation completion data from MES, work order status from ERP, and NCR data from QMS. Interfaces are often partially manual or batch-based.
- Inconsistent definitions: Plants may disagree on what counts as a “first pass.” Implementation should start by documenting and harmonizing definitions, at least for key value streams.
- Validation burden: In aerospace, any derived metric that informs decisions may need documented logic, change control, and validation. FPY calculations and transformations in BI tools should be versioned and reviewable.
- Limited downtime: Re-plumbing routing or operation structures just to make FPY “perfect” is rarely justified. Often it is better to accept partial coverage and call it out explicitly on the dashboard.
Rather than replacing platforms, many sites overlay FPY dashboards that read from existing stacks, with clear caveats about coverage and assumptions. This avoids requalification of core systems while still improving visibility.
How to position FPY on the dashboard
In practice, FPY should play the following roles:
- Top-level view: A small number of FPY tiles by program or value stream on executive dashboards, always paired with scrap/rework cost and NCR trends.
- Operational view: Detailed FPY by process family, cell, or line, with drill-down to operations and recent nonconformances.
- Continuous improvement view: Before/after FPY trends for specific improvement projects, process changes, or tooling introductions, validated against NCR and COPQ changes.
If FPY is the largest number on the page, it should also be the most explainable: users should be able to click from the metric to the underlying work orders, operations, and NCRs that created it.
Connecting to broader aerospace performance and compliance
For aerospace programs concerned with AS9100 and AS9102 expectations, FPY is not a formal compliance requirement, but it strongly influences:
- The volume and severity of nonconformances and MRB workload
- The stability of processes after first article inspection and qualification
- The credibility of your quality management system during audits
Dashboards should therefore treat FPY as operational evidence of process control, not as proof of compliance. A plant can show high FPY and still fail an audit if traceability, documentation, and change control are weak.
If your question is driven by misleading “scoreboards”
Where current dashboards show a single plant-level FPY or scrap percentage and leadership is dissatisfied, FPY should be repositioned as a diagnostic metric rather than a simple grade. That usually means:
- Separating FPY by program, process family, and supplier
- Linking every FPY trend to concrete NCR, rework, and cost data
- Documenting how FPY is calculated in each system and what it does not cover
Over time, this approach tends to reduce surprises (e.g., sudden capacity crises or escalation of escapes) more than chasing a single “plant FPY” target ever will.
