SCADA software: how to choose the right one for your plant

Choosing SCADA software is a decision your plant will live with for ten or fifteen years: it locks in licences, maintenance, integrations and even which engineers will be able to work with you. And yet many companies decide based on a sales brochure or on "what the plant next door uses". This guide collects the criteria we apply as system integrators — with no ties to any brand — so the choice is yours, not the vendor's.

Which SCADA software should you choose for your plant?

If you ask us point-blank, the honest answer from an integrator is: it depends on four factors, and until you have them on the table you shouldn't listen to any salesperson. Any of the serious platforms we'll review below can supervise your plant; the difference is what it will cost you to build it, maintain it and expand it.

Notice that none of the four factors is "which platform has the prettiest demo". All four belong to your plant, not to the product. That is why the right exercise starts with an inventory: count your signals, list your PLCs and fieldbuses, define how many operator stations you need and find out who can service you locally. With that done, half the options rule themselves out.

The main SCADA software families

The market is wide, but in practice industrial projects revolve around a handful of consolidated platforms. Neutral descriptions, no rankings: all of them run in thousands of plants and all of them can do the job if the project is framed properly.

The integrator's criteria (that the brochure doesn't mention)

When we at Nexum evaluate SCADA software for a client, we look at things far less glamorous than the demo screens. These are the ones that ultimately decide whether the project ages well or badly. We also ask who will use the system every day: how many operators, in which language, with what experience. A platform your team can be trained on quickly, with local courses and integrators, saves more money than any licence discount.

Per-tag vs unlimited licensing

It's the first question we ask. In per-tag models you pay by signal tiers (500, 5,000, 50,000...): if your plant is small and stable it can be economical; if it grows, every expansion reopens your wallet. In per-server models with unlimited tags and clients you pay more upfront, but adding signals or stations costs no extra licence. Neither is better in the abstract: project your tags 5-10 years ahead and run the numbers with both models before deciding.

Redundancy and historian

If a supervision outage costs you money, you need to know what each platform offers in redundancy (mirrored servers, automatic failover) and what licensing it costs, because in some models redundancy doubles the bill. Same with the historian: some platforms include it, others sell it as a separate module, others rely on standard databases. Always ask what it costs to store your history at the resolution you need — not the resolution of the demo.

Protocols: OPC-UA, Modbus, Profinet

A SCADA is only as good as its communications. Verify native support for OPC-UA — the open standard that makes you vendor-independent, maintained by the OPC Foundation — plus the fieldbuses already living in your plant: Modbus TCP/RTU, Profinet, EtherNet/IP. With a mixed PLC fleet, driver quality matters more than any screen feature: it's the difference between integrating in days or in weeks.

Cybersecurity and NIS2

The SCADA is the gateway between your OT network and the rest of the world, and with the NIS2 directive OT security has stopped being optional for many industries. Demand robust authentication, encrypted communications, role-based user management and a serious patching track record from the vendor. We cover this in depth in our guide on NIS2 and industrial OT cybersecurity: if your company falls within the directive's scope, this criterion becomes eliminatory.

Cloud or on-premise SCADA?

More and more platforms offer cloud or hybrid deployment. The decision is not about fashion but about your process:

Our practical rule as integrators: control and the supervision production depends on stay on site; analytics, reporting and the corporate multi-site view go wherever they work out best — usually the cloud. Hybrids with a local historian and cloud aggregation are today's most common balance in mid-sized plants.

Total cost of ownership: what you'll really pay

The licence is only the tip of the iceberg. A complete SCADA project includes engineering (screens, communications, alarms, testing), servers and network, training, and the software's annual maintenance, which typically runs at 15-20% of the licence price. With that full picture, and as indicative ranges from real projects:

• Machine-level or small-process SCADA (one server, a few hundred tags): in the region of €15,000-30,000 for the complete project.
• Mid-sized plant SCADA (several thousand tags, historian, several stations): in the region of €30,000-80,000.
• Redundant or multi-plant SCADA (high availability, MES/ERP integration): from €80,000, frequently above €150,000.

Within these ranges, engineering usually outweighs the licence: it commonly accounts for half the budget or more. That is why two quotes for the same software can differ by tens of thousands of euros. We break down the line items and examples in how much a SCADA system costs; use it to read quotes critically before comparing.

One line item deserves its own mention: migration. If you are replacing an existing SCADA, budget for recreating screens, transferring the tag database and running both systems in parallel during changeover. Migrations rarely come in below a third of a new project, and they are the moment when the quality of your current documentation — or its absence — turns into money.

Typical mistakes when choosing SCADA software

We list them because we keep seeing them. Avoid these five and you're already choosing better than average:

• Choosing on the demo rather than the licensing model: the demo lasts an hour; the licence, fifteen years.
• Not projecting tags into the future: buying the exact signal tier and paying for the expansion at the price of someone who can't negotiate.
• Ignoring the real PLC fleet: a magnificent SCADA with mediocre drivers for your controllers is an expensive project.
• Forgetting who will maintain it: with no local integrators trained on that platform, every modification depends on a single supplier.
• Confusing SCADA with HMI and buying more (or less) than the process needs; we explain the difference in SCADA vs HMI.

Frequently asked questions