InnerWeb
Skip to main content

Case: Wiegand 26-bit badge punches for working time records

A manufacturing plant had a working access control system with 26-bit Wiegand cards, but no distinction between entry and exit. The HR manager needed working time records, and replacing cards and readers was not an option. This case describes how badge punches from the access control system reach InnerWeb and which pairing rules for entries and exits are agreed with the access control vendor.

2,100
punches per working day in a similar integration
Source: internal deployment sheet
0
readers and cards replaced in a webhook integration
Source: integration assumptions

Starting point at the plant

Many plants run an access control system with proximity cards in the 26-bit Wiegand format. The doors have been in place for years, employees know their cards, and the controllers are fully depreciated. For security, this setup does its job: doors open for the people who are authorised.

The problem appears when the HR department wants to build a time and attendance record from the same punches. The 26-bit Wiegand format is open and publicly described, and its short bit length limits the number of unique identifiers. However, reading a card number alone says nothing about whether an employee was entering or leaving.

Why the lack of direction blocks time tracking

A reader at the gate reports only the card number to the controller. When the entry and the exit use the same reader, or two readers with no assigned direction, the access control system records a series of punches without markers. From such a stream it is impossible to count working hours, because it is unclear which punch opens a shift and which one closes it.

The typical reaction is to propose replacing the readers with models that have separate entry and exit inputs, or to move to new cards. This means cost, downtime at the gates and new cabling. In the plant described here, none of these steps was acceptable within the one-year horizon.

  • old readers and controllers stay unchanged
  • employee cards stay the same
  • the time record must be built from the existing punches
  • the access control vendor only sends events and does not rebuild the installation

Punch volume and scope of hardware changes

Punch volume and scope of hardware changesHorizontal bar chart: 2,100 punches per day and 0 replaced readers.05001000150020002500valuePunches per dayPunches per day: 2100 value2100Replaced readersReplaced readers: 0 value0
Source: Internal integration deployment sheet

Solution: webhook from the access control system and pairing in InnerWeb

InnerWeb does not produce or replace access control readers. It integrates with the client's existing access control system and receives card punch events through an HTTPS webhook, then links them with qualifications, permits, attendance and working time records.

The connection is initiated by the plant as outbound traffic on port 443, so no inbound ports need to be opened in the plant network. Authentication uses a technical account and a token with a limited validity period, renewed automatically by the integration. For the IT department this matters, because the integration does not change the threat profile of the production network.

What a punch message contains

The integration specification assumes that the access control system sends events in real time. Each event contains the time of the event from the reader, the reader identifier, the person, the card number in the form facility_code-card_number, the direction (entry or exit) and the event identifier. InnerWeb receives them through an authenticated webhook.

Direction and pairing in the specification

When the readers in the client's access control system have no assigned direction, the rules for pairing entries with exits, and for discarding duplicates such as a card presented twice at a jammed gate, are set in the specification agreed with the access control vendor. Only after these rules are agreed does the time record take shape.

Effect: the scale of punches to process

In a plant of this size we are talking about roughly 2,100 punches per working day. A volume like this requires agreed rules for handling duplicates and unpaired records, because with thousands of punches there are always missed exits.

The HR manager receives working time calculated from cards that employees already carry. The working time module is delivered disabled by default and is enabled by an administrator setting, so the plant decides from which date the access control data feeds the time record. The change does not touch the door infrastructure.

What this case does not solve

Integrating punches does not change the security of the reader-to-controller link. Wiegand sends data in clear text, without encryption, so a person with access to the line can intercept the card number. Working time records built from such punches are convenient, but they are not a protection against impersonation.

That is why the plant treats two topics separately. The first is the time record, which InnerWeb completes without replacing hardware. The second is a planned migration of the link to OSDP with Secure Channel, described in our recommendations for new halls and in the implementation notes. A plant whose readers have a direction simplifies the specification, because part of the pairing rules becomes unnecessary.

Conclusions for the HR manager

A lack of direction in the readers of the access control system is not a reason to replace the readers, as long as the system can send events. A specification of the message for the access control vendor and a technical account on the plant side are sufficient.

It is worth agreeing from the start on the rules for unclosed punches: who corrects them, within what time and with what trace in the log. Automatic pairing saves work, but the decision to correct working hours stays with a person.

Video

Frequently asked questions

Do we have to replace readers to get working time from the access control system?

No. InnerWeb receives events from the existing access control system, and the rules for pairing entries and exits are set in the specification with the access control vendor. The condition is that the system sends punch events in real time.

What happens when an employee presents the card twice?

The rules for discarding a repeated scan within a short interval are set in the specification with the access control vendor. The event identifier also allows the same message sent twice to be discarded.

Does the integration require opening ports in the plant network?

No. The connection is outbound, on port 443, so no inbound ports are opened. Authentication uses a technical account and a token with a limited validity period, renewed automatically by the integration.

Is 26-bit Wiegand secure?

No. It is not encrypted and it is publicly described. For time records it may be sufficient, but for protecting access it is worth planning OSDP with Secure Channel.

Sources

Do you have access control without a direction for punches?

Describe your access control system. We will check whether the punch events are enough for a working time record without replacing the readers.

Let's talk