Ignition

Introduction

Ignition is an industrial software platform from Inductive Automation for SCADA, HMI, data acquisition, industrial integration and Industrial Internet of Things applications. The platform is widely used in modern OT environments thanks to its flexible architecture, strong IT integration capabilities and scalability.

Ignition stands out from classic SCADA platforms through:

• web-based architecture
• unlimited licensing models
• strong IT integration
• open standards
• modular extensibility
• extensive database integration

In industrial automation, Ignition is used for:

• process visualisation
• real-time monitoring
• production analysis
• alarm management
• MES functionality
• Historian solutions
• dashboarding
• OT data integration

The platform plays an important role in modern IT OT Convergence architectures and is often used as a central integration layer between OT and enterprise IT.

🏗️ Basic architecture

Ignition is built around a central gateway architecture.

Key components:

The gateway acts as a central platform for:

• data processing
• visualisation
• communication
• scripting
• alarming
• database connectivity

Unlike traditional SCADA systems, Ignition runs largely web-based.

⚙️ Module structure

Ignition uses a modular architecture.

Key modules:

This modular approach allows platforms to be built up in a scalable way.

🌐 OPC UA integration

One of Ignition’s key strengths is extensive support for OPC UA.

Ignition can function as:

• OPC UA client
• OPC UA server
• protocol gateway

This allows diverse OT systems to be integrated:

• PLC
• SCADA
• sensors
• edge devices
• industrial databases
• Historian systems

Supported protocols include:

• Modbus TCP
• EtherNet/IP
• Siemens drivers
• BACnet
• DNP3
• MQTT

This makes Ignition particularly suited to act as a central OT integration layer.

🧠 Tag system

The heart of Ignition is the tag system.

Tags represent:

• process values
• alarms
• machine status
• production data
• calculated values

Tags can come from:

Tags support:

• real-time updates
• alarming
• historisation
• scripting
• role-based security

Within large OT environments, millions of tags can be managed.

🖥️ HMI and visualisation

Ignition supports several visualisation platforms.

Vision

The classic desktop-based HMI platform.

Characteristics:

• Java-based clients
• traditional SCADA screens
• high compatibility
• mature functionality

Perspective

Modern web-based visualisation platform.

Benefits:

Perspective is becoming increasingly popular in modern smart factories.

📊 Historian functionality

Ignition contains integrated Historian functionality for OT data storage.

Applications:

• trending
• production analysis
• KPI monitoring
• audit trails
• predictive maintenance
• energy analysis

Data is typically stored in standard relational databases such as:

• PostgreSQL
• MySQL
• Microsoft SQL Server

Benefits:

• open architecture
• easy integration
• lower vendor lock-in
• IT compatibility

☁️ IIoT and MQTT

Ignition plays an important role in modern Industrial Internet of Things architectures.

Commonly used integrations:

• MQTT
• edge gateways
• cloud platforms
• Kafka
• REST APIs
• OPC UA

In modern smart factories, Ignition is often used as:

• central data hub
• edge platform
• Unified Namespace interface
• analytics gateway

Especially in combination with MQTT, an event-driven OT architecture emerges.

🔄 Unified Namespace

Ignition is often deployed within Unified Namespace architectures.

Ignition then acts as:

• central context layer
• OT data broker
• visualisation layer
• integration platform

Benefits:

Ignition is therefore becoming popular within modern data-driven production environments.

⚡ Performance and scalability

Ignition is designed for large industrial environments.

Key scalability characteristics:

• redundant gateways
• distributed architectures
• clustering
• gateway federation
• load balancing

Performance factors:

In very large OT environments, performance optimisation often requires specialist architectural choices.

🔐 OT cybersecurity

Through close integration between OT and IT, cybersecurity plays a crucial role in Ignition environments.

Key risks:

• unauthorised access
• web vulnerabilities
• credential misuse
• lateral movement
• API exposure
• supply-chain attacks

Important security measures:

Ignition supports integrations with:

• Active Directory
• LDAP
• SAML
• identity providers

🛡️ Security in IT/OT convergence

Because Ignition is often directly connected to enterprise IT systems, additional security challenges arise.

Typical integrations:

• MES
• ERP
• cloud analytics
• BI platforms
• mobile applications

Ignition is therefore often placed within:

• DMZ
• IDMZ
• OT data platform zones

Architectures are often designed according to:

• IEC 62443
• Zero Trust
• Defense in Depth

🧪 Practical example: smart factory

A modern production environment uses Ignition as the central OT data hub.

Architecture

Data flows

Functionality

The environment supports:

• real-time dashboards
• predictive maintenance
• OEE monitoring
• alarm management
• mobile visualisation

Security challenges

Key risks:

• insufficient segmentation
• uncontrolled APIs
• cloud exposure
• remote access
• credential misuse

OT security measures are therefore integrated according to:

• IEC 62443
• Zero Trust Architecture
• Defense in Depth

🔄 Lifecycle Management

Ignition requires active Lifecycle Management due to frequent software updates and integrations.

Important points of attention:

• Java versions
• module compatibility
• database upgrades
• certificate management
• script validation
• backup strategies

Changes typically require:

• staging environments
• test procedures
• rollback scenarios
• validation
• change management

In regulated environments, additional compliance requirements apply.

⚖️ Relevant standards

Ignition is often used within architectures that take into account:

📈 Role in IT/OT convergence

Ignition plays an important role in modern data-driven OT architectures.

Key trends:

• web-based SCADA
• cloud integration
• edge analytics
• MQTT architectures
• Unified Namespace
• AI integrations
• real-time production analysis

Benefits:

• open architecture
• strong scalability
• flexible integration
• modern visualisation
• lower vendor lock-in

Challenges:

• cybersecurity
• governance
• performance management
• complexity
• lifecycle management

Ignition is thus an important platform within modern industrial digitalisation.