What is Ignition? SCADA, IIoT and MES platform, modules and alternatives
Ignition is an industrial application platform from Inductive Automation used to build SCADA, HMI, historian, reporting and IIoT applications. It connects to PLCs and databases, stores tag history in SQL, and lets integrators build web based screens and logic. Many manufacturers also use it as a foundation for MES style applications such as OEE, downtime tracking and production reporting.
Also known as: Ignition SCADA, Inductive Automation Ignition, Ignition by Inductive Automation
Ignition is built around a Gateway, a server that connects to devices through OPC UA and other drivers, manages tags, runs scripts and serves applications. Developers use the Designer client to build screens, reports, alarms and logic, and operators view them through Vision desktop clients or Perspective web and mobile sessions. Tag history and other data are stored in standard SQL databases, which keeps the data accessible to other tools.
The platform is modular. Core modules cover OPC UA, tag historian, alarming, reporting and scripting, while optional modules add drivers for specific PLC brands, SQL bridging, MQTT connectivity and other functions. Third-party modules extend it further, including MES style products such as OEE, scheduling and track and trace from partners. Because of this, Ignition is commonly used as a flexible base rather than a finished MES.
In a manufacturing stack, Ignition usually sits between the plant floor equipment and the business systems. PLCs and sensors feed it, and it passes production counts, downtime and quality data to the ERP and analytics platforms through SQL, web services or MQTT. Success depends heavily on the integrator or in-house team building the applications, since most of the value is created by configuration and design work.
Modules and capabilities
Gateway and OPC UA
Server platform that connects to devices, manages tags and exposes data using OPC UA and device drivers.
Vision
Desktop HMI and SCADA client technology for building and running operator screens.
Perspective
Web based, mobile friendly application framework for responsive industrial screens and dashboards.
Tag historian and SQL
Time series history of tags stored in SQL databases, with tools for trends and queries.
Alarming and notification
Alarm definition, state tracking, history and notification pipelines to people and systems.
Reporting
Report design and scheduled delivery from tag and database data.
MQTT and edge modules
Optional modules for MQTT based data exchange and edge deployments, from Inductive Automation and partners.
Third-party MES modules
Partner products that add OEE, scheduling, genealogy and quality functions on top of the platform.
Integrations and data access
PLCs and devices
Native OPC UA and drivers for many PLC brands, plus third-party drivers and servers such as Kepware class connectivity.
SQL databases
Works with common SQL databases such as Microsoft SQL Server, PostgreSQL, MySQL and Oracle for tag history and application data.
MQTT
Supports MQTT based architectures through partner modules, useful for publishing data to brokers and the cloud.
ERP and business systems
Typically integrated through SQL tables, web services or REST calls, with logic written in Python based scripting.
Web and APIs
Exposes and consumes web services, and Perspective sessions can be embedded or reached through browsers.
Strengths
- Highly flexible platform that integrators can adapt to unusual requirements
- Standard SQL storage keeps data open and easy to reuse in other tools
- Web based Perspective apps work on browsers and mobile devices
- Large ecosystem of integrators and third-party modules
- Vendor neutral approach to PLC connectivity
Limitations
- It is a platform, so a finished MES requires design and build effort or a partner module
- Quality of results varies with the skill and standards of the team building the applications
- Governance, version control and testing practices must be set up deliberately
- Regulated electronic records use cases need careful validation and may need extra tooling
Where AI helps Ignition users
- - Generating tag naming, alarm descriptions and documentation from existing project files
- - Anomaly detection on historian data for equipment drifting outside normal behavior
- - Natural language summaries of shift alarms, downtime and production events for supervisors
- - Drafting scripts and SQL queries for engineer review and testing
- - A private assistant that answers questions over plant history and maintenance notes without data leaving the site
Evaluating Ignition? Check these
- Decide who will build and maintain the applications: internal engineers or an integrator
- Define tag naming, project structure and version control standards before development starts
- Plan database sizing and retention for tag history from the start
- If you need MES functions, evaluate third-party modules against your requirements instead of assuming they exist
- Design cybersecurity, network zones and user authentication for the Gateway
- Test the ERP interface with real work orders and failure cases before go-live
Common alternatives: Proficy, AVEVA System Platform, Siemens WinCC, Rockwell FactoryTalk, Tulip, MachineMetrics.
Frequently asked questions
What is Ignition used for?
Ignition is used to build SCADA, HMI, historian, alarming and reporting applications, and to move plant data to databases and business systems. Manufacturers also use it as a foundation for OEE, downtime tracking and other MES style applications on the shop floor.
Is Ignition an MES?
Not out of the box. Ignition is an industrial application platform, and MES functions are typically built on it or added through third-party modules. This gives flexibility but requires design effort, so compare the total build and support cost against a packaged MES.
What database does Ignition use?
Ignition stores its own configuration internally and uses external SQL databases for tag history, alarms and application data. Common choices include Microsoft SQL Server, PostgreSQL, MySQL and Oracle, which keeps the data accessible to analytics and reporting tools.
Can Ignition run on-premise?
Yes. Ignition is commonly installed on servers inside the plant, and can also run in private or public cloud virtual machines. This makes it a frequent choice where plant data needs to stay local or where air-gapped networks are required.
How does Ignition connect to an ERP?
Usually through SQL tables, web services or REST APIs, with scripting handling the logic. Production counts, downtime and quality data can be written to the ERP or staging tables. The design of that interface is important and should be tested carefully.
Running Ignition?
We add AI, chat, automation and integrations to the systems manufacturers already run, on-prem if needed.
Get a free assessment