How would it be possible to create a series of models for process drawings within CREO 8.0, Merge?

[TC_10043994]

For instance, I've tried the merge function and that seems pretty close to the functionality I'm looking for in regard to sharing geometry between parts (Some limitations of course). In practice I'm looking to create a forging model/drawing, which needs to be referenced by a rough-out/inlay level drawing, which will be referenced by a final machining drawing. In Inventor for example you can very easily derive a component into a brand new file and the first feature you see in the browser of the new file is that referenced part. You can control whether to break the link (as if you wanted to use that geometry as just a template) or maintain the relationship as the design intent would be to have any changes propagate up the chain to all parts making the reference. At any rate, the merge is the first way I see possible to conduct this design intent and wanted to ask the forum in case there is a much better way in CREO. My mind next goes to family tables in regard to feature suppression. which could work, but to keep each phase separate I need to have separate files due to the need of separate released Part numbers for each step.  I taught myself CREO about a year ago and figure something new about it seemingly on a weekly basis. Thanks for any suggestions!

Tim Comer

[StephenW · Accepted solution]

We typically use merge for this exact process.

Create a forge part

use the forge part as the first feature in the new rough machine part using the get data - merge/inheritance feature - then do other operations

we usually have a weld or inlay process where we use the rough machine as the first feature of that part. using merge/inheritance

then finish machine using the weld/inlay part as the first feature.

[tbraxton]

@StephenW has made a good recommendation for how to handle this scenario. Inheritance features were developed to handle this in Creo.

See the link to the zip file in this thread that I posted. It details an example of an as cast/as machined model.

Solved: Inherited models with vardim dimensions - PTC Community

[Patriot_1776]

You can use the Merge (Master Model) technique as Stephen mentioned, or, I used family tables for that, with each instance being a different "op" (drilled holes, turning op, milling op, etc.).  I like Family tables for this kind of stuff a LOT better because ALL the data is in only one file with no chance of having the wrong version master model.  Also, dunno if they fixed this, but there were severe issues with layers.