sbv.wiki - User contributions [en]

ZKTeco Enrolling Instructions

2024-03-22T15:25:17Z

David:

== Hello!!! Congratulations on your new clock. Please see the instructions in the pictures below on how to enroll employees in the clock. ==

[[File:ZKTeco_Enrolling_Instructions_Page_1.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_2.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_3.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_4.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_5.jpg]]

ZKTeco Enrolling Instructions

2024-03-22T15:22:54Z

David:

'''''Hello!!! Congratulations on your new clock. Please see the instructions in the pictures below on how to enroll employees in the clock.
'''''

[[File:ZKTeco_Enrolling_Instructions_Page_1.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_2.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_3.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_4.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_5.jpg]]

ZKTeco Enrolling Instructions

2024-03-22T15:21:37Z

David:

'''''***Hello!!! Congratulations on your new clock. Please see the instructions in the pictures below on how to enroll employees in the clock.***
'''''

[[File:ZKTeco_Enrolling_Instructions_Page_1.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_2.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_3.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_4.jpg]]

[[File:ZKTeco_Enrolling_Instructions_Page_5.jpg]]

File:ZKTeco Enrolling Instructions Page 5.jpg

2024-03-22T15:19:06Z

David:

File:ZKTeco Enrolling Instructions Page 4.jpg

2024-03-22T15:18:58Z

David:

File:ZKTeco Enrolling Instructions Page 3.jpg

2024-03-22T15:18:52Z

David:

File:ZKTeco Enrolling Instructions Page 2.jpg

2024-03-22T15:18:44Z

David:

File:ZKTeco Enrolling Instructions Page 1.jpg

2024-03-22T15:18:36Z

David:

ZKTeco Enrolling Instructions

2024-03-22T15:17:52Z

David: Created page with "Hello!!! Congratulations on your new clock. Please see the instructions in the pictures below on how to enroll employees in the clock. File:Example.jpg"

Hello!!! Congratulations on your new clock. Please see the instructions in the pictures below on how to enroll employees in the clock.

[[File:Example.jpg]]

HandPunch Enrollment

2021-09-01T12:59:55Z

David:

[[image:HandPunch.png|right]]

== Preparation ==

Here are a few guidelines to help you prepare for an enrollment session.

* You can enroll one person or a group of people during an enrollment session.
* Each user must have a unique personal identification (clock ID) number. It will save you considerable time if you assign the ID numbers in advance.
* The HandPunch will not accept two people with the same ID number.
* If you enroll people using the last four digits of their phone numbers or social security numbers, you may get duplicate numbers.

=If you have any questions on the enrollment or anything in this document, please call 914-777-2121 x3.=

== Enrolling ==

To enroll an employee you need to access the supervisor menu.

# From the main screen, which says ('''ENTER ID'''), press Clear '''THEN''' Enter. ('''NOT''' Clear and Enter at the same time)
# If you see '''ENTER PASSWORD''' in the display then there are no users currently enrolled in the HandPunch. You will first need to enroll yourself. Skip to step #7.
# You should see a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your Clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display. If you want to add an employee and NOT add a user that needs to enroll other people then answer Yes (#). If you are the first person being enrolled, or you want to enroll someone that will be enrolling other people, then answer No (*) and answer the next question ('''ADD SUPERVISOR''') with Yes (*).
# Enter in the clock ID of the person you are enrolling and press Enter. If you see '''SORRY CAN'T ADD''' in the display, the clock ID is already being used.
# You will see '''PLACE HAND''' in the display. The person being enrolled places their hand and the display shows '''REMOVE HAND'''. The person being enrolled will need to place and remove their hand 3 times to complete the enrollment.
# The display will return to the question ('''ADD EMPLOYEE''' / '''ADD SUPERVISOR'''). To get from the '''ADD SUPERVISOR''' menu to the '''ADD EMPLOYEE''' menu, press No (*) twice.
# Press Clear to exit from the supervisor menu.

==Un-Enrolling & Re-Enrolling==

To re-enroll a person, you first need to remove them from the HandPunch.

# From the main screen, which says ('''ENTER ID'''), press Clear then Enter.
# You should be a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display.
# Answer No (*) twice.
# You will see '''REMOVE USER''' in the display.
# Answer Yes (#).
# You will see '''REMOVE ID''' # in the display.
# Enter the clock ID of the person you wish to remove and press Enter. *IMPORTANT* - do NOT enter your clock ID.
# You will see '''USER REMOVED''' in the screen briefly and then the display will return to '''REMOVE ID #'''.
# If you have another person that you want to remove then enter their clock ID, otherwise press Clear to get back to the '''REMOVE USER''' menu.
# Press No (*) and you will be at the '''ADD EMPLOYEE''' menu. You can now enroll the people that you removed.

== Employee Education ==
The HandPunch is easy to use and non-threatening. However, most people have never used a biometric HandPunch.
Training employees on how the HandPunch works and how to use it will eliminate most fears and concerns before they occur. Inform the employees of these facts.

* The HandPunch reads the shape of the hand, not the fingerprints or palm prints.
* It does not identify people, it confirms identity.
* It scans with an invisible light of the type used in TV remote controls.
* It does not transfer germs any more than a doorknob or money.
* It does not invade privacy; it guarantees it.
* The enrollment process requires three or more reads to collect enough information to create a template.

== Proper Hand Placement ==

For correct and consistent hand reads, it is very important that your hand is placed on the platen in the same manner every time.
The following rules apply for proper hand placement on the platen.

* If you are wearing a ring, rotate the ring so the stone faces up in its normal position.
* Slide your right hand onto the platen rather like an airplane landing at the airport.
* Slide your hand forward until the web between your index and middle finger stops against the web pin.
* Keep your hand flat. You should feel the surface of the platen on your palm and the underside of your fingers.
* Close your fingers together until they touch the finger pins and watch the hand diagram light display on the top panel. See image below.
* The lights go out when you have properly placed your fingers. If a light remains on, a finger is not in proper contact with its finger pin.

[[File:Hand Placement.png]]

== Left Hand Enrollment ==

Some right hands cannot be used in the HandPunch due to disabilities such as missing fingers. You can enroll a user with the left hand facing palm side up.
The techniques for left hand enrollment are the same as for standard enrollment. The user should keep the back of the hand flat against the platen and move
the fingers against the web pin and the finger pins in the same manner as in standard enrollment. Users enrolled with the left hand must always verify with the left hand.
Extra practice on placing the hand on the platen may be required to ensure correct, consistent hand reads.

== Simple Troubleshooting ==

* Correct hand placement is critical to successful enrollment and punching. The hand should be placed flat on the platen, with the fingers touching the pins. If a red light is lit, then the person being enrolled is not touching that pin with their finger.
* The wrist should be visible when punching. If the wrist is not visible then clothing might block the camera from successfully scanning the hand.
* The HandPunch needs to be kept clean. See [[HandPunch Maintenance]] for maintenance and cleaning instructions.

== See also ==

* [[HandPunch]]
* [[HandPunch Maintenance]]
* [[HandPunch Troubleshooting]]

HandPunch Enrollment

2021-07-27T16:15:02Z

David:

[[image:HandPunch.png|right]]

== Preparation ==

Here are a few guidelines to help you prepare for an enrollment session.

* You can enroll one person or a group of people during an enrollment session.
* Each user must have a unique personal identification (clock ID) number. It will save you considerable time if you assign the ID numbers in advance.
* The HandPunch will not accept two people with the same ID number.
* If you enroll people using the last four digits of their phone numbers or social security numbers, you may get duplicate numbers.

='''If you have any questions on the enrollment or anything in this document, please call 914-777-2121 x3.'''''=

== Enrolling ==

To enroll an employee you need to access the supervisor menu.

# From the main screen, which says ('''ENTER ID'''), press Clear '''THEN''' Enter. ('''NOT''' Clear and Enter at the same time)
# If you see '''ENTER PASSWORD''' in the display then there are no users currently enrolled in the HandPunch. You will first need to enroll yourself. Skip to step #7.
# You should see a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your Clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display. If you want to add an employee and NOT add a user that needs to enroll other people then answer Yes (#). If you are the first person being enrolled, or you want to enroll someone that will be enrolling other people, then answer No (*) and answer the next question ('''ADD SUPERVISOR''') with Yes (*).
# Enter in the clock ID of the person you are enrolling and press Enter. If you see '''SORRY CAN'T ADD''' in the display, the clock ID is already being used.
# You will see '''PLACE HAND''' in the display. The person being enrolled places their hand and the display shows '''REMOVE HAND'''. The person being enrolled will need to place and remove their hand 3 times to complete the enrollment.
# The display will return to the question ('''ADD EMPLOYEE''' / '''ADD SUPERVISOR'''). To get from the '''ADD SUPERVISOR''' menu to the '''ADD EMPLOYEE''' menu, press No (*) twice.
# Press Clear to exit from the supervisor menu.

==Un-Enrolling & Re-Enrolling==

To re-enroll a person, you first need to remove them from the HandPunch.

# From the main screen, which says ('''ENTER ID'''), press Clear then Enter.
# You should be a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display.
# Answer No (*) twice.
# You will see '''REMOVE USER''' in the display.
# Answer Yes (#).
# You will see '''REMOVE ID''' # in the display.
# Enter the clock ID of the person you wish to remove and press Enter. *IMPORTANT* - do NOT enter your clock ID.
# You will see '''USER REMOVED''' in the screen briefly and then the display will return to '''REMOVE ID #'''.
# If you have another person that you want to remove then enter their clock ID, otherwise press Clear to get back to the '''REMOVE USER''' menu.
# Press No (*) and you will be at the '''ADD EMPLOYEE''' menu. You can now enroll the people that you removed.

== Employee Education ==
The HandPunch is easy to use and non-threatening. However, most people have never used a biometric HandPunch.
Training employees on how the HandPunch works and how to use it will eliminate most fears and concerns before they occur. Inform the employees of these facts.

* The HandPunch reads the shape of the hand, not the fingerprints or palm prints.
* It does not identify people, it confirms identity.
* It scans with an invisible light of the type used in TV remote controls.
* It does not transfer germs any more than a doorknob or money.
* It does not invade privacy; it guarantees it.
* The enrollment process requires three or more reads to collect enough information to create a template.

== Proper Hand Placement ==

For correct and consistent hand reads, it is very important that your hand is placed on the platen in the same manner every time.
The following rules apply for proper hand placement on the platen.

* If you are wearing a ring, rotate the ring so the stone faces up in its normal position.
* Slide your right hand onto the platen rather like an airplane landing at the airport.
* Slide your hand forward until the web between your index and middle finger stops against the web pin.
* Keep your hand flat. You should feel the surface of the platen on your palm and the underside of your fingers.
* Close your fingers together until they touch the finger pins and watch the hand diagram light display on the top panel. See image below.
* The lights go out when you have properly placed your fingers. If a light remains on, a finger is not in proper contact with its finger pin.

[[File:Hand Placement.png]]

== Left Hand Enrollment ==

Some right hands cannot be used in the HandPunch due to disabilities such as missing fingers. You can enroll a user with the left hand facing palm side up.
The techniques for left hand enrollment are the same as for standard enrollment. The user should keep the back of the hand flat against the platen and move
the fingers against the web pin and the finger pins in the same manner as in standard enrollment. Users enrolled with the left hand must always verify with the left hand.
Extra practice on placing the hand on the platen may be required to ensure correct, consistent hand reads.

== Simple Troubleshooting ==

* Correct hand placement is critical to successful enrollment and punching. The hand should be placed flat on the platen, with the fingers touching the pins. If a red light is lit, then the person being enrolled is not touching that pin with their finger.
* The wrist should be visible when punching. If the wrist is not visible then clothing might block the camera from successfully scanning the hand.
* The HandPunch needs to be kept clean. See [[HandPunch Maintenance]] for maintenance and cleaning instructions.

== See also ==

* [[HandPunch]]
* [[HandPunch Maintenance]]
* [[HandPunch Troubleshooting]]

HandPunch Enrollment

2021-07-27T16:14:07Z

David:

[[image:HandPunch.png|right]]

== Preparation ==

Here are a few guidelines to help you prepare for an enrollment session.

* You can enroll one person or a group of people during an enrollment session.
* Each user must have a unique personal identification (clock ID) number. It will save you considerable time if you assign the ID numbers in advance.
* The HandPunch will not accept two people with the same ID number.
* If you enroll people using the last four digits of their phone numbers or social security numbers, you may get duplicate numbers.

='''* If you have any questions on the enrollment or anything in this document, please call 914-777-2121 x3.'''''=

== Enrolling ==

To enroll an employee you need to access the supervisor menu.

# From the main screen, which says ('''ENTER ID'''), press Clear '''THEN''' Enter. ('''NOT''' Clear and Enter at the same time)
# If you see '''ENTER PASSWORD''' in the display then there are no users currently enrolled in the HandPunch. You will first need to enroll yourself. Skip to step #7.
# You should see a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your Clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display. If you want to add an employee and NOT add a user that needs to enroll other people then answer Yes (#). If you are the first person being enrolled, or you want to enroll someone that will be enrolling other people, then answer No (*) and answer the next question ('''ADD SUPERVISOR''') with Yes (*).
# Enter in the clock ID of the person you are enrolling and press Enter. If you see '''SORRY CAN'T ADD''' in the display, the clock ID is already being used.
# You will see '''PLACE HAND''' in the display. The person being enrolled places their hand and the display shows '''REMOVE HAND'''. The person being enrolled will need to place and remove their hand 3 times to complete the enrollment.
# The display will return to the question ('''ADD EMPLOYEE''' / '''ADD SUPERVISOR'''). To get from the '''ADD SUPERVISOR''' menu to the '''ADD EMPLOYEE''' menu, press No (*) twice.
# Press Clear to exit from the supervisor menu.

==Un-Enrolling & Re-Enrolling==

To re-enroll a person, you first need to remove them from the HandPunch.

# From the main screen, which says ('''ENTER ID'''), press Clear then Enter.
# You should be a star symbol ('''*''') on the bottom line of the display. If you do not then go back to step #1.
# Enter in your clock ID and press Enter.
# The displays shows '''PLACE HAND'''. Place your hand.
# You should see '''ENTER PASSWORD''' in the display.
# The password is the number 4. Press 4 then press Enter.
# You will see '''ADD EMPLOYEE''' in the display.
# Answer No (*) twice.
# You will see '''REMOVE USER''' in the display.
# Answer Yes (#).
# You will see '''REMOVE ID''' # in the display.
# Enter the clock ID of the person you wish to remove and press Enter. *IMPORTANT* - do NOT enter your clock ID.
# You will see '''USER REMOVED''' in the screen briefly and then the display will return to '''REMOVE ID #'''.
# If you have another person that you want to remove then enter their clock ID, otherwise press Clear to get back to the '''REMOVE USER''' menu.
# Press No (*) and you will be at the '''ADD EMPLOYEE''' menu. You can now enroll the people that you removed.

== Employee Education ==
The HandPunch is easy to use and non-threatening. However, most people have never used a biometric HandPunch.
Training employees on how the HandPunch works and how to use it will eliminate most fears and concerns before they occur. Inform the employees of these facts.

* The HandPunch reads the shape of the hand, not the fingerprints or palm prints.
* It does not identify people, it confirms identity.
* It scans with an invisible light of the type used in TV remote controls.
* It does not transfer germs any more than a doorknob or money.
* It does not invade privacy; it guarantees it.
* The enrollment process requires three or more reads to collect enough information to create a template.

== Proper Hand Placement ==

For correct and consistent hand reads, it is very important that your hand is placed on the platen in the same manner every time.
The following rules apply for proper hand placement on the platen.

* If you are wearing a ring, rotate the ring so the stone faces up in its normal position.
* Slide your right hand onto the platen rather like an airplane landing at the airport.
* Slide your hand forward until the web between your index and middle finger stops against the web pin.
* Keep your hand flat. You should feel the surface of the platen on your palm and the underside of your fingers.
* Close your fingers together until they touch the finger pins and watch the hand diagram light display on the top panel. See image below.
* The lights go out when you have properly placed your fingers. If a light remains on, a finger is not in proper contact with its finger pin.

[[File:Hand Placement.png]]

== Left Hand Enrollment ==

Some right hands cannot be used in the HandPunch due to disabilities such as missing fingers. You can enroll a user with the left hand facing palm side up.
The techniques for left hand enrollment are the same as for standard enrollment. The user should keep the back of the hand flat against the platen and move
the fingers against the web pin and the finger pins in the same manner as in standard enrollment. Users enrolled with the left hand must always verify with the left hand.
Extra practice on placing the hand on the platen may be required to ensure correct, consistent hand reads.

== Simple Troubleshooting ==

* Correct hand placement is critical to successful enrollment and punching. The hand should be placed flat on the platen, with the fingers touching the pins. If a red light is lit, then the person being enrolled is not touching that pin with their finger.
* The wrist should be visible when punching. If the wrist is not visible then clothing might block the camera from successfully scanning the hand.
* The HandPunch needs to be kept clean. See [[HandPunch Maintenance]] for maintenance and cleaning instructions.

== See also ==

* [[HandPunch]]
* [[HandPunch Maintenance]]
* [[HandPunch Troubleshooting]]

Schedule Based Restrictions

2020-08-04T14:46:45Z

David:

When Schedule Based Restrictions are turned on, employee schedules are downloaded to the HandPunch to restrict the times that an employee can punch. This can reduce unauthorized overtime as well as early “in” and late “out” punches. An employee’s individual schedule is used to restrict access. A separate schedule is defined for each employee providing the ultimate in flexibility. The software synchronizes with the HandPunch approximately every 5-10 minutes, to provide the HandPunch with the most accurate and live scheduling updates.

By default, the HandPunch will not accept “in” punches earlier than 7 minutes to the start of the schedule and “out” punches after 7 minutes to the end of the schedule. It will If an employee attempts to punch in earlier than 7 minutes, or late out after 7 minutes, they will get an error at the HandPunch which will read, '''“TIME RESTRICTION”'''.

For a fingerprint clock, you will get one of the following three options when trying to punch:

*When an employee goes to a clock and punches in successfully, the screen of the clock will have a green box on it that says Punch Verified and it will have your name, Clock ID, and time that you punched. The clock will also have a voice say "Verified. Thank You"

*When an employee is trying to punch and is restricted, the clock will display an Orange box which will say "Can't clock you in yet" and will also say "You are not authorized to punch at this time". The clock will also have a voice that will say "Previously Verified". This means you are attempting to punch out of your zone and are being restricted.

*If you attempt to punch and you do not have a schedule within 8 hours of when you are trying to punch the clock will display an Orange box which will say "Can't clock you in yet" and will also say "You do not have a schedule for today". The clock will also have a voice that will say "Previously Verified"

If the employee was supposed to be at the facility but their schedule has not been updated yet in the scheduler (i.e. on a weekend), the employee should notify a higher authority, or someone with time card access, of the exact time of their arrival or departure. This person can then add the restricted punch manually on their time card.

To avoid the above scenario, staffing coordinators should make schedule changes in the scheduler as soon as they are aware a change, to minimize time zone restrictions at the clock. Once the employee punches and gets restricted at the clock, their punch will need to be added manually.

Even after an employee’s punch has been restricted, it is a good practice to have the staffing coordinator update the employee’s schedule in the scheduler for accuracy’s sake.

A report can be run to see all punches that have been rejected due to the time zone restriction. This report displays verified punches made at the time clock that were outside of an allowable punching time zone. See image below:

[[File:Ruth.png]]

[[File:TZR.png]]

[[File:Report.png]]

Schedule Based Restrictions

2020-08-03T20:50:03Z

David:

When Schedule Based Restrictions are turned on, employee schedules are downloaded to the HandPunch to restrict the times that an employee can punch. This can reduce unauthorized overtime as well as early “in” and late “out” punches. An employee’s individual schedule is used to restrict access. A separate schedule is defined for each employee providing the ultimate in flexibility. The software synchronizes with the HandPunch approximately every 5-10 minutes, to provide the HandPunch with the most accurate and live scheduling updates.

By default, the HandPunch will not accept “in” punches earlier than 7 minutes to the start of the schedule and “out” punches after 7 minutes to the end of the schedule. It will If an employee attempts to punch in earlier than 7 minutes, or late out after 7 minutes, they will get an error at the HandPunch which will read, '''“TIME RESTRICTION”'''.

For a fingerprint clock, you will get one of the following three options when trying to punch:

*When an employee goes to a clock and punches in successfully, the screen of the clock will have a green box on it that says Punch Verified and it will have your name, Clock ID, and time that you punched. The clock will also have a voice say "Verified. Thank You"

*When an employee is trying to punch and is restricted, the clock will display an Orange box which will say "Can't clock you in yet" and will also say "You are not authorized to punch at this time". The clock will also have a voice that will say "Previously Verified"

*If you attempt to punch and you do not have a schedule within 8 hours of when you are trying to punch the clock will display an Orange box which will say "Can't clock you in yet" and will also say "You do not have a schedule for today". The clock will also have a voice that will say "Previously Verified"

If the employee was supposed to be at the facility but their schedule has not been updated yet in the scheduler (i.e. on a weekend), the employee should notify a higher authority, or someone with time card access, of the exact time of their arrival or departure. This person can then add the restricted punch manually on their time card.

To avoid the above scenario, staffing coordinators should make schedule changes in the scheduler as soon as they are aware a change, to minimize time zone restrictions at the clock. Once the employee punches and gets restricted at the clock, their punch will need to be added manually.

Even after an employee’s punch has been restricted, it is a good practice to have the staffing coordinator update the employee’s schedule in the scheduler for accuracy’s sake.

A report can be run to see all punches that have been rejected due to the time zone restriction. This report displays verified punches made at the time clock that were outside of an allowable punching time zone. See image below:

[[File:Ruth.png]]

[[File:TZR.png]]

[[File:Report.png]]

Internal SekureID Communication

2020-07-10T12:32:27Z

David: /* Review Logs */

This document an internal document for SBV to troubleshoot communication issues with SekureID clocks.

Typically, the client will notify SBV that punches are not showing in the software. Please be aware that a clock could be sending new punches, but there was an issue within the last few days and although the clock has now reconnected, these older punches are not appearing. This issue can also manifest as new employees not appearing in the clock because the clock is sending information but is not receiving information. Before getting the client involved you need to determine if there is (or was) a communication issue. For example, if tasks were not running then punches will not be in the software. Punches could also be unassigned and not on the time cards.

You will be using the SekureID utility and advanced troubleshooting can use SQL Server Management Studio. Avoid using queries that are SELECT * and instead use TOP N where N is the number of records that you need and use ORDER BY so that the information you are looking for appears first.

[[File:sekureidshortcut.png|100px]]

You will always want to select the Company (#1) and the Serial Number (#2) that you are troubleshooting.

[[File:sekureidutility.png|600px]]

==Review Logs==

From the Connection / Time Logs tab, click on Get Latest Punch Received button (#3). This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' ORDER BY LocalPunchDateTime DESC</nowiki>

Another query that can be helpful is:

<nowiki>
SELECT TOP 100 * from TimeLog where SerialNumber = 'serial number' ORDER BY LogID DESC</nowiki>

but when a clock has been reset, the LogID of the latest punch can be less than the highest LogID ever used in that clock.

The punch date and time will be displayed and whether it has been processed by the software. You can also click on Get Latest Processed Punch Received (#4) to see what the latest punch in the software should be. This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' AND Processed = 1 ORDER BY LocalPunchDateTime DESC</nowiki>

If there is a significant time gap between these 2 punches then the software may not be processing the punches. See the Software Not Processing section.

Even if it is confirmed that the latest punch received is the latest punch made on the time clock, you will still check to see when the clock last communicated to the server. Click Get Latest Device Connection Changed Log (#5) and note when this was. Now click Request Connection Status From Single Clock (#6), wait a few seconds, then click Get Latest Device Connection Changed Log (#5) again. If the clock displays a log that indicates that it was just created and the value is true then the clock is communicating and responding. Refer to the Resend Time Logs section as the clock is communicating but the punches are not up to date. If there was no change from the first and second log, or the logs always have a false value then the clock is not communicating.

The equivalent SQL is:

<nowiki>
SELECT TOP 1 * FROM AdminLog WHERE SerialNumber = 'serial number' AND MessageType = 'DeviceConnectionChanged' ORDER BY CreatedDateTime DESC</nowiki>

==Client Involvement==

Once it is determined that the clock is not communicating and that there are no recent punches, we now need to involve the client.

Ask the client is if there are any X’s on either of the icons in the top right corner of the time clock's main screen. You can refer to this [[Fingerprint_Connection_Issues|page]]. Multiple reboots or removing the power for a few minutes and plugging back in may also need to be done by the client.

If after rebooting there are no X’s, punches will start to upload and you can use the Get Latest Punch Received button to confirm this. There may be a need to resend punches if the clock was offline for a long time. Refer to the Resend Time Logs section.

==Resend Time Logs==

A clock can be instructed to resend punches. This uses the GMT Time and a maximum time span of 24 hours. Punches that are already sent will not be duplicated, but there is nothing to be gained from resending punches that have already been received.

After the client reboots you can look at the TimeLog and determine if new punches are being received. By looking at the LogID and CreatedDateTime columns you can determine if there is a gap in the LogIDs at the point that punches started coming into the software. Using this SQL, scroll down to the records where the new punches were receieved.

<nowiki>
SELECT TOP 1000 * from TimeLog WHERE SerialNumber = 'serial number' ORDER BY LocalPunchDateTime DESC</nowiki>

In this example, there is no gap in the LogIDs.

[[File:PunchesAfterReboot.png]]

Another way to determine if there is a gap is to use the row number and compare the LogID at 2 different places:

In this example, LogID of 26619 is in row number 428. The expectation is that at row number 28, the LogID should be 26619 + 400.

[[File:LogIDCreatedDateTime1.png]]

And scrolling up to row number 28 we see that the LogID is 27019. This confirms that there is no gap from the first TimeLog received after the reboot to the more recent punches made at the time clock.

[[File:LogIDCreatedDateTime2.png]]

==Removing Session from the Hive (Advanced)==

If the admin response is true and resending time logs was unsuccessful then removing the HiveMQ session may resolve the issue. Keep in mind, this is VERY rare and does not happen often so this is a “last result” thing to do. Doing this will not do any harm but shouldn't be done until you have exhausted all other possibilities.

Open a browser on SBV26 and go to http://localhost:8080

Enter the username of "admin" and enter the password of "hivemq".

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question that it asks. Redo the admin and time log steps.

[[File:removesession.png|600px]]

==Final Troubleshooting (Advanced) ==

If after multiple reboots and removing the HiveMQ session, there is still no communication then it could be a firewall issue. You will need to get IT involved. The clocks communicate on port 8883. As the clocks generally use DHCP then any device specific rules will need to use the MAC address which is found under menu / Settings / About device.

==Software Not Processing==

Search for locks using the SQL Server Management Studio on the server that the client's software is located on using the following query;

<nowiki>
SELECT * FROM Lock</nowiki>

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches which makes a clock punch into a punch on the employee's time card.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

<nowiki>
DELETE FROM Lock where PkLockID = "The ID of the lock you want to release"</nowiki>

[[File:deletelock.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”.

==Case Studies==

This is a record of actual communication issues and how they were resolved. These case studies will use 4 markers:
* Local Network / Wifi status on clock - Y = clock shows as connected to the network
* Database icon status on clock - Y means there is NOT an X on the database icon
* Request Status - Y means we are getting a response from the clock
* HiveMQ session - Y means that the session shows as connected

7/2/2020 - New Grove Manor - initial status YNNN - removing disconnected session changed nothing - client rebooted clock - now status is YYYY. All punches came in without needing to resend. Conclusion reached - database shows not connected = HiveMQ disconnected.

7/4/2020 - CareCore at Lima - initial status YYNY - Last punch received 6/28 2:04 PM (LogID 26619) - HiveMQ shows Connected Since 7/1 08:19 - removed session and disconnected client, in both cases the HiveMQ session went back to connected but still no response from the clock - despite sending requests the Offline Message Queue Size was still zero so it looks like messages are being sent and not being received - also tried a company change. Will have them reboot. After reboot all punches came in without any resend required. Conclusion reached - database icon shows connected = HiveMQ connected but Request = false still requires a reboot.

Internal SekureID Communication

2020-07-03T15:52:29Z

David: /* Case Studies */

This document an internal document for SBV to troubleshoot communication issues with SekureID clocks.

Typically, the client will notify SBV that punches are not showing in the software. Please be aware that a clock could be sending new punches, but there was an issue within the last few days and although the clock has now reconnected, these older punches are not appearing. This issue can also manifest as new employees not appearing in the clock because the clock is sending information but is not receiving information. Before getting the client involved you need to determine if there is (or was) a communication issue. For example, if tasks were not running then punches will not be in the software. Punches could also be unassigned and not on the time cards.

You will be using the SekureID utility and advanced troubleshooting can use SQL Server Management Studio. Avoid using queries that are SELECT * and instead use TOP N where N is the number of records that you need and use ORDER BY so that the information you are looking for appears first.

[[File:sekureidshortcut.png|100px]]

You will always want to select the Company (#1) and the Serial Number (#2) that you are troubleshooting.

[[File:sekureidutility.png|600px]]

==Review Logs==

From the Communication / Time Logs tab, click on Get Latest Punch Received button (#3). This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' ORDER BY LocalPunchDateTime DESC</nowiki>

Another query that can be helpful is:

<nowiki>
SELECT TOP 100 * from TimeLog where SerialNumber = 'serial number' ORDER BY LogID DESC</nowiki>

but when a clock has been reset, the LogID of the latest punch can be less than the highest LogID ever used in that clock.

The punch date and time will be displayed and whether it has been processed by the software. You can also click on Get Latest Processed Punch Received (#4) to see what the latest punch in the software should be. This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' AND Processed = 1 ORDER BY LocalPunchDateTime DESC</nowiki>

If there is a significant time gap between these 2 punches then the software may not be processing the punches. See the Software Not Processing section.

Even if it is confirmed that the latest punch received is the latest punch made on the time clock, you will still check to see when the clock last communicated to the server. Click Get Latest Device Connection Changed Log (#5) and note when this was. Now click Request Connection Status From Single Clock (#6), wait a few seconds, then click Get Latest Device Connection Changed Log (#5) again. If the clock displays a log that indicates that it was just created and the value is true then the clock is communicating and responding. Refer to the Resend Time Logs section as the clock is communicating but the punches are not up to date. If there was no change from the first and second log, or the logs always have a false value then the clock is not communicating.

The equivalent SQL is:

<nowiki>
SELECT TOP 1 * FROM AdminLog WHERE SerialNumber = 'serial number' AND MessageType = 'DeviceConnectionChanged' ORDER BY CreatedDateTime DESC</nowiki>

==Client Involvement==

Once it is determined that the clock is not communicating and that there are no recent punches, we now need to involve the client.

Ask the client is if there are any X’s on either of the icons in the top right corner of the time clock's main screen. You can refer to this [[Fingerprint_Connection_Issues|page]]. Multiple reboots or removing the power for a few minutes and plugging back in may also need to be done by the client.

If after rebooting there are no X’s, punches will start to upload and you can use the Get Latest Punch Received button to confirm this. There may be a need to resend punches if the clock was offline for a long time. Refer to the Resend Time Logs section.

==Resend Time Logs==

A clock can be instructed to resend punches. This uses the GMT Time and a maximum time span of 24 hours. Punches that are already sent will not be duplicated.

==Removing Session from the Hive (Advanced)==

If the admin response is true and resending time logs was unsuccessful then removing the HiveMQ session may resolve the issue. Keep in mind, this is VERY rare and does not happen often so this is a “last result” thing to do. Doing this will not do any harm but shouldn't be done until you have exhausted all other possibilities.

Open a browser on SBV26 and go to http://localhost:8080

Enter the username of "admin" and enter the password of "hivemq".

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question that it asks. Redo the admin and time log steps.

[[File:removesession.png|600px]]

==Final Troubleshooting (Advanced) ==

If after multiple reboots and removing the HiveMQ session, there is still no communication then it could be a firewall issue. You will need to get IT involved. The clocks communicate on port 8883. As the clocks generally use DHCP then any device specific rules will need to use the MAC address which is found under menu / Settings / About device.

==Software Not Processing==

Search for locks using the SQL Server Management Studio on the server that the client's software is located on using the following query;

<nowiki>
SELECT * FROM Lock</nowiki>

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches which makes a clock punch into a punch on the employee's time card.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

<nowiki>
DELETE FROM Lock where PkLockID = "The ID of the lock you want to release"</nowiki>

[[File:deletelock.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”.

==Case Studies==

This is a record of actual communication issues and how they were resolved. These case studies will use 4 markers:
* Local Network / Wifi status on clock - Y = clock shows as connected to the network
* Database icon status on clock - Y means there is NOT an X on the database icon
* Request Status - Y means we are getting a response from the clock
* HiveMQ session - Y means that the session shows as connected

7/2/2020 - New Grove Manor - initial status YNNN - removing disconnected session changed nothing - client rebooted clock - now status is YYYY. All punches came in with needing to resend.

Internal SekureID Communication

2020-07-03T14:41:22Z

David:

This document an internal document for SBV to troubleshoot communication issues with SekureID clocks.

Typically, the client will notify SBV that punches are not showing in the software. Please be aware that a clock could be sending new punches, but there was an issue within the last few days and although the clock has now reconnected, these older punches are not appearing. This issue can also manifest as new employees not appearing in the clock because the clock is sending information but is not receiving information. Before getting the client involved you need to determine if there is (or was) a communication issue. For example, if tasks were not running then punches will not be in the software. Punches could also be unassigned and not on the time cards.

You will be using the SekureID utility and advanced troubleshooting can use SQL Server Management Studio. Avoid using queries that are SELECT * and instead use TOP N where N is the number of records that you need and use ORDER BY so that the information you are looking for appears first.

[[File:sekureidshortcut.png|100px]]

You will always want to select the Company (#1) and the Serial Number (#2) that you are troubleshooting.

[[File:sekureidutility.png|600px]]

==Review Logs==

From the Communication / Time Logs tab, click on Get Latest Punch Received button (#3). This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' ORDER BY LocalPunchDateTime DESC</nowiki>

Another query that can be helpful is:

<nowiki>
SELECT TOP 100 * from TimeLog where SerialNumber = 'serial number' ORDER BY LogID DESC</nowiki>

but when a clock has been reset, the LogID of the latest punch can be less than the highest LogID ever used in that clock.

The punch date and time will be displayed and whether it has been processed by the software. You can also click on Get Latest Processed Punch Received (#4) to see what the latest punch in the software should be. This is equivalent to this SQL:

<nowiki>
SELECT TOP 1 * from TimeLog where SerialNumber = 'serial number' AND Processed = 1 ORDER BY LocalPunchDateTime DESC</nowiki>

If there is a significant time gap between these 2 punches then the software may not be processing the punches. See the Software Not Processing section.

Even if it is confirmed that the latest punch received is the latest punch made on the time clock, you will still check to see when the clock last communicated to the server. Click Get Latest Device Connection Changed Log (#5) and note when this was. Now click Request Connection Status From Single Clock (#6), wait a few seconds, then click Get Latest Device Connection Changed Log (#5) again. If the clock displays a log that indicates that it was just created and the value is true then the clock is communicating and responding. Refer to the Resend Time Logs section as the clock is communicating but the punches are not up to date. If there was no change from the first and second log, or the logs always have a false value then the clock is not communicating.

The equivalent SQL is:

<nowiki>
SELECT TOP 1 * FROM AdminLog WHERE SerialNumber = 'serial number' AND MessageType = 'DeviceConnectionChanged' ORDER BY CreatedDateTime DESC</nowiki>

==Client Involvement==

Once it is determined that the clock is not communicating and that there are no recent punches, we now need to involve the client.

Ask the client is if there are any X’s on either of the icons in the top right corner of the time clock's main screen. You can refer to this [[Fingerprint_Connection_Issues|page]]. Multiple reboots or removing the power for a few minutes and plugging back in may also need to be done by the client.

If after rebooting there are no X’s, punches will start to upload and you can use the Get Latest Punch Received button to confirm this. There may be a need to resend punches if the clock was offline for a long time. Refer to the Resend Time Logs section.

==Resend Time Logs==

A clock can be instructed to resend punches. This uses the GMT Time and a maximum time span of 24 hours. Punches that are already sent will not be duplicated.

==Removing Session from the Hive (Advanced)==

If the admin response is true and resending time logs was unsuccessful then removing the HiveMQ session may resolve the issue. Keep in mind, this is VERY rare and does not happen often so this is a “last result” thing to do. Doing this will not do any harm but shouldn't be done until you have exhausted all other possibilities.

Open a browser on SBV26 and go to http://localhost:8080

Enter the username of "admin" and enter the password of "hivemq".

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question that it asks. Redo the admin and time log steps.

[[File:removesession.png|600px]]

==Final Troubleshooting (Advanced) ==

If after multiple reboots and removing the HiveMQ session, there is still no communication then it could be a firewall issue. You will need to get IT involved. The clocks communicate on port 8883. As the clocks generally use DHCP then any device specific rules will need to use the MAC address which is found under menu / Settings / About device.

==Software Not Processing==

Search for locks using the SQL Server Management Studio on the server that the client's software is located on using the following query;

<nowiki>
SELECT * FROM Lock</nowiki>

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches which makes a clock punch into a punch on the employee's time card.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

<nowiki>
DELETE FROM Lock where PkLockID = "The ID of the lock you want to release"</nowiki>

[[File:deletelock.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”.

==Case Studies==

These is a record of actual communication issues and how they were resolved. These case studies will use 4 markers:
* Local Network / Wifi status on clock - Y = clock shows as connected to the network
* Database icon status on clock - Y means there is NOT an X on the database icon
* Request Status - Y means we are getting a response from the clock
* HiveMQ session - Y means that the session shows as connected

7/2/2020 - New Grove Manor - initial status YNNN - removing disconnected session changed nothing - client rebooted clock - now status is YYYY. All punches came in with needing to resend.

Internal SekureID Communication

2020-05-25T20:01:06Z

David:

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

==Testing Communication on SBV 26==

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

[[File:adminlog.png|1000px]]

==Releasing a Lock==

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

==Removing Session from the Hive==

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

==Further Troubleshooting==

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:57:12Z

David:

Internal SekureID Communication

2020-05-25T19:56:51Z

David:

=Internal SekureID Communication=

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

==Testing Communication on SBV 26==

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

[[File:adminlog.png|1000px]]

==Releasing a Lock==

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

==Removing Session from the Hive==

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

==Further Troubleshooting==

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:37:08Z

David:

=Internal SekureID Communication=

==Testing Communication on SBV 26==

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

[[File:adminlog.png|1000px]]

==Releasing a Lock==

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

==Removing Session from the Hive==

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

==Further Troubleshooting==

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:34:50Z

David:

=Internal SekureID Communication=

==Testing Communication on SBV 26==

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

[[File:adminlog.png|1000px]]

==Releasing a Lock==

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

==Removing Session from the Hive==

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:30:20Z

David:

==Testing Communication on SBV 26==

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

[[File:adminlog.png|1000px]]

==Releasing a Lock==

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

==Removing Session from the Hive==

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:23:30Z

David:

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

----

[[File:adminlog.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

----

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:23:06Z

David:

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = Type serial number of the clock you chose in step 2 order by LogID desc'''

----

[[File:adminlog.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

----

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:22:47Z

David:

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

'''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = '''Type serial number of the clock you chose in step 2''' order by LogID desc'''

----

[[File:adminlog.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

----

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

Internal SekureID Communication

2020-05-25T19:15:00Z

David:

This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks.

When the client says there aren’t punches in the software - The first thing to ask the client is if there are any X’s on either of the icons in the top right corner of the main screen. If they say Yes, you need to tell them to reboot the clock. In order to reboot the clock, if there are supervisors set, the one rebooting will have to be a supervisor. The proper way to do this is by telling them to go to click on the three dashes in the top left corner of the main screen and then going into the Settings menu of the clock and at the bottom of the options under Settings, you will see one that says Reboot. Click on that and then click Yes when the clock asks. Once rebooted confirm there are no X’s on either of the two icons. If there are still X’s, have them pull the power to the clock and then plug it back in. If there are still X’s on any of the icons, see the section at the bottom to further troubleshoot.

If there are no X’s, punches should be coming in at the next synching period, but we can double check that everything is good by checking communication on SBV 26.

We test for response from the clock by going onto SBV 26 and using the Sekure ID Client utility (found on the desktop). Once you have the utility open, select the company from the Company Code list, and the clock’s Serial Number. Under the Connection/Time Logs tab, click the Request Connection Status From Single Clock button.

[[File:sekureidshortcut.png|100px]]

[[File:sekureidutility.png|600px]]

Once clicked, open up SQL and run or copy and paste the query below:

''''''select * from AdminLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by CreatedDateTime desc'''

This will order all of the most current communication with that clock at the top of the results. Check the column called CreatedDateTime to confirm that the most recent result is the one you just prompted via the SekureID utility.

If response is True:
Check for latest punches from the clock’s TimeLog (by copying and pasting the query below) and look at the Processed column.

'''select * from TimeLog where SerialNumber = 'Type serial number of the clock you chose in step 2' order by LogID desc'''

----

[[File:adminlog.png|600px]]

If we have latest punches and they are processed then there is no issue – we give client an example “We see punches, e.g. # 12345, is there a specific employee that you do not see punches for?” as it could be that they didn’t check since the punches came in.

If we have latest punches and they are not processed (there is a ‘0’ under the Processed column) then resolution is in the software, e.g. lock on processing, or lock on employee – “the clock is communicating successfully. The punches had not been processed onto the time cards”

Search for locks using the SQL Server on the server that the clients TA software is located on using the query;

'''select * from lock'''

[[File:sqllock.png|600px]]

In the column that says LockableObjectType, you will have two types of numbers. One will be 134 and one will be 10. The 134 means that someone, either the automatic polling or a user is polling the one or multiple time clocks. The 10 is the task that processes the punches.

Look at the LockDateTime column to see when the lock was actually taken. If it was within the last few minutes then chances are it is the automatic polling and processing from the task scheduler. If it was more than a few hours ago then it could be when the software doing the overnight task it lost connection or communication to the clock and it created a lock which holds for about 12 hours. In order to release this lock you can copy and paste the query below into SQL.

'''Delete from lock where pklockID = ‘The ID of the lock you want to release’'''

[[File:deletelock.png|600px]]

----

If we do not have punches in the TimeLog, but we have True response, then you can go to the Hive on SBV 26 and clear the session to see if this kickstarts the punches to come in. keep in mind, this is VERY rare and does not happen often so this should be more a “last result” type of thing. Doing this will not do any harm but shouldn't be done unless needed to.

Go to the internet on SBV 26, and type into the internet,

http://localhost:8080/

Type in the username, admin, and the password is hivemq. All lowercase.

Click on Clients on the left-hand side of the page and under Client ID, type in the serial number of the clock you are having an issue with.

[[File:hive.png|600px]]

Once you have the client open, you will see an option that says Remove Session. Click on that and click Yes to the question it asks and then go back to the SQL and run the AdminLog and PunchLog again and see if anything is coming in.

[[File:removesession.png|600px]]

If after a reboot they still have an X on the network icon and database icon, then you should probably have their IT contact us and we can work with them to get it connected properly.

If after the reboot you have a good network icon, but no database connection, then you can try doing the Hive session in the instructions above or have their IT contact us to see if there are any firewall issues/restrictions.

File:Removesession.png

2020-05-25T18:56:29Z

David:

File:Hive.png

2020-05-25T18:56:21Z

David:

File:Deletelock.png

2020-05-25T18:56:10Z

David:

File:Sqllock.png

2020-05-25T18:55:57Z

David:

File:Adminlog.png

2020-05-25T18:55:41Z

David:

File:Sekureidutility.png

2020-05-25T18:55:28Z

David:

File:Sekureidshortcut.png

2020-05-25T18:55:14Z

David:

Internal SekureID Communication

2020-05-25T18:54:53Z

David: Created page with "This document is an internal document for the staff at SBV to be able to fix any issues in regard to communication with SekureID clocks. When the client says there aren’t p..."

Fingerprint Connection Issues

2020-05-25T18:50:31Z

David:

You may find that punches have not come into the software. This could be because the clock is not connected to the network properly. For reference, the three icons below explain to you what each icon is and when calling SBV for troubleshooting, please let them know which icon you have an "X" on.

[[File:databaseicon.png|50px]] - This is the database icon.

[[File:wifiicon.png|50px]] - This is the WiFi icon. It means you are using WiFi to connect instead of a physical network cable.

[[File:wiredicon.png|50px]] - This is the wired icon. It means that you are using a physical network cable to connect instead of WiFi.

In order for the punches to come into the Time and Attendance software, the clock must be connected to the network via a physical network cable or WiFi (Ethernet cable is preferred). If it is connected properly, then on the top right corner of the main screen, there should NOT be any "X"s on either of the two icons and should look like this:

[[File:MainScreen.jpg|400px]]

Or

[[File:ethernet.jpg|400px]]

If the left icon does NOT have an "X" and the right one does, it would be best to Reboot the clock. To do this, go into the Settings menu of the clock (You may need a time clock supervisor to do this), and scroll down the bottom of the list and there will be an option to Reboot. Click it, and then select Yes on the screen. Once rebooted and back to the main screen, there should not be any "X"s on either of the icons.

If there are "X"s on both icons like this:

[[File:noconnection.jpg|400px]]

This means that the method of communication, either WiFi or physical cable, is not connected properly.

For WiFi connections, make sure in the wireless network list in Settings that you have selected says "Connected" otherwise you did not enter the password for that network correctly.

For physical connections, make sure that the cable is a good cable.( You can test this by plugging that cable into another device such as a Laptop or desktop computer)

File:Wiredicon.png

2020-05-25T18:46:14Z

David:

File:Wifiicon.png

2020-05-25T18:46:06Z

David:

File:Databaseicon.png

2020-05-25T18:45:49Z

David:

Scheduling Training

2020-02-13T21:32:31Z

David:

There are three steps to the scheduling process. Whatever type of scheduling period you use, whether it’s monthly, four weeks, or eight weeks, the steps that you are about to learn is the same for EACH scheduling period and you should do these steps in this order before building the schedules for every scheduling period moving forward.

=Step 1=

==Schedule Patterns==

Schedule patterns (Master Schedule) is where you can input any recurring pattern that your staff works. You can do this by clicking on an employee and going to the Employee -> Scheduling -> Schedule Pattern tab.

[[File:Schedule_Pattern_Tab.png]]

* For example, if you do 4 week scheduling and someone works the same schedule in weeks 1 and 3, and the same schedule in weeks 2 and week 4, then all you need to do is give the employee 2 schedule pattern weeks.
* If you have a 4 week scheduling period and someone works the exact same schedule every single week of the 4 week scheduling period, then all you need to do is give them a 1 week pattern.
* If you have a 4 week scheduling period and someone works a different schedule every single week of a 4 week scheduling period then they will need to have a 4 week schedule pattern.

[[File:Week_2.png]]

* Part of giving a schedule pattern to someone is to choose the floor for that schedule. If you know that the employee will be working the SAME floor for EVERY schedule, then you can Home them on that floor by selecting the homing button and choosing the floor from the labor levels dialog box that pops up.(See Picture A) Alternatively, you can choose each floor manually, but this will take longer. (See Picture B)

(A)
[[File:Homing_Button.png]]

(B)
[[File:Alternativly_choosing_Floor.png]]

* If you have someone who is scheduled to work a double shift, you can enter this in the schedule patterns. First assign the regular shift as you normally would. Then, on any other day in the same week that does not have a schedule, choose the day and change it to the day you want the employee to have a double.(See Picture A) Once the day is changed, give them the second half of the double and you will see that there will be two options of the same day.(See Picture B) One with the first half of the double shift and one with the second half. (See Picture C)

(A)
[[File:Double_Choosing_Day_1.png]]

(B)
[[File:Double_Choosing_Schedule_2.png]]

(C)
[[File:Double_Choosing_Schedule_3.png]]

* If you would like to clear out all the schedule patterns for a specific employee and start from scratch you can use the Delete All button. This will clear out all schedule patterns for the employee that you choose.

[[File:Delete_All.png]]

==Planned Absences==

Once you are done putting in all the schedule patterns for all the regularly scheduled staff, you then move onto planned absences.
Planned absences is where you can put someone on vacation, FMLA, etc., '''BEFORE''' you build your schedules. That way, when you do build your schedules, the software will automatically take the employee off on the days that they have set schedules and make those schedules available for someone else to take.

* You do this by going to the Employee -> Scheduling -> Planned Absences tab and choosing the first day that they are '''AWAY''' and the last day that they are '''AWAY''', choose a reason why from the Status drop down list and click "Add to Planned Absences." If you need to add more placeholders to the list you can do this by contacting SBV support.

[[File:Planned_Absences.png]]

Please note – if you add planned absences after the Schedule Period is built, it won’t be reflected in the scheduler. If an employee informs you of an absence after the build, you can either:
* Unschedule the employee from the applicable shifts in the scheduler
* Use the regenerate function

=Step 2=

The goal of this step is to have both of the following reports empty before moving onto step three.
Once you are done inputting all the schedule patterns and planned absences, you are ready to move onto the next step which is running two reports. Both reports should be ran for the NEXT (specific) scheduler period.

==Schedule Patterns without Budget==

* The first report that you need to run is called "Schedule Patterns without Budget." This can be found by going to Reports -> Scheduling -> Schedule Patterns without Budget. If there are any entries when running this report it means that you gave someone a schedule pattern that you don’t have a budget for. For example, generally, C.N.A.’s work on specific floors while unit managers or supervisors work the house or all floors. So when the client puts a C.N.A. on the house floor and that isn’t part of the budget, it will show up on this report. Another reason for entries on this report is if information is missing. Make sure all schedules that were given to employees have floors/units. If there are any changes that need to be made to the budget please contact SBV support.

[[File:Schedule_Patterns_without_Budget.png]]

==Budget vs. Schedule Patterns (Over Budget Monthly)==

* The second report that you need to run is called "Budget vs. Schedule Patterns (Over Budget Monthly)." This can be found by going to Reports -> Scheduling -> Budget vs. Schedule Patterns (Over Budget Monthly). If there are any entries on this report it will mean that on that specific day, shift, budget group, and floor you have scheduled too many people. There are three common scenarios that would cause these entries on the report.

* The first possibility is that there is a specific employee with a schedule that doesn’t work at your facility anymore. To fix this, go to the employees’ schedule pattern tab and delete all the schedules that they have.

* Another possibility is that they do still work at the facility, but they are given a schedule that you have too many people working that schedule. To fix this, move the employee to a schedule that you are currently under budget for. To see where you are under budget, go to Reports -> Scheduling -> Budget vs. Schedule Patterns (Under Budget Monthly). Make sure to run it for the identical dates that the Over Budget Monthly report is being run for. The Under Budget Monthly report will give you the available schedules and the amounts of positions open to be given to employees.

* The last reason entries would be on this report is because the budget is incorrect. If that is the case, please contact SBV support. Bear in mind, the budget is set and confirmed before we start the scheduling process so in most cases this is not the reason for entries on the report.

[[File:Budget_vs_Schedule_Patterns_(Over_Budget_Monthly).png]]

=Step 3=

==Building the Schedules==

Once both reports come back clean, you are then ready to build your schedules. Follow the steps below to build your schedules.
* Click on Scheduler -> Build Schedules and then a small window will pop up when you click “build schedules”

[[File:Build_Schedules_1.png]]

* Maximize that window and you will see all of your budget groups that you are going to be building.
* Make sure you double check that the build date and end date columns reflect the scheduling period that you want to build for.
* Confirm that it’s correct, then click on the TOP MOST check box (see picture) which will then select all the budgets below.
* With the budgets checked off, click build schedules.

[[File:BuildSchedulesButton.png]]

* Once you select this button you will no longer be able to move out of that window. In the status tab for all the budget groups, you will see it go through a series of steps. This is the software building the schedules.
* Once it is done, the close button will then become available on the bottom, and the build date would move forward to the next build.

[[File:Build_Schedules_2.png]]

Make sure NOT to select the Build Schedules button again because this will cause the software to build an additional scheduler period which isn’t recommended. If you do, the only way to delete out a scheduling period that was built by accident is to contact SBV Support.

=Using The Scheduler=

You can read the section below as well as watching the video in the link below. Both will give you explanations on how to properly use the scheduler.

[https://www.youtube.com/watch?v=W8JUR89r5Eo&t= How to Use the Scheduler]

'''Date Range'''

The date range group provides a drop down of the scheduler period dates. Select from the drop down to fill in the start and end dates. Change these dates before clicking on the Display Schedules command to work with a different date range.

[[image:SchedulerGrid.png]]

Make the day-to-day schedule changes in the scheduler grid. The scheduler grid allows the user to move schedules between employees or to/from the available schedules.

Cell color, text and text color help provide maximum schedule information while using the minimum amount of space. Hovering over a cell will provide more detailed information like schedule start and end times, labor levels, schedule history and punch information.

'''Scheduler Groups'''

The employees and the available schedules are grouped by their respective scheduler group. You can filter or collapse the scheduler groups.

Filtering the groups:

[[image:SchedulerGroupFiltering.png]]

Collapsing the groups:

[[image:SchedulerGroupCollapse.png]]

The filtering, collapsing and expanding of the scheduler groups applies to both the employee and the available's grid.

'''Schedule and Placeholder Display'''

Weekly schedule totals display and can be used to sort the employees (those with less schedules listed first).

[[image:SchedulerWeeklyTotals.png]]

'''Employee Display'''

Employee information displays in columns that can be filtered. Additionally, employee information needed only for filtering, displays above the column headers at the top of the scheduler grid.

[[image:SchedulerEmployeeFields.png]]

In the above screen shot, the department field filter is shown. Employees can be filtered by Name, Shift Count, and Company.

'''Context Menu'''

The right click menu provides management of the schedules and placeholders, and access to reports. When applicable, menu selections are provided for multiple days and/or multiple employees. For example, the Monthly Schedule for Employee report is available for all selected employees.

[[image:SchedulerEmployeeContextMenu.png]]

'''Sorting'''

Employees can be sorted by:

Employee Name – the default sorting, alphabetically by their name.

Employee ID – sorted by the employee’s ID.

Seniority – sorted by date of hire.

Weekly Shift Count – sorted by the total schedule count in the selected week.

[[image:SchedulerSortOrder.png]]

'''Available Schedules'''

The available are grouped to provide a clear visual distinction between availables from different shifts and floors. The number in the cell represents the count of the available schedules. If the text color is white, then you are over budget on the shift and floor.

[[image:SchedulerAvailables.png]]

'''Find and Filter'''

[[image:SchedulerFindAndFilter.png]]

The Filter button is like the Filter Row in the employee list on the main screen. Only employees that match part of the filter text will display. Pressing Enter keeps the currently shown employees visible while newly found employees are displayed.

Here is the result of entering Smith, clicking Filter, entering Brown and pressing Enter.

[[image:SchedulerFilterThenFind.png]]

Shift and floor filtering is available from the 2 drop downs. The Filter Availables option will apply the same shift and floor filtering to the availables. Here is a screen shot of the availables filtered to floor 2.

[[image:SchedulerAvailablesFiltering.png]]

Include Home Shift applies when using shift filtering and will include employees that are homed in the filtered shift, although they do not have any schedules.

With Placeholders Only filters the scheduler screen to employees that have one or more schedule placeholders.

'''Tool Tips'''

There is an employee tool tip and the schedule / placeholder tool tip.

The employee tool tip displays additional information about the employee.

[[image:SchedulerEmployeeToolTip.png]]

The schedule / placeholder tool tip displays detail on the schedule / placeholder and punch information for the day.

[[image:SchedulerScheduleToolTip.png]]

'''Employees Crossing Budget Groups'''

Employees with schedules that cross a budget group, when the budget groups are not displayed together (e.g. RNs and LPNs) will display twice and with the correct counting of schedules for the group.

An RN supervisor works a floor nurse position. The totals are correct.

[[image:SchedulerCrossBudgetGroup.png]]

==Scheduler Grid Editing==

The scheduler grid allows you to manage the schedules assigned to the employees, restricted only by the authorizations of the user. Examples are:

* Move one or more schedules from one employee to another employee

* Move one or more schedules from the availables to an employee

* Move one or more schedules from an employee to the availables

* Add a schedule

* Add or delete placeholders

'''Moving Schedules'''

Schedule moves are a 2-part process. Schedules you are taking “from” (either an employee or the availables) and then giving “to” (either an employee or the availables).

After selecting the “from” schedule(s), press the F key. The selected cells have a red border to indicate that you are in the middle of a from/to action.

[[image:SchedulerFromAvailables.png]]

You can only select a single employee’s schedules (i.e. from the same row). Available schedules can be selected from different shifts and floors (i.e. different rows). Select cells that are not adjacent to each other using the Ctrl key.

Select the receiving employee (known as the “to” employee) from any of their cells and press the T key.

In the screen shot below, the schedules from the 25th and the 27th will move to the employee even though the cell from the 26th is the selected cell. Note: you cannot move schedules from one pay date to a different pay date.

[[image:SchedulerFromTo.png]]

Move schedules from an employee to the availables with the single keystroke of U.

'''Swapping Schedules'''

Schedule swapping occurs when the receiving employee already has a schedule in the same shift. The employee(s) keep their schedule start and end times.

You can combine swaps and moves at the same time.

[[image:SchedulerGiveAndSwap1.png]]

The two available schedules on the 5th floor are given to an employee. The 25th is an “available to employee” while the 26th is a schedule swap.

[[image:SchedulerGiveAndSwap2.png]]

'''Multiple Schedules in a Pay Date'''

If an employee has more than one schedule in a pay date, then you must provide the schedule number to take “from” this employee. The top left schedule is number 1 and the bottom right schedule is number 2. If there are 3 schedules, then they are numbered 1 to 3 from top to bottom. These alternate keys represent the keystroke and number combinations:

R = T and 1

E = T and 2

W = T and 3

I = U + 1

J = U + 2

K = U + 3

If you do not indicate the schedule number, the software will prompt you.

'''Placeholders'''

Add or edit placeholders for multiple days by selecting cells and using the [ Schedule Status Type] shortcut (Shift + Key).

'''Scheduler Type'''

Use the scheduler type for categorizing a schedule. The default scheduler type is Standard. Other scheduler types are Orientation, Light Duty and Make Up. Categorize schedules to provide indicators on the staffing reports. Pressing S, O, L or M on a selected schedule changes the scheduler type between Standard, Orientation, Light Duty and Make Up. The displayed text underlines for all scheduler types except Standard. Additionally, the text color can be configured for each scheduler type (Standard is always black).

'''Other'''

''Monthly Mode''

Make changes in the scheduler in Daily or Monthly mode.

Monthly mode changes are not considered to be a schedule change. Two employees swapping schedules is a typical example of a monthly change. Monthly mode changes do not add to the schedule history.

Daily changes are changes that occur on the "day of," and changes that you do before posting the schedule where you want the employee to have a placeholder, and/or the schedule to maintain history. Examples are a sick call or a last minute vacation request.

Fingerprint

2020-02-10T17:53:30Z

David:

[[image:T500-B.png|right]]

The Fingerprint time clock from [https://sekureid.com/xenio-T500.html SekureID] is an advanced fingerprint recognition terminal designed for today’s cloud and IoT world.

[[Fingerprint Enrollment]] - instructions on enrolling employees in the Fingerprint time clock

[[Fingerprint Connection Issues]] - connections issues

[[Fingerprint Firmware Update]] - Instructions on how to upgrade your fingerprint clock to the latest firmware

[[Fingerprint Service Log]] - advanced topic on the logs created by the Fingerprint service

Fingerprint Firmware Update

2020-02-10T17:52:18Z

David:

Below is a list of instructions on how to update your fingerprint clock to the latest firmware version.

== Updating ==

* From the main screen, which displays the date and time, press the arrow that is pointing down in the top right corner of the main screen.
[[image:DownloadButton.jpg|400px]]

* If you see a yellow bar at the bottom that says "VERIFY YOUR IDENTITY" then a time clock supervisor needs to place their finger.
[[image:VerifyYourIdentity.jpg|400px]]

* Once verified, you will have two options listed. Click on the first option which is SekureID and then click Run at the bottom of the screen.
[[image:SekureIDVersion.jpg|400px]]

* Let the clock run the install and once completed, you will see the screen that says "App Upgrade OK". Click LAUNCH APP to go back to the main screen.
[[image:SekureIDLaunchApp.jpg|400px]]

* Once you click Launch App, the clock will go back to the main screen and you will see the arrow pointing down again. Click it and run the next option which is Timeco.
[[image:TimecoVersion.jpg|400px]]

*Let the clock run the install and once completed, you will see the screen that says "Module Upgrade OK". Click LAUNCH APP to go back to the main screen.
[[image:TimecoLaunchApp.jpg|400px]]

* Once you click on LAUNCH APP, the screen will flicker a few times and then go back to the main screen where you will now only see two icons in the top right corner of the main screen. Please also make sure that there are no X's on either of those two icons. If there are, please reboot the clock.

Fingerprint Firmware Update

2020-02-10T17:45:41Z

David:

Below is a list of instructions on how to update your fingerprint clock to the latest firmware version.

== Updating ==

To update a fingeprint clock to the latest version you need to start by clicking the arrow that is pointing down in the top right corner of the main screen.

* From the main screen, which displays the date and time, press the arrow that is pointing down in the top right corner of the main screen.
[[image:DownloadButton.jpg|400px]]

* If you see a yellow bar at the bottom that says "VERIFY YOUR IDENTITY" then a time clock supervisor needs to place their finger.
[[image:VerifyYourIdentity.jpg|400px]]

* Once verified, you will have two options listed. Click on the first option which is SekureID and then click Run at the bottom of the screen.
[[image:SekureIDVersion.jpg|400px]]

* Let the clock run the install and once completed, you will see the screen that says "App Upgrade OK". Click LAUNCH APP to go back to the main screen.
[[image:SekureIDLaunchApp.jpg|400px]]

* Once you click Launch App, the clock will go back to the main screen and you will see the arrow pointing down again. Click it and run the next option which is Timeco.
[[image:TimecoVersion.jpg|400px]]

*Let the clock run the install and once completed, you will see the screen that says "Module Upgrade OK". Click LAUNCH APP to go back to the main screen.
[[image:TimecoLaunchApp.jpg|400px]]

* Once you click on launch app, the screen will flicker a few times and then go back to the main screen where you will now only see two icons in the top right corner of the main screen. Please also make sure that there are no X's on either of those two icons. If there are, please reboot the clock.

File:TimecoLaunchApp.jpg

2020-02-10T17:20:33Z

David:

File:TimecoVersion.jpg

2020-02-10T17:20:17Z

David:

File:SekureIDLaunchApp.jpg

2020-02-10T17:19:52Z

David:

File:SekureIDVersion.jpg

2020-02-10T17:19:36Z

David:

File:DownloadButton.jpg

2020-02-10T17:19:06Z

David:

Fingerprint Firmware Update

2020-02-10T17:01:42Z

David: Created page with "Below is a list of instructions on how to update your fingerprint clock to the latest firmware version."

Below is a list of instructions on how to update your fingerprint clock to the latest firmware version.

Scheduling Training

2019-07-04T15:34:40Z

David: /* USING THE SCHEDULER */

There are three steps to the scheduling process. Whatever type of scheduling period you use, whether it’s monthly, four weeks, or eight weeks, the steps that you are about to learn is the same for EACH scheduling period and you should do these steps in this order before building the schedules for every scheduling period moving forward.
='''STEP 1'''=

=='''Schedule Patterns'''==

Schedule patterns (Master Schedule) is where you can input any recurring pattern that your staff works. You can do this by clicking on an employee and going to the Employee -> Scheduling -> Schedule Pattern tab.

[[File:Schedule_Pattern_Tab.png]]

* For example, if you do 4 week scheduling and someone works the same schedule in weeks 1 and 3, and the same schedule in weeks 2 and week 4, then all you need to do is give the employee 2 schedule pattern weeks.
* If you have a 4 week scheduling period and someone works the exact same schedule every single week of the 4 week scheduling period, then all you need to do is give them a 1 week pattern.
* If you have a 4 week scheduling period and someone works a different schedule every single week of a 4 week scheduling period then they will need to have a 4 week schedule pattern.

[[File:Week_2.png]]

* Part of giving a schedule pattern to someone is to choose the floor for that schedule. If you know that the employee will be working the SAME floor for EVERY schedule, then you can Home them on that floor by selecting the homing button and choosing the floor from the labor levels dialog box that pops up.(See Picture A) Alternatively, you can choose each floor manually, but this will take longer. (See Picture B)

(A)
[[File:Homing_Button.png]]

(B)
[[File:Alternativly_choosing_Floor.png]]

* If you have someone who is scheduled to work a double shift, you can enter this in the schedule patterns. First assign the regular shift as you normally would. Then, on any other day in the same week that does not have a schedule, choose the day and change it to the day you want the employee to have a double.(See Picture A) Once the day is changed, give them the second half of the double and you will see that there will be two options of the same day.(See Picture B) One with the first half of the double shift and one with the second half. (See Picture C)

(A)
[[File:Double_Choosing_Day_1.png]]

(B)
[[File:Double_Choosing_Schedule_2.png]]

(C)
[[File:Double_Choosing_Schedule_3.png]]

* If you would like to clear out all the schedule patterns for a specific employee and start from scratch you can use the Delete All button. This will clear out all schedule patterns for the employee that you choose.

[[File:Delete_All.png]]

=='''Planned Absences'''==

Once you are done putting in all the schedule patterns for all the regularly scheduled staff, you then move onto planned absences.
Planned absences is where you can put someone on vacation, FMLA, etc., '''BEFORE''' you build your schedules. That way, when you do build your schedules, the software will automatically take the employee off on the days that they have set schedules and make those schedules available for someone else to take.
* You do this by going to the Employee -> Scheduling -> Planned Absences tab and choosing the first day that they are '''AWAY''' and the last day that they are '''AWAY''', choose a reason why from the Status drop down list and click "Add to Planned Absences." If you need to add more placeholders to the list you can do this by contacting SBV support.

[[File:Planned_Absences.png]]

Please note – if you add planned absences after the Schedule Period is built, it won’t be reflected in the scheduler. If an employee informs you of an absence after the build, you can either:
* Unschedule the employee from the applicable shifts in the scheduler
* Use the regenerate function

='''STEP 2'''=

The goal of this step is to have both of the following reports empty before moving onto step three.
Once you are done inputting all the schedule patterns and planned absences, you are ready to move onto the next step which is running two reports. Both reports should be ran for the NEXT (specific) scheduler period.
=='''Schedule Patterns without Budget'''==
* The first report that you need to run is called "Schedule Patterns without Budget." This can be found by going to Reports -> Scheduling -> Schedule Patterns without Budget. If there are any entries when running this report it means that you gave someone a schedule pattern that you don’t have a budget for. For example, generally, C.N.A.’s work on specific floors while unit managers or supervisors work the house or all floors. So when the client puts a C.N.A. on the house floor and that isn’t part of the budget, it will show up on this report. Another reason for entries on this report is if information is missing. Make sure all schedules that were given to employees have floors/units. If there are any changes that need to be made to the budget please contact SBV support.

[[File:Schedule_Patterns_without_Budget.png]]

=='''Budget vs. Schedule Patterns (Over Budget Monthly)'''==
* The second report that you need to run is called "Budget vs. Schedule Patterns (Over Budget Monthly)." This can be found by going to Reports -> Scheduling -> Budget vs. Schedule Patterns (Over Budget Monthly). If there are any entries on this report it will mean that on that specific day, shift, budget group, and floor you have scheduled too many people. There are three common scenarios that would cause these entries on the report.

* The first possibility is that there is a specific employee with a schedule that doesn’t work at your facility anymore. To fix this, go to the employees’ schedule pattern tab and delete all the schedules that they have.

* Another possibility is that they do still work at the facility, but they are given a schedule that you have too many people working that schedule. To fix this, move the employee to a schedule that you are currently under budget for. To see where you are under budget, go to Reports -> Scheduling -> Budget vs. Schedule Patterns (Under Budget Monthly). Make sure to run it for the identical dates that the Over Budget Monthly report is being run for. The Under Budget Monthly report will give you the available schedules and the amounts of positions open to be given to employees.

* The last reason entries would be on this report is because the budget is incorrect. If that is the case, please contact SBV support. Bear in mind, the budget is set and confirmed before we start the scheduling process so in most cases this is not the reason for entries on the report.

[[File:Budget_vs_Schedule_Patterns_(Over_Budget_Monthly).png]]

='''STEP 3'''=

=='''Building the Schedules'''==
Once both reports come back clean, you are then ready to build your schedules. Follow the steps below to build your schedules.
* Click on Scheduler -> Build Schedules and then a small window will pop up when you click “build schedules”

[[File:Build_Schedules_1.png]]

* Maximize that window and you will see all of your budget groups that you are going to be building.
* Make sure you double check that the build date and end date columns reflect the scheduling period that you want to build for.
* Confirm that it’s correct, then click on the TOP MOST check box (see picture) which will then select all the budgets below.
* With the budgets checked off, click build schedules.
[[File:BuildSchedulesButton.png]]
* Once you select this button you will no longer be able to move out of that window. In the status tab for all the budget groups, you will see it go through a series of steps. This is the software building the schedules.
* Once it is done, the close button will then become available on the bottom, and the build date would move forward to the next build.

[[File:Build_Schedules_2.png]]

Make sure NOT to select the Build Schedules button again because this will cause the software to build an additional scheduler period which isn’t recommended. If you do, the only way to delete out a scheduling period that was built by accident is to contact SBV Support.

='''USING THE SCHEDULER'''=

You can read the section below as well as watching the video in the link below. Both will give you explanations on how to properly use the scheduler.

[https://www.youtube.com/watch?v=W8JUR89r5Eo&t=17s How to Use the Scheduler]

'''Date Range'''

The date range group provides a drop down of the scheduler period dates. Select from the drop down to fill in the start and end dates. Change these dates before clicking on the Display Schedules command to work with a different date range.

[[image:SchedulerGrid.png]]

Make the day-to-day schedule changes in the scheduler grid. The scheduler grid allows the user to move schedules between employees or to/from the available schedules.

Cell color, text and text color help provide maximum schedule information while using the minimum amount of space. Hovering over a cell will provide more detailed information like schedule start and end times, labor levels, schedule history and punch information.

'''Scheduler Groups'''

The employees and the available schedules are grouped by their respective scheduler group. You can filter or collapse the scheduler groups.

Filtering the groups:

[[image:SchedulerGroupFiltering.png]]

Collapsing the groups:

[[image:SchedulerGroupCollapse.png]]

The filtering, collapsing and expanding of the scheduler groups applies to both the employee and the available's grid.

'''Schedule and Placeholder Display'''

Weekly schedule totals display and can be used to sort the employees (those with less schedules listed first).

[[image:SchedulerWeeklyTotals.png]]

'''Employee Display'''

Employee information displays in columns that can be filtered. Additionally, employee information needed only for filtering, displays above the column headers at the top of the scheduler grid.

[[image:SchedulerEmployeeFields.png]]

In the above screen shot, the department field filter is shown. Employees can be filtered by Name, Shift Count, and Company.

'''Context Menu'''

The right click menu provides management of the schedules and placeholders, and access to reports. When applicable, menu selections are provided for multiple days and/or multiple employees. For example, the Monthly Schedule for Employee report is available for all selected employees.

[[image:SchedulerEmployeeContextMenu.png]]

'''Sorting'''

Employees can be sorted by:

Employee Name – the default sorting, alphabetically by their name.

Employee ID – sorted by the employee’s ID.

Seniority – sorted by date of hire.

Weekly Shift Count – sorted by the total schedule count in the selected week.

[[image:SchedulerSortOrder.png]]

'''Available Schedules'''

The available are grouped to provide a clear visual distinction between availables from different shifts and floors. The number in the cell represents the count of the available schedules. If the text color is white, then you are over budget on the shift and floor.

[[image:SchedulerAvailables.png]]

'''Find and Filter'''

[[image:SchedulerFindAndFilter.png]]

The Filter button is like the Filter Row in the employee list on the main screen. Only employees that match part of the filter text will display. Pressing Enter keeps the currently shown employees visible while newly found employees are displayed.

Here is the result of entering Smith, clicking Filter, entering Brown and pressing Enter.

[[image:SchedulerFilterThenFind.png]]

Shift and floor filtering is available from the 2 drop downs. The Filter Availables option will apply the same shift and floor filtering to the availables. Here is a screen shot of the availables filtered to floor 2.

[[image:SchedulerAvailablesFiltering.png]]

Include Home Shift applies when using shift filtering and will include employees that are homed in the filtered shift, although they do not have any schedules.

With Placeholders Only filters the scheduler screen to employees that have one or more schedule placeholders.

'''Tool Tips'''

There is an employee tool tip and the schedule / placeholder tool tip.

The employee tool tip displays additional information about the employee.

[[image:SchedulerEmployeeToolTip.png]]

The schedule / placeholder tool tip displays detail on the schedule / placeholder and punch information for the day.

[[image:SchedulerScheduleToolTip.png]]

'''Employees Crossing Budget Groups'''

Employees with schedules that cross a budget group, when the budget groups are not displayed together (e.g. RNs and LPNs) will display twice and with the correct counting of schedules for the group.

An RN supervisor works a floor nurse position. The totals are correct.

[[image:SchedulerCrossBudgetGroup.png]]

==Scheduler Grid Editing==

The scheduler grid allows you to manage the schedules assigned to the employees, restricted only by the authorizations of the user. Examples are:

* Move one or more schedules from one employee to another employee

* Move one or more schedules from the availables to an employee

* Move one or more schedules from an employee to the availables

* Add a schedule

* Add or delete placeholders

'''Moving Schedules'''

Schedule moves are a 2-part process. Schedules you are taking “from” (either an employee or the availables) and then giving “to” (either an employee or the availables).

After selecting the “from” schedule(s), press the F key. The selected cells have a red border to indicate that you are in the middle of a from/to action.

[[image:SchedulerFromAvailables.png]]

You can only select a single employee’s schedules (i.e. from the same row). Available schedules can be selected from different shifts and floors (i.e. different rows). Select cells that are not adjacent to each other using the Ctrl key.

Select the receiving employee (known as the “to” employee) from any of their cells and press the T key.

In the screen shot below, the schedules from the 25th and the 27th will move to the employee even though the cell from the 26th is the selected cell. Note: you cannot move schedules from one pay date to a different pay date.

[[image:SchedulerFromTo.png]]

Move schedules from an employee to the availables with the single keystroke of U.

'''Swapping Schedules'''

Schedule swapping occurs when the receiving employee already has a schedule in the same shift. The employee(s) keep their schedule start and end times.

You can combine swaps and moves at the same time.

[[image:SchedulerGiveAndSwap1.png]]

The two available schedules on the 5th floor are given to an employee. The 25th is an “available to employee” while the 26th is a schedule swap.

[[image:SchedulerGiveAndSwap2.png]]

'''Multiple Schedules in a Pay Date'''

If an employee has more than one schedule in a pay date, then you must provide the schedule number to take “from” this employee. The top left schedule is number 1 and the bottom right schedule is number 2. If there are 3 schedules, then they are numbered 1 to 3 from top to bottom. These alternate keys represent the keystroke and number combinations:

R = T and 1

E = T and 2

W = T and 3

I = U + 1

J = U + 2

K = U + 3

If you do not indicate the schedule number, the software will prompt you.

'''Placeholders'''

Add or edit placeholders for multiple days by selecting cells and using the [ Schedule Status Type] shortcut (Shift + Key).

'''Scheduler Type'''

Use the scheduler type for categorizing a schedule. The default scheduler type is Standard. Other scheduler types are Orientation, Light Duty and Make Up. Categorize schedules to provide indicators on the staffing reports. Pressing S, O, L or M on a selected schedule changes the scheduler type between Standard, Orientation, Light Duty and Make Up. The displayed text underlines for all scheduler types except Standard. Additionally, the text color can be configured for each scheduler type (Standard is always black).

'''Other'''

''Monthly Mode''

Make changes in the scheduler in Daily or Monthly mode.

Monthly mode changes are not considered to be a schedule change. Two employees swapping schedules is a typical example of a monthly change. Monthly mode changes do not add to the schedule history.

Daily changes are changes that occur on the "day of," and changes that you do before posting the schedule where you want the employee to have a placeholder, and/or the schedule to maintain history. Examples are a sick call or a last minute vacation request.

Fingerprint

2019-05-21T17:49:04Z

David:

[[image:T500-B.png|right]]

The Fingerprint time clock from [https://sekureid.com/xenio-T500.html SekureID] is an advanced fingerprint recognition terminal designed for today’s cloud and IoT world.

[[Fingerprint Enrollment]] - instructions on enrolling employees in the Fingerprint time clock

[[Fingerprint Connection Issues]] - connections issues

[[Fingerprint Service Log]] - advanced topic on the logs created by the Fingerprint service