Process capability compares what a stable process actually produces against what the specification requires. Cp measures whether the process spread fits inside the spec limits; Cpk measures the same thing while accounting for how well the process is centered. Higher is better; a common conventional minimum is 1.33.

The indices get treated like mysterious report-card grades, but the picture behind them is simple: a bell curve sitting between two goalposts. Everything Cp and Cpk say can be seen by eye. This guide draws the pictures, works one example with real numbers, and is honest about where the famous 1.33 threshold comes from.

What is Cp?

Cp is the ratio of the spec width to the process spread: the distance between the specification limits divided by six standard deviations of the process. Cp = 1.0 means the process spread exactly fills the spec window. Cp = 2.0 means the spread uses half the window. Cp asks one question: could this process fit the spec if it were perfectly centered?

That "if" is Cp's blind spot. A process can have a beautiful Cp of 2.0 while running so far off center that half the parts are out of spec. Cp ignores where the process sits; it only measures how wide it is.

A centered, capable processCentered process: Cp = Cpk = 1.33LSL 490 gUSL 510 gmean 500 g (target)±3σ spread (σ = 2.5 g)4σ ofmargin4σ ofmargin
The fill-weight example, centered: the ±3σ spread fits with 4σ from the mean to each limit. Cp and Cpk agree at 1.33.

What is Cpk?

Cpk measures the distance from the process mean to the nearest spec limit, in units of three standard deviations. It answers the question Cp dodges: given where this process actually runs, how much room is there before the closest goalpost? When the process is perfectly centered, Cpk equals Cp. The moment the mean drifts, Cpk drops while Cp stays put. The gap between them is a direct reading of how off-center you are.

The same process, off centerSame spread, shifted: Cp = 1.33, Cpk = 0.67LSL 490 gUSL 510 gmean 505 g (drifted)~2.3%over USLonly 2σ to USL6σ to LSL (irrelevant: Cpk uses the nearest)
The same 2.5 g spread, mean drifted to 505 g. Cp still says 1.33; Cpk says 0.67 and about 2.3% of fills are over the limit.

A worked example: one filler, two verdicts

Take a filling line with a spec of 500 ± 10 grams, so LSL = 490 and USL = 510, a 20-gram window. Suppose a capability study on stable data shows a standard deviation of 2.5 grams.

That is the entire Cp-versus-Cpk story: report them together, and read the gap. A big gap says "center the process," which is usually cheap (an adjustment). A low Cp says "the spread itself is too wide," which is expensive (reduce variation or live with fallout). Knowing which problem you have before spending money is the practical value of computing both. The drift case is also why capability work rides on statistical process control: a control chart would have flagged that 5-gram creep long before the capability study did.

Cp versus Cpk at a glanceCp vs Cpk at a glanceCp: POTENTIALspec width ÷ 6σignores centering"could it fit, if centered?"low Cp → reduce variation ($$)Cpk: ACTUALmean-to-nearest-limit ÷ 3σpunishes off-center running"does it fit, as it runs?"gap vs Cp → re-center ($)Cpk ≤ Cp always. The gap between them is your centering problem, priced.
Cp is the process's potential; Cpk is its actual performance. Report both, read the gap.

What about Pp and Ppk?

Pp and Ppk use the same formulas with a different standard deviation. Cp/Cpk use short-term, within-subgroup variation, the process at its best behavior between disturbances. Pp/Ppk use the overall standard deviation of all the data, including drift, shift changes, and lot-to-lot wander. Ppk is therefore usually the lower, more honest number for "what did the customer actually experience," while Cpk describes the entitlement of the process if you eliminated the between-subgroup noise. Automotive practice reflects this split: initial studies at PPAP are commonly judged on Ppk, ongoing production on Cpk.

How do you run a capability study?

  1. Confirm the measurement system first. If the gauge cannot repeat, the study measures the gauge, not the process.
  2. Establish stability on a control chart. Capability math assumes a stable process. An out-of-control process has no single spread or center to measure, so any index computed from it is fiction.
  3. Collect enough data under normal conditions. Common practice: at least 100 individual values across 20-25 subgroups, spanning routine sources of variation.
  4. Check the distribution shape. The ppm predictions assume roughly normal data. Skewed data (flatness, runout, anything bounded at zero) needs transformation or different methods before the indices mean anything.
  5. Compute Cp, Cpk (and Ppk), and read the pair. Low Cp: attack variation. Cp fine but Cpk low: center the process.
  6. Re-check after any process change. Capability is a snapshot, not a property. Tooling wear, material changes, and new operators all move it, which is a running theme in first article inspection and requalification work.

Where does the 1.33 threshold actually come from?

Honestly: it is a convention, not a law of nature. Cpk = 1.33 means the process mean sits four standard deviations from the nearest spec limit (4σ ÷ 3σ = 1.33), which under normality predicts roughly 30 defective ppm on that side. It became the default because influential customers wrote it into supplier requirements, and it stuck.

Treat 1.33 as a floor for ongoing production on characteristics that matter, expect customers in automotive and aerospace to ask for more on new launches, and remember the number is only as good as the stability and measurement work under it.

Why capability numbers go stale

The most common capability failure isn't a bad study; it's a good study that nobody repeats. The index gets computed at launch, framed in a PPAP binder, and quoted for years while tooling wears and the mean wanders. If check weights and dimensional data are captured digitally at the station rather than on clipboards, capability stops being an annual archaeology project: the data for a fresh Cpk is already sitting in the system, next to the downtime log and the scrap reasons. That continuous view of quality data is exactly what Harmony's quality intelligence and paperwork digitization modules exist to provide alongside your QMS software and it is the difference between capability as a certificate and capability as a live number. Poor capability, left unmeasured, doesn't disappear; it just gets paid for in scrap, sorting, and complaints, the failure half of your cost of quality.