A pharma MES runs and records production steps under GMP, often as electronic batch records. In the US, 21 CFR Part 11 sets the rules for electronic records and signatures; in the EU, GMP Annex 11 covers computerised systems. Validation is done for your intended use and stays the manufacturer's responsibility, so buying a product never settles it.
This is a plain-language guide, not regulatory or legal advice. Your quality unit decides how these rules apply to your site, and the linked texts are what count.
What an MES does in a pharma plant
The job is the same as elsewhere, as what is an MES explains. What differs is how much of it must be proven and how carefully records are kept.
- Electronic batch records: each step recorded as it is done, and not typed up later.
- Weighing and dispensing: the right material, lot and quantity, checked at the scale.
- Enforced sequence: the next step stays locked until the last one is complete.
- Line clearance and in-process checks: recorded with who did them and when.
- Lot genealogy: see MES traceability.
Why those details? US batch records must show, for each significant step, items such as dates, equipment, component batches, weights and the people involved, under 21 CFR 211.188(b).
What the rules ask, and what to test
| Clause | In plain words | A test you could run |
|---|---|---|
| Part 11, 11.10(a) | Validate systems for accuracy, reliability and consistent intended performance | Run your own process scripts, with limits and errors |
| 11.10(e) | Secure, computer-generated, time-stamped audit trails, and changes must not hide earlier values | Change a value, then find both the old and new |
| 11.10(d), (g) | Only authorised people can use the system, sign records or do each operation | Try a step with the wrong role |
| 11.10(f) | Checks that enforce the permitted order of steps, as appropriate | Try to skip a step |
| 11.100(a) | Each electronic signature is unique to one person, never reused or reassigned | Try to create a second user with the same signature ID |
| Annex 11, section 1 | Base the extent of validation on a documented risk assessment | Show the risk assessment behind your test plan |
| Annex 11, section 9 | Consider audit trails based on risk; document the reason for changes; review them regularly | Change a value and check that a reason is demanded |
| Annex 11, section 15 | Only Qualified Persons certify batch release, using an electronic signature | Attempt release under another role |
What an audit trail row can look like
| Time | User | Record | Old | New | Reason |
|---|---|---|---|---|---|
| 09:42:10 | Operator 118 | Batch 2417, step 6, weight | 12.50 kg | 12.05 kg | Typing error, see scale printout |
FDA's December 2018 data integrity guidance uses the term ALCOA: data should be attributable, legible, contemporaneously recorded, original or a true copy, and accurate.
A trail kept like this row supports audit-readiness. It does not make any product compliant or validated, because that depends on your whole system and procedures.
Where each rule stands today
Part 11 applies to electronic records kept under agency record requirements, per section 11.1. FDA's 2003 scope guidance recommends a justified, documented risk assessment for validation, and it states that Part 11 remains in effect.
That guidance also describes enforcement discretion on some items, such as validation and audit trails. It is narrow, and the underlying predicate rules still apply, so do not read it as a waiver.
Annex 11 in force is the 2011 revision, with a Volume 4 listing that still showed only that version when we checked on 2 November 2026. The Commission consulted on a draft revision from 7 July to 7 October 2025, along with Chapter 4 and a new Annex 22 on AI.
Check that page before you fix a plan. A project starting now should at least read the draft, since it points to stronger requirements on suppliers, audit trails and security.
MES system validation, step by step
Validation here means showing, with evidence, that the system does what you need in your process. It does not sit inside a product, because your configuration, data flows and procedures are part of what is proven.
Describe the functions you need, based on risk and GMP impact, and keep them traceable (Annex 11, 4.4).
Decide the extent of validation and data integrity controls from patient safety, data integrity and product quality.
Check their quality system and review their documents against your needs (3.2, 3.3, 4.5). Decide on an audit by risk.
Test with suitable scenarios, including limits and error handling (4.7). Check that migrated data is unchanged (4.8).
Report deviations and approve. Set up backups, security and a fallback for system failure (7, 12, 16).
Control every change (10), and evaluate the system periodically (11).
Industry guidance can help you scale the effort. ISPE's GAMP 5, second edition is one such guide, and Annex 15 lists qualification stages, including IQ, OQ and PQ, for equipment, facilities, utilities and systems.
For computerised systems used in manufacture, Annex 15 itself points back to Annex 11.
What a supplier can and cannot do for you
A supplier can provide documents, test evidence and help, and Annex 11 expects formal agreements that state their responsibilities (section 3.1). Those documents still need your review against your own requirements (section 3.3).
So treat a "Part 11 compliant" or "validated" label as a supplier's claim to examine. Compliance depends on how your site configures, uses and controls the system.
- What quality system was the software developed under, and may we audit it?
- Which test evidence can we reuse, and on which version?
- How are updates announced, and how long do we get to assess them?
- Who has remote access, and how is it recorded?
- How do we get our data out, readable, when the system retires (section 17)?
Is all production data GMP data?
No, and this question can save you much effort. The answer comes from what each record is used for, and your quality unit makes the call.
| Data on a packaging line | Used for | Likely view |
|---|---|---|
| Label reconciliation: 30,000 issued, 29,850 used, 150 destroyed | Batch record | GMP record |
| In-process check results | Batch release | GMP record |
| Stop reasons and OEE | Improvement meetings only | May be outside GMP scope |
| Same stop log, used to justify a deviation | Quality decision | Now in scope |
That is why some sites keep improvement data apart from batch records. Availability losses from cleaning and changeovers are covered in OEE and downtime in pharma, and OEE for batch processes shows how to count them.
Where pharma projects go wrong
- Testing everything equally. Risk should move effort to what affects patients and data.
- Copying paper records one to one. Annex 11 says replacing a manual step must not add risk, and it is also a chance to redesign.
- Shared logins. They break attribution at once.
- Treating go-live as the end. Updates and config changes need control for as long as the system runs.
- Vague requirements. Start from a written list, as in the requirements checklist.
This page is about GMP records. For the separate question of where a packaging line loses time, Fabrico is a light MES for OEE: stops, speed and counts live from machines, causes tagged at the line. Whether any system falls in your GMP scope is your quality unit's decision. See Fabrico as a light MES for OEE.
What people ask next
Does FDA require an MES?
We found no rule that requires one. Batch records must meet the rules whether on paper or electronic, and Part 11 applies when you keep required records electronically. Your choice of system still has to meet what the predicate rules ask.
What is the difference between an MES and an electronic batch record?
The batch record is a record of what was done for a batch. An MES is the wider system that can produce it, and it also handles orders, equipment status and more, so some sites run a batch record system with no wider MES. MES modules lists the wider functions.
Who validates a pharma MES?
The manufacturer stays responsible for its validated state, even if a supplier or consultant does much of the work under a formal agreement. Annex 11 sections 3 and 4 place these duties on the manufacturer, or regulated user. Suppliers supply evidence, and your quality unit accepts it or not.
Can a cloud MES be used under GMP?
The rules do not name a hosting model in the sections we read. Annex 11 expects agreements with service providers, supplier assessment and qualified IT infrastructure, and the draft revision goes further. Ask your quality unit early.
What is the difference between Part 11 and Annex 11?
Part 11 is a US regulation on electronic records and signatures, and Annex 11 is EU GMP guidance on computerised systems. They overlap on validation, audit trails, security and signatures, and a global site often plans for both.
Does OEE software need to be validated?
It depends on use. If the data only supports improvement work, your quality unit may place it outside GMP scope, and if it feeds batch or quality decisions it likely comes into scope. See OEE and downtime in pharma for the line losses themselves.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.