What is considered the best practice for rework/repair testing and WATs?

Follow

Kreitzer, Kenny

• January 31, 2024 22:36

Typically, we have a tester and it performs the normal production test.  However, that same tester may at times be used to test parts that have been repaired.

However, we do not have a repair report that we can tie to it yet (what parts were fixed, etc).  We typically get that later.

During this testing, a part can be tested many times.  Currently, we are using the same process Code as production, which causes a lot of alerts (UUT tested X number of times, etc).

Since the tester is the same, it is still running say a PCBA functional test.

Is it better to have a process code for PCBA production (example 10), and a similar one that is still a PCBA process (example 110), but is excluded from alerts, etc?

Or is there a way to flag a test cycle as being in a repair mode that I am not thinking of?

0

• 

  Tom Andres Lomsdalen

  • February 01, 2024 11:52

  Hi Kenny,

  One thing that might help; in Periodic Yield, you can make filter based on Units linked to a UUR or not:

   

  

  Other than that, there is no way to "flag a test cycle as being in a repair mode" other than using a different process, so this would also be my suggestion.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.