Gartner has published a Magic Quadrant for Manufacturing Execution Systems on a roughly annual cadence for years, alongside a companion Critical Capabilities report that scores vendors against specific use cases. The last cycle’s placements are starting to age out right as plant IT teams sit down to build 2027 budget cases this quarter — which means a lot of capital requests circulating right now cite research that’s about to be superseded. That’s not a knock on anyone’s homework. It’s just the nature of an analyst cycle that moves faster than most plants’ actual replatforming timelines.
This is worth pausing on, because MES buying cycles run three to seven years and Gartner’s research cycle runs closer to twelve months. A plant that starts a vendor evaluation using one year’s quadrant can easily be signing a contract under a completely different one. If you’re building a shortlist right now, or defending one to a CFO, you need to know how to read the next MQ as a data point — not as the answer.
What actually tends to move between cycles
Vendor placement on a Magic Quadrant shifts for two very different reasons, and conflating them is the single most common mistake practitioners make. Sometimes a vendor moves because the underlying product changed — new architecture, new deployment model, a genuine capability gap closed. Sometimes a vendor moves because Gartner’s evaluation criteria changed, or because the vendor’s go-to-market narrative got sharper. Both are legitimate reasons for Gartner to adjust a dot on the chart. Only one of them should change your shortlist.
Three areas of the evaluation criteria have been visibly gaining weight across recent cycles, and it’s reasonable to expect that to continue:
- Composability. Analysts increasingly score MES platforms on how cleanly they expose functionality as discrete, orchestrable services — think modular execution, quality, and scheduling capabilities that can be assembled or swapped rather than a single monolithic suite. This tracks with the broader ISA-95-aligned push toward loosely coupled manufacturing architectures instead of one vendor owning the entire stack.
- AI-agent readiness. Expect heavier scrutiny of whether a platform can support agentic workflows — automated root-cause investigation, scheduling recommendations, exception handling — versus vendors simply bolting a chat interface onto existing dashboards. The distinction between “has generative AI features” and “has a data model and event architecture that AI agents can actually act on” is becoming a real evaluation axis, not just marketing copy.
- Cloud and subscription delivery. Gartner has pushed vendors for years toward SaaS and subscription commercial models. Expect continued credit for vendors offering genuine multi-tenant cloud architectures and usage-based licensing, and continued skepticism toward “cloud-washed” on-premise products repackaged with a browser front end.
None of these criteria are new inventions for the next cycle — they’ve been building for several cycles running. What’s likely to change is the weighting, and vendors who under-invested in any of the three could see quadrant movement that has nothing to do with how well their software actually runs a shift.
Reading vendor movement without getting played
When you look at where major MES vendors sit — Siemens Opcenter, Rockwell Automation’s Plex, AVEVA MES, Critical Manufacturing, SAP Digital Manufacturing, and the rest of the field — resist the urge to treat a quadrant change as a verdict. Ask instead: did the product’s actual architecture change, or did the vendor’s briefing deck get better?
A few practical tells. If a vendor jumped in “completeness of vision” but not “ability to execute,” that’s usually a narrative or roadmap story — worth watching, not worth betting a plant on yet. If movement shows up consistently across both the Magic Quadrant and the Critical Capabilities report for your specific use case (discrete manufacturing execution, batch/process execution, or whatever matches your plant), that’s a stronger signal, because the Critical Capabilities scoring is more granular and harder to game with positioning alone. And if a vendor’s quadrant position is stable but its Critical Capabilities score for your specific use case dropped, pay attention — aggregate quadrant position can mask a real regression in the one area you care about.
A scorecard for translating position into a shortlist
The Magic Quadrant is built for a generic buyer that doesn’t exist. Your plant is discrete or process, mid-market or enterprise, single-site or multi-plant standard — and those differences matter more than where a vendor’s dot sits. A practical way to translate the report into your own shortlist:
- Match the use-case scoring, not the quadrant label. Go straight to the Critical Capabilities report and find the use case closest to your plant profile — discrete manufacturing, process/batch, or whichever segmentation Gartner uses that cycle. A vendor buried in the “Niche Players” quadrant overall can still top the use-case ranking that matches your plant.
- Weight architecture over ambition. If composability and cloud delivery matter to your IT roadmap, verify the vendor’s actual deployment options and integration model, not just the analyst’s characterization of them. Ask for a real architecture diagram in the RFP, not a slide.
- Test AI claims against your data reality. Agentic and generative AI features are only as good as the underlying event and transaction data model. A vendor’s AI roadmap is irrelevant if your plant’s data isn’t structured well enough to feed it — that’s an internal readiness question as much as a vendor selection question.
- Separate enterprise fit from mid-market fit. A platform built for multi-plant standardization across a global enterprise carries integration and governance overhead that a single-site or mid-market operation doesn’t need and shouldn’t pay for. Vendor strength in the MQ often reflects enterprise deal volume, which isn’t the same as being the right fit for a smaller footprint.
- Check ISA-95 and interoperability posture directly. Don’t rely on the MQ narrative for this — ask vendors directly how they handle OPC UA connectivity, MQTT Sparkplug B for edge data, and integration with your existing ERP and quality systems. This is where marketing language and real implementation experience diverge fastest.
What to actually do with the next report when it lands
Use the Magic Quadrant to build your longlist and the Critical Capabilities report to cut it down by use case. Then run your own proof-of-concept against your actual data and your actual plant floor, because that’s the step no analyst report replaces. Gartner’s research is genuinely useful for surfacing vendors you might not have considered and for giving procurement a defensible external reference point. It is not a substitute for evaluating whether a platform’s execution model, integration architecture, and total cost of ownership fit the plant you actually run.
If your 2027 budget case leans on this year’s report, plan to revisit it once the next cycle publishes — not to chase every quadrant shuffle, but to confirm the vendors you shortlisted are still moving in a direction that matches where your own architecture is headed. A stale citation in a budget memo is a minor problem. A shortlist built on last cycle’s narrative instead of this cycle’s substance is a much more expensive one.
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.
