LOG iN MOM

MES stands for Manufacturing Execution System: production execution system. It is the manufacturing MES software that bridges the gap between the company management system (ERP) and the operational reality of the production department.

The ERP plans: it releases production orders, calculates requirements, estimates times and costs. But it does not know what happens after the plan enters the factory. The MES is the tool that takes that plan in charge and follows it in execution: it monitors order progress phase by phase, collects data from machines in real time, records stoppages and scrap, calculates operational KPIs such as OEE, traces every product along the process.

In practical terms, the MES serves to answer questions the management system cannot solve. Where is order X? Is line 3 producing at the expected pace? How long was the stoppage of machine 7 and what was the cause? How many defective pieces did the night shift produce? Will we manage to complete production by Friday?

Without a MES, these answers are obtained at the end of the shift: when someone fills in a sheet, updates a file, declares the data to the system. With a MES, the answers are available in real time, generated automatically from field data. The difference is not only in speed: it is in decision quality. Acting on a problem while it is happening costs a fraction of what it costs to discover it after the fact.

In an Italian manufacturing context: where the production mix is high, lots are variable, make-to-order production often coexists with make-to-forecast and market demands change rapidly, the MES is the tool that makes the complexity of the department visible and governable. It does not eliminate it: it turns it into data on which to decide.

The difference between MES and ERP in manufacturing is one of the most frequent, and most relevant, questions for those evaluating production digitalization. The two systems are not alternatives: they are complementary, and each operates on a different level.

The ERP is the company management system. It operates at the planning and administration level: sales and purchase orders, master data, bills of materials, accounting, MRP, costs. When it comes to production, the ERP releases orders, calculates requirements and records final balances. Its data is accounting and transactional: correct, necessary, but updated after the fact.

The MES operates at the execution and operational control level. Its field of action is the department: machines, lines, operators, materials being processed. It collects data from the field in real time, monitors progress, measures performance, records stoppages and scrap the moment they happen, traces the product phase by phase.

The concrete differences are seen on five dimensions. The ERP knows the order was released for 500 pieces, the MES knows that at 3:00 PM 312 were completed and the completion estimate is tomorrow at 11. The ERP records a stoppage at the end of the shift, the MES detects it the instant the machine stops and classifies its cause. The ERP unloads materials per order at final balance, the MES records every consumption the moment it occurs, associated with the phase and lot. The ERP uses standard times for costs, the MES measures actual times and signals deviations. The ERP tracks quantities produced per order, the MES tracks the physical path of the product by machine, operator and process parameters.

The ERP without MES is a plan without control over execution. The MES without ERP is control without planning context. Manufacturing needs both: connected by a bidirectional flow where the ERP feeds the MES with the plan and the MES returns real execution data to the ERP.

LOG iN MOM is designed to work in pairs with the ERP. It receives orders and bills of materials, returns declarations, consumption and times: with connectors tested for SAP, Oracle, Microsoft Dynamics and AS/400. MES integration with ERP and warehouse is not a separate project: it is a native function of the system.

MOM stands for Manufacturing Operations Management. It is the evolution of the MES defined by the ISA-95 standard (the international standard that describes the architecture of information systems for manufacturing).

The traditional MES focuses on production execution: data collection, progress monitoring, OEE calculation, traceability. The perimeter is the production line.

The MOM extends that perimeter to all plant operations. It does not only cover production, but integrates quality management, maintenance and plant logistics under a single model. The idea behind MOM is that these functions are not separate: quality depends on production, production depends on maintenance, maintenance depends on spare-part availability (logistics). Managing them with separate systems generates information silos. Managing them with a single system generates visibility and coordination.

In practical terms, the difference between MES and MOM translates like this: a MES tells you that machine 5 is stopped. A MOM tells you that it is stopped, that maintenance has an intervention planned for tomorrow, that the spare part is in stock in the warehouse and that by rescheduling the order in progress on machine 3 the impact on delivery is half a day. The MOM does not just observe one perimeter: it coordinates several perimeters.

LOG iN MOM adopts the MOM model. It is natively linked to LOG iN WMS (warehouse), LOG iN eKanban (supply) and LOG iN Maintenance (maintenance), not through interfaces, but through a single shared database. This is why it is called MOM and not MES: because the perimeter is the entire plant, not only production.

Times vary based on the scope: number of lines, complexity of processes, level of connection with the machines, state of the ERP integration.

As a reference, implementing LOG iN MOM on a single medium-sized manufacturing plant typically takes between 3 and 6 months from kick-off to go-live.

Analysis and design take 4-6 weeks. It is the phase of the AlfaProject.net Method applied to production: mapping production flows, identifying bottlenecks, defining operational rules (scheduling logics, priority criteria, KPIs to monitor, level of data collection per machine). It is the phase that determines the quality of the implementation: skipping it or shortening it is the surest way to lengthen everything else.

Configuration and integration take 4-8 weeks. LOG iN MOM is configured on the operational rules defined in the previous phase: line structure, work phases, machine connection, ERP flows. The ERP connectors for SAP, Oracle, Microsoft Dynamics and AS/400 are already developed. Interfacing with the machines depends on the available protocols. PLC, OPC-UA, Modbus, operator terminals.

Testing, training and assisted start-up take 4-6 weeks. Functional tests on real flows, training of shift leaders and operators, training of the production manager on dashboards and KPIs. The go-live is assisted by the AlfaProject.net team to calibrate the rules on the basis of the real data generated in the first weeks of operation.

The approach is progressive. You can start from a pilot department: one or two lines, and then extend to the entire plant when the results justify it. Every extension replicates the same logic, it does not redesign it. And when the MOM is operational, the perimeter can be extended to the warehouse (LOG iN WMS), to supply (LOG iN eKanban) and to maintenance (LOG iN Maintenance): on the same database, without new integrations.

The return on investment of manufacturing MES software is measured on concrete operational indicators. The KPIs on which LOG iN MOM generates quantifiable impact are five.

Reduction of production lead time. When progress is visible in real time and priorities update dynamically, waits between phases are reduced. Bottlenecks are identified as they form, not at the end of the week. Synchronization with the warehouse eliminates waits for materials. The order crosses the department faster because the flow is coordinated, not managed by exceptions.

Increase in plant saturation. Unplanned stoppages are reduced thanks to real-time monitoring of machine states, immediate signalling of causes and visibility shared with maintenance. Setups are optimized thanks to the comparison between standard and actual times. Machines produce more not because the pace is accelerated, but because the time in which they are not producing is eliminated.

Reduction of scrap. Real-time recording of defects, associated with machine, phase, lot and operator, makes it possible to trace the cause while the defect is still contained. The reaction is rapid: entire defective lots are not discovered at the end of production.

Improvement of overall OEE. The OEE calculated automatically and in real time, broken down into three factors (availability, performance, quality), makes it visible where efficiency is lost and where to intervene. The improvement is not generic: it is targeted at the specific causes that reduce the OEE of each machine and each line.

Reduction of non-quality costs. Less scrap, less rework, fewer internal returns, fewer non-conformities not intercepted. For sectors with strict regulatory requirements, the impact is also on reducing the risk of recalls and penalties.

The AlfaProject.net Method estimates the payback before implementation: for each scenario, investment, payback times and expected impact on KPIs are calculated. After go-live, LOG iN MOM returns those same KPIs in real time. The comparison between forecasts and results is immediate, no after-the-fact analysis is needed to understand whether the project is producing value.