Traceability Requirements

[ingabramrobles]

For our company this one is not a customer requirement, but we consider only week and year , do we need to maintain a record for each par number?

[Coury Ferguson]

Originally Posted by ingabramrobles

For our company this one is not a customer requirement, but we consider only week and year , do we need to maintain a record for each par number?

If you have no requirement, than why do it? If you are choosing to do it on your own, then the company would define the requirements, in my opinion.

[ingabramrobles]

Week and year is customer requirement. but i don't know if this one is enough

[Coury Ferguson]

Originally Posted by ingabramrobles

Week and year is customer requirement. but i don't know if this one is enough

As long as you meet your customer's requirements there isn't any issues. If your organization wants to do more that is your choice.

[Marc]

Originally Posted by ingabramrobles

For our company this one is not a customer requirement, but we consider only week and year , do we need to maintain a record for each par number?

What do you manufacture?

[ron_f]

There are multiple issues within TL9000 related to traceability

7.5.3.h.1 states that FRU's must be traceable to identify products for recall. If you identify products to the week/year of production then this would be the minimum traceable lot for recall and should be sufficient as long as your organization is willing to accept the risk of recall of an entire week of production.

7.5.3.h.2 is for traceability of design changes and states: changes can be traceable to date, lot or serial number. If the week/year is considered a lot you should be fine on this clause.

The final issue related to traceability is that you need to be able to identify when product was shipped, not built, in order to calculate the hardware measurements (return rates)