Filenames, part numbers, configurations and BOMs
Filenames, part numbers, configurations and BOMs
(OP)
Hi,
I'm setting up a new group on a shoe string so no PDM, and policies yet. Here's what I'm thinking but can't figure out how to do the filenaming and part numbers. For part numbering I will be doing none specific sequence 0001234 with a dash -01, -02, ... for configurations of the same part. For the file name since we don't have PDM I want to do "PartNo, Description" such as:
0001234, Bearing Mount.sldprt
with possible configurations like:
0001234-01
0001234-02
....
To do the BOM I would have a separate property "PartNo" that has the part number. This most PDM like and gives me easier path to future PDM.
The problem comes with toolbox parts which do not assign a PartNo property. Note I'm willing to live with the default part names for the part numbers for standard parts, breaks my non-specific requirement but when in Roman... But, this value is in the filename and the title. I did try to use "title" property as my BOM field, but it does not follow the configuration.
So only reasonable option I can think of is to drop my desire to have the description in the file name which will make finding files a royal pain. Any suggestions?
thanks,
I'm setting up a new group on a shoe string so no PDM, and policies yet. Here's what I'm thinking but can't figure out how to do the filenaming and part numbers. For part numbering I will be doing none specific sequence 0001234 with a dash -01, -02, ... for configurations of the same part. For the file name since we don't have PDM I want to do "PartNo, Description" such as:
0001234, Bearing Mount.sldprt
with possible configurations like:
0001234-01
0001234-02
....
To do the BOM I would have a separate property "PartNo" that has the part number. This most PDM like and gives me easier path to future PDM.
The problem comes with toolbox parts which do not assign a PartNo property. Note I'm willing to live with the default part names for the part numbers for standard parts, breaks my non-specific requirement but when in Roman... But, this value is in the filename and the title. I did try to use "title" property as my BOM field, but it does not follow the configuration.
So only reasonable option I can think of is to drop my desire to have the description in the file name which will make finding files a royal pain. Any suggestions?
thanks,






RE: Filenames, part numbers, configurations and BOMs
Second, you can configure ToolBox. Start->All Programs->SolidWorks->SolidWorks Tools. In there you can set up part numbers, etc.
As for your configurations, is this for manufacturing? If so, what do your configurations control?
Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog
RE: Filenames, part numbers, configurations and BOMs
Ok I see if I add PartNo and make it visible it allows me to type in part number value. Same for description, is there a way to tell it to pull the default value from the toolbox part for the description.
For configurations I'm not sure what you are referring to on the manufacturing side. I'm only using them for say a rod that has six different lengths, each one being a different dash part number.
thanks,
RE: Filenames, part numbers, configurations and BOMs
While I don't agree with using dash numbers for different lengths of rod, there isn't a right or wrong way to do it.
Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog
RE: Filenames, part numbers, configurations and BOMs
Even if you do not adopt anyone's method, offered here or anywhere else let me stress on thing - make a plan, test that it works, and if you are sure about it STICK WITH IT. That means every one in the group. There is no room for every person doing their own thing. I know - that's where we started and it gets ugly really fast.