Division of responsibility: who does what
InnerWeb is a software producer, not a maker of access control readers or cards. The readers, the KD vendor's mobile app and the management of credentials stay on the KD vendor's side. InnerWeb receives identifier punch events from the client's KD system and links them with qualifications, permits, attendance and time records.
This split simplifies the project, because there is no reader replacement and no second system opening doors. It does require a clear clause in the contract with the vendor: who delivers the events, in what format and with what delay.
Stage 1: specification of the punch event
The first thing to settle is the scope of fields in the event. The minimum is the person's identifier (not the card number printed on the plastic, but a stable identifier from the KD system), the punch time, the passage location and the direction. Without direction attendance cannot be counted, and without a stable identifier the event cannot be linked with qualifications.
The event should arrive with as little delay as possible, and the vendor should describe what happens when the link between the KD system and InnerWeb disappears: buffering and resending, or loss. This has to be measured in the pilot, not taken from the product datasheet.
Gate events: KD vs InnerWeb in the pilot trial (example to be measured)
- KD system
- InnerWeb
Stage 2: mapping people and identifiers
The second stage is connecting the identifier from the KD system with the person in InnerWeb. A plant usually has three sources of people: HR, the KD system and the contractor register. The integrator should settle one source of truth for the identifier and describe what happens to a person who exists in one system and not in another.
A QR code in the phone can work next to this stream: events from the gate enter InnerWeb by two routes, from the KD punch and from a code scan. Identifying the string follows one rule on the server side, so two versions of the logic do not arise.
- Event format: identifier, time, passage, direction.
- Delay and behaviour when the link is lost.
- One source of truth for the person's identifier.
- Handling people present in one system and absent in the other.
Stage 3: pilot and pitfalls
It is worth starting the pilot at one gate and one group of people, not for the whole plant. Compare the number of events in the KD system with the number of events in InnerWeb for the same hours. The difference shows whether the vendor loses punches or the person mapping has gaps.
The most common pitfall is changing a person's identifier on the KD side without notifying the integrator, for example after issuing a new mobile credential. Write into the contract that a change of identifier is an event the vendor also sends to InnerWeb.
Stage 4: maintenance and changes
After deployment the plant's IT should keep a simple register of changes on the KD vendor's side: a new version of the mobile app, a change of the event format, new readers. Each of these changes may alter the fields in the event.
InnerWeb works as an independent system supplementing the client's existing systems (KD, time and attendance, HR, ERP) and does not require GPS for location. As a result, the failure of one of these systems does not stop the others, and the QR code remains the backup path.
Video
Frequently asked questions
Does InnerWeb replace readers?
No. Readers and mobile credentials stay on the KD vendor's side, and InnerWeb receives punch events.
Does a mobile ID need a QR code?
No, but the QR code can be a second path for guests and contractors, and a backup path.
What should we agree in the contract with the KD vendor?
The event fields, the delay, the behaviour when the link is lost, and the notification of changes to a person's identifier.
Sources
Let us write the punch event specification for the KD vendor
We will help the integrator prepare the list of fields and link failure scenarios. Let's schedule a short call.
Let's talk