Starting point: readers in place, no punches in time tracking
The plant runs a working access control system with readers at gates and production entrances. The HR department needs entry and exit data to settle working time, but the punches stay in the KD system and never reach time tracking. Every month closes with manual completion of hours.
Replacing readers or controllers would mean cost, gate downtime and months of negotiation with the vendor. The plant chose a path where the readers stay and only what the KD system sends onward changes.
Solution: InnerWeb receives KD events
InnerWeb does not produce or replace readers and access cards. It receives card punch events from the KD system via a webhook and links them with qualifications, permits, attendance and time tracking. This is the deployment pattern at this packaging manufacturer: integration of card punches from the KD system into time tracking, according to a specification for the KD vendor.
The specification describes which fields each event contains, in what format and how often it is sent. The KD vendor works on its side, and the plant's team does not need to know the internal tables of the access system.
What goes into the specification for the KD vendor
The specification is short and concrete, because the KD vendor has to implement it in existing software.
- Card or employee account identifier, in a form agreed between the systems.
- Reader identifier, matching the location defined in the system.
- Event time from the reader, with time zone.
- Direction of passage (entry or exit) and the event identifier assigned by the KD system.
- Retry behaviour when the receiver is temporarily unavailable, and webhook authentication with a token of limited validity, renewed automatically by the integration.
Example punch pairing parameters in the specification
What to check when reviewing the data
Importing accounts from the KD system does not replace the punch log: the history of entries and exits requires a separate event specification, in which the KD system sends each punch as a separate event in real time.
The second pitfall concerns locations. A punch from a reader without an assigned place, that is an action point, does not trigger a training alarm. Reader configuration must match the locations in the system, otherwise the event arrives but has no effect.
The third point is event content. The specification requires the KD system to send the reader event time, the direction (entry or exit) and the event identifier. The rules for pairing entries with exits and rejecting duplicates are set together with the KD vendor, for example a pairing window of up to 13 hours and a duplicate within less than 180 seconds. We describe them on a separate implementation notes page for the punch webhook.
Role of HR and the KD integrator
The HR department is responsible for what belongs in time tracking: the scope of hours, rounding rules and how missing punches are marked. The KD integrator is responsible for delivering events in the agreed format. InnerWeb provides, on its side, the receiving, the linking with the account and a view for authorised persons.
The split is clear: readers and cards are the KD vendor's matter, tracking rules are HR's matter, and connecting the data is a shared matter described in the specification. This way neither party changes the other party's system.
Conclusions for a similar plant
First check what the KD system actually records: a full log with direction, or only the last login. Then describe the event fields and send the specification to the KD vendor together with a request for an implementation date. Finally, verify that every reader has an assigned place in the system.
This order allows the integration to start without replacing hardware. If the plant later chooses a new card type, for example DESFire, the permission logic in InnerWeb stays unchanged.
What to check before starting the integration
Before sending the specification to the KD vendor, check three things. First, whether the KD system keeps a full log of punches or only the last login of an account. Second, whether the account identifier in KD matches the identifier in the permissions system. Third, whether the plant's network team allows outgoing traffic from the server, because if it is blocked, another receiving channel and queuing of events on the KD side must be agreed.
This list takes one meeting with the KD vendor and shortens later corrections. It requires no changes to readers or to KD software beyond sending events according to the specification.
Video
Frequently asked questions
Do KD readers have to be replaced for the integration?
No. The pattern assumes integration according to a specification for the KD vendor, without InnerWeb readers and without replacing the existing ones.
What if the KD account import shows only the last login?
Then a separate event specification for punches is needed. The last login does not replace a register of entries and exits with direction.
Why did a reader punch not trigger the training alarm?
Usually the reader has no assigned place, that is an action point, in the system. Reader configuration must match the locations.
Want to connect KD to time tracking without replacing readers?
We will prepare with you a specification of events for the KD vendor and show how punches reach the records. Book a call.
Let's talk