Can an employee be logged into two jobs as once via MES?
We have a resource group that (for simplicity purposes) cuts something in half (we’ll say job 1 & job 2), then the one half stays on job 1 & goes to the next cutter - the other half stays on job 2 & goes to the other next cutter - thus OP10 should have two jobs running simultaneously.
Would this be a toggle somewhere at the employee level, the resource group level or the operation level?
We have researched split operation & split burden, neither of which are what we need.
Epicor does not restrict how many jobs a single operator can be clocked into. However, it also doesn’t do a “labor cost splitting”… so if an operator is logged into 2 jobs simultaneously for 2 hours each, he’s just “earned” 4 labor hours, and both parts are costed with 2 hours of employee labor.
There are lots of creative workarounds, from setting up different employee IDs to changing costs on resource groups and more, depending on how tight your costing is and what your priorities are.
Is this true in E10 or just E9.
It’s the same in E10. I had a client (I think on 10.1.500) who had built multiple “employee” records that they would use on specific labor transactions so labor costs could be split out appropriately.
Also, make sure about this
We had problems with the employees that were logged in into 2 or more operations because we did not have this checked.
That switch indicates that the Machine time is dependent on the operator. If a Machine/Resource cannot be productive without labor (such as assembly or other manual process) then the burden hours will = the labor hours. With that switch off, if an operator runs two resources, each Operation Resource will receive the full amount of time the employee is clocked in for.
As an example, you have a shear and a deburr. Once loaded the shear will run without the operator. The operator is to deburr the parts that come off the shear while the shear is running. In this case, you cannot deburr the parts without the operator. So the Shear resource/resource group can run without burden = labor. The deburr however cannot and therefor the deburr resource/resource group must run burden = labor.
I hope that is a good explanation of that switch.