All Capabilities Tied to a Resource Pulled When Adding an Operation

Currently from a scheduling perspective I’d like to implement more capabilities within our ERP. We have a lot of similar machines with subtle differences that allow some parts to run across a few and not others. Part A might be able to run on machines 1,2 and 5 while part B can only run on 2,3, and 5. We’ve used capabilities in the past effectively to help the system route these jobs to the correct resources including preference when needed.

The issue I’m having is whenever scheduling, estimating, or engineering is adding this resource to a MOM it is pulling ALL capabilities. This requires manually removing them and when this step is forgotten we have a job routed to 3+ machines simultaneously.

Is there any way to prevent this from happening by default?

We haven’t seen this. When we change a method, I request the resource group be removed and replaced by a capability on the operation.

Never had any issues with that not working correctly, and the scheduler handles the resource scheduling properly. Our situation is remarkably similar to yours…

So if you add an operation to a job manually rather than editing the MOM, and that operation is tied to a resource that has capabilities they don’t all end up as scheduled resources? (see pictures)

image

image

We remove the resource and resource group callouts on the operation, and replace it with the capability. After the order is rescheduled, it will select the resource that has available time in the priority that they are established in the capability.

The only way to tell where the work is scheduled is to see the “Scheduled Resources” tab on the operation. Just because the capability calls out a set of resources does not mean that is where it gets placed.

The matching of the resource contained in the capability only occurs through the scheduling process.

It also works the same way if the capability is in the method. The unfirm job created through MRP will select the available resource in the capability, and the job will be scheduled to run there.

It works well, but we had to tinker with the capability in order to get it to work. If not done properly, clocking errors can occur.