ForHosting KIT · Math

DPMO calculator

Twenty-five defects in 200 assemblies with 5 inspection points each give 25,000 DPMO: defects scaled to a million chances to fail. Compare lines, plants and suppliers on one scale, whatever their volume. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Defects
25
Opportunities per unit
5
You get
Total opportunities
1,000
Defect rate
0.025
Dpu
0.125
Dpmo
25,000

Defects per million opportunities (DPMO) is the Six Sigma quality metric that scales observed defects to a million chances for something to go wrong, so processes with different volumes and different numbers of defect opportunities per unit can be compared on one scale. A line that finds twenty-five defects in two hundred assemblies with five inspection points each reports twenty-five thousand DPMO, not a raw defect count that hides the opportunity base.

What DPMO measures and how the formula works

Defects per million opportunities, abbreviated DPMO, is the standard Six Sigma count of how many defects a process would produce if it had a million chances to fail. Unlike a raw defect count, which grows with volume, or a simple fraction of defective units, which hides how many independent chances each item has to fail, DPMO normalizes both the number of units inspected and the number of opportunities per unit into a single scale that quality engineers compare across lines, plants, and suppliers.

The defining identity is DPMO equals defects divided by the product of units and opportunities per unit, then multiplied by one million. If twenty-five defects appear in two hundred units that each have five independent inspection points, total opportunities equal one thousand and DPMO equals twenty-five thousand. That figure is not a parts-per-million concentration from chemistry; it is a process-quality count of failures per million chances.

A process near 3.4 DPMO is often described as six-sigma capable under the common long-term shift convention, while tens of thousands of DPMO describe a process that still produces many failures per million chances. Zero defects on a positive opportunity base yield DPMO of zero, which is a valid and desirable result. Zero units or zero opportunities, by contrast, would divide by zero: this calculator therefore rejects those cases instead of inventing infinity.

Because the formula uses only finite arithmetic, two callers with the same three numbers always receive the same DPMO, the same total-opportunity count, and the same defect rate, which is what automated quality dashboards and exam graders need when they pin expected values in tests.

Incoming inspection and supplier scorecards

Quality engineers convert lot findings into a volume-normalized DPMO so a small sample with many opportunities is not scored the same as a large sample with one chance per unit.

What is the DPMO formula?

Total opportunities is the product of units and opportunities per unit; the defect rate is defects divided by that product.

Is zero defects allowed?

Yes. A non-negative defect count of zero on a positive opportunity base yields DPMO of zero, which is a valid quality result. Negative defect counts are rejected.

Is the DPMO calculator free?

The browser tool runs free on your device.

What DPMO counts as Six Sigma?

About 3.4 DPMO is usually described as six-sigma capable, under the common long-term shift convention. A result in the tens of thousands means the process still produces many failures per million chances.

Is DPMO the same as parts per million?

No. Parts per million in chemistry is a concentration. DPMO counts failures per million chances to fail, so a unit with five inspection points offers five chances, not one.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/stat/dpmo

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/stat/dpmo \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"defects":25,"units":200,"opportunities_per_unit":5}'
{
  "defects": 25,
  "units": 200,
  "opportunities_per_unit": 5
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "stat.dpmo",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

This calculator takes a non-negative defect count, a positive unit count, and a positive opportunities-per-unit count, returns the DPMO value together with total opportunities, the defect rate, and defects per unit, and rejects zero or negative units or opportunities with invalid_input so callers never see a silent infinity. The arithmetic is fully deterministic, runs free in the browser, and is available over the API at $0.002 per successful request with no language model and no external quality-management service on the hot path.

Input contract, validation, and the JSON you get back

Call the capability with three required finite numbers. Zero or negative units, and zero or negative opportunities per unit, fail with a message that those quantities make DPMO undefined, matching the rule that the calculator must not divide by zero. Negative defects fail as well because a negative count is not a physical inspection result. Failed validation is never charged. Field defects (aliases defect_count and d) is the observed defect count and must be non-negative; zero is allowed and yields DPMO of zero. Field units (aliases unit_count and n) is how many items were inspected and must be strictly greater than zero. Field opportunities_per_unit (aliases opportunities, opu, and opp) is how many independent chances for a defect exist on each unit and must also be strictly greater than zero. Each field may arrive as a JSON number or as a numeric string; missing values, empty strings, NaN, and infinities fail with invalid_input naming the field. On success the body echoes the three inputs, reports total_opportunities as units times opportunities per unit, reports defect_rate as defects over total opportunities, reports dpu as defects per unit, and reports dpmo as the scaled million-opportunity figure, together with a formula string and a short English message. Example: defects twenty-five, units two hundred, opportunities_per_unit five produces total opportunities one thousand and DPMO twenty-five thousand.

Where a DPMO calculator earns its keep

Use the browser tool when you want an immediate DPMO while checking a homework answer, reviewing a first-article inspection, or explaining why opportunity count matters as much as defect count. Results are fully deterministic: the same defects, units, and opportunities always yield the same DPMO, defect rate, and defects-per-unit figures. Prefer this capability when you already have the three counts and only need DPMO; if your source is a word problem, extract defect count, unit count, and opportunities per unit first, then call the solver and compare the published dpmo field to your hand calculation. Each successful request is one billable item at $0.002; failed validation does not consume balance. Keep counts inside ordinary inspection ranges so the product of units and opportunities remains a finite IEEE number; if an input would overflow to Infinity the solver rejects the request rather than returning a non-numeric DPMO. Wire the endpoint into supplier scorecards, process-capability dashboards, coding-interview sandboxes, or preprocessing steps where you already prefer a closed-form DPMO over opaque calculators that hide whether they multiplied by opportunities per unit before scaling to a million. This landing is for people searching for a DPMO calculator or defects-per-million-opportunities tool; it is not a Cpk calculator, not a process-yield converter from chemistry percent yield, and not a parts-per-million concentration converter.

Six Sigma homework and belt exams

Students enter defect count, units, and opportunities per unit from a case vignette and compare a hand-worked DPMO against a deterministic JSON result, including the hard rule that zero units is invalid.

Scripts and CI numeric fixtures

Pipelines and training platforms call a closed-form DPMO contract instead of reimplementing the million-opportunity scale in every language, and they assert the invalid_input path for zero denominators.

How do I calculate DPMO with this tool?

Send JSON with defects (non-negative), units (positive), and opportunities_per_unit (positive). The response returns dpmo, total_opportunities, defect_rate, dpu, the echoed inputs, and the formula string.

What happens if units or opportunities are zero or negative?

The request fails with invalid_input because DPMO would require division by zero. Validation failures are not charged.

Read the full KIT documentation →