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.
The Internet of Things (IoT) refers to the networking of physical devices, sensors, and machines that communicate, exchange data, and execute actions in real time via the internet or local networks. In a manufacturing context, IoT is the technology layer that connects production equipment to software systems, enabling real-time visibility into machine states, process parameters, and production performance.
For manufacturing companies, IoT is not a futuristic concept. It is the infrastructure that makes OEE monitoring, automated downtime tracking, and real-time production dashboards technically possible. Without IoT connectivity at the machine level, there is no real-time data, and without real-time data, there is no data-driven production management.
| Dimension | IoT (Internet of Things) | IIoT (Industrial Internet of Things) |
|---|---|---|
| Definition | Broad term for all connected devices: consumer products, smart homes, wearables, connected cars, smart cities. | Subset of IoT focused on industrial applications: machine connectivity, production monitoring, predictive maintenance, quality control. |
| Typical devices | Smart speakers, thermostats, fitness trackers, connected appliances. | IoT gateways, PLCs, OPC UA servers, digital I/O modules, industrial sensors, edge devices. |
| Data volume | Low to moderate. Intermittent data from consumer devices. | High. Continuous streams from hundreds or thousands of machines. Cycle times, counts, alarms, process parameters at sub-second intervals. |
| Reliability requirements | Moderate. A missed smart-home event is an inconvenience. | Critical. A missed machine signal can mean undetected downtime, quality defects, or production loss. |
| Protocols | Wi-Fi, Bluetooth, Zigbee, Z-Wave. | OPC UA, MQTT, Modbus, PROFINET, EtherNet/IP, EUROMAP (for injection molding). |
| Security | Consumer-grade encryption. Often weak default passwords. | Industrial-grade security. TLS encryption, certificate-based authentication, network segmentation, IT/OT firewalls. |
When manufacturers talk about "IoT in production," they mean IIoT: the industrial-grade connectivity infrastructure that connects machines to MES, ERP, and analytics platforms. The rest of this article focuses on IIoT in manufacturing.
| Layer | What it does | Typical components |
|---|---|---|
| 1. Production assets | The physical machines, lines, and equipment that produce goods. They generate signals: cycle counts, alarms, process values, part status. | Presses, CNC machines, injection molding machines, packaging lines, assembly stations, welding robots. |
| 2. Connectivity (IoT gateways) | Captures machine signals and translates them into structured data. Bridges the gap between OT (operational technology) and IT. | IoT gateways with digital inputs (DI), analog inputs (AI, 4-20 mA), OPC UA clients, MQTT publishers. LTE, Wi-Fi, or Ethernet uplink. |
| 3. Edge / data transformation | Pre-processes data locally before sending it to the cloud. Filters noise, aggregates signals, buffers data during connectivity gaps. | Edge gateways, local OPC UA servers, protocol converters, data buffering logic. |
| 4. Cloud platform | Stores, processes, and analyzes production data at scale. Provides real-time dashboards, KPI calculations, alerting, and reporting. | Cloud-native MES, time-series databases, analytics engines, REST APIs for ERP integration. |
| 5. Manufacturing applications | The user-facing layer: dashboards, OEE monitors, downtime analyzers, order tracking, traceability reports, alarm management. | Web-based MES applications, mobile apps, shopfloor clients, management dashboards. |
The biggest practical challenge in any IIoT project is not the cloud platform or the analytics. It is getting data out of the machines reliably, without disrupting production, and without requiring months of integration work.
| Machine type | Connectivity method | What gets captured | Integration effort |
|---|---|---|---|
| Modern machines with OPC UA | OPC UA client connects to the machine's built-in OPC UA server. No PLC modification needed. | Cycle times, part counts, alarms, process parameters (temperatures, pressures, speeds), machine states. | Low. Configuration only. 2 to 4 hours per machine. |
| Machines with PLC but no OPC UA | IoT gateway reads digital output signals from the PLC (cycle complete, machine running, alarm active). No PLC code change. | Cycle counts, running/stopped status, alarm states. Process data limited to what is available as digital or analog output. | Low. Wiring of digital signals to IoT gateway. 2 to 4 hours per machine. |
| Legacy machines without digital interface | Digital I/O gateway with sensors: light barriers for cycle detection, current sensors for running/stopped, stack light tapping for status. | Cycle counts, running/stopped, basic alarm detection. No process parameters without additional sensors. | Low to moderate. Sensor installation and wiring. No PLC access needed, no production interruption. |
| Injection molding machines (EUROMAP) | EUROMAP 63/77 interface provides standardized machine data exchange for injection molding machines. | Shot counts, cycle times, mold data, process parameters (injection pressure, melt temperature, clamping force). | Low. Standardized protocol. Configuration at gateway level. |
The key principle: no PLC intervention, no production interruption, no months-long integration project. Every machine can be connected, regardless of age or manufacturer, if the right connectivity approach is chosen.
| Protocol | What it is | Typical use in manufacturing | Strengths |
|---|---|---|---|
| OPC UA | Open Platform Communications Unified Architecture. Platform-independent, service-oriented architecture for machine-to-machine and machine-to-cloud communication. | Modern PLCs (Siemens, Beckhoff, Wago), line controllers, packaging machines. The de facto standard for Industry 4.0 machine connectivity. | Rich data model (not just values, but context). Built-in security (TLS, certificates). Vendor-independent. Standardized by IEC 62541. |
| MQTT | Message Queuing Telemetry Transport. Lightweight publish/subscribe protocol optimized for low-bandwidth, high-latency, and unreliable networks. | IoT gateways publishing machine data to cloud brokers. Edge-to-cloud communication. Multi-site data aggregation. | Extremely lightweight. Low bandwidth requirements. Works over LTE/cellular. Ideal for brownfield environments without LAN infrastructure. |
| Digital I/O | Direct electrical signal capture: 24V digital inputs and 4-20 mA analog inputs on IoT gateways. No protocol layer, pure signal-level connectivity. | Legacy machines without any digital interface. Cycle detection via light barriers. Status detection via current sensors or stack light signals. | Works on any machine, regardless of age. No PLC access needed. No software dependency. Lowest integration barrier. |
| Function | What it does | How SYMESTIC implements it |
|---|---|---|
| IoT gateway connectivity | Captures machine signals (digital inputs, analog inputs) and transmits them to the cloud platform. No LAN infrastructure required. | DI-Gateway: 6x digital inputs, 2x analog inputs (4-20 mA), LTE/Ethernet/Wi-Fi uplink. Third-party IoT gateways supported (e.g., IXON via MQTT). |
| OPC UA cloud connector | Connects to modern PLCs and line controllers via OPC UA. Captures rich process data, alarms, and machine states without PLC code changes. | OPC UA Cloud Connector included in Professional and Enterprise tiers. Standard integration for Siemens, Beckhoff, Wago, Rademaker, König, Optima lines. |
| Cloud-native data processing | Processes incoming machine data in real time. Calculates KPIs (OEE, availability, performance, quality), detects downtimes, triggers alarms. | Microsoft Azure infrastructure. Microservice architecture. Auto-scaling. 99.9% platform availability. Automatic updates included in SaaS subscription. |
| Bidirectional ERP integration | Production data flows from machines via IoT gateways to the MES and back to the ERP. No manual reporting at shift end. | SAP R3 (ABAP IDoc), InforCOM (file interface), Navision. REST API for third-party systems. Automatic backflush of quantities, times, and statuses. |
| Multi-site scalability | Same IoT infrastructure scales from one machine to hundreds of machines across multiple plants and countries. | Flat rate per plant. Unlimited users, unlimited dashboards, unlimited shopfloor clients. Meleghy Automotive: 6 plants in 6 months. Carcoustics: 500+ machines across 7 countries. |
At Klocke (pharmaceutical packaging), all lines were connected via DI-Gateways without any LAN infrastructure, using cellular connectivity. The result: 7 additional hours of production time per week, 12% output improvement, and 8% availability improvement within 3 weeks of deployment.
At Carcoustics (automotive, 500+ machines), OT integration was implemented via IXON IoT devices and the MQTT protocol into Microsoft Azure, enabling company-wide performance analysis across plants in Germany, Poland, Slovakia, Czech Republic, Mexico, USA, and China.
| Use case | What IIoT enables | Typical result |
|---|---|---|
| Real-time OEE monitoring | Automatic capture of availability, performance, and quality data per machine. No manual data entry. No shift-end paper reports. | 5 to 15% OEE improvement within the first 12 weeks through visibility alone. |
| Automated downtime tracking | Machine stop detected automatically via digital signal or OPC UA. Duration, timestamp, and machine ID logged without operator intervention. | 10% downtime reduction (Meleghy Automotive). 10% fewer stops (Neoperl). |
| Alarm correlation | PLC alarms captured via OPC UA or digital signals. Correlated with downtimes and quality defects to identify root causes. | 15% less scrap through quality data analysis (Neoperl). |
| Energy monitoring | Analog inputs (4-20 mA) on IoT gateways capture energy meter data per machine. Identifies peak loads and inefficient operating states. | 5 to 10% energy consumption reduction through targeted measures and transparency. |
| Traceability | IoT-captured process data (temperatures, pressures, cycle times) linked to individual parts or batches. Complete production history per product. | 3 to 7% faster defect isolation. Audit-ready traceability reports in minutes instead of hours. |
| Predictive maintenance | Continuous monitoring of process parameters (vibration, temperature, pressure trends) enables detection of degradation before failure occurs. | 5 to 10% fewer unplanned breakdowns through condition-based maintenance. |
What is the difference between IoT and IIoT?
IoT (Internet of Things) is the broad term for all connected devices, including consumer products like smart speakers and fitness trackers. IIoT (Industrial Internet of Things) is the subset focused on industrial applications: machine connectivity, production monitoring, process data capture, and real-time analytics. IIoT has stricter requirements for reliability, data volume, security, and latency than consumer IoT.
Do legacy machines without digital interfaces work with IIoT?
Yes. IoT gateways with digital inputs can capture signals from any machine, regardless of age or manufacturer. Light barriers detect cycles, current sensors detect running/stopped states, and stack light signals provide basic status information. No PLC access is needed, and no production interruption occurs during installation.
What is OPC UA and why does it matter?
OPC UA (Open Platform Communications Unified Architecture) is the industry standard protocol for machine-to-machine and machine-to-cloud communication in manufacturing. It provides a rich, vendor-independent data model with built-in security. Modern PLCs from Siemens, Beckhoff, Wago, and others include OPC UA servers as standard. OPC UA is the de facto connectivity standard for Industry 4.0.
How long does it take to connect a machine to a cloud MES via IoT?
For machines with OPC UA: 2 to 4 hours per machine, configuration only, no PLC code changes. For machines connected via digital I/O gateways: 2 to 4 hours per machine, including wiring of signals. For an entire plant with 10 to 50 machines: typically 1 to 4 weeks, depending on machine heterogeneity and connectivity method.
What role does an MES play in an IIoT architecture?
The MES is the application layer that turns raw IoT data into actionable information. IoT gateways capture signals, but the MES calculates KPIs (OEE, availability, performance, quality), detects and classifies downtimes, manages production orders, provides traceability, and generates reports. Without an MES, IoT data is just data. With an MES, it becomes production intelligence.
MES software compared: vendors, functions per VDI 5600, costs (cloud vs. on-premise) and implementation. Honest market overview 2026.
OEE software captures availability, performance & quality automatically in real time. Vendor comparison, costs & case studies. 30-day free trial.
MES (Manufacturing Execution System): Functions per VDI 5600, architectures, costs and real-world results. With implementation data from 15,000+ machines.