In many plants, production control exists in three forms: once in the ERP system, once on a whiteboard in the plant manager’s office, and once in the mind of the experienced foreman, who knows which job is actually next in line. The gap between these three “truths” is precisely what MES software is designed to bridge.
The market promises a lot in this regard: real-time transparency, less downtime, higher OEE, and automatic traceability. Much of this can indeed be achieved with a Manufacturing Execution System. But the crucial point is rarely mentioned in vendor brochures: MES software does not deliver value simply by being installed, but rather through the data quality and process discipline with which it is operated.
Anyone familiar with production lines has seen both scenarios. Plants where an MES delivered the first reliable scrap rate per shift after just six weeks. And plants where, two years after go-live, the same category of software produced one thing above all else: expensive dashboards that no one opens because the underlying feedback is recorded manually and incompletely.
THE MOST IMPORTANT POINTS AT A GLANCE
|
IN A NUTSHELL
|
1. What Is MES Software? Definition and Classification
In many companies, there is an information gap between what the ERP system plans and what the machine actually produces. MES software closes exactly this gap.
MES software (Manufacturing Execution System, also known in German as a production control system or manufacturing management system) is a software layer that controls, monitors, and documents manufacturing processes in real time. It captures machine, operational, and quality data directly on the production line, links it to the current production order, and generates key metrics such as output, availability, or scrap rate. The key difference from ERP lies in the timeframe: ERP plans in days and weeks, while MES software controls operations in minutes and seconds.
In the classic automation pyramid, the MES sits at Level 3, between corporate planning (Level 4, ERP) and the control level at the machines (Levels 0 to 2). This position precisely describes its role: translating directives from above into actionable instructions for the shop floor and transforming feedback from below into reliable management information.
A real-world example from the mechanical engineering sector illustrates the benefits: Before implementing the MES, a manufacturer with about 30 CNC machines did not know the actual machine utilization rate until the end of the month. After the integration, machine availability was available as a real-time value, and the initial analysis showed that one-third of the downtime was due to setup operations that could have been avoided by changing the order sequence.
WHEN MES SOFTWARE MAKES SENSE
|
2. MES Functions According to VDI 5600: The Eight Functional Areas
The term “MES software” is not a protected term. Almost every provider interprets it slightly differently. In German-speaking countries, the VDI 5600 guideline provides a common framework: It defines eight functional areas that a complete MES should cover.
Important for your own selection: VDI 5600 describes what an MES is supposed to accomplish, not the order in which the functions should be implemented, nor does it require that a single provider master all eight areas to the same degree. In practice, most systems cover one key area very well and other areas only at a basic level.
| VDI 5600 Function | What the Function Achieves | Typical Measurable Benefits |
|---|---|---|
| Detailed Planning and Control | Translates the ERP’s rough planning into a specific order sequence for each machine, tool, and shift. | 10 to 30% reduction in setup time due to optimized sequencing |
| Data collection (BDE/MDE) | Collects machine, operational, and process data automatically or via feedback at the terminal. | Reliable actual times instead of estimated values |
| Performance Analysis | Calculates key performance indicators such as OEE, availability, output, and scrap rate in real time. | Transparency by shift instead of monthly reports |
| Quality Management | Manages and documents inspections, records measurement values and defects on a component-by-component basis. | Complete quality documentation, earlier defect detection |
| Equipment Management | Monitors the availability and condition of equipment and tools, and plans maintenance. | Fewer unplanned downtimes |
| Material Management | Tracks material provision and consumption per order, supports batch assignment. | More accurate inventory, clear traceability |
| Personnel Management | Schedules personnel based on qualifications and availability; records order-related hours. | Precise staffing for each order |
| Information Management | Provides role-based analyses, reports, and dashboards. | Faster, data-driven decisions |
Together, these eight areas form a closed-loop system comprising planning, data collection, analysis, and control. In reality, however, hardly any plant implements all of these areas at once. The proven approach starts with the biggest bottleneck—usually data collection and performance analysis—and expands step by step from there.
MES software isn’t considered good simply because it offers all eight VDI functions, but because the functions a plant actually needs run on clean data. The rest is just overkill.
— Amadeus, Chief Technology Evangelist, CSP Intelligence GmbH
3. MES, ERP, SCADA, and MOM: Who Does What?
The most common confusion when selecting software arises at the boundaries between systems. Understanding these boundaries helps avoid duplicate investments and unmet expectations.
These four terms describe different levels and time horizons. ERP handles business planning for what is produced. MES software controls, at the operational level, how production takes place. SCADA monitors individual machine signals without reference to specific orders. MOM (Manufacturing Operations Management) is the umbrella term for all operational manufacturing systems, with MES at its core.
| System | Task | Time Horizon | Level |
|---|---|---|---|
| ERP | Plans orders, materials, capacities, and costs from a business management perspective | Days to weeks | Level 4 |
| MES | Controls, monitors, and documents production in real time | Minutes to seconds | Level 3 |
| SCADA | Monitors and controls individual machine signals without reference to a job | Seconds to milliseconds | Level 1 to 2 |
| MOM | Umbrella term for all operational manufacturing systems; MES as the core | Operational | Level 3 (comprehensive) |
A practical rule of thumb from projects: SCADA provides signals, the MES converts them into order-specific, control-relevant information, and the ERP draws business conclusions from them. Anyone who tries to implement real-time control in the ERP system or maintain quality documentation in SCADA is working at the wrong level.
For quality-driven industries, one limitation is particularly relevant: A classic, broad-based MES often covers quality and traceability data only at a basic level. Requirements under IATF 16949 Section 8.5.2 (traceability) or audit-proof, long-term archiving in accordance with GoBD and HGB §257 go beyond the standard scope of many MES suites and are frequently supplemented by specialized systems.
4. Architecture Models: On-Premise, Cloud-Hosted, and Cloud-Native
The architecture of an MES software solution determines not so much its feature set as its implementation time, ongoing costs, and scalability. Three models dominate the market.
| Model | Features | Implementation | Suitability |
|---|---|---|---|
| On-premises | Installed locally on your own servers; high degree of customization; requires in-house IT administration | Typically 12 to 24 months | Large plants with their own MES IT infrastructure and special requirements |
| Cloud-hosted | Existing software migrated to the cloud; little architectural benefit | Medium | Transitional solution, rarely strategic |
| Cloud-native | Developed from the ground up for the cloud, SaaS pricing model, rapid integration | Days to weeks | Mid-sized manufacturers without dedicated MES IT |
The market is clearly shifting toward cloud-native solutions because the integration of existing equipment has accelerated significantly. Proof-of-value phases—in which a provider demonstrates the system’s benefits using actual machines and real data—have become shorter. This is increasingly shifting the decision-making authority from the IT manager to the plant or operations manager.
At the same time, honesty is key across the board: cloud-native is not an end in itself. Plants with strict data sovereignty requirements, security-critical processes, or highly customized legacy systems still have good reasons to opt for on-premises operations or hybrid models. The question of architecture is a matter of weighing options, not a matter of faith.
COMMONLY UNDERESTIMATED COST FACTORS IN ARCHITECTURE SELECTION
|
5. Selecting MES Software: Seven Steps to Making a Decision
Most MES mistakes aren’t made when selecting the software itself, but before that: when the selection process begins with feature lists instead of identifying your own bottlenecks. The following process has proven effective in practice.
Step 1: Identify the biggest bottleneckBefore requesting a single quote, it must be clear which problem the MES software is intended to solve first. Unknown OEE, incomplete traceability, excessively long setup times, or a lack of quality documentation all lead to different requirement profiles. |
Step 2: Prioritize the relevant feature setFrom the eight VDI 5600 areas, select the two to three that address the bottleneck. All other areas are optional and do not serve as selection criteria for the first phase. |
Step 3: Check master data and machine connectivityHow accurate are part numbers, work plans, and inspection characteristics? Which machines already provide data via OPC-UA or MQTT, and which ones need to be retrofitted or have data entered manually? This review has a greater impact on the project’s success than any software feature. |
Step 4: Define the architecture and operating modelOn-premises, cloud-hosted, or cloud-native? The decision should be based on data sovereignty, existing IT capacity, and the planned number of locations—not on current trends. |
Step 5: Proof of Value with Real DataTwo to three systems are tested on actual machines using real data. What matters is not the vendor's demo environment, but how quickly the first reliable results become apparent in the company's own plant. |
Step 6: Evaluate Integration and InterfacesHow does the MES software integrate with the ERP system, as well as with the quality control and archiving systems? Missing or proprietary interfaces create precisely the data discontinuities that the MES is actually supposed to eliminate. |
Step 7: Plan the rollout in phasesStart with one plant, one production line, and five to ten machines. Initial results must be visible before the organization loses interest. The rollout should only follow once results have been demonstrated. |
A practical benchmark for reference: The median duration of a proof-of-value phase has decreased noticeably in recent years, from about eight weeks to about four weeks, because integrating existing systems has become easier. Anyone who goes longer than a quarter without seeing initial results should reevaluate the scope of the pilot project.
6. What an MES implementation costs and why it fails
It is difficult to provide reliable price estimates for MES software because the scope, number of machines, and operating model cause costs to vary widely. The following approximate figures serve as a rough guide.
| Model | Rough Cost Estimate (Plant with approx. 30 machines, 3-year TCO) | Pricing Model |
|---|---|---|
| Cloud-native MES | approx. €30,000 to €90,000 | Monthly SaaS model, no on-premises server |
| On-premises MES | approx. €200,000 to €500,000 | Multi-year licenses plus operation and upgrades |
| Enterprise MES | Starting at approx. 500,000 € | Comprehensive suites from major providers |
These figures are market benchmarks, not quotes. The key point lies elsewhere: The critical cost factor is usually not the software itself, but the implementation project. In traditional implementations, project costs regularly exceed licensing costs by a factor of two to three. Using standard configurations instead of custom programming significantly reduces this factor.
COST STRUCTURE OF ERRORS: WHY MES PROJECTS FAIL
|
The countermeasures are well-known and unspectacular: a master data audit before the project starts, mandatory involvement of business units, a tightly scoped pilot project, and a clearly measurable first result. These four points distinguish successful MES projects from costly ones more clearly than any list of features.
Integration quickly spreads poor data everywhere. Anyone who starts an MES project with master data chaos will end up with well-connected master data chaos. The data foundation must come before the software.
— Amadeus, Chief Technology Evangelist, CSP Intelligence GmbH
7. MES Software in the Context of Quality and Traceability: Manufacturing OS from CSP
A note up front, in the interest of transparency: CSP’s Manufacturing OS is not a traditional, full-featured MES suite with detailed planning, materials management, and personnel management. The platform specializes in the quality-, process-, and traceability-critical aspects of manufacturing and operates alongside or within an existing MES and ERP landscape.
For the automotive, mechanical engineering, medical technology, and aerospace industries, this is often where the actual bottleneck lies. Whereas a broad-based MES only provides basic coverage of quality data, Manufacturing OS bundles the functions that are crucial for complete documentation and audit readiness.
PRACTICAL TIP: MANUFACTURING OS FROM CSPManufacturing OS combines four specialized modules into an integrated platform for quality-relevant production data:
The platform is used by BMW, Mercedes-Benz, and Knorr-Bremse, among others. → Learn more about Manufacturing OS and its integration into your MES landscape |
Where AI-supported methods such as Curve Anomaly AI are used for anomaly detection, a clear principle applies: AI provides decision support, not fully autonomous approval. In safety-critical industries, a fully autonomous approval decision by AI is not permitted by regulation. The EU AI Act requires transparency and human oversight for high-risk systems, and the EU Product Liability Directive 2024 extends the definition of “manufacturer” to include AI-supported decisions. Human responsibility for approval remains in place.
8. Frequently Asked Questions About MES Software
What is MES software, explained simply?
MES (Manufacturing Execution System) software is a software layer that controls, monitors, and documents manufacturing processes in real time. It sits between the ERP system—which plans in days and weeks—and the machines on the shop floor. MES software collects machine, operational, and quality data directly on the production line and uses it to calculate key metrics such as OEE or scrap rate. In German, it is also referred to as a production control system or manufacturing management system.
What is the difference between MES and ERP?
ERP plans what is produced from a business management perspective, over a timeframe of days and weeks. MES software controls how production is carried out from an operational perspective, in minutes and seconds. ERP manages orders, materials, and costs, while MES translates these specifications into an executable sequence of operations on the machines and reports the results back. Both systems complement each other and are connected via interfaces.
What features must MES software have?
The leading standard in German-speaking countries is VDI 5600, which defines eight functional areas: detailed planning and control, data collection, performance analysis, quality management, equipment management, material management, personnel management, and information management. No plant needs all eight functions right away. The selection process should begin with the two or three areas that address the most significant current bottlenecks.
How much does MES software cost?
The costs depend heavily on the scope, number of machines, and operating model. As a rough guide for a plant with around 30 machines over three years: cloud-native MES ranges from about 30,000 to 90,000 euros, while on-premises solutions are significantly more expensive. The decisive cost factor is often not the license itself, but the implementation project, which regularly exceeds the license costs by a factor of two to three.
What is the difference between MES and SCADA?
SCADA monitors and controls individual machine signals without reference to the production order, in the range of seconds to milliseconds. The MES software captures these signals, links them to the current order, and uses them to generate control-relevant information at Level 3 of the automation pyramid. Simply put: SCADA provides the raw signals, and the MES turns them into order-related management information.
How long does it take to implement MES software?
That depends heavily on the architecture and scope. On-premises implementations typically take 12 to 24 months, while cloud-native solutions are often up and running within days to weeks. A sensible starting point is a pilot project involving one production line and five to ten machines. The first reliable results should become apparent within a few weeks; otherwise, the scope of the project should be reviewed.
Does MES software support traceability in accordance with IATF 16949?
In principle, MES software can contribute to traceability in accordance with IATF 16949 Section 8.5.2, as it links component and batch data to the order. However, the scope varies greatly among providers. Requirements for complete quality documentation and audit-proof long-term archiving in accordance with GoBD and HGB §257 often exceed the standard scope of broad MES suites and are supplemented by specialized systems.
Does my company need MES software, or is ERP sufficient?
If the current production status is only compiled manually, if key performance indicators such as OEE are only available with a delay of several days, or if traceability in the event of a complaint requires a great deal of effort, the ERP system reaches its limits. ERP is not designed for real-time production control. In these cases, MES software fills a gap that ERP, by its very nature, cannot cover.