Hi Folks, I work for a thermoplastic sheet company that is going after AS9100D certification and I am getting hung up on clause 8.2.1 and 4.2, specific to review of customer requirements. Most Aviation Customer PO's reference Terms and Conditions (some quite lengthy) as well as other additional customer procedures.
I may be over-thinking this, but as I study 8.2.1 and 4.2, I am coming to the alarming conclusion that I need to scan every PO for any reference to requirements (other than the normal product description/specs) and if, for instance the PO should reference any customer procedures, I should obtain copies, review them, document the review along with results of the review including implementation actions. The reason this is so worrisome is that many of these referenced documents will reference other documents, which reference other documents, and so on and so forth.........not to mention the inevitably referenced Terms and Conditions that are written by lawyers and legal departments.
All of our PO's are formally reviewed for the product related specifications stated on the PO's and I do review a lot of the systems requirements, but I do not document the reviews or the actions that come out of those systems requirements reviews. What exactly is the intent of 8.2.1 and 4.2 regarding customers' quality systems requirements for their suppliers? I have considered developing a matrix but we have hundreds of customers (not all Aviation but all products / processes will be included in the scope of the AS9100D certification) and it seems like this would be very difficult to effectively manage. How are other organizations managing the 4.2 and 8.2.1 requirements?
Thanks
I may be over-thinking this, but as I study 8.2.1 and 4.2, I am coming to the alarming conclusion that I need to scan every PO for any reference to requirements (other than the normal product description/specs) and if, for instance the PO should reference any customer procedures, I should obtain copies, review them, document the review along with results of the review including implementation actions. The reason this is so worrisome is that many of these referenced documents will reference other documents, which reference other documents, and so on and so forth.........not to mention the inevitably referenced Terms and Conditions that are written by lawyers and legal departments.
All of our PO's are formally reviewed for the product related specifications stated on the PO's and I do review a lot of the systems requirements, but I do not document the reviews or the actions that come out of those systems requirements reviews. What exactly is the intent of 8.2.1 and 4.2 regarding customers' quality systems requirements for their suppliers? I have considered developing a matrix but we have hundreds of customers (not all Aviation but all products / processes will be included in the scope of the AS9100D certification) and it seems like this would be very difficult to effectively manage. How are other organizations managing the 4.2 and 8.2.1 requirements?
Thanks