For anyone uses API Time & Attendance, do any of you use their beacon technology? If so, what do you like/not like about it? Complaints from employees? Functions work/don't work as expected? How big is your organization?
We have API Time and Attendance and are just looking at the Mobile Workforce. I am interested as well in what others think of the beacon technology. My original though is if they have to be within a short distance to clock in, then they might as well swipe at a badge reader. But would like to hear other opinions.
Thank you
We have API Time and Attendance on v2018.3 and have been looking at the mobile app option. API is offering a temporary package for free till June. This would alleviate many people in close proximity when clocking in, cross infection risks on timeclocks. Currently we have quick badge available for all users and users can clock in from any PC in the network. The mobile app would require Payroll and HR blessing since it would allow the employee to use their mobile device for clocking.
We have API Time and Attendance 2016.4 and are in the process of upgrading to 2019. We implemented Mobile Workforce Managment about 8 months ago but chose NOT to use the beacons and do not allow them to clock in using the app. We use the app for team members to make clocking and calendar requests - not clocking in. Our managers use it to approve requests and approve time cards. We use the Staff Scheduling module so they can also view their schedules on their mobile device.
How is the security handled? Are the mobiles personal (i.e. they could have any thing loaded or jailbroke) or are they business provided/managed?
Most of them are personal devices - they were given instructions to download the app - we provide the Institution ID # and it is linked to their network login and password. We use MaaS360 to manage our devices.
Cindy, how many employees/API licenses does your company have? And do your managers make good use of the app--or only some?
We're on 2015.2, upgrading to 2019 later this year. A previous manager started the upgrade with the beacons in mind, but the current group manning the project doesn't think she knew the extent of cost for the Mobile Workforce Management--that it would be an annual cost per license, not per person actually using it. We have really old readers that are dying--plus our facilities team wants to go to a different prox badge for security rather than our current mag stripe badges that we use with our API readers as well. Just trying to work our way through all the options since cost is pretty daunting either way.
We have 3000 licenses. No - I do not think that the managers use it as much as we expected - nor do the employees - could be because we do not allow them to clock in/out with the app. We use a proximity badge for our door readers but still use the magnetic stripe for our time and attendance readers. We currently have mostly EIS1000 readers but recently purchased a few of the newer EIS5000 readers. We need to replace the EIS1000 readers as they are not supported any longer and are breaking fairly regularly (2 this past week). We opted to spend the money on the newer badge readers and the upgrade. We felt too much risk and cost right now with the beacons.
We have API Time and Attendance, Scheduling and mobile - St Luke's Health System Boise, ID. We performed an upgrade this week to most current version 2019.4.0.1 and have over 15,000 user base using the application. We interface currently to Lawson S3 with a project underway to Infor CSF/GHR Cloudsuite.
Kent, what is your experience with the mobile solution in your organization? Thanks
We introduced mobile over 2 years ago and has been good. We definitely had our issues but overall we are pleased with the choice - especially open shift notification time. We use SSO authentication and have not test environment to test patches with, so when upgrades happen we do a lot of finger crossing that mobile still works. All in all - we use and necessary to have these days!
I appreciate your insight.
I have a followup to this question. I do not see that anyone implemented Beacons at that time. Has anyone made the decision to use Beacons? what are the Pros and Cons? We are in the process of switching to API. Our Networking team seems to have security concerns regarding Beacons but are not specific about it. I appreciate your insight
