Data Sharing Techniques

[mloew]

I would like some input on what the best strategy might be for sharing information across models. I have what I call interface models that detail the important interfaces, package spaces, etc. across interfacing systems. For example, I have three parts, (Part A, Part B, Part C) and there are required interfaces from Part A to Part B and Part B to Part C. I want to have the proper dimensions, tolerances, GD&T, etc. controlled centrally.

In the past, I used external copy geom. features of pub geom. features to copy geometry across models, but the geometry is static, i.e. I have no access to the dimensions, tolerances, etc. It is not really much better than a dependent import. The inheritance feature is neat, because it allows for real access to the actual feature geometry. Unfortunately, I must inherit the entire part including the geometry that is not relevant to the interfaces of interest.

I am looking to emulate inheriting certain features like the pub_geom/external copy geom. with the functionality of the inheritance feature. Any clues?



Best regards,

Matthew Ian Loew
"I don't grow up. In me is the small child of my early days" -- M.C. Escher

Please see FAQ731-376 for tips on how to make the best use of Eng-Tips Fora.

 

[Guest0527211403]

Matthew,

Maybe User Defined Features would work in this case.

If you apply them to recieving parts as UDF Driven, you can standardize these interfaces. The best practice I have seen is to create simple reference parts that contain the basic geometry required for the interface.

A good thing about this method is that you have access to dimensions for drawings, as well as which dimensions are variable between parts.

Also, you can select entire groupings of features. Just make sure that the group itself relies on as few references as possible.

I read somewhere that Wildfire 2.0 lets you see UDFs in the Browser Preview.

Hope it works

Mark

 

[looslib]

Try using MAP parts for the locating dimensions and datums.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[mloew]

Mark/Ben,

Thanks to both of you for the tips. I am not sure I have the right techniques identified yet. Regarding the UDF, this method requires more objects to be maintained in a database, I am looking to consolidate the number of objects to a minimum. I am also concerned about having the information maintained, when a vendor converts the information to a different MCAD system.

I have used map parts before, using the pub_geom/ext_copy_geom method to collect and flow information across models, but this will not allow for the tolerances, GD&T information, etc. to be maintained across models.

Any other thoughts?



Best regards,

Matthew Ian Loew
"I don't grow up. In me is the small child of my early days" -- M.C. Escher

Please see FAQ731-376 for tips on how to make the best use of Eng-Tips Fora.