A batch report is the compiled record of a single batch, gathering into one document everything that happened from start to finish. It captures the recipe used, the actual versus target parameters, the timing of each phase, the material charges, the operator actions, the exceptions, and the signatures. Where the batch runs and generates data in real time, the batch report is the readable summary produced afterward. For SCADA engineers wiring up reporting, the key is understanding how report data is collected from phases during execution and then templated into the final document.
batch report in one line: A batch report is the compiled record of one batch, documenting the recipe used, actual versus target values, phase timings, material charges, operator actions, exceptions, and signatures. Report parameters are collected from phases as the batch runs and are assembled into a templated document at the end, giving a complete, readable account of that single batch.
A batch report is organized around a single batch and tells its whole story. It names the batch by its unique ID, records which recipe and which recipe version produced it, and states the target and actual batch size. From there it walks the execution: the operations and phases that ran, when each started and finished, and how long each took. This gives the report a clear procedural spine that mirrors the recipe.
Around that spine hang the details that matter for quality and accountability. Actual versus target parameters show whether each setpoint was met: the temperature reached versus the temperature commanded, the quantity charged versus the quantity specified. Material charges list what was added and how much. Operator actions record manual interventions, overrides, and answers to prompts. Exceptions record every deviation and how the system responded.
Finally, the report carries the human sign-off. Signatures, whether wet or electronic depending on the system, attest that the batch was reviewed and approved. Together these elements make the batch report a self-contained account: anyone reading it can see what was supposed to happen, what actually happened, where the two diverged, who intervened, and who signed off, all for one specific batch.
The content of a batch report does not appear at the end; it is gathered continuously as the batch runs. Each phase is configured with report parameters, specific values it should capture and pass up to the batch record: a charge phase reports the quantity actually delivered, a heat phase reports the peak temperature and the hold duration, an agitate phase reports run time. As each phase completes, its report parameters are stamped with values and timestamps and stored.
This per-phase collection is what makes the final report accurate rather than reconstructed. Because the values are captured at the moment they are true, tied to the phase that produced them, there is no need to infer later what happened from a flat historian trace. The batch engine knows that this 400 kg charge belongs to this charge phase in this operation of this batch, and it records that linkage as it goes.
Deciding which report parameters each phase should capture is a core reporting design task. Capture too little and the report cannot answer the questions quality and operations will ask; capture too much and the report is cluttered and the collection burdens the system. Well-designed phases report exactly the actual-versus-target values, timings, and material amounts that the batch report needs, so the final document assembles cleanly from data that was purpose-built for it.
At the end of a batch, the collected data is poured into a report template. The template defines the layout, which values appear where, how phases are grouped, what headers and summaries are shown, so that every batch of a given product produces a consistently formatted report. Templating turns raw captured parameters into a document that a person can read and a reviewer can approve, and it ensures batch-to-batch comparability because every report follows the same structure.
It is worth distinguishing the operational batch report from the regulated electronic batch record. The batch report is the operational document that operations and quality use routinely to see how a batch went. An electronic batch record is the formal, regulated version required in validated environments, subject to strict controls on signatures, audit trails, and integrity. The batch report often supplies the underlying data, but the electronic batch record adds the compliance rigor that regulated industries demand.
For a cloud SCADA platform overseeing distributed operations, generating batch reports centrally is a major convenience. When phase data streams to the cloud as each batch runs, reports for many sites can be assembled, stored, and searched in one place, and a remote team can pull up any batch's report without visiting the plant. Cloud-side templating also makes it easy to standardize report formats across sites, so a batch report from one facility reads the same as one from another.
A batch report is the operational document that operations and quality use routinely to review how a batch went. An electronic batch record is the formal, regulated version required in validated environments, with strict controls on signatures, audit trails, and data integrity. The batch report often supplies the data, while the electronic batch record adds the compliance rigor for regulated industries.
The data is collected during execution, not at the end. Each phase is configured with report parameters, values it captures and passes to the batch record, such as the quantity charged, the peak temperature, or the hold time. As each phase completes, its values are stamped with timestamps and stored, then assembled into the final report through a template.
A report parameter is a specific value a phase is configured to capture and report to the batch record as it runs, such as the actual quantity delivered by a charge phase or the peak temperature reached by a heat phase. Choosing the right report parameters per phase determines how complete and useful the final batch report will be.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.