InnerWeb
Skip to main content

KD integration with permits and RCP: guide

The IT department can link access card events from the KD system with qualifications, permits and RCP (time and attendance) without touching the readers: the KD system sends an event, and the supporting system receives it and matches it with the employee's data. The guide walks through six steps, from the event specification to the gate test, and points out three pitfalls that most often cost weeks.

3
fields required in an event beyond the employee identifier: reader time, direction, event identifier
Source: card
6
steps from the specification to the gate test
Source: card

Principle: we do not touch the readers

InnerWeb does not manufacture or replace readers and access cards. It integrates with the client's existing KD system: it receives card access events through a webhook and matches them with qualifications, permits, attendance and RCP. For the IT department this means a simple line of responsibility: the KD vendor is responsible for readers, cards and controllers, and the supporting system is responsible for the logic around the access event.

As a result, the integration needs no hardware replacement, and a change of card technology on the KD side, for example a move to DESFire, does not require a change in permit logic. The supporting system remains an independent system alongside the existing KD, RCP, HR and ERP systems.

Step 1: event specification for the KD vendor

The first document is the access event specification that the IT department hands to the KD vendor. The pattern from a deployment at a packaging manufacturer assumes integration of card access events from the KD system to RCP according to a specification for the KD vendor, without InnerWeb readers. The specification describes which fields the event should contain and how it is delivered.

The specification requires the following: the KD system sends events in real time, and each event carries the employee identifier in an agreed form, the event time read from the reader, the reader identifier, the direction of passage (entry or exit) and the event identifier. InnerWeb receives them through an authenticated webhook; access uses a token with a limited validity period, renewed automatically by the integration. The data minimization rule says we do not transmit the card number if the employee identifier is sufficient.

Step 2: match readers to places in the system

An access event from a reader without an assigned place, meaning an action point, does not trigger a training alert. The reader configuration must therefore match the locations in the system. The IT department maintains a table: the reader identifier in KD, the place name in the system, and the type of place, for example main gate, hall entrance or warehouse.

The table is completed together with security and occupational health and safety, because they know which doors matter for training and permits. An error at this stage is the most common cause of an "integration that works but does nothing".

Step 3: passage direction and event identifier

Passage direction and event identifier are requirements for the KD system, not extras. An event with a direction allows entries to be paired with exits and attendance to be counted, and an identifier allows a duplicate to be rejected when the same message arrives twice. The event time comes from the reader, so the order of events is reliable even when delivery of an event is delayed.

The rules for pairing entries and exits and for rejecting duplicates are set in the specification together with the KD vendor and the plant; this is not a ready-made function to switch on. A starting point for discussion is a pairing window on the order of a dozen hours and a duplicate threshold on the order of a few minutes, but for three-shift work the values must be adjusted, and the plant should accept the rules in writing. If the reader on the KD side does not know the direction, this is a technical fact on the KD system side and requires agreement on how the direction is supplemented in the specification.

Step 4: choosing the event delivery channel

The webhook is the simplest channel, but it is not always possible. When the plant network blocks outbound traffic from the application server, outgoing webhooks can be queued in an outbox table, and receipt happens through another channel agreed with the client. The IT department should settle this at the start, because changing the channel after launch means repeating the tests.

It is worth asking about the plant's network rules already at the specification stage: whether the KD server may initiate connections to the outside or only inside the network, and who manages the firewall rules.

Step 5: three pitfalls that cost weeks

The first pitfall is data that exists only as a trace. Importing accounts from the KD system does not replace the event stream: the attendance record requires a separate event specification with time, direction and event identifier, which a mere import of accounts cannot replace.

The second pitfall is different person identifiers in KD, RCP and the training system. If each system gives the employee a different identifier, linking events becomes manual. It is worth agreeing on one linking key before launch.

The third pitfall is no test on a real access event. A test event from the KD vendor's tool passes, while a real card tap at the gate does not, because the reader has no place in the table from step 2. The final test is performed with a card at the reader.

Step 6: evidence for the auditor

After launch the plant should have three documents: the event specification, the table of readers and places, and the test protocol with a card tap at the gate and the visible effect in the system. For the auditor this is a complete set of evidence that the integration works as described.

Add a contingency procedure to the documentation: what happens when events do not arrive. The plant should know who fills in missing events from the KD system, how, and within what time, and the rules are agreed in the specification with the KD vendor.

Video

Frequently asked questions

Does the integration require changing the readers?

No. The KD system sends events and the supporting system receives them. The readers and cards remain the responsibility of the KD vendor and the client.

What requirements must an event from the KD system meet?

The KD system sends events in real time, with the reader time, direction and event identifier. The rules for pairing entries and exits and rejecting duplicates are set in the specification with the KD vendor.

What if the plant network does not allow an outgoing webhook?

Webhooks can be queued in an outbox table, and receipt happens through another channel agreed with the client. This is settled at the specification stage.

Want to connect KD with permits?

We will pass the event specification to the KD vendor and launch the integration without touching the readers. Book a call or a demo.

Let's talk