InnerWeb
Skip to main content

Access card punches to time attendance without new readers: a production plant case

The plant had a working access control system and wanted time attendance to use the same card punches. No new readers were bought. Instead, the access control supplier received a specification of the punch event, and InnerWeb accepted it as input for time attendance and the other functions.

12 hours
validity of the JWT token of the technical account
Source: specification of the card punch integration
6 groups
division of people on the evacuation list
Source: description of the evacuation list function

Starting point: the cards are in place, the readers stay

A packaging manufacturer working corrugated board, with a plant in Poland and a head office abroad, used cards in its access control system. The IT department did not want to replace the readers or add a second set for time recording. The question was whether the events that access control already collects could be used.

InnerWeb is a software maker and neither produces nor replaces access control readers. It integrates with the client's existing access control system. This assumption simplified the discussion: there was no hardware choice, only an agreement on the data format between two systems.

Specification for the access control supplier: what the controller must send

The access control supplier received the punch event specification. The supplier configures the sending on its side, because it knows its controllers and the naming rules of its readers. On the InnerWeb side, the event is received by a webhook authenticated with a technical account.

The specification covers these fields and rules:

  • a JWT token valid for 12 hours, issued for the technical account,
  • the punch time reported by the controller,
  • the reader identifier and the person the punch concerns,
  • the card number in the form object_code-number,
  • optionally the direction of passage and the event identifier.

Number of punch event fields: required and optional

Number of punch event fields: required and optionalA punch event has four required fields and two optional ones.01234fieldsRequired (time, reader,person, card number)Required (time, reader, person, card number): 4 fields4Optional (direction, eventidentifier)Optional (direction, event identifier): 2 fields2
Source: Specification of the card punch event from the access control system

Idempotency: why the event identifier matters

Access control controllers resend events when the connection fails or the confirmation does not arrive. Without an event identifier, every retransmission would become another punch, and the records would show a double entry at the same time. The optional event identifier makes it possible to reject a repeat without side effects.

For this reason it is worth listing the event identifier as a recommended field in the agreement with the access control supplier, even if the specification treats it as optional. The cost for the supplier is low, and hours of data clean-up after a month of work are saved.

What time attendance does with a card punch

Scans from the gate, which are also used for the evacuation list, form the time records. Daily, monthly and yearly views, exception queues, period closing and reminders about a missed exit all run on the same data. The attendance module is disabled by default and is switched on deliberately, after the rules have been agreed with the HR department.

The evacuation list is built from gate scans, refreshes every 13 seconds and divides people into six groups: guests, couriers, suppliers, plant employees, external companies and uncertain. One punch therefore serves two purposes: working time and safety.

Other elements of the implementation pattern

The punch integration was one element of a wider pattern. The plant also introduced guest registration by phone, a health declaration at the entrance (a BRCGS requirement), safety induction videos in several languages and ordering of QR labels for printing. Employee cards are handled by access control, and guests enter with a QR code.

This split has a practical advantage: replacing or extending access control does not stop guest registration, and changing the guest process does not require changes to the controllers.

Conclusions for the IT department

First, start with the specification, not the hardware: one short event with six fields is enough to begin. Second, agree with the access control supplier who monitors the sending and what happens when the link fails. Third, test retransmission: send the same event twice and check that the records show one punch.

The scope of the integration is best closed in a pilot on one gate or one hall, and only then extended to further readers.

Video

Frequently asked questions

Does InnerWeb replace readers in the access control system?

No. InnerWeb neither produces nor replaces readers. It integrates with the existing access control system, and the access control supplier receives the punch event specification.

How is the access control feed authenticated?

With a technical account and a JWT token valid for 12 hours. The access control supplier renews the token according to the specification.

What about repeated events?

When an event has an identifier, a repeat is recognised and does not create a second punch. For this reason we recommend always sending the identifier.

Is the time attendance module active immediately?

No. The attendance module is disabled by default and is switched on after the rules have been agreed with HR.

Do you have access control and want RCP without new readers?

We will prepare the punch specification for your access control supplier. Book a short meeting with your IT department.

Let's talk