Yes, in practice batch monitoring is required for GMP compliance in 2026, but not under that exact name. GMP rules require you to document, verify, and keep reliable records of every batch, which means you must monitor critical process data. Whether that monitoring is manual or automated is up to you, as long as the result is complete, accurate, and traceable.
The key driver is the combination of batch record requirements and data integrity expectations. Below we answer the most common questions about what GMP asks for and how to meet those expectations in a practical way.
Which GMP rules actually cover batch monitoring?
No GMP regulation uses the phrase “batch monitoring” as a standalone requirement. Instead, batch monitoring is covered through rules on batch documentation, in-process controls, and production records, mainly in EU GMP Chapter 4 and Annex 11, and in FDA 21 CFR Parts 210, 211, and 11.
Together, these rules say that you must be able to show how every batch was made, what happened during production, and that critical parameters stayed within approved limits. Here is how the main sources apply:
- EU GMP Chapter 4 (Documentation): requires records that show each step of manufacture was carried out and that any deviations were investigated.
- EU GMP Annex 11 (Computerised Systems): sets expectations for any computer system that creates, stores, or processes GMP data.
- FDA 21 CFR Part 211: requires batch production and control records, including in-process checks.
- FDA 21 CFR Part 11: covers electronic records and electronic signatures.
In short, the rules do not tell you to buy a monitoring tool. They tell you to prove control of your process, and monitoring is the most reliable way to do that.
Do GMP rules require electronic batch records?
No, GMP rules do not require electronic batch records. Paper records remain acceptable if they are complete, legible, and controlled. However, once you use electronic systems to capture or store batch data, Annex 11 and 21 CFR Part 11 apply, and your system must meet specific requirements.
That said, paper becomes harder to defend as processes grow more complex. Manual transcription introduces errors, and reviewers must cross-check many pages by hand. Electronic records offer clear advantages:
- Data is captured directly from the process, which reduces transcription errors.
- Time stamps and audit trails are created automatically.
- Review by exception becomes possible, so your team focuses on deviations instead of every data point.
If you operate hybrid setups, with some data on paper and some in electronic systems, make sure the link between the two is clearly defined and controlled. Gaps between systems are a common source of inspection findings.
What data integrity expectations apply to batch data?
Batch data must meet the ALCOA+ principles: attributable, legible, contemporaneous, original, and accurate, plus complete, consistent, enduring, and available. Regulators expect that data cannot be changed, deleted, or lost without a visible, traceable record of who did it, when, and why.
For batch data, this translates into several practical expectations:
- Attributable: every entry and change is linked to a named user.
- Contemporaneous: data is recorded at the time the event happens, not reconstructed later.
- Original: the first capture of the data, or a certified true copy, is retained.
- Complete: nothing is missing, including aborted steps, holds, and repeated actions.
- Protected over time: data stays readable and retrievable throughout the retention period.
Audit trails are central here. A reviewer should be able to see what changed, by whom, and for what reason, without relying on memory or separate notes. Access control, backup, and validated systems all support these expectations.
What’s the difference between batch monitoring and batch control?
Batch control executes the recipe: it starts and stops phases, sets parameters, and drives equipment. Batch monitoring observes and records what happens during execution so you can verify it, review it, and prove it later. Control makes the batch happen, while monitoring documents and evaluates it.
The two work closely together, but they serve different purposes:
- Batch control: real-time execution, sequencing, interlocks, and recipe handling on the automation layer.
- Batch monitoring: data collection, event logging, alarms and deviation tracking, and reporting for quality review.
In many plants, such as those running Siemens SIMATIC Batch on PCS 7, the control system generates a rich stream of events and data. The challenge is getting that information to the quality and manufacturing systems that need it, in a form that supports review and release. This is where the line between control and monitoring often blurs, and where integration choices matter.
How does automated batch monitoring support audit readiness?
Automated batch monitoring supports audit readiness by capturing batch events, parameters, and deviations directly from the process, with time stamps and audit trails. This gives you complete, consistent records that you can retrieve quickly, which reduces manual preparation and lowers the risk of gaps during an inspection.
When an inspector asks for the full history of a batch, speed and consistency matter. Automated monitoring helps in several ways:
- Less manual transcription: fewer handwritten values mean fewer errors to explain.
- Faster batch review: deviations and alarms are flagged, so reviewers can focus on exceptions.
- Consistent records across batches: the same data is captured the same way every time.
- Easier retrieval: a complete batch history is available without hunting through binders or separate systems.
Automation does not remove the need for validation. Your monitoring setup still needs documented requirements, testing, and change control. But a validated, automated approach is usually easier to defend than a patchwork of manual steps.
Is anything changing in GMP monitoring expectations for 2026?
The core principles of batch documentation and data integrity are not changing in 2026, but regulators continue to sharpen their focus on computerised systems, data governance, and risk-based validation. Expect inspectors to ask more detailed questions about how data moves between systems and how your electronic records are controlled.
Several trends are worth watching as you plan this year:
- Revisions to EU GMP guidance: the EU has been working on updates to Annex 11 and related guidance on computerised systems. Check the latest published status with your regulatory team, since details may evolve.
- Stronger IT and OT integration: more plants connect batch automation with MES, ERP, and cloud platforms, which raises expectations for secure, traceable data exchange.
- Risk-based approaches: regulators favour validation effort that matches the risk to patient safety and data integrity.
- Legacy interfaces under scrutiny: older communication methods, such as DCOM-based links, can create security and maintainability concerns.
We recommend reviewing your current batch data flows against these themes. Mapping where data is created, transferred, and stored often reveals quick wins before the next inspection.
How Smart Batch Connect helps with batch monitoring
If you run Siemens SIMATIC Batch, getting reliable batch data into your MES, ERP, or cloud applications is often the hardest part of monitoring. We built Smart Batch Connect to solve exactly that. It sits on top of SIMATIC Batch as a standardized integration layer, so external systems can access batch functions and events through modern interfaces instead of legacy ones.
Here is what that means in practice:
- Modern API access: REST API communication (plus a gRPC interface and .NET client SDK, as listed by Siemens) reduces the need to work directly with the SIMATIC Batch COM API.
- Real-time event capture: API and SIS events are captured and distributed to connected systems, supporting production visibility and review.
- Reliable event handling: built-in message broker functionality stores and queues events, which helps prevent event loss during temporary connectivity interruptions.
- MES, ERP, and cloud connectivity: multiple clients can communicate with SIMATIC Batch at the same time, so batch information reaches the systems that need it.
- Less reliance on DCOM: a standardized interface can simplify your architecture and reduce certain security risks tied to legacy communication.
- Mock mode for testing: you can simulate requests and responses without a live SIMATIC Batch installation, which supports development and testing activities.
Smart Batch Connect supports your monitoring and data flow needs, while validation and compliance decisions remain with your quality team. Want to see how it fits your PCS 7 and SIMATIC Batch environment? Get in touch with us and we will gladly talk through your situation.
Frequently Asked Questions
Where should I start if I want to improve batch monitoring in my plant?
Start by mapping your current batch data flows: where data is created (for example in SIMATIC Batch or PCS 7), how it is transferred, and where it is stored or reviewed. Then compare this map against ALCOA+ and your batch record requirements to find gaps such as manual transcription, unlinked paper and electronic records, or missing audit trails. Prioritise the gaps by risk to product quality and data integrity, and address the highest-risk ones first.
What are the most common batch record findings during GMP inspections?
Typical findings include missing or incomplete entries, data recorded after the fact instead of at the time of the event, uninvestigated deviations, shared user accounts, and weak or missing audit trails. Hybrid setups also draw attention when the link between paper and electronic records is not clearly defined. Regular internal audits of batch records and data flows help you catch these issues before an inspector does.
If we move from paper to electronic batch monitoring, do we need to revalidate?
Yes, any electronic system that creates, stores, or processes GMP data needs to be validated according to Annex 11 and 21 CFR Part 11 expectations. Use a risk-based approach: document your user requirements, test the critical functions, and put change control in place. The effort should match the risk to patient safety and data integrity, so a system handling release-relevant batch data needs more rigour than a purely informational one.
How do I make sure no batch events are lost when systems are temporarily disconnected?
Use an architecture that buffers events instead of relying on a live connection at every moment. A message broker that stores and queues events, as built into Smart Batch Connect, helps ensure events reach MES, ERP, or cloud systems once connectivity returns. Whatever approach you choose, test interruption scenarios during validation and document the expected behaviour so you can show completeness of the batch record.
What does review by exception mean, and is it accepted by regulators?
Review by exception means reviewers focus on flagged deviations, alarms, and out-of-limit events rather than checking every data point manually. It is generally acceptable when the underlying system is validated, the exception criteria are defined and justified, and the data is complete and trustworthy. Document your review procedure clearly and make sure reviewers can still access the full batch history whenever needed.
How can I test batch data integrations without risking a live production system?
Use a non-production or simulated environment for development and testing. For example, Smart Batch Connect offers a mock mode that simulates requests and responses without a live SIMATIC Batch installation, which supports early development and integration testing. Formal validation and qualification activities should still be carried out according to your quality system and applicable procedures.
Why are legacy interfaces like DCOM a concern for GMP environments?
DCOM-based links can be difficult to secure, maintain, and troubleshoot, which can affect the reliability and traceability of your batch data exchange. Inspectors increasingly ask how data moves between systems, so a hard-to-explain or fragile interface can become a liability. Replacing or wrapping legacy links with a standardized, modern interface such as REST can simplify your architecture and make your data flow easier to document and defend.
