The project is the enrolment. Everything else is easier.
Software configuration takes weeks. Getting fifteen thousand people to physically appear, one at a time, and place a finger on a scanner takes planning, communication and a realistic view of how many stations you can staff. We plan the deployment around that reality rather than around the software.
Five phases
Duration is quoted as a range against your population size and the number of enrolment stations you can staff, and it is confirmed in the discovery phase rather than assumed at proposal.
Discovery and design
Process mapping, verification point definition, credential design, integration scoping, data protection assessment. Output: a signed configuration specification and enrolment plan.
Configuration and integration
Platform configuration, credential design sign-off, integration build and sandbox testing, device provisioning.
Pilot
A bounded population — one faculty, one department, one site. Enrolment, card production, live verification. Output: measured throughput and a defect list closed before scale.
Mass enrolment
Multiple stations, scheduled by cohort, with self-service pre-enrolment reducing time at the desk. Card production runs in parallel.
Go-live and handover
Verification points activated, administrator and operator training delivered, documentation handed over, support transitioned.
What we need from you
Stated plainly, because deployments slip on these and not on the software.
- A named project owner with authority to make configuration decisions
- Access to the existing population data for pre-loading biographic records
- Physical space and power for enrolment stations during the enrolment window
- Institutional communication to the population about when and where to attend
- Sign-off on credential design before production begins
Support
- Named support contact and defined channels
- Response and resolution targets by severity, set out in the service schedule
- Device maintenance and replacement terms
- Administrator refresher training
- Platform updates included
Training is part of the deployment, not an afterthought
A biometric system fails at the point where an operator who was never trained decides that waving people through is faster than following the exception process. Administrator and operator training is delivered before go-live and refreshed afterwards, and the exception process is documented rather than improvised.
See Biolog running against your own process.
A working session with our team, not a slide deck. Bring your enrolment volumes, your verification points and your awkward edge cases. We will show you how Biolog handles them.