Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The cost of production downtime is the calculated financial loss caused by a manufacturing or process interruption, and it is the number that turns operational technology security from an opinion into a business case.

What Is the Cost of Production Downtime?
Ask a plant manager what an hour of stopped production costs and you will usually get an answer in seconds. Ask a security team the same question and the conversation becomes abstract. Closing that gap is the point of downtime costing: a defensible figure, agreed by finance and operations, for what the organisation loses per hour when a line, a unit, or a site stops. Once it exists, decisions about segmentation, spares, monitoring, and recovery capability stop being arguments about principle.
A credible calculation has more components than lost sales:
Hourly rates are rarely linear. The first four hours may be absorbed by buffer stock, the first shift may be recoverable with overtime, and the loss becomes permanent only after a threshold. Modelling it in tiers is far more useful than quoting a single figure.
Real incidents give usable anchors. The LockerGoga ransomware that hit Norsk Hydro on 19 March 2019 forced the aluminium producer to run parts of its operation manually and cost the company in the region of NOK 800 million to 1 billion, of which insurance covered only a fraction. NotPetya in June 2017 cost Merck around 1.4 billion dollars and Maersk an estimated 250 to 300 million dollars, figures dominated by operational disruption rather than data loss. The August 2023 attack on Clorox produced a quarter in which sales fell sharply and the company reported hundreds of millions of dollars of impact, with manufacturing reverting to manual order processing for weeks. The May 2021 attack on JBS halted meat processing across several countries.
What these have in common is that the loss was not caused by the encryption of production systems. In most cases the operational technology was shut down precautionarily because the IT estate was compromised and operators could not be sure of the boundary, which is an argument for segmentation as a continuity control rather than a confidentiality one, as discussed in our note on the Colonial Pipeline attack.
The figure feeds directly into the business impact analysis and sets realistic values for recovery time and recovery point objectives in the operational environment, where the recovery asset is often a controller configuration or a historian rather than a database. It supports a return on security investment calculation that a finance director will accept, and it informs cyber insurance discussions, where business interruption cover is priced against exactly this analysis and where waiting periods and the definition of a covered event matter more than the headline limit.
It also changes the conversation about testing. If a plant loses a six-figure sum per hour, an unannounced vulnerability scan that knocks a controller over is not a minor incident, which is why operational assessments proceed passively and by agreement.
At Privia Security, we quantify operational impact and test recovery readiness with plant teams through our Cyber Exercise Services.
Contribution margin, not revenue. Using revenue overstates the loss because variable costs such as raw materials are not incurred while the line is stopped, and an inflated figure is the fastest way to lose the finance director’s confidence. Revenue only becomes the right measure where the sale is lost permanently and the input cost has already been committed.
Published industry surveys often quote six-figure sums per hour for automotive and continuous process plants, but borrowed averages are the weakest form of evidence. Two plants in the same sector can differ by an order of magnitude depending on capacity utilisation, buffer stock, and whether the process can be paused. Calculate your own figure for your own units.
Because they could not demonstrate that the boundary between the compromised IT estate and the plant network held. Where segmentation is poor and asset inventory is incomplete, a precautionary shutdown is the only defensible decision. Good zone design, documented conduits, and the ability to prove what a controller is doing turn that decision into a measured one rather than a reflex.
Business interruption cover exists, but the detail decides the outcome: a waiting period before cover begins, a definition of the triggering event that may exclude supplier failures, proof requirements that depend on your own production records, and exclusions for state-attributed attacks. Build the claim evidence into your incident process rather than assembling it afterwards.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.