J-STD-001 touches on this, 12.1. It does not tell you what to document. In a
nutshell, it says you must document, and the user must agree with the repair
approach. 

Guy

-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
Sent: Wednesday, May 15, 2013 9:53 AM
To: [log in to unmask]
Subject: [TN] Trend Analysis of Repair Usage

I am trying to find out if there is an industry requirement or
recommendation that usage of Repair Procedures be tracked and monitored? I
could not find any information on this in IPC-7711/7721. In previous lives
the number of repair usages was tracked, and pareto was published quarterly
(number of repairs used versus number of total CCAs built, number of repairs
used by a given CCA part number, number of repairs associated with a given
component part number, etc.) .
Because repairs are infrequent, it is not easy to detect any trend in their
usage, but over time the trend analysis can provide good data to detect root
causes.
I just want to know if there is any industry standard that covers this.
I am talking about repairs, not rework. If you don't know the difference
please do not respond.
Thanks
dean

This message and/or attachments may include information subject to GDC4S
S.P. 1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed
only by authorized recipients. Use, storage and transmission are governed by
General Dynamics and its policies. Contractual restrictions apply to third
parties. Recipients should refer to the policies or contract to determine
proper handling. Unauthorized review, use, disclosure or distribution is
prohibited. If you are not an intended recipient, please contact the sender
and destroy all copies of the original message.




______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] 
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] 
______________________________________________________________________