1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice
You must be a registered member in order to post messages and view/download attached files in this forum.
Click here to register.

Calibration/Verification Records - IATF 16949 section 7.1.5.2.1 (i)

Discussion in 'IATF 16949:2016 - Automotive Quality Systems' started by Lakshit Seth, Feb 22, 2024.

  1. Lakshit Seth

    Lakshit Seth New Member

    Joined:
    Feb 22, 2024
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Reference clause 7.1.5.2.1 i of IATF which requires that the records of verification of production related software used for Product and process control needs to be maintained, can you please suggest how the same can be demonstrated for a Cold Rolling Mill and Annealing Furnaces. Since all the production processes are controlled by software, how can I demonstrate compliance.
     
  2. yodon

    yodon Well-Known Member

    Joined:
    Aug 3, 2015
    Messages:
    198
    Likes Received:
    115
    Trophy Points:
    42
    I work mostly in medical devices but we have similar requirements so I'll share my perspective.

    If the software just comes with the system then there's just not a whole lot you can do. If you do any kind of system validation, you can cite that to show the software is meeting its intended use.

    If you implement any specifics, say, security, that can be an area that should be addressed in validation. For example, if the system enables unique logins for all users and your company sets things up with a single, generic login, that's probably not the best practice. Maybe there are different privilege levels like operator, administrator, maintenance. Showing those are appropriately allocated is a good exercise.

    The equipment manufacturer may provide software updates so one thing to check is whether you're up to date or not.

    The equipment manufacturer may also maintain a list of known issues. Looking at that and considering if your implementation could be affected can be an eye-opener. You may find you should be doing things differently to avoid such issues.

    If you layer on specific workflows then you can assess whether those are constructed within the framework the equipment manufacturer intended. You also may need to walk through the workflows if the system qualification doesn't cover everything.

    Edge cases (error handling) and safety are always good to look at. Does the software handle error conditions and detect and respond appropriately to unsafe conditions?

    If there is a remote client; i.e., you can operate the system remotely from a stand-alone PC, you'll want to consider if the PC it runs on is appropriate (memory, OS, speed, etc.). And a number of the above considerations (esp. security) can also be appropriate.

    Hope that helps.
     
  3. Andy Nichols

    Andy Nichols Moderator Staff Member

    Joined:
    Jul 30, 2015
    Messages:
    5,110
    Likes Received:
    2,562
    Trophy Points:
    112
    Location:
    In the "Rust Belt"
    Ask your IT function how they actually control equipment software, including version control, bug fixes etc. Start there and let us know what you discover.