Every few years, SCADA vendors get ambitious. They look at the layer above them — the world of work orders, genealogy, OEE, and electronic batch records — and decide that layer belongs closer to the plant floor than the enterprise stack. Inductive Automation has been doing this deliberately for years through its Ignition platform, and the release of Ignition 8.3 has sharpened a question that’s been simmering on practitioner forums and around the edges of ICC for a while: if you can build most of MES natively on top of your SCADA system, why buy a separate MES platform at all?
It’s a fair question. It’s also one that has a real answer, and the answer is “it depends on things you can actually check before you commit budget.”
What Ignition 8.3 and Sepasoft actually are
Ignition is Inductive Automation’s SCADA and industrial application platform, built on a tag-based architecture with a web-deployed client model and a module system that lets you add capability without re-platforming. Sepasoft, which Inductive Automation acquired, publishes MES modules — Track & Trace, OEE Downtime, SPC Quality, and related components — that plug directly into Ignition’s runtime and use the same tag structure, database connections, and Perspective/Vision visualization layer as the SCADA system itself.
That’s the pitch: one platform, one licensing relationship, one team maintaining it, MES functionality living in the same environment as your alarms and trends instead of in a separate application talking to Ignition over OPC UA or a message bus.
Ignition 8.3 doesn’t reinvent that model, but it matures it — a more current module framework, continued investment in Perspective as the primary web-based visualization layer, and the kind of incremental platform hardening that makes the “do more in Ignition” argument easier to make to a plant manager who doesn’t want to manage three vendor relationships.
Where the native-MES approach genuinely earns its keep
For a single site, or a tight multi-site footprint with a common architecture, Ignition-plus-Sepasoft is a legitimately strong option, and in our assessment it’s the right call more often than MES traditionalists like to admit. A few reasons:
- One data model, no reconciliation tax. When SCADA and MES share the same tag namespace and historian, you skip the perpetual argument about whose number is right when a dedicated MES and a separate SCADA disagree about a downtime event.
- Licensing that scales with your footprint, not a headcount-driven enterprise contract. Ignition’s server-based licensing model (rather than per-client or per-tag in the way some legacy SCADA products charge) tends to make expansion less punishing than adding named users or per-seat MES licenses does elsewhere. This matters more the more workstations, kiosks, and operator HMIs you have.
- Faster time to a working OEE and downtime picture. Because the module lives inside the environment your controls engineers already know, standing up basic MES functions — downtime tracking, changeover capture, simple genealogy — is often meaningfully faster than a first MES implementation project, where integration and workflow design eat most of the calendar.
- Smaller team, one throat to choke. A controls-heavy plant IT team can own the whole stack without hiring MES specialists or engaging a systems integrator that only does one platform.
If your plant is discrete or light-process manufacturing, single-site or a handful of similar sites, and your MES needs are mostly OEE, downtime, basic genealogy, and quality data capture, this is where SCADA-native MES modules stop looking like a compromise and start looking like the obviously correct architecture.
Where the gap with dedicated MES still shows up
The trouble starts when you ask this stack to do things dedicated MES platforms were built around from day one.
Regulated-industry validation overhead
In pharma, medical device, and other GxP environments, MES isn’t just a data system — it’s a validated system, with electronic batch records, electronic signatures under 21 CFR Part 11, and change control that has to survive an audit. Platforms like Opcenter or Critical Manufacturing were designed around that reality, with validation documentation, audit trail structures, and workflow engines built for it. You can build compliant workflows on Ignition and Sepasoft, and some validated environments do, but you’re assembling the validation package yourself rather than buying into a framework the vendor already built and other regulated customers have already tested. That’s a real cost difference in effort, even if no number attached to it would be honest.
Multi-site standardization at scale
A handful of similar plants running Ignition-plus-Sepasoft is manageable. Twenty or thirty plants across different countries, different ERP instances, and different levels of local IT maturity is a different problem — one where a centrally deployed, centrally versioned MES with a global master data model, like Plex or Opcenter, has genuine architectural advantages. Ignition’s project-based deployment model can absolutely support multi-site rollouts, and Inductive Automation has continued to invest in tooling for that, but the governance discipline required to keep dozens of Ignition/Sepasoft instances consistent is a real, ongoing organizational cost that’s easy to underestimate during a pilot at one friendly site.
The integration debt nobody budgets for
This is the one that catches teams off guard. SCADA vendors expanding upward into MES territory inherit a strength — proximity to the equipment — and a weakness: they’re generally not where your ERP, PLM, or quality management system integration expertise already lives. A dedicated MES vendor has spent years building certified connectors and reference architectures for SAP, Oracle, and the major PLM suites. Building the same integrations on top of Ignition is very doable using its scripting environment, web service modules, and message queuing options, but it’s custom work your team owns and maintains, not a supported connector. Every SCADA-native MES buildout should price in that ongoing integration maintenance as a real line item, not an afterthought discovered during the first ERP upgrade.
A decision framework, not a verdict
Ask these questions before you pick a lane:
- Are you single-site or a few structurally similar sites, or are you standardizing across a large, heterogeneous multi-plant network?
- Is any part of your production regulated in a way that requires validated electronic records and formal audit trails?
- How deep and how stable are your ERP/PLM integration needs — a handful of transactions, or dense, bidirectional, mission-critical data flow?
- Do you have (or can you build) in-house Ignition/Sepasoft expertise, or does that expertise walk out the door with one key hire?
- Is your MES need mostly shop-floor visibility and OEE, or full production scheduling, complex genealogy, and quality workflow orchestration?
If your answers skew toward single-site, unregulated or lightly regulated, modest integration needs, and a capable in-house controls team, Ignition 8.3 with Sepasoft’s MES modules is a mature, credible, and often more cost-efficient path than standing up a dedicated MES platform. If your answers skew toward regulated, multi-site, and integration-heavy, the dedicated MES platforms haven’t been leapfrogged — they’ve just gotten a more serious challenger to keep them honest on price and deployment speed. For plants budgeting MES spend now, the honest move is to run this checklist against your own footprint rather than trusting whichever camp got to you first at the last trade show.
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.
