Skip to main content
P
psimha1-Visitor
1-Visitor
August 17, 2015
Question

Limitations of usage of family tables in Windchill 10.1

  • August 17, 2015
  • 2 replies
  • 1217 views

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

    2 replies

    V
    VladimirPalffy14-Alexandrite
    14-Alexandrite
    August 17, 2015

    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

      P
      psimha1-VisitorAuthor
      1-Visitor
      August 17, 2015

      Hi Vladimir Palffy,

      Thank you.

        M
        mdebower18-Opal
        18-Opal
        August 17, 2015

        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)
          Terms & ConditionsCookie settingsAccessibility statement