Train Your Staff on Good Documentation Practices in 60 Minutes!

20% Discount With Coupon Code LAGMP-002

Results 1 to 2 of 2
  1. #1
    Validation Analyst
    Join Date
    Sep 2009

    Default PLC Change Control Management


    I am looking for a procedure to help better manage changes made to PLCs in a manufacturing facility. As you know, changes made to PLCs fall into several categories. Some changes impact validation, while others are normal production activities. The validations department at my company cannot handle review of every single change made to the PLC. What guidelines could we put in place to ensure that appropriate changes get reviewed by validation, without having to review normal production changes (e.g. configuration, addition of an employee, etc) I would imagine that company policies would break down changes into varoius categories and specify the requirements for each category type. But, I can't seem to find any examples of what these categories/requirements would be. Any suggestions?

  2. #Ads
    AskaboutValidation Loneaaz is offline


  3. #2
    Validation Expert
    Join Date
    Oct 2006


    Follow the risk based approach (GAMP 5). I am not sure why you would be making so many changes to PLC code. Typically once the PLC is commissioned and qualified it falls under site change control. Enhancements and optimization would drive changes from that point, and that would not be very many. I am not sure I agree that configuration changes are normal production changes. You could write a procedure for system access.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Privacy | Terms © 2006 - 2014 askaboutvalidation. All Rights Reserved