SystemManufacturing Intelligence

Continued Process Verification (CPV)

Continued process verification that reads each approved batch against the signed CPV plan, charts it through the control strategy's links, traces a signal to the parameter that moved and changes the plan under two signatures.

See one slow slide traced to the parameter that moved ↓
Watch with transcript →
The problem

Preservative content slid for sixteen batches before the run rule fired

Every commercial process has to be shown to stay in its validated state, batch after batch. In most plants an MSAT engineer exports results from LIMS and parameters from the batch record and the historian, and builds the charts in a spreadsheet each month, one attribute at a time.

A run rule set to avoid false alarms sees a gentle slide late, and the parameter behind it is often one that is recorded and never trended, like a hold time before filling. The link between them lives in a risk assessment document, so the signal surfaces weeks after the schedule change that caused it.

Built forMSAT process monitoring leadsQA validation leadsStatisticiansProduction managers

The Problem Today

A slow slide inside specification is seen late, because the parameter behind it is recorded but never charted.

Stage 3
of FDA process validation: an ongoing program on process data published

Pulled into spreadsheets by hand

  • LIMS
  • eBR
  • Historian
  • CPV plan
  • One attribute at a timeThe link to a parameter sits in a risk document, off the chart
  • Signals found a month lateCharts are built at the report cycle, long after the batch

The Solution

  1. Each batch read as QC approves itResults and parameters mapped to the signed plan's rows and columns
  2. Run rules and capabilityRules from the signed plan; normality tested before any Ppk
  3. Traced down the linksLinked parameters first, then recorded ones nobody charted
  4. Plan changed under two signaturesAn MSAT author, then a QA approval; tightening starts at once

Built-in controls

  • Only the run rules the signed plan enables
  • Assessments, plans and reports signed by different people
  • A correlation is evidence; people decide the cause

What You Get

CPV becomes a running program on every batch, read through the links the control strategy says matter.

  • Drift caught inside specificationTraced to its parameter while batches still meet their limits
  • Summaries a client can fileEach figure sourced, sent under the quality agreement
  • A control strategy you can queryWhich parameters feed an attribute, and why a link was added
Features

Continued process verification features, from a batch read to a new plan

MSAT, QA, statistics and production follow one oral solution whose preservative content slid inside specification after a filling schedule changed.

demoThe plant, client, people, products, batches and test costs here are sample data.

  1. 01Linkage matrix

    Continued process verification through the control strategy's linked pairs

    • Only linked parameter-attribute pairs drawn. The screen is the control strategy itself, so an engineer reads a signal through the links the risk assessment says matter.
    • Each new batch read as QC approves it. Results from LIMS and parameters from the eBR and historian land on the matrix the morning they are approved.
    • Agents at work beside the matrix. The batch reader, rule runner, capability calculator and link tracer each show their sources, confidence and hand-off.
  2. 02Link traced

    A recorded-only parameter found behind the slide, charted over the attribute

    • Parameter chart over attribute chart. Batch by batch, the hold time sits above the preservative content it affects, with run-rule marks and sources.
    • Recorded-only parameters searched next. Hold time sat in the eBR but was trended nowhere; the link tracer finds it and shows the planning memo behind the change.
    • A correlation shown as evidence. The slope, the correlation and the hold time study behind the mechanism are on screen, and the cause stays a person's call.
  3. 03Statistician challenger

    CPV signal challenged on measurement, sampling and mixed populations

    • Measurement and sampling ruled out with records. A column lot change is checked against the check standard before anyone blames the process.
    • Capability split where the process changed. The window holds two processes, so the report gives capability before and since the change beside the blended figure.
    • A state-of-control claim struck from the draft. A draft that said the process remained in a state of control with a signal open is changed before the MSAT lead signs.
  4. 04Assessment

    Signal assessment classified and signed by the MSAT lead as author

    • Each point opened before it is ruled. The MSAT lead must keep each challenger point open on screen before ruling, so each ruling rests on what was seen.
    • Classification chosen by the author. Process cause inside specification, process failure, measurement cause or no assignable cause: the MSAT lead picks one and signs.
    • QA countersigns after the author. The QA validation lead reads the signed assessment, then countersigns or returns it, giving a reason code either way.
  5. 05Rehearsal

    Heightened monitoring options rehearsed with tests, cost and predicted Ppk

    • Assumptions open to edit. Extra samples, the test cost and the hold time assumed can be changed, and each option recomputes at once.
    • How soon a person sees each batch. Heightened monitoring moves review from the monthly cycle to within days of each batch, shown before the option is chosen.
    • The schedule decision left to production. Capping hold times is a recommendation to the production manager, who owns the filling schedule.
  6. 06Plan redline

    CPV plan redline drafted from the signal, with hold time linked and monitored

    • The redline of the signed plan. Changes show against the controlled plan, so QA reads exactly what moves: links, monitoring levels and run rules.
    • Safer changes go first. Heightened monitoring starts when the author signs; lowering a level or turning a rule off waits for QA.
  7. 07Plan approved

    CPV plan version approved by the QA validation lead after reading the redline

    • Author and approver are two people. The MSAT lead authors and the QA validation lead approves, each with their own password and signature meaning.
    • The client told as the agreement says. A plan change on a client's product starts the client notice due under that product's quality agreement.
  8. 08Matrix redrawn

    The linkage matrix redrawn with the two new links in force

    • New links in force once QA approves. Hold time now reads on each batch against both attributes it affects, with an alert of its own.
    • Monitoring level shown on each attribute. Routine, heightened or reduced sits under each attribute, so anyone can see how closely it is watched.
  9. 09CPV report

    Monthly CPV report drafted with every figure cited, awaiting three signatures

    • Every figure cited to its source. Any number in the report leads straight to its LIMS, batch record or historian source.
    • Author, statistician and QA sign in order. Three different people sign the report, and it waits until the open signal's assessment is countersigned.
    • Ppk with its method, window and count. Each capability figure states its normality test, method and window, so a reviewer can follow how it was reached.

MSAT owns the plan, QA approves it, statistics checks it, production acts

Monitoring leads read and propose, QA signs each version, the statistician sets the methods, and production owns the schedule.

MSAT process monitoring leads

Own the CPV plans, assess signals and propose plan changes

  • Which link moved, beside the chart
  • Assessments drafted and already challenged
  • Plan redlines rehearsed before signing
QA validation leads

Countersign signal assessments and approve each plan version and report

  • A redline of exactly what changes
  • Loosening that waits for their signature
  • Rules derived from past signals to approve
Statisticians

Design run rules and capability methods and review each report

  • Normality tested before any Ppk
  • Mixed populations split, not blended
  • Weekly batch reads reviewed by sample
Production managers

Own the filling schedule and hold times on the line

  • What a schedule change costs the product
  • Recommendations they decide on
  • Alerts on hold time before it matters

Seven agents read, test, trace and draft, and people sign every step

Each shows its plan, sources and confidence, and passes its result on by name.

Batch reader

Reads each approved batch's results and parameters from LIMS, the eBR and the historian and maps them to the plan.

  • Reads no result QC has not approved
Rule runner

Applies the signed plan's run rules to the linked cells and the attributes.

  • Applies no rule the plan does not enable
  • Clears no signal
Capability calculator

Tests normality first, names the method and window, and computes Ppk.

  • Quotes no Ppk without its method, window and count
Link tracer

Follows a signal down its linked parameters, then searches recorded but unlinked ones, and proposes links with their evidence.

  • Adds no link to the plan
  • Treats a correlation as evidence, never as a cause
Report drafter

Drafts signal assessments and the monthly CPV report, with every figure cited.

  • Signs nothing
  • Sends nothing outside the CDMO
Statistician challenger

Attacks each signal and the agents' own draft on measurement, sampling, normality, mixed populations and known causes.

  • Closes no point itself
Plan steward

Drafts plan redlines, monitoring rehearsals and the client summary.

  • Applies no plan change
  • Lowers no level without QA
More screens

Signals across products, agreed causes, the audit trail and the run rules

Around one product's matrix: every open signal in the plants, the causes the agents check first, what each signer did and the settings behind the reads.

Open signals across products and plantsStage 3 products across plants and clients, with each open signal's rule, owner, due date and status, and the week's batch reads.
Agreed causes the agents check firstEach signal's agreed cause is kept and checked first on the next signal of its kind, and a rule derived from them applies only after QA approves it.
Each read, approval and signature loggedActions with the record, the reason and the meaning of each signature, downloadable as CSV or as the signal's evidence pack.
Run rules, clocks and thresholdsRun rules per attribute, the read trigger, the signal clock, monitoring thresholds, residency and retention; loosening waits for QA's signature.

demoSample data, from the working solution.

Only a process failure opens a deviation, and the MSAT lead decides which

Whether a signal is a deviationThe MSAT lead classifies it and signs, and QA countersigns; a signal inside specification is assessed, and only a process failure opens a deviation.
What the CPV plan saysThe MSAT lead authors each version and the QA validation lead approves it; no agent applies a change.
Whether a correlation is the causeThe link tracer brings the evidence, and the engineer and QA decide what it means.
How long the bulk is heldThe production manager owns the filling schedule and decides any cap on hold times.
Whether a batch goes to marketThe plant's QA head dispositions what the plant made, and the client's own quality person releases it to market.

Questions on continued process verification from MSAT and QA

What is continued process verification?

Continued process verification is the ongoing program, after process qualification, that shows a commercial process stays in its validated state batch after batch. Here agents read each approved batch against the signed CPV plan, apply its run rules, test capability, trace signals down the control strategy's links and draft the report; MSAT and QA sign.

Is ongoing process verification the same thing?

Yes, the same work under two names. FDA guidance calls it continued process verification, and the EU GMP annex on qualification and validation calls it ongoing process verification.

What goes into a CPV plan?

The critical quality attributes and critical process parameters, the pairs the risk assessment links, limits, run rules, monitoring levels and the report cycle. MSAT authors each version and QA approves it, and the plan changes as the process teaches the plant.

How is process capability Ppk reported?

Normality is tested first, and the method, window and number of batches are named with each figure. Where the window holds two processes, capability before and after the change is reported beside the combined figure.

What happens when a signal fires inside specification?

A signal opens with an assessment clock, the agents trace it down the linked parameters and then the recorded ones, and the statistician challenger attacks it. The MSAT lead classifies it, and only a process failure becomes a deviation.

What is stage three process validation?

The third stage of process validation in FDA guidance, after process design and process qualification: continued process verification of the commercial process, batch after batch. Here it runs on the signed CPV plan, each signal is classified by the MSAT lead as author and countersigned by QA, and the monthly report waits for three signatures.

Bring one product's
last year of batches.

Send a CPV plan with a year of LIMS results and batch record parameters, and we will draw its linkage matrix and read the latest batch.