TECHNET Archives

May 2013

TechNet@IPC.ORG

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stadem, Richard D." <[log in to unmask]>
Reply To:
TechNet E-Mail Forum <[log in to unmask]>, Stadem, Richard D.
Date:
Fri, 17 May 2013 16:08:36 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (115 lines)
That depends: did he perform any welding not on the original specification or drawing? That is a repair.
Did he remove the cylinder head and replace it, with all gaps and torque settings compliant to the automotive specifications for that make and model? Then it is rework. And it may be better than new, the way they make cars nowadays.

-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Ahne Oosterhof
Sent: Friday, May 17, 2013 10:59 AM
To: [log in to unmask]
Subject: Re: [TN] Trend Analysis of Repair Usage

With that kind of definitions, your car mechanic will never say he "repaired " your car after a collision, he will say he "reworked" it. And add: It's as good as new!

Ahne.

-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Blakley, Peggi J CIV NSWC CRANE, GXSQ
Sent: 17 May, 2013 08:05
To: [log in to unmask]
Subject: Re: [TN] Trend Analysis of Repair Usage

Definitions as defined in the IPC7711/7721 document.

*Rework - the act of reprocessing noncomplying articles, through the use of original or equivalent processing, in a manner that assures full compliance of the article with applicable drawings or specifications.

*Modification - the revision of the functional capability of a product in order to satisfy new acceptance criteria. Modifications are usually required to incorporate design changes which can be controlled by drawings, change orders, etc.
Modifications should only be performed when specifically authorized and described in detail on controlled documentation.

*Repair - the act of restoring the functional capability of a defective article in a manner that does not assure compliance of the article with applicable drawings or specifications.

-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
Sent: Wednesday, May 15, 2013 14:41
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 email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] 
______________________________________________________________________

ATOM RSS1 RSS2