Where the loss of time comes from
A replacement card has to be blocked in the system, a new one issued with a new number and a new link to the person, the reason recorded in the register, and the permissions updated. Each of these steps is short, but together they engage two units: security and HR. Because a reported lost card should be blocked at once, part of the work happens outside HR's working hours and lands on its desk the next day.
Duplicate accounts generate a second kind of loss. When a person has two active accounts, the training result may land on the account without a card, while the account with the card still reports missing training at the gate. Security then has to establish what happened, and HR or the training department has to indicate which account is the right one.
Why duplicate accounts are not merged automatically
Automation is tempting: the system compares surnames and merges similar accounts. In practice this is risky. The system never merges or redirects an active account on the basis of surname alone, because people from one crew with similar surnames could be confused.
A measurement of the surname similarity threshold confirms this. True duplicate pairs of accounts scored from about 83, different people from the same company at most about 74, and brothers about 83, so the score alone is not enough for automatic merging. That is why the merge is performed by a person, using a command with a preview mode before execution, and the command refuses to act for a different company, an administrator account or a source with a card.
Result of the measurement at one installation
A measurement at one installation with a card import found 47 pairs of duplicate accounts, of which 46 were merged. Narrowing the alert to cases with training on an account without a card reduced the number of candidates from 45 to 0. The target is for the number of such pairs to be 0, and a daily alert watches that new cases do not come back.
Hours a month before and after tidying up the register
- Before the clean-up
- After the clean-up
Sample calculation: hours per month
The calculation below is a sample. We assume a plant of 800 people, 16 replacement-card exchanges a month and 20 cases of duplicate accounts a month. Exchanging a replacement card takes 45 minutes of security and HR time in total, so 16 times 45 minutes gives 12 hours. Explaining one duplicate account takes 30 minutes, so 20 times 30 minutes gives 10 hours. Together, 22 hours a month.
At an assumed rate of PLN 90 per hour the cost is PLN 1,980 a month, or PLN 23,760 a year. The input figures should be replaced with your own: the number of exchanges from the card register over the last 12 months and a sample of a few cases with timed measurements.
Return on tidying up the register
Tidying up the register is a one-off effort: checking the accounts, merging the pairs, completing the reasons for changes and establishing who owns each card. In the sample calculation we assume 40 hours of work at PLN 90 an hour, which is PLN 3,600. If the number of hours falls by half after the clean-up, the saving is 11 hours a month, or PLN 990 a month and PLN 11,880 a year.
The return on the clean-up is then about 3.6 months. The result is sensitive to the assumption about the drop: if the drop is one quarter, the payback lengthens to about 7 months. That is why it is worth calculating two variants and deciding on the basis of the pessimistic one.
How to keep the effect after the clean-up
Without procedures, a clean-up wears off after a few months. Three things make the effect last: a card register with full fields (number, person, issue date, status, reason for change and operator), a daily alert on pairs of accounts with training on an account without a card, and a quarterly review of the register.
InnerWeb links card scan events with qualifications, permits and attendance, so at the gate you see both the card and the training status. This reduces the number of cases in which security has to search by hand for the reason a person was refused entry.
Hours a month on replacement cards and duplicate accounts
| Parameter | Value |
|---|---|
| Number of people in the plant | 800 people |
| Replacement card exchanges | 16 exchanges a month |
| Time of one exchange | 45 minutes |
| Duplicate accounts | 20 cases a month |
| Time to explain an account | 30 minutes |
| Hourly rate | 90 PLN per hour |
| One-off tidying up | 40 hours |
| Drop in hours after the clean-up | 50 percent |
Result: 22 hours a month and PLN 1,980 a month before the clean-up; after it 11 hours and a saving of PLN 990 a month, payback about 3.6 months.
Note: Sample calculation on the assumptions above. Take your own figures from the card register for the last 12 months.
Video
Frequently asked questions
Where do I get my own figures for the calculation?
From the card register: the number of replacement exchanges over the last 12 months. Time one activity on a sample of a few cases.
Can accounts be merged automatically?
Not on the basis of surname alone. The merge is performed by a person after reviewing the changes, and the command refuses to act for a different company, an administrator account or a source with a card.
What happens to the data during a merge?
The better training result moves to the account with the card, and the account without a card is marked as deleted with a reference to the target account, without erasing any data.
Do the figures in the calculation apply to our plant?
No. It is an example on explicit assumptions, and the result has to be recalculated on your own data.
Let's count the hours in your plant
We will help collect the data from the card register and prepare a calculation with your own figures.
Let's talk