AVEVA System Platform with InTouch HMI, Ignition and FactoryTalk View SE are all server-based SCADA platforms, but they are built and licensed differently. AVEVA keeps the configuration of a Galaxy in a SQL Server database and runs objects on Application Object Servers. Ignition puts everything on one Gateway and licenses that server, not the clients. FactoryTalk View SE serves displays from HMI servers that clients find through FactoryTalk Directory. Below, the three side by side from each vendor's current documentation. It is not a ranking; "not stated in the docs read" means we found nothing, not that the product cannot do it.
1. What was read
- AVEVA: System Platform 2026, InTouch HMI 2026 and Communication Drivers Pack 2026. The release notes describe System Platform 2026 as a major release of independently upgradable products, among them Application Server, Operations Management Interface (OMI), InTouch HMI and Historian Server.
- Ignition: the 8.3 user manual (8.1 is a separate doc set).
- FactoryTalk View SE: the 16.00 help and Rockwell's product page, whose version history lists Version 16 first; redundant data servers from the FactoryTalk Services Platform 6.60 help.
2. Side by side
| Topic | AVEVA System Platform + InTouch HMI 2026 | Ignition 8.3 | FactoryTalk View SE 16 |
|---|---|---|---|
| Architecture | Galaxy Repository: one per Galaxy, configuration in SQL Server; System Platform IDE and WindowMaker on engineering stations; objects run on Application Object Servers. Standalone InTouch: Application Manager and WindowMaker | One Gateway holds device and database connections, tags and alarming; projects built in the Designer and saved back to the Gateway | FactoryTalk View Studio for design; HMI servers store the HMI project, tag database, alarm detection and data logging; FactoryTalk Directory lets the parts find each other |
| Operator clients | OMI thick client; RDS session or HTML5 web client; InTouch Web Client for selected Industrial Graphics; InTouch Access Anywhere is not part of System Platform 2026 | Vision Clients from the Vision Client Launcher; Perspective Sessions in a browser, Perspective Workstation or the Android and iOS app | SE Client, set up with a .cli file; FactoryTalk ViewPoint in an HTML5 browser, no client software |
| Licensing mechanism | AVEVA Enterprise License Server and License Manager; InTouch licences set how many local and remote reference tags an application can use; on an RDS server, one Workstation licence per WindowViewer session or one Unlimited licence; Web Client licensed separately; Flex subscriptions: Edge, Supervisory, Enterprise | Per server, not per client; modules one by one or as a Solution Suite; unlimited clients, tags and projects; resettable two-hour trial | Product page names SE Station, Server and Client and a simplified bundled licence model from version 14; ViewPoint included with Station and Server; per-tag or per-display counts not stated in the docs read |
| PLC connectivity | Communication Drivers on Device Integration Servers: ABCIP, ABTCP, SIDIRECT, MELSEC, OMRONFINS, MBTCP, BACLITE and others; InTouch Access Names; Gateway Communication Driver for OPC and OPC UA | OPC UA module drivers: Allen-Bradley, Siemens, Modbus, BACnet, DNP3, IEC 61850, Mitsubishi, Omron; OPC UA connections to third-party servers | Data servers: FactoryTalk Linx, and OPC DA 2.05a or OPC UA 1.02/1.03 servers |
| Historian | Historian Server: AVEVA Historian on SQL Server, fed by the Application Object Servers | Core Historian writing to disk; legacy internal and external SQL historians through Store and Forward | DataLogPro (InfluxDB) or Data Log Models (file sets or ODBC); trends read FactoryTalk Historian SE, Historian ME, Asset Framework or PI Server |
| Redundancy | Redundant AppEngines, active and standby, on two platforms with dual dedicated NICs; RedundantDIObject for I/O; InTouch Access Name failover | Master and backup Gateway; configuration replicated; clients move to the active node; backup licence with the same modules, or backup-only | HMI server redundancy in network distributed applications only; FactoryTalk Linx, OPC DA, OPC UA and Tag Alarm and Event servers as redundant pairs |
| Alarms | Application Server platform as alarm provider; InTouch Alarm DB Logger to SQL Server (Mixed Mode authentication) | Alarms on tags and UDTs; Alarm Journal to an external SQL database; email, SMS, voice; shelving | FactoryTalk Alarms and Events: Logix instruction-based and tag-based, server tag-based and OPC UA alarms |
| Scripting | QuickScript .NET; InTouch application, window, key, condition and data change scripts | Python, in components, tags, reports, alarm notification, Clients, Sessions and the Gateway | VBA display code in the Microsoft VBA IDE; PowerShell scripts on the HMI server through ScriptExecute |
| OS and database | Installers for Windows, Linux and macOS; Java-based; SQL databases through JDBC | SE Server runs as Windows services; OS versions not stated in the docs read |
Two rows need a note. For Logix tag-based alarms, the SE help names only Compact GuardLogix 5380, CompactLogix 5380 and 5480, ControlLogix 5580 and GuardLogix 5580 controllers. For InTouch, AVEVA's tag-count page says InTouch now supports an unlimited tag count, tested up to 300,000 tag handles. The licence still sets how many tags get a handle.
Each row has its own article: drivers in PLC drivers on Ignition, Optix, AVEVA, N3uron and Kepware, the Ignition Logix driver and AVEVA's ABCIP driver; history in What is a process historian and AVEVA Historian vs PI System; failover in SCADA server redundancy; alarm design in
3. Which fits which plant situation
These are conditions, each tied to a row above. None of them makes one platform better in general.
The plant already runs FactoryTalk View SE with Rockwell controllers
FactoryTalk Linx is the SE data server for Rockwell controllers. Logix alarms arrive through FactoryTalk Alarms and Events, and tag-based Logix alarms work only with the controller families listed above. Each of these needs checking before a change of platform.
The site has PLCs of several brands
Ignition and the AVEVA Communication Drivers Pack both list their own drivers for Siemens, Mitsubishi, Omron, Modbus and BACnet. FactoryTalk View SE reads other brands through an OPC DA or OPC UA data server.
Many browser or remote screens are needed
Ignition licenses the server, with unlimited clients and Perspective Sessions in a browser. FactoryTalk ViewPoint is an HTML5 add-on that is included with SE Station and Server. AVEVA has the separately licensed InTouch Web Client and RDS sessions, licensed per WindowViewer session or with an Unlimited licence. The InTouch HMI 2026 release notes state that InTouch Access Anywhere is no longer part of the System Platform 2026 installation media.
A Wonderware InTouch application or System Platform Galaxy is running
A standalone InTouch application can be imported into the System Platform IDE as a managed application, and AVEVA migrates Galaxies from Application Server 4.5 onwards. For a move to another platform, the documents we read for Ignition and FactoryTalk View SE describe no import of InTouch windows. See InTouch HMI or System Platform.
The project needs Linux or macOS servers
Of the three, only Ignition documents installers for Linux and macOS. System Platform 2026 is listed on
Two other platforms are covered separately: AVEVA Plant SCADA (formerly Citect SCADA), and FactoryTalk Optix in FactoryTalk View SE vs ME vs Optix.
4. Migrating between them
Inside each family, the vendors document an upgrade path:
- System Platform. A direct upgrade to System Platform 2026 is supported from System Platform 2020 R2 SP1 or later; older versions need an intermediate upgrade first. System Platform 2020 R2 CR1, 2020 R2 CR2 and System Platform Enterprise 2023 cannot be upgraded to 2026. Upgrade the Galaxy Repository first, then the backup platform of a redundant pair, then the primary; both partners must be at the same version before redundancy works again. A plant that used licensing from before System Platform 2017 must first upgrade to 2017.
- InTouch HMI. Applications from InTouch 7.11 P07 or later can be migrated to InTouch HMI 2026. Since version 10.2 InTouch cannot be upgraded as a single product, so every product on the node is upgraded together. Steps and checks: Upgrading Wonderware InTouch.
- Ignition. For 8.1 to 8.3, the upgrade guide asks for a license that is 8.3 compatible, a Gateway backup, the latest 8.1 first, a test on a development system and third-party modules confirmed for 8.3. 8.3 uses a different file system, and the upgrade migrates the stored resources to it. Details: Upgrading Ignition 8.1 to 8.3.
- FactoryTalk View SE. The Application Manager backs up and restores applications. The SE 16 help notes that from version 14 the ODBC data log configuration is bound to one FactoryTalk Directory. After a restore, data server shortcuts, OPC driver settings and historical databases are restored by hand. The FactoryTalk View Alarm Migration tool converts legacy HMI tag alarms to FactoryTalk Alarms and Events tag-based alarms.
Between the families, none of the documents we read describes a tool that converts one platform's project into another's. Old HMI products and their paths are listed in Legacy HMI/SCADA migration.
What we check first
This is TDL's practice, not a requirement of AVEVA, Inductive Automation or Rockwell Automation.
- We list every PLC and its firmware, and look it up in the driver lists of the platform being considered.
- We count operator stations, browser users and remote sessions, because each platform licenses them differently.
- We record where history and alarms are stored today: AVEVA Historian, a SQL database, FactoryTalk Historian or data log files.
- We check whether the plant needs a redundant server and which part of the system it must cover.
- We check the Windows and SQL Server versions on site against the vendor's lists.
- For an existing system, we take a full backup first: the Galaxy, the InTouch application, the Gateway backup or the SE application archive.
How TDL approaches it
TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem, an Ignition Certified Integrator and a System Integrator in the Rockwell Automation PartnerNetwork. Our project pages show FactoryTalk View SE at BSR, where RSView32 was moved to FactoryTalk View SE on four steam turbine generator systems, and at Vinh Hoan FeedOne with FactoryTalk Historian. They show AVEVA System Platform at Samsung SEHC, with HMI migration and extension of the SCADA, and at Nestlé Tri An. More on these services: SCADA and historian, AVEVA system integrator, Ignition integrator and Rockwell Automation system integrator.
Frequently asked questions
How is each platform licensed?
Ignition is licensed per Gateway by module, with unlimited clients, tags and projects. InTouch licences are based on the number of local and remote reference tags, with a licence per WindowViewer session on an RDS server unless an Unlimited licence is used. Rockwell's product page names SE Station, Server and Client and describes a simplified, bundled license model from version 14; it gives no per-tag or per-display count.
Does FactoryTalk View SE work with non-Rockwell PLCs?
Yes, through data servers. The SE help lists FactoryTalk Linx and OPC servers to the OPC DA 2.05a or UA 1.02/1.03 specifications, and HMI tags take an OPC item address.
Which platform runs operator screens in a web browser?
All three document a browser option. Ignition has Perspective Sessions, FactoryTalk View SE has FactoryTalk ViewPoint, and AVEVA has the InTouch Web Client and an HTML5 web client for OMI. InTouch Access Anywhere is not included from System Platform 2026.
Can an InTouch application be converted to Ignition or FactoryTalk View SE?
The documents we read describe no such conversion tool. Inside AVEVA, a standalone InTouch application can be imported into the System Platform IDE.
Which databases does each platform need?
System Platform needs SQL Server for the Galaxy Repository, Historian Server and System Monitor Manager. Ignition connects to SQL databases through JDBC, and its Core Historian writes to disk. FactoryTalk View SE logs to InfluxDB through DataLogPro or to file sets or an ODBC database through Data Log Models.
Sources
- AVEVA, System Platform 2026: AVEVA System Platform 2026 release notes, System Platform component descriptions, Galaxy Repository, Historian Server, Redundancy, Log historical alarms in InTouch HMI and Script editing styles and syntax
- AVEVA, System Platform 2026: Supported operating systems, SQL Server requirements for System Platform components, License installation and activation, License upgrades, Important upgrade information and Upgrade redundant pairs
- AVEVA, InTouch HMI 2026: Compare different types of InTouch HMI applications, InTouch HMI Licensing, License in InTouch HMI, Understand license tag counts, InTouch licensing in RDS and non-RDS environments and InTouch Web Client
- AVEVA, InTouch HMI 2026: Connectivity with Gateway Communication Driver and OPC, Set up access names, Use failover functionality with Access Names, Use scripts, SQL server requirements and Migrating applications to AVEVA InTouch HMI 2026, AVEVA InTouch HMI 2026 release notes
- AVEVA, Communication Drivers Pack 2026: Controller-specific Communication Drivers and Standard Communication Drivers, with the driver list in their table of contents
- Inductive Automation, Ignition 8.3 user manual: Introducing Ignition, Licensing and Activation, Projects, Perspective and Vision, Perspective Sessions and Vision Client Launcher
- Inductive Automation, Ignition 8.3 user manual: Driver Modules, OPC UA Connections, Historian, Ignition Redundancy, Redundant Licensing, Alarming, Scripting, Installing and Upgrading Ignition and 8.1 to 8.3 Upgrade Guide
- Rockwell Automation, FactoryTalk View Site Edition product page and FactoryTalk ViewPoint product page
- Rockwell Automation, FactoryTalk View SE 16.00 help: FactoryTalk View Site Edition Help, FactoryTalk View SE applications, About HMI server redundancy, FactoryTalk View Site Edition Client, Set up communications and Establish FactoryTalk Historian and PI Server connectivity
- Rockwell Automation, FactoryTalk View SE 16.00 help: Logging information, Alarms, Scripts, Use VBA display code, FactoryTalk View SE Application Manager, Restore an archive and FactoryTalk View Alarm Migration tool
- Rockwell Automation, Redundant servers, FactoryTalk Services Platform 6.60 help
Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.