Edge Architectures
The Ignition Edge system is unique in that it can be very flexible and fill in the gaps in any system architecture. Ignition Edge is a smaller version of the standard Ignition install. Edge is deployed at the edge of a network to provide local visualization, data publishing, and centralized synchronization within a larger Ignition architecture.
Up to 35 days or 10 million data points of tag history can be stored locally with an Edge installation. Additionally, Alarm Journal and audit log data is able to be stored locally for 7 days.
Each Edge product (Panel and IIoT) offers specific functionality that works best in certain scenarios. The diagrams show some architecture options using Edge. Additionally, these architecture diagrams show an Edge Gateway paired with an Ignition Gateway, which shows how an Edge system architecture can be added on to any of the other Ignition architectures.
Panel​
An Edge Panel Gateway can act as a stand-alone panel by simply connecting to a local PLC and building a basic screen. When paired with a central Ignition Gateway, the Edge can also act as a local Client fallback, providing control on site in the event of a lost network connection.
Edge IIoT​
An Edge IIoT (formerly MQTT) Gateway provides a simple way of setting up an MQTT Publisher next to a PLC, allowing it to connect to a greater IIoT architecture. Here, you can see multiple types of devices using Ignition Edge to connect in the network.
Edge IIoT as a standalone Edge Gateway to publish device data from the edge of the network to an MQTT broker:
Edge IIoT as an Edge Gateway to publish device data from the edge of the network to an MQTT broker:
Edge IIoT and Edge Panel together to add a local client at the edge of the network and to publish data to an MQTT broker:
Synchronization and Central Management​
Data Synchronization​
Both Ignition Edge IIoT and Ignition Edge Panel can synchronize data from the edge of the network to a central Ignition Gateway over the Gateway Network. This includes tag history, Alarm Journal entries, and audit log data.
Edge stores data locally (up to 35 days or 10 million records) and uses Store and Forward to buffer data during network interruptions. When the connection is restored, buffered data is automatically forwarded to the central Gateway for long-term storage and enterprise-wide visibility. This architecture allows Edge to operate independently at the network boundary while maintaining centralized reporting and long-term data retention.
Enterprise Administration (EAM) Agent Mode​
Both Ignition Edge IIoT and Ignition Edge Panel can function as remote EAM agent Gateways when connected to a central Ignition Gateway with the Enterprise Administration module installed.
In this architecture, the central Gateway acts as the EAM Controller and the Edge Gateway acts as an agent. This allows centralized management of Edge Gateways, including project updates, configuration synchronization, backup coordination, and licensing management.