Richard,
I believe it is all industry dependent: NASA, automobile, aircraft or any of large assembly that service for long time and intended for upgrade or R&O will track in details. Plug and play type, may be not so much. (PC box assembly with choice of mother board, selection of optional video cards, etc. may not be tracked in details = design is not fully in control for the box level, for example, the heat dissipation and fan air flow may not be optimized to ensure the "trend" mean anything = Box A vs Box B may not be same repair trend).
Joyce Koo
Researcher
Materials Interconnect Lab
Office: (519) 888-7465 79945
BlackBerry: (226) 220-4760
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Guy Ramsey
Sent: Wednesday, May 15, 2013 4:19 PM
To: [log in to unmask]
Subject: Re: [TN] Trend Analysis of Repair Usage
We follow this line of logic. J-STD-001 says defects shall be documented. We
do. We have authorized inspectors, who are J-STD-001 certified specialists,
to disposition defects for rework, or review. If a defect is dispositioned
scrap, repair, use as is, or regrade a review must be conducted. As a
result, a record of all defects does exists. In addition, if a repair was
conducted we have a record and a way to evaluate efficacy of the repair.
We define rework as reprocessing with the same or an equivalent method.
Since, we don't bond pads to boards, or plate vias in barrels defect that
requiring a process to correct lifted lands for example require review.
There are gray areas even so. We don't have a process for leveling pads, or
removing parts. So, when a defect requires removal and reinstallation one
could argue that it is repair and not rework. A review might be a wise
course. Consider a $5K BGA gate array, on a $40K board that is rotated on
the board and worst case the corner balls are just over 25% off the pad.
Might a review be wise, before we attempt rework .. . excuse me repair?
Guy
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
Sent: Wednesday, May 15, 2013 2:41 PM
To: [log in to unmask]
Subject: Re: [TN] Trend Analysis of Repair Usage
You are absolutely correct. You are backing me up now. That is exactly my
argument. I'm just trying to find anything documented along those lines.
-----Original Message-----
From: Gumpert, Ben [mailto:[log in to unmask]]
Sent: Wednesday, May 15, 2013 12:55 PM
To: TechNet E-Mail Forum; Stadem, Richard D.
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 transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
______________________________________________________________________
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]
______________________________________________________________________
|
