MES Software: Vendors, Features & Costs Compared 2026
MES software compared: vendors, functions per VDI 5600, costs (cloud vs. on-premise) and implementation. Honest market overview 2026.
By Martin Brandel · Last updated: April 2026
What is a CMMS (Plant Maintenance Management System)?
A CMMS (Computerised Maintenance Management System) — also known as a plant maintenance management system — is software that manages the maintenance of physical assets: machines, production lines, buildings, and infrastructure. It stores an asset register (every machine, its location, its components, its maintenance history), schedules preventive and corrective maintenance tasks, tracks work orders from creation to completion, manages spare parts inventory, and records the cost and time of every maintenance activity. The internationally established abbreviation is CMMS. In the SAP ecosystem, the equivalent function is the PM (Plant Maintenance) module. In asset-intensive industries (energy, utilities, mining), the broader term EAM (Enterprise Asset Management) is used — EAM includes CMMS functionality plus financial asset lifecycle management (depreciation, replacement investment planning). For discrete manufacturing — the SYMESTIC customer base — CMMS is the standard term. A CMMS does not collect machine data automatically. It does not calculate OEE.
It does not know whether a machine is running or stopped right now. That is the job of an MES (Manufacturing Execution System). The two systems are complementary, not interchangeable — and the interface between them is where maintenance transitions from reactive to predictive.
What are the core functions of a CMMS?
| Function | What it does | Data it uses | MES connection |
|---|---|---|---|
| Asset register | Central database of all maintainable assets: machine ID, location, manufacturer, model, serial number, installation date, criticality rating, bill of materials (which spare parts belong to which machine). | Static master data. Entered manually or imported from ERP. | The MES references the same machine IDs. When the MES reports a failure on machine M-007, the CMMS knows exactly which asset that is, what components it contains, and which spare parts are on the shelf. |
| Work order management | Creates, assigns, tracks and closes maintenance work orders. A work order specifies: what needs to be done, on which asset, by whom, with which spare parts, by when. Status tracking: open → in progress → completed → closed. | Work order data: task description, assigned technician, start/end time, parts consumed, labour hours. | MES can trigger work orders automatically. When the MES alarms module detects that alarm #4011 ("hydraulic pressure below threshold") has occurred 5 times in 24 hours, it can push a maintenance notification to the CMMS — before the machine fails. |
| Preventive maintenance scheduling | Schedules time-based or meter-based maintenance tasks: "Replace hydraulic filter every 2,000 operating hours" or "Inspect conveyor belt every 3 months." Generates work orders automatically when the interval is reached. | Calendar dates or operating-hour counters. Operating hours are the more accurate trigger — but only if the actual hours are available. | The MES provides the actual operating hours per machine from PLC signals — not calendar estimates. At Brita, digital machine signals provided the operating-hour foundation. The MES feeds the real operating hours to the CMMS, which triggers the work order at exactly the right time. |
| Spare parts inventory | Tracks spare parts: stock levels, reorder points, supplier lead times, consumption history per asset. Links parts to assets (bill of materials) and to work orders (parts consumed per repair). | Inventory transactions: parts issued, parts received, stock counts. | MES failure data (which components fail most often, measured MTTF per component type) informs the spare parts stocking strategy. Components with low MTTF and high downtime impact are stocked on site. Others are ordered on demand. |
| Maintenance history & reporting | Complete maintenance log per asset: every work order, every repair, every part replaced, every cost incurred. Reporting: MTBF, MTTR, maintenance cost per asset, planned vs. unplanned maintenance ratio. | Historical work order data aggregated over months and years. | The MES adds the production context: this machine had 3 unplanned stops this month (MES data) and each stop was resolved with work order #xxx (CMMS data). The combined view shows the full picture — operational impact + maintenance response. |
What is the difference between CMMS, EAM and MES?
These three systems are frequently confused. They are different systems that manage different things, sit at different levels of the operational architecture, and are used by different people:
| Dimension | CMMS | EAM | MES |
|---|---|---|---|
| Primary function | Manage maintenance activities (work orders, scheduling, spare parts) | Manage the full asset lifecycle (acquisition, operation, maintenance, depreciation, disposal) | Execute and monitor production (OEE, order tracking, quality, process data) |
| Primary user | Maintenance manager, maintenance technicians | Asset manager, finance (capex planning), maintenance manager | Production manager, shift leaders, operators, CI managers |
| ISA-95 level | Level 3 (maintenance management function) | Level 4 (enterprise, overlapping with ERP) | Level 3 (manufacturing operations management) |
| Machine connection | None. CMMS does not connect to machines. It manages the work about machines, not the data from machines. | None (same as CMMS, but with financial layer added). | Direct. MES connects to PLCs via OPC UA, native protocols, or digital I/O gateways and captures machine data in real time. |
| Knows if machine is running? | No. | No. | Yes — in real time, from PLC signals. |
| Examples | SAP PM, IBM Maximo (CMMS mode), Maintenance Connection, Limble, UpKeep, Fiix | IBM Maximo (full suite), Infor EAM, SAP S/4HANA Asset Management, Hexagon EAM | SYMESTIC, Hydra (MPDV), Cronetwork, FORCAM, iTAC, 42Q |
The critical insight: a CMMS tells you what maintenance was done. An MES tells you what happened on the machine. Neither alone gives the full picture. The CMMS knows that bearing SKF-6205 was replaced on press 5 on March 12. The MES knows that press 5 had 14 unplanned stops in the week before March 12, with alarm #3017 ("excessive vibration") occurring 37 times. Together, the data tells the story: the bearing degradation was visible in the alarm data a week before failure — next time, the MES alarm pattern can trigger the CMMS work order before the machine stops.
What are the 4 maintenance strategies and how does a CMMS support each?
| Strategy | Definition | CMMS role | MES role | Best suited for |
|---|---|---|---|---|
| Reactive (run-to-failure) | No maintenance until the asset fails. Repair or replace after breakdown. | CMMS logs the corrective work order after failure. Tracks repair cost and downtime. Over time, builds the failure history that reveals which assets should be moved to a preventive strategy. | MES records the exact duration and production impact of every unplanned stop. Provides the cost-of-failure data that justifies moving to preventive maintenance. | Non-critical, low-cost, easily replaceable assets where the cost of prevention exceeds the cost of failure. Example: indicator lights, non-critical filters. |
| Preventive (time/meter-based) | Maintenance performed at fixed intervals — calendar time or operating hours — regardless of asset condition. | CMMS schedules the work orders at defined intervals. Generates the task list, assigns technicians, tracks spare parts. This is the core strength of a CMMS. | MES provides the actual operating hours (not calendar estimates) to trigger meter-based schedules precisely. A machine that runs 2 shifts accumulates hours faster than one on 1 shift — the MES captures this automatically. | Assets with predictable wear patterns and consistent MTTF. Example: conveyor belts, hydraulic seals, timing belts, filters. |
| Condition-based | Maintenance performed when monitored parameters (vibration, temperature, current, pressure) indicate degradation — not on a fixed schedule. | CMMS receives the condition alert and creates a work order. The trigger comes from the monitoring system, not from a calendar. | MES process data module monitors the condition parameters in real time. When vibration on spindle 3 exceeds threshold, the MES generates the alert that triggers the CMMS work order. At Neoperl, SPS alarm correlation identified the degradation patterns that preceded failures. | Critical, expensive assets with high failure consequences and variable failure patterns. Example: spindle bearings, servo motors, critical pumps. |
| Predictive | Uses machine learning on historical data to predict the remaining useful life of an asset and schedule maintenance at the optimal moment — not too early (wasteful), not too late (failure). | CMMS executes the predicted work order. The prediction model tells the CMMS when and what — the CMMS handles the who, with what parts, and the documentation. | MES provides the training data for predictive models: operating hours, cycle counts, process parameters, alarm history, failure events — all timestamped and linked to specific assets. | High-value assets where the cost of both premature replacement and unplanned failure is very high. Requires 12+ months of historical data from the MES to train meaningful models. |
The progression from reactive to predictive is not a technology decision — it is a data maturity decision. Each level requires more and better data. A plant without an MES is typically stuck at levels 1 (reactive) and 2 (calendar-based preventive). Adding an MES with alarm data and process parameter capture unlocks levels 3 (condition-based) and 4 (predictive). The CMMS itself does not change — the quality of the data feeding it changes.
How does an MES feed a CMMS in practice?
The interface between MES and CMMS is where maintenance becomes data-driven. Here are the 5 data flows that matter:
| # | Data flow | Direction | What it enables | Example |
|---|---|---|---|---|
| 1 | Operating hours per machine | MES → CMMS | Meter-based preventive maintenance triggered by actual run time, not calendar guesses. | MES reports press 5 has accumulated 1,980 operating hours since last belt change. CMMS threshold is 2,000 hours. CMMS generates the work order 20 hours before the interval expires. |
| 2 | Alarm frequency per asset | MES → CMMS | Condition-based alerts: rising alarm frequency signals component degradation before failure. | MES alarm module detects that alarm #3017 on CNC-12 increased from 2/week to 14/week over 3 weeks. MES pushes a maintenance notification to CMMS: "Inspect spindle bearing on CNC-12 — vibration alarm trend." |
| 3 | Unplanned downtime events | MES → CMMS | Automatic creation of corrective work orders when the MES detects an unplanned stop with a maintenance-related reason code. | MES records an unplanned stop on machine M-007, reason code "hydraulic failure." CMMS automatically creates a corrective work order with the machine ID, failure description, and timestamp pre-filled. |
| 4 | Maintenance window availability | CMMS → MES | The CMMS schedules a maintenance window. The MES blocks the machine for production during that window, ensuring no orders are dispatched to it. | CMMS schedules belt replacement on press 5 for Saturday 06:00–10:00. MES marks press 5 as "planned maintenance" during that window. The production planning module routes orders to press 3 and 4 instead. |
| 5 | MTBF / MTTR calculation | MES + CMMS → combined | MES provides failure timestamps (when the machine stopped). CMMS provides repair timestamps (when the technician started and finished). Combined: accurate MTBF and MTTR. | MES: machine stopped at 14:23. CMMS: technician arrived at 14:41, repair completed at 15:18. MTTR for this event: 55 minutes (including 18 min response time + 37 min repair time). That 18-minute response gap is actionable — it is not visible without both systems. |
FAQ
Does SYMESTIC replace a CMMS?
No. SYMESTIC is an MES, not a CMMS. SYMESTIC captures machine data (operating hours, alarms, process parameters, OEE), tracks production orders, and provides real-time shopfloor dashboards. It does not manage maintenance work orders, technician assignments, or spare parts inventory — that is the job of a CMMS. What SYMESTIC does is provide the data that makes a CMMS dramatically more effective: actual operating hours for preventive scheduling, alarm trends for condition-based alerts, and failure timestamps for MTBF/MTTR analysis. At Neoperl, the SPS alarm correlation in SYMESTIC identified the failure patterns that the maintenance team then addressed with targeted preventive actions — a direct MES-to-maintenance workflow.
Can a CMMS work without an MES?
Yes — most CMMS installations worldwide operate without an MES. But without an MES, the CMMS operates on manual inputs and calendar-based schedules. Technicians manually create corrective work orders after a breakdown. Preventive schedules are triggered by calendar dates rather than actual operating hours. Condition-based maintenance is impossible because there is no automated condition monitoring. The CMMS still adds value (structured work order management is better than paper), but it leaves the highest-value maintenance strategies (condition-based, predictive) inaccessible.
What is the difference between CMMS and SAP PM?
SAP PM (Plant Maintenance) is the maintenance module within SAP ERP. Functionally, SAP PM is a CMMS — it manages assets, work orders, preventive schedules, and spare parts. The difference is deployment context: SAP PM is part of the SAP ERP system and shares master data (equipment, materials, cost centres) with other SAP modules (MM, CO, PP). Standalone CMMS products (Limble, UpKeep, Fiix, Maintenance Connection) are independent systems that may integrate with any ERP. For SYMESTIC customers with SAP (like Meleghy with SAP R3 or Carcoustics with SAP R3), the MES connects to SAP via ABAP IDoc for order data — and the same SAP PM module manages the maintenance work orders triggered by MES alarm data.
What KPIs should a CMMS track?
The most important CMMS KPIs for discrete manufacturing are: (1) Planned vs. unplanned maintenance ratio — target: ≥ 80 % planned. A plant at 50/50 has a reactive maintenance culture; a plant at 80/20 is proactive. (2) MTTR — how long does it take to restore a machine after failure? Decompose into response time + repair time to identify whether the bottleneck is logistics (getting the right technician and parts to the machine) or technical (the repair itself). (3) MTBF — how long between failures? Trending MTBF per machine over months reveals whether maintenance actions are actually improving reliability or just patching symptoms. (4) Maintenance cost per unit produced — connects maintenance spending to production output. All four benefit from MES data: the MES provides the precise failure timestamps and production volume that make these KPIs accurate.
Related: MTBF · MTTR · MTTF · TPM (Total Productive Maintenance) · Predictive Maintenance · OEE Explained · SYMESTIC Alarms Module · SYMESTIC Process Data · SYMESTIC Production Metrics · MES: Definition & Functions
About the author
Martin Brandel
MES Consultant at SYMESTIC. Dipl.-Ing. Nachrichtentechnik. Over 30 years in industrial automation. Has connected every conceivable machine to every conceivable system — from Simatic S5 to cloud-native MES to SAP PM — and can draw the interface diagram between MES and CMMS from memory, because he has implemented it at a dozen plants. · LinkedIn
Start working with SYMESTIC today to boost your productivity, efficiency, and quality!
