Ignition vs Wonderware vs FactoryTalk: 2026 SCADA Comparison

Short answer (skip the rest if you’re in a hurry): in 2026, Ignition vs Wonderware vs FactoryTalk still resolves the same way it has for the last four years, only sharper. Ignition 8.3 (Inductive Automation) wins on licensing economics, cross-platform deployment, web-native HMI, and raw developer velocity — it is the default pick for greenfield plants, integrators chasing margin, and any team comfortable with Python and SQL. AVEVA System Platform 2023 R2+ (the artist formerly known as Wonderware) wins on heavyweight process applications, model-driven engineering at scale, batch/recipe execution, and integration with AVEVA PI and Insight. Rockwell FactoryTalk View SE 14 wins almost by default in plants where 70 %+ of the PLC fleet is Allen-Bradley ControlLogix or CompactLogix, where the OT team already lives inside Studio 5000, and where the certified system integrator bench is FactoryTalk-shaped.

This post is written from the seat of a controls engineer who has commissioned and maintained sites on at least two of these platforms — not from a vendor brochure. We will compare architecture, licensing, edge stories, total cost of ownership, decision matrices, and migration paths, and we will name the gotchas that the sales decks won’t.

If you also need the upstream context — “why do I need SCADA at all, on top of PLCs?” — start with our PLC vs SCADA explainer. And if you have already gone one layer up the stack into operational intelligence and unified namespace, our AVEVA PI vs Cognite Data Fusion vs Tulip comparison is the natural companion piece.

The three platforms in 2026 at a glance

The table below is the cheat-sheet version. Everything that follows is the long-form justification.

Dimension	Ignition 8.3	AVEVA System Platform 2023 R2+ (Wonderware)	Rockwell FactoryTalk View SE 14
Architecture	Single gateway JVM + Designer + Perspective/Vision clients	ArchestrA Galaxy model + IDE + IAS runtime nodes + InTouch OMI	FT Directory + HMI Server pairs + FT Linx data servers + Studio 5000
Licensing model	Unlimited tags, unlimited clients, per-server	Per-IO count + per-CAL + module add-ons (Historian, Batch, MES)	Per-display + per-client + Logix CAL + Historian CAL
OS support (server)	Windows, Linux, macOS, Docker, ARM64	Windows Server only (2019/2022)	Windows Server only (2019/2022)
OS support (client)	Any modern browser, iOS, Android, native Vision on Win/Linux/Mac	InTouch OMI on Windows, Web HMI (HTML5) on any modern browser	FT View SE Client on Windows, ThinManager terminals, limited web via VantagePoint
Web/mobile HMI	Perspective is first-class, responsive, mobile-native	AVEVA Web HMI matured significantly post-2022, still secondary to OMI	Limited; vendor pushes ThinManager / Datamosaix for browser-grade UX
Edge story	Ignition Edge — same engine, cut down, MQTT/Sparkplug native	AVEVA Edge (formerly InduSoft) — separate codebase, lighter footprint	FactoryTalk Edge Gateway — Smart Object modelling, AB-centric drivers
Alarm engine	Pipelines, journaling to SQL, mobile notifications built-in	Distributed alarms via Galaxy, A&E history in Historian	FactoryTalk Alarms & Events, tightly coupled to Logix alarm instructions
Historian	Tag Historian (any SQL), or Ignition + Canary / PI	AVEVA Historian (SQL Server backend) — strong native fit	FactoryTalk Historian SE (OSIsoft PI core) + Datamosaix (cloud)
Scripting / extensibility	Jython 2.7 across gateway, client, scripts, components	QuickScript .NET, VB-style, .NET object scripts	VBA in displays, structured text-style in Logix; limited HMI-side automation
AI/ML hooks	Native Python ML libs via modules; MQTT to external Python services	Insight ML, AVEVA Predictive Analytics, Connect platform	FT Analytics for Devices, FT DataMosaix integrations
Multi-site / enterprise	Enterprise Administration Module (EAM) + gateway network	Galaxies federated, multi-galaxy with Connect	Network Distributed application, FT Directory federation
Audit / compliance (21 CFR Part 11)	Audit profile + e-signature components	Mature, validated in pharma deployments	Mature, deep FDA install base in Rockwell life-sciences plants
Latest stable (mid-2026)	Ignition 8.3 (with 8.1 LTS still supported)	System Platform 2023 R2 (some shops still on 2020 R2 SP1 P01)	FactoryTalk View SE 14, FT Historian SE 9.x

A few of those rows will surprise people who haven’t repriced a stack in a few years. We’ll come back to licensing economics in a dedicated section.

Ignition 8.3 (Inductive Automation) — architecture and design philosophy

Ignition’s organising principle is unchanged since 2010: one server, unlimited tags, unlimited clients, single license per gateway. Everything else is downstream of that decision.

In a typical 2026 deployment, an Ignition Gateway runs as a JVM process — increasingly inside a Linux VM or container, often Rocky Linux or Ubuntu LTS — and connects southbound to PLCs through OPC UA, EtherNet/IP, Siemens S7, Modbus TCP, and a stable of vendor drivers. Northbound it serves three classes of client: Perspective projects (HTML5, responsive, mobile-aware), Vision projects (the legacy thick Java client, still widely deployed and still supported), and Designer Launcher for engineering. Tag history, audit, and alarm journals are stored in any supported SQL backend — Postgres is the modern default, Microsoft SQL Server is fine, MariaDB and Oracle work.

The 8.3 release matured several things that had been “almost there” in 8.1:

• Perspective Workstation — a dedicated runtime that gives you Vision-style desktop kiosks without the browser.
• Native Linux + ARM64 gateway support at production quality, which makes panel-PC and edge IPC deployments cheaper.
• Tag groups and tag history overhauls that finally let you tune scan rates and on-change semantics per group without scripting.
• Improved Perspective component library, including better SVG handling for P&IDs and digital-twin overlays.
• Sparkplug B 3.0 alignment in MQTT Engine / MQTT Transmission, which is what most unified-namespace projects in 2026 actually run on.

Design philosophy matters here. Ignition treats SCADA as a software engineering problem with industrial constraints, not the other way around. You get Jython 2.7 scripting everywhere — gateway startup, tag value changes, button event handlers, alarm pipelines, scheduled scripts. You get direct SQL access from any binding. You get a Git-able project export. You get a REST API for the gateway. The trade-off is that the platform assumes you have, or are willing to build, an engineering team that thinks like software developers. Plants whose OT culture is “drag, drop, ladder, done” sometimes find Ignition’s openness intimidating; plants who want to ship features find it liberating.

The licensing model — unlimited clients, unlimited tags — has a second-order effect that is hard to overstate: it removes the incentive to under-instrument. On a per-tag-licensed platform, engineers quietly cut history points to stay under the next license tier. On Ignition, the cost of one more tag is zero, so the historian gets richer, the digital twin gets more faithful, and analytics get better inputs.

Where Ignition is not the obvious answer: very heavyweight batch/recipe applications (ISA-88 with hundreds of recipes and validated phase logic), and shops with an enormous Rockwell PLC fleet where the integration story with Studio 5000 and FactoryTalk Alarms & Events runs out of road — Ignition reads Logix tags fine over EtherNet/IP, but it doesn’t natively consume Logix tag-based alarms with the same fidelity FactoryTalk does.

AVEVA System Platform (Wonderware) — model-driven and ArchestrA

If Ignition’s organising principle is “one server, unlimited everything”, AVEVA System Platform’s is “build the plant model once, instantiate it everywhere”. That model is the ArchestrA object framework, and it lives in the Galaxy Repository — a SQL Server-backed object database that is the single source of truth for the application.

You define templates — $Pump, $Valve, $Reactor, $ConveyorSection — with their I/O, scripts, alarms, history, security, and graphics packaged together. Instances (Pump_P12, Reactor_R101) inherit from templates and override only what’s different. Change the template and every instance updates on the next deployment. For a process plant with hundreds of nearly-identical assets, this is the right abstraction; it is also why AVEVA dominates downstream oil and gas, mining, water/wastewater, food and beverage, and large-scale pharma.

Runtime nodes — IAS (Industrial Application Server) engines — host the deployed objects, talk to field devices through DAServers / OI Gateways (OPC UA, OPC DA, Suitelink, native protocol gateways), and feed the AVEVA Historian (still SQL Server underneath, with the proprietary time-series compression on top). Visualisation comes from InTouch OMI (the OMI ViewApp model, typically running on a terminal server) and increasingly from AVEVA Web HMI for HTML5 thin clients.

The 2023 R2 release line (and subsequent service packs through 2026) brought several things worth flagging:

• AVEVA Web HMI is now genuinely usable for production HMIs, not just dashboards. The component library covers what most ViewApps need, although bespoke graphics still tend to live in OMI.
• AVEVA Connect is the cloud control plane, replacing the older Insight standalone model. Galaxy-to-cloud publishing is now a first-class integration.
• Operations Control as a packaged offering bundles System Platform, Historian, MES, and Insight into one SKU — pricing depends heavily on negotiation, plant scale, and AVEVA’s appetite for the logo.
• InTouch HMI continues as a standalone option for smaller, single-node sites that don’t justify the full System Platform model.

The trade-off is that everything in AVEVA’s world assumes Windows Server. There is no Linux runtime, no container story for the IAS engines, no ARM64. If your IT organisation has moved to a “Linux-default, Windows-where-necessary” posture (which a lot of mid-market manufacturers have, post-2022), this will create friction. The Galaxy Repository in particular is a hefty SQL Server deployment that wants its own infrastructure planning.

The other trade-off is engineering cost. ArchestrA is powerful but it is not drag-drop-and-ship. You need an integrator (or an in-house team) who knows the object model, knows QuickScript .NET, knows the DAServer and OI ecosystem, and knows how to commission a Galaxy without painting themselves into a corner. The AVEVA integrator network is global and mature, but rates reflect the specialist skillset.

Where AVEVA wins clearly: process industries with strong asset templating opportunity (refineries, mining concentrators, large utilities), AVEVA PI shops that want native upstream/downstream integration, plants with heavy ISA-88 batch requirements (AVEVA Batch Management module), and regulated pharma sites with mature validation packages.

Rockwell FactoryTalk — Logix-tight stack

FactoryTalk is not really one product; it is the collective name for Rockwell’s HMI/SCADA/historian/edge/analytics stack, designed to integrate tightly with ControlLogix and CompactLogix PLCs programmed in Studio 5000 Logix Designer. For the purposes of this comparison, “FactoryTalk” means primarily FactoryTalk View SE 14, with the supporting cast of FactoryTalk Linx (data server), FactoryTalk Alarms & Events, FactoryTalk Historian SE, FactoryTalk Edge Gateway, ThinManager, and increasingly FactoryTalk Datamosaix (the rebranded, PI-derived cloud historian).

The story FactoryTalk tells best is end-to-end Rockwell. A Logix tag in Studio 5000 surfaces in FactoryTalk Linx without manual address mapping; a Logix alarm instruction (ALMD / ALMA) appears in FactoryTalk Alarms & Events; that alarm flows to FT View SE displays, gets historised in FT Historian (which is OSIsoft PI under the bonnet), and shows up in VantagePoint reports and Datamosaix dashboards. ThinManager publishes the SE clients to zero-client terminals on the floor with cached failover. Inside that walled garden, the integration is genuinely tight, and for a discrete manufacturing plant with thirty CompactLogix PLCs, it is the lowest-friction path to a working SCADA.

The 2026 reality for FactoryTalk View SE 14:

• FactoryTalk Optix is Rockwell’s modern, web-native HMI platform aimed at greenfield projects and at slowly displacing FT View SE / ME over the next decade. Optix is not yet a like-for-like replacement on large multi-server SE applications, so most existing sites will run SE for several more years.
• FactoryTalk Datamosaix has become the de-facto cloud historian/visualisation story, replacing some of the older Historian SE workflows for new builds.
• FactoryTalk Edge Gateway matured into a credible MQTT/Sparkplug edge node, but it is still strongly biased toward AB drivers and CIP-based access.
• FactoryTalk Hub consolidates Rockwell’s cloud services (Datamosaix, Vault, Analytics) behind a single identity layer.

The honest trade-offs:

• Windows-only, end to end. Servers run Windows Server 2019/2022 with specific Microsoft SQL Server versions; deviating from the supported matrix is unwise.
• Licensing is the most fragmented of the three. You will buy FT View SE Server licenses, Client Access Licenses (CALs) for thick and thin clients, Logix CALs for the data servers, separate Historian licenses, ThinManager licenses, and so on. Negotiated bundle SKUs help, but the line-item count is real.
• Cross-vendor PLCs feel second-class. You can talk to a Siemens or Modicon PLC from FT Linx through OPC UA, but you lose the auto-discovery, alarm-instruction-passthrough, and tag-browse experience that makes Rockwell-on-Rockwell so smooth. In plants with a mixed fleet, this is the single biggest reason engineers eventually evaluate Ignition.
• Web/mobile HMI is the weakest of the three. VantagePoint and Datamosaix cover dashboards well; production-grade browser HMI on FT View SE is not where Perspective or AVEVA Web HMI are. Optix is the long-term answer; today it does not yet carry large SE applications.

Where FactoryTalk wins clearly: any plant where Rockwell PLCs already dominate, where the in-house controls team is Studio 5000-fluent, where the validated integrator bench is FactoryTalk-shaped, and where the procurement path through Rockwell is well-trodden.

Edge stories compared (Ignition Edge, AVEVA Edge, FactoryTalk Edge)

The “edge SCADA” conversation in 2026 is mostly really three different conversations:

Ignition Edge is the same Ignition gateway engine with feature flags. You get a small footprint (designed to run on industrial PCs, panel PCs, or even Raspberry Pi-class hardware in some deployments), a limited tag/client count, and the full Ignition driver set. Crucially, store-and-forward to a central gateway works the same way as it does between two full gateways, and the Edge node can publish Sparkplug B to an MQTT broker — which is how most unified-namespace architectures today actually federate plant-level Ignition Edge nodes up to a corporate Ignition gateway or to an MQTT-based data fabric. The “same engine, smaller envelope” approach means engineering reuse is excellent.

AVEVA Edge (the codebase that used to be InduSoft Web Studio) is a separate product from System Platform. It is a capable, lightweight Windows-based HMI/SCADA suitable for OEM machine builders, kiosk applications, and edge gateways. Integration with System Platform is via standard protocols (OPC UA, MQTT) rather than via a shared object model — meaning if you want plant-floor edge nodes that participate in your ArchestrA Galaxy, AVEVA’s recommended pattern is actually System Platform IAS nodes running at the edge, not AVEVA Edge.

FactoryTalk Edge Gateway uses “Smart Object” data models, integrates with FactoryTalk Hub and Datamosaix in the cloud, and is comfortable with AB drivers (CIP, EtherNet/IP) plus OPC UA. It is the right answer for Rockwell-shop edge data ingest into Datamosaix. It is less obviously the right answer for a vendor-neutral edge node that needs to serve as a local HMI.

Practical observation from integrator-led projects: in mixed-vendor plants with a unified-namespace ambition, Ignition Edge plus MQTT Sparkplug B is the architecture that gets reached for most often, even on sites whose central SCADA is FactoryTalk or AVEVA. The edge tier and the supervisory tier do not have to be the same vendor.

Licensing economics and TCO in 2026

We will not invent specific numbers — vendor pricing is negotiated, regional, channel-dependent, and changes faster than any blog post. What we will do is describe the shape of each cost curve, which is what actually drives decisions.

Ignition’s curve is flat and predictable. You buy a gateway license (Standard or Edge, plus optional modules — Reporting, MQTT, EAM, Perspective, Vision, OPC UA, SQL Bridge, etc.). Tags and clients are unlimited. Adding a new line, a new dashboard, or another fifty operators costs zero in license terms. The cost you add later is engineering time and infrastructure. Integrators report that on a 5-year TCO basis, Ignition is often the cheapest of the three for sites with more than a handful of clients or more than a few thousand tags — particularly on Linux infrastructure where Windows Server CAL costs disappear too.

AVEVA’s curve scales with I/O count and module footprint. System Platform licenses come in I/O tiers; Historian is licensed by tag count; Batch Management, MES, Insight are separate modules. For a small site this can look expensive; for a very large process plant, the model maps reasonably well to the value being delivered (a big plant has a lot of I/O and needs a lot of modules anyway). The Operations Control bundle smooths some of the edges. Be aware that CAL counts and ViewApp seat counts are a real line item — these are the licenses that often get under-estimated at the proposal stage and over-run at site.

FactoryTalk’s curve has the most line items. You buy FT View SE Server, Studio (engineering), Client Access Licenses for displays and clients, Logix CALs in FT Linx, Historian SE points, VantagePoint / Datamosaix subscriptions, ThinManager licenses, and so on. Many shops end up with the TechConnect support contract on top, which is non-trivial. The headline view: per-site, FactoryTalk is typically the most expensive of the three when measured purely on software list price, but the incremental cost versus a plant that already owns Studio 5000, FT Linx, and FT Asset Centre is much smaller. Integrator-reported ranges vary widely; the honest framing is “expect to pay for the integration you’re getting.”

A subtle but important point: support cost matters more than license cost over a 10-year lifecycle. AVEVA Customer FIRST, Rockwell TechConnect, and Ignition’s support contract are all priced differently and offer different SLAs. Most plants discover this on the day a primary historian node fails at 2 a.m.

Decision matrix: when each one wins

If you want a one-page decision tree, this is the one we hand to plant managers asking the question for the first time.

In words:

• Choose FactoryTalk View SE 14 (+ FT Historian / Datamosaix) when your PLC fleet is dominated by ControlLogix / CompactLogix; your in-house team is fluent in Studio 5000; your application is largely discrete or hybrid; your integrator bench is Rockwell-certified; and your IT organisation is comfortable on Windows Server.
• Choose AVEVA System Platform 2023 R2 + Historian + InTouch OMI when you have a heavy process application (refining, mining, water, food, large pharma); you have strong asset-templating opportunity (many near-identical pumps / reactors / lines); you already own AVEVA PI or have AVEVA elsewhere in the enterprise; or you need ISA-88 batch and validated pharma workflows.
• Choose Ignition 8.3 (Perspective + MQTT/Sparkplug) when you want web and mobile HMI as a first-class deliverable; you run a mixed PLC fleet; you have or can build a team comfortable with Python and SQL; you want a unified-namespace architecture; you want Linux/container deployment; or you are CapEx-constrained and need licensing to scale flat rather than steeply.
• Hybrid Ignition front-end over AVEVA PI / Historian is increasingly common in 2026 — keep the time-series store you have and the validated tag library, but modernise the visualisation tier and add a mobile story without ripping out the historian.

These rules are not absolute. The single biggest determinant we see in practice is who you can hire or contract. A theoretically optimal Ignition deployment that no local integrator can support is worse than a slightly-overpriced FactoryTalk one that three certified partners are willing to commission in six weeks.

Trade-offs, gotchas, and migration paths

Ignition gotchas the brochure doesn’t mention.
– The Vision module is supported but no longer the strategic future; new development should default to Perspective. Migrating large Vision projects to Perspective is a project, not a click.
– Jython 2.7 is the scripting runtime. It is not Python 3. Most of what you want works; some third-party libraries don’t, and you bridge them via REST or external Python services.
– Sparkplug B implementations across vendors are not 100 % identical. Test edge-to-broker-to-gateway scenarios end-to-end before committing the architecture.
– Gateway upgrades — particularly 8.1 LTS to 8.3 — are well-documented but should be rehearsed on a clone before touching production.
– Reading Logix tag-based alarms from Studio 5000 does not give you the same alarm-instruction passthrough you get in FactoryTalk. If alarm fidelity from Logix matters, factor that into the design.

AVEVA gotchas.
– Windows-only is genuinely Windows-only. Plan SQL Server licensing and patching alongside the Galaxy.
– Galaxy version upgrades are non-trivial. Plants on 2017 / 2020 versions face a real migration effort to get to 2023 R2 — usually a parallel-build-and-cut-over, not an in-place upgrade.
– ArchestrA template design is a discipline. Bad template architecture early in a project becomes expensive technical debt for the life of the plant.
– AVEVA Web HMI is good in 2026 but still maturing; component-library gaps will occasionally force you back into OMI.
– The naming churn (Wonderware → Schneider Electric → AVEVA → AVEVA-with-Schneider) is real and shows up in documentation, training materials, and certifications. Budget time for your team to mentally re-map terms.

FactoryTalk gotchas.
– Mixed-vendor PLC fleets are second-class citizens. Plan for it.
– The license stack has many SKUs; build a spreadsheet, validate it with your channel partner, and assume some line items will be discovered late.
– FT View SE clustering and redundancy are well-understood but configuration-heavy; spend the time on the FT Directory architecture up front.
– The roadmap clearly points toward FactoryTalk Optix for new HMI work. Greenfield projects in 2026 should evaluate Optix on its merits before defaulting to View SE — but should also be honest about Optix’s current ceiling on large multi-server applications.
– TechConnect contract scope is critical. Know what’s covered and what isn’t before you need a 24/7 callback.

Migration paths worth knowing.
– Wonderware → Ignition: usually a re-platform, not a port. Tags migrate via OPC bridges; graphics are re-built in Perspective; alarms are re-designed in pipelines.
– FactoryTalk SE → Ignition: similar pattern. The data layer (FT Linx → Ignition OPC UA) is straightforward; the graphics layer is a re-design.
– Vision → Perspective (within Ignition): same vendor, same scripting, but component models differ. Plan for a project.
– System Platform → Operations Control (within AVEVA): mostly licensing repackaging, but cloud integration via Connect is real new architecture.
– FT View SE → FT Optix (within Rockwell): currently a forward-looking conversation more than a today migration for large existing applications.

Practical recommendations

For a greenfield discrete manufacturing site with mixed PLC vendors, a lean engineering team, and a unified-namespace ambition: Ignition 8.3 with Perspective and MQTT Sparkplug B, Linux gateways, Postgres for tag history, Ignition Edge nodes at line level. Add a Canary or PI historian later if regulatory needs require it.

For a brownfield Rockwell-heavy plant (say, 50+ ControlLogix PLCs, an existing FT View SE 12 application, an in-house team that lives in Studio 5000): stay on FactoryTalk, upgrade to View SE 14, plan the Historian SE → Datamosaix conversation as a separate phase, and pilot Optix on a single line to learn it before betting big.

For a process plant — refinery, mining concentrator, large food/beverage, regulated pharma — with strong asset-template opportunity, existing AVEVA PI, and validated workflows: AVEVA System Platform 2023 R2 + Historian + InTouch OMI, with AVEVA Web HMI for dashboards and mobile, AVEVA Connect for cloud publishing.

For a multi-site enterprise wanting one corporate visualisation tier across heterogeneous plants: consider an Ignition Enterprise Architecture as the corporate tier, regardless of what runs at site level, talking to local SCADAs via OPC UA and MQTT.

For an OEM machine builder shipping skids worldwide: weigh Ignition Edge versus AVEVA Edge by support footprint in your customers’ regions and by the cost of supplying a Windows-licensed device versus a Linux one.

FAQ

1. Is Wonderware still called Wonderware in 2026?
The product line is AVEVA System Platform (with AVEVA Historian, InTouch OMI, etc.). The name “Wonderware” still gets used colloquially in plants, by integrators, and in older documentation; you’ll see both. Inside AVEVA’s own materials it is firmly System Platform / InTouch / Historian branding.

2. Is FactoryTalk Optix going to replace FactoryTalk View SE?
Eventually, probably yes — that’s the direction of travel. In 2026, FT View SE 14 is still the production-grade choice for large multi-server HMI applications. Optix is the right call for new, smaller applications and for teams who want a web-native, model-driven Rockwell HMI experience. Most large sites will run SE for years to come and migrate when it makes sense, not when the marketing slide says so.

3. Can Ignition run on Linux in production?
Yes — and increasingly it does. Native Linux gateway support is mature; ARM64 is supported; container deployments on Docker are common. Many integrators now default to Rocky Linux or Ubuntu LTS for new gateways unless the customer’s IT policy mandates Windows.

4. How does Ignition handle Allen-Bradley PLCs?
Through native EtherNet/IP / CIP drivers and OPC UA. You can browse and read Logix tags without a separate data server. What you don’t get is the same alarm-instruction passthrough and the same end-to-end Rockwell tooling experience you get with FactoryTalk Linx — if those matter, FactoryTalk wins; if you mostly need values and history, Ignition is fine.

5. Is FactoryTalk Historian really just PI?
At its core, yes — FactoryTalk Historian SE is built on the OSIsoft PI server. The implication is that integration with PI ecosystem tools is excellent and that the underlying time-series engine is a known quantity. The Rockwell-branded layers add tooling, integration with FT View SE, and the Datamosaix cloud story.

6. Which platform has the best mobile / web HMI experience?
Ignition Perspective, comfortably. AVEVA Web HMI has caught up significantly and is production-credible. FactoryTalk’s browser HMI story is the weakest of the three on View SE; Optix and Datamosaix are how Rockwell intends to close that gap.

7. Which platform has the best support for ISA-88 batch?
AVEVA, by a meaningful margin — AVEVA Batch Management is mature, validated, and widely deployed in regulated pharma. FactoryTalk Batch is credible. Ignition can do batch through bespoke development or third-party modules, but it is not where the platform is strongest out of the box.

8. Is there a unified-namespace pattern that works across all three?
Yes — and it’s what a lot of 2026 architectures actually look like. Edge gateways (often Ignition Edge) publish Sparkplug B to an MQTT broker (HiveMQ, EMQX, or vendor brokers). Any of the three central SCADA platforms can subscribe to the broker for the data they need. This decouples the edge data tier from the supervisory HMI choice — and is the pattern that lets a plant pick the best supervisory tool for the job without re-doing the edge layer.

Further reading

• Inductive Automation — Ignition 8.3 release notes and documentation portal.
• AVEVA — System Platform 2023 R2 product documentation and the AVEVA Connect / Operations Control overview material.
• Rockwell Automation — FactoryTalk View SE 14 release notes, FactoryTalk Optix product page, and Datamosaix documentation.
• ARC Advisory Group — annual SCADA market share and platform comparison reports (paywalled; summaries publicly available).
• Control Engineering and Automation World — comparative reviews of SCADA platforms 2024–2026.
• Reddit r/PLC and the PLCtalk.net forums — integrator-perspective threads on licensing surprises, migration stories, and field gotchas (filter for experience reports, frame anecdotally).
• Inductive Automation Community Forum — release-by-release upgrade discussions, particularly for 8.1 LTS → 8.3.
• OPC Foundation and Sparkplug Working Group specifications — for the standards underpinning cross-vendor edge architectures.
• Our companion piece: PLC vs SCADA — the layer below this comparison.
• Our companion piece: AVEVA PI vs Cognite Data Fusion vs Tulip — the layer above.

Whichever platform you land on, the meta-recommendation is the same: decide based on a five-year operating picture, not a quote sheet. The license is the smallest part of what you will spend. Engineering, integration, training, support contracts, and the cost of switching when you outgrow a choice are the parts that dominate. Ignition vs Wonderware vs FactoryTalk is, in the end, a question about which trade-offs you would rather live with for the next decade — and there are three defensible answers depending on what your plant actually looks like.