How to not make a power glitch turn milk into a very expensive problem | Ep 5

What happens to your production when the power flickers, a server reboots at the wrong moment or a firewall rule opens a door you did not know existed?In this episode, Erik Søndergaard joins The Food Tech Podcast to unpack operational resilience in food and beverage production. From power drops and UPS age to backups, segmentation and NIS2, Erik explains how to think about uptime like an insurance policy: decide what an hour of lost production costs, then secure your systems to match that risk.If you run a dairy, brewery or any process plant, you will hear concrete steps to keep lines running and systems ready to restart safely when something goes wrong.In this episode, you will learn:1. What operational resilience really means on the factory floor2. Why power disturbances and aging UPS units are still the biggest real-world risks3. How to use redundancy, backups and restore tests to protect critical servers4. How network segmentation and OT/IT separation limit the blast radius of an attack5. Why NIS2 is not just paperwork but a catalog of good uptime practicesEpisode Content00:06 What operational resilience means in a digitized production01:34 Real-world blockers of production and why power is enemy number one03:38 IT vs OT - why five minutes offline is different in an office than in a cheese vat05:44 Defining operational resilience as the ability to keep producing and restart safely09:04 Calculating the cost of downtime and using risk analysis as an insurance model11:20 Legacy equipment, isolation and why “air gaps” still matter for old systems13:13 Why security is never “done” and the need for regular hygiene walk-throughs16:05 The firewall rule that opened everything and what it teaches about everyday shortcuts20:42 How segmentation limits the blast radius when something does go wrong22:35 The basics to fix first - UPS age, server redundancy, backups and restore tests26:23 Thinking in fire doors and zones for OT networks and systems27:48 Securing vendor remote access without importing new risks30:53 Clear roles when something breaks and anchoring responsibility at board level33:31 Treating NIS2 as uptime engineering instead of box-ticking complianceThis podcast is brought to you by Au2mate.This podcast is produced by Montanus.