MES issues: 9.05.606

Yahoo Archive
1
I don't know if this is the solution, but we see a slow down if even one Employee does not clock out after several days. It sounds like the effect you are seeing, but we do not use the Epicor time and attendance system, we just have "backflush" employees by dept/area.

Logging out and clocking out are not the same.

Hope it helps...

Brad Boes
Metalworks


--- In vantage@yahoogroups.com, "shannon3d" <shannon3d@...> wrote:
>
> We recently added a new company and are using 14 MES stations to clock production workers in and out for the day and to log time on jobs. We're attempting to use these to generate payroll but so far it's been a nightmare.
>
> The MES screens are not responding in a consistent, timely manner. Seemly randomly, a login can take up to 17 seconds to complete. Start production can, again randomly, take 23 sec just to come up. Then if one is slow the whole process is slow until that employee hits log out. The next round may be fine- 1.4 sec to login, 4 to Start prod act, ect. It's not employee specific or user id specific. It's the worst kind of error: random. There may be a slight bias towards slowness on the first login in a session, but it's not 100% that way.
>
> We've run the performance tool and both the app and the network are operating within expectations. I'm in the process of comparing MES response times with network compression vs without (they're configured without at the moment), but I'm not seeing anything significant.
>
> The network times for this location is actually slightly faster than another location that isn't experiencing issues of this extent. The difference between the two locales being that this new location is using the Payroll module and the other isn't. The config files on these are the same as in the other locale. I can't see how PR would mess up the MES clocks, though.
>
> My local support guy is looking at this, my network team is looking at it, our on-staff Epicor specialist is looking at it. We're all coming up with a big question mark. I'm wondering if anyone in the group has experienced this headache and can give us a different angle to investigate.
>
> Thanks for any insight,
> Shannon
>
2
We recently added a new company and are using 14 MES stations to clock production workers in and out for the day and to log time on jobs. We're attempting to use these to generate payroll but so far it's been a nightmare.

The MES screens are not responding in a consistent, timely manner. Seemly randomly, a login can take up to 17 seconds to complete. Start production can, again randomly, take 23 sec just to come up. Then if one is slow the whole process is slow until that employee hits log out. The next round may be fine- 1.4 sec to login, 4 to Start prod act, ect. It's not employee specific or user id specific. It's the worst kind of error: random. There may be a slight bias towards slowness on the first login in a session, but it's not 100% that way.

We've run the performance tool and both the app and the network are operating within expectations. I'm in the process of comparing MES response times with network compression vs without (they're configured without at the moment), but I'm not seeing anything significant.

The network times for this location is actually slightly faster than another location that isn't experiencing issues of this extent. The difference between the two locales being that this new location is using the Payroll module and the other isn't. The config files on these are the same as in the other locale. I can't see how PR would mess up the MES clocks, though.

My local support guy is looking at this, my network team is looking at it, our on-staff Epicor specialist is looking at it. We're all coming up with a big question mark. I'm wondering if anyone in the group has experienced this headache and can give us a different angle to investigate.

Thanks for any insight,
Shannon