Skip to main content
S
Sam-Ravikumar1-Visitor
1-Visitor
March 18, 2019
Question

Revising an instance without having to revise all the other instance in the family table

  • March 18, 2019
  • 3 replies
  • 4808 views

Most of our parts are in family tables. We are in the process of implementing Windchill and we use Creo 3.0.

 

Is there a way to revise an instance without having to revise all the instances in the family table?

After setting the action to "Revise", make changes and while checking in, all the other instances have to be in work to be able to check in this particular instance.

Currently we are asked the following process to work around it. Is there a better way to do this?

Initially the parts are in the released state.

 

1. Set the action to “Revise” by selecting the Instance and related Generic Part. Make sure to collect all the WT parts related to the instance and the generic part. Make sure you are not selecting all the other instances.

2. Check out the Instance and related Generic Part and drawings.

3. Make changes

4. Ask Admin to set other instances of that generic part to “In Work”. The revised instance and the generic part cannot be checked in until all the other instances are in work.

5. Engineer Checks In the revised parts and drawings.

6. Engineer submits changed parts for promotion request

7. Admin sets unchanged parts (other instances) to Released.

 

3 replies

R
Robert-Altman10-Marble
10-Marble
March 18, 2019

We are currently using a similar process so I will be looking for others to reply.

 

The only thing we do different is that during the Promotion request the users are including the ones that were not revised but set back to "In Work"

 

This way Admin does not have to manual set them back to "Released" and they are captured in the history of the change. 

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
March 28, 2019

We basically do the same thing.  It's getting to be a little too much at times especially when some users don't understand what they actually need to do.

Our process is:

1. The user will ask the admin to demote the files first that won't change.

2. The user revises the objects that are changing and makes the changes.

3. The user checks all related files in.

4. The user adds all the instances to the change notice which will promote all objects to the correct state.  The user also adds a note to the Comments box of the change notice for the objects that did not change.  Something to the effect of "No change" and some other comment.

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    March 28, 2019

    You are asking for troubles if you revise only a few of your instances in a family table.

    A family table may consist of hundreds of instances driven from a single generic, but if you export it, you get 1 file. There is no instance file created, only the generic. 

     

    I limit family tables to hardware items or pipe tubes cut to a length. The hardware items rarely get changed because we built a wide range originally. Tubing and such, we will add a new length and always regen the entire table.

     

    What sort of changes are you making that can be made to only selected instances of a family table? To me, that destroys the concept of family tables. You may be better off using a UDF or just a custom template or just doing a Save As to get a similar part design with a mod.

     

      S
      21-Topaz I
      STEVEG21-Topaz I
      21-Topaz I
      March 28, 2019

      We have been doing this for many years now and it's worked just fine but you do have to be careful.

       

      One of the things we do is if we are introducing a new part number to the table then we don't revise the existing numbers.

      Terms & ConditionsAccessibility statement