Why did Line 2 stop at 3:05?

Started by Sam Rivera · 37m ago

Sam Rivera
Why did Line 2 stop at 3:05 this morning?
Facilis
Line 2 had a 42-second micro-stop at 03:05:18. The Downtime Analyzer ran a post-mortem at 03:07 and identified the root cause as capper torque drift on Capper 2 — the torque setpoint had drifted from 14.2 N·m down to 13.6 N·m, just below the lower control limit. The capper auto-corrected and the line resumed within spec.

Line 2 OEE around the event

Capper 2 torque samples (N·m)

TimeSetpointActualStatus
02:5514.214.1OK
03:0014.213.9OK
03:0414.213.6Low
03:05Stop
03:0714.214.2OK
Sam Rivera
Has this happened before on Capper 2?
Facilis
Yes — Capper 2 has had three torque drift events in the past 30 days, all auto-corrected. The pattern is consistent: drift accumulates over ~48 hours of continuous operation. I'd recommend tightening the auto-correction interval from 4 hours to 2 hours, or scheduling a calibration check during the next changeover.
Drift events (30d)
3
All auto-corrected, no quality impact
Scope: Line 2 · Last 24h
⌘⏎