Do aerospace manufacturers need to replace MES to implement a connected operations platform?

No. Most aerospace manufacturers do not need to replace MES to implement a connected operations platform.

In regulated, long-lifecycle environments, full MES replacement is often the riskier option. It can trigger substantial validation work, interface redesign, retraining, downtime exposure, and requalification concerns across execution, quality, genealogy, and reporting processes. In many plants, the practical approach is coexistence: keep the MES that already runs dispatch, transactions, equipment interfaces, or recordkeeping, and add a connected operations layer around it.

That said, this depends on what the current MES actually does, how configurable it is, and how cleanly it can exchange data with surrounding systems. A connected operations platform is not a shortcut around poor master data, weak integration discipline, or fragmented process ownership.

When MES replacement is usually not required

A replacement is often unnecessary when the existing MES can still reliably handle core execution responsibilities and expose the needed data or events. Common examples include:

• The MES remains the system of record for work order execution, traceability, genealogy, or electronic history.

• The connected operations platform adds operator experience, orchestration, workflow guidance, exception handling, analytics, or cross-system visibility.

• ERP, PLM, QMS, and MES each keep their established roles, with the platform coordinating data flows and context between them.

• The plant needs incremental rollout with limited downtime rather than a multi-year replacement program.

This model is common in brownfield aerospace operations because it reduces disruption to validated processes while still addressing real gaps such as disconnected work instructions, delayed status visibility, manual handoffs, and weak exception management.

When MES replacement may still be justified

Sometimes the answer is yes, but usually for specific reasons, not because a connected platform inherently requires it. Replacement may be justified if the current MES is no longer supportable, cannot meet traceability or integration requirements, forces excessive manual workarounds, or blocks critical process changes. Even then, the business case needs to account for more than software functionality.

Typical drivers include:

• Unsupported or obsolete MES architecture

• Inability to support required traceability, genealogy, or electronic record controls

• Integration limitations that make reliable ERP, PLM, QMS, or equipment connectivity impractical

• Excessive customization that prevents upgrades or consistent governance

• High operational dependence on spreadsheets, paper, or duplicate data entry because the MES no longer fits the process

Even in those cases, replacement should not be treated as a simple modernization project. In aerospace, it can become a qualification, validation, and business continuity program with significant execution risk.

What matters more than replacement

The more important question is whether the target architecture can support controlled coexistence across MES, ERP, PLM, QMS, and shop floor systems without losing traceability or introducing conflicting records.

Key dependencies usually include:

• Clear system-of-record boundaries for work orders, routings, quality events, and as-built data

• Reliable integration patterns, not just point-to-point scripts

• Master data alignment across part numbers, revisions, resources, and operations

• Version control for work instructions and process changes

• Validation and change control proportional to the operational and regulatory impact

• A phased deployment plan that avoids forcing every site and process into one cutover

If those basics are weak, replacing MES may simply move the same problems into a new stack.

Practical tradeoff

Keeping the existing MES usually lowers disruption and preserves continuity, but it also means living with some legacy constraints. Replacing MES may promise architectural simplicity later, but often increases near-term risk, cost, and time to value. For most aerospace manufacturers, an integration-first approach is the more realistic starting point, with selective MES replacement only where the current system is a proven blocker.

So the short answer is no: a connected operations platform does not inherently require MES replacement. It requires a workable coexistence strategy, disciplined integration, and enough data and process maturity to support traceable execution across the systems already in place.