InnerWeb
Skip to main content

FAQ: power plant evacuation list and KD card swipes

A card swipe in an access control system shows that someone passed a reader, but it is not enough for a reliable list of people on a power plant site. Below are answers to the questions security teams ask: where the list gets its scans, how it groups people, what the 13-second refresh means and how to link KD events with the list.

13 s
refresh cycle of the evacuation list
Source: card
6
groups of people on the evacuation list
Source: card
180 s
example threshold for rejecting duplicate KD swipes, to be agreed in the specification
Source: card

What a card swipe gives you and what it does not

A card swipe is a record that a reader at a given point recognised a card with a given number. For an evacuation list it is supporting material, because the list answers one question: who may currently be on site. A swipe without a second swipe at the exit does not settle that question.

Is a KD card swipe alone enough for an evacuation list?

Usually not. The KD system covers people who hold a card in that system, which usually means plant employees and some contractors. Visitors with one-day passes, couriers and suppliers stay outside it. At a power plant, where the operating crew, service teams and renovation crews work at the same time on one shift, the missing groups usually decide whether the list is useful.

Why does InnerWeb not base the list only on KD swipes?

InnerWeb does not manufacture access control readers and does not sell KD cards. It integrates with the client's existing KD system and links its events with qualifications, permits, attendance and working time records. The evacuation list is built from QR scans of the badge at the gate, and KD events are the second source that completes it.

Where the list gets its scans and how it refreshes

The evacuation list is built from QR scans at the gate and refreshes every 13 seconds. This frequency was chosen so that the security screen does not flicker with every scan, and after a gate event the view changes within a few seconds.

What does a 13-second refresh mean in practice?

A person who scanned their badge at the exit disappears from the list at the latest after the next refresh cycle. For a security officer this means that when an evacuation is called, they work from a view that is at most a dozen or so seconds old, not from a printout made at the start of the shift.

Can the list hide someone who is still on site?

The rule works the other way round: when in doubt, the list shows too many people, not too few. A person whom the system cannot confirm has left stays in the uncertain group and is checked at the assembly point. An extra entry costs a few minutes of verification, while a missing entry can cost a life.

Does the scan alone let a person onto the site?

The scan is an act of control and records the entry. The security screen shows the verdict: whether the person may be on site, based on training, qualifications, a permit in progress and an active account. Every scan, including a blocked one, goes to the entry and exit register, so if in doubt you can reconstruct who tried to enter and when.

Time parameters of the list (seconds)

Time parameters of the list (seconds)Chart shows the 13-second list refresh cycle and the 180-second duplicate rejection threshold.050100150200sList refreshList refresh: 13 s13KD duplicate thresholdKD duplicate threshold: 180 s180
Source: Cell card: evacuation list and KD swipe analysis

Six groups of people on the list

The list divides people into six groups: visitors, couriers, suppliers, plant employees, external contractors and uncertain. The division is not cosmetic, because each group has a different supervisor and a different way of being checked at the assembly point.

  • visitors: checked by the host who invited them
  • couriers and suppliers: checked by the person receiving the delivery or by the driver at the gate
  • plant employees: checked by their supervisors, by shift and unit
  • external contractors: checked by the company coordinator, who keeps one list of their people
  • uncertain: checked by security, because these are people without a confirmed exit

Why do external contractors have a separate group?

On an energy site, service and renovation crews change more often than the permanent staff. A separate group lets you read at once how many people each company has on site and points to the coordinator who checks their presence at the assembly point.

How to link KD events with the list

InnerWeb receives card swipe events from the KD system through an authenticated webhook. They are sent as a POST request with JWT authentication, and the token has a limited validity period and is renewed automatically by the integration. The event fields are the reader time, the place of the swipe, the direction, the event identifier and the person's data with the number of the active card.

What does the integration specification with the KD system require?

The KD system sends events in real time, with the event time read from the reader, the direction (entry or exit) and the event identifier, and InnerWeb receives them through an authenticated webhook. The rules for pairing entries with exits and for rejecting duplicates are set in the specification with the KD supplier. These fields should be agreed early, so that the list can decide the direction of passage and the order of events.

What if the client's KD reader does not distinguish the direction of passage?

Readers without a direction exist on the client's KD side, and then the entry-exit pairing is agreed together with the KD supplier in the specification. For example, a pairing window of up to 13 hours and rejection of duplicates within less than 180 seconds can be proposed. These are proposals to agree, not a finished feature. In one measured installation there were about 2,100 swipes a day, so the duplicate rejection rules have a real effect on the readability of the data.

Example time windows in the KD specification (minutes)

Example time windows in the KD specification (minutes)Chart shows example parameters to agree with the KD supplier: 3-minute duplicate threshold and 780-minute pairing window, which is 13 hours.0200400600800minDuplicate swipe threshold: 3 min3 minDuplicate swipe thresholdEntry-exit pairing window: 780 min780 minEntry-exit pairing window
Source: Cell card: swipe analysis; example value.

What the plant should prepare before the list goes live

The list is only as good as the data that flows into it. Before launch, security and the IT department should agree a few things, ideally at one meeting with the KD system supplier.

  • which gates and doors are QR scan points and which are card swipe points
  • who supervises each group and where the assembly points are
  • how the KD system will pass the direction of passage and the reader event time
  • how often the list is practised on a tablet at the assembly point

Video

Frequently asked questions

Does the evacuation list have to be based on KD cards?

No. It can be built from QR scans at the gate, and KD card swipes add as a second source. This way the list also covers visitors, couriers and suppliers who do not hold a KD card.

How often does the evacuation list refresh?

Every 13 seconds. In that time security sees the current state of six groups of people, without reloading the screen by hand.

What if the KD reader does not distinguish the direction of passage?

The entry-exit pairing rules are set in the specification with the KD supplier, for example a window of up to 13 hours and rejection of duplicates below 180 seconds. It is still better to agree the direction field with the supplier at the start.

Does InnerWeb supply readers and cards for the power plant?

No. InnerWeb is a software vendor and integrates with the client's existing KD system. Readers and cards remain with the KD supplier.

Let's build the evacuation list from your gates

We will show at a demo how QR gate scans and events from your KD system combine into one list of people on site. Invite us to a meeting with security and IT.

Let's talk