MES

Manufacturing execution system selection and assurance

A manufacturing execution system decides how orders become product on your shop floor and how you prove it afterwards. We help regulated manufacturers choose MES software independently and keep the implementation honest from design to go live.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
0licences or commissions

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Between ERP and the shop floor

The ISA 95 standard, published internationally as IEC 62264, gives the clearest map. Level 4 is business planning and logistics, where ERP lives. Level 3 is manufacturing operations management, the home of the MES. Level 2 is monitoring and supervisory control through PLCs and distributed control systems, level 1 the sensors and valves, and level 0 the physical process itself. The standard concentrates on the interface between levels 3 and 4, which is exactly where MES programmes succeed or fail.

In practice an MES does the work ERP was never built for:

  • Electronic batch records: master batch records authored once, executed step by step with weights, signatures and in process checks, then reviewed by exception
  • Weighing and dispensing, with scale integration and checks on material status and expiry
  • Genealogy: which lots of which inputs went into which batch, at which station and by whom
  • Overall equipment effectiveness: availability, performance and quality losses captured at the line rather than estimated at month end
  • Work instructions, equipment status and electronic logbooks

In food and chemicals the emphasis tends towards recipe control, genealogy for recall and OEE. In pharmaceuticals and medical devices the batch record or device history record becomes the regulated record itself, so its design carries as much weight as its usability. Our guide to process manufacturing ERP covers what normally stays on the ERP side of the line.

ISA 95: where the MES sits

Level 4Business planning and logisticsERPLevel 3Manufacturing operations managementMESLevel 2Monitoring and supervisory controlPLCs and DCSLevel 1Sensors and valvesLevel 0The physical process The 3 to 4 interfaceWhere ISA 95 concentrates,and where MES programmessucceed or fail ISA 95, published internationally as IEC 62264.

Who sells MES software, and to whom

  • Siemens Opcenter Execution Pharma is master batch record driven, with paperless batch records, review by exception and native integration with Siemens production control.
  • Rockwell Automation sells FactoryTalk PharmaSuite for life sciences, with electronic batch recording, weighing and dispensing and centralised cloud deployment in version 12. It also owns Plex, bought in September 2021, a cloud native platform spanning MES, ERP and quality for discrete and food manufacturers.
  • Körber Werum PAS X MES covers pharmaceutical, biotech and cell and gene therapy production, on premise, in private cloud or as fully managed SaaS, with PAS X Neo for more standardised processes.
  • Emerson DeltaV MES, still carrying the Syncade brand on parts of Emerson's site, pairs with DeltaV control in batch process plants. In January 2026 Emerson launched a tool that converts paper batch records into MES recipes.
  • AVEVA, wholly owned by Schneider Electric since January 2023, sells AVEVA Manufacturing Execution System.
  • DELMIA Apriso from Dassault Systèmes is a manufacturing operations management suite for larger multi plant firms, adding quality, warehouse, maintenance and labour, with more than 40 standard ERP connection points.
  • Tulip takes a composable, app based approach. It publishes Essentials at 100 US dollars and Professional at 250 US dollars per interface per month, billed annually with a ten interface minimum. Its Regulated Industries plan, which adds Part 11 electronic signatures and a validation pack, is quoted (checked November 2026).

Outside Tulip's lower plans, expect quotes rather than price lists, driven by sites, lines, users or stations, modules and the depth of integration with your automation layer.

The vendors at a glance

VENDORPRODUCTNOTED FOR SiemensOpcenter Execution PharmaMaster batch record driven, review by exceptionRockwell AutomationFactoryTalk PharmaSuiteLife sciences, cloud deployment in version 12Rockwell AutomationPlexCloud native MES, ERP and quality, discrete and foodKörberWerum PAS X MESPharma, biotech, cell and gene therapyEmersonDeltaV MESPairs with DeltaV control in batch plantsAVEVA (Schneider Electric)AVEVA MESManufacturing execution systemDassault SystèmesDELMIA AprisoLarger multi plant firms, 40+ ERP connection pointsTulipComposable appsPublished plan prices, Regulated tier quoted Beyond Tulip's lower plans, expect quotes driven by sites, lines, users or stations, modules and automation integration.

ERP integration and validation where GxP applies

The ERP to MES boundary has to be settled object by object before anyone configures anything. Process orders, bills of materials, routings and material status usually flow down; consumption, yields, scrap, labour and batch completion flow back up. ISA 95 Part 2 defines the objects exchanged and Part 5 the business to manufacturing transactions, which gives vendors and integrators a shared vocabulary. Arguments about whether ERP or MES owns the master recipe cause more rework than any interface technology. Our ERP integration practice deals with exactly this.

Where an MES holds GMP records it is a computerised system within EU GMP Annex 11 and, for US supply, 21 CFR Part 11. That means user requirements, a supplier assessment, testing proportionate to the risk to product quality and patient safety, and controlled change once live. For medical device makers, FDA's computer software assurance guidance, finalised in September 2025 and reissued in February 2026 alongside the amended Part 820 quality management system regulation, points to scripted testing for high process risk functions and lighter unscripted methods elsewhere.

Vendor validation packs help. Tulip, for example, includes test reports and a traceability matrix in its regulated tier. But a pack proves the product, not your configured recipes, interfaces and roles, which still need your own evidence. Our computer system validation page explains where we draw that line.

The ERP to MES boundary, object by object

ERPLevel 4 MESLevel 3 FLOWS DOWN Process ordersBills of materialsRoutingsMaterial status ConsumptionYieldsScrapLabourBatch completion FLOWS BACK UP Settle who owns the master recipe first. ISA 95 Part 2 defines the objects, Part 5 the transactions.
ERP is Level 4Flows down from ERP to MES

Process orders, bills of materials, routings, material status

MES is Level 3Flows back up from MES to ERP

Consumption, yields, scrap, labour, batch completion

Settle who owns the master recipe first. ISA 95 Part 2 defines the objects, Part 5 the transactions

Validation where GxP applies

EU GMP ANNEX 11 AND 21 CFR PART 11 User requirementsSupplier assessmentRisk based testingControlled change once live Vendor validation packproves the product Your own evidencefor configured recipes, interfaces and roles

How we select and assure an MES

We begin with a question many selections skip: do you need a full MES, or would electronic batch records and line monitoring on a lighter platform do the job? A single site food or chemicals business with three lines rarely needs the same product as a multi site sterile manufacturer. Vendors then demonstrate against a script built from one of your real master batch records, an exception during execution, and an ERP order flowing through to completion and back.

Two things get close scrutiny. The first is support for your control system, because a strong MES with a weak link to your PLCs or DCS becomes a data entry screen. The second is the people the integrator will actually field, as MES skills are scarce and named consultants have a habit of changing after contract.

We take nothing from any MES vendor or integrator. Our people have led and picked apart system decisions at every stage, before, during and after migration and implementation, and our team has run programmes across five continents.

Part A is independent assurance alongside your team and integrator: requirements, design authority, test and validation readiness, and cutover. Part B puts our practitioners in charge of selection and delivery. Use either or both; our fees are shown plainly on the pricing page. If the MES is part of a wider factory change, our manufacturing ERP guide is the companion read.

How we test vendors

VENDORS DEMONSTRATE AGAINST 1One of your realmaster batch records2An exceptionduring execution3An ERP orderto completion and back Then two checks: the link to your PLCs or DCS, and the integrator's people.

What we have delivered

22m+assets, National Grid separation

Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.

£25msaving at BP Pulse, 39 days early

Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.

£9bnEnergy Bills Support Scheme

Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.

19 yrsfinance systems delivery

Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.

ERP and CRMpre, mid and post migration

A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

What is the difference between MES and ERP?

ERP plans and accounts: it holds orders, stock, costs and purchasing at level 4 of the ISA 95 model. A manufacturing execution system works at level 3, directing and recording what happens on the line minute by minute, including weights, operator steps, equipment status and quality checks. ERP tells the plant what to make; the MES records how it was made.

What is an electronic batch record?

An electronic batch record replaces the paper record that accompanies a batch through manufacture. The MES enforces the sequence in the master batch record, captures weights, parameters and signatures as each step happens, and flags deviations as they occur. Quality reviewers can then concentrate on exceptions rather than checking every page, which shortens the time from batch completion to release.

Does MES software need validating?

If it creates or holds GMP records, such as batch records or device history records, yes. Validation should be risk based: concentrate testing on functions that affect product quality, patient safety or data integrity, use the vendor's documentation where it is sound, and test your own configuration. Food and chemicals manufacturers outside GMP still benefit from structured testing, just with lighter documentation.

How does an MES measure OEE?

Overall equipment effectiveness combines availability, performance and quality. An MES captures stoppages, cycle times and rejects directly from equipment or operator input, so the figure reflects what actually happened on each line and shift. The value lies less in the headline percentage than in the reason codes behind each loss, which tell you where engineering effort will pay back.

Can a smaller manufacturer justify an MES?

Often, if the case rests on a specific problem such as slow batch release, recall traceability or unexplained line losses. Composable platforms and cloud subscriptions have lowered the entry point compared with traditional enterprise MES. The risk for smaller firms is buying more scope than they can configure, validate and support, so start with the processes that hurt most.

Weighing up an MES?

Talk to us before you commit to a vendor or integrator, and we will tell you plainly what fits your plant.

Book a conversation