What the integration specification requires from KD
The KD system sends events in real time, and InnerWeb receives them through an authenticated webhook. Each event contains the reader time, the location, the person's data, the direction (entry or exit) and the event identifier. The authentication token has a limited validity period and is renewed automatically by the integration.
For the implementation team this means that the pairing rules are a design decision agreed with the KD vendor, not a setting. It is worth making that decision before launch, because the gate scans depend on it as a reliable basis for the evacuation list and working time records. Some readers in the client's KD system do not distinguish direction; in that case the pairing rules described below become part of the specification.
Stage 1: an entry-exit pair up to 13 hours apart
An example rule to record in the specification: the first swipe of a person is an entry, and each following swipe that occurs within 13 hours is an exit. A longer gap is treated as the start of a new working day. The 13-hour value covers a 12-hour shift with a margin for travel to and from the site.
With three swipes by one person in a short time, the pair cannot show which one is the correct one. That is why a second rule belongs in the specification: rejecting duplicates.
Thresholds of the swipe pairing rules
Stage 2: duplicates within less than 180 seconds
The second rule to agree with the KD vendor: another swipe of the same card within less than 180 seconds is rejected as a duplicate. This protects against a card being presented twice, against a retried send by the KD system, and against a swipe registered by two readers in one airlock. The event identifier helps tell a retry apart from a new swipe.
A pitfall: a person who really enters and leaves within three minutes, for example after forgetting something in the car, will be treated as a duplicate. It is worth informing security about this, because it is rare but happens at the main gate.
Stage 3: mapping to the gate register and mRCP
On some installations, card swipes from the KD system initially appear as the account's last login time, not in the gate entry register or in working time records. That is why the webhook on its own, without mapping to entries, does not give RCP.
Gate scans, which are also used for the evacuation list, can create working time records (mRCP) with daily, monthly and yearly views, exception queues and reminder calls about an exit that was not scanned. The module is switched off by default and is turned on by the administrator. Stage three is therefore the decision to enable the module and to establish which swipe locations are the plant's gates.
Stage 4: exceptions and unscanned exits
A person who leaves without swiping leaves an open pair. The exception queue in mRCP shows such cases, and a reminder call about an unscanned exit lets them be closed. Implementation rule: the first weeks after launch are the time when security and HR review exceptions every day and teach people to swipe the exit as well.
- decide which readers are the plant gates
- decide who reviews the exception queue every day
- inform security about the 180-second rule
- prepare a message for employees about swiping the exit
Development scope of the specification with the KD vendor
When KD events carry the direction and the identifier, pairing rests on data, and the time rules act as a safeguard for readers without direction. It is worth recording this in the specification as a requirement, because a rule based on time alone always has edge cases.
A card swipe in KD only says that a person passed a point. It does not say where the person is after passing it, so linking to the location on the map and to the evacuation list remains the added value of InnerWeb, regardless of the pairing method.
Video
Frequently asked questions
Should the KD system send the swipe direction?
Yes, the integration specification assumes the event time, the direction and the event identifier. For readers without direction, the pairing rules are agreed with the KD vendor.
Why is the pair window 13 hours?
It covers a 12-hour shift with a margin for travel to and from the site. A longer gap means a new working day.
Does mRCP work as soon as the webhook is connected?
No. The module is switched off by default and the administrator turns it on, and the swipes have to be mapped to the gate entries.
Planning working time records from KD swipes?
Book a call about pairing entries and exits and switching on mRCP at your plant.
Let's talk