MES for Pharmaceutical Manufacturing: CPOB Batch Records and Data Integrity
Pharmaceutical plants answer to the strictest documentation expectations of any industry, and Indonesia's version just moved closer to the strictest interpretation of them. CPOB 2024 — Cara Pembuatan Obat yang Baik, the Indonesian GMP for drugs, set out in PerBPOM No. 7 of 2024 and revised by PerBPOM No. 7 of 2025 — rebuilt the national rulebook on the EU GMP framework, and it now explicitly covers computerized systems and data integrity: audit trails, electronic records, control over who changed what. For a mid-market pharma manufacturer the practical meaning is blunt. "We keep records" is no longer a sufficient answer; the record has to survive questions about who typed it, when, and whether it can be trusted.
What CPOB 2024 Changed
The 2024 text replaced the previous CPOB generation and aligned its structure with EU GMP. The PerBPOM 7/2025 revision then tightened Annex 1 on sterile products, following the same direction the European text took. Those changes matter most for sterile operations. The one that matters for every plant, sterile or not, is the explicit treatment of computerized systems and data integrity.
Where the old expectation read roughly as "records must be kept and retained," the new text states what a record kept in a computer must satisfy. Audit trails that show who entered and who changed what, and when. Electronic records that carry the same obligations as signed paper. Access controls so entries are attributable to a named person rather than a shared terminal. None of this is exotic — it is the same logic regulators have applied in the EU and US for years — but it is now written into the Indonesian text your inspector carries.
The consequence lands on plants that improvised. A shared-login spreadsheet, a logbook transcribed at end of shift, a batch record "corrected" by overwriting: each was sloppy before, and under the 2024 text each is a data integrity finding with a name.
What a Pharma MES Must Do Beyond Generic
A MES for pharmaceutical manufacturing is a different product category from a generic production tracker. The generic features — work orders, downtime with reasons, output counts — are table stakes. What a CPOB-facing plant needs on top:
- Review and release by exception. QA must review the batch record before release, and a system that makes QA read every line guarantees rubber-stamping. The pharma pattern: the system compares the record against the master, flags exceptions — a missing entry, an out-of-spec check, an unexplained deviation — and QA reviews the exceptions plus a risk-based sample, then dispositions the batch: release, reject, or hold.
- Deviations tied to the batch, permanently. A deviation is not a sticky note. It attaches to the batch record with its investigation status and outcome, and the batch cannot leave that history behind. Six months later an auditor picks the batch and finds the deviation, the investigation, and the corrective action in one place.
- E-signatures that mean something. In a computerized system, a signature is an event: the identity of the signer, the timestamp, and the meaning — performed, verified, approved. An image of a signature pasted into a PDF satisfies nobody.
- ALCOA+ by construction. Attributable, legible, contemporaneous, original, accurate — plus complete, consistent, enduring, and available. In floor terms: entries captured at the moment the work happens, by the person doing it, with no shared logins and no end-of-day transcription from memory.
- Segregation and second-person verification. The person who performed a step cannot be the person who verifies it. The system enforces the separation — production enters, QA verifies — instead of hoping the paper routing enforces it.
This is the batch record skeleton we describe for BPOM food audits in our electronic batch record primer, raised to a stricter standard: in pharma, the review-and-release step is a controlled process of its own, not a signature at the end.
The Mid-Market Gap
Walk the market and the options bunch at two ends.
At the high end sit the enterprise validated suites — the MasterControl and Kneat class — built for exactly the workflow above: validated batch records, managed deviations, audit trails, qualification documentation. They are real products doing real work in sterile suites and export-oriented plants. They are also enterprise purchases: procurement runs in quarters, validation runs in quarters more, and the total cost prices out most mid-market manufacturers.
At the other end is the binder. Paper batch tickets, wet signatures chased across shifts, a documentation office that photocopies and files. It passes inspections when discipline holds, and it is what many Indonesian pharma plants still run for most of their lines.
Between them — a system that captures production events digitally, keeps genealogy and deviations, and could one day grow into a validated record — the shelf is nearly empty. That gap is why plenty of mid-market plants run their newest line on a validated suite while commercial and legacy products stay on paper for years.
An Honest Scope Note
Voltrus MES is in early access, and it is not a validated GMP system today. We will not dress that up: batch release under CPOB is a QA decision, and no plant should route that decision through software that has not been qualified for it.
What Voltrus does today is the production record and genealogy layer for lines where records are otherwise lost: commercial and legacy products, packaging operations, lines running alongside a validated system of record. Work orders, material lots, operators, in-process checks, downtime, deviations, and two-directional genealogy — captured at the station while the batch runs, assembled into a per-batch audit pack. That layer feeds the validated record rather than replacing it, and it upgrades the lines the validated suite never reached.
The validation path — qualification documentation, audit trail review, the controls a GMP system of record needs — is on the roadmap as pilot demand grows. If your QA team wants to pilot that journey on one line, say so; that demand is what moves it up the schedule.
Where the Record Meets the Audit
The audit-facing test is the same one we describe for BPOM food plants: an inspector picks one batch and asks for its story, then reverses it — here is a material lot, show every batch that used it. That second direction is the genealogy question, and it is the same mechanics as answering a customer genealogy request: the record must link batch to lots and lots to batches, in both directions, on demand.
If an inspection is close, change nothing in a panic. Start from the BPOM audit preparation checklist (in Bahasa Indonesia) and find where your documentation actually stands. And if your plant is small enough that the enterprise suites are out of reach, the sequencing in MES for small manufacturers applies: fix capture and retrieval before buying anything with the word "enterprise" in it.
Frequently Asked Questions
Does CPOB require computerized systems?
No. CPOB 2024 defines requirements that computerized systems must meet when you use them — audit trails, access control, attributable entries, data integrity — but it does not mandate software. A well-kept paper record with real signatures remains acceptable. The trap is the middle: once a computer touches the record, those requirements apply to it. A shared spreadsheet is not "still paper"; it is an uncontrolled computerized system.
Is Excel acceptable as a batch record?
As an analysis tool on top of a controlled record, yes. As the record itself, it fails the expectations almost by construction: entries are not attributable to a named person, edits leave no audit trail, and any cell can be changed silently. If Excel holds your batch data today, the finding to expect is not about Excel; it is about the missing audit trail around it.
We cannot justify an enterprise validated suite. What is the realistic path?
Sequence it. First, fix capture where records are lost — the lines where events happen and nobody records them; a disciplined paper record beats an undisciplined digital one. Second, decide what the system of record is for each line, and keep QA release decisions inside the qualified perimeter. Third, grow the digital layer where it pays for itself in retrieval time and genealogy, and treat validation as a deliberate project when pilot economics support it. What does not work is buying the suite first and hoping the floor data appears.
Batch Records Built for Inspection
Voltrus MES records production as it executes — work orders, material lots, operators, checks, deviations, two-way genealogy — and assembles the per-batch audit pack. Early access, one line to start.
See Voltrus MES