Inside an MBD world a full annotated model is the basic for a digital production. How do we handle REUSE feature from other models or out of a library? OK, Merge is a nice solution, and is supporting the digital MBD approach 100%, if there is no dimension or features which need to get changed or modified or suppressed. As soon as a merged library part get modified, it's not a standards library file anymore (inside Windchill) and need to get copied and renamed. A variable reuse of feature is missing inside CREO. More and more library parts are similar and can be used in different sizes, that’s a kind of flexible library reuse part. Inheritance Feature is the answer for it. But there are some limitations inside an inheritance feature, because it’s working complete different as a merge feature. The idea of an inheritance feature is to make a reuse feature flexible and possible to modify.
First, some advantages of an inheritance feature:
Dimension modification during placement
An Inheritance feature is like a flexible reuse of single or multiple features which are fully annotated and can be stored inside a write protected library
Without loosing the reference to its base model
But there are also a lot of disadvantages, which will block every company to use inheritance feature for a flexible reuse approach.
What needs to get changed to support an inheritance feature to fulfil MBD inside a digital thread.
Datum System can cause issues and conflicts, here it should use the same solution as MERGE feature
Datum symbol cannot get moved to another position
GD&T annotations are uncomfortable to move
Colors out of the library model (base) should get transferred
In case of pattern, datum system is wrong. Here each pattern instance needs his unique datum system. Creo should rename for each pattern instance the datum symbols and relations to corresponding GD&T tolerances. Like Merge is doing. A Datum sysmbol is unique
Inheritance should support a pattern ISO GPS conform by using correct Datums
PTC need to modify inheritance feature to work the same way as a merge feature. Without those requested changes, a reuse of feature in a flexible way is not possible. Merge is no solution here to support flexible inheritance features for an automated and controled reuse process.