Representative End User Clients
Representative Automation Clients
Representative Software Clients
Inductive Automation’s annual community conference highlighted Ignition 2027, historian strategy, practical AI enablement, open standards, and the expanding role of SCADA as an industrial application platform.
Inductive Automation’s ICC 2026, held September 22–24 in Sacramento, reinforced how far the Ignition ecosystem has evolved. What began as a disruptive SCADA platform has become a broader foundation for industrial applications, data operations, historian workloads, open standards integration, and practical AI enablement.
The message throughout the event was clear: industrial organizations want more than visualization and supervisory control. They want flexible platforms that support modernization without lock-in, scale data architectures across the enterprise, reduce engineering effort, and help operations teams move faster while maintaining governance and reliability.
Ignition 2027 Extends the Platform Vision
A major focus of ICC 2026 was Ignition 2027, the first release under Inductive Automation’s calendar-based major release cadence. The company positioned Ignition 8.3 as the current long-term support foundation while identifying Ignition 2027 as the next step in making advanced platform capabilities more accessible.
The release direction reflects several customer priorities, including stronger cybersecurity readiness, expanded operational data APIs, partial gateway import and export, Excel-based tag import and export, enhanced audit logs, OPC UA event-source support, Perspective Workstation improvements, and deployment automation through first-party Ansible tooling.
Taken together, these enhancements point to a maturing platform designed not only for project delivery but also for lifecycle management, governance, repeatability, and enterprise-scale deployment.
Historian Strategy Becomes an Increasingly Competitive Battleground
One of the most important announcements was Inductive Automation’s partnership with Tiger Data to support TimescaleDB for Ignition and a new Enterprise Historian Module. This is strategically significant because historian architectures are becoming more central to industrial data strategies.
Many customers want high-volume time-series performance, efficient storage, strong query capabilities, enterprise support, and continued openness. By building around a SQL-oriented time-series foundation, Inductive Automation is positioning its historian strategy as a more open alternative to traditional historian architectures.
For ARC, this is an important development to monitor. The historian market is being reshaped by open-source databases, cloud-native architectures, industrial DataOps requirements, and the need to connect real-time operations with analytics and AI initiatives.
Practical AI, Not AI Hype
ICC 2026 also showed how AI is entering industrial software in more practical forms. Ignition Catalyst was positioned around AI-assisted engineering, diagnostics, and user-defined agents rather than fully autonomous operations.
This distinction matters. In industrial environments, the near-term value of AI is likely to come from helping engineers work faster, generating or troubleshooting logic and queries, enriching alarms, improving diagnostics, and enabling controlled interaction with operational context. Inductive Automation’s direction also emphasizes customer control over data exposure and bring-your-own-model flexibility, both of which are important for industrial users.
The broader lesson is that AI in OT will advance through governed, contextualized, and operationally constrained use cases before it is trusted for higher levels of autonomy.
Open Standards Remain Central to Modernization
Open architecture was a recurring theme across the event. Sessions reinforced the complementary roles of OPC UA, MQTT, Sparkplug, CESMII/i3X, and open process automation. Rather than competing directly, these standards and models address different aspects of industrial interoperability.
OPC UA and Companion Specifications help standardize information models. Sparkplug adds publish/subscribe communication, network state awareness, and efficient payload structures. CESMII’s i3X initiative provides an open API approach for interacting with contextualized manufacturing information platforms. Open process automation continues to push the market toward greater modularity and vendor independence.
The common thread is that industrial companies are trying to reduce bespoke integration work. Standardized data models, reusable architectures, and interoperable systems are becoming essential to modernization programs.
The Ecosystem Message Is Getting Stronger
Partner sessions from HighByte and Cirrus Link added depth to the platform story. HighByte positioned industrial DataOps as a governance and contextualization layer between complex OT environments and enterprise systems. This reflects a broader market need: industrial data is no longer just real-time telemetry. It includes historical, transactional, contextual, and file-based data that must be modeled, governed, and delivered to many consumers.
Cirrus Link highlighted the continued expansion of MQTT and Sparkplug adoption. The discussion reinforced the value of event-driven architectures, reduced bandwidth consumption, standardized tag structures, and scalable deployment practices. Large renewable energy deployments demonstrated how Ignition, MQTT, Sparkplug, UDTs, templates, EAM, and rigorous QA processes can support enterprise-scale rollout across many assets and sites.
These examples show that the Ignition ecosystem is not only expanding through software capabilities but also through implementation practices, partner technologies, and reusable reference architectures.
Modernization Is a Change-Management Challenge
Several customer and practitioner sessions made another point clear: modernization is not simply a software conversion. Legacy SCADA migration, MES-like application development, and enterprise data architecture all require stakeholder alignment, process mapping, standards, training, phased validation, and clear ownership.
This is especially important as customers use Ignition for broader application development. The platform may enable faster development, but successful outcomes still depend on disciplined requirements, governance, and organizational readiness.
The JELD-WEN example was especially relevant because it showed how an end-user team used Ignition to build MES-like capabilities for production tracking, downtime capture, maintenance dispatching, operator launchpads, and visual management. This points to the growing importance of low-barrier industrial application development supported by strong training, community resources, and reusable examples.
ARC Takeaway: SCADA Is Becoming a Broader Industrial Platform Layer
ICC 2026 reinforced a larger market shift: SCADA is no longer just a supervisory control and visualization layer. In many industrial organizations, SCADA platforms are becoming application platforms, integration hubs, data movement layers, historian front ends, and AI enablement environments.
This does not mean every customer will use a single platform for everything. However, it does mean that platform flexibility, openness, data governance, ecosystem strength, and lifecycle scalability are becoming more important selection criteria.
For Inductive Automation, the opportunity is significant. Its challenge will be to continue scaling enterprise capabilities, support models, cybersecurity posture, historian performance, and AI governance while preserving the openness and accessibility that made Ignition successful.
For the broader market, ICC 2026 was another signal that industrial software competition is shifting. The winners will not only provide applications; they will provide platforms that help customers modernize incrementally, govern data effectively, integrate openly, and prepare for practical AI adoption.