TECHNET Archives

October 2001

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:
Guy Ramsey <[log in to unmask]>
Reply To:
TechNet E-Mail Forum.
Date:
Wed, 24 Oct 2001 18:53:31 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (70 lines)
I believe I miss used the word "Qualify".

I think we agree.

"In order for the user to apply and use the content of this document
(IPC-A-610), the assembly/product should comply with other existing IPC
requirement, such as IPC-SM-782, IPC-2221, IPC-6011 and IPC-A-600. If the
assembly does not comply with these or equivalent requirement, then the
acceptance criteria needs to be defined between the customer and supplier."
(The 610 acceptance criteria may not apply).

"For a more complete understanding of this document's recommendations and
requirements, one may use this document in conjunction with IPC-HDBK-001 and
J-STD-001."

The MIL-Q-2000 paradigm is dead. Process, Process, Process. The J-STD-001
makes allowance for risk associated  with Class 1 and Class 2 products.

If I was a salesman I would proclaim IPC-A-610 acceptability
If I was a buyer I would demand J-STD-001 compliance.
If I was an investor I would seek companies with knowledge of the
difference.




> -----Original Message-----
> From: TechNet [mailto:[log in to unmask]]On Behalf Of Sauer, Steven T.
> Sent: Tuesday, October 23, 2001 8:51 AM
> To: [log in to unmask]
> Subject: Re: [TN] Trimming Leads...
>
>
> I can't resist Guy, with the all due respect, you struck a nerve
> and I could
> provide a long dissertation but I will only hit the highlights.
> For a true
> understanding of 610, read the scope and purpose, which are
> pretty much self
> explanatory.
> We all know what happens when you "asssume".
> Therefore, one should require conformance to the full gambit of specs/stds
> covering design, fabrication, documentation, assembly, acceptability and
> rework/repair dependent on product class.  Conformance to these documents
> does not guarantee an acceptable product nor does it "qualify" a product.
> These documents minimize the risk of attaining an acceptable, reliable,
> fieldable product.  ("...it sure looked good, I got the C of C and all the
> other paperwork, but I don't understand how it smoked after I turned it
> on...")
> To "qualify" the product is another subject unrelated to this topic.  But,
> it all depends on how much the user is willing to pay and how
> well the user
> defines the product requirements.
> I believe you would be hard pressed in the real world to have class 1
> product and some class 2 product manufacturers buy into your logic.  These
> mfr's rely on the end product acceptability (does it look good enough)
> requirements of 610 and use best manufacturing practices to achieve that
> end.
>

---------------------------------------------------------------------------------
Technet Mail List provided as a free service by IPC using LISTSERV 1.8d
To unsubscribe, send a message to [log in to unmask] with following text in
the BODY (NOT the subject field): SIGNOFF Technet
To temporarily halt delivery of Technet send the following message: SET Technet NOMAIL
Search previous postings at: www.ipc.org > On-Line Resources & Databases > E-mail Archives
Please visit IPC web site (http://www.ipc.org/html/forum.htm) for additional
information, or contact Keach Sasamori at [log in to unmask] or 847-509-9700 ext.5315
---------------------------------------------------------------------------------

ATOM RSS1 RSS2