Automotive MES: Buy, Build, or Extend What You Have

What Automotive MES Actually Does

A Manufacturing Execution System (MES) sits between two systems every plant already runs. ERP plans production at the scale of days and weeks: what to build, how much, by when. SCADA supervises the equipment below it, collecting tag data from PLCs in real time. MES is the layer in between, taking the ERP plan, dispatching it as work orders, and tracking execution as it happens.

From Monolithic MES to Modular MES

For most of MES's history, the entire stack shipped as one tightly coupled platform (hence the term ‘monolith’). Changing any piece meant touching the whole system: a vendor engagement and months of lead time for custom configurations.

That model is breaking down for the same reason why automotive plants are hard to standardize in the first place. Every plant, product line, and OEM contract has its own quality requirements, downtime taxonomy, and mix of legacy equipment. The industry's response has been a shift toward modular, composable MES architecture that breaks routing, quality, genealogy, and downtime tracking into pieces that can be built or replaced independently. Extending an existing MES, the third option here, is that same shift applied to a plant that already has a working MES and no interest in replacing it just to get modularity.

Why Automotive Manufacturing Makes MES Decisions Harder

Automotive manufacturing carries more accumulated technical debt than most manufacturing environments, and it's structural, not incidental. Equipment spans decades, so a single line can mix PLCs from different vendors and eras never built to talk to each other. Plants added through M&A bring their own MES instances, ERP configurations, and naming conventions with them. Every integration is custom and manual, usually an integrator writing point-to-point code for one connection at one plant that nobody else can safely touch, and when that engineer leaves, it's a real risk.

None of this is unique to any specific manufacturer. It's the normal condition of any automotive manufacturer or supplier, and it's exactly why a corporate rollout can't assume one MES configuration fits every site.

The Real Decision: Buy, Build, or Extend

When Buying an Off-the-Shelf MES Is Right

An off-the-shelf MES is the fastest path to solid routing, dispatch, and out-of-box error-proofing. It's right when a plant runs a standardized process, has no system yet, and needs core execution running quickly. Cost varies a lot by architecture and market: on-premise systems typically run {% raw %}$120,000 to$600,000{% endraw %} upfront, plus around 20% of license cost annually in maintenance, with six to eighteen months before going live, while cloud-native platforms start in the low thousands per month (Symestic, 2026). In the UK, a cloud MES typically runs £6,000 to £15,000 a year with a 90-day go-live, against £75,000 to £150,000 to implement on-premise and three-year totals of £120,000 to £450,000 (TotalControlPro, 2025).

There are plenty of strong MES platforms on the market, from comprehensive systems like Siemens Opcenter Execution and Rockwell's Plex, to composable, build-your-own-app platforms like Tulip. Manufacturers running these don't need to rip them out to close the gaps this blog covers. In practice, manufacturers have implemented FlowFuse alongside deployments like these to extend their functionality, which is what the next option is about.

When Building a Custom MES Is Right

Building makes sense when a process is differentiated enough that no off-the-shelf platform fits it, and the organization has the capacity to own it long term, not just ship it once. The trade-off is real: a custom build competes with the IT roadmap for a year or more, and every future change depends on that same team staying in place. Hexagon Manufacturing Intelligence took this route, building its own Smart Factory Manager rather than buying off-the-shelf, after concluding the fit and long-term ownership were worth the investment (IndustryWeek, 2025).

When Extending Your Existing MES Is The Right Move

Extending is right when the core MES already works, and the actual gaps are plant-specific: a quality gate that enforces a specific control plan, a genealogy structure that satisfies a specific OEM's safe launch requirements, a downtime taxonomy that matches how a plant fails. Those are the pieces that get patched together in scripts and spreadsheets when nobody builds them properly, and what a modular extension layer standardizes.

This is where FlowFuse fits, and it's worth being direct: FlowFuse is not an MES, and it doesn't compete with the one already running the plant. It's an application layer that connects to MES, ERP, and SCADA systems already in place and makes them more configurable at the plant level.

It's also worth naming a fact that shapes this whole decision: to our knowledge, no vendor sells an MES built and sold specifically as an automotive-only product. MES platforms are horizontal, enterprise-wide systems used across automotive, pharma, food and beverage, and electronics alike, not vertical-specific products with a separate automotive SKU. That's why customizing your existing MES is often the more practical path:

• Capturing torque measurements across the chassis line with poka-yoke checks that stop the station before a bad fastener moves downstream, then standardizing that application for other lines like powertrain.
• Measuring operator productivity at one plant and rolling that application out across all sites so data flows into a standard dashboard without manual reconciliation.
• Automating genealogy capture, binding component lots to serial numbers, for one vehicle program, then extending that logic to additional programs or plants instead of running a custom integration project each time.
• Adding real-time quality gate enforcement, control plan limits with automatic hold-and-containment, to a line where the base MES configuration lacks it, then standardizing that pattern across other lines and plants building for the same OEM, even though each site submits its own PPAP per part number.

Where the Gaps Are, and What Extension Needs to Cover

Routing and dispatch are the core of what a packaged MES sells, and an extension layer doesn't need to touch that logic. FlowFuse supports IT/OT connectivity that layers on top of existing MES routing, adding what a packaged system leaves as a gap.

The gaps themselves cluster into two categories: quality gate enforcement (capturing a measurement, holding the station when a control-plan rule trips, routing the part to containment, and logging it against the serial number) and standardization across sites (a shared downtime taxonomy and genealogy captured at the point of consumption, so a reason code or a build record means the same thing at every plant). Unplanned downtime alone costs industrial manufacturers an estimated $50 billion annually (Forbes Technology Council, 2022), and without standardization, a recall investigation ends up tracing the same defect to a shift's production at one plant and specific serial numbers at another.

Final Thoughts

So where do we go from here? It honestly depends on how fast you want to see results and the availability of your existing resources.

If the core MES is good, a manufacturer can use FlowFuse to extend its existing capabilities rather than replace it, closing the quality gate, genealogy, and downtime gaps most vendors leave for each plant to solve on its own. FlowFuse gives IT and operations teams a way to build custom applications, starting small and expanding from there, instead of reconfiguring the same enforcement at every site. It's part of FlowFuse's broader automotive manufacturing solutions, used by 30+ automotive manufacturers in 20 countries.

Sources

• Forbes Technology Council. (2022). "Unplanned downtime costs more than you think."
• Symestic. (2026). "MES System Prices 2026: Cost Comparison, TCO & ROI."
• TotalControlPro. (2025). "The End of the Production Black Box: How Much Does a Modern MES Really Cost?"
• IndustryWeek. (2025). "Build or Buy Your MES? Lessons from Hexagon Manufacturing Intelligence."