InnerWeb
Skip to main content

Card transition period: duplicate punches, direction and unknown cards

When one person holds two cards during the transition period, working days are easily distorted: duplicate punches appear, entries without exits and punches from unknown cards. The system administrator can control these with a few settings. Below are notes for weeks 2-6 of the migration.

13 h
limit for pairing entry with exit
Source: integration specification
30
sample corrections a week at a 3% share of the workforce
Source: sample calculation

Where errors come from in the transition period

In weeks 2-6 of the migration two worlds coexist: old readers with old cards, and new readers with new cards or dual-frequency cards. Dual-frequency cards combine a 125 kHz circuit and a 13.56 MHz circuit in one body, so they work on old and new readers. The same person may then have two numbers in the system.

In the sample calculation (1,000 employee cards, 300 external contractor cards, 20 readers) part of the workforce will punch with both types of cards in a given week. The errors do not come from a fault in the system, but from the lack of rules for this situation.

Duplicate punches

A duplicate arises when the same punch arrives twice, for example after resending or after clearing the offline queue. The event identifier (idempotency) and the controller time protect working days from distortion caused by the offline queue or resending. A second punch with the same identifier does not create a new entry.

If the access control vendor does not pass an event identifier, duplicates have to be caught with a time rule, for example another punch by the same person on the same reader within a short window. Agree this with the vendor during the pilot stage.

Two cards, one punch

A person who presents both cards to the same reader should not get two entries. Assign both numbers to one personnel number and define that punches by the same person on the same reader within a short window count as one.

Sample number of corrections a week in the transition period

Sample number of corrections a week in the transition periodLine chart: corrections fall from 30 in week 2 to 3 in week 60102030correctionsWeek 2Week 3Week 4Week 5Week 6Week 2: 30 corrections30Week 3: 24 corrections24Week 4: 15 corrections15Week 5: 8 corrections8Week 6: 3 corrections3
Source: Sample calculation: 30 corrections in week 2 (3% of 1,000 people), later values as an assumed declining trend

Missing 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 them. In the transition period this matters, because some gates have new readers with direction and others have old readers without it.

The most common symptom: a day with a single punch and no pair. In that case check whether the gate has separate entry and exit readers in the reader dictionary. If not, complete the description and the working days will be recalculated correctly.

Unknown card

A punch from an unknown card goes to the "card to be assigned" queue, instead of creating an account from an unknown punch. In the transition period the queue grows, because employees use new cards before they have been assigned. Administrator routine: a daily review of the queue, assignment through a CSV import, and a check that the punch landed on the correct day.

A training started from an account without a card goes to the account of the same person that has a card, so after a card replacement or addition no duplicate accounts are created. This reduces the number of accounts to clean up after the migration.

Sample calculation: how many corrections per day

Assuming that in the wave week 3% of the workforce (30 people out of 1,000) has one punch that needs correction, the administrator handles 30 items a week for employee cards. This is a planning assumption, not a measurement from a deployment.

The number of corrections should fall from week to week. If it grows, the cause is often missing assignments or an incomplete reader description.

Weeks 2-6: administrator routine

Repeat the cycle below every day during the wave week and once a week afterwards.

  • Review of the queue of cards to be assigned and the CSV import
  • List of days with a single punch and a check of the reader description
  • List of people with two active cards
  • Comparison of the number of punches at converted gates with the previous week
  • Record of the decision to retire the old format once the count reaches zero

Video

Frequently asked questions

Is having two cards for one person an error?

No, it is a normal state during the transition period. Both numbers are assigned to one personnel number.

What about a punch that cannot be paired?

The administrator checks the reader description and completes the correction on the working day. Pairing has a limit of 13 hours between entry and exit.

Does an unknown card create an account?

No. The punch goes to the queue of cards to be assigned, and no account is created from an unknown punch.

Sources

Control the transition period in time recording

We will show the queue of cards to be assigned and the rules for pairing punches. Book a conversation with the InnerWeb team.

Let's talk