Automation Studio Idea - End Activity / Clock out

A great solution Mark!

How about this for a “solution”. Nobody automagically clocked out but instead have a watcher check every [5/10/15] minutes and if someone is past their shift and hasn’t clocked out they (and supervisor) receive an e-mail notification. If indeed they left for the day and aren’t working OT then have a process in place wherein the person can reach out to mgmt who has availability to clock out for them and the next morning correct the labor entry. You would also need a UD field (LaborHead?) to capture an updated time for departure if working OT so you don’t get the notice until after the new departure time. Seems like it’s not too complicated to implement (in the std), gives visibility for followup and encourages everyone to remember to clock out (or they get annoying e-mails or texts).

2 Likes

OOO… even better yet… the recipe could send the email (or TEXT message) to the employee AND the supervisor… the email would not only notify, but would also have a BUTTON that would allow them to send a command back to clock them out. This way we can automate the cleanup. when they press the button, it could also mark the record as needing further review.

2 Likes

From what I have seen on Netflix, both of these have already been developed in Hawkins, Indiana! :shushing_face: Maybe you could license the technology just like you’ve done with Workato! Might be a little more difficult to transfer!

We have standardised this functionnality and we almost implement that functionnality for each of our client. You set the tolerance directly on the SHIFT (ex: +20min) and it automatically cock out anyone who has clocked on that shift.

We also have a customisation to add a trigger directly on the employee card.

Completed Qty = 0

What we did at a company I previously worked for was to have supervisors check Shop Tracker at the end of the shift for people who haven’t clocked out for the day. They had to reconcile everything before they left for the day.

2 Likes

What we currently use is to schedule a BAQ report running at 11:57 PM every day and then setup a BPM to detect that if the specific BAQ report was running, if yes, then in the BPM we use the c# code to end activities for all active labor detail records and then clock them out for all active labor head rows. No issues for almost 3 years. This solution is great. Also, that BAQ report will be sent to all the supervisors before the BPM clock out everybody.

2 Likes