For the IT administrator: access and authentication
The IT administrator is responsible for ensuring that the access control system can call the webhook securely. The call requires a token obtained from the API login endpoint; the token has a limited validity period and is renewed automatically by the integration. Before going live, check whether the access control vendor has a technical account, whether it renews the token with a margin, and whether it logs in again after an authorization rejection.
Also verify the network connection: whether the access control server can reach the API address, whether the firewall rules allow it, and whether events are not lost during a short outage. InnerWeb provides an API and webhooks for integration with plant systems, so the same channel can later be used for further scenarios.
For the IT administrator: data and fields
The report carries the event time from the reader, the place of the swipe and the person's data. The first and last name and the company name are required, and the active card number is the identifier linking the swipe to the account. A swipe by an unknown person creates an account and a company from the report data, so the data in the access control system must have one consistent spelling, especially the names of work agencies. Before the start, agree with the access control vendor on a dictionary of company names.
Split of checklist items between roles
For the security manager: places and templates
The security manager knows the readers and their layout. The swipe place field distinguishes locations, and events from a place without a template in InnerWeb go to the log and do not trigger a training alert. Before the start, prepare a list of all readers with their place names and make sure each has a matching template.
Also determine which training requirement applies: the OHS training requirement can be set to cover all companies except the indicated exceptions, and a training group can have versions in several languages. This matters for a plant with agency workers of different nationalities.
Joint: requirements for event sending
Both should know the three requirements of the specification. The access control system sends events in real time and with the event time from the reader. Each event carries the direction of entry or exit and an event identifier. The rules for pairing entries and exits and for rejecting duplicates are set in the specification with the access control vendor. The traffic at a plant with several work agencies can exceed 2,000 swipes per working day, so the integration must handle bursts and repetitions.
InnerWeb does not produce or replace readers. If a reader does not send events, the solution is configuration on the access control side, not replacing the hardware.
Final test before production
Run a live trial: a known person, an unknown person, a double swipe, a swipe at every reader on the list. For each event check whether it is visible in the entry register, not only in the account history, because an entry in the account history does not yet mean a working time record. Save the results and the date of the trial as evidence for the audit.
Checklist
Video
Frequently asked questions
Who owns the list of readers?
The security manager, who knows the layout of the readers. The list is the basis for the swipe place templates in InnerWeb.
What if a reader does not send events?
The solution is configuration on the access control side. InnerWeb does not produce or replace readers.
Is checking the log enough?
No. The swipe should be visible in the entry register, because an entry in the account history does not yet mean a working RCP.
Let's check the readiness of your plant
We will go through this list with your IT administrator and security manager before go-live. Book a call with the InnerWeb team.
Let's talk