Honeywell has spent the past couple of years reshaping its industrial software business, folding acquisitions in automation software, connected worker tooling, and industrial AI into the Honeywell Forge umbrella while realigning its broader automation organization around software-defined outcomes rather than hardware and services alone. The result is a portfolio that, on paper, now touches a lot of the same ground as traditional MES suites: production visibility, quality workflows, asset performance, workforce tools, and increasingly, AI-driven optimization layered on top.
What hasn’t changed is where Honeywell shows up in practice. Ask a plant IT director or a controls engineer running an MES RFP to name their comparison set, and you’ll almost always hear Siemens Opcenter, Rockwell’s Plex or FactoryTalk stack, AVEVA, or one of the ISA-95-native specialists like Critical Manufacturing or iTAC. Honeywell rarely makes that list — not because the technology is irrelevant, but because most buyers don’t have a clear picture of what Honeywell is actually selling at the execution layer versus what it’s selling as an optimization and analytics layer sitting on top of someone else’s execution system.
What Honeywell Is Actually Assembling
Forge is best understood as an industrial software and AI platform, not a single product. It aggregates data from OT sources, historians, and enterprise systems, then applies analytics and increasingly generative-AI-assisted workflows for things like performance monitoring, predictive maintenance, and cybersecurity posture. Layered around Forge, Honeywell has been acquiring and integrating pieces that fill in adjacent capability: connected worker platforms for frontline task management and digital work instructions, automation software assets that strengthen its control and asset-management story, and AI tooling aimed at things like autonomous operations and root-cause analysis.
That’s a real and growing footprint. It’s also a fundamentally different footprint than what a classical MES provides. A true MES, in the ISA-95 sense, sits at Level 3 — it owns work order dispatch, in-process genealogy, electronic batch records, real-time scheduling against the plant floor, and the transactional system of record for what actually happened during production. Forge, and most of what sits under it, is built to consume data from that layer and add intelligence on top — Level 3-to-4 analytics and optimization, not the Level 3 execution backbone itself.
That distinction sounds academic until you’re the one who has to explain to an auditor where your genealogy record actually lives.
The Overlap Is Real But Uneven
Honeywell’s connected worker and quality-adjacent tools genuinely compete with point solutions in the MES-adjacent space — digital work instructions, andon-style issue escalation, some forms of SPC. Its asset performance and predictive maintenance capability competes credibly with EAM and APM vendors. Its AI layer competes with the analytics add-ons that Siemens, Rockwell, and AVEVA all now bundle into their own platforms.
Where the overlap gets thinner is exactly where MES buyers spend most of their evaluation time: transactional execution. Work order release and dispatch tied to ERP. Electronic batch records with regulatory-grade audit trails. Material genealogy that can survive an FDA or customer quality audit. Real-time scheduling that reacts to a line-down event in seconds, not through a downstream analytics refresh. Honeywell’s own process control and DCS heritage (through its process solutions business) gives it deep credibility in continuous and batch process environments, and that shouldn’t be dismissed — but credibility in process control isn’t the same as owning the execution-layer system of record that ties shop floor transactions to enterprise business processes.
A Practical Checklist Before You Put Honeywell on the Shortlist
If Honeywell shows up in a vendor conversation — or if your incumbent Honeywell automation footprint makes someone in procurement ask “why not just extend what we already have” — work through these questions before scoping happens for you:
- Who owns the historian? If you’re already on a Honeywell historian (PHD or similar) or a Honeywell-native DCS, ask exactly what Forge adds versus what still requires a separate execution system to write transactional state back to. Data visibility is not execution.
- Where does the ISA-95 Level 3 logic actually run? Ask the vendor, point-blank, to show you where work order dispatch, routing, and genealogy live in their architecture — not where the dashboard lives. If the answer routes back to “your existing MES” or “your ERP,” you’re evaluating an analytics layer, not an MES.
- Is this a point solution wearing a platform’s clothing? Connected worker and AI-driven insights are legitimately valuable. They are not, by themselves, a replacement for execution software. Make the vendor draw the line explicitly.
- What’s the integration burden to your MES/ERP boundary? Any Forge deployment sitting alongside a real MES needs a clean, documented interface — ideally via standard means like OPC UA or MQTT Sparkplug B for OT data, and defined B2MML or equivalent messaging for ISA-95 Level 3/4 handoffs. Vague answers here are a red flag regardless of vendor.
- Does your process type favor Honeywell’s process control heritage? Continuous and batch process plants with heavy DCS investment may get more genuine synergy from Honeywell’s stack than a discrete manufacturer bolting Forge onto a line-based operation. Fit varies by process type more than most vendor pitches admit.
- Who’s accountable for the audit trail? In regulated environments, get an explicit answer on where the validated, auditable record of production lives — and whether that system has the qualification history and change-control rigor your quality team already trusts.
What to Watch
Honeywell’s acquisition pace in software and AI suggests the company is trying to close the execution-layer gap over time rather than staying purely in the optimization tier. Buyers should watch for two things: whether Honeywell articulates a clear, ISA-95-mapped execution offering rather than a bundle of analytics and connected-worker tools marketed under one brand, and whether independent system integrators — the ones who actually implement MES day to day — start including Honeywell in bake-offs rather than treating it as an adjacent automation vendor.
Until that happens, the honest read for most discrete and hybrid manufacturers is that Honeywell belongs in the conversation about plant analytics, connected worker tools, and AI-assisted operations — and deserves real evaluation there. It doesn’t yet belong in the conversation as a drop-in MES replacement, and any RFP response that implies otherwise deserves the same scrutiny you’d give any vendor overselling scope.
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.
