How to Handle Model Files for Different Stock Lengths

[Beggar]

We make assemblies that use different lengths of copper tubing. I'm not sure how to handle the part model of the copper tubing. As I see it, my options are either:

[ul]
[li]Have a single model file for the tubing and create a new configuration for each new length[/li]
[li]Create a new model file for each new length.[/li]
[/ul]

The problem with the second option is that I'm not sure what to name the files. Typically, we name the assy/part model files using the part number but the lengths of tubing don't have part numbers (there is a number for the tubing stock).

Any suggestions?

 

[Creigbm]

I would have to go with the different configurations. A design table might also suit your needs if you have standard lengths (never used the design table much but I hear it's quite useful).

 

[Creigbm]

I take back what I said about different configs, go with the design table.

 

[EdDanzer]

Unless you want the people who assemble these tubes to be regularly confused, give each length its own identifier, or part number. This can be either as an individual part (my preference) or as a configuration. Just because it is easier for you, does not mean it will be easy for the production people. Part of your job is to eliminate mistakes constructing your designs. Everyone who deals with your product including material ordering, kit building, manufacturing, assembly, replacement parts stocking, salesmen, invoicing, and the customer ordering replacement parts will need your diligence in being successful in using your design. If during the manufacturing process, or repair there is a chance of screwing up it will happen. When this happens the product is in jeopardy of being labeled junk or the company will be considered a poor place to do business with.

 

[TheTick]

If you are using a PDM system, you may be forced to use individual part files. Many PDM systems don't handle multiple parts from a single file.

If this is the case, you might consider creating a seed file. Perhaps a macro that takes are of description, name, number, etc. would be in order.

Due to illness, the part of The Tick will be played by... The Tick.

http://www.EsoxRepublic.com

 

[Beggar]

TheTick, do you know if PDMWorks will allow multiple configurations from a single file? We have PDMWorks but I haven't had time to figure out how to implement it well.

 

[ctopher]

It will not allow different revisions for each config.

 

[Beggar]

ctopher: What does that mean? Unless I'm confused, there would be no revision for each configuration since each configuration differs from another simply by its length.

Changes at the assy level would simply be changing the length of the part (meaning select an existing config or create a new one).

I've managed to come up with a way that works for me (though the PDM issue might blow me out of the water):

Created a new Toolbox standard, renamed the Aluminum structural shapes to Copper, and then edited some of the existing shapes to yield what I need. In the model file I've added a reference dimension to the extrusion length and this is referenced on the assy BOM as the cut length.

Now, if I could find the Access table holding all those values so that I could delete the ones that are meaningless, I'd be one happy camper.

 

[ctopher]

Just a FYI. I talk to alot of users that try to check in a prt with configs and control revs on each config. Didn't know if you knew. Just FYI. Sorry if I wasn't clear.

 

[Beggar]

ctopher: Thanks for the heads up - I appreciate you not making assumptions regarding my knowledge. As it happens, my knowledge re SWX is very fragmented. The things I know, I know very well. Much of the program, though, remains unexplored territory for me - including PDMWorks

 

[Standing]

Beggar,
We had to do the same thing for our items that only changed in length. We did not want to create a separate model for each part, because if something changed in one model we would have to change them all.
What we ended up doing was to create configurations for each length and within that configuration we added a sketch with the length on it. That dimension would be placed in our Excel based BOM under the QTY with the unit of measure. It was complicated to setup, but once done it was easy for a drafter to put a different length wire in a BOM, because it is all automatically done.


Bradley