What actually happens when a production line goes down at 2am on a Friday
Most of the conversation about operational risk has moved towards cyber, and fairly so. A cyberattack can stop a factory as completely as a power cut, and it's now treated as a production and financial threat rather than something IT handles on its own.
Still, ask anyone who has worked nights on a production floor what actually stops their line, and they'll rarely point to a hacker. It's a belt that's been tracking slightly off for a fortnight, a bearing nobody has listened to, or a jammed section that nobody on shift can diagnose.
What follows is fictional. However, if you run a production operation, you'll probably recognise every minute of it.
01:52, the noise
Dan is the night shift supervisor at a chilled food packing site in the Midlands. Thursday night is meant to be the steady one: a manageable order book, a crew of nine, and a full day shift arriving at 6am to push Friday's orders out of the door.
The first sign isn't an alarm. It's a noise from the infeed conveyor on line 2, a dry squeal that comes and goes, the kind you notice and then talk yourself out of. One of the operators mentions it on his way back from break. Dan walks over, watches the belt for a minute and can't see anything wrong. Product's moving, the wrapper's running, the counts are fine.
He makes a note to tell days. (Everyone reading this has written that note.)
02:07, the trip
Fifteen minutes later, the belt stops dead. The drive motor has tripped on overload, and the line behind it backs up within seconds: trays stacking against the stationary belt, the operator upstream hitting the stop, the wrapper running empty.
Dan resets the trip. The belt runs for about forty seconds, then trips again. Second reset, same result, except this time there's a smell. Not quite burning, but heading that way.
This is the moment the night changes shape. Up to now it was a nuisance. Now it's a decision, and Dan's the only one awake who's allowed to make it.
02:20, the phone calls
The site has one maintenance engineer on call overnight. Tonight that's Steve, who lives forty minutes away and answers on the fourth ring, sounding exactly as you'd expect. Dan describes the noise, the trips and the smell. Steve's best guess, over the phone, is the bearing on the drive drum.
"Have we got a spare?" he asks.
Nobody knows. The stores cabinet is locked, the spares list lives in a spreadsheet on the maintenance manager's laptop, and the maintenance manager is on holiday.
Steve sets off anyway.
02:45, the workaround
While they wait, Dan has two problems running side by side. The obvious one is the conveyor. The less obvious one, and arguably the bigger, is the product already on the line. It's chilled, it can only spend so long out of temperature control, and every minute it sits on a stopped belt brings it closer to becoming waste. (If you work in food, you'll know exactly what that means for your HACCP plan.)
So the crew does what crews always do. Two operators start hand-loading trays past the dead section, straight onto the wrapper's infeed. It's slow, it's awkward, and it's exactly the kind of manual handling the conveyor was installed to remove. That being said, it keeps a trickle of product moving, and at quarter to three on a Friday morning a trickle is worth having.
Dan logs the time the line stopped, the quantity on hold and the temperature readings, because he knows the technical manager will ask for all three before she asks how he is.
03:30, the diagnosis
Steve arrives, isolates the conveyor and has the guard off inside ten minutes. The drive drum bearing has collapsed. Looking along the belt edge, it's also been running off-centre long enough to start fraying, which is probably where the squeal began.
The good news is that the fix itself is straightforward. The bad news is that there's no spare bearing on site, and nowhere stocking the right one will open until after the day shift has started.
Steve can get the belt running again with a temporary fix he isn't happy about, at reduced speed, on the understanding that it needs proper attention as soon as the part arrives. Dan takes it. Of course he does.
05:45, handover
By the time the day shift walks in, line 2 is limping. Dan has lost roughly a third of the night's output, put two pallets on hold pending a temperature review and written a handover note that runs to a page and a half. On a Friday, with a full dispatch schedule, that's the day shift's problem now, and they won't be thrilled.
He drives home in daylight, replaying the 01:52 squeal and wondering whether he should have stopped the line then. He probably should have. Mind you, nobody would have thanked him for stopping a running line over a noise.
What the night actually tells you
The striking thing about nights like this is how little of the damage comes from the failure itself. A bearing giving out is a normal mechanical event; it was always going to happen eventually. What turned it into a lost shift was everything around it.
The warning signs were there for weeks. A belt doesn't start fraying in an evening. Tracking drift and a noisy bearing are exactly the slow faults routine inspection is meant to catch, and both were sitting in plain sight.
The knowledge wasn't on shift. Dan's crew could run the line but couldn't diagnose it, and the one person who could was forty minutes away. That isn't a criticism of anyone, it's simply how most nights are staffed.
The spares were a mystery. Not necessarily missing, just unknown, which at 2am amounts to the same thing.
The plan for the product was improvised. It worked this time largely because the crew was good, which is a nice thing to be able to say but a poor thing to rely on.
Of course, the answer isn't to staff every night like a day shift. Very few operations could justify it, and most nights nothing goes wrong. The answer is to make sure the 2am version of your team has fewer decisions to make.
What to sort out before it happens to you
Planned preventative maintenance. Regular checks on belt tracking and tension, bearings, rollers, motors and gearboxes catch the slow faults long before they become trips. It's the least dramatic thing on this list, and the one that would have saved Dan's night.
A spares list someone can actually find. Know which critical parts you hold, where they are and who has the key. A sheet on the stores door beats a spreadsheet nobody on nights can open.
A clear rule on when to stop the line. If an operator reports an unusual noise, smell or vibration, what happens next? Settling that in advance is kinder than leaving it to a supervisor's judgement at 01:52.
A known route to outside help. Whether that's a maintenance contract or a firm you can call for emergency repairs, the time to find their number isn't during the breakdown.
Where MJE Projects fits in
We provide maintenance and repair for all types of conveyor, whoever originally built them. That covers planned preventative maintenance, belt tracking and tensioning, motor and gearbox inspections, roller and bearing replacement, safety audits and emergency repair support, with options ranging from one-off repairs to annual maintenance contracts.
We can't promise your line will never go down at 2am on a Friday. Nobody honestly can. What we can do is make it a lot less likely, and make sure that when it does happen, the morning after looks more like a routine repair than a page-and-a-half handover note.
The 2am breakdown will never get the boardroom attention a cyber attack does, and it doesn't need to. It just needs someone to have listened to the squeal a fortnight earlier.
Comments