Here is a summary of the information I received on skeleton model creation
in Pro-E. Following the bullet points, I pasted the longer email
descriptions at the end.
. When working with a data manager (Intralink/Windchill), isolating
your design intent into skeletons enables you to keep track of changes in a
group of designers. A skeleton getting 'out of date' is giving another
message than an assembly getting 'out-of-date'.
o We tend to reuse skeletons 'read-only' in assemblies, other than the
original one. This way, we interchange the interfaces between assemblies.
. The reason for needing AAX is not to gain skeleton functionality,
but instead to be able to easily control the passing of product design
intent info from one model to another
. My opinion is that the only benefit is that in drawing they're
automatically not show in the BOM. Personally I think you have more
flexibility from a modeling view point to just use a regular part. Until a
few releases ago there were major limitations with pro/e's dedicated
skeleton parts. These have mostly been corrected now.