Introduction
Hardware time clocks, web-based clocks and mobile are all managed via the Clock Management section of the System Menu. The following topics outline the infrastructure for adding and maintaining clocks on the platform.
Clock Profiles
Each clock, web clock and mobile device is controlled by a Clock Profile which manages the authentication, applications and other behaviors of the device.
Sample Clock Profiles are included for typical time clock, web and mobile use. A profile should be created for each unique set of properties you'd like to maintain, while clocks then share profiles based on those properties. For example, hardware time clocks may contain a biometric, so the profile for those devices will contain instruction on how to authenticate with biometric. Web clocks and mobile won't use biometric (at least within the app) so require their own profile without biometric options.
Clock Groups
Clock Groups allow you to create collections of clocks, against which users are assigned. In this way, a user can only use the clocks which belong to their clock group. Clocks can belong to more than one group, so group membership can be overlapping. Users, however, can only belong to one Clock Group.
Installing Time Clocks
Time clock installation is a relatively simple process which can be performed by IT or mechanical personel. The time clock comes with the following included in each box:
- Clock
- Mounting backplate (attached to the clock)
- Backplate tool (for removing the backplate)
- PoE circuit board (attached to the backplate via ribbon cable)
- DC power supply (as a backup in the event PoE is not available)
- Quick Reference Guide (installation instructions)
Registering Time Clocks
When a clock is initially booted up the first time, it will display a unique device validation ID. This validation ID is used to add the clock to your platform instance.
Registering Web Clocks
Web clocks are PCs, tablets or other shared devices which run the same clock application as hardware time clock, but on your browser based device. The requirements to run a Web Clock are:
- Late model device (must have sufficient CPU to run modern browser)
- Chrome, Edge, Safari, Firefox or compatible browser with latest updates
- Internet connect (wired or wifi)
The registration process is similar to the hardware time clocks in-that a unique validation ID will be generated by the app running on the local device. That validation ID is then entered through the clock registration wizard in the platform application.
Registering Mobile
Users can access the platform in one of two ways:
- Via web login at https://app.simplywork.com on any device (PC, tablet, or mobile), or
- Through the dedicated clock app at https://clockapp.simplywork.com.
The benefit of the second choice is that the app is dedicated to being a clock vs a full user web experience. Authentication, UX and other aspects have been optimized for a general clock experience (including scheduling, leave and messaging.)
Clock Management
Registered time clocks, web clocks and mobile users are all managed using the Clocks app under the System Menu Clock Management. The current status of the clock is displayed in the far right. Time clocks check-in every 10 minutes with an update on their current time, and collect any instruction such as Reboot, Update, etc. Web clocks and mobile may not check-in if the app is not currently running. The Current Time column corresponds to the last time the device has checked in.
Time Clock App
The time clock app is driven by the platform, so the user experience can vary based on your application choices: punching, leave request, scheduling, messaging and more. The sections below cover the Settings available at the clock and Identification to start a user session.