It's 6 a.m. and the first shift is ready to go. But the system that runs the floor won't load. No production schedule, no work orders, no labels printing. The crew is standing at their stations, the trucks are booked for the afternoon, and the one person who understands the server is forty minutes away and not answering. The morning's output is evaporating one minute at a time.

If you run a manufacturing operation, you don't need this scene described. You've either lived a version of it or you've felt how close you are to it. The hard part is that the cost of a morning like this rarely shows up as a single line on a report. It hides inside idle labour, late shipments, and the customer who quietly starts sourcing a backup supplier.

The problem usually isn't the thing that broke

When the line stops, attention goes to whatever failed: the server, the switch, the application. But the failure is usually the last step in a longer story, and that story is about the setup underneath it. Most plant networks grew piece by piece alongside the business, added to whenever something new was needed, and nobody has had a reason to look at the whole of it in years.

Three things tend to be true at the same time. The hardware is older than anyone would choose, because a server or a switch is a real capital expense and there is always something on the floor that needs the money first. So "it's still working" quietly becomes the plan. The backup is running, technically, but nobody has tested it by actually restoring from it. And the production software and the office network are tangled together, with no clear plan for what happens when one of them goes down.

That's the pattern we see most often on the plant floor, and it isn't negligence. It's a system that was built for the company you were five years ago, quietly carrying the company you are today.

What downtime really costs, honestly

The published numbers are worth knowing, and worth putting in perspective. Siemens' True Cost of Downtime report puts an idle automotive line at up to $2.3 million an hour, and estimates that the world's 500 largest companies lose around $1.4 trillion a year to unplanned downtime. Those are enormous plants with enormous output. Your number is nowhere near that, and your number is the only one that matters. You can work it out in about ten minutes.

Take the wages of everyone standing idle for the hour. Add the margin on the output that hour was supposed to produce. Add the overtime or the Saturday shift you'll run to catch up. Add anything a late shipment costs you, including the freight upgrade to hit the date anyway. For most mid-sized manufacturers, one lost morning lands somewhere in the thousands, and higher once a customer delivery is involved. Having that figure written down changes how the next conversation about IT spending goes.

There's a security dimension too. In IBM's X-Force Threat Intelligence Index, manufacturing was the most-attacked industry for the fifth year running, accounting for just over a quarter of all incidents in 2025. The logic is plain enough: attackers know a plant with near-zero tolerance for downtime is more likely to pay to get moving again. That's not a reason for alarm. It's a reason to make sure the basics are genuinely in place, so a bad day stays a bad day instead of becoming a bad month.

It's worth saying outright: most manufacturers we meet aren't behind because they did something wrong. They're behind because the floor demands their attention every single day, and the systems running underneath it rarely get a quiet moment to be looked at properly. Naming the cost isn't about worry. It's about deciding the quiet moment is worth making before the loud one arrives.

What a steadier setup looks like

The path out of this is not a single product. It's a handful of things working together, and a guide who watches them so you don't have to. At Red Rhino, this is the stretch of terrain we walk with manufacturers most often:

·      Proactive monitoring, so problems get caught and fixed before the first shift ever notices. The goal is fewer 6 a.m. surprises, not faster apologies for them.

·      Backups that are tested, not just running. A backup you've never restored from is a hope, not a safeguard. We verify yours actually works.

·      A real recovery plan. If something does go down, everyone knows the steps and the expected time to be back, instead of waiting on one person's phone.

·      Security built for how plants actually operate, including the older equipment that can't simply be replaced overnight.

·      Planning that looks ahead. A virtual CIO helps you budget for the hardware and upgrades you'll need next year, so decisions happen on your schedule rather than during a crisis.

A manufacturer who got ahead of it

A mid-sized manufacturer in Richmond came to us after a morning much like the one above. A failed server had cost them most of a production shift, and the outage got everyone's attention. They wanted to know whether it would happen again.

We started where we usually do, by going through what they had and where the soft spots were. Then we put proactive monitoring in place, rebuilt their backups and tested a full restore, and mapped a sensible replacement schedule for the hardware that was living on borrowed time. The next time a drive started to fail, it was flagged and swapped on a quiet afternoon, not discovered at 6 a.m. by a crew with nothing to do. The line kept running. That's the whole point.

The right time to look is before you need to

The best moment to evaluate your IT isn't in the middle of a crisis. It's during a quieter stretch, when you have room to plan and budget for the year ahead. If your operation is in that window now, it's a good time to find out exactly where you stand.

If this raised a question about your own floor, the backup nobody has restored from, or the box everyone hopes lasts one more year, we're glad to talk it through on a short call. We work with manufacturers across Greater Vancouver and the Fraser Valley. You'll get a straight read on where you stand and what's worth doing first, whether or not you end up working with us. When you're ready to walk that next stretch, we know the way.

‍