|

Computerized System Performance Qualification (PQ)

1. Purpose and Scope

Performance Qualification establishes documented evidence that a computerized system performs reliably under routine operating conditions and intended use.

This phase confirms that the system supports actual business processes, real users, and expected data volumes without compromising data integrity, accuracy, or compliance. It applies to all GxP-relevant systems where system performance has direct or indirect impact on product quality, regulatory decisions, or data reliability. Performance Qualification evaluates system performance in real operational context.

2. Role of PQ within the Validation Lifecycle

Performance Qualification is the final verification phase following successful completion of Installation Qualification and Operational Qualification. Within the lifecycle:

  • Installation Qualification confirms correct installation
  • Operational Qualification verifies functional behavior
  • Performance Qualification confirms performance under routine conditions

PQ provides confirmation that the system is fit for intended use in the actual operating environment.

3. PQ Execution Strategy

Performance Qualification must reflect real system use. Execution must be:

  • based on actual business workflows
  • performed by trained or qualified users
  • executed using realistic or production-equivalent data
  • conducted in the intended operating environment
  • representative of routine system usage

The goal is to demonstrate consistent and reliable performance under normal conditions rather than controlled test scenarios. The diagram below illustrates how Performance Qualification verifies system performance under routine operating conditions. It shows the relationship between business processes, users, system operation, and data processing, and how these elements generate records that are evaluated for consistency, accuracy, and stability. The operational conditions layer emphasizes that PQ is performed under realistic workload, concurrent usage, and sustained operation.

Performance Qualification Operational Use Model diagram showing flow from business processes and users through system operation and data processing to outputs and performance evaluation, with an operational conditions layer representing routine environment, concurrent users, realistic data volumes, and sustained system operation.

4. Business Process Verification

Performance Qualification confirms that complete business processes execute correctly from start to finish. Verification includes:

  • execution of full end-to-end workflows without interruption
  • correct sequencing of process steps and system transitions
  • interaction between multiple system functions within a process
  • consistency of outcomes across repeated executions
  • handling of typical operational scenarios and variations
  • verification that no manual workarounds are required

The focus is on operational continuity and process integrity.

5. Data Integrity in Routine Operation

Performance Qualification must demonstrate that data integrity controls remain effective during actual system use. Verification includes:

  • Audit trail consistency
    Confirm that all user actions, system events, and record changes are captured automatically during routine operations without gaps.
  • Attribution and traceability
    Verify that each action is linked to a unique user identity, with accurate timestamps reflecting system time synchronization.
  • Original data preservation
    Confirm that original values are retained and that any modifications are recorded without overwriting prior data.
  • Data lifecycle traceability
    Verify that data can be traced from initial entry through processing, review, approval, and reporting.
  • Concurrent usage integrity
    Confirm that simultaneous user activity does not result in data conflicts, overwrites, or loss.
  • Data storage and retrieval reliability
    Verify that records are consistently stored, retrievable, and protected from corruption during routine use.
  • System-enforced controls
    Confirm that data cannot be altered or deleted outside controlled and authorized processes.

Data integrity must be demonstrated under realistic workload and user interaction conditions.

6. User Interaction and Usability

Performance Qualification evaluates system behavior when used by intended personnel under routine conditions. Verification includes:

  • Execution of routine tasks
    Confirm that users can perform assigned tasks correctly following approved procedures without system-related barriers.
  • User interface clarity
    Verify that system screens, prompts, and messages support correct decision-making and reduce risk of user error.
  • Error prevention mechanisms
    Confirm that system controls prevent invalid entries, incomplete data submission, or incorrect workflow execution.
  • User role alignment
    Verify that users only access functions appropriate to their roles during actual operations.
  • Training effectiveness support
    Confirm that trained users can operate the system without ambiguity or need for undocumented actions.
  • Consistency of user experience
    Verify that system behavior remains predictable across different users and sessions.
  • Human-system interaction reliability
    Confirm that system response supports efficient and accurate task completion without delays or confusion.

The system must enable correct and consistent use rather than rely on user workarounds.

7. Interface and Operational Data Flow

Performance Qualification must confirm that interfaces perform reliably during routine operations. Verification includes:

  • Real workflow data exchange
    Confirm that data is transferred correctly as part of actual business processes, not isolated test transactions.
  • End-to-end data flow integrity
    Verify that data originating in one system is received, processed, and stored correctly in connected systems.
  • Data mapping accuracy under load
    Confirm that field mappings remain accurate when handling realistic data volumes and variations.
  • Timing and synchronization
    Verify that data transfers occur at the correct time and sequence within operational workflows.
  • Handling of routine transaction volumes
    Confirm that interfaces process expected data volumes without delay, backlog, or failure.
  • Error detection and recovery
    Verify that failed transfers are detected, logged, and resolved without data loss or duplication.
  • Reconciliation capability
    Confirm that data can be reconciled between source and destination systems during routine operations.

Interfaces must perform as an integrated part of the operational system environment.

8. System Performance and Stability

Performance Qualification must demonstrate stable and consistent system operation under expected workload conditions. Verification includes:

  • Response time under routine use
    Confirm that system response times remain within acceptable limits during normal operations.
  • Concurrent user performance
    Verify that system performance is maintained with multiple users performing tasks simultaneously.
  • Data processing capacity
    Confirm that the system processes realistic data volumes without delay, error, or degradation.
  • Sustained operation
    Verify that the system operates continuously over defined periods without crashes or instability.
  • System resource utilization
    Confirm that CPU, memory, and storage usage remain within acceptable limits during operation.
  • Performance consistency
    Verify that repeated execution of processes produces consistent performance outcomes.
  • Recovery from routine interruptions
    Confirm that the system recovers correctly from events such as session timeouts or temporary connectivity loss.

System performance must support reliable and uninterrupted operation in the production environment.

9. Error Handling in Routine Use

Performance Qualification must confirm that operational errors are managed in a controlled and compliant manner. Verification includes:

  • detection of errors during routine operations
  • clear and accurate system error messages
  • prevention of data corruption during error conditions
  • controlled recovery and continuation of processes
  • logging and traceability of error events

Errors must not compromise system integrity or data reliability.

10. PQ Protocol Structure and Execution

Performance Qualification must be executed using protocols aligned with real operational scenarios. The protocol must define:

  • business workflows to be executed
  • user roles and responsibilities
  • data sets representative of routine use
  • acceptance criteria
  • evidence requirements

Execution must demonstrate alignment with intended use and operational conditions.

11. Acceptance Criteria

Acceptance criteria for Performance Qualification must confirm that the system is fit for routine operational use. Criteria include:

  • Successful end-to-end process execution
    All defined business workflows must execute completely and correctly without interruption or deviation.
  • Consistent data accuracy
    Data must be processed, stored, and reported accurately across all executed scenarios.
  • Sustained data integrity
    Audit trails, record protection, and traceability must remain intact during routine operations.
  • Reliable user operation
    Intended users must be able to perform tasks correctly and consistently without system-related issues.
  • Interface reliability under operational conditions
    Data exchanges must be accurate, complete, and consistently executed during real workflows.
  • Stable system performance
    The system must operate without crashes, slowdowns, or data loss under expected workload.
  • Controlled error management
    Errors must be detected, handled, and documented without impacting system integrity.
  • Reproducibility of results
    Repeated execution of processes must produce consistent and predictable outcomes.

All acceptance criteria must be met or deviations resolved prior to system release.

12. Deliverables and Approval

Performance Qualification results in documentation demonstrating system performance under operational conditions. Typical deliverables include:

  • executed PQ protocol
  • workflow execution records
  • system-generated outputs and reports
  • deviation records and resolutions
  • summary report

Approval confirms readiness for routine use.

13. Link to Ongoing Lifecycle Control

Performance Qualification establishes that the system is fit for intended use at the time of release. This validated state must be maintained through:

  • change control
  • periodic review
  • monitoring of system performance

Any change to workflows, users, data volumes, or interfaces must be evaluated for impact and may require requalification. PQ represents the transition from validation to controlled operational use.