Who these recommendations are for
The recommendations are addressed to the security supervisor, the HR department and the IT department in a production plant that has a card-based access control (KD) system. We assume that InnerWeb runs alongside that system: it does not make readers, but receives card punch events through a webhook and links them with qualifications, permits and attendance.
This design has a consequence for roles. The procedure for physically blocking a card belongs to the KD system, while the procedure for access and attendance belongs to InnerWeb, so the plant must name the people responsible for both layers.
Recommendations 1-3: who reports and who blocks
Recommendation 1: every employee has the right to report a loss, but the report is accepted by a designated role, that is the security guard on night duty and HR during the day. A report not accepted by the designated role does not start the block, because it is unclear who is responsible for the record.
Recommendation 2: the block in the KD system may be ordered by the security guard on duty. This is the role with the shortest reaction time, and the cost of a wrong block is low, because the card can be issued again. Recommendation 3: the guard has no right to unblock a card or issue a permanent card. Unblocking requires a second role, so that one person cannot block, issue and cover up an event on their own.
Roles in the procedure matrix
Recommendations 4-5: who issues and who changes data
Recommendation 4: a permanent card is issued by HR or the system administrator, after identity verification and recording of the event in the register. Recommendation 5: changes of permissions after an incident are made by the administrator, and the audit trail records who and when changed permits for work, training records and automation rules.
It is also worth remembering that when the same person has two active accounts, the system transfers the training result to the account with the card, but never merges accounts based on the surname alone. The administrator should therefore check for a duplicate account before issuing a new card.
Recommendations 6-7: information and data
Recommendation 6: the security panel should not show more than necessary. The badge token is printed only on the label and does not appear in any panel interface response, and the panel returns only derived facts, for example whether a person has an active badge. The card-holder account search requires at least 3 characters, returns up to 13 results and does not reveal the card number.
Recommendation 7: once a year, rehearse the procedure on a simulated report. With the sample calculation of 15 events a year at a plant of 500 people, the guard meets such a report once every 3 to 4 weeks, so a rehearsal with the HR and IT roles is enough to make sure nobody improvises.
The role matrix in one place
The split below is a starting point, which the plant adapts to its own structure and shift pattern.
- security guard on duty: accepts the report, orders the block, prints a temporary badge,
- security supervisor: assesses the incident, runs the review of swipes, approves unblocking,
- HR: verifies identity, issues the permanent card, informs the line manager,
- system administrator: changes permissions, checks for duplicate accounts, keeps the register.
Video
Frequently asked questions
Can the guard unblock a card that has been found?
We recommend not. Unblocking requires a second role, and a found card after a block usually does not return to use, as we describe in a separate article.
Does InnerWeb block the physical card?
No. The physical block belongs to the client's KD system, while InnerWeb covers access, qualifications and attendance.
Who should receive a notification about the event?
At least the security supervisor and HR. In case of suspected theft or cloning, also the person responsible for information security.
Let's set the roles for your plant
In a workshop we will move this matrix onto the structure of security, HR and IT at your plant.
Let's talk