SW REVISIONS

[jloeff]

I was wondering if anyone has had trouble with controling revisions made to a part. My experience is that when I change my model and update the parts referencing it, I have know record of the previous state of any part in reference. Therefore, I can not tell exactly what changed for the revision level.
Example:
I have a part A with a Ø.250 hole that has another part B referencing that same hole. Part A gets modifed to have a Ø.375 hole as revA. When I bring up drawing of Part B 2 months later it also has a hole of Ø.375, but no reference of change.
Is there some way to control this?

 

[DetroitPickles]

If you want part B to tell you it changed, then you got a problem. I don't know of a way to do it other than a fancy, complicated VB routine to interrogate every part that references the changed one and add a Custom property (?) to it.

Unless PDM does this somehow, but I don't do PDM, so maybe someone else knows...


Mr. Pickles

 

[josephv]

Hello,

The only way to effectively control Revisions is to use a PDM (Product Data Management) Software.

I strongly recommend that you look into PDM/Works.

Frankly, I don't know how someone can work with out it.

There are other work arounds like using SolidWorks Explorer and Folders, but they are lame work arounds at best.

cheers,

Joseph

 

[macPT]

That's why I never create parts incontext or add relations between parts. This can be a big problem if you share parts between different assemblies because it can result in unknowing changes in parts.

I think DetroitPickles is right: you need a macro or mabe PDM.

Regards

 

[TheTick]

Use "Where used" in the SW Explorer to see where a file is reference. This will at least tell you the assemblies where a part is linked to other files.

On justice and on friendship, there is no price, but there are established credit limits.

 

[jloeff]

It sounds like the best solution is a PDM, but for now I will just have do without and try SW Explorer.
Also,I have been trying to find a good revision block editor using VB. Has anyone used such a thing?

 

[meintsi]

We operate quite well without a PDM system in place. Within our file system for our parts, each folder has it's own "obsolete" folder.

We copy the existing drawing to this folder, open up the copy in RapidDraft format and re-save. This temporarily will break the link to the part/assembly and requires you to manually synchonize the drawing to the model. We then make sure the RapidDraft file in checked for read-only.

Design changes can then be made to part/assembly with the newest revision update appearing only on the original drawing.

Check your help for further explanations. It may 'help' you out.



Remember...
"If you don't use your head,
your going to have to use your feet."

 

[Patreich]

Our company fought this for a long time, we use to make a dxf of the drawing when a change notice was to be made. Now we have changed that to making a dxf (a dwg would work just as well) as soon as a drawing is released - (even on a prototype level). That makes sure we have a record of what was released is case someone makes a change to the model and forgets and saves. The released drawing and model remains the same number, the Dxf drawing gets a revision number. Has worked fine for several years. We are, though looking at a PDM solution to see if it would help.
Pat R

 

[deek05]

jleoff,

I just finished our titleblock editor. What's your email address and I'll send it to you.

DT

 

[TheTick]

deek05:

I would love to see your TB editor. If you care to, please send it to the email address posted in my profile.

Thanks,
TheTick

On justice and on friendship, there is no price, but there are established credit limits.

 

[dogarila]

I would like to see your editor, deek05.

I can send you in return mine.

My address is andrew@netshop21.com.

Thank you

 

[JNR]

Hmm... lots of intersting comments again.

OK, the basic problem is that this is a parent/child type of relationship. Typically it is easy for the parents to know who their children are but not the other way around. It is a logical paradox. It is a bit like using standard parts in assemblies (I'm talking real world, not CAD). If the standard part changes, the assemblies made with it will automatically change. However the standard part vendor has no idea what assemblies use his parts or what they look like before or after the change. The only way to track this is on a where-used basis which requires some database recording or real-time searching. So both the PDM type approach and SW Explorer where-used approach should be fine.

BTW: Josephv, do you get a commission on PDM/Works? I notice you recommend it a lot. Or are you just a user with a lot of experience with it? In which case I might want to pick your brains about a few things.

 

[DHALE1]

deek05,and netshop21

I have been working on creating a titleblock editor. I have finished the titleblock part in VB. Now I am working on the revblock part. I would be interested in seeing what you guys have created, or any ideas you could share.


thanks

 

[Morglisn]

I'd also like a copy of that title block editor, deek05.

blittle@litnc.com


Thanks!!

 

[DHALE1]

deek05,and netshop21

Sorry, my email didn't show up.
dhale@greenlee.textron.com

 

[josephv]

Hello JNR,

No, I don't get commission on PDM/Works.

I always recommend any CAD user a PDM software.

Quite frankly, I still don't know how someone can run a business without a PDM package.

I am not a PDM/Works expert, but I really enjoy it and find that it saves me time and money.

Feel free to ask me any questions.

Cheers,

Joseph