Onboarding Process Submitted
Onboarding Process Submitted
SWITCH TO
DEVICE AND
DEVICE MGT CENTER PRODUCTIO
PERSONNEL
ONBOARDING DEPLOYMENT AND CONTINO
ACTIVATION
ENROLMEN
OVERVIEW OF ENROLMENT
CENTER DEPLOYMENT CONTD
CURRENT SYSTEM VS NEW SYSTEM
I. The management of FEPs and Devices is currently carried out
with the central billing system.
II. The new on-boarding process will be carried out with the new
device management platform.
III. This current system works with all NIMC’s enrollment
application but the new platform currently works with the
android Seamfix application while other application(windows
and Contactless) are work in progress.
FEP TECHNICAL ONBOARDING
PROCESS
Approval; once FEP has completed BDCS and Legal documentation all
required documents for technical onbaording are issued to FEP
The listed document should be submitted before the commencement of
setup.
i. VPN form.
ii. Enrolment Environment Setup checklist.
iii. System specifications sign off.
iv. Risk assessment checklist (Pre-license check list
application by Information
security unit).
Creation of FEP on the Device management Portal; NIMC’s Tech Team
creates Profile for the FEP and email containing the link to the platform
is automatically generated to the provided organization email that will
be used to login to the device management platform Portal
DEVICE MANAGEMENT
ONBOARDING REQUIREMENT
Organization’s
Approval
details
FEP onboarding
CENTER DEPLOYMENT.
CENTRE READINESS
• I. Communication to NIMC’s on identified centre by FEP
• II. Environment Certification:FEP visit NIMC state office to document
the environment setup.
• III. NIMC State IT and Operation Staff carry out the certification using
the following documents to physically certify the readiness of the
enrolment environment for setup:
• iv. NIMC state personnel ensures the FEP attains NIMC standard in
the environment setup with all necessary guidanc
•
•
CENTER DEPLOYMENT cont’d
• CENTRE DEPLOYMENT
Centre is deployed in line with the ERC checklist provided.
Centre is setup to ensure an adequate capture environment with
emphasis on the following
Ensure adequate lighting.
Deploy a smooth surface grey backdrop for all systems for
enrolment.
Deploy lights to provide adequate illumination for the
applicant’s facial capture
VI. The NIMC tech team forwards signs off on the ERC checklist and
forwards to Headquarters for centre creation
VII.Centre is created and can be viewed on FEPs platform.
DEVICE ACTIVATION AND
• CERTIFICATION
A. DEVICE ON BOARDING
FEP On-boarding admin downloads Enrolment application
Application and sends activation request and email is automatically
generated to the onbaording admin email
On-boarding admin clicks the link in the email and this generates the
workflow for approval to the FEP IT admin
FEP IT Admin approves, assign to a center and awaits checks and
approval from NIMC Admin
NIMC Admin approves after necessary checks and device is automatically
on test after activation
2 TEST The is the state of the device when onboarding has been approved and at this point
the enrolment software can only do test enrolments
3 ACTIVE This state would be request for by the enrolment application after successful test
enrolment has been carried out.
4 INACTIVE This state represents when a system has been inactive for a specified period.
5 DISABLED This state represents when an admin or authorised user choses to deactivate the
device.
6 RETIRED This state represents when as system no longer is being used for enrolment or stolen
or lost.
7. TRANSFERED This state indicates that the device has been moved to another FEP
ONBOARDING ENROLMENT PERSONNEL
After successful training exercise of enrolment agents, certificates is
issued to all participant and their list are uploaded to the device
management platform.
Users On boarding
I. FEP IT Admin creates Enrollment Personnel on the device management
platform by selecting from the pre-populated list and emails sent to
the provided email.
II. Users login in to activated devices
III. Users login to on-board their biometrics on activated devices
IV. Maximum of 5 users per device