MES
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.
Delivered for and alongside
































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:
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
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
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
Process orders, bills of materials, routings, material status
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
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
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.
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.
Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.
Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.
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.
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.
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.
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.
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.
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.
Where next
Talk to us before you commit to a vendor or integrator, and we will tell you plainly what fits your plant.