Ask five plant managers what MES they run and at least one will say “Ignition” without blinking, even though Ignition is, strictly speaking, a SCADA and industrial application platform, not an MES. That answer is more accurate than it sounds. With Sepasoft’s MES modules layered on top — Statistical Process Control, Downtime, OEE, and Track & Trace — Inductive Automation’s platform has become a genuine way for manufacturers to run manufacturing execution functions without ever signing an MES contract in the traditional sense. The question worth asking isn’t whether this approach is legitimate. It clearly is, for a lot of plants. The question is how you know when yours has outgrown it.
What you’re actually buying
Ignition is built by Inductive Automation and licensed differently than almost anything else in this space: unlimited clients, unlimited screens, and unlimited tags on a given server, with pricing structured around the server and the modules you activate rather than per-seat counts. Sepasoft builds its MES modules on top of that same Ignition core, using the same tag structure, the same Vision or Perspective visualization layer, and the same Ignition Gateway architecture. The practical effect is that a controls engineer who already knows Ignition can add SPC, downtime tracking, and basic genealogy without learning a second platform, integrating a second historian, or standing up a separate application server.
That’s the real appeal, and it’s not a marketing story — it’s an architectural fact. There’s no data integration project between “the SCADA system” and “the MES system” because they’re the same system. For a plant that’s tired of stitching together a historian, an HMI package, and a bolted-on reporting tool from three different vendors, that consolidation is worth real money and real engineering time, even if none of us are going to put a number on it here.
Where it’s genuinely enough
For a single site, or a handful of sites running similar equipment and similar products, Ignition plus Sepasoft can cover a surprising amount of ground: OEE and downtime reasoning, SPC charting against control limits, basic lot and batch tracking, work-order execution against a scheduling system, and enough genealogy to answer “what else came out of that lot” when quality asks. If your regulatory burden is light — you’re not producing under FDA 21 CFR Part 11 electronic-record requirements, you don’t need a validated system lifecycle, and your customers aren’t demanding a formal DHR or eBR — this stack can run real production for years without anyone missing a “real” MES.
It’s also a strong fit for plants where the controls team, not a dedicated IT/OT applications group, owns the system. Ignition’s tag-based architecture and Jython scripting are approachable to someone who came up through PLCs and HMIs. A purpose-built MES typically assumes a more formal implementation team, a defined configuration methodology, and often a systems integrator or the vendor’s own services group involved for anything beyond the out-of-box workflow. If you don’t have that team and don’t want to pay for it, staying inside Ignition’s world keeps the system in the hands of people who already understand it.
The tells that you’ve outgrown it
The failure mode here isn’t that Ignition breaks. It’s that the plant keeps extending it, one Jython script and one custom UDT at a time, until what’s running production is architecturally a MES but was never designed as one — and nobody documented the design decisions along the way. A few specific signals are worth watching for.
- Multi-site master data management. Once you have more than a couple of sites that need a shared item master, shared routings, and synchronized recipe or BOM changes, you’re doing MDM by hand — replicating tag structures and UDTs across gateways and hoping nothing drifts. Purpose-built MES platforms like Opcenter or Plex are built around centralized master data with site-level overrides as the design center, not a workaround.
- Genealogy that goes deep and branches. Simple lot tracking (this finished good came from these raw material lots) is well within Sepasoft’s Track & Trace capability. Complex genealogy — assemblies of assemblies, co-products and by-products, rework loops that merge and split lots, full where-used and where-came-from traversal across dozens of process steps — starts to strain a system built on Ignition’s tag database rather than a relational data model designed explicitly for genealogy queries.
- Regulated batch records. If you need electronic batch records with enforced execution sequencing, exception and deviation workflows, electronic signatures with full audit trail under Part 11, and a validated software lifecycle, you’re now in territory that dedicated MES platforms, particularly those built for life sciences and regulated food and beverage, have spent years hardening. Building that compliance layer yourself on Ignition is possible; it is also where a lot of well-intentioned custom builds quietly become the thing an FDA inspector or internal quality audit flags as insufficiently controlled.
- Scheduling and finite capacity planning complexity. Basic work-order execution is fine in Ignition. Constraint-based scheduling across shared resources, changeover optimization, and integrated APS logic is a different discipline, and it’s a place where platforms like Plex or Critical Manufacturing bring purpose-built engines rather than custom scripts.
How the alternatives actually differ in approach
It helps to be precise about what “graduating” means, because Opcenter (Siemens), Plex (Rockwell Automation), and Critical Manufacturing are not interchangeable with each other, let alone with Ignition. Opcenter tends to show up in complex discrete and process manufacturing with deep integration into Siemens’ broader PLM and automation portfolio. Plex is cloud-native and ERP-adjacent, appealing to manufacturers who want MES, quality, and supply chain functions in one hosted system. Critical Manufacturing has particular strength in high-complexity, highly regulated electronics and life sciences environments where full traceability and validation are non-negotiable. None of them share Ignition’s licensing model — they’re generally sold on named modules, sites, or user tiers rather than an unlimited-connection server license, and they generally arrive with a more structured (and typically longer, professionally-led) implementation methodology.
That’s the real tradeoff, not just a features checklist. Ignition trades a more prescriptive, vendor-guided implementation for flexibility and in-house control. Purpose-built MES trades some of that flexibility for a data model, compliance scaffolding, and multi-site architecture that were designed for exactly the problems above from day one, rather than adapted to them later.
A framework, not a verdict
Before your 2026 renewal cycle forces the question, run your own system through three tests: Can a new engineer understand your genealogy logic without you explaining the custom scripts? Could you pass a serious quality audit on your batch records today? Would adding a fourth or fifth plant mean copying gateway configuration by hand? Two “no” answers means Ignition and Sepasoft are still doing their job. Three “no” answers is the signal to start scoping a real MES evaluation — not because the platform failed, but because the plant grew past the problem it was built to solve.
This article was written with the assistance of artificial intelligence. While we aim for accuracy, the information may be incomplete, out of date, or incorrect, and should be independently verified before you rely on it for any decision. It is provided for general information only and does not constitute professional advice.
