Why describe the installation before integration
InnerWeb receives card badge-in events from the access control system via webhook and links them with qualifications, permits, attendance and time recording. For this connection to make sense, each event must point to a passage, and the passage must be assigned to a zone in the installation description.
InnerWeb is a software producer: it does not manufacture or replace readers and access control cards. The installation description is therefore drawn up by the plant's integrator or the access control supplier, and we accept it as input data for the configuration.
Data about controllers
The controller is where the decision to let someone through is made, so the description starts with it. For each controller, record its designation, location, the number of readers it serves and the way it sends events to the parent system.
It matters whether the controller works autonomously when the connection to the server is lost, and what happens to the events stored in that time. This determines whether the badge-ins arrive later in full or part of them is lost.
Time windows for processing badge-ins in the installation description
Data about readers and the link
For each reader, record the protocol that connects it to the controller. OSDP runs on an RS-485 line and is a bidirectional protocol, and the controller constantly supervises the reader's status, which makes it possible to detect disconnection or tampering. Wiegand sends data in plain text, without encryption and without authentication, and does not offer such supervision.
Also record whether the Secure Channel with AES-128 encryption is enabled in OSDP, because in installation mode data flows in plain text. The Wiegand 26-bit format is open and publicly described, and its short bit length limits the number of unique identifiers, which can be a constraint when there are many cards.
Data about zones and the direction of passage
A zone is an area with defined rules of entry. For each zone, record which readers protect it, which groups of people have access to it and according to which schedule.
A separate point is the direction of passage. When the access control reader does not provide the direction, badge-ins are paired: an entry with an exit within a window of up to 13 hours, and duplicates within less than 180 seconds are rejected. The description should therefore indicate which readers are entry, which are exit and which are bidirectional.
How to use the list
The list is meant to be filled in by the integrator before the first technical meeting. A missing answer to one of the points does not block the integration, but it means we will accept an assumption and mark it in the documentation.
The completed description is an attachment to the event specification that the access control supplier sends to the platform. When the installation changes, for example when a reader is added, the description is updated together with the zone configuration.
Checklist
Video
Frequently asked questions
Who should record the installation description?
The integrator of the plant or the access control system supplier. InnerWeb is a software producer, so it accepts the description as input data for the integration.
Does missing information about the direction of passage block the integration?
No. Without a direction, badge-ins are paired: an entry with an exit within a window of up to 13 hours, and duplicates below 180 seconds are rejected.
Why does the reader protocol matter?
Wiegand sends data in plain text and without reader status supervision, while OSDP is bidirectional and makes it possible to detect a disconnected reader. This affects how much the events can be trusted.
Sources
Let us start with the installation description
We will provide the integrator with a ready form listing the data and discuss zone configuration on the platform side. Contact us for a talk.
Let's talk