For whom and why this description
These recommendations are addressed to the IT or OT team and to the integrator who talks to the vendor of the access control system. InnerWeb does not manufacture or replace card readers: it integrates with the client's existing access control system as an independent complementary system, alongside access control, time recording, HR and ERP. That is why the quality of the data depends on how precisely the zones and readers are described on the access control side.
A good description of a time zone answers four questions: who, where, when and in which direction. Lack of an answer to the last question is the most common cause of reporting problems.
Recommendation 1: a direction on every reader
The rules for time zones and shift schedules require the readers in both directions of a passage to report the direction, entry or exit. Without this, anti-passback has nothing to work on, and the report cannot tell a late entry from an exit before the end of the shift.
The order to the vendor should list each passage with a separate entry reader and exit reader. If any gate has one reader serving both directions, it must be established how the controller distinguishes the direction, and this must be written into the specification.
Sample token renewals per day
Recommendation 2: stable names of punch locations
The punch location field distinguishes the locations of the readers. Events from a location that has no matching template in InnerWeb go to the log and do not trigger a training alarm. That is why location names should be stable, unique and agreed with the team that configures InnerWeb.
Renaming a reader on the access control side without informing InnerWeb is one of the most common reasons punches stop triggering rules. We recommend a log of name changes kept by the IT department.
Recommendation 3: authentication and token renewal
Calling the webhook requires a token obtained from the API login endpoint. The token has a short validity period and is renewed automatically by the integration, so no manual steps are needed on the access control side. We recommend that the integration renews the token ahead of expiry, not only after a refusal.
It is worth setting an alarm in the IT monitoring system for a series of refused responses from the endpoint, so that an authentication problem is visible before it affects the night shift.
Recommendation 4: resilience to bursts and repeats
At a plant with several staffing agencies, card traffic can exceed 2 000 punches per working day, and most of them fall within a few minutes before the start of a shift. The webhook must be resilient to bursts of events and to repeats.
On the access control side we recommend a queue with retries, and on the receiving side rejection of repeats. For a double scan of a code at the registration station, InnerWeb ignores the second scan within 5 seconds, but this is a different path from the access control card webhook, so the anti-duplication rules must be agreed separately in the specification with the access control vendor.
Requirements for events from the access control system
The integration specification assumes that the access control system sends events in real time. Each event carries the reader event time, the direction (entry or exit), the punch location and an event identifier. InnerWeb receives them through an authenticated webhook, and the punches feed the time records and attendance lists.
The rules for pairing entries with exits and for rejecting duplicates are set in the specification together with the access control vendor. This way both sides know which time is binding, how to treat a missing exit, and what to do with a repeated event after a resend.
A card punch in the access control system only says that a person passed a point. Where the person is after passing it is shown by the location on the map and the evacuation list in InnerWeb, so this information should not be expected from the access control system alone.
If any reader in the client's access control system does not distinguish the direction, this is a technical fact on the access control side. It must then be established with the vendor how the controller indicates the direction, and this must be recorded in the specification before the integration starts.
SLA parameters, meaning availability, response times and repair times, are set in the maintenance contract, for example availability of 99.5% per month. We recommend describing them before the integration goes live, together with the person responsible on the IT department side.
Checklist for the vendor
The points below are worth sending to the access control vendor as an attachment to the order.
- Entry or exit direction on every reader
- Stable, unique names of punch locations
- Event format with fields for reader time, direction, card, location and event identifier
- Token with a short validity period, renewed automatically by the integration
- Queue and retries when there is no response
- Rules for pairing entries with exits and for rejecting duplicates
- Log of reader name changes
Video
Frequently asked questions
Who configures the time zones?
Time zones and schedules are set in the client's access control system. InnerWeb receives punches through the webhook and does not change the controller configuration.
What happens to a punch from an unknown location?
An event from a location without a template in InnerWeb goes to the log and does not trigger a training alarm.
Does the webhook carry the passage direction?
According to the integration specification, the access control system sends events with the reader time, the direction entry or exit and an event identifier. The pairing and duplicate rules are agreed with the access control vendor.
Sources
Let's prepare the specification for the access control vendor
We will go through the punch format, location names and token renewal with your IT department before the vendor starts the configuration.
Let's talk