Skip to main content
R
RC_102727986-Contributor
6-Contributor
September 12, 2023
Question

WTPart and CAD files .asm /.prt, association.

  • September 12, 2023
  • 2 replies
  • 1100 views

Hi all,

 

for our projects, we usually create pipe solution as .asm file, where a .prt file represents the duct and others .prt files (With different file names/numbers) for standards components like washer, fitting etc.

To allow check-in, and so association, between WTPart, .asm and .prt files. we add to the .prt name/number underscore plus numbers as follow:

 

- WTPart DUCT , DUCT.asm , DUCT_01.prt.  

 

I have found out that, before check-in CAD files, modifing the association type for the .prt file from "Image" to "Content", we can check-in .asm and .prt even if thay have the same name/number:

 

- DUCT.asm , DUCT.prt.

 

Whci one is the best solution and why?

2 replies

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
September 12, 2023

We do not allow a part file and an assembly to have the same name. The 'exception' is a drawing may have the same name as its part or assembly and MUST have the .drw file extension. This does not affect WTparts as drawings do not have them,

There is an option in Windchill to turn off file extensions when checking in an object. If you have this enabled, you will run into issues with WTpart associativity as the WTpart (DUCT1) can only be associated to either the part (DUCT1) OR the assembly (DUCT1), but not both and check in will fail.

If we have an inseparable assembly (DUCT101.asm) then the components will be named with dash numbers (DUCT101-01.prt, etc.) for all related components. Since it is an inseparable assembly, no dash numbers of the DUCT101 assembly may be used in any other assembly. If we have a part that is used in multiple assemblies, it gets a unique number. All parts and assemblies have a corresponding WTpart in Windchill.

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    September 12, 2023

    @BenLoosli does something similar to what we do. Users will blindly hit check in and changing association types is a tough concept to manage. Take for example an assembly with a plate and some pins/inserts. Its very easy to call them the same, plate.asm and plate.prt. This will cause a conflict when its creates the WTPart. From a BOM perspective, you might want to identify the plate without the pins/inserts different from the completed assembly, even if you received from the supplier complete. The indented BOM will therefore be complete showing the pins/inserts. 

     

    If the assembly was R44-12345-001.asm, the part without the pins/inserts would be R44-12345-101.prt. Easy for folks to follow and avoids conflicts.

      Terms & ConditionsCookie settingsAccessibility statement