It happens on plant floors everywhere: a routine shift turns into chaos as a line goes down, a PLC stops responding, or a network segment drops — and production grinds to a halt. For most businesses, downtime is an inconvenience. For a manufacturer, it’s measured in a number the plant manager already knows cold: the per-minute cost of a stopped line.
Downtime in manufacturing doesn’t stay an IT problem. It becomes a missed shipment, a penalty clause with a customer, a supply chain ripple that shows up in someone else’s production schedule three days later. Understanding what actually drives that cost — and what’s increasingly causing it — is the first step to protecting against it.
Top Causes of Downtime on the Plant Floor
- Hardware Failures — Servers, network devices, and increasingly the sensors and controllers that keep a line running.
- Software Malfunctions — Bugs, compatibility issues, or misconfiguration, often worse on legacy OT systems that can’t be patched without a maintenance window.
- Cyberattacks — Ransomware, malware, and unauthorized access are a fast-growing cause of downtime, and manufacturing has been the most-targeted industry for cyberattacks four years running.
- Network Failures — Connectivity issues, server overload, or a dropped link between a plant and the systems it depends on.
- Human Error — Misconfiguration, accidental changes, or mishandled hardware.
- Power Outages — Immediate downtime, and prolonged outages can outlast even a well-provisioned UPS.
Cause #3 deserves more attention than it usually gets. A ransomware event doesn’t have to touch a single PLC to stop a plant — it just has to lock the systems that schedule, monitor, or authenticate access to the line. And a growing share of these incidents trace back to the same entry point: a device or a vendor connection nobody was tracking. An integrator’s laptop that plugged in for one job and never lost access. A sensor installed two years ago that’s still on the network with default credentials. It’s not always a sophisticated attack — often it’s just an open door nobody remembered was open.
Understanding Downtime Costs — Real Business Impact
Calculating the cost of downtime isn’t as complex as it seems. The core formula:
Hourly Cost of Downtime = Lost Revenue + Lost Productivity + Recovery Costs + Intangible Costs
Lost Revenue — For a plant, this tracks closely to OEE (Overall Equipment Effectiveness). If a line generates $5,000/hour in output and goes down for 3 hours, that’s a direct, calculable hit — before counting the knock-on effect of a missed shipment window or a contractual penalty for late delivery.
Lost Productivity — When the line stops, the crew doesn’t. Calculate each affected employee’s hourly cost, multiplied by the percentage of their time that depends on the line running, multiplied by headcount.
Recovery Costs
- Repair services — IT or OT engineering time, in-house or emergency vendor support, to diagnose and restore the affected system.
- Replacement parts — From a failed network switch to, in worse cases, replacing hardware that was damaged or corrupted during the incident.
- Data recovery — Lost production data, quality records, or scheduling data may need specialized recovery, especially if backups were also affected.
- Miscellaneous costs — Regulatory exposure if the incident involved sensitive data, customer trust erosion, and the OEM/customer security questionnaires manufacturers increasingly have to pass to keep contracts.
Intangible Costs — Reputational damage that shows up later: a customer who quietly starts qualifying a second supplier, or a cyber insurance renewal that gets harder after an incident, as carriers increasingly require device inventory and segmentation evidence as a condition of coverage.
What Actually Reduces This Risk
Most downtime-prevention advice focuses on redundancy and backups — necessary, but they address recovery, not prevention. The access control side of the equation gets less attention, despite being one of the more addressable causes: knowing what’s connected to the network, who’s allowed to be there, and for how long.
That matters more on a plant floor than almost anywhere else, because the standard fix — active scanning, agents, endpoint software — is often the wrong fix. A PLC that’s never been touched since commissioning can’t handle an active vulnerability scan without risking the exact disruption you’re trying to prevent. Any approach to closing this gap has to work passively: seeing and controlling every device without interrogating it, and governing vendor and contractor access so it expires with the work order instead of lingering indefinitely.
System downtime can cripple operations, reputation, and revenue — and on a manufacturing floor, the clock runs faster and the number is bigger than in almost any other industry. Understanding the real cost isn’t just about surviving the next incident; it’s the business case for closing the access control gaps that cause a growing share of them in the first place.
