MES - multiple labor detail entries for exact same time on different resource groups

Kinetic ERP
1

Problem: We have MES Labor Detail records for the same employee, same date, same clock in and out time, same job, different assemblies and operation. It appears that duplicate transactions are being created for different assemblies and operations.

I am investigating the issue. Unfortunately, I have not found the pattern to the problem or the root cause. I am hoping that you can give me ideas to check and test to find the issue root cause.

Here is an example to describe the issue more clearly.

Labor Detail 1)

image

Employee 406 clocked on the job and was on the resource group ROUT. He started at 6.30 and finished at 7.20.

Labor Detail 2) This is the almost duplicate labor detail transaction.

image

Here is the second transaction for the same employee, same day, same job, and almost the exact same time. But the asm and opr are different and the resource group is different. The resource groups ROUT and ASSY are in different parts of our building and there is no way to work on these 2 resource groups at the same time.

I wondered if the operator was using the work queue to clock on both assemblies and operations at the same time. But these two resource groups are not in the same department and there is no way these two transactions would show up at the same time on the work queue. So I don’t think this issue has to do with the work queue.

In the last month, I have 72 records with this issue. Based on the number of records, I also don’t think employees are purposefully clocking on 2 different operations using Start Production Activity.

Question) Are there fields that I can check to determine if these were work queue entries or Start Production Activity entries?

Question) Will the SysRevID and SysRowID help me to track the issue?

There is one more hint to the issue. Sometimes when there are two almost identical transactions, the operator immediately clocks off one of the duplicates and puts quantity 0.

Example Labor 1)

image

I think in this example the operator noticed there were two transactions and immediately clocked off this one and entered a 0 quantity.

Example Labor 2)

image

Same employee, same date, same job, and same clock in time. Different resource group. But notice that it is for the same Asm and Opr. We only have one scheduled resource for the operation.

image
image1857×728 69.8 KB

I have only looked at the last month of data. This issue existed before the update to 2026 and after the update. For approximately 10,000 labor transactions this issue is hitting 72 times. There were also multiple people that worked on this same job, assembly, and operation. None of the other transactions had the same duplication issue.

Can you give me ideas for trouble shooting?

Thank you,

Heide

2

Not sure if this will help you, since there is limited info to go on, but…

We have the same issues maybe not for the same reason but it might be. We learned, there is no limitation to choosing Res Group/Resource when going through “Start Activity”. Anything can be chosen. The assigned resource is good, and it’s used for Scheduling and Work Queue data, but it’s not fixed.

Perhaps your employee has some difficulty with choosing the right resource - visual/learning impairment, focus issues, whatever - doesn’t matter, except that you work with them to find out what’s going on.

In our case, we put some barcodes on our Job Travelers and are making Resource barcode cheat sheets at MES stations which also have scanners. This is a slow process as we identify problem areas but eventually it’ll be at all the MES stations. That’s how they do it now. This is recent for us because we just started asking them to log into a machine resource instead of their operator resource (which is the default value) and this has created a similar issue to yours.