INHERITANCE ASSEMBLIES

[FPerez]

INHERITANCE FEATURE FOR ASSEMBLY SAME AS INHERITANCE FEATURE FOR PARTS.

POSSIBILITY TO SUPPRESS PARTS & TO CHANGE ASSEMBLIES DIMENSIONS.

We need this functionnality to decline assemblies wich contains differents parts (because of different grooves) but should be dependent to a master.

Today we a doing family tables.

     CREO BOM should list the component of the Inheritance feature (components of the source assembly that have not been suppress by the user).

     WTPart of the Inheritance assembly should be created and managed.

     Careful with the WTPart of the source assembly: should not be affect by internal modifications of the inheritance feature.

     (we use multi-owner links)

[GregoryPERASSO]

-Think about resulting CAD structure in Windchill:

     - display or not Master_asm.asm level ?

     - Master_asm sub prt should be placed at same level of sub prt of the Assembly_one.asm ?

-Think about Creo View representation and Dynamic Viz impact in Windchill

- And think about associated WTparts and eBOMs.  Build process and multi owner case

     -if a WTpart is built with Master_asm. should it be added in Assembly_One WTpart eBOM ? as gathering ?

[PhilippePradour]

Hello, There are 2 needs in the background of this request 1) build a simulation model for mechanism / CE-Tol / spark assembly, in which we have to append components that are locked in Windchill (released state, managed by other departments or teams) with some additional information (curves, tolerance models, ...), while maintaining consistency with the source objects when they update - for this use case, it remains a pure simulation, and it is not expected to be associated with WTParts (at least not with owner or contributing links), which resolves many of the above questions 2) build variant families and product assemblies... and then, yes, the questions of the WTpart association, the data collector (for Add, Check/O, Check/i, revise / Promote / Add to Change / etc ...) shall be considered, as well as a mass update of all the inherited variants in the WS .... like a Family Table but that would have a Creo file for each variant object instead of a shared creo file, enabling to manage changes on one variant only without revising all the other variants (let's say add a feature to one variant only, not just a parametric change). Best regards, Philippe

[ArnaudVandeVeer]

We have an active working group on this topic.