![]() ![]() The app was NOT tied in automatically to HR or payroll. (Edits in submitted data were flagged and visible to the staff member, management, and the admins who took care of the back end of the app.) They could go back and edit their times for up to four weeks and view times back for twelve months, and managers could go back eight weeks in subordinates' sheets and apply edits. Users just fired it up and input their in and out times each day. It wasn't automated, and therefore did not require monitors, badges, or any of that hardware. The best one I've ever seen was a very simple (on the surface) in-house application which mimicked a timesheet. If a Samsung umpc can last 2 years - these should last 5. If every clock dropped dead on one year warranty expiration day +1, it would be a wash, and I expect these to last for years in our clean environment with light usage. ![]() If we go company wide (we will) our 1st year cost for software and hardware will be about equal to a year of leasing clocks and paying recurring fees to Paychex. We went with a clock from TimeClockPlus - 25% less than a dumbed down Paychex clock, no recurring monthly user fees. Aside from the cost, it's a huge point of failure. I have some locations so small they wouldn't have a clock were it not there simply to provide continuity throughout the company. So.they want to lease us expensive clocks with the guts ripped out of them, so we have to provide a host pc, and pay a monthly per user fee? Then I received the system requirements and to make a long story short, to maintain compatibility with an old web architecture, they apply an overlay on their hardware clocks to turn them into dumb terminals, which are then dependent upon a pc on the local subnet that runs a 'helper' service to "facilitate network communications" Jumped through the sales hoops - arranged a no cost trial. I just went through an attempt to implement Paychex Time & Labor Online. ![]() Grrrr.I swore I wasn't gonna post about this, but. The only issue I've had is that because the implementation is non standard, there is no provision for offline punch storage upon loss of connectivity. It sounds hokey, but the umpc's were the least expensive devices I could get at the time. We've been using an old small biz version of TimeClockPlus on umpc's connecting via rdp to their own instance of the onscreen clock. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |