best practice

[EngineerPhil]

I am trying to determine what might be the best solidworks modelling practice.

I have a product which in essence can be modelled as a 4 part asembly. I have used the answers from my previous thread to create cutting tools of each part so that they fit neatly together. I need to create drawings of three parts and must have associativity between them for future changes. This route will create 4 part files and 3 drawings.

The other route is using configurations of one part file. I sketch the full product and revolve round each individual part as a feature. I then create configs of the default and switch off the revolve features that I don't need. This creates one file which has 4 configs. I can then draw up the 3 configs that I need.

So what are the pros and cons of both methods? I am unsure.

I really want to get the method right before I start to model. I would like to set it up so I can use what ever approach as a generic file/folder as there are many products belonging to the same family. If I can copy and save the whole folder or all the parts to another location and not have links to each folder, that would be great. My life would be made so much easier.

If anyone can shead some light that would be fantastic,

Cheers

Phil.

 

[TheTick]

In most cases, I would stay away from the multiple configurations in a single file scenario. The only real good case for this is if the parts are all similar, like boards cut to length. Also, if you need to maintain associativity, the configurations can become a real headache.

As far as maintaining the associativity between the parts, you need to maintain a master assembly to maintain the context of the associativity.

I'm not sure what you mean about how this applies to the drawings. If you create a drawing of a part, the dimensions on the drawing will update along with changes to the part. As far as tracking where a part is used, you may be due for a PDM system. If you are low-budget, look into SimplePDM (

http://www.cpuandsimplepdm.com

).

At the very least, get used to using SolidWorks Explorer to scan for where a file is used.

All this machinery making modern music can still be open-hearted.

 

[SBaugh]

http://www.solidworks.com/pages/services/subscription/guideslinks/practicesguide_link.html?pid=252

You have to login using your SW Subscription to view it.

Regards,

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376
When in doubt, always check the help

 

[macPT]

EngineerPhil

You shouldn't think only in terms of SW. You have SW to work in your company and not the opposit.

So it must be clear to you the company srategy in product design, manufacturing and management. This will drive you in your SW solution.

Examples:
- if your company manufactures several products having the goal to standardize components as possible, you must not associate parts and assemblies. But, if you are focussed in the optimization of each product, no mater the others, then incontext parts will be the best practice.
- if your company manages parts as variations of master parts (like a part that can be painted or hot dip galvanized, the master part being the one without surface treatment) then it is better to work with configurations (1 part, several drawings). If it's not the case then maybe it's better to avoid configurations (one part, one drawing)
- if your company as small production, it's better to stay in the to level assemblies and drawings so you don't have extra work. But if your company as mass production, then you will benefict of the maximum detail, so you can optimize each single part.

Best Regards