-
Leon Zhang Sales Manager
-
Email: sale@relayprotect.com
-
Phone/WhatsApp: +86 13655813266

SCADA Software: Stack, Deployment and How to Choose
SCADA software links field devices, PLCs and operators on one real-time screen. This guide covers HMI, historians, OPC UA and how to choose a vendor.
What does SCADA software actually do and how is it deployed?
SCADA software is the application layer that turns wired-together controllers into something an operator can watch, command and trust. It does four jobs: acquire values from PLCs and RTUs on a scan cycle often 100 to 500 ms, present them as screens and trends, remember them in a historian, and alert when a value breaks its limit. The programming model is IEC 61131-3:2025, the security baseline IEC 62443-2-1:2024, and alarm management follows IEC 62682 (built on ISA-18.2). The SCADA layer polls controllers without replacing their logic, sitting between field devices and the HMI; a weak glue point is where most incidents start. A historian stores tags at their configured rate, sometimes 1 Hz across 50,000 tags, roughly 4 GB a day before compression, so retention is chosen first and the disk sized after. A redundant server pair fails over in under 2 s. Deployment is on-premise, web-based or cloud-hosted; the difference is who patches what. Setting review and quotation within 12 hours, MOQ 1, 7-15 working days.
scada software is the application layer that turns wired-together controllers into something an operator can watch, command and trust. It polls the PLCs and RTUs, draws the screens, stores history and raises the alarm when a pump overheats or a feeder trips. The programming model is IEC 61131-3:2025; the security baseline is IEC 62443-2-1:2024.
At a Glance
- SCADA software = data acquisition + HMI + historian + alarm engine, running above the PLCs.
- IEC 61131-3:2025 defines the PLC languages; IEC 62541-1:2025 (OPC UA) defines data exchange upward.
- HMI is one pane of the system, not the whole thing.
- Size the licence to peak tag count plus 30 % headroom, not today’s device list.
- Keep safety-critical logic on site; treat any cloud link as untrusted (IEC 62443-2-1:2024).
- A historian turns the live view into a record; size the disk to retention, not the other way around.
What SCADA Software Actually Is
Strip away the marketing and this layer does four jobs. First, it acquires: it asks every controller for its current values on a scan cycle, often every 100 to 500 ms. Second, it presents, rendering those values as screens, mimics and trends an operator can read in a glance.
Third, it remembers: a historian writes the time series to disk so you can ask what line 3 did at 2 am. Fourth, it alerts: an alarm engine compares each value to its limit and tells the right person when something breaks the envelope. Everything else, from reporting to mobile apps, is built on those four.
Separating the software from the system keeps a migration honest. The system is the cables, the RTUs, the PLCs and the screens on the wall; the software is the logic that ties them together. Most plants keep the same PLCs and swap only the application layer, exactly what a typical migration does, but the data model and the alarm philosophy travel with the software, not the hardware. The scan cycle, usually 200 ms, is quick enough for nearly every process demand.
How SCADA Software Fits the Control Stack
A plant is a stack of responsibility. At the bottom sit field instruments: transmitters, motor starters, protection relays. Above them, PLCs and RTUs run the control logic and speak to the instruments over Modbus, Profibus or hardwired I/O. The SCADA layer arrives next: it polls those controllers, never replacing their logic, only reading state and issuing setpoints. Above that sits the HMI that humans watch, and at the very top, the enterprise layer that turns plant data into KPIs for management. The software is the glue between the controller and the human, and a weak glue point is where most incidents start.

Selecting a relay for a live project?
Send the system voltage, CT ratio and tripping scheme. Our engineers confirm the model and reply within 12 hours.
HMI SCADA Software: The Operator’s Window
HMI the SCADA system is the operator’s window into the process. A good HMI shows state, not decoration: pump running or not, tank level as a number and a bar, the three alarms that matter right now at the top of the list. Modern HMI the platform is web-based, so the same screen opens on the control-room monitor, the shift supervisor’s tablet and the engineer’s laptop, with role-based rights deciding who can merely look and who can command. The screen in Figure 2 is deliberately plain: navigation on the left, a live trend in the centre, and an alarm list that sorts by priority rather than by time of arrival.

The trap with HMI this layer is over-design. Animated pipes, 40-colour gradients and pop-up wizards look impressive in a demo and slow the operator down at 3 am when a real trip is unfolding. Keep the alarm list legible, keep the trend one click away, and resist the urge to make the screen a screensaver. Alarm management follows IEC 62682 (built on the ISA-18.2 practice), which says every alarm needs a defined response, not just a coloured box.
SCADA Software on the Server Side
SCADA system software is the server side: the services that actually run the plant view. The core is the real-time database, a fast in-memory store of the current value of every tag. Around it sit the alarm engine, the historian, the report scheduler, the user-directory service and the protocol drivers that talk to each vendor’s PLC. A single server can run all of this for a small site; a redundant pair splits it for a critical one, with a heartbeat link that fails over in under 2 s when the primary dies.
The historian deserves its own sentence. It is the component that turns SCADA system software from a live viewer into an asset: it compresses and stores every tag at its configured rate, sometimes at 1 Hz across 50,000 tags, which is roughly 4 GB of raw history per day before compression. Pick the retention first, 13 months is a common minimum for seasonal comparison, then size the disk, not the other way round.
| Service | Job | Failure symptom |
|---|---|---|
| Real-time database | Holds current tag values | Screens freeze or show stale data |
| Alarm engine | Evaluates limits, routes alerts | No alarms, or alarms to wrong person |
| Historian | Stores the time series | Trends empty, audits impossible |
| Protocol drivers | Talk to PLCs and RTUs | Comms loss on one vendor’s gear |
| User directory | Authenticates operators | Everyone shares one login |
Table 1. The services that make up a SCADA system software install.
Choosing Among SCADA Software Companies
the software companies range from the global automation majors, who sell the PLC, the HMI and the cloud together, to specialist vendors who only do the software and happily talk to anyone’s controllers. The majors win on integration and support reach; the specialists win on openness and price. When you shortlist this software companies, score them on four things that actually matter later: which PLC protocols they driver natively, whether the historian licence is per-tag or per-server, how they handle redundancy, and what the version-7-to-8 migration costs in year 6.
- Native drivers: ask for a written list of supported PLC and RTU protocols, not a vague ‘open standards’ line.
- Licence model: per-tag pricing punishes growth; per-server pricing is predictable but caps scale.
- Redundancy: confirm the failover time in writing, under 2 seconds for a critical site.
- Migration path: request the last two major-version upgrade notes before you sign.
A useful test is to ask each vendor for a reference site in your exact industry, then call that site. Vendors quote uptime; operators tell you the truth about patching weekends and how often the historian filled the disk.
On-Premise, Web and Cloud Deployment
the SCADA system runs three ways, and the difference is mostly about who patches what. On-premise puts the server in your control room on a locked VLAN; you own every update and every risk. Web deployment keeps the server on site but serves the HMI through a browser over a reverse proxy and VPN, which shortens both the learning curve and the hardware list. Cloud-hosted moves the server to the vendor’s data centre, which scales fast but asks you to trust a perimeter you do not control. Figure 3 lays the three models side by side.

For a utility or a power plant, on-premise or web with the server on site remains the default, because the process must keep running when the wide-area link drops. Cloud is a strong fit for aggregation, analytics and multi-site roll-ups, provided the safety-critical control never depends on it. The pattern that works is edge control plus cloud insight: keep the logic local, send only summarised data upstream.
Connecting to PLCs and RTUs
Getting the platform to talk to the controllers is where projects slip. Legacy plants carry Modbus RTU on serial links, Modbus TCP on the network, IEC 60870-5-104 for telemetry and DNP3 for North American utilities. Newer substations speak IEC 61850, which is not a polling protocol but a self-describing object model, so the software imports the substation configuration language file instead of hand-mapping points. Substation protection and control is covered in our SCADA guide, and the controller languages behind it in our PLC programming guide.
Each protocol driver is a point of failure and a point of trust. A driver that silently drops a register will not alarm, it will simply show zero, which is why every tag needs a freshness timeout and an out-of-range flag, not just a value. Map the drivers early, before the screens, because the data model they expose is what every later screen is built on.

Data Exchange With OPC UA
Inside one vendor’s world, the drivers handle everything. Across vendors, and upward toward MES and ERP, the common tongue is OPC UA, standardised as IEC 62541-1:2025. Unlike its COM-based predecessor, OPC UA is platform-independent, carries its own type system and security, and lets a historian in one building subscribe to a tag in another without a custom shim. If you are choosing between two otherwise equal this layer packages, the one with a certified OPC UA client and server is the safer long-term bet, because your next system will almost certainly speak it too.
Historian and Trending
The historian is where the software earns its keep after the screens impress at commissioning. It stores every tag at a configured rate and dead-bands the noise, so a valve that sits at 50.0 % never writes 10,000 identical rows. It serves trends back in under 1 s even years later.
The same record catches the failures. A sensor that drifted to 65 °C is visible before the bearing fails, and a stuck valve shows up as a slow drift instead of a hard fault. A maintenance engineer proves that the bearing temperature crept up for three weeks before the trip; an energy manager bills each line for its kilowatt-hours; an auditor shows the regulator that the emissions stayed inside the limit. Treat the historian as a legal record, back it up like one, and test the restore, not just the backup.
Alarms, Events and Acknowledgement
An alarm is a contract: when this value breaks this limit, these people are told, in this order, and someone must acknowledge. this software that fires 400 alarms an hour has no alarms, it has noise, and operators learn to ignore it, which is how the one real trip gets missed. Good practice, now codified in IEC 62682, caps the rate, ranks by consequence, and requires every alarm to have a defined operator response. The software should support shelving, suppression and a standing alarm report, and someone should read that report monthly.
Security Built Into the Software
the SCADA system is a favourite target precisely because it sits between the office and the turbine. The control-floor rule is that availability beats confidentiality: a relay must answer in milliseconds, so you cannot bolt a 3 s antivirus scan onto its scan cycle. The practical answer is zoning. IEC 62443-2-1:2024 describes the programme, IEC 62443-3-3:2013 sets the security levels, and IEC 62443-4-2:2019 specifies what each component must do. Put the HMI on a different zone from the PLCs, broker the crossing with a hardened gateway, and never let the business network touch a controller directly. Our SCADA overview walks the zoning model in detail.
On the software side, enforce least privilege: operators get read and acknowledge, engineers get configure, administrators get the rest, and none of them share a login. Two-factor authentication for remote access, an asset inventory the software can export, and a patch window that actually happens, these are the unglamorous controls that stop most incidents before they start.
Selection Criteria That Matter
Most buying decisions overweight the demo and underweight the lifecycle. Score candidates on the table below before you invite them to present, and weight the rows by what your plant actually suffers from.
| Criterion | Why it matters | Red flag |
|---|---|---|
| Native protocol drivers | Fewer converters, fewer failure points | Only Modbus, everything else is a gateway |
| Historian licence model | Drives 5-year cost | Per-tag pricing with a growing plant |
| Redundancy and failover | Keeps the view alive | No written failover time |
| OPC UA certification | Future integration | Proprietary only |
| Upgrade and migration | Year-6 survival | No public version notes |
Table 2. Selection scorecard for a supervisory-control platform purchase.
Versioning and Lifecycle
A SCADA platform build is not a product you buy once, it is a system you steward for a decade. Vendors support a major version for roughly 5 to 7 years, then charge for migration. Budget the upgrade in year 6, while support still exists, not in year 11 when you are running an unpatched build on a live process. Keep the configuration in version control where practical, document every screen change, and rehearse the restore on a training server, because the day you need it is not the day to learn the tool.
Obsolescence is not only about the software. The Windows build it runs on, the browser the HMI targets, and the driver for a PLC you bought in 2009 all age on different clocks. Track them on one spreadsheet with one owner, and review it every quarter, because the gap that bites is the one nobody was watching.
Integration With Protection and Switchgear
On a 132 kV substation bus the platform does not replace the protection system, it watches it. A protection relay still trips on its own logic in milliseconds; the SCADA layer merely reports the trip, logs the waveform flag and shows the operator which breaker opened. That is why the HMI must reflect real state, not assumed state, and why the integration with switchgear and circuit breakers — a 100 A feeder or a 2 MW pump on a 50 Hz bus — is a mapping exercise, not a control one. Get the state model right and the screens almost write themselves; get it wrong and operators learn to distrust the picture, which is worse than having no screen at all.
When a SCADA Software Rollout Is the Wrong Answer
Honest engineering includes declining the purchase. Five situations argue against starting such a programme, at least until something else is fixed.
- Greenfield design stage: if the control system does not exist yet, the architecture is a one-page spec, not a remediation project; buy the zones, do not retrofit them.
- A single standalone controller: one PLC with no network path and no remote access needs hygiene and a locked cabinet, not a SCADA rollout.
- When safety is the real problem: misconfigured trips are functional-safety work under IEC 61511, and no software layer fixes them; do not let a SCADA label swallow the safety budget.
- When reliability is on fire: a plant with weekly nuisance trips gains more from maintenance discipline than from dashboards; stabilise first, then visualise.
- When the asset list is fiction: any assessment run before the device count is complete produces findings nobody can apply; count first, architect second.
A poorly matched this layer build, implemented well, still wastes the budget. Match the scope to the actual attack surface, however small, and resist the vendor who wants to sell you the enterprise module on day one.
Standards Behind the Software
The software rests on a stack of standards, and citing the right edition matters because the requirements shift between versions. The PLC languages are now IEC 61131-3:2025, which replaced the long-standing 2013 edition and added UTF-8 strings. Upward data exchange uses OPC UA, IEC 62541-1:2025. Security follows IEC 62443-2-1:2024 for the asset-owner programme, IEC 62443-3-3:2013 for security levels, and IEC 62443-4-2:2019 for component requirements. Batch and enterprise integration sit on IEC 62264-1:2013, the international form of ISA-95. Alarm management is IEC 62682, built on the ISA-18.2 practice.
| Standard | Edition | Coverage |
|---|---|---|
| IEC 61131-3 | 2025 | PLC programming languages |
| IEC 62541-1 | 2025 | OPC UA data exchange |
| IEC 62443-2-1 | 2024 | Security programme for asset owners |
| IEC 62443-3-3 | 2013 | System security levels 1 to 4 |
| IEC 62443-4-2 | 2019 | Component security requirements |
| IEC 62264-1 | 2013 | Enterprise-control integration (ISA-95) |
Table 3. Standards most often cited when specifying the software.
Further Reading on This Site
- Our SCADA overview explains the system before the software.
- The PLC programming guide covers the controller languages the software talks to.
- Our programmable logic controller piece links the hardware to the logic.
- See how SCADA meets the cabinet in our switchgear and circuit breaker guides.
Conclusion: Choosing the Right Layer Without Regret
SCADA software is the layer that makes a controlled process observable and operable, and the right choice is the one your operators trust at 3 am, not the one that won a demo. Start from the data model and the protocol drivers, size the historian to your retention, keep the safety-critical logic on site, and treat the cloud as insight, not control. Pick a vendor from the shortlist above, hold them to a written failover time and a published upgrade path, and you will still be supported when the next version lands. The work is mostly discipline: count the assets, document the alarms, patch the window, and rehearse the restore.
Frequently Asked Questions
What is the job of a SCADA system?
A SCADA system is the program layer that collects data from plant equipment, shows it to operators on screens, stores it in a historian, and raises alarms when a value leaves its limit. It sits above the PLCs and RTUs and below the business systems.
How is HMI software different from the wider SCADA layer?
HMI software is the operator-facing window; the SCADA layer is the wider system that also polls the controllers, runs the alarm engine, archives history and manages user accounts. Many products bundle both, but the HMI is only one pane of the system.
Is cloud control safe for a power plant?
It can be, provided the control functions stay on site and only aggregated data crosses the boundary through a hardened gateway. The safety-critical logic must never depend on the cloud link. Treat the perimeter as untrusted and apply IEC 62443-2-1:2024 zoning.
Which standards should the software support?
At minimum Modbus TCP, IEC 60870-5-104 and DNP3 for legacy gear, IEC 61850 for substation devices, and OPC UA (IEC 62541-1:2025) for vertical data exchange. Native drivers reduce the need for protocol converters.
How many tags can one package handle?
Small packages start around 500 tags; mid-size systems manage 5,000 to 50,000; large historian-backed deployments exceed 1,000,000 tags. Size the licence to peak tag count plus 30 percent headroom rather than today’s device list.
How long before the software is obsolete?
Plan for a 10-year lifecycle. Vendors typically support a major version for 5 to 7 years, then require paid migration. Budget the upgrade in year 6, not year 11, so you are never running an unsupported build on a live process.
Related products: SCADA System ATN-400 · RTU Communication Panel ATN-400 · PLC Control Panel for Hydropower and Pumping Stations
Written by Leon Zhang, protection application engineer. Reviewed by the relayprotect.com engineering team. Updated October 26, 2026.
Related: SCADA security
If the selection has to be checked against your switchboard, send the single-line and the ratings.




