FingerTec TimeTec Auto Restart Services Tools

Tuesday, July 30, 2013 TimeTec 0 Comments

Does your server show frequent signs of slow data return or data not appearing on the TimeTec server at all? For the convenience of users, FingerTec has newly developed an application to remedy this situation with FingerTec TimeTec Auto Restart Service.

Installation Setup

1) Click on the image below to download the installer, and extract it to your desktop.

2) Double-click the installer and click Next to begin the installation process. 

3) Read the agreement and select I accept the terms... etc. Continue by clicking Next

4) Select your preferred installation path or use the default location. Click Next to proceed. 

5) After completing the installation, click Finish to exit the wizard. 

Operation Steps

After completing the installation, go to your Start button > Click All Programs > FingerTec Worldwide > FingerTec TimeTec Auto Restart Services as per the image below.  

The FingerTec TimeTec Auto Restart Services tool have two types of operation:

1) Restart at Specific Time(s)

2) Restart according to Time Interval(s)

Initiated by Jazz, finalized by Afiq


Have any questions or inquiries about FingerTec? Drop your input here.

Use of Clocking Range in Ingress & TCMS V3

Monday, July 29, 2013 TimeTec 2 Comments

Please be informed that the below configurations are done on Ingress software, as shown in the accompanying images. However, this can also be applied in TCMSV3 to achieve comparable results, as the configuration is similar with only a slight difference in the interface.

The clocking range (only applicable for Weekly and Daily schedules) is used to determine the maximum time that one slot can record before it is considered as the time for the corresponding slot. For example, value for IN is 08:00 and the value for OUT is 17:00 in Clocking Time as per the picture below.

If you leave the clocking range blank, the system will calculate the middle time as the range of time to be used as per the picture below. 

For example, if the IN column in the clocking range is blank, the system will calculate the middle time between the IN and OUT columns. For the example above, the system will use the middle time between 08:00 and 17:00, which is 12.30. Hence, if a user punches in at 12:31 onwards, it will appear in the OUT column in the attendance sheet.

By using Clocking Range, you can change the software's default data allocation system as per the picture below.

In Clocking Range, insert 15:00 into the IN column. This will prompt the software to overwrite its default data allocation and use the inserted time value to allocate the data. Now, any transactions before 15:01 will fall in the IN column while those transactions after will be automatically assigner into the OUT column. 

If the employees work according to the work schedule, you may ignore this option. This option is only for special work case scenarios where it is needed to overwrite the software's default data allocation system. 

Replace with latest clocking (as per picture below) - When you click this checker, Ingress will replace any clocking data with the latest clocking data after the download process. It is recommended to check on OUT and DONE columns only because Ingress will always check the latest OUT time of the users and will publish it in the attendance sheet.

For example, the employee performs clocking at 16:30 and verified his fingerprint at the door to exit the premises. The software will use the transaction data 16:30 as the OUT time. Even if the employee subsequently comes in and finally exits at 17:00, the software will still use the transaction data 16:30 as the OUT time. If you tick the Replace with latest clocking checkbox at the OUT column, the Attendance Sheet will display the latest transaction data which is 17:00 instead of 16:30. 

Initiated by Zul, finalized by Afiq


Have any questions or inquiries about FingerTec? Drop your input here.

Ingress: Reboot Terminals After Making Changes to Device & Door Settings

Monday, July 29, 2013 TimeTec 2 Comments

Some users has gone through scenarios whereby the changes that they have made in Ingress are not updated into the relevant terminals. This is because the terminals need to be rebooted when a user performs any changes to the settings. Even though the Ingress software will prompt users to sync the software each time changes are made via a small pop-up window on the bottom left corner of the screen (Click to sync all device info window as seen in the picture below), users still need to reboot the terminals for the settings to be properly reflected.

The reason why the update did not take effect immediately is because the terminal will only recognize the original settings while the new settings has not been reflected into the terminals. Thus, the terminals need to be rebooted in order for the settings to take effect. This can be done in three ways:

  1. Turn the terminals' power off and back on, 
  2. Press the reset button at the terminal, 
  3. Reboot remotely via Ingress by clicking on Devices > Select the devices involved > Other > Reboot Device. Voila!

Interested in giving Ingress a try? Request for your FREE trial version here.

Initiated by LimSF, finalized by Afiq


Have any questions or inquiries about FingerTec? Drop your input here.

5 Reasons to Use FTDP

Thursday, July 25, 2013 TimeTec 0 Comments

Not sure if FTDP is right for you? Let me help! 
Like most other Muslims, I’ve been thinking about food a lot lately. It comes with Ramadan, I suppose. So here’s my question: If I had to choose between two plates of free food, one plate containing 5 pieces of chicken worth 5 dollars and the other containing a small piece of caviar worth 20 dollars, which plate would I choose? Would I go for what’s more filling or what’s more rare? Should I choose what I could finish eating only? Could the original financial value be a factor as well?

See, the choice may seem simple at first, but if you think about the pros and cons of both alternatives, you’ll realize that the answer ultimately comes down to your situational needs and wants. This also applies to FingerTec Data Processor Application, aka FTDP. The application is definitely not a ‘one-size-fits-all’ solution, as TCMS V2 or Ingress would have more comprehensive features, but there are 5 main reasons that may require you to use FTDP instead. Read more to see the top 5 situations that would be best solved with FTDP.


Have any questions or inquiries about FingerTec? Drop your input here.

New Feature for Face ID 3 & Face ID 4/4d – Managing Photos of Failed Identification

Wednesday, July 17, 2013 TimeTec 0 Comments

FingerTec has developed a new, added safety feature for Face ID 3 and Face ID 4/4d! When a face template fails to be identified by a terminal after a certain period of time, a photo of the face will be captured and stored. Below are some sample screenshots for a failed verification:

Failed verification in Face ID 3
Failed verification in Face ID 4
This is useful as administrators can trace back and determine the failure frequency of a particular individual by using FingerTec's TCMS V2 software.

The fail time period of each terminal is set to 10s by default. However, the time period is adjustable. To do so, simply follow the steps below:
Menu > System > Log Settings > Face Fail Time > Enter desired duration

For existing Face ID 3 & Face ID 4/4d users, the firmware must be updated before using the new feature. For the update, click on the relevant links below:

Face ID 3 -


Have any questions or inquiries about FingerTec? Drop your input here.