Hello Guest! Log In or Register now. Lost Password? Click Here to Reset

Ask About Validation

Writing & Executing a Software Validation Protocol: Plain and Simple

Writing & Executing a Software Validation Protocol: Plain and Simple


This quick and easy guide describes methods and approaches for writing a validation protocol that can help ensure a thorough validation effort. It also provides some tips and tricks on executing the protocol and documenting the results.

While this book was written primarily for those new to validation projects and the effort required gathering sufficient evidence to support validation claims , experienced folks will likely find nuggets to help improve their efforts.



Results 1 to 6 of 6
  1. #1
    Validation Analyst
    Join Date
    Mar 2009
    Posts
    7

    Default Periodic review of equipment

    Hi,

    I have been given the task of generating a SOP for periodic review of equipment. I havent had much exposure in this area and would appreaciate if anyone could provide me with the vital information that should go into this SOP (including what assessment forms would need to be filled out) or if anyone would have a template for this SOP.

    Kind regards
    SFlan

  2. #2
    Forum Creator gokeeffe's Avatar
    Join Date
    Oct 2006
    Location
    Ireland
    Posts
    1,215

    Default

    Hi SFlan,

    First of all you need to find out what regulatory aspect you are basing this review against. When you know this I would then set up a matrix and analyse each equipment type against this. The result of this assessment would then allow you to identify any gaps that exist and then use these gaps to do any remediation testing that needs to occur.

    The initial matrix may look something like:

    # Requirement Finding Description
    1 General Principals of Software Validation - Final Industry Guidance,
    GHTF 5.3 & 5.4
    Computer HW/SW validation requirements verified, as appropriate
    ● Application source code
    ● Training of operators
    ● Security
    ● Software Configuration Control
    ● Disaster Recovery, Backup & Restore
    ● System logbook
    ● Validated Version
    2 FDA General Principals of Software Validation, Final Industry Guidance and GHTF 5.4, pg 10 Failure Modes/Alarms verification
    3 FDA General Principals of Software Validation, Final Industry Guidance and GHTF 5.4, pg 11 Boundaries Challenge Testing (ex. response to unacceptable input or output values)
    Graham O'Keeffe
    Director of Operations
    Premier Validation Ltd
    Website: www.premiervalidation.com
    Forum: www.askaboutvalidation.com
    LinkedIn: LinkedIn Profile


  3. #3
    Validation Analyst
    Join Date
    Sep 2009
    Posts
    11

    Default

    We have an in-house periodic review procedure which has a number of forms capturing information in relation to equipment/facilities/utilites and ccomputerised systems.

    Starting point should to define what equipment you are going to review first and what criteria you are using for this. A risk-based approach will help you define your periodic review schedule based on frequency/duration of operation, age of equipment (e.g. length of time since last qualification) criticality (business criticality and with respect to quality critical attributes of your manufacturing process), frequency of routine maintenance etc. etc. All this information should help you define a schedule indicating that your most critical and/or oldest systems will be reviewed first.

    Review then will concentrate on performance history of the equipment as determined through historical review of planned preventative maintenance, breakdowns, service reports, calibration certificates (including drift analysis), deviations, audit observations, change control etc. Maintenance and calibration should be reviewed not only to demonstrate that the activities were performed on time and passed acceptance criteria but also that they are still fit for purpose - is instrument criticality properly defined, do critical instruments have correct range, accuracy etc.?

    Design criteria should be checked to ensure that the P&ID is still reflective of the equipment, the equipment meets current regulatory requirements, review original validation documents and perform gap analysis - are original materials of construction still acceptable to industry etc. Again, a lot of this is driven by a risk-assessment.

    The output of all of this should be a decision as to whether your equipment remains in a validation state and requires no further action other than a further review in X years; the equipment remains fit for intended use however additional requalification is required; equipment is not fit for intended use and will be removed from use until requalification is completed.

    It can be a lot of work for complex systems but it is a great document to present to auditors as it demonstrates control, provides an opportunity to plug any gaps and provides an overview of the equipment which is generally sufficient to keep focus away from your original documentation which could be years old.
    Last edited by erez; 03-23-2012 at 09:56 AM.

  4. #4
    Forum Creator gokeeffe's Avatar
    Join Date
    Oct 2006
    Location
    Ireland
    Posts
    1,215

    Default

    Nice response erez

    Quote Originally Posted by erez View Post
    We have an in-house periodic review procedure which has a number of forms capturing information in relation to equipment/facilities/utilites and ccomputerised systems.

    Starting point should to define what equipment you are going to review first and what criteria you are using for this. A risk-based approach will help you define your periodic review schedule based on frequency/duration of operation, age of equipment (e.g. length of time since last qualification) criticality (business criticality and with respect to quality critical attributes of your manufacturing process), frequency of routine maintenance etc. etc. All this information should help you define a schedule indicating that your most critical and/or oldest systems will be reviewed first.

    Review then will concentrate on performance history of the equipment as determined through historical review of planned preventative maintenance, breakdowns, service reports, calibration certificates (including drift analysis), deviations, audit observations, change control etc. Maintenance and calibration should be reviewed not only to demonstrate that the activities were performed on time and passed acceptance criteria but also that they are still fit for purpose - is instrument criticality properly defined, do critical instruments have correct range, accuracy etc.?

    Design criteria should be checked to ensure that the P&ID is still reflective of the equipment, the equipment meets current regulatory requirements, review original validation documents and perform gap analysis - are original materials of construction still acceptable to industry etc. Again, a lot of this is driven by a risk-assessment.

    The output of all of this should be a decision as to whether your equipment remains in a validation state and requires no further action other than a further review in X years; the equipment remains fit for intended use however additional requalification is required; equipment is not fit for intended use and will be removed from use until requalification is completed.
    Graham O'Keeffe
    Director of Operations
    Premier Validation Ltd
    Website: www.premiervalidation.com
    Forum: www.askaboutvalidation.com
    LinkedIn: LinkedIn Profile


  5. #5
    Validation Analyst
    Join Date
    Mar 2009
    Posts
    7

    Default

    Thanks guys for the helpful info...

    Kind regards
    SFlan

  6. #6
    Validation Analyst
    Join Date
    Oct 2010
    Location
    tuscany ITALY
    Posts
    1

    Default

    We have in place a computerized system periodic review to be executed every 3 years (at least). This re-evaluation consists in a report organized like the following:

    - Scope
    - Re-evaluation summary
    - System description
    - Re-evaluation analysis:
    GxP Deviation and Problem Management
    Change Control verification
    Security Management verification
    System Backup and Restore verification
    System Documentation review
    Infrastructure Maintenance verification
    Open Action Item review
    Computerized System Gap Assessment checklist.
    I hope this helps.
    Regards
    Alberto

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Get In Touch with AskaboutValidation

© 2006 - 2012 askaboutvalidation. All Rights Reserved
Single Sign On provided by vBSSO