Where time is lost at the gate
Minutes at the gate are lost through three kinds of event. The first is a slower scan, when the screen is dimmed or the code is smudged by a film. The second is a failed scan, after which the guard asks for another attempt or moves to the emergency procedure. The third is a report that reaches the security supervisor because the person claims that 'the phone does not work'.
The time of a phone scan at the gate can be a few seconds longer than the time of a card tap, when the screen is dimmed or smudged. This difference is a time to be measured by the plant during the pilot, not a universal figure, so in the calculation it is only an assumption.
Calculation assumptions
We assumed a gate with 400 scans a day over 250 days a year. A phone scan takes on average 3 seconds longer than a card tap, so the additional time is 1,200 seconds, or 20 minutes a day.
Five percent of scans, or 20 a day, do not succeed the first time. Handling one such case takes the guard 90 seconds, which gives 30 minutes a day. In addition, 3 reports a day reach the security supervisor, at 10 minutes each, which is 30 minutes a day. Rates: PLN 60 an hour for a guard and PLN 90 an hour for a supervisor.
Security minutes per day by cause
Result
The guard's time is 50 minutes a day, or 12,500 minutes, about 208 hours a year, which at PLN 60 an hour gives PLN 12,500. The supervisor's time is 30 minutes a day, or 7,500 minutes, 125 hours a year, which at PLN 90 gives PLN 11,250. Together PLN 23,750 a year, or 80 minutes of work a day.
This result is not an argument against the QR code, but a measure of what is worth reducing. Each reduction of the share of failed scans by one percentage point saves, in this example, 4 scans a day, or 6 minutes of guard time a day.
How to measure it in the pilot
Measurement requires nothing beyond a sheet of paper and a watch, and the system helps with one thing: a repeated scan of the same person within 5 seconds does not create a new entry event, so the log does not overstate the number of entries through repeated attempts.
For two weeks the guard records three numbers: the number of scans, the number of failed attempts and the handling time. The supervisor records the number of reports and their time. After the pilot you substitute your own values into the calculation.
- Number of scans per day at each gate
- Share of scans that fail the first time
- Average handling time for a failed scan
- Number of reports to the security supervisor and their time
- Most common cause: brightness, film, code size, browser
What reduces the cost
For 'phone not working' reports the greatest effect comes from removing the causes, not from speeding up the guard. The security panel reads the code from a HID scanner, a USB-COM scanner and a camera, so the plant can choose a scanner suited to the conditions at the gate. The default size of the code label is 86 x 54 mm, and the code is not printed smaller than 13 mm, which reduces read errors on the printout.
The second factor is the preparation of the workforce. A test of employees' phones before the pilot detects screen brightness, films and browsers before the problem appears at the gate. The third is the emergency procedure: when a scan fails, the guard knows the next step.
How to present the result to management
The head of security should show three numbers, not one: minutes a day, the share of failed scans and the most common cause. The annual cost alone can be misleading, because it depends on rates that the management knows better. The share of failed scans and their causes, on the other hand, show what can be fixed cheaply.
Record also what the measurement does not cover. It does not count the queue behind the gate at peak hours or employee irritation. If the plant wants to include them, it can add a second measurement: the time from approaching the gate to the opening of the passage during shift changes.
What to do with the result after the pilot
When the share of failed scans is higher than expected, start with the causes that cost least: an instruction for the workforce, a change in scanner settings, a better label printout. Only then consider changing the equipment at the gate. The security panel reads the code from three sources, so often it is enough to change the way of reading, not the whole station.
Enter the pilot result into the same calculation in place of the assumptions and compare it with the example version. The difference will show whether the plant has an organisational or a technical problem.
Example calculation: handling gate reports
| Parameter | Value |
|---|---|
| Scans per day | 400 scans |
| Working days per year | 250 days |
| Additional time of a phone scan (to be measured) | 3 s |
| Failed scans | 5 % |
| Handling time for a failed scan | 90 s |
| Reports to the supervisor | 3 per day |
| Time per report | 10 min |
| Guard rate | 60 PLN/h |
| Supervisor rate | 90 PLN/h |
Result: Guard: PLN 12,500 a year (208 hours). Supervisor: PLN 11,250 a year (125 hours). Total PLN 23,750 a year.
Note: Example calculation based on assumptions to be replaced. The plant measures the extra time of a scan during the pilot.
Checklist
Video
Frequently asked questions
Are the 3 seconds of additional scan time a figure from an implementation?
No. It is an assumption of the calculation. The scan time depends on the screen, the scanner and the gate, which is why the plant measures it during the pilot.
Does a repeated scan inflate the number of entries?
No. A repeated scan of the same person within 5 seconds does not create a new entry event.
How can the share of failed scans be reduced?
Test the workforce's phones before the pilot, choose a scanner suited to the conditions at the gate, and keep an eye on the code size. Details are in the guide on testing phones.
Plan the measurement in the pilot
We will prepare a measurement sheet for security and show a QR code scan from a phone at the gate on an example plant.
Let's talk