Is there a way to specify part backflush via the MoM or other methods beyond the site/detail maintenance? I am aware we can create another PN but that is not preferred.
Eg. Assembly A has Part Z that should be set to backflush.
Assembly B has Part Z that will not be set to backflush.
A part has to have a related operation in the MOM in order to backflush. The backflushing is tied to the reporting against that specified related operation for the backflushed part.
I suppose if you has a material with no related operation that would do it. I’m not sure you’re meant to do that though, ymmv.
That could work. However we need the job material backflush marked in Assm A and not Assm B. We use this to base our pick kits in the fulfillment WB.
I understand we can fulfill both materials the same, but we only pick kits for our jobs once. Assm B would take place 2 weeks early in a different part of the plant.
We’ve been doing this for months. I will say it feels wrong to set up, but we haven’t run into any major issues yet.
This works great at the top level of the MOM. It starts to get a little dicey when the parts you want left as open are multiple levels deep, but it can be done.
@elange It may depend on your setup, as well. We have jobs with multiple phantom assemblies, but they are all done at the same resource with the same operation. If the parts you want left open are top level, just remove the related operations. If the parts are under an assembly within the MOM, the assembly/phantom number should not have a related operation. Then, create a MOM for the assembly and all included materials. Add another operation to the assembly (if backflushing some parts) and leave desired open parts without a related operation.
To summarize:
Top level - related operation on everything except the assembly number
Assembly level - add another operation, set related op on everything except the desired open parts.
For us, any additional assembly operations have a production standard of zero, so no extra labor cost is added. This does create duplicate operations on the traveler and resource scheduling boards, but we filter out operations with zero hours to combat this. The real fun is when the same assembly is used on multiple resources and you need to set up alternate methods.
Hopefully this makes some sense. I spent quite a bit of time playing with this because it was our number one issue after switching to Epicor. It feels like it’s not the intended way of doing things, but it made a huge difference for us.