# Burden Hours Hybrid Solution

**URL:** <https://www.epiusers.help/t/burden-hours-hybrid-solution/130170>\
**Category:** Kinetic ERP\
**Created:** [October 21, 2025, 7:57pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170 "2025-10-21T19:57:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bridget\_Casey1](https://www.epiusers.help/user_avatar/www.epiusers.help/bridget_casey1/32/27296_2.png) [@Bridget\_Casey1](https://www.epiusers.help/u/Bridget_Casey1)\
**Post date:** [October 21, 2025, 7:57pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170/1 "2025-10-21T19:57:57Z")

</div>

In our shop, we have our Resources set to **Split Burden** because we can have one person running three different jobs on three machines at the same time. In that setup, the labor gets split three ways, but the burden is calculated for the full shift on each machine—since each machine is actually running for the entire shift.

Now, we’re running into a **hybrid situation** where one machine is running three different jobs throughout the day. The operator stays clocked into all three jobs at once, so the system is **tripling the burden** for that single machine.

However, switching the setting to **Burden = Labor** doesn’t solve the problem either. In some cases, that same operator might be clocked into three jobs for one machine **and** another job on a different machine. That causes the burden to be divided four ways, which still doesn’t reflect reality.

Does anyone have ideas or recommendations on how to handle this scenario more accurately?

---

<div class="post-metadata">

**Author:** ![jkane](https://www.epiusers.help/user_avatar/www.epiusers.help/jkane/32/57624_2.png) [@jkane](https://www.epiusers.help/u/jkane)\
**Post date:** [October 21, 2025, 7:59pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170/2 "2025-10-21T19:59:26Z")

</div>

If you have Advanced Production and Scheduling, you can batch the operations together so only one operation is being used.

---

<div class="post-metadata">

**Author:** ![Bridget\_Casey1](https://www.epiusers.help/user_avatar/www.epiusers.help/bridget_casey1/32/27296_2.png) [@Bridget\_Casey1](https://www.epiusers.help/u/Bridget_Casey1)\
**Post date:** [October 22, 2025, 1:11pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170/3 "2025-10-22T13:11:00Z")

</div>

> [@jkane](#):
>
> Advanced Production a

Thank you John! But I am not sure if this would solve my issue. They are 3 separate part numbers running through out the day on one machine but it is to much to have the operator keep clocking in and out of each job. Can you maybe provide an example on how Advanced Production and scheduling would work?

---

<div class="post-metadata">

**Author:** ![hackaphreaka](https://www.epiusers.help/user_avatar/www.epiusers.help/hackaphreaka/32/56320_2.png) [@hackaphreaka](https://www.epiusers.help/u/hackaphreaka)\
**Post date:** [October 22, 2025, 1:17pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170/4 "2025-10-22T13:17:22Z")

</div>

> [@Bridget\_Casey1](#):
>
> it is to much to have the operator keep clocking in and out of each job

Can you go into a bit more detail here?

The operator is clocked into jobs they aren’t actively working on?

---

<div class="post-metadata">

**Author:** ![jkane](https://www.epiusers.help/user_avatar/www.epiusers.help/jkane/32/57624_2.png) [@jkane](https://www.epiusers.help/u/jkane)\
**Post date:** [October 22, 2025, 2:05pm UTC](https://www.epiusers.help/t/burden-hours-hybrid-solution/130170/5 "2025-10-22T14:05:40Z")

</div>

Batching takes all of the operations you select and creates a single operation. It would give the operator one job/operation to log into. You can only use it if you have APS though