What Does MER Stand For?
MER stands for Machine Edition Runtime. It is the compiled binary file format that FactoryTalk View Studio ME generates when you build a HMI project for deployment to an Allen-Bradley PanelView Plus terminal. The "Machine Edition" refers to Rockwell's HMI software designed for panel-mounted touchscreens, as opposed to FactoryTalk View SE (Site Edition), which is the PC-based SCADA software.
When you open FactoryTalk View Studio ME and create a new HMI project, you work with source files that include editable screens, tag definitions, alarm configuration, and communication settings. Once you build and compile the project, Studio generates an MER file. This MER file is what actually runs on the PanelView terminal — the end-user cannot modify it without FactoryTalk View Studio.
This separation of source and compiled is similar to how C++ code compiles to binaries or how Python code compiles to bytecode. The MER file is a deployment artifact, not a source file. It is optimized for fast execution on PanelView hardware and is in a proprietary binary format that Rockwell controls.
One key distinction: FactoryTalk View ME (Machine Edition) targets panel-mounted HMI terminals and is different from FactoryTalk View SE (Site Edition), which runs on workstations and generates APA files instead of MER files. If you are working with panel HMI projects, you will encounter MER files. If you are working with PC-based SCADA, you will see APA files.
What Is Inside an MER File?
MER files are binary archives that contain all the data needed to run a FactoryTalk View ME HMI on a PanelView terminal. The internal structure includes screens (also called displays or pages), tag definitions, alarm configurations, PLC communication settings, security configuration, and runtime metadata.
Screens (Displays): Each screen is a UI layout with buttons, text boxes, gauges, trend charts, and other graphical elements that the operator interacts with. MER files can contain dozens of screens. The screens are stored in a proprietary vector format designed for the PanelView hardware.
Tag Database: Tags are named variables that represent real-time data from the connected PLC or hardcoded values within the HMI. An MER file contains the complete tag database with data types, initial values, access permissions, and aliases. These tags are displayed on screens, logged to files, or sent to alarms.
Alarm Definitions: MER files include alarm configurations that trigger when tag values exceed thresholds or when communication errors occur. Alarms can be severity-based (critical, warning, info) and can be routed to audio alerts, email notifications, or logged to a database. The alarm table stores the complete message text, alarm type, and response actions.
PLC Communication Configuration: MER files embed the RSLinx communication settings that tell the HMI how to connect to the PLC — which controller, which network protocol (EtherNet/IP, ControlLogix, CompactLogix), IP address, slot number, and data refresh rates. Security settings like user authentication, role-based access control, and password hashes are also stored.
How Do You Open an MER File?
There are three primary ways to open an MER file: FactoryTalk View ME Station (the free runtime), FactoryTalk View Studio ME (the licensed development environment), or plc.company (a web-based viewer).
FactoryTalk View ME Station: This is the free runtime application that PanelView terminals use to execute MER files. It displays the HMI screens and handles tag updates, alarms, and PLC communication. However, ME Station is designed for production runtime only — it does not let you edit screens or inspect the underlying file structure. It is also only installed on the PanelView terminal itself, so you cannot easily view an MER file on a desktop or laptop computer.
FactoryTalk View Studio ME: This is Rockwell's official development environment. Studio can open and edit MER files, but it requires a paid license (several thousand dollars per seat). Studio is the only tool that lets you modify screens, update tags, or rebuild the project. However, many organizations do not have Studio licenses readily available, and you may not have access to it.
plc.company: This is a web-based MER file viewer that parses the binary format in your browser. You upload your MER file, and plc.company displays all screens, tags, alarm definitions, and PLC communication settings without requiring any Rockwell software or licenses. This is the fastest and most accessible way to inspect an MER file when you do not have FactoryTalk View Studio available.
How Do You Convert an MER File Back to a Project?
FactoryTalk View Studio ME has an "Import MER" function that allows you to load a compiled MER file back into the editor as source code. However, this process is incomplete and comes with significant limitations. The import function can recover screen layouts and tag definitions, but it often loses or corrupts alarm configuration, complex script logic, user access control settings, and other advanced features.
This is the central problem organizations face: if you lose the original Studio project file and only have the MER binary, you cannot fully restore the source code. The import function is designed as a recovery tool for disaster scenarios, not as a reliable way to extract full project information. Many engineers report having to manually recreate missing configuration after an MER import.
plc.company solves this differently. Instead of trying to convert the MER back to editable source (which is lossy and painful), plc.company lets you read all the data directly from the binary format without conversion. You can inspect screens, tags, alarms, and communication settings in human-readable form. This avoids the data loss and manual reconstruction that comes with Studio's import function.
If you need to actually edit and rebuild the MER file, you will still need FactoryTalk View Studio ME and the original project. But if you just need to understand what is in the MER or troubleshoot a running HMI, plc.company is the faster option.
Why Are MER Files Hard to Work With?
MER files are difficult to work with for several technical and business reasons. First, the format is proprietary and binary. Rockwell does not publish the MER file specification, so there is no open documentation on the format structure. This means you cannot easily inspect, parse, or manipulate MER files with standard tools — you must use Rockwell software or a specialized parser like plc.company.
Second, MER files are version-locked. An MER file compiled with FactoryTalk View ME 10 may not open in ME 11 or ME 12 without conversion. This creates challenges when you inherit a project from an older system or need to migrate HMI applications across equipment generations. Version compatibility issues can prevent you from even opening a file on modern hardware.
Third, the license barrier is real. FactoryTalk View Studio ME costs thousands of dollars per seat. If you are a technician, contractor, or plant engineer who needs to inspect or troubleshoot an HMI, you may not have access to a Studio license. This forces you to rely on whoever owns the software or to travel to a location where it is installed.
plc.company removes this friction. By parsing MER files in the browser, we eliminate the version lock, the license requirement, and the need for specialized software. You can upload your MER file from any device and see everything inside — screens, tags, alarms, PLC communication — in seconds. This is especially valuable for troubleshooting, compliance audits, or understanding legacy systems where the original documentation is lost.