Why the card swipe alone is not enough
Receiving a swipe from the access control system does not yet mean an entry in the gate register or in the working time records. A webhook alone, without mapping to entries, does not produce a time record. A swipe is an event, while a record requires a pair: the start and the end of presence.
For the records, the access control system sends events with a direction (entry or exit) and an event identifier, and InnerWeb accepts them through an authenticated webhook. The pairing rules are set in the specification with the access control vendor.
Rules for pairing entries and exits
Two rules are worth setting in the integration specification. An entry and exit pair should have a window covering a shift together with longer overtime (in the sample settings, up to 13 hours). A repeated scan within a few seconds is ignored, so a double tap of the card does not create a false pair.
The access control system sends events in real time, with the event time read from the reader. For the records this is a requirement: a delayed batch from the access control system would distort the start and end times of work.
What happens when there is no exit
When a person does not swipe the card at the exit, the pair is not closed within the 13-hour window. Such a case goes to the exception queue, and the person may receive a phone call reminding them about the missed exit scan. In this way gaps are explained on the same day, not at the end of the month.
Swipe pairing rules
The mRCP module: views, exceptions, reminders
Gate scans, also used for the evacuation list, can build the working time records (mRCP) with daily, monthly and yearly views, exception queues and phone reminders about a missed exit scan. The module is disabled by default and is switched on by the administrator, so it must be planned in the implementation schedule.
One set of scans therefore serves two purposes: the evacuation list and the records. For the plant this means fewer systems to maintain, and for security fewer actions at the gate.
Card swipe and location
A card swipe in the access control system only says that the person passed a point; it does not say where the person is after passing it. Connecting it with the location on the map and with the evacuation list is the added value of InnerWeb. Location works without GPS: the position from signals of several transmitters is averaged on the map, and in a building there is roughly one transmitter per 100 to 200 m². Working time records are based on the gate, but in case of an evacuation what matters is who is in which place, not only who came in the morning.
Four-stage implementation plan
Stage one: the webhook and the swipe place templates, without records. Stage two: mapping swipes to entries and verification in the gate register. Stage three: switching on mRCP by the administrator and a review of the daily view with the supervisors. Stage four: launching reminders about a missed exit scan and a weekly review of the exception queue. At each stage compare the number of swipes in the access control system with the number of entries in InnerWeb, to detect missing readers early.
Checklist
Video
Frequently asked questions
Does mRCP work right after the integration?
No. The module is disabled by default and is switched on by the administrator, and the swipes must be mapped to entries.
What about a person who does not scan the exit?
The pair is not closed within the 13-hour window, the case goes to the exception queue, and the person may receive a reminder call.
Does the time record replace the evacuation list?
No. The same scans serve both purposes, but the evacuation list also requires location information.
Let's start the records from your card swipes
We will show mRCP on swipes from your existing access control system and agree on a plan to switch on the module. Book a call with the InnerWeb team.
Let's talk