SCADA Report Generation
for GMP — What Counts
as a Valid Record

GMP Record vs Report — The Distinction That Drives Everything

The terms "report" and "record" are used interchangeably in most engineering contexts. In GMP they are not the same thing. A record is primary data — the original captured evidence of what happened during a process. A report is a presentation of that data, formatted for a specific purpose. The GMP integrity requirements attach to records, not to reports. But when a report is the primary evidence for a regulated activity, it functions as a record and must be treated accordingly.

On a pharma SCADA, the clearest example of a report functioning as a record is the sanitization cycle report. The cycle happened. The report is the evidence that it happened correctly — hold duration achieved, temperatures maintained at all monitoring points, operator who initiated and released. That report is not a convenience summary of data available elsewhere. It is the regulated evidence. It must be unalterable after generation, retained for the required period, and exportable as a certified copy. If it can be deleted, regenerated with different parameters, or modified after the fact, it fails as a GMP record regardless of how detailed it looks on screen.

The test for whether a SCADA report is a GMP record is simple: would a QA reviewer, an auditor, or a regulatory inspector use this report as evidence that a regulated activity was performed correctly? If the answer is yes, it is a GMP record — and it must be designed and validated accordingly.

Three Report Types — Different Requirements for Each

Most GMP SCADA systems generate three categories of reports. Each category has different integrity requirements, different generation triggers, and different validation obligations.

Auto-Generated GMP Reports

These are reports triggered automatically by a system event or a defined schedule, containing regulated process data. The daily water quality summary (generated at 06:00, covering the previous 24 hours) and the sanitization cycle report (generated automatically at Phase 3 completion) are the standard examples for a continuous process SCADA. Both have the same set of requirements: they must be generated automatically without operator intervention, stored as unalterable electronic records immediately on generation, have a system-generated filename that cannot be modified, contain a fixed content structure with no configurable fields in the GMP section, and be retained for the full regulatory retention period.

The "no configurable fields in the GMP section" requirement is worth emphasising. A sanitization cycle report where the operator can modify the hold duration displayed, add comments to the temperature section, or adjust the timestamp is not an unalterable record — it is a form. The GMP data section of the report must be computer-generated and locked. Operator comment fields, if required, must be clearly separated from the GMP data section and must themselves be audit-trailed.

On-Demand Certified Copies

These are exports of primary data from the historian, generated on operator request for a specific purpose — investigation support, regulatory submission, periodic review. The data being exported is the primary GMP record (it lives in the historian). The export is a copy. For the copy to be usable as evidence, it must be certifiable — meaning a reviewer can confirm the exported data matches the original stored data and has not been altered in transit or after export.

This is what the certified copy header achieves. Every export from a GMP SCADA historian must include: the source system name, the export timestamp, the exporting user's ID, the parameter range and time period covered, the total record count, and a checksum or verification statement that allows the data integrity of the export to be verified. A PDF export that shows a trend graph without these header elements is not a certified copy — it is a screenshot with no verifiable connection to the original data.

Report Content as an OQ Acceptance Criterion

This is the point that most first-project engineers miss. The content of GMP reports is not a UX decision made during development. It is an acceptance criterion defined in the FDS and verified at OQ. If the FDS states that the sanitization cycle report must contain nine specific fields, then the OQ must verify that all nine fields are present in an actual generated report, with the correct values for the cycle that was executed during testing.

The OQ test for report content is not "the report generated" — it is "the report generated AND contained field X with value Y, field Z with value W, for all nine required fields." Attaching the actual generated report as an OQ evidence attachment is mandatory. The QA reviewer signs the OQ based on the evidence that the report content matches the FDS specification exactly.

This means the FDS must be specific. "The report shall contain process data" is not a testable acceptance criterion. "The report shall contain the sanitization cycle start datetime, Phase 1 start and end times, Phase 2 start time, hold duration achieved in minutes, minimum temperature at each of the five monitoring points during the hold phase, Phase 3 completion datetime, and the user ID of the operator who initiated and the operator who released PoU supply" is testable. Every field in that specification becomes an OQ check box. See the article on writing testable acceptance criteria for the full framework.

Retention, Access, and the 7-Year Requirement

GMP records on a pharma SCADA must be retained for a period defined by the applicable regulation and the site data retention policy. In most pharmaceutical manufacturing contexts the minimum is the product shelf life plus one year, or five years after the batch release date, whichever is longer. For continuous process systems like water systems and environmental monitoring, the typical practical requirement is seven years from the date of the record.

Retention is not just storage. A record that is stored but not accessible is not compliant. The SCADA must be able to query and export records from the full retention period throughout that period. This has design implications: a historian that provides online access for two years and archived access for seven years must have a consistent query and export interface for both windows. An inspector who asks for water quality data from four years ago must get the same certified copy format as data from last week. Designing the archived access to use a different query tool or a different export format creates a compliance gap.

The SCADA historian configuration article covers the technical implementation of retention periods. The relevant design principle here is: the report generation and certified copy export capability must work against archived data with the same result as it does against online data. This must be verified — not assumed — during the validation lifecycle.

What the FDS Must Document for Reports

Every GMP report must be specified in the FDS before development begins. The specification must be complete enough to serve as OQ acceptance criteria — which means it must define the trigger, the content field by field, the storage behaviour, and the retention period. For each report type, the FDS needs to answer these questions:

• What triggers generation? Scheduled time, system event, or operator action — and who can trigger it if operator-initiated.
• What fields does it contain? Named explicitly. Not "process parameters" — each parameter by name, with units and the source tag it is drawn from.
• Where is it stored? Historian table, file system path, or both. Storage must be in the validated environment, not on an operator workstation local drive.
• Who can access it? Read-only access for all roles including Read-Only is the standard. No role should be able to delete or modify a stored GMP report.
• Can it be regenerated? For auto-generated GMP reports, the answer is no — regeneration would allow the original to be replaced. The original must be preserved and any additional copy must be clearly labelled as a copy with a different timestamp.
• What does the certified copy export contain? The six certified copy header elements must be listed, along with the export format (PDF, CSV, or both) and the checksum mechanism.