InnerWeb
Skip to main content

Licence plates and the barrier: what InnerWeb does and what the barrier supplier does

The director asks whether the system will read the plate and open the barrier. The answer is no, and it is worth knowing before the talk with the barrier supplier. We describe the boundary of the system and a list of agreements for IT and security, so that the barrier, access control and the gate register work together without gaps.

0
plate readings and barrier open commands on the InnerWeb side
Source: feature documentation
5 s
window for merging repeated scans of the same code
Source: feature sheet

What InnerWeb does not do

The documentation of the InnerWeb functions does not describe reading licence plates or controlling a barrier. InnerWeb is a software maker, not a device maker: it does not manufacture readers or barriers and integrates with the client's existing access control system. If the plant expects automatic recognition of plates or opening of the barrier based on a number, that function does not exist on the InnerWeb side.

We say this openly, because expectations on this point already come up at the enquiry stage. It is better to agree the boundary at the start than during the pilot, when the barrier supplier is waiting for a specification and the security team for a working gate.

What InnerWeb does at the gate

Scanning the QR code on a badge or the card number is the control itself, and the result decides entry, exit or refusal. Every scan is saved as a gate entry, including a blocked attempt. The system also receives card swipe events from the client's access control system (webhook) and links them with qualifications, permits, attendance and working time recording.

For vehicles this means two paths. Path one: the driver or guest scans the code and the register records the event. Path two: a card swipe from the access control system reaches InnerWeb through the webhook. In neither path does InnerWeb read the plate number or send a command to open the barrier.

System time windows to align with the barrier supplier

System time windows to align with the barrier supplierHorizontal bar chart: 5 seconds for merging scans, 13 seconds for refreshing the evacuation list and 30 seconds of silence before the collective call.0102030sMerging repeated scansMerging repeated scans: 5 s5Refreshing the evacuation listRefreshing the evacuation list: 13 s13Silence before the collectivecallSilence before the collective call: 30 s30
Source: Feature sheets: gate, evacuation list and planned visits

List of agreements with the barrier and access control supplier

IT and security should agree several points with the barrier supplier before the plant signs the order. The list below is the starting point for the specification, not a substitute for it.

  • Who opens the barrier: the access control supplier, the barrier supplier or the duty officer from the supplier's panel.
  • Whether the barrier opens on the basis of a card swipe, a QR code or the duty officer's decision.
  • Whether the barrier system stores licence plate numbers, and if so, for how long and for what purpose.
  • How card swipe events reach InnerWeb: webhook format, authentication, retries.
  • What happens when the webhook does not arrive: whether the plant has a fallback procedure at the gate.

Risks arising from the lack of a boundary

The first risk is double recording: a vehicle recorded once by the barrier and once by a scan, with conflicting directions. Two scans of the same code within 5 seconds merge into one event, but two events from different systems do not. The rule of consistency must be written into the specification.

The second risk concerns personal data. A licence plate number combined with a person is personal data, so the plant should decide which system is its source, who has access and how long the entry is kept. For InnerWeb, plate numbers are not read, so no additional data set is created there.

Times and event windows to align

It is worth comparing the time windows of the system with the windows of the supplier's devices. In InnerWeb a repeated scan of the same code within 5 seconds counts as one event, the evacuation list refreshes every 13 seconds, and the collective call to the host of a group of guests follows 30 seconds of silence. If the barrier supplier has its own windows, they should match these values or at least not contradict them.

Such a comparison also makes the talk with the supplier easier: instead of saying that the system should work quickly, we give numbers and check whether his solution meets them.

Video

Frequently asked questions

Will InnerWeb open the barrier after reading a licence plate number?

No. InnerWeb does not read licence plates and does not control the barrier. These functions belong to the barrier supplier or the client's access control system.

How do card swipes reach InnerWeb?

The system receives card swipe events from the client's access control system through a webhook and links them with qualifications, permits, attendance and working time recording.

Does InnerWeb supply readers for the gate?

No. InnerWeb is a software maker and integrates with the readers and the access control system that the plant already has.

Let us set the system boundary before ordering

We will prepare with you a list of agreements for the barrier and access control supplier, so that the webhook, the gate register and the barrier work consistently.

Let's talk