MES — manufacturing execution system

Order and actual execution

We refer to the data regarding the operation, position, time and batch of material. We record good quantities, shortages and inspection results. The established status definition allows you to distinguish between a started, suspended and completed operation.

Information may come from operators or from prepared integrations with devices. You need to check the reliability of the measurement and the context: the machine's operating signal alone does not always mean that a good product has been made.

Example: indoor operation

The operator identifies the order and the batch of raw material, starts work, and then confirms the result. Downtime gets a reason. Quantities and consumption go into the ERP, while the history remains linked to the operation.

Such data can be used to determine where the process stopped and which batches were involved in production. The scope of traceability and quality control requires process-specific design.

MES limits and implementation on the job site

MES does not automatically replace machine controllers or MRP material planning. Responsible for the execution and information layer that we connect with ERP and devices within the agreed scope.

Before implementation, we check change handling, terminals, authorizations, loss of communication and corrections of incorrect registrations. The operator screen should make work easier, instead of requiring extensive reporting after each activity.

From the product to the material and the performed operation

Product genealogy relates the batches used to operations and output. It allows you to trace where the material was used and what inspections were carried out. We select the scope of identification to suit the process.

The project also includes correction of registration, rework and decision on further use of the lot. The history should distinguish the original record from the approved change.

From performance data to shift decisions

The report links quantities to time, position and reason for deviation. OEE combines availability, performance and quality; requires agreed definitions of planned time, reference speed and good product.

Before we compare the results, we check the completeness of registration. Information about a repeated stop can feed the maintenance task. The indicator itself does not explain the cause and does not guarantee improvement.

Data on time, material consumption and shortages can feed into the settlement of direct costs and the agreed division of indirect costs. We plan the queue of operations taking into account the availability of positions, rearmament and priorities. Inspection plan, breakdowns and maintenance orders can be linked to the CMMS so that machine unavailability is visible in planning.

The report distinguishes between planned and unplanned stops. Exceeding the agreed threshold may trigger notification to the appropriate person and require confirmation of the response. We match the validity of data and the frequency of reports to the process.

• Select one position and one question that the report should answer.
• Establish a reason dictionary and limit manual entry to information needed for decisions.
• Compare recording with observing actual work.
• Agree on actions when a threshold is exceeded or non-compliance is detected.