![]() This goes a long way to tracking down problems, and determining if the trouble is systemic or user oriented. To further harden the integrity of this system, I have a method for determining the difference in clock punches from the automated system, versus the employee punches. Since our system is in-house, it does a lot of special operations. Make sure the software logs punch records well. This give not only HR support if a payroll question is raised, it also gives a last-chance for the employees to make a claim for a correction if something is amiss. One of our reports that is delivered each week is a sign-off summary so that each employee can initial their time. Make a sign-off sheet: HR will want something on record for employees to acknowledge their weekly time. In our case, we use a form that folks submit for corrections of any kind, and it becomes part of someone's daily/weekly routine to enter in corrections as needed. If you have addressed the above note (manual corrections) properly, times where there is an actual outage will be more of the same. An ACTUAL network outage: While 99% of reported time clock errors, in our case, actually have nothing to do with the network being down, it has happened. (Forgot to clock, left their badge, forgot their pin, or my all time favorite. At the end of the day (or week) SOMEONE will always have their time wrong. Manual Time corrections will always be required. So have an alternative method, such as PIN code ready for those folks. Access Cards (RFID): These are GREAT, but understand that employees will forget them, break them, and or lose them. While writing your own may not be an option, but here are the lessons learned from our deployment. We report this directly with SSRS report delivered to department heads via email subscriptions. In our case, I opted to create our own software that ties into our ERP system, using the same SQL backend and a series of touch-screen all-in-ones. My company went through a conversion to networked time tracking a while back. I think it is one of the more prominent and has integration with a number of external ERP/accounting systems. I have heard of good things about Kronos. I'm currently leaning towards one of the Pyramid Time Systems network clocks purely because of what I've read. I'll update and respond as I organize my own comparisons. I'm just trying to get a litmus test of what I should be looking at so I don't end up screwing myself and my coworkers by implementing and supporting a garbage system. How do you compensate for problems, including network failure? What is it like to configure or maintain? Is it fob, card, pin, or bio-metric? Do you have a preference? Is this service any good?ĭoes your company use a physical networked time card machine or a software based service? If so, what kind and who's the vendor?ĭoes it save/collate data and support integration with outside services? ![]() We've got locations in two different states, so we are also contemplating a software or cloud based service such as Paychex's Flex Time service as well. In a failure mode we'd probably pass out manual cards just in case. Store to their local memory or to a network share, and the OS/Cloudīased service will be completely unavailable unless hosted within the ![]() I'm guessing that with a network failure, the physical punches will Personally I'd like to find one that works with Wiegand format fobs to save money and keep us from buying more hardware, but that's purely optional. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |