MES Isn’t the Problem. How We Implement It Is

Most manufacturers don’t hesitate to invest in manufacturing execution system (MES) functionality because they doubt its value. They hesitate because they’ve seen how it often plays out. Long timelines, large budgets, extended design phases, and results that arrive much later than expected.

At Actemium Avanceon, we see this hesitation often. It’s not a lack of interest in MES, but uncertainty around how to approach it in a way that actually works.

In response, the industry has started to shift. There is more discussion around modular approaches, starting small, and reducing risk. Those are steps in the right direction, but they do not fully address the underlying issue.

Too often, MES is still approached as something that needs to be fully designed before it delivers any value.

Rethinking the Starting Point

The core challenges in manufacturing have not fundamentally changed. They still come down to a few familiar areas:

• Scrap
• Downtime
• Inconsistent performance
• Lack of visibility

What has changed is the ability to address those challenges differently.

Today’s technology makes it possible to take a more incremental approach. Instead of committing to a full system upfront, organizations can begin solving specific problems and expand from there.

Stop Treating MES Like a One-Time Decision

Historically, MES was treated as a single, large decision. A platform was selected, requirements were defined, and the goal was to design a complete solution before roll-out.

That model often meant:

• Significant upfront investment
• Long periods before measurable return
• High organizational risk

And once you started, you were locked in. Stopping halfway meant failure. That model does not hold anymore.

Build the System While You’re Using It

If we were starting from scratch today, the goal wouldn’t be to “implement MES” in the traditional sense. It would be to build it while it is already delivering value.

That starts with a simple shift in approach:

• Begin with a specific problem, not a platform
• Deliver something usable in weeks, not months
• Expand only once value has been proven

Take scrap as an example. Instead of designing a full MES architecture upfront, teams can start by pulling data from existing sources, such as PLCs, historians, or even a current MES, and structuring it into something usable.

Within a short timeframe, that data can be turned into a clear, actionable view for operations. At that point, the system is no longer something being planned. It is already in use and already delivering value.

Replace Systems When It Makes Sense — Not All at Once

This is where most approaches break down. Organizations tend to fall into one of two extremes:

1. Rip-and-Replace

“We need to get rid of everything and start fresh.”

• High risk
• High disruption
• Rarely realistic

2. Layer Forever

“Just sit on top of everything you already have.”

• No architectural progress
• Technical debt accumulates
• You never actually modernize

Neither works.

The Right Approach: Replace Systems with Intent

You don’t replace systems because they’re old. You replace them because:

• They don’t fit the future architecture
• They limit your ability to move faster
• They can’t integrate cleanly
• Or they no longer create value

If your historian is capturing clean, reliable data and integrates well into the broader architecture, there may be no reason to replace it.

In other cases, systems begin to create limitations. They may restrict access to data, slow down decision-making, or make integration more difficult.

Then it becomes a candidate for replacement, on your timeline, tied to value.

MES Becomes the Backbone, Not Just a Layer

As these changes take place, MES begins to play a different role.

It is no longer just a layer on top of existing systems. It becomes part of a broader operational backbone that connects data across the organization, from control systems to enterprise applications.

This backbone provides:

• A consistent structure for how data is organized and accessed
• A foundation for faster development of applications and insights
• A clearer link between operations and business systems

At the beginning, it works alongside existing systems. Over time, as improvements are made and new capabilities are introduced, it can begin to replace them in a more structured and intentional way.

Where This Approach Succeeds or Fails

You can have the best architecture in the world, but it doesn’t matter if the operator experience gets worse.

The goal is not to give operators another tool. If MES makes work more complicated, adoption will struggle. If it simplifies how information is accessed and used, it becomes part of daily operations.

The focus should be on:

• Presenting only the information that matters
• Reducing friction in decision-making
• Aligning with how operators already work

In some cases, that means improving what is already in place. In others, it may involve introducing new tools that are easier to use. If we’re adding complexity, we’re doing it wrong.

You Should Be Able to Stop and Still Win

This is the biggest shift.

Each phase should deliver value on its own. Solving a scrap issue should lead to measurable improvement. Increasing visibility into downtime should have a direct operational impact. Adding scheduling should build on what is already in place.

The key difference is that at any point, the effort can pause without losing what has already been achieved.

Instead of being left with a partially implemented system, organizations retain working capabilities that continue to support operations. The value is already there.

That was not true with traditional MES approaches, where stopping early often meant the investment had not yet paid off.

From Project to Ongoing Capability

The idea of a fully “completed” MES implementation is becoming less relevant.

What organizations are building is not a fixed system, but an evolving capability. One that grows alongside the business, adapts to new requirements, and continues to deliver value over time.

Rather than waiting for a final go-live, improvement becomes continuous.

A Practical Path Forward

The industry does not need another message about digital transformation. What it needs is a more practical way to move forward.

Manufacturers can start small, move quickly, and reduce risk while still building toward a modern, scalable architecture.

Not by replacing everything at once, but by making targeted decisions over time, based on what delivers the most value.

From our experience at Actemium Avanceon, the most successful MES efforts follow this pattern, starting small, delivering value early, and expanding based on what works.