When Maintenance Feels Like Ransom

Imagine this: you buy a car, and five years later the manufacturer sends you a letter saying, “We’ve changed the deal—if you want to keep the radio or turn the steering wheel, you now need to pay a yearly subscription.”

Absurd? Yes. But that is exactly how many software “maintenance” models are presented to industrial operators today.

These offers don’t read like maintenance; they read like ransom notes. Upgrades, updates, kill codes, annual renewals — all framed as “benefits.” In reality, they inject uncertainty into systems where stability is non-negotiable. And this is one of the hidden reasons why modern industrial standards fail to gain traction.

The Hidden Black Swan

Every update, patch, or new device is presented as progress. In reality, each is also a potential black swan — an unexpected vulnerability introduced by the supply chain itself. Attackers know this well. The SolarWinds breach, Stuxnet, and recent hardware backdoor scandals all worked because trusted updates or components were weaponised.

Every update, patch, or new device is presented as progress. In reality, each is also a potential black swan …

The paradox: newer is not necessarily safer. Proven systems, even if “old,” are predictable. Their quirks and flaws are known and managed. By contrast, every new release or patch opens a fresh front door to attackers.

Industrial operators run plants where downtime means lost megawatts, penalties, and safety risks. Supply chain is now the main attack vector. Each enforced upgrade expands the attack surface rather than shrinking it.

The Beyond Purdue View

If new standards are to succeed, they must respect industrial reality:

1. Installed Assets Cannot Be Ignored – TXP, T3000, Mark V/VIe, ABB and similar systems still run plants today and will continue to do so.
2. Data Must Carry Meaning – Without context and tagging, IT only gets numbers, not knowledge.
3. Transfer Must Be Hardware-Enforced – One-way data flow remains the most credible protection, ensuring operators can share data out without letting attacks in.

When “maintenance” is sold like ransom, trust erodes. When every patch is a new black swan, adoption stalls. The lesson is simple: stability is not the opposite of innovation — it is the foundation for it. Until standards reflect that, operators will continue to choose proven systems, protect them properly, and resist the false promise of perpetual upgrades.

The lesson is simple: stability is not the opposite of innovation — it is the foundation for it.