PanelView and FactoryTalk View: Rockwell HMI and Visualization

FactoryTalk View and the PanelView terminals that run it are the only part of a Rockwell control system most of the plant ever touches. The HMI is also the layer where a poor decision is most visible daily and hardest to reverse, because replacing it means retraining every operator on every shift. This page separates the product lineages that are routinely confused, explains the Machine Edition and Site Edition choice, describes how HMIs actually fail, and sets out which migrations are conversions and which are rebuilds.

The product split

Rockwell’s visualization portfolio contains several lineages that are frequently confused, and the confusion is expensive because the software is not interchangeable.

Terminal or runtime	Designed in	Notes
PanelView Plus 7	FactoryTalk View Machine Edition	The mainstream terminal. Standard and Performance variants
PanelView 5000 (5310, 5510)	Studio 5000 View Designer	A different product line with a different design tool. Tightly coupled to Logix, tag browsing rather than mapping
Windows servers and clients	FactoryTalk View Site Edition	Supervisory, multi-user, client-server
Panels, industrial PCs, virtual machines	FactoryTalk Optix	Newer platform with web-based, collaborative design
PanelView Standard / PanelView Plus 6	Legacy	Discontinued or approaching it. Check the catalogue number

Studio 5000 View Designer is not FactoryTalk View. They share a vendor and nothing else. An application built in one cannot be opened in the other, and a plant standardising on PanelView 5000 has standardised on a separate toolchain from every PanelView Plus terminal it already owns. Rockwell’s View Designer page offers a converter for ME displays, and describes it as a starting point, not a complete conversion.

FactoryTalk View Machine Edition or Site Edition

The choice that gets made wrong most often.

	FactoryTalk View ME	FactoryTalk View SE
Runs on	A PanelView Plus terminal, or a PC as a standalone runtime	Windows servers and clients
Scope	One machine or one line, one screen at a time	Plant-wide, multiple clients, distributed
Architecture	Standalone. No server	Local station, network station or network distributed; HMI servers can be made redundant
Users and security	Basic	Full FactoryTalk Directory security, per-area access
History and alarming	Local, limited	Server-side alarming and event history
Real cost	Terminal plus licence	Servers, Windows licences, FactoryTalk licences, and the IT support to keep them patched

The rule we apply: if the answer is one machine and one operator position, use ME. If you need more than one simultaneous view of the same process, alarm history that survives a terminal replacement, or user-level access control across areas, you need SE and should budget for the server infrastructure honestly at the start rather than discovering it at commissioning.

Where plants go wrong is choosing SE for a single line because it sounds more capable, then carrying a Windows server, its patching burden and its licence renewals for one screen. The opposite mistake, stretching ME across a plant with six terminals that each need the same alarm history, is less common but harder to unwind. The full decision, with the cost table, is on FactoryTalk View SE vs ME.

How to select the HMI for a new machine or line

Written as the decision we would make, in order:

1. Stay in the site’s lineage. If the plant runs PanelView Plus and FactoryTalk View ME, the next machine does too, unless there is a site decision to move. The second toolchain costs more than any single terminal’s features save
2. One operator position: ME on a PanelView Plus 7. If the machine needs a larger display, ME on an industrial PC keeps the standalone model without adding a server
3. Several simultaneous viewers, alarm history that must outlive a terminal, or per-area security: SE, with the server owner named before the order is placed
4. PanelView 5000 only by decision. It suits a Logix-only site that chooses View Designer as its standard. It is the wrong answer when it arrives because one OEM prefers it
5. A new supervisory layer with no SE estate behind it: evaluate SE, Optix and third-party SCADA on the same criteria. This is the layer where tying yourself to the controller vendor buys the least
6. Then the hardware: environment rating, screen size, touch type and mounting. When a legacy terminal is replaced, Rockwell lists adapter kits that fit a PanelView Plus 7 into the old PanelView Standard cutout, which saves cutting the enclosure door

How FactoryTalk View HMIs actually fail

It works on the desk and fails on the panel. The most common support call in this whole category. The application tests clean in FactoryTalk View Studio, gets downloaded, and then loses tags and throws communication errors.

The cause is almost always the communication path, not the application. FactoryTalk Linx, previously RSLinx Enterprise, resolves a named shortcut to a controller path. Anything that changes that path invalidates the shortcut: a controller firmware flash, a chassis slot change, a new IP address, a restored backup from a different machine. The application is fine. The path underneath it is not. Start at the shortcut, not at the code.

Tag browse works, runtime does not. The ME user’s guide describes two tabs in Communication Setup: Design (Local), which the editor uses to browse tags, and Runtime (Target), which the terminal uses to reach the controller. They are configured separately and can disagree, which produces an application that looks correct in every offline test.

The only copy is a runtime file. A PanelView Plus runs a compiled .mer file. The ME guide lets the author allow conversion back to an editable application, protect it with a password, or never allow it. A plant holding only a .mer built with conversion never allowed, and no source, owns screens it can run but cannot change.

Hardware ages first. Displays dim, touch screens drift, and the PCs behind SE clients reach the end of their operating system support long before the application stops being useful. Plan terminal and PC replacement as a lifecycle item, not a breakdown.

Graphics imported from elsewhere. Screens built by importing artwork from a drawing package render slowly on terminal hardware and scale badly. Native graphics objects, drawn in the tool, consistently outperform imported assets on the same terminal.

Screens designed for the designer. Colour used decoratively rather than for state, buttons sized for a mouse rather than a gloved hand, and label hierarchies that read well on a twenty-seven inch monitor and not at all on a ten inch panel at arm’s length. ISA-101 is the reference standard here; on a standalone machine it is worth applying selectively rather than wholesale.

Migration

The PanelView Plus 6 to 7 path is generally straightforward, an application conversion plus hardware. The paths that are not straightforward:

• PanelView Standard to PanelView Plus 7 is an import followed by rework. Rockwell’s migration guide imports the PanelBuilder32 application into FactoryTalk View ME, then works through a conversion log, object mapping and unsupported features, and may require ladder changes in the controller
• PanelView Plus to PanelView 5000 is a rebuild in practice. ME applications do not open in View Designer; the display converter gives a starting point only
• ME to SE is a rebuild plus an infrastructure project

Budget migrations on the software lineage, not on the hardware generation. Hardware that looks like a like-for-like swap frequently is not. The detail, with the planning sequence, is on PanelView migration.

A worked example (illustrative). A plant has 30 terminals: 8 PanelView Standard, 18 PanelView Plus 6 and 4 PanelView Plus 7. The 18 Plus 6 units convert within the ME lineage and go first, two per weekend, because each is days of work. The 8 Standards are imported and reworked, and each is scheduled into the shutdown of the controller it talks to, since that migration repoints its tags anyway. Nobody adds a PanelView 5000 without a decision to adopt View Designer across the site, so the plant keeps one HMI toolchain.

Evaluation checklist

• Every terminal and SE client listed with catalogue number, firmware and lifecycle status
• The editable application and its backup archived for each, not only the runtime file
• The FactoryTalk View version that opens each application, installed and licensed
• Design and runtime communication paths documented for each terminal
• ME or SE chosen against the three operational questions, with a named server owner for SE
• One HMI lineage per site unless a decision says otherwise
• A screen standard: colour for state, button sizes, alarm presentation

What we do here

• Decide ME or SE against the actual operational requirement, and state the infrastructure cost up front
• Review screen design against ISA-101 where it earns its keep on the equipment in question
• Diagnose communication and path faults rather than rebuilding applications that were never broken
• Plan terminal migrations by software lineage, with the rebuild cost identified honestly
• Set HMI standards so screens across a plant behave consistently for operators moving between lines

Deeper

• PanelView Migration Paths: which upgrades are conversions and which are rebuilds
• FactoryTalk View SE vs ME: the decision, the real infrastructure cost, and how to avoid buying a server for one screen

Back to the Rockwell Automation hub, or across to Networks and Communications, where most HMI communication faults actually originate. If the HMI decision is part of a wider upgrade, our control system modernization work covers the sequence.