Sigma Level Calculation converts defect performance into a sigma metric that summarizes process quality on a common Six Sigma scale.

Back to BoK Index
Six SigmaDPMOCapability

Definition

Sigma Level Calculation estimates how many standard deviations fit between process performance and the nearest defect threshold, or converts DPMO and yield into an equivalent sigma score. It is a communication metric for defect performance.

Sigma level must be interpreted with clear definitions for units, defects, opportunities, yield, and any long-term shift convention.

History

Sigma level reporting became widespread through Motorola and later Six Sigma deployments. It helped executives compare defect performance across very different processes, but it also created misuse when opportunity definitions were inflated or assumptions were hidden.

When to Use

Use Sigma Level Calculation to communicate baseline defect performance, compare processes at a high level, track DMAIC gains, or translate DPMO into a common language. Use capability analysis when continuous process distribution and specification limits are central.

Step-by-Step

  1. Define the unit of work or product.
  2. Define defect and opportunity carefully.
  3. Collect representative defect and unit counts.
  4. Calculate DPO, DPMO, or yield.
  5. Convert the value to sigma level using the selected convention.
  6. Document assumptions, timeframe, and data source.
  7. Stratify results if different processes are mixed.
  8. Use the metric to guide improvement priorities and verify results.

Examples

  • Manufacturing: Defects per opportunity are converted to DPMO and sigma level.
  • Healthcare: Medication-order errors are reported as opportunities and defects.
  • Finance: Invoice defects are tracked before and after a DMAIC project.

Common Pitfalls

  • Inflating opportunity counts to make sigma level look better.
  • Mixing defect counts with defective-unit counts.
  • No statement of shift convention.
  • Using sigma level without customer-risk context.
  • Combining unrelated work streams.
  • Ignoring measurement and data-collection quality.

Related Tools

Further Reading