The Unique Identification Card (UID Card)
Shaila Garg, Mahima Kapoor
rockingshaila@yahoo.com, smarty_mahima@yahoo.com
ABSTRACT
The Unique Identification Authority of India (UIDAI) is
an agency of the Government of India responsible for
implementing the envisioned Multipurpose National
Identity Card or Unique Identification card (UID Card)
project in India. It was established in February 2009,
headed by Nandan Nilekani and he will own and operate
the Unique Identification Number database.
Purpose:
The aim of this project is to provide a unique number to all
the Indians. The authority would provide a database of
residents of India in a very simple manner.
The UID will link a person's Passport Number, Driving
License, and PAN card, Bank Accounts, Address, Voter ID
etc and all this information will be checked through a
database. So if someone has a different address on PAN
and driving license, is liable to get caught. Those who will
try to stay out of this program will have to face much
inconvenience in doing business operating bank accounts
and other offices, which will require a UID.
UID project is given a name called AADHAAR meaning
'support', and its logo is a yellow sun with a fingerprint
embedded in the center.
This paper will identify the different techniques for the
implementation of the UID like Code Configuration and
Number Format.
KEYWORDS
UID, UIDAI, AADHAR, Nandan Nilekani
1.INTRODUCTION
1.1Background
Unique identification project was initially conceived by the
Planning Commission as an initiative that would provide
identification for each resident across the country and
would be used primarily as the basis for efficient delivery
of welfare services. It would also act as a tool for effective
monitoring of various programs and schemes of the
Government.
1.1.1 The concept of a unique identification was first discussed
and worked upon since 2006 when administrative approval for
the project –"Unique ID for Below Poverty Line (BPL)
families" was given on 03 March 2006 by the Department of
Information Technology, Ministry of Communications and
Information Technology. This project was to be implemented
by the National Informatics Center (NIC) over a period of 12
months. Subsequently, a Processes Committee to suggest
processes for updation, modification, addition and deletion of
data fields from the core database to be created under the
Unique ID for below BPL project was set up on 03 July 2006.
This was set up under the chairmanship of Dr. Arvind Virmani,
Principal Adviser, and Planning Commission.
1.1.2 A "Strategic Vision on the UIDAI Project" was prepared
and submitted to this Committee by M/S Wipro Ltd (Consultant
for the design phase and program management phase of the
Pilot UIDAI project). It envisaged the close linkage that the
UIDAI would have to the electoral database. The Committee
also appreciated the need of a UIDAI Authority to be created
by an executive order under the aegis of the Planning
Commission to ensure a pan-departmental and neutral identity
for the authority and at the same time enable a focused
approach to attaining the goals set for the XI Plan. The Seventh
Meeting of the Process Committee on 30 August 2007 decided
to furnish to the Planning commission a detailed proposal based
on the resource model for seeking its "in principle" approval.
1.1.3 UIDAI may limit its activities to creation of the initial
database from the electoral roll/EPIC data. UIDAI may
however additionally issue instructions to agencies that
undertake creation of databases to ensure standardization of
data elements.
1.1.4 December 2009 was given as the target date for UIDAI to
be made available for usage by an initial set of authorized users.
1.1.5 In pursuance of the Empowered group of Ministers' fourth
meeting dated 04 November 2008, the Unique Identification
Authority of India was constituted and notified by the Planning
Commission on 28 January 2009 as an attached office under the
aegis of Planning Commission with an initial core team of 115
officials. The role and responsibilities of the UIDAI was laid
down in this notification. The UIDAI was given the The UBCC will specify the initial biometrics system and from
responsibility to lay down plan and policies to implement time to time enhance to introduce new technologies and best
UIDAI scheme and shall own and operate the UIDAI practices. UBCC will evaluate and characterize technology,
database and be responsible for its updation and devices, algorithms and processes to assess what and when
maintenance on an ongoing basis. specifications need to be revised or enhanced. It will push the
state of art in Biometrics to achieve UIDAI’s objectives. It will
1.2 Mandates and Objectives be a national resource to other departments for implementing
UIDAI compatible biometrics systems.
The Unique Identification Authority of India (UIDAI) has
been created as an attached office under the Planning 2. ABOUT AADHAR
Commission. Its role is to develop and implement the
necessary institutional, technical and legal infrastructure to 2.1 What is Aadhaar?
issue unique identity numbers to Indian residents.
Aadhaar is a 12-digit unique number, which the Unique
On 25 June 2009, the Cabinet also created and approved Identification Authority of India (UIDAI) will issue for all
the position of the Chairperson of the UIDAI, and residents. The number will be stored in a centralized database
appointed Mr. Nandan Nilekani as the first Chairperson in and linked to the basic demographics and biometric information
the rank and status of a Cabinet Minister. Mr. Ram Sewak – photograph, ten fingerprints and iris – of each individual. The
Sharma has been appointed the Director General. details of the data fields and verification procedures are
available here.
1.3 Mission and Timeline
Aadhaar will be:
1.3.1 The Mission
The role that the Authority envisions is to issue a unique 2.1.1 Easily verifiable in an online, cost-effective way.
identification number (UIDAI) that can be verified and
authenticated in an online, cost-effective manner, which is 2.1.2 Unique and robust enough to eliminate the large number
robust enough to eliminate duplicate and fake identities. of duplicate and fake identities in government and private
databases.
1.3.2 The Timelines
The first UIDAI numbers are issued over the next 12-18 2.1.3 A random number generated, devoid of any
months counted from August 2009. Prime Minister at classification based on caste, creed, religion and geography.
Nandurbar, Maharashtra issues the first number on 29th
September 2010. Over five years, the Authority plans to TABLE 1: WHAT AADHAR IS?[3]
issue 600 million UIDs. The numbers are issued through
various 'registrar' agencies across the country. What AADHAR IS WHAT AADHAR
ISN’T
1.3.3 Technology Development Unit (TDU) A number (12 digits) Another Card
For every individual, including One per family
A Technology Development Unit (TDU) consisting of infants
experts in various areas of operation including technology, Enables identification , & is for Establishes citizenship
legal framework, procurement of hardware and software every resident & is only for Indians
etc. have been established. Volunteers, Resources and Will collect demographic & Will collect profiling
Sabbaticals support the units. biometric information to information such as
establish uniqueness of caste, religion,
1.3.4 Project Management Unit (PMU) individual language
Voluntary Mandatory
The team has been established with the assistance of the
For every resident, irrespective Only for individuals
National Institute of Smart Government (NISG) with whom
of existing documentation who possess
the UIDAI has entered into an agreement on 30 November
identification
2009. Twenty professionals are currently onboard in roles
documents
ranging from Technology, Legal, Communications and
Each individual will be given a Individual can obtain
Procurement to Capacity Building, Process and Operations.
single unique ID number multiple AADHAAR’s
1.3.5 UIDAI Biometrics Centre of Competence (UBCC) UIDAI will enable a universal AADHAARs will
identity infrastructure that any ID replace all other IDs
based application like ration
card, passport etc. can use
UIDAI will give a “Yes” or “No” UIDAI information
response for any identification will be accessible to
authentication queries public & private
agencies
2.2 How to get an Aadhaar?
The process to get an Aadhaar will be circulated by the
local media upon which residents need to go to the nearest
Enrolment Camp to register for an Aadhaar. The resident
primarily needs to carry certain documents, which will be
specified in the media advertisement.
Upon registering for Aadhaar, residents will go through a
biometric scanning of ten fingerprints and iris. They will
then be photographed and given an enrolment number upon
completion. Depending on the enrolment agency, residents
will be issued an Aadhaar number within 20 to 30 days.
3. BIOMETRIC DEVICES
3.1 Iris Scanner
Iris cameras perform recognition detection of a person's
identity by mathematical analysis of the random patterns
that are visible within the iris of an eye from some distance.
It combines computer vision, pattern recognition, statistical
inference and optics.
3.2 Fingerprint Scanner
A fingerprint scanner is an electronic device used to
capture a digital image of the fingerprint pattern. This scan
is digitally processed to create a biometric template, which
is stored and used for matching.
3.3 Face Camera
Face detection is used in biometrics, often as a part of (or
together with) a facial recognition system. It is also used in
video surveillance, human computer interface and image
database management. A face camera is a web cam with 2
Mpx or above which can take a clear crisp photograph of
the face. Some recent digital cameras use face detection for
auto focus. Also, face detection is useful for selecting
regions of interest in photo slideshows that use a pan-and-
scale Ken Burns’s effect. That is, the content of a given
part of an image is transformed into features, after which a
classifier trained on example faces decides whether that
particular region of the image is a face, or not.
4. FEATURES OF THE UIDAI MODEL
4.1 The Aadhaar will only provide identity:
The UIDAI's purview will be limited to the issuance of unique
identification numbers (Aadhaar) linked to a person's
demographic and biometric information. The Aadhaar will only
guarantee identity, not rights, benefits or entitlements.
4.2 A pro-poor approach:
The UIDAI envisions full enrolment of the residents, with a
focus on enrolling India's poor and underprivileged
communities. The Registrars that the Authority plans to partner
with in its first phase such as – the Mahatma Gandhi National
Rural Employment Guarantee Scheme (NREGA), Rashtriya
Swasthya Bima Yojna (RSBY), and Public Distribution System
(PDS) – will help bring large number of the poor and
underprivileged into the UID system. The UID method of
authentication will also improve service delivery for the poor.
4.3 Enrolment of residents with proper verification:
This will ensure that the data collected is clean right from the
beginning of the program. However, much of the poor and
underserved population lack identity documents and the UID
may be the first form of identification they will have access to.
The Authority will ensure that the Know Your Resident (KYR)
standards do not become a barrier for enrolling the poor, and
will devise suitable procedures to ensure their inclusion without
compromising the integrity of the data.
4.4 A partnership model:
The UIDAI approach leverages the existing infrastructure of
government and private agencies across India. The UIDAI will
be the regulatory authority managing a Central ID Repository
(CIDR), which will issue Aadhaar, update resident information
and authenticate the identity of the residents as required.
4.5 The UIDAI will emphasize a flexible model for
Registrars:
The UIDAI will provide standards to enable Registrars to
maintain uniformity in collecting certain demographic and
biometric information, and in performing basic KYR activities.
These standards will be finalized by the KYR and biometric
committees constituted by the Authority.
4.6 Process to ensure no duplicates:
Registrars will send the applicant's data to the CIDR for de-
duplication. The CIDR will perform a search on key
demographic fields and on the biometrics for each new
enrolment, to minimize/eliminate duplicates in the database.
4.7 Online authentication:
The Authority will offer a strong form of online authentication,
where agencies can compare demographic and biometric
information of the resident with the record stored in the indicating the least level of similarity and 100 as the highest
central database. level of similarity.

5.1.2. Multi-vendor:
4.8 The UIDAI will not share resident data:
It may determine to route a particular de-duplication request to
The Authority envisions a balance between 'privacy and more than one biometric solution. If it routes a de-duplication
purpose' when it comes to the information it collects on request to more than one solution, it is responsible for
residents. The agencies may store the information of the determining the final outcome of the de-duplication request.
residents they enroll if they are authorized to do so, but will
not have access to the information in the Aadhaar database. The key features of the middleware are:
The UIDAI will answer all requests to authenticate identity
only through a 'Yes' or 'No' response. The Authority will 5.1.2.1Routing and mediation.
also enter into contracts with Registrars to ensure the
confidentiality of the information they collect and store. 5.1.2.2Guaranteed delivery
4.9 Data Transparency: 5.1.2.3Fault tolerance and load balancing
The authority will place all the aggregated data for public
5.1.2.4Open standard based messaging (AMQP) using open
to access under RTI. However Personal Identity
source Rabbit MQ
Information (PII) will NOT be accessible by any entity.
5.1.2.5Transparent connectivity to analysis and system
4.10 Technology will under gird the UIDAI system:
monitoring modules of UIDAI applications
The Aadhaar database will be stored on a central server.
Enrolment of the residents will be computerized, and 5.1.2.6Support of Web 2.0 based UIDAI ABIS API and CBEFF
information exchange between Registrars and the CIDR data format standard
will take place over a network. Authentication of the
residents will be online. 5.1.2.7Encapsulation and isolation of ABIS components

5. UID SYSTEM REQUIREMENTS OF THE 5.1.3 Verification Subsystem of Authentication Server

BIOMETRIC COMPONENTS
5.1 Multi-modal Biometric de-duplication in the Enrolment
Server
Considering the expected size of the de-duplication task,
the UID Enrolment server will utilize:
5.1.1. Multi-modal de-duplication.
Multiple modalities such as– fingerprint and iris image will
be used for de-duplication. Face photograph is provided if
the vendor desires to use it for de-duplication. While
certain demographical information is also provided, UIDAI
provides no assurance of its accuracy. Demographic
information shall not be used for filtering during the de-
duplication process, but this capability shall be preserved
for potential implementation in later phases of the UIDAI
program. Each multi-modal de-duplication request will
contain an indexing number (Reference ID) in addition to
the multi-modal biometric and demographic data. In the
event of one or more duplicate enrolments are found, the
ABIS will pass back the Reference ID of the duplicates and
the scaled comparison scores upon which the duplicate
finding was based. The scaled fusion score returned with
each duplicate found will have a range of [0, 100], with 0
In the first release of the UIDAI server, the biometric
verification module, provides verification within the
authentication server. The solution should be capable of 1:1
verification comparisons of enrolled references with incoming
ISO/IEC 19794-2-compliant fingerprint, iris or face images or
ISO/IEC 19794-2 compliant fingerprint minutiae sets without
proprietary extended data.
The templates will be maintained in memory resident database
by the UIDAI authentication server application.
5.2 Partner Portal
The UIDAI project is based on a partnership model consisting
of Registrars and their respective enrolling agencies on the
ground. There are other entities such as device suppliers,
trainers, letter delivery agencies, and pre-enrollers etc all of
whom play an important role in enrolling 1.2 billion residents.
The partner portal will cater to the needs of the partner
community.
This portal will provide them with overall statistics that involve
them, as well as allow them to track individual cases.
These users will be able to track:
5.4 Data Portal
5.2.1 Administration and user management – creation /
deletion of the user records We want to expose all publishable public information through a
"Data Portal" where all data is exposed in machine-readable
formats. This portal allows third party developers to develop
5.2.2 Aggregate pre-enrolment statistics – number, latency, Web 2.0 applications based on this data.
validation issues. (For Registrars, Sub-Registrars, and
Enrolment Agencies) 5.4.1 Registrar System:

Registrars will have their own IT infrastructure to interact with

5.2.3 Aggregate enrolment statistics – number, latency, Aadhaar System. The functionalities include the following:
approvals, and rejection reasons (for Registrars, Sub-
Registrars, and Enrolment Agencies) 5.4.1.1 Getting updates during enrolment process

5.4.1.2 Uploading bulk demographic data

5.2.4 Aggregate authentication statistics – number, latency,
success / failures (for authentication clients)
5.4.1.3 Act as an Authentication User Agency (AUA)

To keep the confidentiality of the data being sent to the

5.2.5 Track individual resident information – pre- registrar system, the data will be encrypted using the public key
enrolment, enrolment, and authentication – that they are provided by the Registrar. It follows that the Registrars have to
involved in. manage their <Private Key, Public Key> pair securely and put
the necessary infrastructure in place. The interacting Registrar
5.3 Public Portal systems have to be hardened. UIDAI may provide security
guidelines to Registrars to assist in the implementation but the
The UIDAI being a project of national importance will ownership will always reside with the Registrars. UIDAI will
need to continually share various design, development, define interfaces for the Registrar System to interact with
implementation and operational aspects with the public. CIDR. There will be no libraries to be integrated with. Since
The grievance redressal system also needs to be integrated the Registrars also maintain a copy of their enrolment data, they
into the public portal to redress complaints and grievances have to take enough precautions to secure the data.
faced by residents in the process of enrolment and
authentication. The UIDAI information portal will address 6. UBCC AND RESEARCH
the above needs. This portal will also provide all users with
information about the UIDAI system, and allow them to 6.1 Introduction:
drill down on the performance by region, etc. It will not
allow users to track individual cases. The UIDAI has been setup by the Government of India with a
mandate to issue a unique identification number to all the
All users will be able to view the following: residents in the country. A key requirement of the Aadhaar is to
minimize/eliminate duplicate identity to improve the efficacy of
5.3.1 List of Registrars, Enrolment Agencies, etc. the service delivery. Biometrics features are selected to be the
primary mechanism for ensuring uniqueness.
5.3.2 Number of UIDs issued by time (day, month, year),
and region (country, state, district, city) Therefore, it is necessary to create a UIDAI Biometrics Center
of Competence (UBCC) that focuses on the unique challenges
5.3.3 Performance Metrics – At an aggregate level – the of UIDAI.
number of Registrars, latency to allocate UIDAIs,
number of complaints, etc. 6.2 Mission:

5.3.4 Authentication requests – count, latency, success To design biometrics system that enables India to achieve
/failures. uniqueness in the national registry.

5.3.5 Grievance requests filed with the UIDAI and the The endeavor of designing such a system is an ongoing quest to
responses. innovate biometrics technology appropriate for the Indian
conditions.
 system personnel.
6.3 Goals:
6.4.4 Biometric Laboratory:
The mission of UBCC can be achieved through the
following distinct goals: It will build and maintain state-of-art laboratory to remain
viable independent research and engineering unit.
6.3.1 Specifications:
7. ENROLEMENT PROCESS
UBCC will specify the initial biometrics system and will
enhance the features at regular intervals to insert new 7.1 Introduction to the Unique Identification Number:
technologies and best practices.
7.1.1 It is a 12-digit number that the Unique Identification
6.3.2 Characterization: Authority of India (UIDAI) will provide to residents of India
after collecting and verifying their demographic and biometric
UBCC will evaluate and characterize technology, devices, data.
algorithms and processes to assess what and when 7.1.2 The Unique Identification Number (UID number) is a
specifications need to be revised or enhanced. unique 12-digit number assigned to every person residing in
India, verifiable by means of a biometric identification system.
6.3.4 Innovation:
7.1.3 A UID number can be obtained by anyone who is a
UBCC will push the state of art in Biometrics to achieve “usual resident” as defined in the Citizenship Act.
UIDAI's objectives.
Remember! The UID number does not grant Indian citizenship
6.3.5 Assistance: to anyone.

CIDR will be a national resource to other departments for
implementing UIDAI compatible biometric systems.
6.4 Strategy:
UBCC will achieve its goals through the following four-
pronged strategy:
6.4.1 Talent:
It will attract and hire world-class biometric talent. UBCC
will emphasize quality over quantity and build a small
group of exceptional scientists and engineers.
6.4.2 Collaboration:
7.2 Who is an enrolment operator?
An enrolment operator is appointed by an enrolment agency to
carry out the enrolment of residents using the AADHAAR
enrolment client.
7.2.1 An enrolment operator is responsible for the actual
capture of resident data (using the AADHAAR
enrolment client installed on the computer and the
biometric devices provided by the enrolment agency
that appointed him).
7.2.2 An enrolment operator is expected to ensure that all
the data captured is correct and has been verified using
one of the means specified by the enrolment agency.

It will closely collaborate with other technical departments,
academic institutes, international experts and international
bodies to assimilate and share combined knowledge. It will
promote joint research, investigation and analysis at
national and international academic institutes through
grants and "funded research".
6.4.3 Rapid adoption:
7.2.3 The roles and responsibilities of an enrolment
operator include:
7.2.3.1 Enrolment of residents by capturing their demographic
& biometric data.
7.2.3.2 Capture of residents’ biometric expectations
(missing/extra fingers, missing eyes/iris, etc)

It will build reference architecture, prototype and conduct

proof of concept to support rapid adoption of the 7.2.3.3 Obtaining supervisor verification for all biometric
technology for UIDAI system both during the initial expectations pertaining to residents
development and later during operation. It will stay
grounded by working closely with the operational UIDAI
7.2.3.4 Saving resident data, exporting data to memory
stick, ensuring integrity of resident data until it is 8.3 Enrolment agency Supervisors
sent to the CIDR (over the web or through the
Indian Post). 8.4 Enrolment agency Operators

7.2.4 The enrolment captures process: Using the 8.5 UIDAI users.
enrolment client
8.6 Users
The following section will provide detailed information
about the steps involved in enrolling residents, along with Enrolment agency administrators are required to fill in data
instructions for how to use the enrolment client to perform pertaining to –
these steps. Given below is the list of steps involved in
enrolling residents using the enrolment client. 8.6.1 Enrolment agency administrators

7.2.4.1 Step1: Logging into the enrolment client – by 8.6.2 Enrolment agency Supervisors
enrolment operator.
8.6.3 Enrolment agency Operators
7.2.4.2 Step2: Importing the pre-enrolment data file into
the computer. Registrar administrators are required to fill in data pertaining
to-
7.2.4.3 Step3: Capturing resident demographic data - by
enrolment operator. 8.6.4 Registrar Administrators

7.2.4.4 Step4: Capturing resident photograph – by 8.7 Data Import Format

enrolment operator.
The attached spreadsheet provides a template to be used for
7.2.4.5 Step5: Capturing residents iris data (with providing user data.
exceptions, if required) – by enrolment operator.
Instructions to fill in the details in the below excel is in User
7.2.4.6 Step6: Capturing resident fingerprint data (with Import Rules Table.
exceptions, if required) – by enrolment operator.
TABLE 2: USER IMPORT RULES TABLE[1]
7.2.4.7 Step7: Verification of biometric exceptions (if
any) – by enrolment supervisor and operator. Column Max Instructions
Length
7.2.4.8 Step8: Review and confirmation of captured data. user_code 40 This is a unique code to be
assigned to each user by the
7.2.4.9 Step9: Export of captured data to memory stick or organization (Register/Enrolment
UID server (depend on internet connectivity) at Agency)
the end of the enrolment session. user_org_code 30 Organization Code of the
Enrolment Agency or Registrar
(Available from UIDAI) as
applicable
8. USER MANAGEMENT user_type_code 30 • “UT_OPERATOR” for
Operator
Import of Users into the UIDAI System shall be managed • “UT_SUPERVISOR” for
by consolidating the Information specific to Enrolment Supervisor
Agencies & Registrars via excel sheets of which formats • UT_ENROL_AGENCY_A
are attached as below. DMIN for Enrolment
Agency Administrator
Users may be broadly classified as Introducers and non-
• “UT_REGISTRAR_ADMI
introducers. Non-Introducers comprise of
N” for Registrar
Administrator
8.1 Registrar administrators
user_name 99 Name of the User
8.2 Enrolment agency administrators user_uid 12 UID of the User
user_enrol_id 36 Enrolment ID of the user is for the Introducer. Not
mandatory if UID is not available mandatory.
user_status 1 Enter the value ‘1’ if new user user_email_id1 60 Email address of the
Enter value ‘0’ if you want a Introducer
existing user to be deactivated User_email_id2 60 2nd Email address of the
user_telephone1 16 Telephone Number owned by the Introducer
User
user_telephone2 16 2nd Telephone Number of the 9.2 Introducer Region mapping format
User if available
user_fax 16 Any fax number accessible for For filling up Region Codes for the Introducer (the regions for
the user. Not mandatory. which he can act as Introducer), the state region codes which
user_email_id1 60 Email Address of the User. This can be used are as below.
is mandatory for Enrolment
Agency Administrator. If the region type is district, sub-district or v/t/c, the region
user_email_id2 60 Email Address of the User. codes have to be input based on region codes published on
UIDAI Website. If the Registrar wants to assign multiple
Please ignore the columns user_vtc, user_district, regions to the Introducer, repeat the Introducer code and assign
user_sub_district, user_state and user_pincode. the next region in the next row of the attached excel file.

9. INTRODUCER MANAGEMENT Instructions to fill in the details in the below excel is in

Introducer Region mapping Import Rules Table.
Registrar administrators & UIDAI users are required to fill
in data pertaining to Introducers and also Region mapping TABLE4: INTRODUCER REGION MAPPING
of Introducers. IMPORT RULES TABLE[2]

Introducer Data Import Format Column Max Instructions

Length
The attached spreadsheet provides a template to be used for Introducer_code 40 This is a Unique
providing user data. Instructions to fill in the details in the Code to be assigned
below excel is in Introducer Import Rules Table. by the Registrar for
each Introducer.
TABLE 3: INTRODUCER IMPORT RULES TABLE[1] Introducer_org_code 30 Registrar Code
entered in the
Column Max Instructions Introducer Import
Length format.
user_code 40 This is a unique code Assigned Region Type 1 Region Region
assigned by the Registrar for Type Type
the Introducer Code
user_org_code 30 Organization Code of 1 State
Registrar (Available from 2 District
UIDAI) 3 Sub-
user_type_code 30 UT_INTRODUCER District
user_name 99 Name of the Introducer 4 VTC
user_uid 12 UID of the Introducer is Region_code 20 Region Code of
mandatory Regions to be
user_status 1 Enter the value ‘1’ for new assigned to the
introducer Introducer based on
Enter value ‘0’ if you want the region codes
the existing introducer has to Published by
be made inactive UIDAI. If multiple
user_telephone1 16 One Telephone Number regions have to be
owned by the Introducer assigned to a
user_telephone2 16 2nd Telephone Number for particular
the Introducer if available introducer, add a
user_fax 16 Any fax number accessible new row with all
 the details above, The AADHAAR Enrolment Client application captures the
choose the Region KYR (Know Your Resident) data. The registrars may require
Type Code and the capturing some other registrar specific fields related to residents
new Region Code. called as KYR+data. For example, In case of PDS data,
Pincode 6 Pincode is information such as APL (Above Poverty Line), BPL (Below
applicable for Poverty Line), Family Details, etc. may be collected as part of
Region Type Code KYR+data.
4 only.
Region_association_Status 1 If the region Following diagram depicts the relation between AADHAAR
association has to Enrolment Client and Registrar’s KYR+Application their
be activated when integration.
the Introducer is
imported into the
system. Aadhaar
Enrolment
10. SET UP PROCESS Client KYR+data file KYR+Applic
(kyrplus.dat)
ation
10.1 Pre-Requisites

10.1.1 Registrar has been provided with a 3 digit Registrar Enrolment

code by UIDAI; the Enrolment Agency must be aware of Station
its Registrar’s code

10.1.2 The Enrolment Agency must be aware of its 4-digit
enrolment agency code provided by UIDAI
10.1.3 The Enrolment agency must have filled in the “User
Management Toolkit” provided by UIDAI and the same
should be sent to UIDAI before starting the enrolment
process.
10.1.4 The enrolment client users (operators/supervisors)
should have applied for an UID.
10.2 System Requirements
The minimum system requirements for using the enrolment
client are as stated below.
10.2.1 2GHz, Dual core CPU, 2GB RAM, 160 GB HDD,
100Mbps NIC, Windows XP Professional - SP3 or
Windows 7 Professional / Enterprise Version, 4 USB ports
or equivalent hub.cy
Recommended monitor resolution setting: 1024 x 768.
10.2.2 Bio-metric devices - Iris scan (Cross Match or L1),
Digital photo camera, Finger Slap device (Cross Match or
L1).
10.2.3 Machine should not have any pending Windows
update. (Windows updates are performed automatically by
connecting to internet and selecting live windows update)
11. PRE ENROLMENT DATA & KYR + DATA
The typical process to integrate the pre-enrolment data file with
the AADHAAR Enrolment Client application is as follows:
11.1Residents comes closer to enroll
11.2The enrolment operator finishes the KYR data capture
using AADHAR Enrolment Client of the resident
11.3The KYR+ data as per the template gets saved into a .dat
file (name-value pair) at a pre-defined location on the
enrolment station
11.4The operator switches to the KYR+ application with the
help of Alt+Tab key
11.5The KYR+ data of the resident can be pulled to the KYR+
application with the help of a function key for eg. F5
11.6KYR+ data is captured and saved by the KYR+
application.
The KYR+ data gets captured from the AADHAAR client
application after each enrolment capture and gets saved into a
pre-defined location. At the end of every enrolment, a unique
“Enrolment ID” is generated. This edited KYR data along with
Enrolment ID is shared using a Name-Value pair file, which
will typically be a .dat file (kyrplus.dat) to Registrar’s software
for collecting KYR+ fields.
The only extra column added is that of the Enrolment ID which
is generated as a part of the enrolment from the application
itself. The “Name” and the “Value” field will be separator with
a delimiter ‘=’ (equal to) and name will carry the labels as
mentioned below. For every new name-value pair, ‘new 12.8 Application This refers to the AADHAAR enrolment
Line’ will be separator, ex. client application.

FullName=Ram Prakash 12.9 Machine The system on which the application is installed
DateOfBirth=10/04/1980 and the biometric devices are connected.

TABLE 4[3] 12.10 Entity An entity may be a person, group of people or

organization performing a particular task or set of tasks in the
PreEnrolmentID overall process of enrolling residents and issuing UID numbers.
Mandatory
LockLanguageCode
EnrolmentID 12.11 Registrar is the entity/organization that acts as the
Application Number administrator and owner of the entire enrolment process and
system.
NPR Receipt Number
Bank Account Number 12.12 Enrolment Supervisor is a person who supervises the
FullName enrolments that happen at a given enrolment center. S/he makes
FullName_LL sure all the enrolments take place smoothly and all the rules are
DateOfBirth/Yearof Birth followed. S/he also authenticates and overrides the exception
Options
DateOfBirthType capture done by the enrolment operator.
Gender
AddrCareOf 12.13 Enrolment Operator is a person who captures and
AddrCareOf_LL maintains the details of the resident. S/he is also responsible for
exporting the resident data file to an external (secondary
AddrBuilding
storage) device.
AddrBuilding_LL
AddrStreet 12.14 Demographic Data is data about the resident that is
related to Name, Address, Gender, Data of Birth, Relationship,
12. TERMINOLOGY Mobile Number and Email.
12.1 Enrolment is the process of capturing resident data 12.15 Biometric Data is data about the resident that is related
(including demographic and biometric data). The enrolment to face (phot), IRIS and Fingerprints.
is done by the enrolment operator/agent.
13. CONCLUSION
12.2 Enrolment Center is the location where the
enrolment happens. Each enrolment station has the required The UIDAI's mandate is to issue every resident a unique
enrolment set-up to make the enrolment possible. identification number linked to the resident's demographic and
biometric information, which they can use to identify them
12.3 Enrolment Station is the system, which does the anywhere in India, and to access a host of benefits and services.
enrolment, capture. The enrolment set-up includes a The number (referred to until now as the 'UID') has been named
computer, the biometric devices and some accessories. Aadhaar, which translates into 'foundation', or 'support'. This
word is present across most Indian languages and can therefore
12.4 Resident is a person who undergoes the enrolment be used in branding and communication of the UIDAI program
capture process and gets a UID from the government. across the country.
12.5 AADHAAR Number is a 12-digit number issued by It is believed that Unique National IDs will help address the
the government as proof of identity and residence in India. factors effecting the elections, poverty, terrorist threats etc. so
that an effective action can be taken to control the unwanted
12.6 Central ID Data Repository (CIDR) a repository situations or circumstances.
regulated and managed by the UIDAI. It issues
AADHAAR numbers, updates resident information and
authenticated the identity of residents as required. FUTURE SCOPE
12.7 Operator The enrolment operator who captures the UID cards distribution will start on a large scale in 2011. So in
resident’s data on the field and maintains the details of the country like India where a language or culture changes after
resident. every couple of kilometers traveled, where the people living in
the interiors are not educated enough to know their rights,
the implementation of UID project is comparatively
tougher than U.S. or Europe. Let’s see how revolutionary
results it will come up with.

REFRENCES

1.
http://uidai.gov.in/index.php?
option=com_content&view=article&id=15
3&Itemid=13

2. http://uidai.gov.in/index.php?
option=com_content&view=article&id=14
9&Itemid=189

3.
www.uidai.gov.in