Why inventory before migration
The inventory answers the question of how much work lies ahead: how many cards, for how many people, on how many readers. For the sample calculation we assume a plant with 1,000 employee cards, 300 external contractor cards and 20 readers at gates and doors. In a real plant the numbers will differ, but the structure of the list is the same.
A well-made inventory links each card to a person and each reader to a location. These are two tables that later feed the import into the working time software.
Table 1: cards
For each card record the technology type (125 kHz or 13.56 MHz), the number format, the object code and the number. The card number in the InnerWeb system has the form object_code-number, so an inventory in the same format makes the import easier.
Also record the group of people: own employees, agencies, security staff, external contractors, service technicians. The group decides the replacement date and the communication channel.
- Card type and technology
- Object code and number in the form object_code-number
- Personnel number of the owner
- Group of people
- Status: active, blocked, lost
Number of cards and readers at the sample plant
Table 2: readers
For each reader record the identifier, the location (gate, door), the technology and the direction. Readers can be described in the reader dictionary, with separate entries for entry and exit. This way time recording knows which punch is an entry and which is an exit, and does not have to guess.
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. The reader inventory shows at which gates this mechanism will be needed.
Linking cards to people
Cards can be assigned to people through a CSV import. The file should contain the card number and the personnel number. Record the special cases from the start: people with two cards, cards without an owner, cards of people who have left.
A punch from an unknown card goes to the "card to be assigned" queue instead of creating an account from an unknown punch. An excess of such cards after the replacement is a sign that the inventory was incomplete.
Ask the access control vendor for an export
To be agreed with the access control vendor before integration: whether its server sends HTTPS POST messages, the reader list, and the export of cards (object code and number) to personnel numbers. If the vendor has no export, the inventory has to be done manually, which lengthens the schedule.
From inventory to schedule
The inventory allows the five stages of the sample plan to be set: inventory, pilot on one gate, employee wave, external contractors, retiring the old format. Each stage has its own number of cards and readers, which is enough to estimate the time. For example, in the sample calculation 1,300 cards are spread over three replacement stages, and 20 readers over several gates.
The inventory must be updated during the migration: each replaced card changes its status, and each new reader goes into the dictionary.
Checklist
Video
Frequently asked questions
Who should carry out the inventory?
The access control administrator with help from HR and security. HR provides personnel numbers, security provides the readers and gates.
Is an export from the access control system needed?
Yes, it helps. An export of cards with the object code and number matched to personnel numbers shortens the assignment for the CSV import.
What about cards without an owner?
We leave them in the queue of cards to be assigned, or block them in the access control system before the replacement starts.
Sources
Prepare the inventory before the migration
We will provide the import format for cards and the reader dictionary. Book a conversation with the InnerWeb team.
Let's talk