I am looking for a little guidance on the right way to setup our labor resources. For testing we have setup labor resource groups that match the machine resource groups. For example, we have a Vertical Mill group (4A), and there is also a Vertical Mill Labor group (L4A). Within L4A, I list out the employee IDs of the people that are capable of using that machine. group. But we know some of these guys can also run a lathe, or a bridgeport.
Ideally, we have a list of employees, and then for each employee, a list of the resources they can operate.
What do you think? Do we setup a labor group that represents the entire shop? Then somehow apply capabilities to the individual resources? I am not clear on this part.
Thanks!
Nate
I think we should use Capabilities. Setup a labor capability for each resource group. Then I can assign the users to the capability. The users come from the âLaborâ resource group.
Nate - we have a similar issue and your supposition is how we did it. Just be careful on your setup and especially on the ârequiredâ resources listed on each operation. In your example, the real catch is for employees who could move back and forth across machine groups. We have some of those as well, but we track that manually b/c it doesnât happen often (We catch it in Labordtl).
Instead of the way we did it (below), you could do the one labor pool and use Capability. You just have to make sure whomever is creating jobs, is using it correctly. If you are using the configurator, you can use the ârulesâ to your advantage and maybe have two groups - a general labor pool and s âspecialâ labor pool for those who move about and/or have capabilities. That way the configurator rules can determine if a capability is required or not and choose the right group to place on the operation. Since we use the Configurator, weâd do it like this if we werenât already doing it differently.
If you care - this is how we are currently:
We have about 60 âoperatorsâ across 4 machine types. not an even distribution but close enough. Within each group of machines there are âspecialâ machines or âspecialâ skills that are required for some operations. And each of our operations has a machine and operator resource specified as required. So, using Capability, we can match a machine AND an operator to an Operation via the Configurator.
Our Configurator and our MOM/BOMs use Capabilities wherever we could, and the whole things works nicely once you get the ârulesâ setup right.
The users come from the âLaborâ resource group.