Family Tables

[MDrake]

Hi everyone,

I am wanting to create a family table that allows the user to pick from a list some options for features. Like, do you want 3 grooves on the face or only 2 grooves.  Our parts are just optional features that sometimes vary in size. I was looking at nested family tables but it doesn't seem like I can select an instance from the subfamily table in the main family table. Our parts are very simple and of the 10 features there are only 2-5 different variations which is why I am not worried about using a family table. Ideally I would like this to easily translate into a drawing so I am not having to put a lot of dimensions for each new drawing. I need one drawing per instance.

Thank you in advance for the help!

[tbraxton · Accepted solution]

For what you are describing, I would consider using Pro/Program as the interface to control configurations rather than nested family tables.

[MDrake]

What is Pro/Program?

Thank you

[tbraxton]

Start here:

Pro programming user guide - PTC Community

[MDrake]

Thank you I will look into this. However this seems pretty complicated and difficult for new users.

I’m sure I can handle it but I want to make sure anyone else that isn’t as experienced can handle it.

[tbraxton]

If the user can open a model and then read and comprehend prompts from Pro/Program they should be able to deal with it.

[tbraxton]

This company offers a third party option to manage models as well vis Excel.

Nitro-CELL (simplifiedlogic.com)

[MartinHanak]

Hi,

the only thing you need is to:

• add column into family table for every varying item
• create family table instance for every variation and assign it suitable name

[Chris3]

You could look at using an Excel analysis feature to drive the model by Excel as well:

http://support.ptc.com/help/creo/creo_pma/usascii/index.html#page/model_analysis/bemod/To_Create_an_Excel_Analysis.html 

https://www.youtube.com/watch?v=2kwNkNkn7Vk 

https://community.ptc.com/t5/3D-Part-Assembly-Design/Modifying-Parameters-with-Excel-Spreadsheet/td-p/244554 

[Patriot_1776]

I agree with Tom, do NOT use nested family tables in Creo, it causes problems when using Windchill.