Utility description: Potency Assay Trend
Potency Assay Trend Checker — Statistical Potency Trend Analysis (SPC)
ℹ️ Utility performs statistical analysis of historical potency data for medicinal products in accordance with Statistical Process Control (SPC) principles and ICH Q10 / VICH GL requirements:
• Linear Regression: Calculation of trend Slope and Coefficient of Determination (R²) to assess direction of changes.
• Shewhart Control Charts: Automatic calculation of mean, standard deviation (SD), upper and lower control limits (UCL/LCL ±3SD) and warning limits (±2SD).
• Westgard Rules: Algorithmic check of data sequences for systematic errors (mean shifts, drift, out-of-control limits).
⚠️ IMPORTANT:
• To ensure statistical significance, it is recommended to use a sample of at least 10–15 consecutive batches.
• Detection of statistically significant trends allows initiating corrective actions before parameters go out of specification (OOS).
Usage:
PotencyAssayTrendChecker.exe → demo mode (console output)
PotencyAssayTrendChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,ManufacturingDate,PotencyResult_IU_per_dose,TargetPotency_IU_per_dose
Example:
VAC-001,2025-01-15,105.5,100.0
— WHY IS THIS NEEDED?
Trend monitoring is a mandatory element of the Pharmaceutical Quality System (PQS) according to ICH Q10 and Stage 3 of Process Validation (Continued Process Verification).
Gradual change in activity may indicate raw material degradation, equipment wear, or uncontrolled drift of Critical Process Parameters (CPP).
Early detection of such deviations allows conducting an investigation and implementing CAPA before batch defects occur.
⚠️ CRITICAL:
• 7x Mean Rule: Presence of 7 consecutive points on one side of the central line indicates a statistically significant process shift.
• Trend Rule: Presence of 6 or more consecutively increasing or decreasing points indicates systematic drift.
• Out of 3SD: Single point beyond control limit indicates Special Cause Variation requiring investigation.
• Homoscedasticity: Analysis assumes stability of data variance over time. If spread changes, baseline recalculation is required.
Key features:
• Automated calculation of process statistical parameters
• Detection of Westgard rules violations and other instability criteria
• Quantitative assessment of trend direction and reliability
• Generation of reports compliant with QA audit and regulatory inspection requirements
• Support for ICH Q10 (Pharmaceutical Quality System) and VICH GL requirements
Critical parameters:
• Trend Slope: Indicator of parameter change rate
• R-Squared: Measure of linear model reliability
• Westgard Rules Violations: Indicators of loss of statistical control
• Process Status: OK (Under Control), WARNING (Investigation Required), ALERT (Out of Control)
💡 Usage tips:
1. Data Integrity: Use only verified results from released batches that have passed full quality control cycle.
2. Analysis Frequency: Recommended to perform analysis monthly or after each batch release as part of Annual Product Review (APR/PQR).
3. Status Interpretation: "WARNING" status indicates need for technological investigation, even if results are within specification.
4. Documentation: JSON reports must be saved as objective evidence of trend monitoring.
5. Corrective Actions: Upon detection of significant trend, initiate deviation management procedure and assess impact on previously released batches.
⚠️ Note: Unlike batch-by-batch specification compliance control (Pass/Fail), this tool is designed to assess the State of Control of the manufacturing process dynamics, which is a requirement of modern GMP standards.
input.csv
BatchNumber,ManufacturingDate,PotencyResult_IU_per_dose,TargetPotency_IU_per_dose
VAC-2025-001,2025-01-15,102.5,100.0
VAC-2025-002,2025-02-10,101.8,100.0
VAC-2025-003,2025-03-05,103.1,100.0
VAC-2025-004,2025-04-12,99.5,100.0
VAC-2025-005,2025-05-20,100.2,100.0
VAC-2025-006,2025-06-18,98.7,100.0
VAC-2025-007,2025-07-22,97.5,100.0
VAC-2025-008,2025-08-15,96.8,100.0
VAC-2025-009,2025-09-10,95.2,100.0
VAC-2025-010,2025-10-05,94.1,100.0
VAC-2025-011,2025-11-12,93.5,100.0
VAC-2025-012,2025-12-01,92.0,100.0
URS & FS — User Requirements and Functional Specification
This document describes the controlled interface and behaviour of PotencyAssayTrendChecker for Potency Assay Trend Checker.
Domain limits and critical parameters
Key fragments from the source description are shown below. Before production use, limits must be verified against the approved specification, registration dossier and local SOPs.
- Potency Assay Trend Checker — Statistical Potency Trend Analysis (SPC)
- ℹ️ Utility performs statistical analysis of historical potency data for medicinal products in accordance with Statistical Process Control (SPC) principles and ICH Q10 / VICH GL requirements:
- • Shewhart Control Charts: Automatic calculation of mean, standard deviation (SD), upper and lower control limits (UCL/LCL ±3SD) and warning limits (±2SD).
- • Westgard Rules: Algorithmic check of data sequences for systematic errors (mean shifts, drift, out-of-control limits).
- PotencyAssayTrendChecker.exe → demo mode (console output)
- PotencyAssayTrendChecker.exe input.csv output.json → evaluate your data
- BatchNumber,ManufacturingDate,PotencyResult_IU_per_dose,TargetPotency_IU_per_dose
- Trend monitoring is a mandatory element of the Pharmaceutical Quality System (PQS) according to ICH Q10 and Stage 3 of Process Validation (Continued Process Verification).
- Gradual change in activity may indicate raw material degradation, equipment wear, or uncontrolled drift of Critical Process Parameters (CPP).
- ⚠️ CRITICAL:
- • Out of 3SD: Single point beyond control limit indicates Special Cause Variation requiring investigation.
- • Support for ICH Q10 (Pharmaceutical Quality System) and VICH GL requirements
- Critical parameters:
- 4. Documentation: JSON reports must be saved as objective evidence of trend monitoring.
- ⚠️ Note: Unlike batch-by-batch specification compliance control (Pass/Fail), this tool is designed to assess the State of Control of the manufacturing process dynamics, which is a requirement of modern GMP standards.
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
|---|
| URS-001 | The utility shall accept an input.csv file for Potency Assay Trend Checker with headers defined in the data contract. | High | The file is processed without manual header editing. |
| URS-002 | The utility shall perform deterministic QC evaluation without machine learning and without probabilistic conformance decisions. | High | Identical input data, rule version and configuration produce reproducible results. |
| URS-003 | The utility shall validate mandatory fields, data types, ranges, units and domain plausibility. | High | Schema, conversion and range errors are explicitly reported. |
| URS-004 | The utility shall apply domain limits and rules from the description, approved specification, registration dossier and local SOPs. | High | Each check has PASS/WARNING/FAIL and a clear message. |
| URS-005 | The utility shall generate output.json with machine-readable results, source values, warnings, failures and critical findings. | High | JSON is suitable for LIMS/ELN/MES integration and QA/QC review. |
| URS-006 | The utility shall preserve traceability between batch/sample, input file, applied rules and final status. | High | Output contains identifiers, checked parameters and audit metadata. |
| URS-007 | The documentation shall support IQ/OQ/PQ, CSV/CSA and review by internal QA or inspectors. | Medium | URS, FS, input/output contract and test scenarios are supplied with the utility. |
| URS-008 | The utility shall be used as a QC decision-support tool and not as a substitute for approved specifications and QA/QP release decision. | Medium | Documentation states change control and limit-verification expectations. |
input.csv contract
| # | Field | Type | Sample | Purpose |
|---|
| 1 | BatchNumber | string / controlled vocabulary | VAC-2025-001 | Batch or lot identifier used for traceability. |
| 2 | ManufacturingDate | string / controlled vocabulary | 2025-01-15 | Controlled input parameter for deterministic QC rules. |
| 3 | PotencyResult_IU_per_dose | decimal | 102.5 | Potency/activity; critical efficacy-related parameter. |
| 4 | TargetPotency_IU_per_dose | decimal | 100.0 | Potency/activity; critical efficacy-related parameter. |
BatchNumber,ManufacturingDate,PotencyResult_IU_per_dose,TargetPotency_IU_per_dose
VAC-2025-001,2025-01-15,102.5,100.0
VAC-2025-002,2025-02-10,101.8,100.0
VAC-2025-003,2025-03-05,103.1,100.0
Input validation rules
| ID | Field | Rule | Criticality |
|---|
| VR-001 | BatchNumber | The field shall match an approved dictionary or accepted string representation. | High |
| VR-002 | ManufacturingDate | The field shall match an approved dictionary or accepted string representation. | High |
| VR-003 | PotencyResult_IU_per_dose | The field shall match an approved dictionary or accepted string representation. | High |
| VR-004 | TargetPotency_IU_per_dose | The field shall match an approved dictionary or accepted string representation. | Medium |
FS — Functional Specification
| ID | Function | Implementation |
|---|
| FS-001 | CLI execution | Support execution modes: demo mode without arguments and production mode input.csv output.json. |
| FS-002 | CSV import | Read input.csv in UTF-8/CSV-compatible format and validate header and expected columns. |
| FS-003 | Schema validation | Check mandatory fields, column count, unknown key fields and empty mandatory values. |
| FS-004 | Type conversion | Convert numeric, flag and text values; invalid format is recorded as a row-level error. |
| FS-005 | Domain rule engine | Apply rules for Potency Assay Trend Checker, including critical limits from the description and approved specification. |
| FS-006 | Status aggregation | Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance. |
| FS-007 | JSON export | Write output.json with detailed checks, source values, warnings, failures and critical findings. |
| FS-008 | Audit support | Keep result structure suitable for review, deviation investigation and calculation reproduction. |
| FS-009 | Integration contract | Support the scenario LIMS/ELN/MES → input.csv → utility → output.json → portal/admin review. |
| FS-010 | Error handling | Return explicit messages for missing file, empty CSV, invalid schema, output write failure and invalid format. |
Example output.json
{
"utilityId": "potencyassaytrendchecker",
"utilityFolder": "PotencyAssayTrendChecker",
"package": "Vet",
"overallStatus": "PASS|WARNING|FAIL",
"sourceFile": "input.csv",
"processedAtUtc": "2026-06-10T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "VAC-2025-001",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-001"
},
{
"parameter": "ManufacturingDate",
"value": "2025-01-15",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-002"
},
{
"parameter": "PotencyResult_IU_per_dose",
"value": "102.5",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-003"
},
{
"parameter": "TargetPotency_IU_per_dose",
"value": "100.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-004"
}
],
"criticalFindings": [],
"warnings": [],
"audit": {
"inputHash": "sha256:<calculated at runtime>",
"rulesVersion": "<utility executable version>",
"documentation": "PotencyAssayTrendChecker.documentation.html"
}
}
Traceability matrix
| URS | FS | Test | Evidence |
|---|
| URS-001 | FS-001, FS-002 | OQ-001 | Verify execution and import of valid input.csv. |
| URS-002 | FS-005, FS-006 | OQ-004 | Repeat the same dataset and compare output.json. |
| URS-003 | FS-003, FS-004, FS-010 | OQ-002, OQ-003 | Verify missing columns and invalid types. |
| URS-004 | FS-005, FS-006 | OQ-004, PQ-001 | Verify critical deviations on real/boundary data. |
| URS-005 | FS-007, FS-009 | OQ-005 | Verify JSON schema and downstream-system suitability. |
| URS-006 | FS-008 | OQ-006 | Verify identifiers and audit metadata. |
| URS-007 | FS-008, FS-010 | IQ-001, OQ-007 | Verify documentation completeness and control evidence. |
| URS-008 | FS-005, FS-008 | PQ-002 | Verify review workflow and no replacement of QA decision. |
IQ/OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|
| IQ-001 | Verify executable, input.csv, documentation and checksum availability. | Delivery set is complete; version is recorded. |
| OQ-001 | Valid sample row from input.csv. | PASS or acceptable WARNING according to rules. |
| OQ-002 | Remove a mandatory CSV column. | Schema error or FAIL with missing-column reference. |
| OQ-003 | Place a non-numeric value into a numeric field. | Type-conversion error with row/field reference. |
| OQ-004 | Set a critical parameter outside the limit. | FAIL and critical finding. |
| OQ-005 | Verify output.json structure. | All mandatory sections are present and JSON is valid. |
| OQ-006 | Verify batch/sample traceability. | Input and result identifiers match. |
| PQ-001 | Verify 3–5 real user batches/samples. | Result is confirmed by QC/QA review. |
| PQ-002 | Verify deviation workflow and manual QA decision. | Utility supports review but does not replace approved decision. |
QA/QC and change control
- Do not rename columns without updating validator, documentation and test set.
- Retain
input.csv, output.json, executable version and checksum. - Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
- Critical limits shall be verified against the approved specification, registration dossier and local SOPs.
- The utility provides structured QC decision support; final release decision remains with QA/QP and approved procedures.