Defects Per Million Opportunities (DPMO)
Last updated: Oct 25, 2025
What is Defects Per Million Opportunities?
Defects Per Million Opportunities measures how many defects you find for every one million chances a defect could occur in your process. It is a core Six Sigma quality metric that accounts for the complexity of a product by counting the number of possible defect points on each unit. You use it to compare processes with different designs, track quality over time, and translate defect rates into a Sigma level.
Defects Per Million Opportunities Formula
How to calculate Defects Per Million Opportunities
You inspect 5,000 units. Each unit has 3 defined opportunities for a defect. Inspectors record 28 total defects across all units. DPMO = 28 / (5,000 x 3) x 1,000,000 = 28 / 15,000 x 1,000,000 = 1,866.7 You would report 1,867 DPMO.
Start tracking your Defects Per Million Opportunities data
Use Klipfolio PowerMetrics, our free analytics tool, to monitor your data.
Get PowerMetrics Free
What is a good Defects Per Million Opportunities benchmark?
Six Sigma quality is commonly equated with about 3.4 DPMO using the traditional long-term shift assumption. Outside of that convention, meaningful benchmarks vary by industry, product risk, and inspection rigor. Most teams set internal targets by establishing a baseline, then driving stepwise reductions against their top defect families. State the opportunity definition and inspection scope whenever you compare numbers across plants or suppliers.
More about Defects Per Million Opportunities
Why DPMO normalizes complexity
DPMO gives you a normalized view of quality across products and lines with different numbers of potential failure points. A complex assembly with dozens of steps can generate more chances for error than a simple part. By dividing total defects by total opportunities, then scaling to one million, you control for that complexity and get an apples-to-apples rate.
Units, opportunities, and defects
Start by separating three ideas: units, opportunities, and defects. A unit is one item you produce. An opportunity is a distinct place where a defect could happen on that unit, such as a hole diameter, a solder joint, a label, or a torque spec. A defect is any failure to meet the requirement at an opportunity. One unit can carry multiple defects if it fails at several opportunities. That is why DPMO can be much higher than the percentage of defective units.
Opportunity definition
Defining opportunities is the most important design choice you will make with this metric. Keep the list practical and stable, tied to customer-facing or safety-critical requirements. Group trivial issues under broader categories so you do not inflate the denominator. If you change the opportunity count, document it and restate your baseline so trends remain meaningful.
When to use DPMO
DPMO is useful when you want to compare lines, shifts, products, suppliers, or time periods that do not share the same number of checks. Yield or PPM can make a complex process look worse simply because it has more checks. DPMO adjusts for that and shows whether you are truly improving quality, not just building simpler parts.
Link to Sigma levels
Interpreting DPMO often goes hand in hand with Sigma levels. Lower DPMO means fewer defects and a higher Sigma performance. Many teams reference the classic Six Sigma convention that ties a long-term Sigma level to a DPMO value using the 1.5 Sigma shift assumption. Treat those translations as guides, not gospel. Your process, sampling plan, and inspection method influence the real-world relationship between DPMO and defect escape to the customer.
Measurement and data integrity
Measurement discipline matters. Count defects consistently. If a unit misses three torque specs, that is three defects, not one defective unit. Make sure inspectors share the same definitions and thresholds. Calibrate gauges, run periodic agreement checks, and review your nonconformance codes so analysts see clean, reliable data.
Using DPMO to drive improvement
Use DPMO to drive improvement, not just reporting. Trend the metric by week and month, and annotate process changes like new work instructions, fixture updates, or supplier changes. Break the metric down by defect family and by opportunity, then target the top contributors. A quick Pareto view usually points you to a handful of issues that cause most of the pain. Pair the metric with corrective actions and verify the change by watching DPMO fall in the next production run.
Inspection scope and detection method
Consider data collection scope. Inspection coverage, sample size, and detection method all affect the numerator. Automated vision systems might uncover more minor defects than manual checks, raising DPMO without any real process change. Document your inspection method and keep it consistent when comparing time periods or suppliers.
Rework and repair
Account for rework and repair. DPMO counts defects found, not whether you fix them later. If you want a metric that reflects what escapes to the customer, pair DPMO with outgoing quality or customer returns. For internal efficiency, track rework hours and scrap costs alongside DPMO so you see the full cost of poor quality.
Related metrics
Relate DPMO to sibling metrics. Defects Per Unit (DPU) measures average defects per unit without normalizing by opportunities. PPM measures defective units per million units. First Pass Yield and Rolled Throughput Yield show pass rates through stations. Together with DPMO, these metrics give you both unit-level and defect-level views.
Short-run and custom products
Short-run or custom products deserve careful opportunity definition. When volumes are low, one batch with a concentrated set of defects can swing DPMO wildly. Use control limits, medians, and rolling windows to smooth noise, and compare similar product families rather than mixing very different designs.
Customer impact and severity
Finally, keep the customer lens front and center. A small cosmetic blemish might inflate DPMO but carry little impact on function or safety. A single critical defect could trigger a recall. Use DPMO alongside severity ratings and cost-of-poor-quality tracking so you prioritize the defects that matter most.
Defects Per Million Opportunities Frequently Asked Questions
What is the difference between DPMO and PPM?
Both are defect rate measures, but they answer different questions. DPMO counts the total number of individual defects per million opportunities for a defect to occur. One unit can contribute multiple defects if it fails at more than one opportunity. PPM, often called defective parts per million, counts how many units are defective per million units produced, regardless of how many defects are on each unit. If your customers care about any defect rendering a part unacceptable at the unit level, PPM is more directly aligned. If you want a complexity-adjusted signal that helps compare processes with different opportunity counts, DPMO is the better choice. Many teams track both, using DPMO to diagnose and PPM to reflect customer impact.
How should we define an "opportunity" without inflating or understating DPMO?
Define an opportunity as a single, verifiable requirement that matters to the customer or to safety. Focus on measurable features like dimensions, torque, presence-absence checks, label accuracy, surface finish thresholds, or functional tests. Avoid breaking one requirement into many micro checks that inflate the denominator and make progress look better than it is. On the other hand, do not lump dissimilar requirements into one catch-all item that hides real problems. Publish a stable opportunity list for each product, review it with quality and engineering, and only revise it when the design or control plan truly changes. When you do revise it, document the date and start a new baseline so trends remain honest.
When is DPMO more useful than yield or first pass yield?
Use DPMO when products or processes differ in complexity, or when you need a sensitive metric for early detection. Yield and first pass yield operate at the unit level, so they treat a unit with one minor defect the same as a unit with several. DPMO captures the total defect load, which gives you a stronger diagnostic signal for continuous improvement and supplier development. It also helps you compare across lines with different numbers of inspections. That said, yield is easier to communicate to non-technical audiences because it maps directly to acceptance at the unit level. In practice, track both. Use DPMO to find and fix the biggest defect families, and use yield to confirm that customers see fewer defective units.