1. 3DS Blog
  2. Brands
  3. DELMIA
  4. How to Evaluate MOM and MES Software: Critical Questions Most RFPs Miss

ManufacturingJuly 15, 2026

How to Evaluate MOM and MES Software: Critical Questions Most RFPs Miss

Most MOM/MES evaluations focus on features. The organizations that make the right choice ask different questions, about architecture, global scalability and operational continuity. Here’s a framework to guide your selection process.
header
AvatarHélène Motycka

Table of contents

Introduction

When a manufacturing organization decides to invest in a Manufacturing Execution System or a broader Manufacturing Operations Management platform, the stakes are high, and the RFP process rarely reflects that. Whether your organization still uses the term “MES” or has moved toward “MOM,” the underlying challenge is the same: selecting a system that will support your operations reliably, at scale, for the next decade. Most evaluation frameworks default to a feature checklist: production scheduling, quality management, traceability, OEE reporting. Vendors check every box. The shortlist looks identical. And then, months after go-live, the gaps appear.

The organizations that consistently select the right platform ask a different set of questions, questions that move beyond features to expose how a solution actually behaves at scale, across sites, over time. This article outlines the criteria most likely to separate a genuinely capable platform from one that will require significant workarounds within three years.


1. How does the architecture support global standardization without sacrificing local flexibility?

This is arguably the most consequential question for any multi-site manufacturer, and it almost never appears in a standard RFP.

The challenge is well known: corporate wants standardized processes, harmonized KPIs and a consolidated view of operations. Plants need the flexibility to adapt to local regulations, shift patterns, labor agreements, shop-floor equipment, and product-specific workflows. Most MES/MOM implementations treat this as a configuration problem. It isn’t, it’s an architecture problem.

Ask vendors to demonstrate, concretely, how a process change initiated at the corporate level is deployed, validated, and rolled out to 15 plants simultaneously, while preserving approved local variants. Ask how conflicts between the global template and a local override are managed, versioned, and audited. The answer will reveal whether global/local governance is genuinely built into the data model, or patched in after the fact.


2. How does the platform integrate with PLM, not just ERP?

The ERP integration question is standard. The PLM integration question usually isn’t, and that’s a problem for discrete manufacturers, particularly in aerospace, automotive and industrial equipment.

In complex manufacturing environments, the manufacturing bill of materials, the engineering change order process and the as-built record are inseparable from operational performance. A MES or MOM platform that treats PLM as an external data source to be periodically synced creates a structural gap in the digital thread. Changes propagate late. Work instructions and quality control plans are outdated. As-built records are incomplete. Traceability is reconstructed rather than native.

Ask how engineering changes flow from the PLM environment into the MES/MOM layer automatically, with full version history, and without manual re-entry. Ask how electronic work instructions and quality control plans are passed from Manufacturing Engineering to MES/MOM. Ask how the as-built record is constructed and whether it can be interrogated directly from the engineering environment. For manufacturers with complex BOMs and frequent design iterations, this integration is not a nice-to-have.


3. What is the upgrade path and what does it actually cost?

Total cost of ownership calculations for MES and MOM platforms are notoriously misleading because they undercount customization maintenance costs. Most platforms require significant custom development to handle site-specific workflows. That custom code becomes a liability at every upgrade cycle.

Ask vendors for a transparent account of how upgrades have gone for customers with a similar level of implementation complexity. How many custom objects needed to be reworked? What was the average downtime? What percentage of customers are running the current version versus versions two or three releases behind?

A platform that enables process configuration without custom code (where business logic is expressed in configurable process models rather than hard-coded extensions) fundamentally changes this equation. The upgrade cost is lower, the dependency on implementation partners is reduced, and the organization retains genuine ownership of its operational processes.


4. Can the platform support operations beyond the production line?

Traditional MES thinking is line-centric. Broader MOM thinking is operations-centric, and for most discrete manufacturers, operations extend well beyond the production line itself.

Warehouse and material logistics, quality control workflows, maintenance and MRO operations, tooling management, workforce competency tracking: these functions either live in separate point solutions (creating integration overhead and data silos) or they are native capabilities of the platform. The difference has compounding effects on data quality, operational visibility and total system complexity over time.

Ask whether these adjacent functions are native modules with a shared data model, or integrations to third-party systems. Ask specifically how the platform handles MRO operations in a repair and overhaul context. The data model and process logic are substantially different from serial production, and not all platforms handle both with equal depth.


5. How does the platform perform in a brownfield environment?

The majority of MES and MOM implementations are not greenfield. They happen in plants with existing automation layers, legacy SCADA systems, aging PLCs and a patchwork of point solutions accumulated over decades.

A vendor’s ability to manage a clean greenfield deployment tells you relatively little about their ability to deliver value in a real industrial environment. Ask for specific examples of brownfield integrations, ideally in your industry, ideally with a similar level of legacy complexity. Ask how the platform handles heterogeneous equipment landscapes, and what connectivity options exist beyond standard OPC-UA.

The organizations that underestimate this question typically discover it six months into implementation, when the integration layer becomes the project.


6. Does the platform have built-in tools to govern how processes are created, shared and deployed across plants?

For a global manufacturer, process governance rarely appears in an RFP, yet it is one of the most consequential decisions you will make at the platform level.

Most multi-site deployments end up with a fragmentation problem: plants adapt the system to local needs, best practices stay siloed, IT has no visibility into plant-level modifications and transferring production between sites becomes a project in itself.

The question to ask any vendor is not whether they support a Center of Excellence model conceptually. The question is whether the platform provides digital tools to govern it in practice: centralized process authoring, electronic distribution of process changes to impacted plants, deployment tracking and controlled autonomy at the plant level for approved local variants.

Ask vendors specifically how a process change is authored at the corporate level and distributed digitally to 30 plants simultaneously. A platform that relies on manual coordination and change management processes external to the system will not scale, and the cost difference over a multi-site rollout lifecycle is significant.


Closing: A note on how to use this framework

These criteria are not exhaustive, and the relative weight of each will depend on your organization’s specific context: your industry, your site footprint, your integration landscape and your internal capabilities. But they represent the questions most consistently absent from MES and MOM evaluations, and most consistently relevant to long-term outcomes.

If you are currently in a selection process, DELMIA Apriso is designed to answer each of these questions with demonstrable depth, from its process-centric architecture and native PLM integration within the 3DEXPERIENCE platform, to its global/local process governance model and its track record in complex, multi-site discrete manufacturing environments. We would welcome the opportunity to walk through any of these criteria in deta

Request a technical deep-dive with a DELMIA Apriso specialist to find out more.

DELMIA, from Dassault Systèmes, enables manufacturers to keep factory operations running smoothly. Powered by the 3DEXPERIENCE platform, our Manufacturing Operations Management (MOM) and Manufacturing Execution Systems (MES) solutions establish a unified digital environment that provides real-time visibility and AI-enhanced control. By connecting the virtual and real worlds, we enable you to streamline complex processes, minimize waste and guarantee quality. Harnessing data-driven insights and intelligent automation allows for optimized production, enhanced adaptability to disruptions and the delivery of sustainable, customer-focused manufacturing performance at scale.

Stay up to date

Receive monthly updates on content you won’t want to miss

Subscribe

Register here to receive updates featuring our newest content.