Home
/
Case studies
/
From fragile scripts to 16 Ignition modules: the Plantformance product line
Ignition modules

From fragile scripts to 16 Ignition modules: the Plantformance product line

Client
Plantformance
Industry
Cross-industry
16

Ignition modules developed internally

Plantformance used scripting to extend Ignition until the scripts became hard to maintain and secure across its fleet. It started building its own Ignition modules instead and has developed 16 internally, including 5 commercial modules: Gateway Analyzer, Security Auditor, Devices Mirroring, Ultra Charts, and Host Agent, with 6 more in the pipeline.

Key results

  • 16 Ignition modules developed internally
  • 5 commercial Ignition modules
  • 6 more modules in the pipeline

The problem

Standard Inductive Automation Ignition deployments had real gaps in functionality, diagnostics, security, and peripheral integration. Closing them meant heavy custom scripting or costly third-party tools. For a team running many gateways for many clients, neither option scales. Scripts multiply, each one needs care, and the limits of Jython keep coming back. Every new client and every new feature made the problem bigger.

What it looked like before

Plantformance used scripting to add features to Ignition. As the fleet grew, those scripts became hard to maintain, secure, and manage.

How Plantformance solved it

Plantformance started building its own Ignition modules, first to manage servers and then to deliver functionality. It added module development on behalf of clients. Then it launched a dedicated product line of 5 commercial Ignition modules: Plantformance Gateway Analyzer, Security Auditor, Devices Mirroring, Ultra Charts, and Host Agent, with 6 more in the pipeline. By the end of 2026, Plantformance had developed 16 Ignition modules internally. Modules replaced the scripts on managed gateways.

What changed

A modern development pipeline, an ITIL service desk, and 24/7 support are in place, and scripting has practically disappeared from Plantformance-managed gateways.

Results

  • No more piles of scripts or Jython limitations to work around
  • Countless hours of troubleshooting saved by replacing scripts with modules
  • 5 commercial Ignition modules on the market, 6 more in the pipeline
  • 16 Ignition modules developed internally
  • Scripting has practically disappeared from Plantformance-managed gateways

Plantformance products and services used

Gateway Analyzer, Security Auditor, Devices Mirroring, Ultra Charts, Host Agent, Professional Services

Frequently asked questions

Why replace Ignition scripts with modules?

As its fleet grew, Plantformance found scripts hard to maintain, secure, and manage, with Jython limits that kept coming back. Replacing them with modules saved countless hours of troubleshooting, and scripting has practically disappeared from Plantformance-managed gateways.

Which commercial Ignition modules does Plantformance sell?

Plantformance has 5 commercial Ignition modules on the market: Gateway Analyzer, Security Auditor, Devices Mirroring, Ultra Charts, and Host Agent. 6 more are in the pipeline, and Plantformance has developed 16 Ignition modules internally.

Does Plantformance build custom Ignition modules for clients?

Yes. After building modules to manage its own servers and deliver functionality, Plantformance added module development on behalf of clients, backed by a modern development pipeline, an ITIL service desk, and 24/7 support.

Related Ignition case studies

Planning a similar project? Talk to a Plantformance Ignition engineer or browse all 37 Ignition case studies.

Planning a similar Ignition project?

Tell us about your plants and your Ignition setup. A Plantformance engineer will show you how a project like this would work for you.