FactoryTalk View SE vs ME vs FactoryTalk Optix: Differences and Migration Checks

FactoryTalk View ME and FactoryTalk View SE differ in scale and architecture. ME (Machine Edition) is a single-machine HMI that runs on PanelView Plus terminals or industrial computers. SE (Site Edition) is HMI/SCADA software that scales from one workstation to a distributed system with HMI servers, data servers and client workstations. FactoryTalk Optix is Rockwell Automation's newer visualization platform. Optix has web-based or desktop design, a runtime on OptixPanel or Windows or Linux computers, and runtime licensing based on "feature tokens". This article compares the three using Rockwell's public documentation and lists what to check before a migration.

Quick comparison

Summary based on the product pages, help and publications listed under Sources. It is not a ranking.

FactoryTalk View ME: an HMI for one machine

Rockwell positions ME as the HMI for machine-level operator interface devices. Applications are built in FactoryTalk View Studio ME. The runtime runs on PanelView Plus 7, PanelView Plus 6, MobileView or an industrial computer. On PanelView Plus terminals the ME runtime comes installed and activated. On industrial computers a license must be activated (VIEW-SG002D, p. 9).

The two PanelView Plus 7 families have different limits. The Standard family is limited to 1 controller, 100 screens and 500 alarms. The Performance family has no limit on these items (VIEW-SG002D, pp. 4 and 8). Standard runs Windows CE. Performance Series B runs Windows 10 IoT LTSC (pp. 7–8).

ME alarms are set up in the Alarm Setup editor. Each trigger monitors a tag or an expression, and an alarm is generated when the value matches a message's trigger value (ME 16 help). The VIEW-SG002D feature table (p. 3) shows that PanelView Plus 7 does not support Logix alarms. ME scripting is "events and commands", with no VBA (p. 4).

FactoryTalk View SE: HMI/SCADA for an area or a plant

SE has three application types (SE 16 help, "FactoryTalk View SE applications"):

• Local station: all components run on one computer, with only one HMI server and no areas.
• Network station: the application sits in the FactoryTalk Network Directory and has exactly one HMI server, either at the application root or in an area.
• Network distributed: components run on several computers that share one FactoryTalk Directory. The application has at least one HMI server (one per area), data servers such as FactoryTalk Linx or OPC DA/UA, and SE Clients for display.

HMI server redundancy is available only in network distributed applications. When the primary server cannot serve clients, they move to the secondary ("About HMI server redundancy").

SE alarms go through FactoryTalk Alarms and Events. Alarm sources can be Logix controller alarms (instruction-based or tag-based), server tag-based alarms (for Rockwell controllers, third-party controllers via OPC, and HMI tags), or alarms from OPC UA servers. The SE 16 help has a separate page on migrating legacy HMI alarms to FactoryTalk Alarms and Events.

Browser access uses FactoryTalk ViewPoint, an HTML5 interface with no client software to install. The SE product page states that, with the simplified license model of v14, ViewPoint for mobile HMI design is included with Station and Server licenses (supported on v11 and later). When displays are published to ViewPoint, unsupported objects produce errors or warnings in the publishing report (ViewPoint 16 help). VBA display code runs only in the SE Client (SE 16 help, "VBA display code").

FactoryTalk Optix: a newer platform with token-based licensing

OPTIX-AT001D (01/2026) describes Optix in three parts. Optix Studio is the design tool: Studio Standard is free and installed locally, and Studio Pro is a cloud-based editor sold by subscription. The Runtime runs the application. FactoryTalk Remote Access provides remote connectivity. The runtime runs on Windows 10/11, Windows Server or Ubuntu 22 (x64). OptixPanel and Embedded Edge Compute run Yocto (ARM64), and users cannot access the operating system (Optix release notes, "System requirements").

Runtime licensing uses feature tokens. Each feature has a token value, and the total must fit the purchased package. The packages are XS 5, S 8, M 11, L 15 and XL 21 tokens. For example, alarming costs 1 token, and HTML5 web clients cost 2 tokens for up to 3 clients or 7 tokens for up to 20 clients (OPTIX-AT001D, pp. 12 and 62). Without a valid entitlement, an application runs in demo mode for about 2 hours (p. 11). OptixPanel Compact includes package S (8 tokens), OptixPanel Standard includes package M (11 tokens), and both can be upgraded. Running Optix on an industrial PC requires a separate runtime purchase (VIEW-SG002D, pp. 5–6).

Moving from FactoryTalk View to Optix: what Rockwell says

The Rockwell documents we opened for this article do not describe a tool that converts FactoryTalk View ME or SE applications to FactoryTalk Optix. They are VIEW-SG002D, OPTIX-AT001D, the Optix product page, the "System features" page of the Optix 1.8 release notes, and the "Import and conversion of an application" page of the ME 16 help. They also do not state that no such tool exists.

The only conversion tool VIEW-SG002D lists for ME is the FactoryTalk View ME to Studio 5000 View Designer conversion tool, the software for PanelView 5000 (p. 11). So until Rockwell or a distributor confirms a tool for the plant's exact version, TDL plans an Optix project as an HMI rebuild. The existing tag list, alarm list and screenshots of the old screens serve as the specification.

When to stay on ME/SE and when to consider Optix

Stay on or upgrade within ME/SE when:

• The application runs well and the plant only needs new hardware or a newer version. Moving between FactoryTalk View versions is much lighter than a rebuild.
• An SE system already has several servers, redundancy, FactoryTalk Alarms and Events and a lot of VBA code.
• The maintenance team knows View Studio, and the system is part of a PlantPAx architecture.

Consider Optix when:

• The machine or line is new, or the whole HMI is being redesigned anyway.
• You need native web clients, OPC UA or MQTT on the HMI itself, or a Linux runtime.
• You want several engineers to design together and track versions in the cloud with Optix Studio Pro.

What to check before migrating

1. Version. Record the FactoryTalk View Studio and runtime version on every computer. View Studio ME cannot import an application created with a later version. For an earlier version, it creates a copy for the current version and leaves the original unchanged (ME 16 help).
2. Graphics. Count displays, faceplates, global objects and ActiveX controls. If web access is needed, test-publish to ViewPoint and read the publishing report.
3. VBA and scripts. SE VBA runs only in the SE Client. Optix uses C#, so all VBA code has to be rewritten and retested.
4. Alarms. Find out whether the alarms are ME triggers, legacy SE HMI alarms, or FactoryTalk Alarms and Events / Logix alarms. This affects the migration effort more than anything else. If the alarms are being redone, see our article on ISA-101 and ISA-18.2.
5. Licensing and sizing. For Optix, add up the tokens for the features you need (alarms, web clients, logging…) before choosing a package or an OptixPanel.
6. Hardware and panel cutouts. OptixPanel sizes differ from PanelView Plus 7, so check the cutout in the enclosure door.
7. Communications. List drivers and third-party controllers, and the firewall ports between computers (see FactoryTalk firewall ports).

Other migration paths (RSView32, PanelBuilder, WinCC…) are covered in Legacy HMI/SCADA: what to replace it with. TDL handles PanelView Plus migration on the PanelView Plus HMI migration page and SCADA systems on the SCADA and historian page.

Need an engineer to assess your running application: request support.