Splitting Labor and Burden Costs Between Resource Groups

Good morning,
As we move towards scheduling in Epicor, we are considering using two resource groups for some operations. One would be the machine resource, and one would be the person resource. To this end, I have setup two resource groups. One for the vertical milling machines (4A), and one for all the laborers in the shop (LB). I add all 16 machines that can be scheduled as resources to 4A. I add all 30 shop laborers to the labor group LB.

Next, I setup the capabilities for machines and labor. C4A, and L4A. To C4A, I add all 16 machines, and the primary resource group 4A. To L4A, I add only the 5 guys that can run vertical mills L10-L14, and I set the primary resource group to LB.

Now, I setup the operations for the job. The operation 130 requires the C4A, and L4A capabilities. Once I schedule the job, Epicor picks resources for these capabilities, say machine #15, and laborer L10.

In the past all of our work was done without labor resources, so the labor and burden cost was included all inside the 4A resource group. We are trying to figure out if we should take the labor cost out of the machine RG, and add it to the individual labor resources instead.

Should we split this way? What are the downstream implications? This is related to another scheduling question I just asked:
Scheduling and MES for Multiple Resource Groups on a Single Operation - Kinetic 202X - Epicor User Help Forum (epiusers.help)

In this post I couldn’t see the labor resource being utilized after my user clocked into the job we just setup. I could only see the machine resource. (in MES or in T&E entry, or in Job tracker)
Thanks for your time!
Nate

The labor rates on resources are only used for quoting and costing. They are not used on actual.

The actual labor rate comes from the employee record when they start activity.

1 Like

I think the answer is - don’t put labor costs into the Costing Labor Rates fields for labor resources. Only put those labor costs in the machine resource group.
I am going to push forward with this! Thanks John!