Any idea on reliability? Maybe take a squizz on the way by tomorrow and see what make?
The only time it fails is if someone doesn't place their finger correctly. And whoops, forgot to check the brand, I'll do it tomorrow.
Have the staff been informed that they will be required to "sign in" and possibility of their finger print being recorded?
I don't think they will take to kindly to having that forced down upon them.
My work tried it, but because people don't want to have to filter through the main office to get places, and would much rather go directly to their workplace they just don't do it. And no one checks.
Also, with regards to storing fingerprints, it is a one way process, you can't get the fingerprint back from the DB record. Well that's at least the case with the sagem sdk.
Pure interest how is that possible? Surely if you can query the db you can get its data back?
Pure interest how is that possible? Surely if you can query the db you can get its data back?
Maybe I'm overthinking it but surely all fingerprint comparison uses an algorithm similar to each other as such if you could work out how it compares prints you could create a fingerprint that contains the relevant comparison points.
Obviously this is far above your average employee to log their buddy into work but I was just curious about the one way claim.
What's the point in a non mission critical secure workplace, people will immediately know if you haven't shown up for work?
I'm assuming here it's being used for payroll purposes and not access control.
there is a high degree of trust placed on staff in our work place to keep to their working hours and record their over time legitimately. unfortunately 2 or 3 staff members appear to not be playing fair.
the hope is that the implementation of a clocking system will act as a 'polite' reminder to be a bit more honest regards breaks and time keeping in general - rather than having to go straight into the whole issuing warnings/disciplinary etc