What to do When a PLC Fails in Production
Written by Maria Bitu
5 minutes read | 17 Dec 2025
Written by Maria Bitu
5 minutes read | 17 Dec 2025
A PLC failure in the middle of production is one of the most disruptive events a manufacturing site can face. Lines stop, pressure builds quickly, and every minute of downtime carries a cost. In those moments, the difference between a controlled response and a panicked one can mean the difference between a short delay and a full shift lost.
While every site and system is different, there are clear, practical steps that can help contain the situation and get production moving again as quickly as possible.
When a PLC goes down, the instinct is often to start changing things immediately. Power cycling, reseating modules, swapping cables — all without fully understanding the fault. This approach can sometimes make the situation worse.
Instead, slow things down just enough to assess what has actually failed. Is the PLC completely offline, or is it running but not communicating? Are I/O modules responding? Has the HMI or SCADA system lost connection, or is the fault confined to the controller itself?
Clear thinking at this stage saves time later.
Many PLC failures turn out not to be PLC failures at all.
Before assuming the worst, check:
Power supplies and incoming voltage
Blown fuses or tripped breakers
Loose or damaged wiring
Network switches and communication cables
Environmental issues such as heat, vibration, or moisture
A failed power supply or network component can bring a production line to a standstill while the PLC itself is perfectly healthy.
Modern PLCs provide valuable diagnostic information, but it’s often ignored under pressure.
Look for fault LEDs, error codes, or system alarms. If the PLC is still accessible, review diagnostic buffers or logs. These can quickly point to issues such as failed I/O cards, communication faults, or memory errors.
Replacing components without understanding the root cause can lead to repeated failures once production restarts.
Restarting a PLC might seem like a quick fix, but it isn’t always harmless.
In some systems, a reboot can:
Lose unsaved data or recipes
Interrupt controlled shutdown sequences
Cause unsafe machine states
If a restart is required, make sure the wider system is safe to stop and restart, and that operators are informed. Where possible, back up the program before taking any major action.
One of the biggest factors in recovery time is preparation done long before a failure occurs.
Sites that recover quickly usually have:
A recent backup of the PLC program
Known-good spare CPUs or I/O modules
Clear documentation of the system
Without these, even a simple fault can turn into a lengthy investigation while engineers search for software, passwords, or replacement parts.
If diagnostics confirm that the PLC CPU itself has failed, the priority becomes sourcing a replacement quickly.
For discontinued or older PLCs, this is where many sites struggle. Replacement units may only be available through specialist suppliers, and prices can be significantly higher during an emergency.
This situation often highlights a wider issue: reliance on obsolete hardware without a contingency plan.
Getting production running again is the immediate goal, but it’s important not to stop there.
A PLC failure should trigger a broader review:
Is the controller approaching end-of-life?
Are spare parts becoming harder to source?
Is the software documented and backed up properly?
In many cases, a failure is the warning sign that a planned upgrade or migration is overdue.
Once production is stable again, take time to understand what caused the issue. Environmental conditions, electrical disturbances, or simple component age can all play a role.
Addressing the root cause reduces the likelihood of repeat failures and helps justify preventative investment to management.
A PLC failure in production is stressful, but it doesn’t have to be chaotic. A calm, structured response combined with good preparation makes a huge difference.
The most resilient sites are not the ones that never experience failures — they’re the ones that are ready when they do.