MPMLink Process Plan - Splitting QTYs during allocation

[GregOlson]

What is the best practice for being able to split quantities into different operations.  We are a bit confused here on how to proceed.

Assembly:  410-158444

Child parts:  401-158888 (QTY 4) needs to be split between 2 operations in the process plan.

Do we make a manufacturing view of this part, add another instance of 401-158888 with a qty of 2 and then from the occurrences tab reduce the number of the original 4 to 2?  Please provide any details you can (what UIs Explorers or browsers) to achieve this.

We have quite a few assemblies that the design view could be used in the process plan - except for the allocation of qty to operations.

Thanks,

Greg

[GregoryPERASSO]

Hello

yes, think today you have to change View and split the usage link .  Cause MPMLink (like SAP ERP) does not  allow to allocate occurrences of the same Usage link in different operations (even if PTC have prepared something in the data model for this .... but not fully implemented.)

We exactly do that today.

But we do not manage occurrences .  Only quantity on usage links. So I can no tell you how to correctly handle occurences... Notably for the 3D représentations of the ProcessPlan if you want to use Work Instructions features .

the 11M020 ,in the HTML dual eBOM/mBOM comparator, there's some new features for managing equivalent occurrence links between eBOM and mBOM. So hope it will be better than the applet...

regards

Gregory

[GregOlson]

So what you guys are currently doing (using the above example) would be:

1. Create downstream MFG view with a qty 4 of 401-158888. 
2. Using the structure tab of the mBOM you'll split up the qtys needed by changing from a QTY (4) to two QTY (2) - Uses tab?  I believe that you would need to remove a couple occurrences and add the part in the BOM again to achieve this.
3. End goal would be
   1. 401-158888 (QTY 2)
   2. 401-158888 (QTY 2)

Greg

[GregoryPERASSO]

Yes exactly.

by "not managing occurrences", I mean that today , we use our mBOM only to feed our ERP.

So occurrences are deleted without taking care of the exact instances ... and we do not update occurrences on the mBOM after that.