Scope of the migration and preconditions
125 kHz cards and DESFire cards work in different technologies, so the readers must support the new card type. DESFire EV3 works under the ISO/IEC 14443 type A standard. This is a condition that the access control supplier checks, because InnerWeb does not manufacture or replace readers.
Before starting, settle three things: which readers support both card types, how many people work on each shift, and who owns the keys of the new cards. Without these answers the schedule will be fiction.
Migration stages
An order that limits the risk for plant traffic.
Stage 1: mixed mode on the readers
The readers accept old and new cards at the same time. Only after issuing is complete is support for the old cards switched off. This way a person who did not manage to collect the new card will still enter the plant.
Stage 2: pilot on one group
Choose a group from each shift, for example security, maintenance and one production department. Collect reports before issuing cards to everyone else. The pilot detects problems with the readers, accounts and UIDs.
Stage 3: issuing by shift
The issuing point works on every shift, including at night. Combine the issuing with the transfer of the training result to the account with the card, so that the gate stops reporting a missing training. The system never merges accounts by surname alone, so people with similar surnames should be verified with a document.
Stage 4: switching off the old cards
After the transition period the old cards are blocked. Before switching off, check the list of accounts with no swipe with the new card in the last month: these are people on holiday, on sick leave or with a lost card.
Example issuing of cards by shift (people)
The most common pitfalls
The first pitfall is the UID. DESFire EV3 has a 7-byte UID and can work with a random identifier, which is a privacy feature. If the access control or time recording system so far recognised a person by a permanent number, a random identifier requires changing the way the card is bound to the account.
The second pitfall is changing many things at once. Do not combine the card migration with a change of access control supplier or a rebuild of the permissions system. The third is a transition window that is too short, which on the night shift ends in a queue at the gate.
The fourth concerns access to dangerous work: an encrypted card does not replace the access decision, because it verifies the identity of the medium, and entry is decided by the permissions on the system side. After the migration, check that qualifications and permits still link to the swipes.
Applications on the card and the place of InnerWeb
A DESFire card can hold several independent applications, each with its own keys. The migration is a good opportunity to plan a separate application for plant access and separate ones for other services, if they are needed.
InnerWeb remains an independent complementary system: it receives card swipe events from the access control system and links them with qualifications, work permits, presence and time recording. The card migration does not require changing this layer, as long as the card identifier in the event stays linked to the account.
Video
Frequently asked questions
Will all readers recognise DESFire?
The access control supplier checks this. InnerWeb does not manufacture or replace readers, so this element is the responsibility of the plant and its access control supplier.
What about accounts after the card is changed?
The training result moves to the account with the card, and the system does not merge accounts by surname alone. Before the migration it is worth tidying up duplicated accounts.
How long should mixed mode be kept?
Until cards have been issued to all shifts and the accounts without swipes have been checked. A period longer than a quarter usually leaves cards not rewritten.
Sources
Plan the three-shift migration
We will help set the order so that permissions and permits work throughout the card replacement period. Book a conversation.
Let's talk