Skip to main content
P
ptc-1131131-Visitor
1-Visitor
January 7, 2010
Question

Force wt.parts, once and forever, to synchronize with their associated cad docs

  • January 7, 2010
  • 5 replies
  • 5882 views
Hi,
Suppose you create a new cad document in winchill and check it in. With auto associate turned on, a wt.part is created automatically. Fantastic.

But the lifecycle of the wt.part and the cad document easily diverge, even at the very next iteration. It is quite easy, especially if you are coming from a 3.4 paradigm, to focus only on changing the cad doc. You can revise the cad doc independent of the wt part. After you very next check in the iterations no longer match. So much for the idea of using A.1, A.2 , A.3 to describe the Revision of the product, at least at the wt.part level.

Are there settings in Windchill, to once and forever, force the wt.part and the cad.doc to be 100% synchronized in Revision and Version. In this case, you would not be able to check in a modified cad doc without the wt.part iterating simultaneously at check in.


Please comment from your experience.
Thank you very much in advance,


Andrew Amsden
CAD\PDM Administrator
Midmark Corporation
937-526-8770







5 replies

S
sdrzewiczewski10-Marble
10-Marble
January 7, 2010
I don't think you can force them to march in iteration and I don't 
think it is important.

For Revision make sure your collectors are setup correctly to grab the 
correct objects. This way if you start from a part or from cad both 
will be collected and revised at the same time



C
cc-21-Visitor
1-Visitor
January 12, 2010

Hi

I agree with Stephen. WTpart is the object defining your product. The definition is made of CAD data and also Documents. Therefore it is very rare to have the version of the WTpart the same than the CAD model.

If you do not use any other type of object in your WTpart than the CAD data, why do you need WTpart ?

The other issue you relate is from my point of view more important. You should not be able to revise a model if you do not revise the WTpart. Since the model is part of your product definition, if you change it, you change your product definition and therefore your WTpart. We have not find a way to force the user revising (and changing the state of the WTpart at the same time than its content and accordingly). My admin set up the setting for the dependent object to always be automatically collected.

Hope this helps

Best regards

P
patrick.chin11-Visitor
1-Visitor
January 12, 2010

Have you ever thought that your WTPart Process and your CAD document process is different. WTPart follows fit, form and function. While CAD documents can change with any modification to the CAD file that has no changes to fit, form and function. Constantly changing WTPart to sync to your CAD may not be the best practice of solutions. Small changes in the file management may have dramatic changes in the entire enterprise. It is best now to package your changes in ECNs of PLM.

You have to break away from file management methodology when dealing with WTParts because it affects the entire organization. Pro/E file or any CAD file/tool management methodology should not break basic engineering principles of form, fit and function. Sometimes, you should just not revise any more after it has been released for detail inseparable components. Just create a new WTPart and save as for CAD.

Good luck,

Patrick

M
mdebower18-Opal
18-Opal
January 12, 2010

A related question I have is, what CAD documents get a WTPart?

With using auto-associate you get WTParts for every CAD document. But does every CAD document need a WTPart?

Obvious example, a sheetmetal part with a flat pattern as an instance, the flat pattern instance doesn't need a WTPart, but with auto-associate, it gets one.

-marc

CAD / PLM Manager

OliverDroop
OliverDroop15-Moonstone
15-Moonstone
October 28, 2015

Since Version 10 there are preferences available to control this behaviour together with some CAD Parameters

Look for Part Structure Override Attribute Name and Phantom Assembly Override Attribute Name

Terms & ConditionsAccessibility statement