Manufacturing Execution System, MES.

A manufacturing execution system is the software layer that sits between the BPCS and the ERP, executing production orders, tracking work-in-progress, recording genealogy, and enforcing electronic batch records. MES is the L3 layer in the ISA-95 model and the layer most likely to anchor a digital-transformation project in process manufacturing.

Upload a drawing Pricing

Part ofGlossary

What Manufacturing Execution System, MES means.

A manufacturing execution system is the software layer between the plant-floor controllers and the enterprise business systems, and in the ISA-95 model it is Level 3, the bridge between the OT world below it and the IT world above. Its job is everything that sits between an order arriving from ERP and a finished, released batch. It schedules the order to an equipment train, triggers the recipe in the control system, records the live process data and the operator's manual entries and exceptions as the batch runs, assembles the electronic batch record that quality reviews and releases, and tracks the genealogy that ties every unit of input to every unit of output. In process manufacturing the batch-record and genealogy functions dominate, and in regulated industries they are usually the reason an MES is bought at all. 21 CFR Part 11 and EU Annex 11 require electronic records and signatures where electronic records replace paper, and past a few hundred batches a year paper review becomes the bottleneck on production release. The MES does not own its own measurements. Every tag it historizes or displays comes from the controller tag database, which is built from the I/O list. A tag missing or misclassified at that foundation is a tag missing from the MES historian, so the data-integrity gap an incomplete I/O list creates propagates all the way up to the batch record.

What an MES does day-to-day

Receives production orders from ERP. Schedules them to equipment trains. Triggers batch execution in the BPCS, via ISA-88 recipe download. Records the live process data, manual operator entries, and exceptions during execution. Produces an electronic batch record for review and release. Tracks WIP genealogy, OEE, downtime causes, and quality metrics. Feeds production results back to ERP. The role differs in discrete and process. In process manufacturing, the batch-record and genealogy functions dominate.

Common MES platforms

Aveva MES, formerly Wonderware, Siemens Opcenter Execution, Honeywell MEP, Rockwell FactoryTalk ProductionCentre, GE Proficy, Werum PAS-X, pharma-specific. Pharma also runs custom-built MES on Pi-or-equivalent stacks. The ROI driver is consistent. Cut the cycle time on batch record review, eliminate paper, and feed production data to higher-level systems automatically.

Common questions

Do you need an MES if you have a DCS.

Not always, but in regulated industries, pharma, food the answer is usually yes. The DCS handles equipment-level execution. The MES handles the order, recipe, batch-record, and genealogy layer that the DCS does not natively manage. Plants without an MES typically maintain those records on paper or in spreadsheets, which the audit regimes don't accept beyond a certain scale.

How does the I/O list relate to the MES tag database.

Every MES tag is sourced from the BPCS tag database, which is sourced from the I/O list. A clean controls-extraction dataset is a precondition to a clean MES configuration. Tags missing from the I/O list become tags missing from the MES historian. Data integrity gaps cascade upward.

What triggers a pharmaceutical plant to implement an MES versus managing with paper batch records.

Regulatory scale and audit frequency. 21 CFR Part 11, US FDA and EU Annex 11 require electronic records and electronic signatures for processes where electronic records replace paper. Beyond a few hundred batches per year, paper batch-record review becomes the production-release bottleneck, and regulators increasingly scrutinize review-by-exception practices on paper. An MES replaces the paper and can enforce the review workflow electronically.

Run it on your drawings.

Upload a drawing set, get every document populated and classified, export to the format your team uses.