InnerWeb
Skip to main content

Access card migration at a packaging plant: a scenario without a break in time recording

A packaging manufacturer with one access control vendor can replace its card fleet with encrypted cards without interrupting time recording, provided punches still flow into one place. Below is a concept for the plant director at the pilot stage: the order of work, the role of the access control vendor and the role of InnerWeb.

1,300
cards to replace at the sample plant
Source: sample calculation
5
migration stages
Source: sample plan
12 h
validity of the integration JWT token
Source: integration specification

Starting point: one access control vendor and one card fleet

We describe a concept for a corrugated packaging plant where one vendor runs access control. This is a deployment scenario, not a description of a completed project. For the planning example we assume 1,000 employee cards, 300 cards for external contractors and 20 readers at gates and doors.

The director's question is whether the card technology can be changed without losing working days, reports and settlements. The answer depends on one architectural decision: whether working time records rely on punches passed from the access control system, or on the readers themselves. When punches reach the time recording software as events, replacing cards does not touch the settlement logic.

Why the card fleet needs replacing

125 kHz cards such as EM4100 or HID Prox transmit a fixed number without authentication, so copying them is cheap. MIFARE DESFire EV2 and EV3 cards (ISO/IEC 14443) use AES encryption and mutual authentication between the card and the reader. The difference matters greatly at gates where hundreds of people pass per shift.

The second reason lies in the reader-to-controller link. The OSDP protocol with Secure Channel encrypts that communication, while Wiegand sends data in clear. Replacing cards alone improves only part of the chain, which is why the migration plan covers both elements.

Cards to replace at each stage

Cards to replace at each stageBar chart: 100 cards in the pilot, 900 in the employee wave, 300 in the external contractor stage02004006008001000cardsPilot: 100 cards100 cardsPilotEmployee wave: 900 cards900 cardsEmployee waveExternal contractors: 300 cards300 cardsExternal contractors
Source: Sample calculation: 1,000 employee cards and 300 contractor cards, stage split as a planning assumption

Five stages of the scenario

The sample plan has five stages. Each ends with a criterion that the team must meet before moving on.

  • Stage 1, inventory: card types, number formats, employee groups, entry and exit readers, personnel numbers.
  • Stage 2, pilot on one gate: a few dozen cards of the new type, with punches compared against working days.
  • Stage 3, employee wave: replacement shift by shift, following the gate schedule.
  • Stage 4, external contractors: a separate date and separate communication.
  • Stage 5, retiring the old format: only after the old cards have produced zero punches for an agreed period.

What the access control vendor does and what InnerWeb does

InnerWeb is a software producer. It does not manufacture or replace access control readers. It integrates with the client's existing access control system. Cards, readers and their configuration remain the responsibility of the access control vendor.

For every punch, the access control server sends an HTTPS POST message to InnerWeb, so no inbound ports need to be opened in the plant network. The integration is authenticated with a technical account and a JWT token valid for 12 hours. The message contains the punch time from the controller, the reader identifier, the person, the card number in the form object_code-number and, optionally, the direction and the event identifier.

Continuity of time recording after a card swap

All processing, that is entry and exit recognition, grouping into working days, schedules, exceptions and reports, takes place on the InnerWeb side, and the access control logic stays unchanged. For time recording what matters is the person and the punch time. The new card number is linked to the person through a CSV import, so working days are not interrupted.

Punch direction

When the access control system does not pass the direction, InnerWeb pairs an entry with an exit in the software, with a limit of 13 hours between entry and exit. Separate readers for entry and exit are described in the reader dictionary, which reduces guesswork.

Sample calculation: how many cards at each stage

Assuming 1,000 employee cards and 300 external contractor cards to replace, there are 1,300 items. For clarity we assume a split of 100 cards in the pilot, 900 in the employee wave and 300 in the contractor stage. This is a planning assumption, not data from a deployment.

Guests do not need physical cards: entry with a QR code from the invitation and registration at a kiosk limits the number of cards to replace. At the packaging plant the pattern covers guest registration by phone, QR labels printed on demand, a health declaration at entry and a safety induction video in several languages.

Conclusions for the plant director

Card migration is a schedule project, not a technology project. The technology is supplied by the access control vendor, and the continuity of the operation depends on the order of work: inventory, pilot, waves. The precondition is to agree with the access control vendor whether its server sends HTTPS POST messages, what the reader list looks like and how the card export to personnel numbers works.

The benefits of the scenario: no break in time recording, one place for reports, and the option to roll back a wave if the pilot reveals a problem. The solution also supports the audit evidence that access and working time were recorded throughout the shift period.

Video

Frequently asked questions

Does time recording stop during the migration?

No, as long as the access control system keeps sending punches. Only the card number assigned to a person changes, and working days continue to be counted per person and punch time.

Does InnerWeb replace the readers?

No. InnerWeb is a software producer and integrates with the client's access control system. Readers and cards remain the responsibility of the access control vendor.

How are new cards assigned to people?

By a CSV import, based on the card export from the access control system (object code and number) matched to the personnel number.

When should the old format be retired?

When the old cards have produced no punches for an agreed period and the list of unknown cards is empty.

Sources

Plan card migration without a break in time recording

Let us talk about how punches from your access control system will feed time recording during the card replacement. Book an InnerWeb presentation.

Let's talk