The role of each party
The plant's access control system is responsible for reading the card and opening the door or the barrier. InnerWeb is responsible for the second part of the question: whether the person has valid trainings, qualifications, a permit or a visit, and an active account. That is why InnerWeb does not manufacture or replace access control readers, but integrates with the client's existing access control system.
Technically, InnerWeb receives card swipe events from the access control system through a webhook and links them with qualifications, permits, attendance and the time and attendance register. The access control system remains the owner of the readers and of the decision to physically open, while InnerWeb delivers the verdict and records the event in the register.
What to settle with the access control vendor
The questions for the access control vendor are specific and can be closed in one technical conversation.
- Whether the system can send swipe events to an external address (webhook), and in what format.
- Which identifier the event carries: card number, user identifier, reader, direction, time.
- Whether the event contains the direction (entry, exit) or only the fact of a swipe.
- What the access control system does when the event recipient does not respond: queues, retries or skips.
- Whether swipes from several readers at one gate can be told apart.
Questions to close before the pilot, by addressee
What to settle with the plant IT department
The IT department is responsible for the route the event takes from the access control system to InnerWeb, and for what happens when that route fails.
- Network segment and firewall rules: which system may talk to which.
- Encryption of the connection and authentication of the event sender.
- Time synchronisation between the systems, because the order of swipes depends on the clocks.
- Behaviour when the link fails: whether the gate keeps working under fallback rules.
- Who owns the IT contact during the pilot.
Traps that appear in the pilot
The first trap is duplicated events. The gate panel rejects a double scan within a short interval on the server side, within a 5-second window, but duplicated events from the access control system require a separate finding: whether the source is the reader or a repeated send after a network error.
The second trap concerns the direction. The system determines the direction of an entry: a green verdict for a person from outside the plant gives entry, a green verdict for a person inside gives exit, and a red verdict gives a recorded refusal. If the access control system sends a direction, it must be settled whether it takes precedence over the InnerWeb logic. Without that settlement, an exit record may be read as an entry.
The third trap concerns people without a card. Guests and service technicians with a single-use QR badge pass through the scanner at the gate, not through an access control reader, so the attendance list must combine both sources. During the pilot it is worth testing two people from each category.
Pilot scope and criteria for moving on
It is worth limiting the pilot to one gate and one category of people. A good criterion for moving on is the agreement of three indications for the same people on the same day: the gate register, the attendance list and the record in the access control system. A discrepancy larger than a single case means that one element of the chain needs improvement before the rollout is extended.
After the pilot, further gates are added by repeating the settlements with the access control vendor, not by a new integration. This matters for the budget: the cost of extending depends mainly on the number of gates and the working time of the access control vendor.
Checklist
Video
Frequently asked questions
Does InnerWeb replace the readers at the plant?
No. InnerWeb does not manufacture or replace readers; it integrates with the client's access control system.
How does an event reach InnerWeb?
Through a webhook from the access control system. InnerWeb links it with qualifications, permits, attendance and the time and attendance register.
Does a card swipe always open the gate?
The access control system decides on the physical opening. InnerWeb delivers the verdict and records the event, so the way the connection affects the opening must be settled in the pilot.
Let's plan the pilot with your access control vendor
We will prepare the specification of the swipe events for the access control vendor and the list of settlements for the IT department.
Let's talk