Or 0.5% Mahendra Gandhi M&P Engineer Northrop Grumman Aerospace Systems One Space Park, M5/1085A Redondo Beach, Ca. 90278 Ph.: 310-813-6857 Fax: 310-812-8630 [log in to unmask] -----Original Message----- From: IPC-600-6012 [mailto:[log in to unmask]] On Behalf Of Jose A Rios Sent: Thursday, February 24, 2011 10:39 AM To: [log in to unmask] Subject: EXT :Re: [IPC-600-6012] Document Sets in the case of bow & twist, there is dual criteria; for surface mount and for pin in hole. fabricators may be able to guess what is what, but not for all designs. i find it valuable in the case of b&t to call out specifically if 0.75% or 1.5% applies. Joey Rios PWB & Process Quality Eng'r Endicott Interconnect Technologies 1093 Clark St. Endicott, NY 13760 Office: 607-755-5896 Jack Olson <[log in to unmask]> Sent by: IPC-600-6012 <[log in to unmask]> 02/24/2011 12:50 PM Please respond to "(Combined Forum of D-33a and 7-31a Subcommittees)" <[log in to unmask]> To [log in to unmask] cc Subject Re: [IPC-600-6012] Document Sets I have a follow-up question. What led me to writing that last post was that I have collected many samples of fab drawing notes as part of my working with the IPC-2610 series committee, and I noticed that the MAJORITY of them call out both IPC-6011 and IPC-6012, so I thought I was onto something. I' m trying to figure out why people are specifying things that are already part of IPC-6012. For example, many people have a Bow and Twist note on their fab drawings, but the maximum allowance they are calling out exactly matches the one in 6012 (which in my mind, if its already in there, you don't need to call it out separately, right?) So my follow-up question is: "Why do people do that?" Jack . On Thu, Feb 24, 2011 at 11:17 AM, John Perry <[log in to unmask]> wrote: > Hi Jack, > > I believe the words you are looking for in IPC-6012C are in section 3.1, > General. Here is the reference to meeting the generic requirements of > IPC-6011. So in the case of this document, the wording is a little farther > in than the other documents, which has such language in section 1. > > John Perry > Technical Project Manager > IPC - Association Connecting Electronics Industries(r) > 3000 Lakeside Drive # 309S > Bannockburn, IL 60015-1249 USA > +1 847-597-2818 (tel) > +1 847-615-7105 (fax) > +1 847-615-7100 (Main) > [log in to unmask] > www.ipc.org > > -----Original Message----- > From: IPC-600-6012 [mailto:[log in to unmask]] On Behalf Of Jack Olson > Sent: Thursday, February 24, 2011 11:13 AM > To: Listserv IPC-600-6012 > Subject: [IPC-600-6012] Document Sets > > I have a question about how document sets are structured, in particular > comparing the 6010 series with others like 2220 or 2610 series. > > IPC-2222 specifically incorporates all of the generic IPC-2221 with this > statement: > > 1.1 Purpose The requirements contained herein are intended to establish > specific design details that shall be used in conjunction with IPC-2221 > > IPC-2614 (for example) incorporates everything in the generic IPC-2611 > > 3 REQUIREMENTS The requirements of IPC-2611 are a mandatory part of this > standard. > > What this says to me is that the documentation only needs to call out the > specific standard to get the requirements of BOTH the specific and the > genericl standards. > > Logically I assume that the same holds true for IPC-6011 and IPC-6012, but > in my latest copy of 6012C (PROPOSED STANDARD FOR BALLOT - JANUARY 2010) I > don't see any wording like this. Am I losing my mind? Do I have to call out > BOTH of them on my fabrication drawing? > > onward thru the fog, > Jack > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please contact helpdesk at x2960 or [log in to unmask] > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________