Pp / Ppk
Within-subgroup sigma vs the full long-term spread.
Cpk uses short-term (within-subgroup) variation; Ppk uses overall, long-term variation. When Ppk lags Cpk, between-shift drift is quietly eating your margin.
What this method tells you
Pp / Ppk is one of the analytical methods Niobia AI surfaces inside the spc & process control branch. The short readout is: Cpk uses short-term (within-subgroup) variation; Ppk uses overall, long-term variation. When Ppk lags Cpk, between-shift drift is quietly eating your margin.
Where it fits in Niobia
Niobia keeps this method connected to the surrounding workflow, so teams can move from capability into adjacent methods without reformatting data or rebuilding the context from scratch.
Method-specific output, not just a screenshot
Niobia packages pp / ppk alongside the rest of the spc & process control stack, so the result stays connected to the raw inputs, the upstream context, and the next method the team needs to run.
Frequently asked
What does Pp / Ppk help a team understand?
Pp / Ppk sits inside Niobia AI's spc & process control workflows and helps teams turn raw process, materials, or quality signals into a defensible engineering readout.
When should engineers use Pp / Ppk?
Use Pp / Ppk when the question is better answered by that specific method than by a generic summary: it provides the method-specific signal, tradeoffs, and context the broader workflow depends on.
What should I read alongside Pp / Ppk?
The closest companion methods are Cp / Cpk. Reading them together makes it easier to see how Niobia AI moves from one analytical method to the next.