HMI SCADA Software Comparison: Wonderware, Ignition, FactoryTalk

HMI/SCADA Market Overview and the Selection Problem

The question "does anything beat Wonderware?" no longer has a single answer because Wonderware as a brand has effectively been retired. The Wonderware product line — InTouch, System Platform, Application Server, Galaxy Repository, Historian, InBatch, and the Workflow MES components — was consolidated under AVEVA's Operations portfolio following the AVEVA–Schneider Electric industrial software consolidation that completed in 2021. Engineers evaluating a long-lived SCADA platform now compare AVEVA Wonderware derivatives against modern stacks: Inductive Automation Ignition, Rockwell FactoryTalk View SE/ME with ViewPoint, Siemens WinCC Unified, Emerson iFIX/CIMPLICITY, Schneider Citect/Vijeo, and the hardware-HMI category represented by Red Lion Crimson 3.0, AutomationDirect C-More EA, and Beijer iX.

This reference is a field-engineer view of the tradeoffs. It focuses on architecture, licensing, OS lock-in, migration risk, redundancy, scripting, and how each platform handles the day-two realities: Windows cumulative updates, virtualized servers, IPv6 networks, OPC UA servers, and PLC tag database browsing from the HMI editor.

Wonderware to AVEVA — What Actually Changed

AVEVA acquired Wonderware from Schneider Electric as part of a 2017 share-exchange deal that valued the combined industrial software business; the integrated branding as "AVEVA Wonderware" was formalized in 2020–2021. Per the AVEVA Wonderware product page, InTouch, System Platform, Historian, and MES are now positioned inside AVEVA's "Industrial Intelligence" portfolio alongside the PI System.

Engineer-relevant consequences of the transition:

• License file format unchanged. Existing InTouch and Application Server license keys continue to be honored; support contracts moved to AVEVA subscriptions.
• System Platform Galaxy Repository can now be hosted on AVEVA CONNECT-managed cloud or on-prem — see AVEVA System Platform.
• Historian integration with PI is now a first-class integration path; the legacy Wonderware Historian (HD) and PI Server have bidirectional bridging.
• ArchestrA IDE is renamed AVEVA Application Server IDE; the Galaxy Database and symbol deployment model is identical to Wonderware 2014R2 onward.

If a panel integrator spec'd "Wonderware," the practical engineering decision is whether the project deploys on the legacy InTouch standalone runtime or the System Platform / Application Server model. That choice drives tag count, redundancy, and remote client architecture more than the rebranding does.

Inductive Automation Ignition — Modern Java SCADA

Ignition by Inductive Automation is a server-based SCADA platform built on Java with a web-launched HMI client (Vision module) and a Python-scripted transaction layer (SQL Bridge, Tag Historian, etc.). The platform gained serious mindshare in mid-2010s because it inverts three legacy SCADA assumptions:

1. Unlimited tags, unlimited clients. Licensing is per Ignition server, not per tag or per client. A single server can address tens of thousands of PLC tags and serve many concurrent Vision clients and Perspective mobile clients.
2. Platform agnostic. The gateway runs on Windows, Linux, and macOS. The HMI is rendered in the browser (Vision) or on iOS/Android (Perspective). The runtime is not tied to a Microsoft release cycle.
3. Online editor to runtime. Windows updates that break a Java install break the HMI, but a recovery is generally faster than rebuilding a corrupted FTView ME application cache.

From a hands-on integrator perspective, three engineering attributes matter most:

• Tag database is virtual. OPC UA server tag paths are bound to memory tags; the OPC browse, expression tags, and UDTs let one engineer build 1,000 tags from 8 CSV files in roughly the time it takes to import the equivalent into FTView Studio.
• Templates with parameters. A single screen template accepts a parameter to instantiate at 18 well sites and 5 booster pump stations, replacing 23 nearly identical screen libraries.
• Scripting in Python (Jython 2.7 runtime). System scripts, tag event scripts, and component scripts are editable online. This is the workflow FTView users typically request when the trend export or alarm rollup features fall short.

Rockwell FactoryTalk View SE/ME and the PV5500 Generation

FactoryTalk View split into two product lines that are commonly confused by name but architecturally distinct:

• FactoryTalk View SE (Site Edition) — server-based, multi-client, distributed HMI/SCADA. The HMI server is the FactoryTalk View SE Server, the design environment is FactoryTalk View Studio, and the client is FTView SE Client or ViewPoint for browser-based read-only clients.
• FactoryTalk View ME (Machine Edition) — PanelView Plus runtime, single-panel, PanelBuilder-style merged development/runtime. ME projects are developed in the same Studio shell as SE, but compiled and stored on the panel.

Version 6.x of FactoryTalk View is widely cited as the version that introduced the SQL-backed tag database that was historically hosted on Watcom (later Microsoft) SQL Server. The legacy 32-bit Watcom database compatibility issue persists: ME projects created on 32-bit FactoryTalk View Studio 7.x must be edited in a 32-bit Windows XP/7 VM if the project was last saved with a 32-bit Point Server. Version 8.x replaced the Watcom backend and removed the 32-bit dependency for new projects, but legacy ME files still bind to FTView 7.

PanelView 5500 (2715P-) is the next-generation Allen-Bradley HMI panel that runs a Linux-based runtime and uses Studio 5000 View Designer for development. It is a Logix Designer-aligned product: project bindings pull directly from the Logix Designer controller tag database, eliminating the standalone tag database import that has been the source of ME project corruption for two decades. Per Rockwell, PV5500 firmware is upgradeable in the field and the development environment is View Designer, which is a separate install from FactoryTalk View Studio.

Schneider Citect and AVEVA System Platform

Schneider Electric's Citect SCADA remains in active deployment in water/wastewater, mining, and metals. The Citect platform uses the Cicode scripting language and the CitectSCADA project model with the famous multi-process architecture: alarms, trends, reports, and I/O are independent Win32 processes connected by a shared in-memory database. CitectSCADA 2016 (7.x generation) and 2018R2 are the current generally available releases; Schneider is steering new projects toward AVEVA System Platform as the strategic SCADA, while maintaining Citect for installed-base projects.

Citect's engineering relevance today:

• Process Analyst trend export is widely cited as the most usable export-to-CSV pipeline in any major SCADA. CSV can be opened directly in Excel; FTView SE Trend, by contrast, requires a separate "TrendExport" command-line utility and a fixed column format.
• Alarm screen modernization arrived in 7.5; pre-7.5 alarm acknowledgements were a known integrator pain point.
• Variable tags vs. cluster tags support Citect's variable tag model where the I/O server writes to a shared memory page; this is fast but does not scale linearly beyond ~50,000 tags without process tuning.

Vijeo Designer is the Magelis panel HMI editor. It is the Schneider equivalent of FactoryTalk View ME, and as of Magelis GTU/STM panels, the project runtime is HTML5-based. Vijeo licensing is per developer seat, which is the cost driver most often raised by integrators moving from Magelis to Red Lion or C-More.

Red Lion Crimson 3.0 — Hardware HMI with PC-Speed Configuration

Crimson 3.0 is Red Lion Controls' configuration environment for the Graphite HMI and the CR3000 HMIs. The engineering case is integration density: a single Crimson project can hold up to 20 simultaneous protocol drivers, write to onboard SD logs, publish to MQTT, and run IEC 61131-3 logic on the Crimson controller variant — all in one project file that deploys to the panel in seconds over USB or Ethernet.

Practical integrators note three characteristics:

1. Free download, free runtime upgrade. Crimson 3.0 install and the project emulator are downloadable without license. Firmware and runtime updates are pushed to the panel from the same deploy step as the project — no separate service pack install, no reboot that forces a re-deploy.
2. Data logging is native. CSV logs, FTP push, and a built-in OPC UA server (server-side, not just client) mean an HMI panel can also act as a data concentrator for legacy Modbus RTU devices.
3. Byte swapping and protocol conversion are exposed as first-class operations: the same panel can read Modbus from a VFD, swap words and bytes, and write scaled values to an Allen-Bradley MicroLogix over EtherNet/IP without a separate protocol converter.

Crimson 3.0 is positioned against PanelView Plus for new mid-size projects and against Vijeo Designer for Magelis retrofits. It is not a SCADA — it is a hardware HMI that can be used as a data source for a SCADA.

AutomationDirect C-More and C-More EA

The AutomationDirect C-More (EA series) is the most common lower-cost hardware HMI in North American panel shops. The development environment is C-More Programming Software v6, the runtime is on the EA9/EA7 panel. The C-More ecosystem has matured since 2018 to include:

• Built-in MQTT publisher to AWS IoT, Azure, and Ignition cloud brokers.
• OPC UA server and client.
• 1,500-tag databases with tag import from CSV and direct browse for several PLC families (DirectLOGIC, CLICK, Productivity, Do-more, plus Modbus TCP, EtherNet/IP, and Siemens S7 MPI/TCP).
• 12.1" to 15" multi-touch panels comparable to Magelis and PanelView Plus 7 performance.

For new projects in non-OEM facilities that have no existing SCADA, C-More EA9 panels with built-in data logging to SD card and a free HMI/SCADA package on the operator's PC is often the lowest total-cost option short of an Ignition gateway.

Feature Comparison Matrix

Licensing Model Comparison

Architecture and 32-bit to 64-bit Migration

Legacy HMI/SCADA projects accumulate technical debt in three predictable ways:

1. 32-bit project file format lock-in. A PanelView Plus ME project last saved on a 32-bit FactoryTalk View Studio 7.x with the Watcom SQL Point Server can only be re-opened on a 32-bit Windows 7/XP environment. The version-8 / version-12 Studio cannot load it without a project migration. The standard field remedy is to maintain a 32-bit Windows XP or 7 VM with the original Studio version installed.
2. ActiveX extensions on PanelView Plus. Many ME projects shipped with ActiveX controls from third-party vendors (Symbol Factory, IndustrialSQL, etc.) that do not have 64-bit equivalents. The PV5500 generation dropped ActiveX in favor of native HTML5 vector graphics to break this dependency.
3. Walled-garden integration between acquired product lines. Schneider's Vijeo Designer does not browse the Unity Pro / M340 / M580 tag database the way FactoryTalk View Studio browses Logix Designer tags. Citect's variable tag model accepts CSV import but does not provide a live browse into a Modicon M580 controller.

Ignition by contrast was designed post-2010 with no ActiveX and no 32-bit runtime. Projects saved in Ignition 7.9 open in 8.1; OPC UA server endpoint URLs do not change with Ignition version. This is the operational pain point that motivates migration off Wonderware/AVEVA InTouch or FactoryTalk View ME on a 5-year horizon.

Operating System Lock-in and Patch Cycle Risk

Every Windows cumulative update has historically broken a SCADA runtime. Documented failure modes include:

• FactoryTalk View Studio refusing to load a project if the SQL Server Express instance used for the local Point Server is upgraded by a Microsoft patch.
• Wonderware InTouch hanging on WindowMaker startup if the .NET Framework version is rolled forward by a Windows feature update.
• CitectSCADA 7.0 alarm screen failing to render after KB448xxxx is applied (a real production incident on multiple mining sites).

For new deployments, the engineering question is: can the HMI/SCADA runtime be hosted in a container or virtualized server that is decoupled from the IT-managed patch cycle? Ignition (Linux or container), AVEVA System Platform (Windows Server Core VM), and FactoryTalk View SE (Windows Server VM with patch exclusion) all support virtualized deployment; hardware HMIs (Crimson, C-More, PanelView Plus, Magelis) are physically isolated by definition and immune to the OS patch cycle on the engineering workstation.

Open Standards vs Proprietary Runtime

The mid-2010s shift in HMI architecture has been from native Windows clients to HTML5 browser clients. The driver is twofold: IT managers want zero-install clients, and integrators want the SCADA client to render on whatever device the operator is carrying.

For new greenfield sites, an HTML5-first client strategy is the lowest-risk choice: it survives Microsoft browser deprecations (Silverlight end-of-life, Internet Explorer 11 retirement), iOS/Android OS upgrades, and Windows Server OS migrations. AVEVA, Inductive, Rockwell, Siemens, and Schneider have all moved their flagship SCADA to HTML5 clients within the last five years for this reason.

Engineering Selection Criteria

The integrator question "does anything beat Wonderware?" resolves to a four-axis selection matrix that any controls engineer can apply without bias:

1. Existing tag database and PLC fleet. If the facility is all ControlLogix/CompactLogix with Logix Designer 33+, FactoryTalk View SE is the lowest-friction path. If the facility is mixed Rockwell, Siemens, Schneider, and Modbus devices, Ignition is the lowest-friction path because of the UDT-based tag abstraction and built-in OPC UA server.
2. Tag count and growth trajectory. For sites above ~50,000 tags, AVEVA System Platform, Ignition, and Siemens WinCC Unified are the only platforms with proven deployments. Below 5,000 tags, hardware HMIs (Crimson, C-More, Magelis) are the lowest total cost.
3. IT alignment and OS constraints. IT-mandated Windows Server 2022 + Active Directory integration favors FactoryTalk View SE, Citect, or AVEVA System Platform. Linux-only data centers and containers favor Ignition. Strict air-gapped OT networks favor Crimson or C-More for hardware HMIs, AVEVA or Ignition for SCADA on a hardened VM pair.
4. Redundancy and operator-mobility requirements. Active/standby HMI server pairs are standard in AVEVA System Platform, Ignition, FactoryTalk View SE, and Citect. Mobile operator dashboards are strongest in Ignition Perspective and AVEVA InTouch Access Anywhere; weakest in classic FactoryTalk View ME.

Field Commissioning Recommendations

Across hundreds of greenfield and retrofit projects, the same commissioning pitfalls repeat. The following checklist applies regardless of which HMI/SCADA platform is selected:

• Test the OS patch cycle before commissioning sign-off. Run the SCADA host through a full month of WSUS-approved updates in a test environment with the actual project loaded. A 30-day soak catches ~80% of post-deployment runtime crashes.
• Document the project's tag database export path. Every SCADA platform has a different way to extract the runtime tag database to CSV. Confirm the export path before sign-off; the end customer will request it during the warranty period.
• Lock the project file format version. Disable automatic Studio updates on the engineering workstation. A version bump that silently converts a 32-bit ME project is the most common cause of "we cannot open the project anymore" support calls.
• Verify the OPC UA server certificate trust chain. When a SCADA is the OPC UA client to a PLC UA server (or vice versa), the certificate trust store must be configured before the first browse. Most commissioning issues on multi-vendor OPC UA projects are certificate trust issues, not tag mapping.
• Capture a clean VM snapshot or panel backup. After the customer's UAT sign-off, snapshot the SCADA host VM and store it offline. Save a copy of the panel project file with the same timestamp. This is the recovery point for any subsequent failure.

Troubleshooting Matrix

Bottom-Line Recommendation

There is no universally "best" HMI/SCADA platform. The decision is driven by installed PLC fleet, tag count, IT/OT boundary, and 5-year roadmap. For new projects in 2024 onward:

• Rockwell-only fleet above 10,000 tags → FactoryTalk View SE + PanelView 5500 + ViewPoint.
• Mixed-vendor fleet with strong IT/OT collaboration → Ignition by Inductive Automation with Vision or Perspective clients.
• Installed base on legacy InTouch or System Platform → continue with AVEVA support contracts; migrate the editor only when the application is being rewritten for other reasons.
• Standalone panel retrofit, no SCADA → Red Lion Crimson 3.0 or AutomationDirect C-More EA.
• Siemens PLC-fleet-heavy facility → Siemens WinCC Unified or TIA Portal HMI, paired with the controller's integrated OPC UA server.

What truly distinguishes a modern HMI/SCADA platform is not the editor or the trend export, but the platform's tolerance for the IT-mandated OS upgrade, the ability to survive a 32-bit-to-64-bit project migration, and the HTML5 client's survival of a browser deprecation. On all three axes, AVEVA's Wonderware, Ignition, FactoryTalk View, and Citect have all converged to a workable modern implementation — the choice is local integrator capability and existing license investment, not feature parity.

Frequently Asked Questions