WT parts first or CAD parts first?

We create our WT Part & CAD thru Windchill. New Part -> New CAD Document. We have 60 designers so it is much easier to have them create the WT Parts for our upcoming ERP Connector.

Our WT Parts have a XXX-XXXXX number while our CAD has the 10-digit autonumber.

We are actually using Inventor & Workgroup Manager. For our Creo users, they create their CAD that gets the 10-digit autonumber and another user further down does the auto-associate to get a WT Part with the XXX-XXXXX number.

Hi

interesting topic.

I can't speak for Inventor but with Creo files which are uploaded into a EPMDocument, we configured Windchill to create and auto associate WTpart and it takes the same number than the CAD Number.

Indeed we are configured to have

EPMDoc Number = WTpart = Filename + extension

I would have assumed that when you use a Workgroup CAD Manager, Windchill can be configured the same regardless of the CAD application you use.

This is something you should clarify with your consultant/reseller.

I may end up with Windchill and Inventor so I am quite touchy at the moment about Inventor integration. Our Reseller keeps saying it works the same than with Creo.....

Please keep me posted.

Thank you

In Reply to NacNac MOTT:

Hi

interesting topic.

I can't speak for Inventor but with Creo files which are uploaded into a EPMDocument, we configured Windchill to create and auto associate WTpart and it takes the same number than the CAD Number.

Indeed we are configured to have

EPMDoc Number = WTpart = Filename + extension

I would have assumed that when you use a Workgroup CAD Manager, Windchill can be configured the same regardless of the CAD application you use.

This is something you should clarify with your consultant/reseller.

I may end up with Windchill and Inventor so I am quite touchy at the moment about Inventor integration. Our Reseller keeps saying it works the same than with Creo.....

Please keep me posted.

Thank you

Our configuration for the 2 auto-numbers is intentionally set up as our WT Part numbers match our ERP. Our CAD Document number is unimportant to us. We have the filename customization because we do not utilize a naming convention for a components. A search of our system would easily return 2500+ files called "PLATE, A". Our business is mostly one-off designs that are "never" the same.

It is a single WC configuration. From the Software dowloads section, I can download any of the WWGMs depending on my CAD Platform. I work in Inventor but when I was asked to do a test data import of NX data, I simply needed NX installed and the NX Workgroup manager. After that, my test NX Data import process was IDENTICAL to my Inventor Data Import.

Stephen Oerton

Windchill Process Specialist

Hi

Our WTpart numer use the same numbering schema as our ERP

Our CAD document have got a different numbering schema. their numbers respects a normalized convention so the CAD designer can easily find parts in Creo assembly tree

In my previous company, the CAD Doc have the same number as the WTpart. We have been working in both directions:

top down design by firstly creating Wtpart then CAD

Bottom up design by firstly creating CAD then WTpart

A supported hook can be customized in Windchill for the auto associate action. In order to create (or retrieve an existing ) the Wtpart with the correct number

have a look to the preferenrece: Site/Operation/Auto Associate/ Custom class for auto associate Part

-In Catia V5 WGM and Windchill 9.1 , there's other client hook that permit lot of things on CAD side. It seems does not exist anymore in 10

-Since 10, can create directly CAD documents from templates in the WTpart create wizard. So easy to align the numbers ....

regards

We create the WTPart and the CAD part independently, sometimes one first, then the other.

However all PRT parts are re-named with the WTPart number, and we use the Edit Association under the Actions menu to Associate the two, all while still in the workplace. Drawings are autonumbered by WC with a D beginning, and that becomes our document number.

I wish it was a bit more automatic, but this works well for us. One more thing, we stopped using Auto-Associate because it would occasionally create unwanted WTParts, when the system couldn't find the WTPart we intended to Associate with the PRT file.

Our idea is that the WTPart drives all the information. One of the reasons we do this, is a large amount of legacy data that was never associated with WTParts in the past.