family table instances and their relation to the generic.

[dnordin]

I'm looking for an explaination on family table instances and their relation to the generic.

I have a ticket open with PTC asking this, but haven't received a response yet. I thought I'd ask the community as well.

Using Pro/Intralink 9.1 M060 & Creo Elements Pro 5 M120.

Using the following scenario:

Create a generic part XYZ.prt with one instance ABC.prt.
Check these into the CS. Version on both items will be 0.0 in our installation.
Checkout the -
www.baesystems.com

[BenLoosli]

While the instance ABC.0.0 is in generic XYZ.0.1, ABC.0.0 was not saved with it pointing to XYZ.0.1, so you are getting exactly what the systems knows. ABC.0.0 only knows about XYZ.0.0.
If you look at XYZ.0.1, it will show both ABC.0.0 and DEF.0.0 as instances.

My rule for family tables to keep them clean is to always edit the whole table and check in all instances with the generic. This keeps the relationships clean. As for releasing items, I would release the generic and all instances. If I add a new instance, they all get bumped up a version so the generic is XYZ.1.1 with instances ABC.1.1 and DEF.0.1.



Thank you,

Ben H. Loosli
USEC, INC.

[Dmi3U]

We had a long discussion in my company about bumping all the instances just to keep the family table happy, and decided against it from the CM stand point - you should not iterate object if it has not been changed. We also have usually a single drawing representing all instances with repeat regions. That drawing is almost always at different revision than the part.
So, the rule is to look for the latest wtpart.