Complete Guide to Ignition SCADA by Inductive Automation

Quick Answer

Ignition by Inductive Automation is a web-deployed SCADA platform built on a gateway architecture that connects industrial devices via OPC-UA, stores process data in SQL databases, and delivers HMI screens through browser-based or native clients. It is widely used in oil and gas, utilities, and manufacturing.

What Is Ignition SCADA?

Ignition is a full-featured industrial automation platform developed by Inductive Automation in Folsom, California. Unlike legacy SCADA software that relies on per-seat licensing and proprietary databases, Ignition uses an unlimited licensing model — one license covers unlimited tags, clients, and connections. The platform runs on the Java Virtual Machine, making it cross-platform (Windows, Linux, macOS) and deployable on standard IT hardware or cloud infrastructure.

Ignition serves as the central hub for supervisory control and data acquisition in facilities ranging from single-site oil production batteries to enterprise-wide pipeline monitoring networks. Its modular architecture lets integrators pick only the modules they need — Perspective for web HMI, Vision for desktop clients, SQL Bridge for transaction groups, Alarm Notification for callout, and Reporting for automated PDF generation.

How Ignition Works: Gateway, Designer, Client Architecture

Ignition follows a three-tier architecture that separates the runtime engine from the design environment and the operator interface:

• Gateway — The server-side process that manages all OPC-UA device connections, runs Python scripting, executes tag logic, handles alarm routing, and serves client sessions. The gateway runs as a system service and is configured through a web-based administration console on port 8088 (HTTP) or 8043 (HTTPS).
• Designer — A thick-client application launched from the gateway webpage. Integrators use the Designer to create screens (windows or views), configure tags, write scripts, build reports, and set up alarm pipelines. Multiple designers can connect simultaneously for team-based development.
• Client — The operator-facing interface. Vision clients launch as Java applications from the gateway. Perspective clients run in any modern web browser or the Perspective Workstation app, with full responsiveness for mobile and tablet use.

This separation means the gateway can run on a hardened server in a datacenter or control room, while operators view screens from any networked device. Gateway-to-gateway communication via the Gateway Network allows multi-site architectures with centralized historian and alarm management.

Key Modules

Perspective

Perspective is Ignition's modern, web-native visualization module. It renders screens using HTML5 and CSS in any browser — desktop, tablet, or phone — without plugins or Java. Perspective is the recommended module for new projects and supports responsive layouts, session-based security, and mobile gestures.

Vision

Vision is the original desktop visualization module. It launches as a Java application and is well-suited for control room environments with dedicated operator workstations. Vision provides a rich library of industrial components (tanks, valves, pumps, trend charts) and supports template-based screen design.

Reporting

The Reporting module generates PDF, HTML, or CSV reports on a schedule or on demand. Reports can pull data from historian tags, SQL queries, or script-generated datasets. Common use cases include daily production summaries, shift handoff reports, and regulatory compliance documents.

Alarm Notification

Alarm Notification handles callout via email, SMS, and voice. Alarm pipelines define escalation logic — if the primary operator does not acknowledge within a configurable window, the alarm escalates to a supervisor or on-call engineer. Rosters and schedules are managed inside the gateway.

SQL Bridge

SQL Bridge provides transaction groups that move data between OPC tags and SQL database tables without scripting. It supports historical logging, database-to-tag writes, and stored procedure execution. SQL Bridge is the backbone of Ignition's historian functionality.

OPC-UA

Ignition includes a built-in OPC-UA server and a comprehensive library of device drivers. Supported protocols include Allen-Bradley EtherNet/IP and ControlLogix, Siemens S7, Modbus TCP/RTU, DNP3, BACnet, MQTT Sparkplug B, and many more. The OPC-UA module also supports connections to third-party OPC servers.

Ignition in Oilfield and Industrial Automation

Ignition has gained significant adoption in upstream and midstream oil and gas operations. Its unlimited licensing model is particularly attractive for pipeline SCADA deployments where thousands of RTU data points must be monitored without escalating software costs. Common oilfield use cases include:

• Pipeline SCADA — Monitoring pressure, flow, and temperature across hundreds of miles of gathering and transmission pipelines, with leak detection algorithms running in gateway scripts.
• Production Monitoring — Real-time visualization of wellhead pressures, separator levels, compressor status, and tank volumes across multiple production batteries.
• Tank Farm Management — Automated tank gauging with high-level shutdowns, custody transfer calculations, and regulatory reporting for LACT units.
• Wellsite Automation — Rod pump controllers, plunger lift optimization, and artificial lift monitoring with historian trending and alarm callout to field operators.

In these deployments, Ignition typically connects to field RTUs such as the Bristol FB300, Emerson ControlWave, or ABB RTU560 via DNP3 or Modbus TCP. The gateway aggregates data from hundreds of remote sites and presents unified dashboards to control room operators.

Connecting Devices with OPC-UA

Ignition's OPC-UA module is the bridge between field devices and the SCADA application layer. Configuring a device connection involves:

1. Opening the gateway web interface and navigating to Config > OPC-UA > Device Connections.
2. Selecting a driver (e.g., "DNP3 Driver" for RTUs, "Modbus TCP" for meters, "Allen-Bradley" for ControlLogix PLCs).
3. Entering the device address (IP, port, DNP3 addresses or Modbus unit ID).
4. Configuring scan classes to set polling rates (e.g., 1-second for critical analogs, 10-second for status discretes).
5. Browsing the OPC device tree in the Designer to verify tag availability and data quality.

For environments with Bristol FB300 RTUs running DNP3, Ignition's DNP3 driver supports unsolicited responses, class-based polling, and secure authentication (SA) for critical infrastructure compliance.

Python Scripting in Ignition

Ignition uses Jython (Python 2.7 on the JVM) for all scripting. Scripts can execute in several contexts:

• Gateway Event Scripts — Timer scripts, tag change scripts, and message handlers that run on the server regardless of client state.
• Tag Event Scripts — Value change, quality change, and alarm event handlers attached directly to tags.
• Client/Session Event Scripts — Startup, shutdown, and periodic scripts scoped to individual client or Perspective sessions.
• Component Event Scripts — Mouse click, property change, and action performed handlers on individual screen components.

Ignition provides extensive scripting APIs through the system.* namespace — system.db for database queries, system.tag for tag reads and writes, system.alarm for alarm queries, system.net for HTTP requests, and system.util for threading and scheduling. The scripting console in the Designer allows rapid prototyping and debugging.

Database Historian Integration

Unlike legacy SCADA platforms that store data in proprietary formats, Ignition logs all historical data to standard SQL databases — MySQL, Microsoft SQL Server, PostgreSQL, MariaDB, or Oracle. This approach provides several advantages:

• Standard SQL queries for reporting and analysis
• Integration with BI tools (Power BI, Tableau, Grafana)
• Familiar backup and replication using database-native tools
• No vendor lock-in on historical data

Tag history is configured per tag or tag group in the Designer. The historian stores timestamped values with configurable deadband and scan rates. Transaction groups (via SQL Bridge) handle bulk data transfers between OPC tags and database tables for recipe management, batch tracking, and production logs.

Alarm Management

Ignition provides a unified alarm system across all connected devices. Alarms are configured on tags using setpoint, deviation, bit-level, or expression-based triggers. Key alarm management features include:

• Alarm Journal — Persistent storage of all alarm events (active, acknowledged, cleared) in a SQL database for regulatory compliance and post-incident analysis.
• Alarm Pipelines — Visual workflow builder for escalation logic, notification routing, acknowledgment collection, and roster-based scheduling.
• Real-time Alarm Status Table — A built-in component that displays active alarms with filtering, sorting, and shelving capabilities for operator workstations.
• ISA-18.2 Support — Alarm rationalization and priority classification aligned with the ISA-18.2 standard for alarm management in process industries.

Ignition Edge and IIoT

Ignition Edge is a lightweight version of the platform designed for deployment on field hardware and edge computing devices. Edge editions include:

• Edge Panel — Local HMI with a limited tag count for operator interfaces at remote sites such as wellheads or pump stations.
• Edge Compute — Gateway scripting and database logging at the edge, enabling store-and-forward when WAN connectivity is intermittent.
• Edge IIoT — MQTT Sparkplug B publisher that transmits tag data to a central Ignition gateway or any Sparkplug-compatible broker, enabling efficient IIoT architectures with minimal bandwidth.

Edge gateways buffer data locally during network outages and automatically forward stored records when connectivity is restored. This store-and-forward capability is critical for oilfield sites served by cellular or satellite links with variable reliability.

Sub-Article Links

Explore the full Ignition SCADA knowledge cluster:

• Ignition SCADA Platform Overview
• Ignition Installation and System Requirements
• Gateway Configuration and Administration
• Designer Basics: Navigation, Components, and Bindings
• Tag Configuration and OPC Browsing
• Python (Jython) Scripting in Ignition
• OPC-UA Device Connections and Driver Setup
• Database and Historian Integration
• Alarm Management and Notification Pipelines
• Reporting Module: Scheduled and On-Demand Reports
• Ignition Edge and IIoT with MQTT Sparkplug B
• Troubleshooting Ignition: Logs, Diagnostics, and Common Issues