March 26, 2018
Today sees the addition of time punch logging to Online Time Clock MTS. To see what this is, how to enable it, and why it might be useful please see the Time Punch Logging Help Topic.
Posted by markn at 12:37 PM
March 23, 2018
Online Time Clock MTS will be unavailable for 1 hour at 6.30PM Pacific Time while we roll out a small update. The update adds time punch logging and a new report to display the log of changes to time punches.
Posted by markn at 10:30 AM
March 17, 2018
Today sees a major update to Online Time Clock MTS. The most visible changes to the system are the addition of GPS Location and GeoFencing.
A new setting has been added on the Tools->Time Clock Options->Display and Report Settings screen called Record GPS Position with Time Punches. When checked the GPS Position of all time punches created on the timeclock screen, the Edit Times screen, and via the mobile interface will be recorded. Obviously if the punch is recorded from a mobile device (like a cell phone or tablet) with built in GPS this location is going to be quite accurate.
If the time punch is recorded from a device without a built in GPS (say from a desktop computer or an older tablet) then GeoLocation is used to approximate the location of the device, accuracy of this can range from excellent to abysmal.
The GPS location of recorded time punches can be viewed on the new Time Punch Map which can be accessed via the Tools->Time Punch Map menu. This will allow you to view the time punches for an employee over any date range plotted out onto a map.
GeoFencing in Online Time Clock MTS allows you define geographic regions where your employees can punch in and out from. GeoFences (or fences) are defined by drawing shapes on a map. Fences can be specific to a time clock Location or global to your time clock account and are managed from the new Manage Fences screen available as usual from the Manage Data parent menu.
Fences and the Desktop Site
Fences can be applied to time clock user security logins to control the geographic location employees can punch in and out from using the Online Time Clock MTS Desktop Site. Given that the GPS accuracy of desktop computers can be patchy its likely that you'll have to define a large GeoFence to make things reliable. However this can still be useful especially when combined with Computer IP Address restrictions (see the Login Access Control help topic here).
Fences are assigned to Time Clock User Security Logins using the Manage Data->Manage Logins screen.
Fences and the Mobile Device Site
If your employees are using the Mobile Device Interface you can control where employees can punch in and out from on an employee by employee basis. Given that the accuracy of built in GPS systems in most cell phones and tablets is excellent you can probably define smaller Fences with more confidence.
Fences are assigned to Employees using the Manage Data->Manage Employees screen.
We've made many other changes to the system, some visible, some not. You'll notice that window positioning is more consistent, data lists are styled differently and sized more regularly, and that the time clock screen is a bit larger and more clearly laid out. What you won't notice is a total clean up of the backend data structures, a re-factoring of most of the client / server data communications, and updating of backend database code to with a more modern and reliable API.
This has been nearly 9 months in the making and we hope you're as excited about it as we are!
Posted by markn at 3:29 PM
March 15, 2018
We will be rolling out the Geolocation / GeoFencing upgrades to Online Time Clock MTS this Saturday, 17 March 2018 at 6.30PM Pacific Time. Online Time Clock MTS will be unavailable for 2-3 hours while we roll out the upgrades and do some final testing. Apologies for any inconvenience this might cause.
Posted by markn at 8:44 AM
March 1, 2018
As part of the upcoming Geolocation / GeoFencing upgrades Online Time Clock MTS will be unavailable for approximately 1 hour at 6:30PM PST this Sunday, 4 March 2018. Apologies for any inconvenience this might cause.
Posted by markn at 2:37 PM