Limitations of usage of family tables in Windchill 10.1

[psimha]

Hi,

I am looking out for a list of limitations of using family tables in Creo 2.0 which is interfaced with Windchill 10.1. Request all of you to contribute as many points as possible. Thanks in advance.

Best regards,

Simha

[VladimirPalffy]

Hi - best practice >> minimize family table's models in common space.

You can store it and use it, but ... many times you need to download all instances and then your workspace is a huge - for example Flat Sheet Metal part you can create as simplified

[psimha]

Hi Vladimir Palffy,

Thank you.

[mdebower]

Here are some thoughts on family tables:

• Do not use the generic in assemblies.  The only job of the generic is to define the family table.
• Keep family table instances numbers small.  Think brothers and sisters, not aunts, uncles, cousins.
• Never use nested family tables. Too complicated.
• Windchill understands family tables pretty well, it is usually the unfamiliar user that causes problems.
• Number and name the generic and instances similar to each other, that will make gathering them for Windchill operations easier on the humans. (if possible)