For various reasons, I've always 'checked in' my Toolboxparts into PDMWorks. This has worked great over the years, not justfor me but for other companies I've done business with.
Basically I use ToolBox to create the initial parts, and a fewbasic configs. Once I have all of the properties set up, it goesinto PDMWorks as 'working copy default'.
Anyone with basic SolidWorks 101 skills can add new sizes,configurations, properties, design tables etc. the old fashionedway... manually. After all, it's not rocket science.
So anyhow...
My latest customer just started using PDMWorks and decided to setup ToolBox on a network using the 'Not Revision Managed' setting.
I have compiled a list of what I feel are the disadvantages. SinceI've never done it this way, maybe I have a few things wrong. Ifanyone has a comment, I would appreciate them before I send my listoff to others I work with.
This is on SolidWoks 2007 (no particular order):
*) Can't rename a toolbox part file name, and have it automaticallyupdate
in every assembly and drawing (This alone is enough not to do it)
*) Many extra settings need to be created/enable/maintained etc.
ahead of time, and no guarantee it's done correctly
- Need to spend huge amounts of time editing the internal ToolBoxdatabase
before anyone can use it, to conform to company standards
- Who will have the knowledge to edit the internal database?
- Need to hire a dedicated ToolBox guru?
*) Can't drag & drop or open from PDM
*) Forced to use ToolBox interface instead of PDMWorks
- Just an 'eye candy' marketing gimmick?
- Default naming conventions make no sense
- Prone to bugs
*) Doesn't copy to your local folder
- Can't zip everything up, forced to do 'find references' thencopy to a new folder
- If network is down, your out of luck
- Checking out to take work home, you accidentally forget to getthe HDWR
- Working off a network is always a bad idea (common knowledge)
*) Don't know who has ownership
- May be overwritten at any time (the whole point of using PDM)
- Can't make a change if someone has it opened as 'non read-only'
- No protection from editing mistakes
*) Always opens 'read only' making changes difficult
- Have to switch from read-only to write, make a change, thenchange it back
*) Missing configs cause HUGE problems!!
- New users may have ToolBox local and overwrite criticalinformation
- Assemblies 'blow up' constantly
- ToolBox tries to automatically create new configs, adding to theconfusion
*) How do you know the difference between differing hdwr shapes andmaterials?
- SAE vs USS vs Mil-Spec vs ...
- Nylon vs Steel vs fiberglass vs ...
- Color/appearance settings for rendering
- All of this has to be programmed ahead of time?!
*) While inserting part-into-part, you have to search for thetoolbox part path
*) May cause problems for others in the company (that don't haveSolidWorks)
that want to tap into the vault info and view/work with the data.
*) May cause problems for PDM Enterprise?
FINAL NOTES:
*) Basically it's not flexible to future changes
- Company may go to MRP system requiring need for simple yetuniversal changes
*) Little value-added for much loss in productivity
*) Adds unnecessary complications and dependencies
*) Not user friendly or intuitive for editing
*) Maybe some companies *want* to revision manage their hdwr (orhave that option)
- Or just keep it defaulted to 'working copy'
BOTTOM LINE:
I would recommend checking inall parts into PDMWorks, including library (or COTS,purchased parts).
SolidworksWorkgroup Pdm
Basically I use ToolBox to create the initial parts, and a fewbasic configs. Once I have all of the properties set up, it goesinto PDMWorks as 'working copy default'.
Anyone with basic SolidWorks 101 skills can add new sizes,configurations, properties, design tables etc. the old fashionedway... manually. After all, it's not rocket science.
So anyhow...
My latest customer just started using PDMWorks and decided to setup ToolBox on a network using the 'Not Revision Managed' setting.
I have compiled a list of what I feel are the disadvantages. SinceI've never done it this way, maybe I have a few things wrong. Ifanyone has a comment, I would appreciate them before I send my listoff to others I work with.
This is on SolidWoks 2007 (no particular order):
*) Can't rename a toolbox part file name, and have it automaticallyupdate
in every assembly and drawing (This alone is enough not to do it)
*) Many extra settings need to be created/enable/maintained etc.
ahead of time, and no guarantee it's done correctly
- Need to spend huge amounts of time editing the internal ToolBoxdatabase
before anyone can use it, to conform to company standards
- Who will have the knowledge to edit the internal database?
- Need to hire a dedicated ToolBox guru?
*) Can't drag & drop or open from PDM
*) Forced to use ToolBox interface instead of PDMWorks
- Just an 'eye candy' marketing gimmick?
- Default naming conventions make no sense
- Prone to bugs
*) Doesn't copy to your local folder
- Can't zip everything up, forced to do 'find references' thencopy to a new folder
- If network is down, your out of luck
- Checking out to take work home, you accidentally forget to getthe HDWR
- Working off a network is always a bad idea (common knowledge)
*) Don't know who has ownership
- May be overwritten at any time (the whole point of using PDM)
- Can't make a change if someone has it opened as 'non read-only'
- No protection from editing mistakes
*) Always opens 'read only' making changes difficult
- Have to switch from read-only to write, make a change, thenchange it back
*) Missing configs cause HUGE problems!!
- New users may have ToolBox local and overwrite criticalinformation
- Assemblies 'blow up' constantly
- ToolBox tries to automatically create new configs, adding to theconfusion
*) How do you know the difference between differing hdwr shapes andmaterials?
- SAE vs USS vs Mil-Spec vs ...
- Nylon vs Steel vs fiberglass vs ...
- Color/appearance settings for rendering
- All of this has to be programmed ahead of time?!
*) While inserting part-into-part, you have to search for thetoolbox part path
*) May cause problems for others in the company (that don't haveSolidWorks)
that want to tap into the vault info and view/work with the data.
*) May cause problems for PDM Enterprise?
FINAL NOTES:
*) Basically it's not flexible to future changes
- Company may go to MRP system requiring need for simple yetuniversal changes
*) Little value-added for much loss in productivity
*) Adds unnecessary complications and dependencies
*) Not user friendly or intuitive for editing
*) Maybe some companies *want* to revision manage their hdwr (orhave that option)
- Or just keep it defaulted to 'working copy'
BOTTOM LINE:
I would recommend checking inall parts into PDMWorks, including library (or COTS,purchased parts).
SolidworksWorkgroup Pdm
