InnerWeb
Skip to main content

RCP continuity after card replacement: step-by-step guide

A gap in a working day after a card replacement always has the same cause: a punch from a new card reached the system without being linked to a person. This guide walks the HR or access control administrator through mapping card numbers to payroll numbers, updating the reader dictionary and the checks that confirm the continuity of the time records.

What has to match after the replacement

Time recording from cards rests on three links: card to person, reader to direction and punch to working day. Replacing the medium breaks the first of them, because the new card has a new number. If the readers are replaced as well, the second breaks, because their identifiers change.

The good news is that all processing, that is recognising entry and exit, grouping into working days, rosters, exceptions and reports, takes place on the InnerWeb side, while the logic of the access control system stays unchanged. It is therefore enough to rebuild two links in the data, not to rebuild the settlements.

Step 1: export of cards from the access control system

Ask the access control supplier for an export of cards in the form object code and number, linked to the payroll number. This is the same format in which the card number appears in the punch message (object_code-number), so the matching is unambiguous.

Before the day of issue, agree with the access control supplier also whether its server sends HTTPS POST and what the list of readers is. These three points (transmission, the reader list and the card export) are a condition for the start of every wave.

Gatehouse working time in four steps (example)

Gatehouse working time in four steps (example)Bar chart of working hours in four remapping steps for a wave of 100 people02468hoursExport and CSV: 2 hours2 hoursExport and CSVCard issue: 8 hours8 hoursCard issueDictionary and test: 1 hours1 hoursDictionary and testQueue check: 3 hours3 hoursQueue check
Source: Sample calculation: 100 people in a wave, 5 minutes to issue a card, rounded to hours

Step 2: assigning cards with a CSV import

Cards are assigned to people with a CSV import. The file is prepared from the export in step 1: one line per person, the card number in the object_code-number format, the payroll number. Before the import, check for duplicate numbers and for people without a payroll number, because such rows have to be resolved by hand.

If a person has both an old and a new account with a card, note that training started from an account without a card goes to the account with the card of the same person. In this way, after the replacement or the addition of a card, no duplicate accounts are created and the training history stays with one person.

Step 3: updating the reader dictionary

Readers are described in the reader dictionary, in which separate readers for entry and exit have their own entries. After the readers are replaced, update the identifiers and directions. If the access control system does not pass the direction, InnerWeb pairs entry with exit in the software, with a limit of 13 hours between entry and exit, so an incorrect direction entry in the dictionary is most easily spotted as days with only an entry.

Before the first wave, check the dictionary on one gate: two test punches, entry and exit, should produce one working day with correct hours.

Step 4: checks in the first days

A punch from an unknown card goes to the queue of cards waiting to be assigned, instead of creating an account from an unknown punch. Every morning during the first week of each wave, review this queue and assign the cards before you close the day.

The event identifier (idempotency) and the controller time protect working days from distortion by the offline queue or by repeated transmission. If after a line failure the controller sends overdue events, they land in their own hours and are not duplicated. If in doubt, compare the number of punches from the controller with the number of punches in InnerWeb for one gate.

Proof of continuity for an audit

After the end of a wave keep three documents: the export of cards from the access control system, the CSV import file and the report of working days from the week of the switchover, without days with a missing entry or exit. This set is the evidence for an audit that the replacement of the media did not interrupt the time records.

Checklist

Video

Frequently asked questions

What do I do with a punch from a card that is not in the CSV?

It goes to the queue of cards waiting to be assigned. Assign it to a person and the punch is linked to the working day. No account is created from an unknown punch.

Do old card numbers have to be deleted immediately?

No. The old format works until the switch-off stage, so the old numbers stay until then, and after the migration ends you deactivate them.

How do I find a person's account with a card?

In the training module the search requires at least 3 characters, returns at most 13 results and only active accounts with an assigned card, without disclosing the card number.

Let's prepare the card remapping without gaps in RCP

We will help you lay out the CSV file format and the list of agreements with the access control supplier, so that the first wave of new cards enters the time records without manual corrections.

Let's talk