Capture and Visualize More Data With Ignition Edge
Explore effective edge computing solutions |
Schedule a free demo
A Simple, Strong & Secure
Edge-of-Network Solution
Ignition Edge® makes edge computing easier and more affordable with far-reaching features for your field devices and OEM equipment. Extend your system with data syncing and system management. Use unlimited tag and device connections to expand data collection, then see it with versatile visualization tools. Run scripts or interface with applications out at the edge, too. It’s all possible with Ignition Edge.
Ignition Edge Product Sheet
Meet the Ignition Edge Product Line
Ignition Edge consists of two powerful product options: Edge IIoT and Edge Panel. Each edge computing solution contains different capabilities and functionality to best fit your specific needs so you can build robust local control systems that are future-proof and Industry 4.0‑compatible.
Ignition Edge Features
Unlock Your Entire Architecture With Ignition Edge
With Ignition Edge computing software, stranded data is a thing of the past. Seamlessly connect any network edge device, and publish and sync data to your central Ignition system. Install Edge products right onto devices on the plant floor or in the field so you can poll data right at the source.
Unlimited Tags & Devices
Includes unlimited tags and device connections for included drivers, and acts as an OPC UA server so it can connect with most PLCs.
Cross-Platform Compatible
Works seamlessly with most computing platforms and can run on virtually any edge device.
Transmit & Synchronize Data
Able to transmit data to any MQTT broker using the Sparkplug specification and acts as a limited remote server that synchronizes data.
Remote Synchronization
Acts as a limited remote server that synchronizes data from the edge to a central Ignition server.
Remote EAM Agent Gateway
Acts as a remote EAM Agent Gateway at the edge, working with a central Ignition server that has the Enterprise Administration Module (EAM).
Run Scripts at the Edge
Able to run scripts and create REST APIs for interfacing with third-party applications from the edge.
Internal Tag Historian
Turn a SQL database into a high-performance time-series tag historian.
Alarm Notifications
Stay aware of what’s happening at your facility and sites, wherever you are.
Event Logging
Capture and store critical event information at the edge.
Included Ignition Native Drivers
In addition to the OPC UA Module, Ignition Edge includes a multitude of drivers for connecting with virtually any PLC and device.
- UDP and TCP Drivers
- BACnet Driver
- Serial
- Allen-Bradley Driver Suite
- Siemens Driver
- Mitsubishi Driver
- Modbus Driver
- DNP3 Driver
- Omron Driver
- Opto 22 SNAP PAC Driver (by request)
- IEC 61850 Driver
Ignition Edge Architecture
A Piece of the Ignition Architecture
Designed to install and run on edge devices, Ignition Edge is perfect for distributing I/O, providing local visibility of data, collecting data from remote sites over slow connections, and offering robust fiber networks with more scalability and access to data.
Extend Your Network, Not Your Budget
Easy, affordable, and scalable, Edge products compliment and work seamlessly with Ignition. Add more real-time visibility and control to your Ignition architecture, from the plant floor to independent remote sites, without breaking the bank.
See Ignition Edge prices
The Difference Between Edge and Standard Ignition
Unlike standard Ignition, Edge runs a limited set of Ignition modules and has no database connectivity. It is meant for one Ignition project and one tag provider at a time. Edge does, however, include 35 days of internal data storage for historical and event logging.
Ignition Edge Architectures
Ignition's server-centric web-based deployment model enables you to build flexible architectures that easily scale up or down to match your growth needs. Ignition Edge installs and runs on your edge devices so you can connect assets and collect data straight from the source.
Ignition Edge Remote IIoT
Use Edge IIoT as an edge gateway to publish device data from the edge of the network to an MQTT broker and/or directly to an Ignition Gateway over a Gateway network connection.
Architecture Diagram
Ignition Edge IIoT Standalone
Use Edge IIoT as a standalone edge gateway to publish device data from the edge of the network to an MQTT broker or to an Ignition Gateway over a Gateway network connection.
Architecture Diagram
Standalone HMI
Use Ignition Edge Panel to create a standalone HMI at the edge of the network.
Architecture Diagram
Hub-and-Spoke with Local Client Fallback
Ignition Edge Panel adds local client fallback to a hub-and-spoke architecture. Edge Panel provides visualization at the edge, a 35 day data buffer to cache PLC data while a network connection is down, and store and forward functionality for when the connection is restored.
Architecture Diagram
Enhancing Edge Products
Ignition Edge IIoT and Panel come with a predefined set of modules. You can purchase additional Cirrus Link Solutions modules (Emerson ROC, ABB TotalFlow) for an additional cost. Contact your IA account representative for more details.
Ready for Deployment with Select Partner Devices
Ignition Edge products can be purchased by themselves or as part of select Opto 22 devices. Ignition Edge also comes preinstalled on select devices sold by some Inductive Automation Alliance Partners. Ignition Edge Ready devices sold by Alliance Partners do not include Edge licenses but are verified to be fully compatible with Edge.
Edge FAQs
What are the use cases for Ignition Edge?
Ignition Edge has two primary use cases: local I/O with store-and-forward to a central system, and local HMI or fallback client for visibility and control of data.
- Local I/O with Store-and-Forward: Easily deploy Ignition Edge IIoT or Panel to provide local I/O with store-and-forward to a central Ignition system.
- Local HMI or Fallback Client: Easily deploy Ignition Edge Panel to provide on-site local visibility and control of your data.
When do I use Ignition Edge versus a standard Ignition server?
Ignition Edge is perfect for distributing out I/O, providing local visibility of data, efficiently collecting data from remote sites over slow connections, and for robust fiber networks to offer more scalability, access to data, and distribution of I/O. It is limited and designed to work in tandem with a central Ignition system. Ignition Edge is not suitable to run an entire facility or site as a SCADA system, nor is it designed to act as an unlimited I/O server for all of your PLCs. If you need local functionality and have a use case that requires features beyond Ignition Edge, a standard Ignition server is recommended.
What’s the difference between Ignition Edge IIoT and Ignition Edge Panel?
Both Edge IIoT and Edge Panel include unlimited tags and device connections, the ability to publish MQTT data, run scripts, create REST APIs, synchronize data to a central server, and act as an EAM Agent Gateway. Ignition Edge Panel also includes local visualization and control functionality, which is ideal for local HMIs or remote systems, using Perspective (2 sessions) or Vision (1 local client, 1 remote client). Ignition Edge IIoT does not include visualization capabilities.
Is Ignition Edge IIoT meant to be used as a standalone solution?
No. Ignition Edge IIoT is designed to work seamlessly with a central Ignition server for optimal performance, and to synchronize data to a centralized system and provide critical functionality.
Is Ignition Edge Panel meant to be used as a standalone solution?
Yes. Ignition Edge Panel is designed to work both as software for standalone HMIs and also work seamlessly with a central Ignition server. When connected to a central server, it can easily synchronize data to a centralized system and provide optional remote access and control.
How does Ignition Edge communicate to a central Ignition server?
Ignition Edge can communicate with a central Ignition server in two ways: through the Gateway Network and MQTT. You can configure both connection methods at the same time.
For more information about how to configure the Gateway Network and the MQTT protocol, please visit the user manual: https://www.docs.inductiveautomation.com/
Is Ignition Edge a good option for data collection in my industry?
It depends on your needs. For many industries, such as manufacturing, oil & gas, automotive, and food & beverage, Edge can be a great option for local data collection. In industries with large numbers of simple devices, Ignition Edge typically isn’t a good fit. Examples of these are applications like inverter connections in the solar industry, certain municipality connections, power distribution, building automation, or other industries where connections to hundreds of simple devices are standard. For these industries, a full version of Ignition is a better alternative to Edge.
Does Ignition Edge support OPC UA?
Yes. Ignition Edge supports OPC UA as a server and client. Ignition Edge can communicate to any external OPC UA (or OPC COM) server to bring in data. Ignition Edge can also expose data through OPC UA locally. However, Ignition Edge is not designed to be a full-blown OPC UA server.
Where can I deploy Ignition Edge to?
Here are some of the many devices, services, and systems on which you can deploy Ignition Edge:
- Devices: Embedded PCs, laptops, desktops, high-grade servers, fog computing
- Managed Services: AWS EC2, AWS ECS, AWS Outposts, Azure Virtual Machines, Azure Containers, Google Compute Engine
- Virtual Machines & Containers: VMware, Parallels, VirtualBox, Hyper-V, Docker
Does Ignition Edge support ARM?
Yes. With support for ARM processors (32-bit HF and 64-bit), Ignition Edge can run on devices like Raspberry Pi or the latest generation of edge devices.
Can Ignition Edge work with SQL databases?
No, Ignition Edge cannot communicate to external SQL databases. It is designed to synchronize data to a central Ignition server that is communicating with a SQL database. Ignition Edge has everything built-in to store and forward data to a central Ignition server with ease.
Can I deploy Ignition through Docker or orchestration platforms?
Yes. Inductive Automation has an official Docker hub image that allows you to quickly deploy Ignition or Ignition Edge on any device. You can also use orchestration platforms such as Zededa, Balena, Azure Stack Edge, edgeIQ, and more.
For more information on Ignition’s official Docker hub image: https://hub.docker.com/r/inductiveautomation/ignition
Is it possible to upgrade Ignition Edge to a standard Ignition server?
Yes, it is possible. Ignition and Ignition Edge share the same basic technology. To learn more about how you can upgrade, please contact our sales representatives at 1-800-266-7798.
Where can I purchase Ignition Edge?
You can purchase Edge directly through Inductive Automation or from our Solution Partner, Opto 22. When purchasing from Inductive Automation, you will be responsible for installing Ignition. When purchasing an Ignition Edge Included device from Opto 22, Edge will come preinstalled and pre-licensed on your device for faster development.
For more details about our Solution Partner, Opto 22, go to: https://inductiveautomation.com/partners/solution-partners/opto22/