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.

Settings

From the time clock main idle screen, press the gear icon in the upper left to access the Settings Menu.

The table below summarizes each of the apps available in the Settings Menu:

info

Initially there are no security pins required to get into the Settings Menu. You can assign security pins in the Clock Profile.

App	Description
About	Shows general information about the clock, including its name, IP address, version and online status.
Enroll	Enroll users on a biometric clock. A distributable document is located here: Biometric Enrollment
Network	Adjust network settings; the clock defaults to DHCP and we recommend you manage IP's at the DHCP server by way of MAC as opposed to setting a static IP address on the clock
Biometric	Shows the detected biometric type if available
Card Reader	Test app for reading cards; used with the Clock Profile app to test the decode raw cardreader data
Sync	Forces a update to the platform servers; this occurs automatically every 10 minutes and will reconnect a clock to the platform automatically in the event of a network outage
Offline Queue	In the event of a network outage, punches are still recorded and stored in the Offline Queue. Upon reconnection the clock will automatically resend these punches in the order received.
Update	Checks for an available update on the platform servers. An update request can also be made from within the Clock Management app within the platform. The clock will receive the reboot request on the next automated sync.
Reboot	Reboots the clock. Can also be requested from the Clock Management app within the platform. The clock will receive the reboot request on the next automated sync.
Reset	Removes all stored data on the clock and returns it to the unregistered state. NOTE: no user data or enrollments are removed at the server, this step simply unregisters the clock with your platform instance and removes local data.
Exit	Used to exit the app to the underlying OS for support purposes

User Identification

Identification is managed by the Clock Profile assigned to the selected clock. Generally identification starts with one of the following:

• Keypad entry using the on-screen keypad to enter an employee or badge number
• Cardread using a Prox or Barcode card which corresponds to a badge number of a user
• Login button when using a biometric in Identification mode

If using a biometric in Verify mode with keypad or cardreader modes above, the biometric verification will be prompted (e.g. place finger, take picture) before continuing to the clock's chosen application. The screenshot below shows the punch app:

In addition to the default app, the user can press the Menu button in the upper left to access other apps available on the clock, or the Done button to exit the session and return to the main screen.

Note

Generally, a timeout will cause the app to return to the main screen without having to press Done so the clock is ready for the next user if the current user walks away.

Transactions

Transactions collected at the clock--such as punches, leave requests or messages--are sent immediately to the platform and are therefore visible in the target app (e.g. Timesheets). If a clock is off-line due to a network disruption, certain applications--such as leave request--won't be available as those applications require information not stored on the clock.

The Punch app is able to operate offline and will continue to collect transactions from users. These offline transactions are stored in the Offline Queue and will be transmitted automatically when network connectivity is restored.

Transactions recorded at a clock can be viewed through the Clock Management app. They are also visible through Timecards (by Employee) and in the Punches app (by Date).

Event Logs

Clock events are transmitted to the platform and are visible through the Clock Management app. Events include user and system events such as:

• User authenticated
• Verification failed
• User enrolled
• Clock rebooted
• Update requested