Starting scenario
Consider a production plant with several staff gates. The access control readers record card swipes, but they do not distinguish entry from exit: the same reader is used in both directions, and the controller sees only an event with a card number and a time. This is a conceptual scenario based on a typical layout, not a description of a specific deployment.
The head of security wants to know who is on site at any moment. The HR department wants working time records with entry and exit times. Without direction, both questions stay unanswered, and replacing the readers with models that have separate entry and exit units would require costly rebuilding of the gates.
Concepts: zone, schedule, anti-passback
A zone is an area whose access is governed by the access control system, for example a hall, a warehouse or a laboratory. A schedule defines on which days and at which hours a given card may enter the zone. Anti-passback combines both concepts with direction: the system will not accept a second entry of the same card into the zone if it has not recorded an exit.
Hard anti-passback blocks the gate, while soft anti-passback records the violation and notifies security. In a plant without swipe direction the hard version is not safe to switch on, because an incorrectly paired event would block an employee at the gate.
Entry-exit pairs from 40 swipes per shift
- Without duplicate filter
- With 180 s filter
Solution: pairing swipes
The integration assumes that the access control system sends events in real time, with the time of the event from the reader, the direction (entry or exit) and an event identifier. When the reader in the client's access control system does not distinguish direction, this is a technical fact on the access control side, and the rules for pairing entries with exits and for rejecting duplicates are set in the integration specification with the access control vendor. Presenting the same card again within a few seconds should usually not count as a separate event.
InnerWeb receives card swipe events from the access control system through an authenticated webhook and links them with qualifications, permits, attendance and time records. It does not replace the readers: it integrates with the client's existing access control system, because it is a software manufacturer.
- Rules for pairing an entry with an exit: set in the specification with the access control vendor.
- Rejecting duplicates: event identifier and rules set in the specification.
- An odd number of swipes within the window goes to exceptions, not to an automatic decision.
Gate with scan control
Where the gate works with QR code control, the scan itself is a control act: the first scan with a green verdict records an entry, the second an exit, and a scan with a red verdict records a refusal. The system does not open the gate itself; the decision is carried out by a person or by the plant's existing automation.
Gate scans form the time records (RCP) with daily, monthly and yearly views, exception queues and period closing. In the plant scenario this means one source of truth about attendance, fed by access control swipes where cards are used and by scans where QR codes are used.
Effect and conclusions for the plant
In the example calculation, assume 40 card swipes in one shift at one gate, of which 6 are duplicates within 180 seconds. After rejecting duplicates, provided the specification allows it, 34 swipes remain, which gives 17 entry-exit pairs. Without the duplicate filter the system would see 20 pairs, and three of them would be false.
Conclusion: direction can be rebuilt from swipes alone, provided the pairing and duplicate rejection rules are set in the specification and ambiguous cases go to a person. Soft anti-passback gives security a signal about a card used twice without an exit, and the time records receive the pair needed to settle working time.
Pairing swipes at one gate per shift
| Parameter | Value |
|---|---|
| Card swipes per shift | 40 swipes |
| Duplicates within 180 s | 6 swipes |
| Pairing window | 13 hours |
Result: 34 swipes after filtering give 17 entry-exit pairs; without the filter the system would show 20 pairs, of which 3 are false.
Note: Example calculation based on the assumptions above; it does not describe a specific plant.
Video
Frequently asked questions
Does anti-passback require separate entry and exit readers?
Not always. When a reader does not report direction, swipes can be paired within a time window, and ambiguous cases can be sent to exceptions.
Does InnerWeb open the gate itself?
No. A scan with a green verdict records an entry, but the gate is opened by a person or by the plant's existing automation.
What about a card swiped twice within a few seconds?
A repeat swipe within a few seconds is usually treated as a duplicate, and the rule for rejecting it is set in the specification with the access control vendor, so that no false pair is created.
Rebuild direction from existing swipes
Let's talk about how to build attendance and working time records from the swipes of your access control system, without replacing the readers.
Let's talk