TECHNET Archives

February 2000

TechNet@IPC.ORG

Options: Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Subject:
From:
Wanner Bernhard <[log in to unmask]>
Date:
Tue, 22 Feb 2000 20:09:13 +0100
Content-Type:
multipart/alternative; boundary="----_=_NextPart_001_01BF7D68.52AD6F70"
MIME-Version:
1.0
Reply-To:
"TechNet E-Mail Forum." <[log in to unmask]>, Wanner Bernhard <[log in to unmask]>
Parts/Attachments:
text/plain (2844 bytes) , text/html (5 kB)
Probably its not a real problem, because...
*       if you are cleaning your pwa's anyway, you will clean also the
components,
*       if you use clean-free, you will take accept also all your "normal"
internal contaminants (flux, fingerprints ..) and most
component-contaminants will be at a similar level/kind.
I like it, Dougs :"...YOU determine ..". hehe, that's exactely what you have
to do, but instead of to write own standards I would refer to the golden
IPC-octuple (you don't know it? so what!: IPC-2221, -2222, -6011, -6012,
-4101, -A-600, -A-610, J-STD-001, all class 2, and IPC-D-279 + IPC-HBK-001
as guidelines). 
Bernhard

> -----Ursprüngliche Nachricht-----
> Von:  Douglas Pauls [SMTP:[log in to unmask]]
> Gesendet am:  Dienstag, 22. Februar 2000 19:42
> An:   [log in to unmask]
> Betreff:      Re: [TN] components cleanliness
> 
> In a message dated 02/22/2000 11:50:09 AM US Eastern Standard Time,
> [log in to unmask] writes:
> 
> > Is IPC has requirement for component cleanliness?  I have checked
> archives
> >  of TechNet.  No IPC requirement in Sept. 1998.  Anything changed?  As
> Bev
> >  Christian stated 2 years ago:
> >   "No company can really afford to carry a complete set of its own
> standards
> >  any more and with the contract manufacturing industry out there, it
> doesn't
> >  even make sense to try and do it."
> >   Help!  (with components comming from anywhere and everywhere,
> standards
> are
> >  needed)
> 
> Joyce,
> Don't hold your breath.  With the move towards performance based
> specifications, most IPC assembly level specifications are going the route
> of
> having the assembler or OEM define for their hardware what cleanliness
> measures are to be used and what cleanliness requirements are for their
> products.  From a cleanliness standpoint, I don't foresee any more "one
> size
> fits all" cleanliness specs.  Them days is gone.  I think about the best
> you
> will see will be recommended protocols from the IPC on how YOU determine
> cleanliness of components and how YOU determine how clean your components
> need to be for your hardware.
> 
> Doug Pauls
> Technical Director
> Contamination Studies Labs
> 
> ##############################################################
> TechNet Mail List provided as a free service by IPC using LISTSERV 1.8c
> ##############################################################
> To subscribe/unsubscribe, send a message to [log in to unmask] with
> following text in
> the body:
> To subscribe:   SUBSCRIBE TECHNET <your full name>
> To unsubscribe:   SIGNOFF TECHNET
> ##############################################################
> Please visit IPC web site (http://www.ipc.org/html/forum.htm) for
> additional
> information.
> If you need assistance - contact Gayatri Sardeshpande at [log in to unmask] or
> 847-509-9700 ext.5365
> ##############################################################


ATOM RSS1 RSS2