Ignition 8.3 One Year Later: Key Changes for Industrial Automation Teams

It has been just over a year since Inductive Automation released Ignition 8.3, its latest long-term support version. For industrial automation teams still working with Ignition 8.1 or considering their next upgrade, it's a good time to look at which changes could have the most practical impact.

Ignition 8.3 introduced updates across Gateway configuration, source control, historical data storage, mobile applications, deployment, security, and system integration. Not every feature will matter equally to every facility, but several are worth understanding when planning how an Ignition system will be developed and maintained.

More Control Over Gateway Configuration

One of the most significant changes in Ignition 8.3 is how teams can manage Gateway configurations.

The redesigned Gateway web interface includes updated navigation and search, while a documented REST API allows authorized external tools to read and modify configurations programmatically. For teams managing multiple Gateways, this creates opportunities to automate repetitive setup tasks and check configurations more consistently.

Ignition 8.3 also moves Gateway configuration out of the internal configuration database and into the file system. This extends source control beyond project resources to settings such as device connections, database connections, and tag configurations.

Because these configuration files are human-readable, teams can use tools such as Git to compare changes, maintain revision histories, and incorporate peer review into their change management process.

Teams still need to establish their Git repositories, workflows, and review practices. But for organizations looking to bring more structure to automation system changes, 8.3 provides more options for doing so.

New Options for Field and Mobile Workflows

Ignition Perspective also received several updates that affect how teams can build operator interfaces and mobile applications.

New drawing tools allow developers to create SVG-based graphics directly in the Designer, while the new Form component supports structured data entry, validation, and submission handling for applications such as equipment inspections, production records, and commissioning checklists.

Offline Mode takes that a step further. Supported workflows in the Perspective mobile app can use cached project resources and queue form submissions when connectivity isn't available, then deliver them when the device reconnects.

That can be useful for inspections or commissioning activities that require someone to move throughout a facility where reliable connectivity isn't guaranteed.

There are limitations. Offline Mode must be enabled and configured, and it isn't available in a desktop browser. Live tag values, alarms, database queries, and Gateway-dependent scripts are unavailable while disconnected, so applications need to be designed and tested specifically for offline use.

A New Approach to Historical Data

Another notable addition is the Core Historian, introduced before release as Power Historian.

Powered by an embedded QuestDB engine, Core Historian provides a time-series storage option without requiring a separately managed external database for that history. Its capabilities include automatic time-based partitioning, optional data deduplication, native aggregation, and configurable retention.

For plants collecting large amounts of process data, the potential benefit is simpler historian infrastructure and efficient storage and retrieval.

But upgrading to Ignition 8.3 does not automatically mean moving to Core Historian. Ignition continues to support other historian storage options, including external databases. Existing history, reporting dependencies, backup procedures, availability requirements, collection rates, retention settings, and query workload should all factor into that decision.

More Consistent Development, Test, and Production Environments

Gateway Deployment Modes allow teams to define environment-specific overrides for Gateway resources.

For example, a database connection can point to a test database during development and then to a production database after deployment. This can reduce repetitive configuration changes and help prevent a test system from accidentally connecting to production equipment.

Teams still need to define and verify the settings for each environment, and changing the active mode requires a Gateway restart. Deployment modes complement an established project release process rather than replacing one.

New Ways to Move Data Between Systems

Event Streams provide a common way to receive, filter, transform, and route events within Ignition.

Sources can include tag events, event listeners, Kafka, and HTTP endpoints. Handlers can then send the resulting data to other systems or trigger actions within Ignition.

For example, a production event could be transformed into a standard message and sent to an enterprise application. Keeping that logic within an event stream can make it easier to maintain than distributing it among unrelated scripts.

Available connections depend on the modules installed. Kafka requires the Kafka module, HTTP sources and handlers require Web Dev, and database handlers require SQL Bridge.

Other Ignition 8.3 Updates Worth Knowing About

Several additional changes may be useful depending on a facility's systems and applications:

• Siemens connectivity: The Siemens Enhanced Driver adds browsing and symbolic addressing for supported S7-1200 and S7-1500 controllers.
• Alarm notifications: Twilio Voice and WhatsApp alarm notification profiles provide additional options for delivering and acknowledging alarms.
• Secrets management: The Secrets Management system helps teams manage passwords, tokens, and other sensitive values without hard-coding them into application logic.
• Aggregated alarm metrics: Metrics at the tag-folder and UDT-instance levels can simplify area-level status displays and equipment summaries.
• Application launching: Launcher deep links and file associations can simplify opening a specific project or Designer directly.
• Container deployments: An official Helm chart gives teams using Kubernetes a starting point for repeatable Ignition Gateway deployments.

Don't Overlook Backup and Recovery

Gateway backups remain central to recovery planning, but a Gateway configuration backup is only one piece of a complete recovery plan.

External database contents and PLC programs require separate protection. Before upgrading, teams should verify exactly what each backup contains and test the restore process.

Planning the Move from Ignition 8.1 to 8.3

Just over a year after its release, the strongest reasons to move to Ignition 8.3 still depend on the application.

For one facility, easier configuration management and change review may be the biggest advantage. Another may benefit more from historian improvements, mobile field data collection, or new integration options.

 For teams currently using Ignition 8.1, the support lifecycle also provides a reason to evaluate the current control and SCADA system as part of upgrade planning. 

That doesn't mean every system needs to be upgraded immediately. It does mean there is value in understanding which 8.3 changes matter to your applications, what an upgrade will require, and how the transition fits into your longer-term automation strategy.

If you're evaluating an Ignition upgrade or considering how 8.3 fits into your existing automation environment, Hallam-ICS can help you assess your current system and plan a transition based on your operational requirements.

Contact Us

Frequently Asked Questions About Ignition 8.3

When was Ignition 8.3 released?

Inductive Automation released Ignition 8.3 on September 16, 2025. It is a long-term support (LTS) release, with active support scheduled through September 16, 2030.

What are some of the key changes in Ignition 8.3?

Ignition 8.3 includes changes to Gateway configuration and source control, Perspective mobile workflows, historical data storage, deployment modes, Event Streams, security, alarm management, and other development and integration tools. Which changes matter most will depend on the application and how an organization uses Ignition.

Do I need to use Core Historian when upgrading to Ignition 8.3?

No. Core Historian provides a time-series storage option powered by QuestDB, but Ignition continues to support other historian storage options, including external databases. Existing history, reporting dependencies, backup procedures, availability requirements, collection rates, retention settings, and query workload should factor into the decision.

When does active support for Ignition 8.1 end?

Active support for Ignition 8.1 is scheduled to end September 16, 2027, with limited support continuing through September 16, 2029. Organizations still using 8.1 can use that timeline to evaluate their applications and plan a potential transition to Ignition 8.3.

About the Author

Jason Barry is a Controls Engineering Manager for Hallam-ICS. He has spent his career working on process automation systems in a variety of industries including Semiconductor, Chemical, Food and Beverage, Oil and Gas, and Toxic Gas Monitoring. His area of expertise includes Rockwell PLCs, multiple SCADA software, and SQL databases.

Read  My Hallam Story  

About Hallam-ICS

Hallam-ICS is an engineering and automation company that designs MEP systems for facilities and plants, engineers control and automation solutions, and ensures safety and regulatory compliance through arc flash studies, commissioning, and validation. Our offices are located in Massachusetts, Connecticut, New York, Vermont and North Carolina  and Texas and our projects take us world-wide.