Efficiency Indicator System —— How OEE Decomposition, FPY, and Value Stream Efficiency Indicators Work Together

1. Efficiency Indicators: Not Just an OEE Pie Chart

At operational meetings, when OEE is 75% — no one can clearly explain whether it's low availability, low performance rate, or low quality rate; while the quality department is reducing PPM, output per person and cost per unit hour are deteriorating.

An efficiency indicator system helps organizations break down waste, align improvement projects, and avoid misguidance from a single metric. It is not in opposition to quality indicators: the quality rate is one dimension of OEE; repeated rework harms both quality and efficiency.

2. Efficiency vs. Quality: Cause and Effect, Not Trade-offs

Recommendation: The value stream team should collectively manage RTY/FPY + OEE + cycle time, with the quality department providing quality loss breakdown.

3. Hierarchical Efficiency Indicators in Manufacturing

3.1 Equipment Level (OEE Decomposition)

• Availability = Operating time / Planned production time (downtime, changeover, material shortage)
• Performance = Actual output / Theoretical output (minor stops, speed reduction)
• Quality = Good units / Total output (startup scrap strategy must be consistent)

OEE = A × P × Q; improvements must first identify the weakest dimension.

3.2 Value Stream Level

• Cycle Time, Lead Time
• WIP Turnover Days, Line-side Inventory Value
• Changeover Time (SMED), First Piece Pass
• On-Time Delivery (OTD) — a composite of planning and execution efficiency

3.3 Factory / Corporate Level

• Output per Person, Labor Hours per Unit
• Energy Consumption / Material Utilization (linked with COQ)
• Order Commitment Achievement Rate

4. Quality-Related "Efficiency" Indicators

Note: The numerator and denominator definitions should be consistent across the company (e.g., whether FPY includes rework).

5. Example of an Indicator Tree (Discrete Assembly)

OTD ↑
 ├─ Plan Achievement Rate ↑
 ├─ Material Shortage Incidents ↓
 └─ Manufacturing Lead Time ↓
      ├─ OEE ↑ (A/P/Q)
      ├─ WIP ↓
      └─ FPY ↑
           ├─ Incoming PPM ↓
           └─ Process Cpk ↑

Improvement projects should be linked to a specific node on the tree to avoid the issue of "improvement activities being unrelated to KPIs."

6. Target Setting and Benchmarking

1. Collect 6-12 months of baseline data (avoid guesswork)
2. Set targets by customer/line (mixed product factories need stratification)
3. Define improvement magnitude (e.g., OEE +3pt annually, FPY +2pt)
4. Specify the percentage of data automatically collected (manual entry can lead to inaccuracies)
5. Yellow/Red thresholds trigger QRQC

7. Kanban and Meeting Rhythm

Top 5 Losses (Pareto) should be in a fixed format: reason classification, duration, DRI, status.

8. Relationship with COQ and Lean Tools

• External Failure COQ ↓ often accompanies FPY ↑, OEE Q ↑
• SMED improves the A dimension; minor stop improvements improve the P dimension
• Kanban supermarket improves WIP and Lead Time
• Efficiency projects must assess quality risks (e.g., skipping steps to speed up)

Articles on Cost of Quality (COQ) Management and Lean Logistics can be read in conjunction.

9. Common Pitfalls

Pitfall 1: One Global OEE Number Mixed production lines mask issues — report by line and product family.

Pitfall 2: Excluding Startup Scrap from Quality Rate Inconsistent with financial and customer reporting — define in the quality manual.

Pitfall 3: Efficiency Projects Not Validating Quality Complaints rise after speeding up — project closure must include 90-day FPY/complaint monitoring.

Pitfall 4: No Owner for Indicators Numbers look good or bad, but no one is accountable — clear RACI.

10. Implementation Checklist (Joint Quality/Operations)

1. Unify OEE, FPY, Lead Time definition manual
2. Select one pilot value stream, automatically collect MES data
3. Establish daily 15-minute loss review
4. Monthly Pareto update + improvement project pool
5. Management review input both efficiency and quality trends

11. Data Collection and Systems

Project: First connect one value stream for automatic data collection, then expand; define a data steward to manage criteria.

12. Template for Linking Improvement Projects to Indicators

Each lean/Six Sigma project charter must include:

• Associated KPI tree node (e.g., OEE-A dimension, FPY)
• Baseline / Target / Verification Period
• Quality Guardrail Indicators (e.g., complaints must not increase during the project)

13. Shift-Level OEE Loss Codes (Example)

Unified coding facilitates Pareto analysis:

The quality department should participate in defining Q codes to ensure production reports A/P but not Q.

14. Joint Reporting with COQ (4.3.1)

Management review should use the same page: external failure COQ trend + customer PPM + OEE quality rate + FPY — four lines moving in the same direction indicate win-win in quality and efficiency; if COQ decreases while OEE Q increases, verify the definitions are consistent.

15. Template for Pilot Value Stream Weekly Reports

• OEE (A/P/Q) and top 3 loss hours
• FPY / RTY compared to last week
• WIP value and completeness rate
• This week's improvement items and quality guardrail results

When benchmarking across multiple factories, standardize loss codes and OEE calculation boundaries (whether to include planned downtime, startup scrap) to prevent horizontal rankings from discouraging participation. The purpose of benchmarking is to share best practices, not to penalize through rankings.

16. Interface with TPM

Equipment availability (OEE-A) improvement projects should share TPM work order data; the quality department should monitor whether Q losses due to improper adjustments are included in TPM validation. During the ramp-up phase of new production lines, do not set OEE targets too early; first stabilize FPY and loss code accuracy before pursuing performance rates. Incorporating output per person and quality rate into the value stream manager's evaluation can reduce short-term behaviors of "sacrificing quality for output." During quarterly reviews, remove unused indicators to prevent indicator inflation on the kanban.

The value of the efficiency indicator system is to make "where the slow-downs are and where the losses are" visible, discussable, and improvable — not to gloss over issues with a single OEE number.

Before improvement, ask: Has the number of hours for the top reason in the last OEE loss Pareto changed this month? Who is responsible?

Knowledge Number: 4.3.3

Version: v20260702

Author: Quality Excellence Think Tank Quality Excellence Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously enhance their quality capabilities.