reusing parts: rename or not to rename

[grunt58]

This is probably not the right area for this question but wasn't sure where else to post it.

My question is:
When I create a custom part it gets a part # relative to that project. The part # includes the project #. Now if I reuse that part on another project for a different customer I like to rename it, so that new part is unique to that new project. Is that the right way to handle naming "reused" parts or should it stay the original part #? Im affraid if it stays the original part # if there is a revision it will obvisously effect where else its used.

We are divided on this issue I strongly feel renaming is the best for the dept. to keep things organized even though it adds more work for our cnc programer and supply chain person who have to so there job twice. Others think it should stay the same name. Just looking for other opinions and advice.

Hopefully this makes sense. Also if I should post in another section let me know where.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[grunt58]

Forgot to add. The reused parts are usually simple mounting brackets and plates, nothing complex.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[KirbyWan]

The answer depends on how you expect a part change to effect future design.

By using the same name for the part if you decide that an update is needed that update will propigate to every part. That may be good if you want everything to get updated to the newest design, but that could cause problems with nearby parts in one project and not in another.

If you rename the parts then if you update the part you are only updating one part. You may then decide that that fix should be updated for every instance of that type of part and have to go through each file idividually make the update.

I've faced both problems and the decision is really yours based on which of these two problems is more likely, either a change affecting more parts then you want or having to make the same change repeatedly.

You could try and split the difference by having a generic part, and then when you create a project specific part you create a part with that projects name and import the part and then add any tweeks you feel are needed for that project. For example you could have a standard bracket, but without any fastener holes. You import the part and then add fastener hole locations. If you update the design of the bracket that change will be propigated to every bracket, or you could update the project specific file and only affect that individual part. It's not a perfect solution. I've had the problem of anytime I make a change to an imported part all the assembly mates can go haywire. But give it a whirl and see if this would provide the utility you are looking for.

-Kirby

Kirby Wilkerson

Remember, first define the problem, then solve it.

 

[CorBlimeyLimey]

I usually find that taking a scenario to an extreme helps form a decision. Imagine if the part was used in hundreds of other projects, and that you had to stock hundreds of each piece for each project. Given that scenario how would you name/number the part?

We also use a project-specific name/number for our parts ... but if a part is needed for another project, it is moved to a "common parts" folder and renamed accordingly. This makes it obvious that when revising the part, multiple projects are involved.

If a revision to a part is suitable only for a specific project, a new part is created and named accordingly.

 

[MadMango]

I would be in the camp that votes to keep the same part number for reused parts. If a change affects a common part tot he extent that it does not fit all uses, it should get a new part number. You should be working within a system that allows you to check "where used" to help in deciding when a change needs to be a new number instead of just a bump in revision.

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read faq731-376 to make the best use of these Forums?

 

[SnowCrash]

The tricky part ;-) is that if you reuse the name but have saved the parts in different assemblies and different directories they are not the same part, they just have the same name. (that "Fred" is not this "Fred" ) So if you make a change in one that does not propagate to the other parts and assemblies.
In a previous job they used text names for parts before I joined. We had several "LED Holders" that were very different. Our vendors hated that, too.
So if you are going to have differences in the parts at some point give them unique names.
OTOH, if this becomes a company standard part give it a common name but save it out and back in as a parasolids part so everyone knows to not change it - it will have no features to modify, just an imported body. Then save that in a common access library. I call mine "SWShare" and it is on the network.
BTW, we also use the convention that the part and assembly names include the project ID; I do not like it and would rather just have sequential non-significant PNs. Due to company policy we are supposed to include a date code as well, I have managed to get that moved to the end of the name and only applied to drawing documents.
This gets another layer of complexity if the part number does not resemble/equal the file name, of course.

--
Hardie "Crashj" Johnson
SW 2010 SP 2.1
HP Pavillion Elite HPE

 

[ShaggyPE]

I agree with CBL and MM

-Dustin
Professional Engineer
Pretty good with SolidWorks

 

[steinmini]

Personally, prefer to use a "prefix" for part names. Regardless if they are or are not identical parts used in some design. For example, a "Downhill Scooter" has all the parts named "DHS_part_name.SLDPRT"; if, for any reason, I have to use a part that's identical by all means (dimension, material, appearance) in a different project, say, "Turntable", it will have a different name, "TT_part_name.SLDPRT"
Some specific parts, like a custom designed bike wheel hub always has the same name, and the (custom designed) tightening Titanium bolt keeps the unique name through all the designs where that component is used, without an added "prefix" or "sufix".

This would be an alternative option. Personally, in the beginning, even before using SW, I had the same dilemma and found a solution that suits me best this way.
Furthermore, when I conclude the designing process, I always create a new package with "Pack & Go" where all the part files are included with the assembly file, label it with a date and revision number. If anything gets to be changed, the modified assembly gets it's own folder with date and revision number. Looks like an extra work, but this way I can always go back and check for changes, make a comparison between several versions of the final product design. shouldn't be a big problem with assembles with a relatively small number of parts, say, u to 100 or so...

Maybe isn't so important, but want to remind that naming everything as soon as it's created is also not a bad idea, instead of keeping the default feature names.

 

[drawoh]

grunt58,

This is not really a CAD issue. This is a procurement and warehousing issue. In this case, CAD should be organized around the optimal procurement and warehousing process.

If you do not change the part number, you must load the part read-only. You must not modify the part. You may manufacture a whole bunch of the parts and take them from your parts bin as required.

If you copy the parts out, you may modify them whenever you want. You may not substitute stuff from your warehouse.

JHG

 

[SteveMartin]

I'm firmly in the camp of keeping one part number. If at some point a part is changed such that it is no longer common, then that part gets a new number for the changed geometry.

Like was already suggested a 'common parts' project number might be best for these parts.

Renumbering parts just because they are used in a new place doesn't just waste programmer & supply chain time. It also wastes machining time, stocking time, inspection time, and makes it harder to leverage quantity discounts. Most importantly, it wastes MY time.

Would you renumber a screw just because it's used in multiple projects?

 

[KENAT]

forum781 might have some info.

By the way, the revision thing is a bit of red herring. To be a true revision, rather than a PN change, it should really be fully forward & backward compatible.

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[fcsuper]

My thoughts:

If the part in question is truly generic and will not change, then keep the number the same (almost as though you are buying an off-the-shelf part). Just be sure to still pull new numbers if you need modifications to the standard form.

If the part can change from project to project (even slightly), then assign new numbers everytime.

Matt Lorono
Lorono's SolidWorks Resources & SolidWorks Legion

http://groups.yahoo.com/group/solidworks & http://twitter.com/fcsuper

 

[grunt58]

No I wouldn't rename a screw because it is a stock part. We have catalog/stock parts that have part numbers. Im refering to custom non stock parts machined in house. Sorry I did not mention that aspect. They only get made after we do our free design and recieve a PO.

Our project #'s are 1234 so a custom part would be 1234-1, 1234-2 etc.. IMO the dash means its a custom part relative to that project. We try not to make custom parts but often we do need them.

I have no problem with a common parts folder we already have our 1000 page catalog modeled and use as common CAD parts. The problem is we don't want to enter parts into our part tracking system until it is ordered. We have to give it a part # during the quoting process though.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[ctopher]

I agree with Matt.
If the part does not change, use its p/n in all assy's.
Any changes, new p/n.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion