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
TL;DR: Production Data Collection (PDC) is the systematic capture and analysis of all operational data on the shop floor — orders, personnel, machines, tools, and materials. It goes beyond Machine Data Collection (MDC), which only covers machine signals, but is narrower than a full MES, which adds execution, traceability, and process control. Modern PDC systems are cloud-based, modular, and capture data automatically in real time. Without PDC, manufacturers lack the data foundation for OEE calculation, cost transparency, and continuous improvement.
Transparency note: SYMESTIC is a cloud-native MES platform that includes PDC and MDC functionality. Implementation examples are from approved SYMESTIC projects.
Table of contents
- What is production data collection?
- What are the 5 types of production data?
- What are the benefits of PDC?
- PDC vs. MDC vs. MES — what is the difference?
- How did PDC systems work in the past?
- What makes a modern PDC system?
- How do you implement PDC cost-effectively?
- FAQ
What is production data collection?
Production Data Collection (PDC) is the systematic process of gathering, monitoring, and analyzing real-time manufacturing data from shop floor operations. It covers both organizational data (orders, personnel, shifts) and technical data (machine states, cycle times, tool usage, material consumption). PDC is the data foundation for every manufacturing KPI — from OEE to cost-per-unit to on-time delivery.
The concept originates from the German "Betriebsdatenerfassung (BDE)" and is standardized in frameworks like VDI 5600 and ISA-95. In practice, PDC bridges the gap between what your ERP thinks is happening and what actually happens on the shop floor.
What are the 5 types of production data?
Production data fall into five categories. Each serves a different operational purpose — and together, they create a complete picture of shop floor reality.
| # | Data type | What it captures | Why it matters | Organizational / Technical |
|---|---|---|---|---|
| 1 | Order data | Order quantities, processing times, order status, completions, confirmations back to ERP | Tracks production progress against plan. Enables on-time delivery monitoring. | Organizational |
| 2 | Personnel data | Working times, attendance, quantities per operator, shift assignments | Wage calculation, workforce planning, operator performance analysis. | Organizational |
| 3 | Machine data | Running times, stoppages, cycle times, parts produced, alarms, energy consumption | Foundation for OEE, availability tracking, and maintenance planning. Often also includes quality data for traceability. | Technical |
| 4 | Tool data | Tool usage counts, remaining life, tool changes, tool-to-part associations | Prevents quality issues from worn tools. Enables predictive tool replacement. | Technical |
| 5 | Material data | Material consumption, batch/lot tracking, stock levels, waste quantities | Supply chain visibility, material cost tracking, regulatory traceability. | Technical |
SYMESTIC implementation insight: Most manufacturers start with machine data (type 3) because it delivers the fastest ROI — OEE visibility within days. Order data (type 1) follows next, typically through ERP integration, to link machine performance to actual production orders. Personnel and tool data are added as the system matures.
What are the benefits of production data collection?
| Benefit | What it means in practice | Without PDC |
|---|---|---|
| Real-time transparency | See stoppages, deviations, and order status as they happen — not at the end of the shift | Problems found hours or days later via manual reports |
| Higher efficiency | Historical data analysis reveals systematic losses. Root causes become visible and addressable. | Improvement efforts based on gut feeling |
| Precise costing | Direct cost assignment to orders, machines, and shifts. True cost-per-unit becomes calculable. | Overhead-based estimates that hide unprofitable products |
| Optimal resource planning | Reliable data on availability, performance, and quality (OEE) enables data-driven capacity decisions | Capacity decisions based on theoretical calculations |
| Regulatory compliance | Complete production history for traceability, batch tracking, and audit readiness | Paper-based records with gaps and delays |
| Foundation for digitalization | PDC is the data layer for every downstream system — OEE dashboards, digital shopfloor management, predictive maintenance, AI | Digital tools without a reliable data source |
PDC vs. MDC vs. MES — what is the difference?
| Dimension | MDC (Machine Data Collection) | PDC (Production Data Collection) | MES |
|---|---|---|---|
| Scope | Machine signals only | Machine + organizational data | Full production management |
| Data types | Cycle times, stoppages, counts | + Orders, personnel, tools, material | + Traceability, quality mgmt, scheduling |
| Standard | — | VDI 5600 (partial) | ISA-95, VDI 5600 |
| Typical use case | OEE monitoring, downtime tracking | Order tracking, cost analysis, shift reports | Full production control & optimization |
| Relationship | Subset of PDC | Subset of MES | Superset — includes PDC + MDC |
In practice, the boundaries are fluid. Cloud-native platforms like SYMESTIC start with MDC (machine connectivity and OEE), expand to PDC (order and personnel data via ERP integration), and scale to full MES (production control, traceability, quality) — all within the same platform.
How did PDC systems work in the past?
Traditional PDC systems relied on proprietary terminals on the shop floor, connected to locally installed databases. Data was entered manually by operators, processed in batch mode, and exchanged with ERP systems through custom interfaces.
The weaknesses of this architecture are well documented: high upfront investment (typically six-figure sums), long implementation timelines (12–18 months), rigid data structures that could not adapt to changing production requirements, and data quality issues from manual entry. Worse, many legacy systems are still in use today — creating data silos that prevent cross-plant analysis.
What makes a modern PDC system?
| Characteristic | What it means | Why it matters |
|---|---|---|
| Cloud-native / SaaS | No local installation. PDC as a service, accessible from any browser. | Eliminates capital investment. Go-live in days, not months. Automatic updates. |
| Modular architecture | Start with machine data, add order tracking, quality, scheduling as needed. | Scales with your needs. No upfront commitment to features you don't use yet. |
| Open connectivity | OPC-UA, MQTT, REST API, digital I/O — connects to any machine and any IT system. | No vendor lock-in. Integrates with SAP, Infor, proAlpha, and other ERP systems. |
| Real-time processing | Data captured, processed, and visualized in seconds — not batch mode. | Enables immediate response to deviations. Makes shift-level improvement possible. |
| Enterprise-grade security | Data encryption, role-based access, Azure Active Directory integration, ISO 27001. | Meets corporate IT requirements without on-premise infrastructure. |
How do you implement PDC cost-effectively?
The traditional approach — 12-month project, six-figure budget, extensive requirements gathering before a single machine is connected — is no longer necessary. Cloud-native PDC platforms fundamentally change the implementation model.
| Phase | Timeline | What happens |
|---|---|---|
| 1. Connect first machines | Days 1–5 | Install edge gateway, connect 1–3 pilot machines via digital signals or OPC-UA. First data visible in dashboards. |
| 2. Validate & expand | Weeks 2–4 | Configure downtime categories, validate data against shop floor reality. Connect remaining machines. |
| 3. Integrate ERP | Weeks 4–8 | Bidirectional ERP connection (SAP IDoc, REST API, file-based). Map machine cycles to production orders. |
| 4. Scale & optimize | Ongoing | Add plants, activate additional modules (quality, scheduling, traceability). The team expands the system independently using the modular toolkit. |
Example from SYMESTIC implementations: Meleghy Automotive scaled from one plant to six plants across Germany, Czech Republic, and Hungary within 6 months. Bidirectional SAP R3 integration via ABAP IDoc maps machine cycles to production orders in real time. Results: 10 % fewer stoppages, 7 % higher output, 5 % better availability. Klocke Pharma went from one packaging line to full plant coverage in just 3 weeks — gaining 7 hours of additional productive time per week.
For product details: → Production Metrics · → Production Control
FAQ
What is production data collection (PDC)?
PDC is the systematic capture of all operational data from the shop floor — orders, personnel, machines, tools, and materials. It creates the data foundation for OEE, cost analysis, and continuous improvement. The German equivalent is "Betriebsdatenerfassung (BDE)".
What is the difference between PDC and MDC?
Machine Data Collection (MDC) captures only machine-generated signals: cycle times, stoppages, counts. PDC is broader — it adds organizational data like order status, personnel times, and material consumption. MDC is a subset of PDC.
What is the difference between PDC and MES?
An MES (Manufacturing Execution System) includes PDC plus additional functions: production scheduling, traceability, quality management, and process control. PDC is the data collection layer; MES is the full execution layer. The ISA-95 standard defines the MES scope.
How long does it take to implement PDC?
With cloud-native platforms, first machines can be connected within days and full plant coverage achieved within weeks. Traditional on-premise systems typically require 12–18 months. The difference is architecture: cloud SaaS eliminates server installation, database setup, and network configuration.
What does a PDC system cost?
Cloud-based PDC starts at EUR 500/month. On-premise systems typically require six-figure upfront investments. The total cost depends on machine count, required integrations (ERP, quality systems), and scope of modules.
The bottom line: Production data collection is not a technology project — it is the foundation for data-driven manufacturing. Start with machine data for immediate OEE visibility, add order data for cost transparency, then scale to full production control. The best time to start was yesterday. The second best time is today.
→ What is an MES? · → Machine Data Collection · → OEE Explained · → OEE Software · → MES Software
About the author
Martin Brandel
MES Consultant & Automation Project Manager, SYMESTIC · Dipl.-Ing. Communications Engineering · 30+ years in industrial automation & machine connectivity · LinkedIn
Start working with SYMESTIC today to boost your productivity, efficiency, and quality!
