Metromotion Controls has been an Ignition Gold Certified System Integrator since 2017. That gives us a reasonably clear view of where the platform is the right choice, where it is one of several good options, and where other platforms serve clients better.
This article is an honest assessment, not a sales pitch for any platform.
The right SCADA platform for a site is the one that best fits the existing infrastructure, the capabilities of the engineering and operations team, and the actual functional requirements of the project. Capability comparisons matter less than fit.
What Ignition does well
Licensing model
A single server licence with no per-tag, per-client, or per-screen fees. For sites with many operator workstations, large tag counts, or multiple displays, the total cost of licensing is significantly lower than alternatives that charge per connection or per client.
Browser-based clients
Perspective, Ignition's modern client module, runs in a web browser and on mobile devices without any client software installation. This makes operator access from tablets, office PCs, and mobile devices straightforward.
IIoT and data integration
Native MQTT support, Unified Namespace (UNS) architecture capability, built-in historian, and connectors to cloud platforms make Ignition well-suited to sites that need plant data connected to business systems, reporting tools, or cloud analytics.
MES and batch modules
Sepasoft MES and Batch and Procedure modules extend Ignition into ISA-88 batch control, OEE tracking, SPC, and recipe management. These are purpose-built modules, not add-ons, and they share the same database and tag structure as the SCADA layer.
Where Ignition is the clear choice
Greenfield projects without legacy SCADA: When there is no existing SCADA infrastructure to replace, Ignition starts with a clean slate and its advantages are available from day one without migration costs.
Multi-site or multi-plant deployments: Ignition's centralised architecture (Ignition Gateway with remote clients) and predictable licensing make it cost-effective for organisations managing multiple sites from a central operations team.
Sites that need plant data connected to business systems: MQTT, UNS, and the Ignition Exchange of pre-built connectors make integration with ERP, MES, and cloud platforms more accessible than on most alternatives.
Food and dairy sites that need MES functionality: Sepasoft's MES modules are mature, well-supported, and tightly integrated with the SCADA layer. For sites that need ISA-88 batch control, OEE, and traceability in one platform, Ignition with Sepasoft is a strong combination.
Where other platforms may be a better fit
Rockwell-heavy sites with existing FactoryTalk infrastructure: Sites with an established FactoryTalk View or FactoryTalk Historian environment, trained operations and engineering teams, and deep Rockwell integration often benefit from staying within the ecosystem. The integration between FactoryTalk and Allen-Bradley PLCs is tight, the diagnostic tools are familiar, and the migration cost from an established system is not trivial.
Sites with existing AVEVA or Citect SCADA with significant customisation: SCADA systems with years of site-specific customisation, reporting, and operator training represent real accumulated value. Replacing them with Ignition needs to be justified by concrete improvement, not platform preference.
Sites with constrained IT infrastructure: Ignition's browser-based clients require a reliable network and server infrastructure. On sites with limited IT support or unstable networks, the traditional thick-client architecture of platforms like FactoryTalk or Citect can be more resilient.
The migration question
When migrating existing SCADA to Ignition is worth it
- The existing platform is end-of-life or approaching end-of-support, and the cost of maintaining it is increasing.
- The site has genuine requirements for IIoT connectivity, mobile access, or MES integration that the existing platform cannot support.
- The existing system has significant technical debt, undocumented graphics, complex custom scripting, no support from the original integrator, that makes it difficult to modify.
- The organisation is adding sites and wants a consistent SCADA platform across them.
Migration from an existing SCADA platform is always a project in itself. The tag migration, graphics rebuild, historian reconnection, and operator retraining represent real cost that needs to be weighed against the benefits of the new platform.
What this means
Ignition is one of the strongest SCADA platforms available and is the platform we use most often on greenfield and major upgrade projects. It is not the right choice in every situation. The right answer depends on what is already on site, what the functional requirements actually are, and whether the migration or new installation cost is justified by the improvements the platform enables. That is a site-specific assessment, and getting it right requires understanding both the platform capabilities and the specific context of the project.