mixing numbering convention

[Andy330hp]

As most of you know from other threads, I am going through a file restructuring.

We have solid models of some of our supplier's parts which are assembled with ours.

The suppliers have their own part numbers. It is a hyphenated number. We may or may not use hyphenated numbers, but that's not the point. The question is: Do we create our own part number, or use theirs?

And, on a more general note: are their problems with having some parts with hyphenated numbers, and some parts that do not? For instance, some of our parts are really just different configurations which share 99% of the machined dimensions. It would be best, I would think, to make a design table for them, name the part file 12345-xxx
and each configuration as 12345-1, -2, etc
However, many of our parts are one config only. Should they also have hyphenated numbers? should there be 56789-1 even if there is not, and never will be, a 56789-2? The

I gues what I am getting at, is HOW consistent the numbering should be. I daydream about PDM, but I have no idea what it is going to expect in terms of this. If the answer is that the system must be completely repeatable, then it looks like we do have to assign a new p/n to our suppliers parts, correct?

 

[automationbabe]

Andy330hp -

Do we create our own part number, or use theirs?
This depends on a number of factors. If you deal with a number of manufacturer's and vendors, and are a large company with many files, it may be worthwhile to generate your own internal part number for their numbers. An electronic data sheet will let other's know what your internal part number represents. When the supplier information changes, all you have to do is update the source data sheet file and leave your number the same, assuming the form-fit-function requirements are still there. This way, none of the upper level information has to change, just the data related to the supplier number. This practice has other benefits down the road as well.

I have also used supplier numbers, and both seem to work. There can be a number of snafus that come out of this, but that is another story.

However, many of our parts are one config only. Should they also have hyphenated numbers?
Better safe than sorry. Adding a -1 to your part number isn't a big deal. If you never add additional dash numbers, then the -1 is still valid. If you left it as a base part number and then added a -2, you need to then add a -1. If this part is used in a number of places and you are using a vaulting system, this can become cumbersome. Of course I'm far from being a vault guru, but I do have a number of years in document control...lessons learned <sigh>

Hope this helps and good luck. This is rarely an easy task.

D~

 

[automationbabe]

One more thing: with the internal supplier numbers, we added dash numbers as well, and added a letter prefix to the number. This was our visual cue that it was a puchased part. And the reason for the dash, well, suppliers have configurations as well. Example internal number: P-10000-1
Parts we made did not have the prefix.

 

[Arlin]

As far as using vendor part number I say DEFINATELY DO NOT USE VENDOR PART NUMBERS AS YOUR OWN. I have been down that road before and believe me, you don't want to go there too. This is just another version of an intelligent part number, which I absolutely despise (if you could not tell).

What happens when the vendor &quot;revises&quot; their part numbers? What if you switch vendors? Maybe you decide to make the part in house.

USE YOUR OWN PART NUMBER and keep track of vendor part numbers some other way.

As for the dash thing, I say all or none. If you use dashes, ALL parts should get a dash. This helps cover future contingencies. Say you create a new part with only 1 config and name it 12345. LATER, a new design could easily be accomplished by using a new config of 12345...BUT WAIT!!! Now what do we do with the original 12345?? It would be better if you just called it 12345-1 to begin with.

Just for the record, I am still against using dash numbers for configs in a production environment. I still say plain old sequential numbering is best. Of course, you will need some sort of tool/method to find some models. That could be a PDM system, a custom API program, or even a well-maintained Acces database to help you do your searching.

Of course these are just my opinions...

 

[MadMango]

I concur so far with what everyone is saying.

1. Use/create your own part numbers instead of vendor numbers.

2. Dashes or no dashes, be consistant.

I feel dashes only add room for human error. I would create numbers without dashes.
[blue]Case in point:[/blue] Recently during an ISO audit an employee pulled a model from the network, F92008. What came up was an old Rev B. That was a minor discrepency since the current rev was D. The problem? The employee entered the number wrong, he should have entered F9-2008.

MadMango
&quot;Probable impossibilities are to be preferred to improbable possibilities.&quot;
Have you read faq731-376 to make the best use of Eng-Tips Forums?