Ignition vs FactoryTalk vs Wonderware: an honest SCADA platform comparison
I build in Ignition, so I'll tell you straight where FactoryTalk and Wonderware still beat it. This is how the three compare on licensing, architecture, openness, and cost at scale, from someone who has run all three.
How to compare SCADA platforms without the sales pitch
Most SCADA platform comparisons you read online were written by whoever is selling the license. I sell my labor, not a platform, and I've built and maintained systems on Ignition, FactoryTalk, and Wonderware, so I'll try to keep this fair. There's no best SCADA platform in the abstract. What matters is which one fits the PLCs you run, the way your budget scales, the people who maintain it, and where the plant is headed in five years.
Five things decide it, and I'll walk each one: how the license is priced, whether the client is a thick Windows app or a browser, how open the platform is to non-vendor gear and MQTT, what it costs once the plant grows, and how deep the local support bench is. Ignore the feature checklists. Every one of these platforms can draw a trend and throw an alarm. The differences that cost you money show up in how they're built and how they're sold.
Licensing: where the cost actually lives
FactoryTalk View SE and Wonderware (now AVEVA) price by tags, clients, or displays. FactoryTalk counts clients and displays. Wonderware System Platform counts I/O tags and galaxy size. Grow the plant, add screens and operator stations, and the license bill climbs right along with it. That's the model that surprises people two years in, when a line expansion turns into a license true-up nobody budgeted for.
Ignition prices by the server, not the tag or the client. One gateway license. After that, tags, clients, and screens are all unlimited. You pay once for the modules you use (Perspective, SQL Bridge, a driver suite) and build as much as you want on top. For a plant that's growing, that math tends to win. For a small fixed system that will never change, the per-tag platforms can come in cheaper up front.
- FactoryTalk View SE: licensed by client and display count, tied to the Rockwell/FactoryTalk stack. Costs scale as you add screens and operator stations.
- Wonderware / AVEVA System Platform: licensed by I/O tag count and galaxy size. Big tag counts on a large plant get expensive, and the model quietly pushes you to keep tags down.
- Ignition: licensed per server (gateway), unlimited tags and clients. You pay for modules once, then scale the build at no extra license cost.
Architecture: thick client vs the browser
FactoryTalk View SE and Wonderware InTouch/System Platform are thick-client platforms at heart. The runtime is a Windows application installed on each station. It works, and it's fast on the local network, but every client is one more Windows machine somebody has to patch and keep on an OS the software still supports. Remote access usually means RDP or a terminal server, which is one more thing to license and secure.
Ignition Perspective runs in a browser. The gateway serves the screens, and anything with a browser (a panel PC on the line, a phone in the parking lot, a laptop in the office) becomes a client with no install. Ignition also still ships Vision, its own thick client, if you want the traditional model. Having both under one license is part of why I default to it. You're not betting the whole plant on one delivery method.
The browser model isn't free of tradeoffs. Perspective wants a solid gateway server and a network that stays up, and a badly specced server will feel it. But for multi-site visibility and mobile access, not reinstalling a client on forty machines is a real day-to-day saving.
Openness, MQTT, and the lock-in question
This is where the platforms split hard. FactoryTalk is a Rockwell product built to run best on Rockwell PLCs. If your floor is all ControlLogix and CompactLogix, that tight coupling is a feature. The day you add a Siemens S7-1500 or inherit a mixed fleet, FactoryTalk starts working against you.
Ignition is vendor-agnostic by design. It talks Allen-Bradley, Siemens, Modbus, and OPC UA through its own drivers, and it was one of the first SCADA platforms to take MQTT Sparkplug B seriously. That matters if you're building a Unified Namespace or pushing data to the business side without a stack of middleware. Wonderware connects widely too, through OI/DAServers and OPC, but it's a heavier, more license-laden path to the same place.
Lock-in is the honest concern with any of them. Your screens, scripts, and tag database are platform-specific no matter which you pick, and nobody hands you a clean export. What Ignition does better is keep your data open. History goes into standard SQL databases you control, and native MQTT means your production data isn't trapped inside a proprietary historian. Your build stays specific to the platform. Your data doesn't have to.
Ignition vs FactoryTalk: the Rockwell-shop case
I'll say it plainly. If your plant is all Allen-Bradley, your maintenance team lives in Studio 5000 every day, and you already run FactoryTalk Historian and asset management, FactoryTalk View SE is a reasonable call. The diagnostics between the PLC and the HMI are tighter. Your people already know the tools. There's something to one vendor's throat to choke when it breaks.
Where FactoryTalk hurts is cost at scale and openness. The licensing climbs as you grow, the client is thick, and the day you add a non-Rockwell PLC you feel the walls. For a single-vendor plant that isn't going to change, that may never bite. For a plant that's growing or mixing brands, it usually does.
Ignition vs Wonderware (AVEVA): the installed-base case
Wonderware, now AVEVA, has decades of installed base and a deep template model in System Platform. If you already run a large galaxy, have staff who know it cold, and have standardized your object templates across sites, ripping it out for the sake of it is a bad trade. The platform is capable and the ecosystem is large.
The friction is the licensing and the direction of the product. Tag-based pricing punishes big plants, the thick-client model carries the same patching overhead as FactoryTalk, and AVEVA's push toward subscription and cloud has left some long-time users uneasy about where their costs go next. If you're happy and stable, stay. If you're staring at a big true-up or a forced modernization, that's the moment to price Ignition against it honestly.
So what's the best SCADA platform?
There isn't one, and anyone who tells you there is wants to sell you a license. The best SCADA platform is the one that fits your PLC fleet, your growth plans, your budget curve, and the people who'll maintain it. FactoryTalk fits all-Rockwell shops. Wonderware fits big existing AVEVA sites. Both are real answers, and I'll tell you when you're looking at one.
I lean Ignition for most of what I build. It's vendor-agnostic, so I'm not forced to match your SCADA to your PLC brand. The per-server license means a growing plant doesn't get a growing bill. Because the client runs in a browser, there's less software to babysit machine by machine. And history lands in standard SQL with native MQTT on top, so your data stays closer to open than it would on the others. For a Central Florida plant without a controls engineer on staff, that mix usually costs less to own over five years and is easier to hand back to your own team. If your situation calls for one of the other two, I'll price it that way and say so.
Trying to pick a SCADA platform, or stuck on one you regret?
Bring it to a 15-minute call. Tell me what PLCs you run, what your license bill looks like, and what you're trying to see that you can't today. You'll get a straight read on whether Ignition, FactoryTalk, or Wonderware fits, even when the honest answer is stay put. Call (321) 378-0424 and the engineer who does the work answers.