Home  /  Case Studies  /  Defect Reduction & SPC

Defect Reduction & Statistical Process Control (SPC)

Process Improvement

Research-backed case study: methodology, implementation, and measurable outcomes.

Executive Summary

A critical assembly line was experiencing a high defect rate that drove rework, customer complaints, and audit scrutiny. This case study documents a structured approach: root cause analysis using the 8D (Eight Disciplines) and 5-Why methods, implementation of Statistical Process Control (SPC) with calculated control limits, real-time Power BI dashboards for monitoring and alerts, and operator training on out-of-control response. The result was approximately 40% defect reduction, faster containment via automated alerts, and audit-ready SPC documentation.

  • ~40% defect reduction
  • Faster containment via automated alerts
  • Audit-ready SPC documentation

Context & Problem

The line in question was a high-volume assembly process where defects were discovered both in-process and at final inspection, and sometimes by the customer. Rework and scrap costs were rising, and customer quality scorecards were at risk. Management needed a data-driven response that would not only fix the immediate causes but also establish ongoing monitoring so that future shifts in the process could be detected and corrected before defects escaped.

Key challenges included: (1) multiple potential causes (material, machine, method, environment); (2) lack of real-time visibility into process stability; (3) reactive rather than preventive quality actions; and (4) need for documentation that would satisfy internal and external audits (e.g., IATF/ISO expectations around SPC and corrective action).

Methodology & Frameworks

The approach aligned with established quality frameworks and standards:

Implementation

After root causes were identified and short-term corrective actions were in place, SPC was rolled out for the critical characteristics that had the strongest correlation to the defects. Data was collected at the source (or pulled from existing systems) and fed into a data model. Power BI was used to build real-time control charts and a simple alert logic (e.g., flag when a point exceeded UCL/LCL or when run rules were violated). Dashboards were deployed to the floor and to quality/engineering so that everyone could see the same view of process stability.

Operator and supervisor training focused on: how to read the charts, when to stop and escalate, and how to document the response. This closed the loop between “data” and “action,” which is often where SPC initiatives fail. The SPC documentation (limits, revision history, response procedures) was organized so that auditors could easily verify that the process was monitored and that out-of-control events were addressed.

Outcomes

Lessons Learned

(1) Root cause analysis must be disciplined (8D/5-Why) so that fixes address causes, not symptoms. (2) SPC is only effective when the organization commits to acting on out-of-control signals; otherwise it becomes “wall art.” (3) Real-time dashboards (Power BI) made the data visible and actionable at the right level. (4) Training and clear ownership for response are as important as the statistics. (5) Keeping documentation in one place and linked to the QMS simplified audit readiness.

Related Reading

Deep dives on the methods and tools used in this case study: