Manufacturing execution systems (MES) occupy the ISA-95 level between the plant floor and the enterprise: the software that executes, records and reports production as it happens. The discipline covers production tracking, shop floor control, OEE tracking, batch management and the wider manufacturing operations management functions that connect work orders from ERP to the machines, operators and materials that fill them. It is a growth market built on modernization: ABI Research puts global MES software spending at USD 20.7 billion in 2025, rising to USD 40.3 billion by 2035 at a 6.9 percent compound annual rate . ARC Advisory Group describes modern MES and MOM platforms as a central focus of digital transformation, IT/OT convergence and cloud adoption in manufacturing, with low-code platforms and AI-assisted operator advisors driving the next generation .
Challenges in Manufacturing Execution Systems Recruiting
Manufacturing operations management spans the ISA-95 level 3 boundary
ISA-95 organizes the enterprise into levels, and everything MES does lives in the space between them. Level 3 is manufacturing operations management: the activity models defined in Part 3 of the standard, covering production operations management, product definition management and production resource management, with the goal of reducing the cost and errors of the interface to the level 4 business systems . The MESA lineage maps the same ground from the practitioner side, from the eleven core functions of the 1996 MESA-11 model to the collaborative MES model that added integration with the surrounding enterprise . Hiring splits along that boundary. Some candidates model operations; others have configured one vendor's platform against a plant that already had a model. The first group can design the level 3 space for a new site. The second group ships faster inside an existing architecture. A job brief that says only "MES experience" will not tell you which one you are interviewing.
ERP-MES integration dies on master data, not connectors
ARC's research across 600 end users in 16 industries found IT organizations treating MES as the single source of truth that feeds dashboards comparing shop floor reality against business metrics . The integration work that makes that true is master data. Item masters, bills of material, routings, work centers and units of measure must mean the same thing on both sides of the ISA-95 level 3 to level 4 interface, or every transaction downstream is poisoned . The engineer who has run a real ERP-MES integration can describe the data objects they harmonized, the plant model they maintained, and where they drew the transaction boundary. The engineer who has only watched one will talk about connectors and APIs. This is the most common oversell in the discipline, because the vocabulary is shared between both populations.
Production tracking fragments by product genealogy
Production tracking means different things in different industries, and the difference is genealogy: which raw material lot went into which finished serial or batch, through which equipment, operated by whom. ISA-95 part 3 defines the production tracking activities that sit inside production operations management . A pharmaceutical plant records lot-level history for regulatory release; a discrete plant tracks serials through test stations; a food plant needs forward and backward traceability for recall containment. The same "production tracking" keyword covers all three. A candidate whose genealogy experience is a serial counter on a packaging line does not transfer into a plant where the tracking record is a release document, and the reverse is just as true. Scale changes the craft again: tracking a hundred units a day on one line is a database problem, tracking thousands across twenty lines with rework loops is an event modeling problem. The brief has to name the product record that matters before the CV can be read against it.
Batch management answers to electronic batch records
Batch management is the ISA-88 side of the discipline. The standard defines the procedural model, recipes with unit procedures and operations, and the production information that batch control must capture . Part 4 turns that into a reference model for batch production records: batch history entries, events, data sets, comments, samples, and manifests covering personnel and resource qualification, so that a record supports compliance, validation and audit . The skill that separates the field is deviation handling. A batch specialist knows how exceptions were logged, what the auditors accepted, and how a record was reconstructed after a failed unit operation. Pharma, chemical and food plants hire on exactly that evidence, and the population that owns it is small and concentrated in a few process regions.
OEE tracking definitions vary before the dashboard does
OEE tracking looks standardized and is not. Availability, performance and quality multiply cleanly in the textbook, but the plant time model decides what counts: whether planned maintenance is excluded from availability, how changeover time is allocated, which losses sit in the tree and which reason codes operators are allowed to pick. MESA's classic function set treated performance analysis as a core MES capability precisely because the definitions are plant-specific . A candidate who built a dashboard on someone else's time model has done reporting; a candidate who changed a time model and watched the OEE number move has done analysis. The difference shows up in the questions they ask back: which loss buckets exist, how micro-stops are separated from breakdowns, and what happened to the number when shift patterns changed.
Shop floor control separates operators from configurators
Shop floor control is the operator-facing half of the system: dispatch lists, work instructions, data collection terminals, and the flows that move a unit through its routing. ARC notes that manufacturing visualization is advancing from HMI/SCADA screens toward enterprise visualization, with dashboards personalized to distinct roles and skill levels . That shift pulls two different people into one title. The configurator builds and maintains the flows, screens and permissions; the operator-support engineer keeps the system usable under production pressure and fixes what breaks mid-shift. One is an engineering role, the other closer to product ownership of a live system. Conflating them produces hires who can build a flow but cannot keep a shift running, or who keep a shift running but cannot extend the model when a new line arrives.
Genealogy and reason codes expose inflated production tracking claims
The verification probes for this discipline are model-specific. Which activity model did the candidate map their project to, and what did the plant model contain . For an ERP-MES integration: which master data objects they harmonized and where the transaction boundary sat . For batch management: how deviations and exceptions were recorded, and whether the electronic batch record survived an auditor's review . For OEE tracking: which losses they classified and what changed in the time model as a result . The cost of a miss here is paid later than in most disciplines. A genealogy gap surfaces in an audit finding or a recall whose scope cannot be bounded, and the rework runs to months because the record for the affected period cannot be recreated. The false negative is equally real: an ERP consultant with five years inside one plant often carries more integration sense than a certified MES tool specialist, and screening on platform keywords alone throws that hire away.
References
- Manufacturing Execution Systems (MES) Market Value — ABI Research. (accessed 2026-09-28)
- Digital Transformation Drives Manufacturing Execution Systems for Discrete Adoption — ARC Advisory Group. (accessed 2026-09-28)
- ISA-95 Standard: Enterprise-Control System Integration — International Society of Automation (ISA). (accessed 2026-09-28)
- MESA Model: A Framework for Smarter Manufacturing — MESA International. (accessed 2026-09-28)
- ARC Advisory Group Sees Rising Interest in Virtual Controllers, MES in the IT/OT Convergence, and Operational Resiliency — Automation World. (accessed 2026-09-28)
- ISA-88 Series of Standards - Batch Process Control — International Society of Automation (ISA). (accessed 2026-09-28)
- ANSI/ISA-88.00.04-2006, Batch Control Part 4: Batch Production Records — International Society of Automation (ISA). (accessed 2026-09-28)