Process Validation Software: CPV, PPQ and Digital Execution

A Cpk value computed in an unvalidated spreadsheet and quietly feeding a batch disposition decision is a shadow system, not a shortcut. If the calculation influences release, it needs the same rigor as the batch record it's judging.

Process Scope

Process validation software covers the two most data-intensive stages of the process validation lifecycle: Process Performance Qualification (PPQ), the Stage 2 batches run under actual production conditions to establish a statistical baseline, and Continued Process Verification (CPV), the Stage 3 ongoing monitoring that confirms the process stays in control for the rest of its commercial life. This is distinct from equipment or computer system validation software — the object being validated is the manufacturing process itself, measured statistically across batches, not a piece of equipment or an application.

Required Records

• ✓ PPQ protocol and report defining the qualification batches, acceptance criteria, and statistical justification for batch count.
• ✓ Batch genealogy linking raw material lots through processing steps to each data point feeding the statistical trend.
• ✓ CPV monitoring plan defining which parameters are tracked, at what frequency, against what control limits.
• ✓ Control charts and capability reports (Cpk/Ppk) generated from the actual batch data, not manually reconstructed.
• ✓ Excursion and deviation records for any out-of-trend result, linked to the specific batch and parameter.

Digital Workflow

Batch data should flow automatically from the MES, historian, or LIMS into the statistical engine, rather than being manually transcribed by someone copying values into a spreadsheet. From there, control charts and capability indices update continuously, with statistically significant drift flagged automatically for review rather than surfacing only when someone happens to open a static report. The PPQ baseline should carry forward into CPV monitoring within the same system, so every new batch is trended against the original qualification standard, not a baseline quietly redefined by whatever the process has been doing lately.

Deviation and Change Management

A control limit or alert threshold determines when a process deviation gets flagged, which makes it GxP-critical configuration — the same category of decision as a specification limit in a LIMS. Changing it based on informal statistical judgment, without documented change control and QA review, removes the safeguard the threshold exists to provide. An out-of-trend result should generate a linked deviation automatically, not depend on someone noticing a chart trending the wrong way during a periodic report review.

Reporting

CPV reporting should run on a defined cadence — typically periodic management and QA review — summarizing trend performance against the PPQ baseline, any excursions and their disposition, and any control limit changes made since the last report along with their documented rationale. A report that only shows the current state without the history of what changed and why doesn't give a reviewer enough to judge whether the process is genuinely stable or drifting slowly under a series of small, individually-justified limit adjustments.

Vendor Evaluation Criteria

• • Direct integration with MES, historian, or LIMS for automated data capture, not manual entry as the primary path.
• • Genuine statistical process control methods — real control charts and capability indices, not averages dressed up as trending.
• • PPQ-to-CPV continuity within one system, so the qualification baseline isn't lost when ongoing monitoring begins.
• • Automatic drift flagging rather than static reports someone has to remember to open and interpret.
• • A validated statistical engine with its own change control over calculation logic and control limits, not a black box.

How GoVal Supports Process Validation Software

GoVal manages the validation of the systems executing PPQ and CPV — classifying the statistical monitoring platform by GAMP 5 category, routing control limit and alert threshold changes through change control with documented QA review, and keeping PPQ baseline data and ongoing CPV evidence linked as one traceable, audit-trailed record rather than scattered across disconnected spreadsheets and standalone tools.

Related Topics

Frequently Asked Questions