MES — Manufacturing Execution System
MES (Manufacturing Execution System) is the software layer between the ERP and the shop floor — between strategic production planning and the actual machines, operators and inspection stations. MES collects real-time data from production, executes the detailed shop-floor schedule released from ERP/APS, and reports actuals back to the ERP for costing and inventory updates.
Core MES functions
- Detailed scheduling: dispatching individual operations to machines and operators
- Shop-floor data collection (BDE): actual start/end times, scrap, rework, downtime causes — usually via touchscreen, scanner or direct machine connection
- Machine data collection (MDE): real-time signals from machines via OPC UA
- Quality management: in-line inspection, SPC charts, deviation handling
- Traceability: batch- and serial-number tracking, mandatory in pharma, food, automotive
- Tool and resource management: tool wear tracking, calibration intervals, operator certifications
MES vs ERP's native production module
Most ERP systems include a production-planning module that handles basic shop-floor data entry and dispatching. For simple assembly with few variants, this is sufficient. MES becomes necessary when: real-time machine data drives planning decisions, regulatory traceability is required (pharma GxP, automotive IATF 16949), high automation requires sub-minute scheduling, or quality data must be captured at every operation. The boundary is fluid — modern ERP vendors push their production modules upward, MES vendors push their planning capabilities downward.
Leading MES vendors
iTAC (electronics manufacturing), HYDRA by MPDV (broad installation base from automotive to food), Siemens Opcenter Execution, GE Proficy Plant Applications, AVEVA MES, SAP Digital Manufacturing. Specialised industry MES exist for pharma (Werum PAS-X), food and beverage, and aerospace. Implementation budgets typically run 100,000-1,000,000 EUR per plant.
Selection criteria for DACH mid-market buyers
- Machine-connectivity coverage: how many of your existing machines speak OPC UA, MTConnect, EUROMAP, or proprietary protocols the MES already supports out of the box? Retrofit gateways for older CNC and injection-moulding machines drive significant cost and risk.
- BDE/MDE ergonomics on the shop floor: touchscreen, barcode and RFID workflows must work in a glove-and-coolant environment. Pilot with operators on a real shift before committing — user-acceptance issues sink more MES projects than functional gaps.
- ERP-integration depth: confirm bi-directional flow for production-order release, confirmations, scrap, rework, batch links and cost postings. Out-of-the-box integration with your ERP (SAP, Microsoft Dynamics, abas, proALPHA) shortens the project by 3-6 months.
- Regulatory alignment: for pharma (GMP, EU Annex 11), medical devices (MDR, FDA 21 CFR Part 11) and automotive (IATF 16949), audit trail, e-signature and validation documentation must be native rather than bolted on.
- Reporting and OEE analytics: usable shift-leader dashboards with drill-down to downtime causes and quality losses produce more management value than abstract data-lake architectures.
Integration patterns
MES is a pivot system that integrates upward to ERP and downward to machines. Typical interface patterns: ERP ↔ MES exchanges production orders, BOM and routing snapshots, confirmations, scrap, time tickets, batch identifiers and inventory movements — most often via REST or SAP IDoc/OData. MES ↔ APS reads a finite schedule from the planning system and writes back actual progress for replanning cycles. MES ↔ machines via OPC UA, MTConnect or proprietary PLC protocols collects cycle counts, alarms, temperatures and quality measurements. MES ↔ QMS exchanges in-line inspection results, non-conformance records and CAPA links. MES ↔ WMS coordinates material staging and finished-goods movements. For DACH organisations using cloud-first stacks, see cloud ERP patterns; cloud-based MES with edge agents at each plant is becoming common.
Real-world use cases in DACH
Case 1: Bavarian automotive Tier-2 supplier, ~600 employees. Three plants producing precision-machined components. The MES (HYDRA) connects 140 CNC machines via OPC UA and operator terminals. The business value sits in real-time OEE tracking, automatic IATF 16949 traceability and a 30% reduction in unplanned downtime through trend-based maintenance prompts. ERP integration with SAP S/4HANA covers production-order release and confirmation, scrap and rework postings.
Case 2: Swiss pharma contract manufacturer, ~250 employees. Sterile-fill operation under EU GMP. The MES (Werum PAS-X) enforces electronic batch records, with e-signatures at every critical step and full chain-of-custody from raw material to finished vial. The MES is the audit anchor for FDA and Swissmedic inspections. Without it, the company could not legally serve regulated markets.
Comparable terms
MES sits in a family of shop-floor and manufacturing-IT concepts. APS handles finite-capacity scheduling that feeds MES dispatching. PPS (Production Planning und -steuerung) is the German-language umbrella often used loosely for both ERP-PP and MES functions. Industrie 4.0 and IoT-ERP describe the architectural shift in which MES becomes data-fed by edge devices. Track-and-trace and batch traceability are regulatory-driven capabilities most MES platforms cover. OPC UA is the dominant machine-connectivity protocol in modern MES deployments.
Related Topics
Frequently asked questions
What is Active Directory in simple terms?
Active Directory is Microsoft's directory service for centrally managing all users, computers, groups and permissions in Windows environments. Each employee has one AD account used to sign into the PC and many applications.
What is the difference between Active Directory and Entra ID?
Active Directory runs on-premise on Windows Servers using Kerberos/LDAP. Microsoft Entra ID (formerly Azure AD) is the cloud variant with modern standards like OAuth2/SAML — primarily for SaaS authentication and Microsoft 365.
How does an ERP integrate with Active Directory?
Classically via single sign-on: user signs into Windows, ERP automatically logs them in. AD groups map to ERP roles — permissions are managed centrally in AD and ERP picks them up.
Do I need Active Directory for a cloud ERP?
Not on-premise. Cloud ERPs like Microsoft Dynamics 365 use Microsoft Entra ID as cloud identity provider. Those with existing AD can sync via Entra Connect — users sign in everywhere with the same credentials.
What are the biggest security risks around Active Directory?
Pass-the-Hash attacks, Kerberoasting, compromised domain-admin accounts, unpatched vulnerabilities like Zerologon. Best defenses: multi-factor authentication, Tier-0 admin workstations, continuous monitoring.