A single defect is a data point. The same defect showing up a second and third time is a pattern — and patterns are much cheaper to catch on the first repeat than the fifth.
A single defect on a production line is, on its own, just a data point — it happens, it gets logged, the line moves on. The problem is when the same underlying cause produces the same defect a second time, and a third, without anyone connecting the dots early enough to intervene before it's cost real yield. Defect logs usually contain the information needed to catch this pattern. Reading them carefully enough, consistently enough, to catch it early is the harder part.
Defect logs are typically reviewed for immediate corrective action — fix this unit, move on — rather than for pattern detection across time. A calibration drift on a specific machine, showing up as a slowly increasing defect rate on one particular measurement, is easy to miss if each individual defect is being handled as its own isolated event rather than being checked against the recent history of similar defects.
The Manufacturing copilot is built to read a defect log with exactly that pattern-detection lens: not just logging each defect, but checking it against recent history to identify whether it's an isolated event or part of a developing pattern, and suggesting the likely root cause based on what's changed recently in the process.
Ask it to analyze a defect log and flag the root cause, and it doesn't just categorize the defect. It looks for the pattern across recent entries, identifies a likely cause — a calibration issue, a material batch change, a maintenance interval that's been exceeded — and suggests preventive maintenance where the pattern indicates it, rather than waiting for the defect rate to become obviously unacceptable before anyone investigates.
The cost of a defect pattern scales with how long it runs before being caught — not linearly, but in a way that compounds through wasted material, rework, and yield loss. Catching a calibration drift on the third occurrence rather than the fifteenth is the difference between a quick maintenance fix and a much larger quality investigation after a customer complaint forces the issue.