Richard,
Here is the link to the NASA trend analysis paper I was speaking of.
http://archive.org/details/nasa_techdoc_19890007063
I don't know of any standards that are about trend analysis. It is usually
all part of the quality management and assurance program that is created
from experience and utilizing statistics calculations.. I know of few
possible tools that may help, but not for sure if it is what you are
looking for.
Toby
On Wed, May 15, 2013 at 2:59 PM, Mike Bogden <[log in to unmask]> wrote:
> A repair is due to damange. Rework is due to assembly error.
>
> Just a thought.
>
> Mike Bogden
> Engineer
>
>
>
> ----- Original Message ----
> From: "Stadem, Richard D." <[log in to unmask]>
> To: [log in to unmask]
> Sent: Wed, May 15, 2013 1:43:46 PM
> Subject: Re: [TN] Trend Analysis of Repair Usage
>
> Yes, but not defects that require repair usage (lifted pads, damaged
> traces,
> etc.)
>
> -----Original Message-----
> From: TechNet [mailto:[log in to unmask]] On Behalf Of Ed Popielarski
> Sent: Wednesday, May 15, 2013 1:08 PM
> To: [log in to unmask]
> Subject: Re: [TN] Trend Analysis of Repair Usage
>
> Are not some "defects" considered "not rejectable", i.e., "process
> indicator"?
>
> Ed Popielarski
> Engineering Manager
>
>
> 970 NE 21st Ct.
> Oak Harbor, Wa. 98277
>
> Ph: 360-675-1322
> Fx: 206-624-0965
> Cl: 949-581-6601
>
>
> https://maps.google.com/maps/myplaces?hl=en&ll=48.315753,-122.643578&spn=0.011188,0.033023&ctz=420&t=m&z=16&iwloc=A
>
>
>
> -----Original Message-----
> From: TechNet [mailto:[log in to unmask]] On Behalf Of Gumpert, Ben
> Sent: Wednesday, May 15, 2013 10:55 AM
> To: [log in to unmask]
> Subject: Re: [TN] Trend Analysis of Repair Usage
>
> Dean,
>
> But isn't a defect a defect, regardless of the fix?
>
> You may not track / trend repairs separately from rework, but they should
> be
> included in the overall defect trends. In some cases, the defect itself is
> enough to identify the instance as a repair, such as lifted/missing pads
> on a
> PCB.
>
>
> Ben
>
> -----Original Message-----
> From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
> Sent: Wednesday, May 15, 2013 10:39 AM
> To: [log in to unmask]
> Subject: EXTERNAL: Re: [TN] Trend Analysis of Repair Usage
>
> Yes, for rework in 12.1, but for repair trending, nothing in 12.2.
> Still looking for trend analysis.
>
> -----Original Message-----
> From: TechNet [mailto:[log in to unmask]] On Behalf Of Guy Ramsey
> Sent: Wednesday, May 15, 2013 9:28 AM
> To: [log in to unmask]
> Subject: Re: [TN] Trend Analysis of Repair Usage
>
> 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]
> ______________________________________________________________________
>
> ______________________________________________________________________
> 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]
> ______________________________________________________________________
>
> ______________________________________________________________________
> 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]
> ______________________________________________________________________
>
> ______________________________________________________________________
> 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]
> ______________________________________________________________________
>
--
Toby
______________________________________________________________________
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]
______________________________________________________________________
|
