- This topic has 1 reply, 2 voices, and was last updated 2 years, 3 months ago by Terri V..
-
AuthorPosts
-
7 August 2024 at 6:42 am #8508LFLuc F.
Hello,
We are experiencing an issue when employees log into multiple job tasks. If we ask them to log into 5 tasks, they often get disconnected after 2 or 3. Sometimes one employee manages to do it, while another gets disconnected every time.
Do you have any ideas on how we can resolve this issue?
Thank you in advance.
7 August 2024 at 7:46 am #9965TVTerri V.Insight WorksHello Luc,
I’m not sure I understand what you mean with disconnected. Are you saying the time card is getting closed? This could be explained by the length of time between the initial clock on and whenever the user comes back to the SF web client. There is a setting on the SF setup page near the top called “Hours before close”. This value indicates the number of hours of inactivity – you should have a number around 11 hours. What this does is to automatically close the time card is more than 11 hours have passed and then the user scans his employee badge, the systems recognize an open time card to his name, but the amount of time is say 12h, therefore that time card is automatically closed and a brand new time card is presented to the user.
If instead you are referring to scenarios where you have multiple open time card lines and how some time card lines are being clocked off, this could be a misunderstanding or misconfiguration of the automatic time splitting feature. When users start working on say 5 operations, they need to clock onto these more or less at the same time, with no significant time between the user clocking onto them. The user will then work for X amount of time, then he can clock off and this should trigger the time splitting for all routing lines in that time splitting batch. Which lines get clocked off will depend.
A few settings will impact this behaviour, found on the SF client configuration card:
“Auto-Split by” = this will define what operations are included in the same batch or not. Typically, this is set to “Same Work center” which means that only routing lines with the same WC on the TC line will be in the same batch. If you have a Machine center on the TC line, even if it is the same WC, this is not considered the same. If you want to split routing lines across multiple WC/MC you need to set this value to “Work Centers in filter” and then list all the MC/WC where you want to group them together in the “Auto-Split Work Center Filter” field. If you do have “Same Work Center” this could explain why some TC lines get clocked OFF while other don’t.
“Auto-Split Lines” = This could also explain some different behaviours you are seeing. I would recommend you set this to “All matching lines” meaning whichever TC line you use to clock off (either with the button or by scanning the barcode from the job card report) this will clock OFF all lines in the same batch. If you have the other option of “Selected line and previous lines” then which one of the group will matter as only the selected line and previous lines get clocked off while the ones below will not.
Please see this page here for more information on the automatic time splitting feature: https://kb.dmsiworks.com/knowledge-base/configure-shop-floor-insight-for-automatic-time-splitting-scenarios/.
Remember to close and re-open the browsers on the scanning stations after any setting change in BC.
If you are still having issues or have questions, please submit a ticket to su*****@*******ks.com.
Thank you,
-
AuthorPosts
- Sign in below to reply.