Has anyone else seen a scenario where an employee clocking out through MES does not register?
We have multiple companies and this only seems to effect 1 of them where nearly all, but typically not all, employees will clock out but it will not register and will require someone else to clock them out and adjust the time after. It seems to happen 1-2 times per month for the past 3 months or so.
I believe in the past we had very, very sporadic reports of this but it seems to be happening more frequently now in 1 of our companies that we have seen before.
Clock ins don’t seem to be effected, other employees in other companies in the same building & on the same network clocking out at the same time are fine. All of the computers used on the shop floor are the same and the missed clock outs happen from all different computers with no errors being reported by the employees during the clock out process.
do you have any bpms on the clock out that would be company specific or behave differently?
What makes you sure they are doing the process in mes correctly and not just forgetting. I have a dashboard to see when employees are clocked out and there are always a few.
Absolutely nothing, to be honest one thought I’ve had is that they don’t like their supervisor so they play this game every now and then.
I think I have found the problem though but we are still monitoring the issue to see if it is the problem or not.
We have an updatable dashboard that makes changes to LaborHed, normally through T&E you can’t update an active record but the dashboard does not stop you. They have always been told not to make the adjustment unless the person is clocked out and swear up and down they are not but I can reproduce the problem at will by making changes to the record int he dashboard.
What adds onto this is that it only seems to effect the clock out if the employee is actively logged into an MES screen at the same time and do not switch stations or relaunch MES. If they go to clock out and the session has been uninterrupted it looks like they have clocked out but looking at T&E they have not, if they start a new session at any point it takes the clock out as expected.
I am not 100% sure this is the problem but the fact that I can reproduce it at will leads me to believe the supervisor is not following the process. I now have emails setup to be sent if certain fields are touched during an active transaction so I can monitor if/when changes are being made and what that ends up looking like at the end of the shift.
If this turns out to not be it then I am back to square one and suggesting that the supervisor has pissed his people off.