InnerWeb
Skip to main content

Service entry to a water treatment plant with a KD card: implementation scenario

A technician from an external service company swipes their card at the gate of a water treatment plant, and the system checks whether they hold valid qualifications and a permit for today's work. We describe a concept for a water utility in which an event from the existing KD access control system feeds permits and the attendance register, while InnerWeb replaces neither the cards nor the readers.

180 s
threshold for discarding duplicate swipes
Source: karta
13 h
window for pairing an entry with an exit
Source: karta

Scenario: service visit at the plant gate

The water treatment plant has an access control system with proximity cards and readers at the gate and at several technical doors. External companies visit the plant regularly: pump service, automation, chemical dosing. Until now the gate opened on the card alone, and whether the person had a work order and training today was checked by the duty officer from a paper list.

The utility wants a single card swipe to feed three things at once: a record of entry in the attendance register, a check of qualifications, and a link between the person and a work permit. This is an implementation scenario, not a description of a completed project. We show how such a chain can be built on the existing infrastructure.

How a KD event reaches InnerWeb

InnerWeb receives card swipe events from the access control system as HTTPS messages initiated by the utility's site, on port 443. The utility does not open any inbound ports. Authentication uses a technical account and a token with a limited validity period, renewed automatically by the integration, so from the IT side the pattern resembles other outbound integrations.

The KD system sends events in real time. Each swipe message carries the event time from the reader, the reader identifier, the person, the card number, the direction (entry or exit), and an event identifier that ensures idempotency. The rules for pairing entries with exits and for discarding duplicates, for example a window of up to 13 hours and a threshold of 180 seconds, are set in the specification agreed with the KD vendor. This way, a double swipe at a jammed gate does not corrupt the register.

Most important for the budget: the integration requires no replacement of cards or readers. InnerWeb is a software producer, not a maker of access control readers, so it uses what the utility already has.

  • the HTTPS message is sent by the KD system or its integration gateway
  • authentication: technical account and a token with a limited validity period, renewed automatically
  • fields: event time from the reader, reader, person, card number, direction, event identifier
  • rules for discarding duplicates are set in the specification with the KD vendor

Example parameters of the KD swipe integration specification

Example parameters of the KD swipe integration specificationHorizontal bar chart: example duplicate threshold of 180 seconds, pairing window of 46,800 seconds.010,00020,00030,00040,00050,000sDuplicate thresholdDuplicate threshold: 180 s180Pairing window (13 h)Pairing window (13 h): 46,800 s46,800
Source: Example parameters of the KD card swipe integration specification

What the system checks before the gate opens

When a permit is created, the system automatically checks whether the assigned workers hold the required, valid qualifications. This means a technician without current training or the qualification for work in a confined space will not be added to the permit at all, so on the day of the visit there is nothing to open for them.

The utility must still decide at which stage the KD event affects the gate. In the simplest variant, the swipe goes to the register and the duty officer sees in real time who entered and whether they had a permit. In the extended variant, the KD system receives information from InnerWeb that a given person does or does not hold a valid permit today, and the KD system itself decides whether to open. Such feedback has to be agreed with the KD vendor, not just configured in InnerWeb.

It is worth stating this clearly to plant management: InnerWeb provides the evidence and the verdict, while the decision to physically open the gate stays with the system that controls the lock.

Permit, attendance and the next step on site

The contractor's request and the permit issued to the contractor work on the same permit, visible on both sides. The service company submits the request, the plant operator accepts it, and on the day of work the card swipe confirms the person's presence on site.

On the contractor's screen, a green status with the label Working means clearance for the main works only. A team waiting for preparatory tasks sees an amber call to action. This matters at a plant where, before a tank is opened, it has to be isolated, pumped out and ventilated before anyone enters.

All permit changes are recorded with the author and the time, so after an inspection or an incident it is possible to reconstruct who admitted the contractor and when.

Talking to the KD vendor: what needs to be settled

Three things remain to be settled with the KD vendor: whether the system can send events via HTTPS POST, which readers are entry and which are exit, and how a card export works. Everything else is on the InnerWeb side.

It is good to hold this conversation before the first project meeting and to get the answers in writing. It shortens commissioning time and makes it possible to judge at once whether the register variant is enough or whether feedback to open the gate is needed.

Conclusions for the plant operator

One scan, three effects: an attendance entry, a check of qualifications, and a link to the permit. Start with one entry at one plant, compare the events with the manual register for two weeks, and only then extend to other sites.

Video

Frequently asked questions

Do we have to replace the card readers?

No. The access control integration does not require replacing cards or readers. InnerWeb uses events from the existing KD system.

Does the plant have to open inbound ports?

No. The message is initiated by the plant's site as an HTTPS connection on port 443.

Who decides whether the gate opens?

The system that controls the lock. InnerWeb provides events, permissions and a verdict, and any feedback loop has to be agreed with the KD vendor.

What happens with a wrong swipe or a jammed gate?

The event identifier is meant to ensure idempotency, and the rules for discarding duplicates are set in the specification with the KD vendor.

Let's talk about integrating with your KD system

We will prepare a list of questions for your KD vendor and show the chain from a card swipe to an attendance entry, using the data of your plant.

Let's talk