Part A. System Design, Components and Parameters
Please describe the system architecture in detail. In particular, is enrollment and authentication done locally or on a server?
– The enrolment and authentication is done locally on the ACTAtek reader, ACTA3-1K-FLI-SMC. In this particular model, the fingerprint sensor module, RFID smart card, and a CMOS camera for taking picture of the user are available. The template can also be stored in a RFID smart card, such that the smart card is kept by the user and all the templates on the device are removed. The template stored in the card is read by the device and then used to match with the finger. However, the time taken for authentication is slower when compared with the case of templates stored in the device.
Which hardware and software products from the vendor are used? Can you provide specifications for those products, besides those publicly available on the vendor’s website?
– The hardware will be the ACTAtek reader, ACTA3-1K-FLI-SMC model, and no software is required to be installed at any PCs. The system and application software are embedded in the device. It is a highly integrated all purposed built system.
In the case of a one-to-many identification system, how many templates is the system capable of matching (e.g., 1:3000, 1:20000)? The answer to this question is critical.
– The system is capable of one-to-many matching 1:3000 templates by default, but can be expanded to 1:N but slower. If the user can accept slow response time, the ratio can be increased further without theoretical limitation.
What is the actual number for the False Acceptance Rate (FAR) that is configured for the system? Does this number refer to a one-to-many or a one-to-one system? Is it applicable to one or two-finger scanning?
– The FAR is 0.01%. This applies to all method of authentication. Each user can register up to 3 templates. For best performance, we recommend using the same finger. However, if a user likes to enroll 3 different finger template that is also accepted by the device but performance will be degraded.
Does the system create a record of attendance and/or transactions? How are those data used?
– The system creates an event log that records the time, unit, triggers, and ID when there is a user trying to do the authentication whether it’s approved or not. These data can be used by different application software to generate different kind of reports and analysis depending upon the user requirement.
Part B. Enrollment Process
How many fingers are needed per user, and which ones (e.g., right index + left index) are enrolled?
– We recommend using the same finger, and we recommend the index finger.
How many fingers and which ones are normally needed for authentication (i.e. one of the enrolled fingers or both)?
– We recommend only using 1 finger for enrolment.