ansi 9standards0 code issues - standard for parts callou

huangyhg

ansi standard for parts callou
at our company, we engineers have been tasked with reviewing and providing suggestions for updating various engineering drawing standards.  although we prefer to base our company standards on ansi  standards, we have not been able to locate an ansi  standard for callout of parts.
we prefer to callout the actual part number rather than an item/find number in a bubble, but we are concerned with how to illustrate quantity notations.
for example, assume we have a parts callout that is a leader arrow linking the part number text to a hole, and the hole is repeated on the part six times in a pattern.  we want to point to one hole and imply the pattern, not create a leader arrow with a parts callout to all six holes.  in each individual hole, we wish to install one bolt, one nut, and two identical washers.  (don't beat me up for the stackup, this is a hypothetical example.)
this example would callout a total of six bolts, six nuts and twelve washers on the one leader arrow pointing to the one hole.  currently our company drafting standards manual allows either of the following callout methods to be the text depicted at the leader arrow:
first callout method
6x nas1801-3-6
12x nas1149d0332j
6x ms21042l3
second callout method
nas1801-3-6
2x nas1149d0332j
ms21042l3
6x
we don't like the first method because it is not clear exactly how many instances of the holes you have without mental math, so the production person must search for like hole features and mentally divide the quantities to determine the correct quantity for each hole.
the second method more clearly defines six identical instances with the "6x" below the part numbers.  however, we don't like the fact that the "2x" is only delineated from the "nas1149d0332j" by a blank space.  it is possible that someone could accidentally believe the quantity to be part of the part number.  think a copy of a copy of a copy with production floor dirt and grease, and maybe what looks like a dash (created by dirt) appears between the "x" and the "n".  we have considered changing the standard to:
nas1149d0332j; 2x
so that there is a distinct break between the part number and other information with the comma plus the space, and also so that the leader points first and foremost to the part number itself.  of course this assumes no part number ever contains a comma.
however, if an ansi  standard exists that we have failed to locate, we want to review and make a case for following industry standard.
thanks for any pointers to an ansi  or other industry standard.
debodine
eng-tips forums is member supported.
asme y14.34-1996
associated lists
"wildfires are dangerous, hard to control, and economically catastrophic."
"fixed in the next release" should replace "product first" as the ptc slogan.
ben loosli
cad/cam system analyst
ingersoll-rand
thank you!
we will search for that ansi  standard and review it.  sadly, we do not have a complete library of ansi  or asme standards here so its no wonder we did not locate it internally.
best regards,
debodine
please note, there is ansi  & asme. looslib referenced asme not ansi .
chris
sr. mechanical designer, cad
solidworks 05 sp2.0 / pdmworks 05
yes, you are correct.  i noticed that fact after i sent the last post.  we are searching for the asme y14.34-1996 as looslib recommended, not an ansi  standard.
thanks for making sure we weren't spinning our wheels uselessly!
yes, but asme has taken over as the 'official' publisher of the standards. ansi -y14.5m-1982 was replaced with asme y14.5m-1994.
"wildfires are dangerous, hard to control, and economically catastrophic."
"fixed in the next release" should replace "product first" as the ptc slogan.
ben loosli
cad/cam system analyst
ingersoll-rand
okay, now i think i understand what you were trying to tell me.  can you see that we have not been very up to speed on ansi  standards at our company?  
so asme has been converting ansi  standards to asme standards, just as easa has been converting jar regulations to cs regulations (e.g., jar-25 to cs-25) and sae has been converting nas standards to as standards.
thanks again for the pointer and also the explanation of the migration of standards.