No - but sense doesn't always seem to come into when working to ISO9000. The question is, does the standard explicitly state that we must uniquely number drawings, or can we use a generic numbering system for generic drawings? I can see that we need to identify which project a drawing refers to, but must that be part of the drawing number or can it be a separate box in the drawing template?
>>I have a general question about devising a numbering system for CAD
>>drawings. My engineer insists that every project we work on must have a >>set
>>of unique drawing numbers, even if the drawing is one from a pool of
>>standard components. To me this seems counter-intuitive; if a drawing is >>of
>>a standard part (albeit one that we get manufactured) then it would make
>>sense to me to leave the number unchanged. Otherwise we have 2 drawings of
>>the same part that have different drawing numbers.
>>Does ISO9000 state absolutely that drawing numbers must be unique, or is >>my
>>engineer over-interpreting things?
> If you had a standard bolt used many places on many projects
> would you get them from diferent suppliers & from different
As far as standard parts (Hardware, screws, washers, purchased products like o-rings, snap rings, etc, etc.) we set up a numbering system. As we create a new assembly, if the hardware is in our system, we'll simply use it. If it's not, we'll assign the new hardware a the next number in the system. It does not have to be unique to a specific job/project (ie, as you said and have multiple p/n's for the same part)
For example, this is the system we use. We assigned a series of numbers that are only for purchased parts (95000 series)
We created a standard print (in excel actually) for each. When we need an o-ring that's not there, we assign the next dash number to what we need. If it's a new category, we assign it the next 95000 series number and it becomes the first dash number. We have our own SWx library of standards parts that correspond to the 95000 series dash numbers.
If you break down ISO 9000 to it's basic form, it's simply traceability. Have procedures documented and make sure you follow them, and conduct frequent audits to make sure they are being followed.
I don't know what ISO 9000 says but here is my theory:
We have a low volume product that sometimes uses parts that are the same as in another product but we refrain from re-using the same part number across projects. The reasoning for this is what if the part has to be revised at design or in the future, this now changes the part for all jobs it was used in. There is a specification for defining when a part gets a new number but I feel it is just to dangerous and prone to errors, ie: someone not realising where else the part is used and changing it. So we just do a save as and give the part a new number for the new job.
For comman parts ie; nuts screws etc we have a system similer to the previous poster.
Again we produce low volumes so this makes sense for us it may not for a different situation.
Thanks for the replies. In the scenario below, depending on the scale of the change, we would either save the part as a new revision (ge; 100-01-B) or as a new part (eg; 100-02). Drawings that had used the rev 100-01-A part would remain unchanged and new projects could use either part as required as they would be uniquely identified.
What I'm trying to get my engineer away from is calling a part "ProjectA-100-01-A" and then on the next project calling the same part "ProjectB-100-01-A" because I feel that this means we can't tell from the part name whether the 2 are really identical. What I want him to do is simply call the part "100-01-A" and on the drawing refer to it as such. Identification of the project should be a separate unrelated entity on the drawing template.
He however insists that ISO9000 explicitly states the the name of the part should contain the project reference. We're not actually ISO9000 registered but do want and try to follow the guidelines where we can.