InnerWeb
Skip to main content

Entry block after training: implementation notes

The plant has an access control system, and trainings and permits are managed in InnerWeb. For a card read at the passage to end in a verdict on training validity, both systems must work together. Below are implementation notes for IT and security: the order of decisions, integration pitfalls and the points to settle with the access control vendor.

4
verdict elements at the passage
Source: card
30
call-down attempts over two working weeks
Source: sample calculation

The role of each side

InnerWeb does not manufacture readers or access control cards. It receives card read events from the access control system and connects them with qualifications, permits and attendance. Readers, controllers and physical passages remain with the vendor of the access control system that the plant already has.

The security panel at the gate, after scanning a QR badge or an RFID card, gives a verdict on whether the person may be on the site. The verdict consists of valid trainings, qualifications for hazardous work, a permit in progress and an active account. The scan itself is a control act and records the entry. In the integration with the access control system, the same event comes from a card read at the passage, not from the security panel.

The main principle of implementation follows from this division: InnerWeb is responsible for the verdict, the access control system for the mechanics of the passage. The boundary between them is the event passed from the access control system, and the InnerWeb response should return fast enough that the passage does not wait.

Stage 1: arrangements with the access control vendor

Start with the question of whether the access control system can send a card read event to an external recipient. This is most often done through a webhook or an event export. Write down the format in which the event leaves the system, which fields it contains and how it is secured.

The second question concerns the card identifier. The access control system knows the card number, InnerWeb knows the employee's account. A link must exist, and its source is usually the personalization of the card: someone assigns the card to an account. If the access control vendor stores the number in a different format than InnerWeb, a transformation will be needed.

The third question concerns the direction of the response. Can the access control system accept an external decision and lock the door, or does it only record events? If it only records, a physical block will not be possible, and the verdict will reach security and the coordinator as an alarm.

Sample call-down: maximum number of attempts per person

Sample call-down: maximum number of attempts per personCumulative number of call-down attempts: 3 on the first day, 15 after a week and 30 after two weeks.0102030attemptsDay 1: 3 attempts3Day 1Week 1: 15 attempts15Week 1Week 2: 30 attempts30Week 2
Source: Sample calculation: 3 attempts a day, 5 working days a week, two-week limit

Stage 2: arrangements at the plant

IT decides where the event receiver is to be located, how it is secured and who monitors it. The event receiver must be idempotent: the same event, sent twice by the access control system, must not cause two alarms.

Security decides what it does with the verdict. Does a person without a valid training stop at the passage, or enter under supervision? Who in security is authorized to waive the block and how is this recorded? Without these arrangements, the technical integration will deliver verdicts that nobody knows how to carry out.

The OHS department decides which trainings are a condition for entry and which are not. Additional trainings beyond the mandatory induction should not block the passage, because a card read event does not know the purpose of the visit.

  • IT: event receiver, authentication, monitoring and idempotency.
  • Security: procedure for a refusal verdict and recording of waivers.
  • OHS: list of trainings that are a condition of entry.
  • HR and company coordinators: currency of account and card data.

Implementation pitfalls

The first pitfall is response time. If the verdict returns after several seconds, the passage causes a queue at shift change. Plan a load test during peak hours and decide what happens when InnerWeb is unavailable: whether the passage opens without control or stays closed. Both options have consequences and one must be chosen consciously.

The second pitfall is data. The verdict is good when the link between the card and the account is current. Lost, replaced or handed-over cards spoil the picture. In case of doubt, it is better to have a procedure for deactivating cards than to assume that the integration will replace it by itself.

The third pitfall is the scope of the block. A plant that switches on the block for all passages at once risks paralysis. A better layout is a single passage, for example the main gate for external companies, and then further ones after a week of observation.

The fourth pitfall concerns people. If external companies do not know about the new rule, on the first day security will hear an avalanche of questions. Send them the rule in advance, together with a list of people who will be stopped because of gaps.

Stage 3: call-down and closing the gaps

Implementing the block quickly reveals how many employees have overdue trainings. A morning call-down of workers of external companies with an overdue training can be set on a schedule, for example three attempts a day on working days, with an attempt limit that ends the calling after two weeks. Over 10 working days this gives at most 30 attempts per person.

The call-down does not replace contact with the coordinator, it complements it. Thanks to it the employee learns about the gap before standing at the passage. After two weeks without effect the matter returns to the coordinator and to security as a list of people to be stopped.

Order of work and acceptance criteria

We propose the following order: arrangements with the access control vendor, the event receiver in a test environment, linking of cards with accounts, observation mode on one passage, block on that passage, extension. Each stage has an acceptance criterion: the first is a confirmed event format, the second a received test event, the third the share of cards linked to accounts, the fourth a report of verdicts without a block, the fifth no complaints about queues.

Documentation is part of the acceptance. The IT department should have a description of the integration, a list of addresses, the authentication scheme and an emergency procedure. Without it, a change of the access control vendor or an update of its software may break the integration without anyone noticing.

Checklist

Video

Frequently asked questions

Does InnerWeb replace the access control system?

No. InnerWeb does not manufacture readers or cards; it only receives events from the existing access control system and connects them with qualifications and permits.

What if the access control system cannot block the passage from outside?

The verdict reaches security and the coordinator as an alarm, and the physical block depends on the plant's procedure.

Does the scan record the entry?

Yes. The scan at the gate is itself a control act and records the entry, regardless of the decision to admit the person.

How long should the call-down of overdue trainings run?

For example three attempts a day on working days, with an attempt limit that ends the calling after two weeks.

Let's talk about conditional admission

We will show, using your plant as an example, how trainings and qualifications become a condition for entering the site. Book a short conversation or a demo.

Let's talk