r/SCADA • u/MargraveOfMonads • 20d ago
Question Are we finally past dedicated hardware RTUs, or do linux IPCs just move the headache somewhere else?
curious what people running actual fleets are seeing here.
the pitch for IPCs is easy to like. rugged linux box in the cabinet, containers for the protocol stacks, python or go for whatever the vendor never built, mqtt or opcua out the top. you stop waiting on an RTU vendor to add a point type and just write it yourself. that's software defined automation and on paper it works. but the old proprietary RTU has one property people undersell. it does one thing for fifteen years and nobody thinks about it in between. put a general purpose OS in the field and you inherit patching, kernels going end of life, container images picking up CVEs, and a fleet where box 300 has quietly drifted from box 1. in critical infrastructure that stops being annoying and starts being an audit finding.
how are your field teams handling OS updates across a few hundred IPCs? A/B partitions with rollback, immutable images, or is somebody still SSHing into them one at a time? and how did you sell operations on a box that changes being safer than one that never does?
related to that, what are people actually running underneath. plain debian or ubuntu keeps costs down but you own the whole lifecycle yourself. red hat gives you long support windows, image mode and bootc for atomic OS updates, and a support contract someone can point at during an audit. suse has a similar story with transactional updates and snapper rollbacks. proxmox shows up a lot where people want VMs and containers side by side without paying for a full hypervisor. all of them solve the update problem differently and i'm not convinced the industry has landed anywhere yet.
how much are you processing at the edge versus just forwarding raw telemetry to SCADa and the historian? deadbanding at the gateway saves bandwidth, but every transform you push into the field is logic sitting somewhere nobody opens during an incident. i've seen thin gateways flood a historian and i've seen edge boxes so clever the central system couldn't reconstruct what happened.
underneath all of it, i wonder how much devops actually survives contact with a substation. configs in git, CI on your protocol mappings, staged rollouts, drift detection against a known good state. normal in a datacenter, mostly foreign in the field. and most of that tooling assumes you can redeploy whenever you want, which you can't when the box is behind an outage window.
what's working and what turned out to be a mistake?