Part dependant save as copy

[supercell]

Is there a way to save a copy of a part whilst being dependant on the original part? I would like the part to behave similar to a mirrored part but without creating a file that's mirrored. 

[KenFarley]

When I am faced with this dilemma I use family tables. One entry is the original part, the other is the part after adding two more features:

(1) A mirror through a plane.

(2) A cut that removes the geometry of the original part completely.

Someone else might have a more clever way to do this type of thing, but that's my technique. It requires me to do a bit more if I have features like engraving on the parts and such, but everything has its price.

[DavidBigelow]

Would a Copy Geom work?

[tbraxton]

Merge and inheritance shared geometry functionality will enable a dependent derivative part from a master. If you explain in detail exactly what you are trying to do you will get better suggestions.

[supercell]

I would like to create multiple copies of one original common part and to make different changes on top of each of those copies whilst being dependant on any changes made to the original.

So as an example, let's say you have a common mounting plate that is to be used as a universal attachment for different items. You would make changes on top of the common mounting plate for each of the different items. If there was any changes to the common mounting plate, it would update for all the different attachments that use that common mounting plate.

The best way I can think of for what I'm looking for is when you create a save as mirror which is dependent on the original part. I'm not too well experienced with Creo so I don't know a lot of its features.

[tbraxton · Accepted solution]

Based on what you want to do the two options that come to mind as useful are as follows.

I would probably use merge/inheritance functionality  for non trivial geometry (molded, cast, etc.)

If it is a plate (sheet metal or similar)  as you mention I would consider a family table to configure each unique version of the part. 

There are other ways to deal with it but without understanding the desired design intent it is difficult to offer specifics. You should read about the top down design tools and get an understanding of them at a high level to decide.

[barryschaeffer1]

I and my colleagues at my current and former work places have routinely done what you describe using merge/inheritance.  Much less prone to strange issues than family tables, and rock solid for long term viability.

Barry