Honeywell has spent the past couple of years reorganizing its industrial businesses under an “Industrial Automation” banner, and the MES conversation is now part of that story in a way it wasn’t before. Through Honeywell Forge — its industrial software and analytics platform — and a string of manufacturing operations management (MOM) partnerships, Honeywell is showing up in more MES vendor shortlists, sitting alongside Siemens Opcenter, Rockwell/Plex, and GE Vernova’s Proficy in evaluations that used to be a three-horse race. That’s a real shift, and it’s landing right as plants work through summer and fall renewal cycles and start planning 2026 capital and software budgets.
For plant IT and manufacturing engineering teams, the practical question isn’t whether Honeywell is a “real” MES vendor. It’s where the pitch is backed by two decades of installed automation base, and where it’s asking you to be the reference customer. Those are very different risk profiles, and they call for different diligence.
What’s actually changed
Honeywell’s MES ambitions aren’t new — it has offered production management and operations software for years, largely tied to its Experion distributed control system (DCS) and process-industry customer base in oil and gas, chemicals, and refining. What’s changed is the packaging and the go-to-market. Forge is now positioned as the connective layer that pulls together historian data, APM (asset performance management), and MOM/MES functionality into a single cloud-and-edge platform, and Honeywell has been announcing partnerships with software providers to fill out functionality it doesn’t build natively — things like scheduling, quality management, or discrete-manufacturing execution capabilities that sit outside its traditional process-industry comfort zone.
That partnership strategy is worth naming plainly: it means a Honeywell MES pitch today may involve more than one vendor’s code running under the Forge umbrella. That’s not disqualifying — plenty of MES stacks are assembled from best-of-breed components — but it changes what you need to ask about support, upgrade paths, and who owns a break/fix ticket when something in the integration layer misbehaves.
Where the pitch is genuinely strong
If you’re already running Experion as your DCS, or you have Honeywell instrumentation and PlantCloud infrastructure on site, the integration argument is legitimate. Native OPC UA and historian-level connectivity between a DCS and an MES layer from the same vendor removes a class of integration risk you’d otherwise carry with a third-party MES talking to Experion through a middleware layer. Tag mapping, alarm context, batch data lineage tied back to ISA-88 recipe structures — these are areas where same-vendor stacks tend to have fewer surprises, because the vendor has already solved the handshake internally rather than leaving it to a systems integrator.
This is Honeywell’s real home turf: continuous and batch process industries where it has decades of DCS deployment experience. If your plant fits that profile, the case for at least evaluating Honeywell’s MES offering is sound, not just marketing.
Where you should slow down
The further you get from that process-industry, Experion-centric footprint, the more the pitch shifts from “extension of what you already run” to “adopt something new.” Discrete manufacturing, complex multi-plant scheduling, and heavy MOM functionality like advanced quality management or genealogy tracking are areas where Honeywell has been building through partnership and acquisition rather than decades of in-house depth. That’s a legitimate way to build a platform, but it means the reference base is thinner, and you should expect fewer peer plants in your specific vertical to call for a candid conversation.
A checklist before you commit a pilot
Given that plants only get so many shutdown windows a year, and a poorly scoped MES pilot can burn one without producing a usable answer, a few questions are worth insisting on before signing a proof-of-concept statement of work:
- Integration depth, not integration claims. Ask for a live demonstration of the specific data path from your DCS or historian into the MES layer — not a slide, an actual tag flowing through in a test environment. If your site runs Experion or PlantCloud today, this should be straightforward for Honeywell to show. If it isn’t, that tells you something.
- Reference sites in your vertical, with contact access. Don’t accept a logo slide. Ask to speak with a plant running a similar process type, similar batch/continuous mix, and similar scale. If Honeywell can produce that easily in refining or chemicals but struggles in discrete or life sciences, take that as a signal about where the platform is mature versus where it’s still proving itself.
- Who owns what in the partner stack. If the MES functionality is delivered through a named software partner under the Forge umbrella, get in writing who handles support escalation, who patches what, and how upgrades are coordinated across the two vendors’ release cycles.
- Exit and data portability terms. Standard MES diligence, but worth restating: know how your production data, recipes, and configuration come out if you don’t renew, and in what format.
- Pilot scope tied to a measurable outcome, not a demo. Insist the SOW defines a specific production scenario — a line, a product family, a defined set of work orders — with success criteria agreed in advance, rather than an open-ended “let’s see how it goes” engagement that quietly expands.
- Shutdown window contingency. If the pilot requires any DCS-side configuration change or historian tap that needs a maintenance window, get that identified and scheduled before you agree to a start date, not after.
The bigger picture for this budget cycle
Honeywell entering more MES bake-offs is good for buyers in the general sense that more credible competition tends to sharpen pricing and service commitments across the field, including from Siemens, Rockwell, and GE Vernova. But “more credible competition” doesn’t mean “equally mature everywhere.” The right move this renewal cycle is to treat Honeywell’s MES pitch as strong by default if you’re deep in its process-automation ecosystem already, and as an early-adopter bet — worth evaluating, not worth rushing — if your plant runs discrete production or a mixed environment where Honeywell’s MOM partnerships are still relatively new. Ask for the reference calls before you ask for the pilot. The answer to that request will tell you more than anything in the sales deck.
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.
