A perspective of Identity System: Why do we need a “Unique ID System”? by Navneet
Now, that we have acknowledged that the need of a “Unique ID System” exists (Refer my previous post), we must further acknowledge the purpose of deploying such a system i.e. the application areas and the usage environments.
A) Application Areas:


Civil applications
• Availing social benefits (RSBY, NREGS, etc) and
• Exercising citizen rights (Voting, etc) OR
Law Enforcement
Identifying a person from prints left behind at crime scene


Difference between Civil Applications and Law Enforcement
The difference is in the nature of participation of the subject, which is voluntary in the Civil Applications and involuntary in the law enforcement. Also, in the case of the law enforcement, the print left behind, also known as latent prints can be partial or be from the palm area; thereby making the identification very difficult and complex.
Further, the implications of a “False Acceptance” or “False Reject” are very different among these systems. While a “False Acceptance” in a civil application would result in multiple benefits to an individual under a scheme (which can be rectified subsequently), it would allow a criminal prosecution against a wrong individual, and vice-versa for “False Reject”. It would be imperative to note that the system requirements for Law Enforcement system would be more rigid and complex.
B) Usage:
Unique ID Alone Vs Unique ID
It is also important to asses if
• The output desired from such a system is to be able to identify a new record submitted as already existing in the historical database built over time, alone
OR
• To authorize a transaction request with biometric based authorization data.
The primary difference between the two environments being system uptime and availability requirement; while the “Unique ID” can be established online as a transaction, they are generally done in batches for optimization purposes and service is merely delayed, not denied in case of downtime. On the other hand, for transaction environment needs, the system uptime and efficient response are mandatory for continual service else it is perceived as service denied.
Provision for a Transaction Environment
Further, the transaction environment described above envisages an online environment and assumes communication channel availability at the point of transaction. However, if the need is that transaction be allowed offline as well, then there is a requirement of secure token issuance and lifecycle management – which will require a collection of systems like KMS, SCMS, etc.
FINO has successfully implemented transaction environments around a fingerprints based “Unique ID System” for various civil applications.


Recent Comments