Choosing a SCADA Platform: Ignition, Citect, WinCC and Experion

Every SCADA selection I have sat through eventually turns into an argument about which HMI looks nicer. That is the wrong argument. The screens are the part you can change. What you cannot easily change is the licensing model you signed, how open the data layer is, who in the Gulf can actually support the thing, and whether an upgrade in year four forces a forklift replacement. This guide compares Ignition, AVEVA Plant SCADA (Citect), Siemens WinCC and Honeywell Experion across the criteria that still matter in year five.

Licensing model: unlimited-tag vs per-tag

This is the single biggest cost driver over five years, and the platforms split cleanly. Ignition sells server-based licensing: you buy the server and get unlimited tags, unlimited clients and unlimited screens under that server. Add points and your licence cost does not move. Citect (now AVEVA Plant SCADA) and Siemens WinCC have historically been point-based or tag-tiered: you buy a bracket of tags, and crossing into the next tier costs money. Experion is a full DCS-grade platform licensed by controllers, points and stations, priced as a Honeywell-integrated system rather than an off-the-shelf tag bundle.

The practical effect: on a small, static system the per-tag models can come in cheaper. On a growing utility or a multi-site estate, the unlimited-tag model wins decisively once you cross the crossover point, which I work through in the TCO example below.

Openness of the data layer

Ask one question of any SCADA vendor: how do I get my data out without paying you again? Openness is measured by native support for open protocols, OPC UA in particular, and by whether the tag database and history are reachable through documented, non-proprietary interfaces.

Ignition is built around a database-centric, OPC UA-first architecture, which makes downstream integration to a historian, an EAM or an analytics stack straightforward. Plant SCADA and WinCC both speak OPC UA well but keep more of the value inside their own ecosystems. Experion is the most closed of the four by design; it is a tightly integrated control system where the openness you get is the openness Honeywell exposes, which is real but on their terms. For why this matters downstream, see my notes on SCADA historian integration and the broader picture in enterprise system integration explained. A useful neutral reference on the protocol itself is the OPC Foundation .

Historian bundling

A historian is where your time-series data lives, and whether one ships with the platform changes both cost and lock-in. Ignition bundles a tag historian that writes to a standard SQL database you choose (PostgreSQL, SQL Server, MySQL), so your history sits in a database you can query directly. AVEVA sells the historian as a separate, powerful product (AVEVA Historian, formerly Wonderware), so budget for it as a line item. WinCC has its own historian tiers and integrates with the Siemens data stack. Experion ships with Honeywell's historian in the integrated bundle.

The buying test is simple: is my history in a format I can reach with standard tools, or only through the vendor's client? A bundled historian in a proprietary store is convenient until the day you want to feed an asset management system, which is exactly the scenario I cover in SCADA to EAM integration.

Cost of adding clients

Client licensing is where budgets quietly blow up. Under Ignition's server model, web-launched clients are unlimited, so a control room, a manager's laptop and fifty tablets cost the same as one. The per-seat or per-station models on the other platforms charge for concurrent or named clients, so every new operator station or remote viewer is a fresh cost. If your operation is a single fixed control room, this rarely bites. If you are rolling out mobile access to field crews across a water network, it compounds fast.

Integrator availability in the Gulf

This is the criterion buyers underweight and regret most. In the UAE, Saudi Arabia and the wider Gulf, Siemens and Honeywell have deep, long-established system integrator and channel networks, especially in oil, gas, power and water, where they are often the incumbent. AVEVA (Plant SCADA and the wider portfolio) also has strong regional presence through its integrator base. Ignition adoption in the Gulf is growing and has capable local integrators, but the pool is smaller than the Siemens or Honeywell bench.

Read that as availability, not quality. A smaller pool of genuinely competent Ignition integrators can beat a large pool of mediocre ones. But if the one firm that knows your system walks away, platform popularity is what determines whether you can replace them in a month or a year.

Upgrade and version-lock risk

Version lock is the risk that a future upgrade forces disruptive rework or a hardware refresh. The heavier and more integrated the platform, the higher this risk tends to be. Experion upgrades are major, planned, DCS-grade events aligned to Honeywell's lifecycle. WinCC upgrades track Siemens TIA and runtime versioning, which can strand older projects. Plant SCADA has carried strong backward compatibility over the Citect lineage but still has migration steps between major versions. Ignition's model, with a standard database back end and web-delivered clients, tends to make upgrades lighter, though scripts and modules still need regression testing. No platform is upgrade-free; the question is how big and how forced each jump is.

Scorecard and typical fit

The table below scores each platform 1 to 5 on the criteria above (5 is best for the owner) and notes the environment each fits most naturally. Read the fit column as tendency, not a rule; all four run in most settings.

Building-centric estates (BMS-heavy sites) usually reach these platforms through a supervisory layer rather than head-on; Ignition and Plant SCADA sit most comfortably there, while Experion is rarely the right tool for a building.

Five-year TCO: a 15,000-tag water utility

Numbers make the licensing argument concrete. Take a water utility with 15,000 tags, three operator stations, and a handful of remote viewers, over five years. These are illustrative planning figures, not quotes; treat them as the shape of the cost, not the price.

At 15,000 tags the unlimited-tag model is already well past the crossover. The crossover point, where the two models cost roughly the same, sits far lower, in the region of 3,000 to 4,000 tags plus a couple of extra clients in this cost structure. Below that a small, static system can favour per-tag; above it the unlimited model pulls away and never looks back.

Now double the tag count. Take the utility to 30,000 tags in year three as the network expands. The unlimited-tag total barely moves, because tags are free under that model; you might add a second server for redundancy, call it another $30,000, for roughly $125,000. The per-tag model roughly doubles its tag line and drags maintenance up with it, pushing past $340,000. The gap widens from about 2.5x to nearly 3x. The lesson is blunt: if you expect to grow, model the growth case, not today's tag count.

The point most selections miss

After all the scoring, here is what actually determines whether your SCADA project is a success in year five: the availability of a competent local integrator, and your own ability to hold the tag database, the screens and the scripts. A platform you cannot get supported in the Gulf is a liability regardless of its features. A platform whose configuration lives only in an integrator's laptop is a hostage, regardless of how open the data layer claims to be.

So write ownership into the contract. You should receive, and be able to open without the integrator, the complete tag database, the HMI screens, and every script and module. Ask for a documented handover and prove you can restore the system from your own copy. This single clause protects you more than any feature comparison in this guide.

Cloud and hybrid SCADA claims

Every vendor now has a cloud or hybrid story. Some of it is genuinely useful for dashboards, analytics and multi-site aggregation. Some of it is marketing draped over the same on-premises product. For a water utility or any critical infrastructure owner, two questions cut through the pitch, and you should demand both answers in writing.

• Offline operation. If the internet link drops, does local control and monitoring continue fully, with no loss of alarming or historisation? For critical infrastructure the honest answer must be yes; the cloud is for aggregation, never for the control loop. Get the exact degraded-mode behaviour documented.
• Data egress and ownership. Where does the data physically sit, who can access it, and how do you get a full export out, in an open format, if you leave? Ask about egress fees, data residency inside the UAE or KSA where regulation may require it, and the exit process. If a vendor cannot answer the exit question crisply, that is your answer.

Vendor references worth reading directly rather than through a reseller include Inductive Automation for Ignition and AVEVA for Plant SCADA and the historian. Read the licensing pages yourself; do not rely on a slide.

A note on independence

This is independent guidance, not a paid review. No vendor sponsored this comparison, saw it before publication, or had any editorial input. The scores are my own judgement from owner-side and integrator-side work, and I hold no reseller relationship that depends on you picking one of these platforms. Because licensing models change frequently, verify every commercial detail with each vendor before you decide; the comparison table is date-stamped as at August 2026 for exactly that reason.

Conclusion

All four platforms are competent; none of them will fail you on technical merit alone. Ignition wins on licensing value and openness for growing, multi-client utility systems. WinCC and Experion win on Gulf support depth and suit tightly integrated plant and process environments. Plant SCADA sits in between with a strong historian story. But make your decision on total five-year cost with your growth case, on whether you can get real local support, and on whether you will genuinely own your tag database, screens and scripts. Decide those three well and the logo on the HMI matters far less than the room thinks it does.