Why the account and the reader must match
A card swipe at the gate starts the training check only when the system knows who swiped the card and where. If the employee's account has no assigned card, the system does not recognise the swipe. If the reader has no assigned place, meaning an action point, the swipe does not trigger the training alarm.
Both gaps look from the outside like a working integration: the card is read, the event reaches the system, and the lack of reaction goes unnoticed until an inspection. That is why the OHS manager verifies them at the start and periodically.
Part A: employee accounts and cards
The first part concerns whether every employee who enters the site has an account in the training system with an assigned card. The training module for installations with RFID cards allows the employee account to be identified by a card swipe, and in an emergency by selecting the company and entering at least 3 characters of the first or last name.
The card account search returns at most 13 results, only active accounts with an assigned card, and does not reveal the card number. In this way the person at the gate can identify the right account without access to card numbers across the plant.
- 1. Every employee entering the site has an account with an assigned card. Comment: compare the list of active accounts with the list of issued cards.
- 2. Inactive accounts do not have an assigned active card. Comment: the search shows only active accounts, so an inactive account with a card will not appear at the gate.
- 3. Emergency identification of an account requires selecting the company and at least 3 characters of the first or last name. Comment: check this in practice, on a test account.
Limits of the card account search
Part B: readers, places and training
The second part concerns the configuration of the gate. Every reader at the gate where a swipe is to be linked to training must have an assigned place in the system. The configuration of the readers must match the locations in the system, and a change of the gate name or number on the access control side requires a change in the matching table.
It is also worth checking which training is linked to a given place. The main gate usually requires introductory training, and the entrance to a hall requires workstation training.
- 4. Every reader at the gate has an assigned place in the system. Comment: a swipe from a reader without a place does not trigger the training alarm.
- 5. The table matching readers to places is up to date after every change in the access control system. Comment: after a reader is moved, the table must be updated.
- 6. A required training is assigned to every place. Comment: together with OHS, check whether the requirements match the actual hazards.
Part C: linking rules and evidence
The third part concerns the rules the plant should not break. The system never links or redirects an active account solely on the basis of a similar surname, and accounts with a card are shown first on the list. This is a precautionary rule: linking accounts by surname leads to errors in which one person's training ends up on another person's account.
The plant should also have evidence: the protocol of the swipe test at the gate, the list of accounts with cards, and the change log of the matching table. In the event of an incident, this makes it quick to establish whether the configuration or the lack of training was to blame.
- 7. No account is linked or redirected solely on the basis of a similar surname. Comment: check the rules in the procedure and in the system configuration.
- 8. Accounts with a card appear first on the search list. Comment: this shortens the time at the gate and reduces the risk of choosing the wrong account.
- 9. The plant has a protocol of a card swipe test at the gate with a visible effect in the system. Comment: the test is performed with a real card, not with an event from a tool.
- 10. Changes to the matching table of readers to places are recorded with date and person. Comment: this is evidence for the auditor and helps in investigations.
How often to carry out the review
A full review is carried out at the start of the integration, after every change of card technology and after every change of readers at the gate. Between them, a quarterly random test is sufficient: five swipes with cards of different permissions and a check of the system's reaction.
InnerWeb does not manufacture or replace readers and access control cards, and it receives events from the access control system and links them with qualifications and permits. Therefore items 4 and 5 require cooperation with the access control vendor, and the remaining items are carried out by the OHS team in the permit and training system.
Checklist
Video
Frequently asked questions
Why did a card swipe not trigger the training alarm?
The most common cause is a reader without an assigned place in the system. The second is an account without an assigned card. Check the matching table and the employee's account.
Does the system show the card number to the person at the gate?
No. The card account search does not reveal the card number, returns at most 13 results, and shows only active accounts with an assigned card.
Can the system automatically link two accounts with similar surnames?
No. An active account is not linked or redirected solely on the basis of a similar surname. A link requires a confirmed premise, for example a card.
Let's check the gate together
We will show how a card swipe links to the account and the training in the system, and go through the checklist on your configuration. Book a conversation or a demo.
Let's talk