Part Instance Allocation

[BF_13811900]

Version: Windchill 13.0

Use Case: The OOTB Windchill functionality appears to only allow one part instance allocation to each part included in the structure of a parent part Instance. For example, it appears that if I wished to associate 100 different instances of a child part within the structure of a parent part instance, I would first have to specify that the quantity of the child part is 100 before then allocating a unique part instance to each of the 100 rows. This could end up being quite time consuming.

Description:

I am unable to find a way of achieving the same objective in a more efficient manner. For example, it would be nice if it was possible to only include one row under the parent part instance which communicates the details of the child part. Using my example above, I could use this single row to specify a quantity of 100 before then using the "Allocate Existing Part Instance" wizard to multi-select the 100 child part instances I would like to associate with the row used to represent the child part.

Can anybody suggest a more efficient means of allocating part instances to parts listed in a part structure than the functionality detailed in the "Use Case" section of this post?

[avillanueva]

In you example, are you saying you have 100 unique part instances of that component? Would these be 100 unique series numbers you are trying to allocate? I think the functionality did not expect so many which is why a multi-select does not exist. Something like a bunch of fasteners would not be serialized therefore should not need to be allocated as unique instances. Note I have not used this functionality but just postulating on its use. 

[BF_13811900]

Hi. That's exactly what I'm saying. It would be 100 unique serial numbers, using my example.