What Can MES Do in Production Management?

In the morning, the shift manager checks the plan from an Excel sheet, the machine operator records the quantity on paper, and the quality inspector logs discrepancies in a separate system. By the afternoon, it's unclear where each order stands, which ones are delayed, and whether yesterday's scrap data is final. In such a situation, a valid question arises: what can MES doand does it really solve the daily problems of production?

MES, or Manufacturing Execution System, is a system for managing and tracking production execution. It is not simply a new screen in production, nor a replacement for ERP. Its role is to connect planned production with what actually happens on the shop floor: orders, operations, people, machines, raw materials, quality checks, and finished products.

The real value does not come from a company "implementing an MES." It comes from clarifying how work is conducted, where information is lost, and which decisions lack reliable data today.

What can MES do in daily operations?

A well-designed MES shows what is happening in production now, not just what happened yesterday or at the end of last month. Necessary operations, workstations, specifications, materials, and checkpoints can be assigned to the production order. The worker does not start from an old printout or verbal instructions but sees the current task.

This is especially important when there are multiple products, changing order priorities, or frequent changeovers. If sales promise an urgent order, production needs to know more than just that capacity is "roughly full." It needs to see which work phase is idle, where materials are awaited, where there are machine bottlenecks, and what the consequences of a sequence change would be.

MES typically supports the issuance of production instructions, feedback on operations, recording of material usage, handling reasons for scrap and downtime, and collecting quality data. These are known tasks in themselves. The difference is that they do not appear in isolated papers, emails, and spreadsheets but are linked to the same production process.

The most important result: deviations become traceable

In many plants, the difference between the plan and reality only becomes apparent at the end of the shift or even later. The production manager suspects from experience that there is a problem, but there is no clear answer as to why an order is not completed on time. Material shortage? Machine downtime? Missing tool? Inadequate documentation? Too long changeover? Rework due to quality error?

MES does not automatically eliminate these causes. However, it can record them in a disciplined manner. This is an important difference. An inaccurate or overly general downtime category provides as little help as a "technical problem" note in an email. However, if it consistently shows that the deviation repeats on the same machine, product family, or before the same operation, the root cause can be addressed.

For management, this provides a better basis for decision-making. Intervention is not based on feelings or the loudest problem but on visibility of which loss is most significant. It may turn out that a new machine is not needed, but more precise material preparation is. Other times, machine maintenance, operation sequence, or the location of quality control causes the bottleneck.

MES and ERP: they do not solve the same problem

The ERP system is typically the center for business planning, procurement, inventory, finance, order management, and resource planning. It knows what needs to be produced, for which order, with what deadline, and with what inventory status. But it is not necessarily suitable for handling the minute-by-minute changing events of production by operation.

MES operates at the detailed execution level of production. It manages which workstation a production order is specifically at, who started it, with what parameters it ran, what material was used, and what quality result was achieved. Then the relevant, verified information can be fed back into the ERP: completed quantity, usage, scrap, operation readiness, or inventory movement.

The connection between the two systems is often a decisive question. If someone manually enters the production order from the ERP into the MES, or manually writes back the results at the end of the shift, the new system easily becomes just another layer of administration. In such cases, the issue is not technological but a process and integration error.

In what problems is it justified to consider MES at all?

Not every manufacturing company needs a full-scale MES. For a plant with a small volume, simple and stable workflow, a well-thought-out job sheet, better feedback discipline, or targeted system integration may be more valuable than an oversized platform.

It is worth considering MES if several of these phenomena occur simultaneously:

• the current state of production can only be compiled from phone calls, papers, or personal consultations;
• the reasons for scrap, rework, and downtime cannot be reliably measured;
• the same data is recorded multiple times by the workshop, office, and quality department;
• it is difficult to trace which material, machine, setting, or shift a product was made from;
• the growing order backlog disproportionately increases production administration.

The question is not solely about what software to buy. First, it is necessary to understand why the current process requires so much manual coordination. It may be that data simply does not originate where it is being recorded. It may be that the production instruction exists in too many versions. It may also be that the ERP master data or production standards are inaccurate, so the production feedback will not be credible either.

The quality of data is more important than the number of displays

An MES can create detailed dashboards, but a colorful display does not ensure reliable operation. If workers have too many fields to fill out, if the meaning of the downtime code is unclear, or if the system is slow and cumbersome, the entered data will be incomplete. This later results in reports that appear accurate but are misleading.

Good design therefore does not start with what screens management wants. It starts with what decisions require information, who makes these decisions, and which data can be recorded in real-time, reliably. A signal sent by a machine represents a different level of reliability than a shift report filled out later from memory. Both can have their place, but they should not be mixed.

The human aspect of implementation is also not negligible. Workers in the workshop are not there to compensate for IT system errors. They need a tool that clarifies work, reduces searching, and shows the necessary information. If MES appears only as a control tool, it naturally triggers resistance. If it helps avoid incorrect version instructions, unnecessary paperwork, and repeated inquiries, its use becomes more realistic.

What makes an MES project successful?

Gradual implementation is often safer than a comprehensive transformation covering everything at once. A critical product family, a production line, or a particularly difficult-to-track operation can be a good starting point. Here it can be checked whether the master data is correct, feedback works, the operator process is acceptable, and the necessary information for management actually appears.

The system design must also consider exceptions. What happens in case of machine failure? How is rework handled? Who approves a deviation? What is the process if the network is temporarily unavailable? A production system's value is not only shown in normal operation but also when an anomaly occurs.

MES provides lasting value if it is not a digital copy of the existing paper process but helps simplify it. The best first step is often not selecting the system but jointly exploring the actual path a production order takes from plan to finished product. Where this path is clear, the appropriate technology also becomes a much easier good business decision.