Why compressed-air controls need a resilience plan
Modern compressor houses are full of networked devices: machine controllers, master sequencers, VSDs, dryer controllers, flow and power meters, HMIs, gateways, historians and remote-monitoring modems. Each one adds visibility, and each one adds a way for the air supply to be disturbed – by a cyber incident, a failed switch, a firmware update gone wrong, a wrong set point typed from an office PC or simply a lost time signal.
The aim is continuity. If the analytics platform goes down, the plant should lose its charts, not its air. If the sequencer fails, the compressors should fall back to safe local pressure control. If someone changes a set point without authority, it should be noticed and reversible.
This page is practical, vendor-neutral architecture guidance. It does not cover credentials, addresses or exploit details, and the exact controls for any site must follow the site’s IT/OT policy, current manufacturer documentation and competent specialists.
What could go wrong: consequence first
Start by asking what happens to compressed air when each digital function fails, not by listing technologies.
| Digital failure | Typical consequence | Design response |
|---|---|---|
| Loss of view (dashboard, historian) | No trends or alarms remotely; air still produced | Local HMI and controller alarms remain; operators know local checks |
| Loss of command (sequencer or BMS link) | Machines may stop receiving start/stop or load signals | Each machine falls back to local pressure band control |
| Loss of communication between machines | Uncoordinated loading, pressure swings, extra unloaded running | Staggered local set points pre-configured as fallback |
| Bad data (failed transmitter) | Sequencer reacts to false pressure; over- or under-supply | Sensor plausibility checks, backup pressure reference |
| Unauthorised set-point change | Higher energy, nuisance trips, low pressure at users | Access levels, change log, regular configuration comparison |
| Configuration loss after a controller fault | Machine restarts on defaults or will not run | Dated backups of every controller and VSD parameter set |
| Loss of time synchronisation | Event records cannot be correlated | Recorded time source; offset noted in logs |
Watch for common-mode digital failures: one network switch, one power supply or one gateway that, if lost, removes control from every machine at once.
Architecture principles that keep air flowing
- Local safe control first – each compressor’s own controller handles protection and pressure control. Shutdowns for high discharge temperature, overload and motor protection must never depend on a network.
- Analytics separate from command – monitoring and reporting paths should read data, not write set points. If write access is truly needed, it is a deliberate, limited exception.
- Least necessary connectivity – connect only what is needed, to only the systems that need it.
- Segmented networks – the compressor and utility controls sit in their own zone, separated from the office network by a controlled boundary.
- Controlled northbound data flow – data leaves the OT zone through a defined gateway or historian, ideally one-way where practical.
- Controlled remote support – remote access is enabled only for a specific job, by a named person, and switched off afterwards.
- No public exposure for convenience – controllers and HMIs should never be reachable directly from the internet.
Fallback behaviour you must test
A fallback that has never been tested is a hope, not a plan. Check how each item behaves, and write the result down.
- Disconnect the sequencer link to one machine: does it revert to its local pressure band, and is that band sensible?
- Simulate loss of the master pressure sensor: does the sequencer hold, fall back or shut machines down?
- Restore power after a planned outage: do machines restart automatically, in what order and with what delay? Is that safe for the electrical supply and for the process?
- Take the remote-monitoring gateway offline: does anything other than visibility stop?
- Restore a controller from backup on a spare or during a shutdown: are the parameters complete and correct?
- Check dryer controls: does a communication fault ever leave a dryer bypassed or a desiccant dryer stuck on one tower?
Many sites set local fallback bands slightly below the sequencer band so machines take over smoothly. The exact values depend on the system’s pressure needs and should be decided with the energy cost in mind – roughly 7% more power for each extra bar of generation pressure.
Inventory and configuration control
You cannot protect what you have not listed. A compressor-house OT inventory should record, for every device:
- Device type, make, model, serial and location
- Firmware and software version, and the tool used to configure it
- Network zone and which systems it talks to
- Who owns it and who is allowed to change it
- Date and location of the latest configuration backup
Keep a change log for every set-point, parameter or firmware change: what changed, why, who approved it and how to reverse it. Compare live configurations against the last approved backup at each service visit. Before any firmware update, confirm compatibility with the manufacturer’s documentation, take a backup, plan the work for a period when standby capacity or a rental machine is available, and know how to roll back.
Remote monitoring without remote risk
Remote monitoring is valuable: early alarms, trend review by an engineer who is not on site, and better service planning. It does not need to be risky.
| Choice | Lower-risk option | Higher-risk option |
|---|---|---|
| Data direction | Read-only data out | Read/write from the cloud or office |
| Connection | Through a managed gateway or plant historian | Controller directly on the internet |
| Remote support | Enabled per session, logged, time-limited | Always-on, shared password |
| Accounts | Named users, role-based access | One shared login for everyone |
| Alarms | Local alarms stay primary; remote is extra | Plant relies only on remote alerts |
Also think about power. A gateway or switch on an unprotected supply may reboot during voltage dips, which are common on some industrial feeders. Use a small UPS for network and control power where the failure would matter.
Recovery: getting back to normal after an incident
- Secure air first: put machines on local control and confirm pressure and air quality at critical users.
- Isolate the affected network segment if a cyber incident is suspected; follow the site’s incident procedure and involve IT/OT specialists.
- Check controller set points and parameters against the last approved backup.
- Restore from known-good backups where needed, then verify protection functions before returning to automatic sequencing.
- Bring monitoring and remote links back last, once control is confirmed stable.
- Record what happened, what was changed and what will be improved.
If the incident has taken compressors or dryers out of service, temporary air can bridge the gap while controls are restored; see the business continuity and emergency air guidance.
How Reddy Compressors helps
Reddy Compressors, Tarnaka, Secunderabad, has served industry since 2002 as an independent multi-brand compressed-air specialist – selling new and used machines, renting from our own fleet, and providing service, AMC, overhauls, audits and spares for ELGi, Atlas Copco, Ingersoll Rand, KAESER, Chicago Pneumatic, Sullair, Doosan, Kirloskar, Gardner Denver and others. We are not an authorised dealer of these brands, and we are not a cybersecurity firm; we work alongside your IT/OT team on the compressed-air side. We have tie-ups with all major and reputed brands.
- List compressors, dryers, sequencers and VSDs with controller types and visible software versions
- Record and photograph controller settings so you hold a reference of the working configuration
- Test local fallback pressure bands and restart behaviour during planned service
- Advise on sequencing and pressure bands that remain stable if communication is lost
- Supply controller and sensor spares after confirming compatibility from the nameplate and existing hardware
- Provide rental compressors from our fleet as cover during control upgrades or recovery
Our service engineers and technicians cover all of Telangana and Andhra Pradesh, with equipment, rentals and spares supplied across India.
What to send us
- List of compressors, dryers and controls with make, model and serial
- Photos of controller screens, sequencer panels and network or gateway boxes
- Current pressure set points and how machines are sequenced
- Whether remote monitoring or BMS/SCADA links are in use
- Any recent trips, pressure swings or control faults
Frequently asked questions
Will my compressors stop if the sequencer or network fails?
They should not, if the system is set up correctly. Each compressor’s own controller should take over with a local pressure band when it loses the sequencer signal. Some installations are configured badly, so machines stop or run on default settings. Test this during a planned window, record the behaviour and correct the fallback settings before a real failure happens.
Is it safe to connect compressors to remote monitoring?
It can be, when monitoring is read-only by default, data passes through a managed gateway or historian rather than exposing controllers to the internet, accounts are named and remote support is enabled only for specific sessions. Local alarms and protection must remain primary. Follow your IT/OT policy and the manufacturer’s current guidance for the actual devices installed.
Should the BMS or SCADA be able to change compressor set points?
Usually it is better for BMS or SCADA to read compressor data and send only simple, well-defined commands, such as enable or disable, if any. Pressure control and protection should stay with the compressor controllers or the dedicated sequencer. Where write access is needed, limit it, log every change and agree clearly who has authority over the air system.
How often should compressor controller settings be backed up?
Take a backup after commissioning, after every approved change and before any firmware update or controller repair, and keep dated copies with the change log. Comparing live settings with the last approved backup at routine service visits catches unauthorised or accidental changes. The method depends on the controller; some allow file export, others need screen records.
What should we do first after a cyber incident affects the compressor house?
Secure compressed air first by putting machines on local control and confirming pressure and quality at critical users. Then follow your site incident procedure: isolate the affected network, involve IT/OT specialists, check settings against known-good backups and restore control before bringing monitoring back. Arrange rental cover if machines must stay offline for some time.
Can Reddy Compressors help with control upgrades on mixed brands?
Yes, on the compressed-air side. We work with controllers and sequencing on many brands, record existing configurations, test fallback behaviour, supply compatible controller spares and provide rental machines during changeovers. We coordinate with your IT/OT team or specialists for network and cybersecurity design, which we do not supply as a separate service.
Related pages
Technical content reviewed by D. Srinivas Reddy, Managing Partner and service engineer, Reddy Compressors. Last updated 17 October 2026. How our engineering content is reviewed.