Batching jobs for a single operation - not the entire job, split burden/labor

We may be asking too much of the system, but this process requires a fair amount of flexibility. Our goal is to batch operations at a resource, not entire jobs. However, the current scheduling batching process groups the whole job, which isn’t what we want.

In many cases, we don’t know ahead of time which jobs will be batched together. In one scenario, at a Hydro operation, one person may be working on multiple jobs simultaneously. In another case, we may have a resource like an oven that can run up to three jobs at once but not always run three jobs. We tried to use split burden, but it doesn’t seem to behave as we expect in these scenarios. We also track an employee rate, so splitting the labor across the jobs as well is important. What happens is, Joe clocks into 5 jobs for 5 hours. Instead of Epicor splitting out the hours to each job, it allocates all 5 hours to each job. We do custom work, so we were hoping to leverage time and quantity. Now I am leaning towards switching it to quantity only but still don’t know how best to track additional rework costs without adding another T&Q operation.

How are others handling these types of scenarios?

1 Like

You can batch a single operation with APS. Do you own APS?

Yes we have APS. We worked with a consultant to review batching and was informed it batches all of the jobs and puts them onto a new job, doing make to job.

Correct, but you can choose to only group a single operation across the original jobs. If you have 5 jobs with operation X, you can batch only operation X and it will create a new job with a single operation. You perform the operation and the demand link for that job will be a make to job back to the original jobs. It will split the costs based off of the co-part calculations you put in and should be fairly accurate based on rounding.

1 Like