Know a company with years of records? Refer it and earn up to $100K
Manufacturing resource

Manufacturing Execution System (MES): What It Is and Does

What a manufacturing execution system (MES) does, the ISA-95 levels, what MES data it records, how it differs from ERP and SCADA, and how to export it.

Short answerChecked

A manufacturing execution system (MES) is the plant-floor software that runs and records production between business planning and machine control. It releases work orders to lines, tracks materials and lots, guides operators, collects counts, downtime and quality results, and keeps the history of every unit or batch. In the ISA-95 model it sits at Level 3, between ERP at Level 4 and the PLCs and control systems at Level 2.

ISA-95 level
Level 3manufacturing operations management
International standard
IEC 62264the IEC edition of ISA-95
Functions listed by NIST
11from scheduling to performance analysis
A laptop showing a code diff with a sprint board behind
Key points
  • An MES runs and records production at ISA-95 Level 3, between ERP (Level 4) and machine control (Level 2).
  • Its core records are work orders, genealogy, quality results, downtime and labor, tied to units and lots.
  • Integration runs two ways: machine data in (OPC UA, MTConnect, operator entry), and orders and results to and from ERP.
  • Before you replace an MES, export its history with the keys and audit trails in an open format.

What is a manufacturing execution system (MES)?

A manufacturing execution system (MES) is the software that runs and records production on the plant floor. It takes the orders planned in the business system, releases them to lines and work centers, tells operators what to build and how, and records what actually happened: quantities, materials and lots used, machine states, downtime, test results and who did each step. NIST's manufacturing extension partnership puts it simply: "An MES is manufacturing operations management software that accounts for inputs and outputs" (NIST). An "MES system" is the same thing; the S already stands for system.

The standards call this layer manufacturing operations management, or MOM. The main reference is ISA-95, which ISA describes as "an international set of standards aimed at integrating logistics systems with manufacturing control systems" (ISA). Its international edition, IEC 62264, says Part 1 "describes the manufacturing operations management domain (Level 3) and its activities, and the interface content and associated transactions within Level 3 and between Level 3 and Level 4" (IEC 62264-1:2013).

An ISA history of the standard notes that its Parts 3 and 4 "formally defined the level 3 space, creating the term "manufacturing operations management"" (ISA InTech, 2020). In practice MOM is the wider term for everything at Level 3, and MES usually means the software that executes production within it. Many plants and suppliers use the two words for the same system, so check which functions a product actually covers.

What does an MES system do?

A 2016 paper in NIST's Journal of Research lists eleven functions for the MES category: "Resource Allocation and Status; Operations/Detail Scheduling; Dispatching Production Units; Document Control; Data Collection/Acquisition; Labor Management; Quality Management; Process Management", and "Maintenance Management; Product Tracking and Genealogy; Performance Analysis" (NIST Journal of Research). Few plants use all eleven. What each means on the floor:

FunctionWhat it does on the floorRecord it leaves
Resource allocation and statusTracks machines, tools, people and materials and whether they are availableEquipment and tool status history
Operations and detail schedulingSequences orders on each line or machine, shift by shiftPlanned versus actual schedule
Dispatching production unitsReleases work orders and batches to the floorOrder release and start times
Document controlShows the current work instruction, drawing or recipe at the stationWhich revision was used for each unit
Data collection and acquisitionCollects counts, times, readings and operator entriesProduction and process data by order
Labor managementRecords who worked on what, and their qualificationsOperator and time records
Quality managementRuns in-process checks and holds nonconforming productInspection results, holds and dispositions
Process managementWatches the process and directs operators when it driftsAlarms, deviations and interventions
Maintenance managementTracks equipment condition and planned and unplanned workDowntime reasons and maintenance events
Product tracking and genealogyFollows each unit, lot or batch through every stepAs-built history: materials, machines, people, results
Performance analysisCompares actual results with targetsOutput, yield, scrap and equipment effectiveness reports

NIST adds that an MES lets a company "acquire the real-time data needed to recognize when a defect or inefficiency occurs", and that "An MES can serve as a Quality Management System or a scheduling system" (NIST). For the quality records an MES often starts, see the non-conformance report template and the 8D report example.

Where does MES sit in the ISA-95 levels?

ISA-95 sorts plant and business systems into five levels. It "relies on the well-known Purdue Reference Model for computer-integrated manufacturing", and "Its scope prioritizes activities, not technologies" (ISA). The levels, as ISA describes them:

LevelWhat happens thereTypical systems
Level 4: Business planning and logisticsRunning the business: orders, planning, inventory, financeEnterprise resource planning (ERP)
Level 3: Manufacturing operations managementRunning production: dispatching, tracking, quality, maintenance, performanceMES and other operations systems
Level 2: Monitoring and supervising controlSupervising the process minute by minutePLCs, distributed control systems, operator screens
Level 1: Sensing and manipulatingMeasuring and acting on the processSensors, smart devices, valves
Level 0: Physical processThe production process itselfMachines and material

ISA says "Level 3 describes manufacturing execution systems (MES) and other systems such as supervisory control and data acquisition (SCADA) that manage manufacturing operations", while Level 2 "refers to programmable logic controllers (PLCs), distributed control systems (DCSs) and other control devices" (ISA). An earlier ISA article places SCADA functions at Level 2 (ISA InTech, 2017). SCADA sits on the line between the two: its screens supervise control, and its history feeds operations.

The standard's main job is the boundary between Level 3 and Level 4: "The ISA-95 standard primarily deals with the interface between levels 3 and 4." Part 5 "defines transactions in terms of information exchanges between applications performing business and manufacturing activities associated with levels 3 and 4 of the ISA-95 model" (ISA).

What is the difference between MES, ERP and SCADA?

They answer different questions on different clocks. ERP decides what to make and when, in days and weeks. An MES runs today's orders and records what happened, in shifts and minutes. SCADA and PLCs control and watch the machines, in seconds and less.

ERPMESSCADA and PLCs
ISA-95 levelLevel 4Level 3Level 2 (ISA also lists SCADA at Level 3)
Time scaleDays, weeks, monthsShifts, hours, minutesSeconds and less
Main questionWhat to make, buy and shipHow the orders run, and what was madeIs the process in control right now?
Typical recordsSales and purchase orders, inventory, costsWork orders, lot genealogy, test results, downtime, laborTag values, alarms, events
Unit of recordOrder and itemUnit, lot or batch at each operationSignal and timestamp

The systems overlap. The NIST paper notes that "ERP and MES manage resource information related to the factory operation including real-time status" (NIST Journal of Research), and NIST's extension partnership explains that "An MES collects data from many components, so it can feed data into an Enterprise Resource Planning (ERP) system" (NIST). Decide which system owns each piece of data, such as the schedule, inventory or a quality hold, before you connect them.

What data does an MES record?

MES data is the as-run record of production, tied to orders, units and lots. The common types:

MES dataExample fieldsUsually comes from
Work order executionOrder, operation, start and end times, good and scrap countsOperator entries, machine counters
Genealogy and traceabilitySerial or lot number, component lots consumed, station, operatorBarcode or RFID scans
Quality resultsMeasurement, specification limits, pass or fail, hold and dispositionGauges, test stands, inspectors
Equipment states and downtimeRunning, idle or down, reason code, durationMachine signals plus operator reason codes
Process parametersSetpoints and actual values for each lotPLCs and control systems
LaborWho did each step, time on the job, training statusBadge scans and logins
Electronic batch or device history recordEvery step, material, check and signature for a batch or unitAll of the above, compiled

In regulated plants the MES record is often the legal production record. For drugs, FDA rules say "Batch production and control records shall be prepared for each batch of drug product produced and shall include complete information relating to the production and control of each batch", including the "Identity of individual major equipment and lines used" and "A statement of the actual yield and a statement of the percentage of theoretical yield at appropriate phases of processing" (21 CFR 211.188). Electronic records also need "secure, computer-generated, time-stamped audit trails" of operator entries and changes (21 CFR 11.10). This page is general information, not legal advice.

How does MES integration and production data collection work?

An MES has two sets of connections: down to the machines and up to the business systems.

  • Machine and production data collection. In older plants, manufacturing data collection relies on operator entry and barcode scans. Newer plants read machines directly: NIST names MTConnect and OPC UA as "other standards in the MES area for collecting data from machine tools" (NIST Journal of Research). The OPC Foundation describes OPC UA, "released in 2008", as "a platform independent service-oriented architecture", whose subscriptions "report-by-exception when values change" (OPC Foundation).
  • ERP integration. ISA-95 gives both sides a shared vocabulary for the information that crosses between them; NIST notes that "In the MES area, there is the ANSI/ISA-95 enterprise-to-control-system integration standard" (NIST Journal of Research). Production orders and material lists usually flow down, and confirmations, material use and quality results flow back up.
  • Maintenance, quality and historian links. The quality system takes inspection results and holds, the maintenance system takes downtime and equipment condition, and a process historian keeps second-by-second values. ISA-95's asset model was added to support "integrating production and maintenance activities" (ISA InTech, 2020). For downtime and repair records, see the maintenance log template.
  • Historical data. When you replace or add an MES, NIST suggests asking: "will the provider be able to upload all their historical data into the system?" (NIST).

Small plants often start without one. NIST observes that "In many cases, SMMs are missing the comprehensive production data collected by an MES" (NIST), meaning small and medium-sized manufacturers. Supplier quality records such as PPAP submissions usually live outside the MES and link to it by part number.

How do you export data from an MES?

Most systems offer three routes: built-in reports saved as CSV or Excel files, read-only database views or a reporting database, and the integration interface itself (ISA-95 style messages or an API). For a full export, such as before a system change or a site closure, plan it like this:

  • List the record types you need: orders, genealogy, quality results, downtime, labor and audit trails.
  • Export the master data with them: product, routing, equipment and reason-code lists, so the codes can be read later.
  • Keep the keys on every row: order number, serial or lot number, operation and equipment ID, so the records still join.
  • Include revision history and audit trails, not only the latest values.
  • Save in an open format such as CSV or JSON, with a short data dictionary that explains each column.
  • Check a sample against the MES screens before you trust the full export.

Regulated records add rules. FDA requires systems that hold electronic records to have "The ability to generate accurate and complete copies of records in both human readable and electronic form" (21 CFR 11.10), and drug batch records must be "retained for at least 1 year after the expiration date of the batch" (21 CFR 211.180). Read the retention rules for your products and customers before you retire a system.

MES data example: one work order, start to finish (illustration)

An illustrative event trail for a fictional order of 500 machined brackets. Order numbers, lots, machines, people and results are invented for this page.

TimeEventData recorded
06:02Order WO-4471 released from ERP to Line 2Part 88-120 revision C, quantity 500, routing of 3 operations
06:15Material issuedBar stock lot H2291 scanned at machine CNC-04
06:20Setup and first-piece checkProgram revision 7; first piece bore 12.02 mm, within limits; approved by inspector 31
07:41Machine stopDown 18 minutes, reason code "tool break"; insert replaced
10:05In-process check failsBore 12.09 mm, above the upper limit; 14 parts on hold; non-conformance NC-208 opened
10:40DispositionNC-208: 14 parts scrapped; cause a worn boring bar; tool life limit reduced
13:30Order complete486 good, 14 scrap, yield 97.2 percent; genealogy links each serial to lot H2291, CNC-04 and its operators

Each row joins to the next by order, lot and machine. That chain, a failed check, its cause and the change it led to, is what an MES keeps and a spreadsheet of shift totals does not.

Common mistakes with MES projects and MES data

Most MES problems are data problems that start on day one.

  • Choosing software from feature lists before deciding which system owns each piece of data.
  • Free-text downtime and defect reasons instead of a controlled code list.
  • Operators back-filling counts at the end of the shift, which hides when a problem started.
  • A different custom interface for every machine and system.
  • Losing the link between lots and serial numbers when a part moves between systems.
  • Replacing an MES without exporting the old history and its audit trails.
  • Relying on vendor rankings instead of writing your own requirements by ISA-95 function first.

Is years of MES data also a data asset?

It can be, for manufacturers that kept the history linked. AI data buyers have asked Origin for manufacturing work orders and quality logs with the links between them intact: the inspection result, the non-conformance it opened, the root cause, the corrective action and the measured result after the change, together with maintenance history that shows each failure code and what happened after each repair. An MES that kept genealogy, quality results and downtime reasons for years holds those chains, tied to orders and lots. For the rights questions, see licensing manufacturing quality records, licensing industrial maintenance records and, for time series and alarms, PLC, SCADA and historian data.

What must come out first: drawings and specifications your customers authored, export-controlled technical data under ITAR or the EAR, supplier and customer material received under a nondisclosure agreement, operator and inspector names, and critical infrastructure details. Shops whose archive is mostly CAM programs should also read machine shop CNC and CAM files, and the de-identification guide covers replacing names with codes.

Origin is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.

Does your company hold records like these? See what your data is worth.

Common questions

What does MES stand for in manufacturing?

MES stands for manufacturing execution system: the plant-floor software that releases work orders, guides operators, tracks materials and lots, and records what was produced, with quality results and downtime. In the ISA-95 model it sits at Level 3, manufacturing operations management, between ERP business systems at Level 4 and the PLCs and control systems that run the machines.

Is an MES the same as an ERP system?

No. ERP plans and runs the business: orders, purchasing, inventory and finance, in days and weeks. An MES runs and records production on the floor in shifts and minutes: which unit was made, from which materials, on which machine, by whom, and whether it passed its checks. The two exchange orders and results, and ISA-95 describes the interface between them.

What is the difference between MES and MOM?

MOM, manufacturing operations management, is the term the ISA-95 standard uses for the whole Level 3 space, including quality and maintenance activities as well as production. MES usually means the software that executes production within that space. Many plants and suppliers use the two terms for the same system, so check which functions a product actually covers before you compare them.

Do small manufacturers need an MES?

Not always, but many benefit. NIST notes that many small and medium-sized manufacturers lack the production data an MES collects, and that an MES can also serve as a quality or scheduling system. Start by listing the questions you cannot answer today, such as why a line was down or which lot went into an order, and check whether a lighter tool already answers them.

What is ISA-95 in simple terms?

ISA-95, also published as IEC 62264, is a set of standards for connecting business systems with plant-floor systems. It divides a manufacturer into levels, from the physical process at Level 0 to business planning at Level 4, defines what manufacturing operations management does at Level 3, and describes the information exchanged between Level 3 and Level 4, so different systems can share orders and results.

What data should an MES collect from machines?

Start with machine state (running, idle or down) with timestamps, part counts, and a reason code for every stop. Add the process values that affect quality, such as temperatures, pressures or feeds, recorded for each lot or unit, plus alarms. Standards such as OPC UA and MTConnect let an MES read many machines directly instead of relying on manual entry.

How long should MES records be kept?

As long as the product, the customer or the regulator requires, whichever is longest. For drug products, FDA rules require batch records to be kept at least 1 year after the batch expiration date. Customers can set longer periods in purchase orders and quality agreements, so check those too, and keep genealogy and quality history for the service life of the products you shipped.

Can an MES replace a quality management system?

Sometimes, in part. NIST notes that an MES can serve as a quality management system or a scheduling system on its own. An MES is strong at in-process checks, holds and traceability on the floor. Document control, supplier quality, audits and corrective action programs often stay in a separate quality system, so map which system owns each quality record before you retire either one.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.