Kierownik produkcji analizuje wskaźnik OEE na tablecie z systemem monitoringu maszyn w hali produkcyjnej
Articles MES systems

Does Your Factory Really Need an MES? When Agile Machine Monitoring Is Enough – and How to Save 80% of the Budget

When does a factory really need a full MES, and when is agile machine monitoring enough? A comparison of costs, implementation time and ROI, plus 4 signs that a machine data platform will work faster and cheaper.

In brief

When does a factory really need a full MES, and when is agile machine monitoring enough? A comparison of costs, implementation time and ROI, plus 4 signs that a machine data platform will work faster and cheaper.

A strategic guide for operations directors, plant owners and production managers in manufacturing.

A traditional MES (Manufacturing Execution System) is a powerful but expensive tool (from PLN 250,000 to over PLN 1.5 million, roughly €60,000–€350,000+) that takes a long time to implement (6–18 months) and is designed mainly for dynamic order scheduling, routings and process genealogy. If your main goal is to eliminate unplanned downtime, calculate real OEE live, control energy consumption per part and track shift performance, a full MES is usually costly over-engineering. Up to 80% of the real operational benefits can be achieved in 2–4 weeks by deploying an agile machine data acquisition and analytics platform (a Production Data Hub), while keeping flexibility and a total cost of ownership (TCO) that is many times lower.

Many production directors and plant owners face the same dilemma: “We have to raise efficiency and cut losses. Everyone is talking about Industry 4.0, so I guess we need an MES.” Right after that, the first offers from software vendors arrive: budgets in the hundreds of thousands, pre-implementation audits lasting months, a requirement to reorganise shop-floor processes and the prospect of 12 months of decision paralysis.

Meanwhile, market data published by analyst firms (including ARC Advisory Group and Gartner) is unforgiving: as many as 50–60% of classic, monolithic MES implementations fail to deliver the expected return on investment (ROI), or end up using only 15–20% of the purchased modules. In practice, the factory pays for a heavyweight combine harvester and uses only a simple machine status view.

So it is worth asking why this happens and how to tell a genuine need for an MES from a need for reliable, agile real-time production monitoring.

1. What a traditional MES really is – and what it is not

According to the ISA-95 standard and the guidelines of MESA (Manufacturing Enterprise Solutions Association), an MES is the intermediate layer between business planning (ERP) and direct machine control on the shop floor (SCADA/PLC). The full, classic MES model covers 11 defined functions, including:

  • Detailed scheduling (APS): sequencing operations while accounting for changeovers and the availability of dies and moulds.
  • Routing and dispatching: sending tasks step by step to specific work centres.
  • Electronic document management (SOP): work instructions and technical drawings on operator screens.
  • Laboratory and quality management (LIMS): sample validation and batch holds.
  • Strict product genealogy (traceability): linking a raw material serial number to the finished product.
  • Resource and skills allocation: checking operator qualifications before a machine can be started.

The problem is that most SME and mid-sized manufacturing plants do not actually suffer from a lack of sophisticated dispatching or electronic instructions. Their real, everyday pain is a lack of basic visibility:

  • No live insight: Why did the packing line stand still for 45 minutes on the second shift?
  • Unreliable paperwork: Distorted shift reports in which micro-stoppages are blurred or rounded off.
  • Distorted OEE: The metric is calculated in Excel based on declarations rather than hard signals from the PLC.
  • Uncontrolled costs: No idea how much energy and compressed air it took to produce a specific batch.

Solving these problems does not require a monolithic system. What you need is an agile data acquisition and monitoring platform (such as iPLAS) that focuses on extracting the truth from machines and instantly calculating the cost of downtime and real ROI. This applies especially to smaller plants – see also Is an MES system for small companies?

2. Decision table: traditional MES vs an agile monitoring platform (iPLAS)

Area Classic, monolithic MES Agile monitoring platform (iPLAS)
Main business goal Strict control of production flow and routings. Instant visibility of machine status and OEE, elimination of downtime and energy losses.
Implementation time 6–18 months (often with change orders and delays). 2–4 weeks.
Implementation model Heavy IT project, deep process reorganisation. Modular / plug & play (step by step, without paralysing the shop floor).
Data source Frequent manual reporting on terminals. Automatically from PLCs / sensors + simple touch panels.
Infrastructure Dedicated servers, expensive database licences. Cloud (SaaS) or a lightweight on-premise server (Gateway).
Initial budget (CapEx) PLN 200,000 – 1,500,000+ (approx. €47,000–€350,000+) plus an expensive annual SLA. Low entry threshold (flexible subscription model).
Workforce resistance High – complex forms and screens. Minimal – automatic data capture + Andon screens on the shop floor.
Return on investment (ROI) Usually more than 24–36 months. Usually 3–6 months (losses reduced by 10–25%).

3. When does your factory really need an MES?

Let’s be precise – there are specific production environments where implementing a full, formal MES is justified or outright required by industry regulations:

  • Strict OEM requirements (automotive Tier 1, aerospace): When the contract requires recording the exact tightening torque of every bolt against a unique VIN/serial number and blocking the next assembly step if there is a deviation.
  • Pharmaceuticals and biotech (FDA / GMP / 21 CFR Part 11): When every operator action requires a double electronic signature, electronic batch release and strict laboratory quarantine.
  • Exceptionally complex dynamic routings: When a part passes through 30 machining centres and routings are reconfigured dynamically depending on tool failures.

If your production consists of discrete processes – machining, plastics processing, packaging, food, furniture or metal manufacturing – and your challenge is efficiency, a full MES will almost certainly prove too heavy and inflexible.

4. Four signs that agile monitoring will solve your problems faster and cheaper

Sign 1: “We know how much we made, but not how much we COULD have made”

A shift produced 10,000 units. The plan was 12,000. Why were 2,000 units missing? The paper report says: “Feeder failure – 20 min.” Where did the rest of the time go? The answer is micro-stoppages lasting 30–90 seconds, which an operator physically cannot record. An agile system takes the cycle signal directly from the machine and precisely records every second of delay.

Sign 2: “We have an ERP system, but it is blind to what happens on the shop floor”

Most companies already have an ERP system (e.g. SAP, Comarch, IFS, Sage). ERP handles inventory, finance and orders very well, but it does not know what is happening at the work centres. We discuss these differences in detail in ERP vs MES: what are the differences. Instead of spending a fortune customising ERP production modules, an agile Data Hub (iPLAS) acts as an intelligent connector – it collects data from machines and passes ready, cleansed order confirmations to the ERP.

A common decision trap: extending the existing ERP with a production module instead of deploying a system for collecting machine data. An ERP is a relational transactional database designed to process documents, not thousands of sensor events per second. Trying to connect machines directly to the ERP ends with a choked database, sharply higher licence costs and a sluggish interface. iPLAS works as a filter and buffer – machines report to iPLAS, and the ERP receives only hard facts about order execution.

Sign 3: “Rising energy costs and no idea of the real unit production cost”

A single aggregated electricity invoice at the end of the month makes it impossible to calculate the margin on a specific order reliably. An agile platform combines energy meter readings with the production cycle, so you can calculate the real technical cost of manufacturing per batch and use a dynamic energy price forecasting module to optimise the schedule.

Sign 4: “The workforce rebels against complicated IT interfaces”

Forcing operators to log in to multi-level MES screens creates resistance and distracts them from watching the machine. In the agile approach, 90% of the data is collected automatically from the PLC, and the operator uses a simple touch panel only when the reason for a longer stoppage needs to be entered. This data feeds an automated Pareto analysis of losses.

5. Phased implementation: how to start digitalisation without risking shop-floor paralysis

The most effective digital transformation strategy is a phased approach: from the bottleneck to the whole shop floor (Start Small, Scale Fast):

  1. Step 1 (weeks 1–2): Connect 2–3 pilot machines (bottlenecks). Collect statuses and cycle times.
  2. Step 2 (weeks 3–4): Launch Andon screens on the shop floor and OEE dashboards for management.
  3. Step 3 (month 2): Add utility monitoring (electricity, compressed air) and breakdown notifications.
  4. Step 4 (month 3+): Scale to the remaining lines and integrate with the ERP.

For more ways to cut the cost and time of a rollout, read: 5 ideas to make MES implementation cheaper and faster.

The business decision: when to choose a full MES and when agile monitoring

Instead of starting a risky MES implementation that takes many months, choose an agile tool that delivers hard data from the shop floor within a few weeks. Cleansed machine facts will immediately show where money is leaking – giving you a fast return on investment and a solid foundation for the further development of your factory.

Next step: find out how much you can gain by eliminating micro-stoppages

Wondering whether agile monitoring is enough for your plant, or whether industry regulations will force a full MES? Don’t make the decision blindly based on sales offers.

  • Production profile analysis: We will tell you plainly whether your operations require a full MES or an agile data hub.
  • ROI and loss estimate: We will calculate, free of charge, an indicative figure for the losses generated by unplanned micro-stoppages in your plant.

➔ Book a free consultation and calculate the ROI for your factory

Sources and industry literature

  • MESA International (Manufacturing Enterprise Solutions Association): ISA-95 standard (Enterprise-Control System Integration) and the 11-function MES model.
  • ARC Advisory Group: market reports “Manufacturing Execution Systems and Production Intelligence Market Outlook”.
  • Gartner Research: Magic Quadrant for Manufacturing Execution Systems & Industrial IoT Platforms.
  • NIST (National Institute of Standards and Technology): Special Publication on Smart Manufacturing Systems and Data Integration Frameworks.
Marcin Zielinski
Author and subject-matter consultant

Marcin Zielinski

Industrial IT & Analytics Specialist

Marcin supports the strategic and technological development of the iPLAS platform, bridging industrial process knowledge with modern IT solutions and manufacturing data analytics.
iPLAS for manufacturing

Turn production data into confident decisions.

Connect machines, operators and systems in one place — from OEE and downtime to energy, quality and traceability.