Case: Functional Outlier
One Part Failed, Seven Did Not
This review asks whether one failing part is random contamination or a first warning of repeatability loss in the run.
Open Case StudyCases where one part differs from the rest. We evaluate whether the anomaly is isolated, functionally relevant, and large enough to change the final batch decision.
A single anomaly does not automatically reject a batch. We score outliers by repeatability risk, functional impact, and evidence strength.
| Signal | Typical Reading | Action |
|---|---|---|
| Isolated visual defect | 1 of 8 parts | Document exception, release with note |
| Fit or load failure | Any single part | Hold batch, expand sample |
| Pattern recurrence | 2+ matching anomalies | Treat as process drift |
This review asks whether one failing part is random contamination or a first warning of repeatability loss in the run.
Open Case Study
An outlier appeared only in later samples, changing acceptance logic and proving that timing matters in small-batch evidence.
Open Case Study