What you are describing is how a phantom assembly works. I've always looked at the gathering part as in where you have something like a purchased assembly but you need to track the parts in it for design, but in manufacturing you would only see the top level because it is bought as a unit. Then what should happen is that it should remove the gathering parts from the mBOM.
The Gathering Part attribute identifies a part that is not manufactured, but is created to facilitate the CAD design by acting as a “part container”. Gathering parts do not appear in product structure reports such as a BoM, and their children are rolled up to the next higher-level assembly in the product structure tree. The value of this attribute can be set to Yes or No.
Phantom
The Phantom attribute identifies a part that is not physically assembled and stored, but is created to facilitate the product manufacturing process. For example, a welding jig. The value of this attribute can be set to Yes or No.
Please see this thread on Gathering Parts from 2013. Gathering Part The definition that I show in this discussion is from Windchill help and is a screen shot.
Historically in the manufacturing world between Engineering (PDM) and manufacturing (MRP or ERP), a phantom has always been an assembly that shows a structure but isn't produced.
So a phantom in Windchill produces the same affect when going from eBOM to mBOM. Per the definition in the thread link I provide, gathering parts are the parts that are just gathered to make your CAD structure, ie a purchased assembly.
Where in the Windchill help is that definition???? I'm having a hard time finding it when I open help center from my Windchill. Here is what I show for Phantoms in Windchill help.
i'm agree with Daniel. I've created the same Enhancement Request few years ago after a Technical Support call. Cause I was pretty sure that i have seen this in a demo ... bu unfortunately not ...
The gathering is clearly a CAD workaround .... notably for Creo where the assembly tree is file driven. contrary to Catia or CADDS where we can create some assembly nodes , with positionning or features , without creating a CAD file for this level ....
I only see this ability to work in 1 scenario, as a 1 time effort to allocate the parts to the mBOM. The problem you are describing doesn't work so well when the gathering assembly is updated and parts are added/removed. You cannot have those updates to the assembly automatically update your mBOM. Since the gathering node no longer exists on the mBOM side, any changes have to be done manually.
Question for you Daniel, do you see this as being a 1 time action to roll up the parts, or do you expect it to update your BOM every time the gathering assembly is updated?
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
