Scope of the integration and its limits
InnerWeb does not supply access control readers or cards. It receives card punches from the client's KD system via a webhook and links them with qualifications, permits, attendance and working time registration, and the integration specification is handed to the KD vendor. The client therefore does not replace readers or cards, and the existing infrastructure stays in place.
The boundary of responsibility is simple. The KD vendor is responsible for the readers, the cards and sending the event, while InnerWeb is responsible for receiving it, matching the person and recording it in the register. Whoever has a missing punch first checks whether the event left the KD system.
What the KD vendor must provide
The specification for the KD vendor describes the minimum set of event data. An event must unambiguously identify the person, the moment of the punch and the direction of passage, because entry and exit in the register are built on that basis. The exact field format is set from the integration specification, while below we describe the logic that IT should check.
Events are sent via a webhook, so the KD vendor must provide retries when the recipient is unavailable, and a stable identification of the person, for example by an employee number matching the InnerWeb account.
- Person identifier matching the account's employee number.
- Moment of the punch with an unambiguous time zone.
- Direction of passage: entry or exit.
- Gate or zone identifier, if it is to affect the evacuation list.
- Retries when the recipient does not respond.
What InnerWeb does with a punch
Gate scans, also used for the evacuation list, create working time records in the mRCP module: daily, monthly and annual views, a team console for supervisors, exception queues, period closing and timesheets in PDF. The module is disabled by default and switched on with a setting, so integrating punches is a separate decision from launching the module itself.
The evacuation list refreshes every 13 seconds, is built from gate scans and divides people into six groups: visitors, couriers, suppliers, plant employees, external firms with tabs per firm, and an uncertain group. The printout is one page per group, so the commander can hand the sheets to coordinators at the assembly point.
Asymmetry of error on the evacuation list
The list is designed around an asymmetry of error: a person listed although they have left costs an unnecessary search, while a person omitted is someone nobody looks for. In case of doubt the list shows more people, not fewer. For the integration this means that a missing exit punch does not remove the person from the list, so the KD vendor should ensure that exit events are complete, so the list does not grow for no reason.
What the IT department checks before go-live
The IT department should verify five things: reachability of the recipient address from the KD network, consistency of person identifiers, the time zone of events, behaviour during retries, and completeness of exits. Each of them can be checked on a pilot group of people before the integration is switched on for the whole plant.
The test should run on several people from different groups and go through a full cycle: entry, exit, entry without exit, and an attempt to send a duplicate event. The result is compared with the daily register view and with the evacuation list.
Pitfalls and division of responsibility
First pitfall: time zone differences. An event stored in UTC and read as local time shifts an entry by an hour or two and distorts working time. Second: a person identifier in KD different from the one in InnerWeb, which ends in the uncertain group. Third: no retries, so events from a period when the recipient was unavailable are lost.
All three can be detected with a test before go-live. The KD vendor should receive a checklist as an annex to the specification, and the plant should record the test results in the implementation documentation.
Checklist
Video
Frequently asked questions
Do the KD readers need to be replaced?
No. InnerWeb does not supply readers or cards and receives punches from the client's existing KD system.
What happens to a person with no exit punch in KD?
The evacuation list is designed around an asymmetry of error: in case of doubt it shows more people, not fewer.
Does mRCP switch on by itself?
No. The module is disabled by default and switched on with a setting.
Let's talk about integration with your KD
We will pass the integration specification to your KD vendor and go through the pre-go-live test with the IT department. Book a conversation with the InnerWeb team.
Let's talk