What exactly we call the scan window
The scan window is the time interval in which repeated taps by the same person are treated as one. It prevents an entry and an exit from being recorded after a code is accidentally held to the scanner twice. The window is asymmetric, meaning it has different limits before and after an event, depending on whether the person is considered to be on site.
An important distinction: the scan window is not the hourly window of a visit. A planned visit is equivalent to a one-day permit, without a time, and the day is counted according to the local time of the server. Matching arrival times to the security shift is done in the invitation plan, while the scan window applies only to repeated taps.
Why the window is asymmetric
The full window, by default 3 minutes, applies only when the person's last entry is an entry and the next scan would record an exit. In all other cases, that is when the person is outside, after a refusal or after automatic checkout, the short window of 5 seconds applies.
The reasoning is related to safety. An exit that is suppressed for too long means someone stays on the evacuation list longer than necessary, which is an organizational cost. A suppressed entry means the person is on site but missing from the rescue document. The two errors are not equal, so the same number of minutes cannot apply in both directions.
The price of the solution and why it is acceptable
Two scans at the exit more than 5 seconds apart record an exit and then an entry, so the person who left appears as present. This is the safe direction: the list has rather too many people than too few, and the excess is explained during settlement.
Scan window depending on the person's state
Night shifts: what to assess before going live
On night shifts at a chemical plant one guard often stands at the gate, traffic is light but concentrated around the shift change. Before setting the window, check how many people pass the gate within a few minutes at peak times, and whether the scanner is operated by people experienced in using it.
The default value is sufficient in most plants. Consider changing it only after collecting data over several weeks: if many repeated taps at the exit are visible, shortening the window reduces the number of false exits, but increases the risk that someone exits twice.
- Measure the traffic peaks at the gate against the shift roster.
- Check that the scanner is well mounted and does not force repeated taps.
- Do not change the window before collecting data over several weeks.
- Record the decision and the owner of the setting.
Two safeguards against a double scan
The system applies two safeguards. On the server side a 5-second window applies, during which another scan of the same person does not record a new event, and the guard still sees the person's card. On the browser side additional suppression of an identical code within a very short time reduces unnecessary calls, but it does not replace the server's decision.
For implementation this is an important point: the setting you change in the panel concerns the entry window, not the internal suppression of the scanner. So do not look for the problem in the settings when the scanner reports a code twice within a fraction of a second.
Link with automatic checkout
A person who remains on site for longer than 12 hours is checked out by a scheduled task every 3 hours. On night shifts with long working hours it is worth checking whether anyone really exceeds this threshold, because a checked-out person disappears from the list of people present. The scan window and automatic checkout are two different mechanisms, but both affect the reliability of the evacuation list, so assess them together.
After automatic checkout the short window of 5 seconds applies, so the person's first subsequent scan is recorded as an entry.
Sample calculation: the effect of the window setting
Assume, for example, a night shift with 60 taps at the exit within 30 minutes and 3% accidental repetitions. That is about 2 repetitions. With the full window for the exit, a repetition is suppressed, so the list remains correct. With the window shortened to 5 seconds, a repetition after 8 seconds would record an exit and an entry, so the person would appear on the list. These are assumptions for your own measurement, not data from a specific plant.
Repeated taps at the exit on a night shift
| Parameter | Value |
|---|---|
| Exit taps in 30 minutes | 60 taps |
| Share of accidental repetitions | 3 % |
Result: about 2 repetitions in 30 minutes, suppressed by the full window
Note: Sample calculation based on the assumptions above; the actual share must be measured.
Video
Frequently asked questions
Does the scan window limit the visit hours?
No. A planned visit is equivalent to a one-day permit, without a time. The window applies only to repeated taps.
Why is the entry window shorter than the exit window?
Because a suppressed entry means a person on site who is missing from the evacuation list, while a suppressed exit only overstates the list.
Can I change the window value?
Yes, in the installation settings, but it is recommended to change it only after collecting data over several weeks of operation.
What about a person checked out automatically?
After automatic checkout a short window applies, so the first subsequent scan is recorded as an entry.
Set the scan window to your shifts
We will go through your shift roster and gate traffic with you to assess the settings before going live. Book a conversation with the InnerWeb team.
Let's talk