Table for multiple models on a drawing

[B_Baker]

I have a user asking if it is possible to add multiple models (not a family table) to a drawing and then create a drawing table to list all of the models associated with the drawing.

Their idea is to add a drawing table that lists all of the models associated with the drawing and the model's lengths.  Example: Hex bolts with different lengths but bolts are individual components and not in a family table.  When a bolt is added, the table automatically updates.

Let me say that I do not agree with doing things this way, but agreed to check into it for them.  In my opinion, the drawing should revise each time another model is added.

We are also using Windchill.

[dnordin · Accepted solution]

Without having actually tested this, you can try:

create an assembly with all the individual bolt files in it.
in each bolt file, create a parameter via a relation called "BOLT_LENGTH" and set it equal to the dimension for the bolt length. i.e. BOLT_LENGTH=$d4
add the bolt assembly file to the drawing.
add a table and create a repeat region that displays the individual component model name (or whatever descriptive parameter you use) along with the BOLT_LENGTH parameter.
the table should update if you add a new bolt to the bolt assembly.

Regards,

Dan N.

[B_Baker]

That will work.  Trying my best not to do it.  Thank you.

[BenLoosli]

If the drawing file is released in Windchill after the initial creation, any additions to the table will require a revision to the assembly and drawing.

Why not convert the parts to a family table?

[B_Baker]

You are correct about the revision.  Trying our best to eliminate family tables.  

I have used this in the past and did not care for it.  We had the Windchill admin make the change without revising it.

One more reason that I do not like to do it this way.

[BenLoosli]

What don't you like about family tables?

I have over 12000 models in family tables in Windchill.

They provide consistency in naming and interface/mating conditions.

[B_Baker]

We have many tables also.  Problem is usually Windchill, users and revisions. No matter how much you try to lock things down, somebody will figure a way to break it.

[BenLoosli]

I have my family tables in the Part Library, so only a librarian can modify them. Most of my family tables are hardware items and we built them with a full range of diameters and lengths to avoid one-off additions. This also brings part family instances into the user's workspaces as read-only objects.

[B_Baker]

Thanks.  I will talk it over with the Windchill Admin.