Ignition MES Integration: Connecting Perspective to a Central MES

Published 22 October 2026 · 6 minute read

Plenty of plants already run their HMIs on Ignition. The question is how the operator at that HMI reaches the MES without a second screen, a second login and a clipboard. This article walks through the choices and what a working connection needs.

Three ways to connect Ignition to an MES

• Tags only. The MES reads PLC data and the HMI shows nothing of the MES. Cheap, but the operator still codes downtime and records quality somewhere else.
• MES inside Ignition. MES modules that run in the gateway itself. Tight integration, but the MES data, licences and upgrades now live in every gateway.
• A connector to a central MES. Ignition stays the operator's screen; the records live in one MES for all plants. This is the PulseMQ approach.

What a working connection must get right

The operator's own identity

A shared "HMI" account in the MES defeats the audit trail: every downtime code and every hold carries the same name. The operator should sign in as themselves, ideally with single sign-on, and the gateway should act on their behalf.

Surviving the network

Plants lose their uplink. A downtime reason or a label report entered during an outage must wait in a queue that survives a gateway restart and be sent exactly once when the link returns.

No custom code per site

If every new line needs its own scripting project, the integration does not scale. Machines, functions and PLC tags should be settings; the module should be the same signed file everywhere.

Pairing, not passwords in project files

The gateway should be paired with the MES once, with a short-lived code an MES admin creates, and keep its secret encrypted, never in a project or a tag.

What it looks like in practice

With the PulseMQ MES Connector, a Station component in the HMI's header shows the job, downtime, material, checks, logbook, documents and help calls for that machine. A bar button opens the section; nothing else on the HMI changes. Commissioning a new line is a gateway setting, a template view and one property. The records feed the same downtime tracking, OEE and traceability as the rest of PulseMQ MES.

Connect your Ignition HMIs →

Frequently asked

Can Ignition be connected to a cloud MES?
Yes. A gateway module can call the MES over HTTPS on the operator's behalf and show MES functions in Perspective, with nothing opened inbound on the plant network.

Should the HMI use a shared MES account?
No. A shared account means every record carries the same name. Each operator should sign in as themselves so the audit trail names the person who made each record.

What if the plant loses its internet connection?
A good connector queues what the operator enters, survives a gateway restart and sends each action exactly once when the link returns.

Ignition is a trademark of Inductive Automation. PulseMQ is not affiliated with or endorsed by Inductive Automation.