Assumptions: on-premise and an independent system
An InnerWeb installation can run in the client's server room as an independent system complementing the client's existing systems: KD, RCP, HR and ERP. For the IT department this means its own host on the plant network, its own backups and its own update windows. For security it means a screen that runs on the same installation, with no dependency on the cloud.
The pilot limits the scope: one server room, one gate and one group of service firms. The other rooms are connected after the pilot closes. A scope like this can be assessed within a few weeks, without freezing other IT work.
Before the start, settle three things: who owns the register on the plant side, who runs the installation and who represents security. Without these three people the pilot gets stuck on the first question.
Stage 1: host, access and authentication
The IT department prepares the host in line with the plant's policy and enables the administrative accounts. Multi-factor authentication (email code or TOTP) is switched on per installation, with a trusted device period. For accounts that approve access to the server room this is a reasonable minimum.
At this stage roles and the scope matrix are set up. Permissions come from roles with inheritance, roles are granted along a seniority ladder, and a role higher than one's own cannot be granted. A pitfall: granting every administrator every role at the start, which is hard to undo a month later.
Also settle how the installation will communicate with the KD system and with the alarm network. If the plant network blocks outbound traffic, this has to be planned now, not after go-live.
Manual compilation of the register: entries and hours a year
Stage 2: gate scan and the security screen
Security gets the screen and learns a new rhythm. A scan of a QR badge or an RFID card gives a verdict: whether the person may be on site, based on valid training, qualifications, a permit in progress and an active account. Security sees the verdict and the list of missing items, not the full view of permits.
Every scan is an act of control and is recorded in the entry and exit log. A pitfall of the first days is scans skipped during heavy traffic. The fix: a short shift briefing and watching the gate during the first peak hours by a person from IT.
A planned visit replaces the permit requirement at the gate for one day, but training, qualifications and an active account still decide on entry. The visit has a host, whom the system calls once at the first entry. It is worth preparing short instructions for the hosts, because their phone will ring first.
Stage 3: KD badge events and location
Once the gate works, the server room door joins. InnerWeb receives card badge events from the client's access control system through a webhook and links them with qualifications, permits, attendance and time and attendance (RCP) data. Readers are not replaced. The integration requires cooperation with the KD integrator, so arrange their involvement at this stage in advance.
Location inside the building is based on one transmitter per 100-200 m2 and works without GPS. For the server room it is a complementary option: it checks whether the person in the permit is actually in the room. It is not required for the entry log and can be added in the expansion phase.
Pitfall: the time difference between systems. The audit log records local time in the Europe/Warsaw zone from October 2026, and entries from the winter seasons 2023/24-2025/26 are shifted by one hour. When comparing with KD badge events, check in which time zone the KD system records time.
Stage 4: pilot acceptance and expansion
The pilot ends with acceptance: a summary of entries, exceptions and problems. It is worth setting the criteria in advance: whether every entry has a permit, whether badge events arrive without gaps, whether security scans in all shifts. Compiling such a log by hand from paper takes about 72 hours a year at 288 entries, which gives a reference point in the sample calculation.
After acceptance, the expansion goes to the next rooms: OT cabinets, switchrooms, the backup room. Periodic reports for the board are added. It is worth revisiting the roles at this point, because after the pilot it becomes clear who really needs permissions.
Checklist
Video
Frequently asked questions
Does an on-premise installation require internet access?
It depends on the plant's requirements. On a network without outbound traffic, alarms are stored in a durable queue collected by an external poller, which is described on a separate page.
How long does the entry log pilot take?
The scope of one server room and one gate can be assessed in a few weeks. The time depends on the availability of the KD integrator and on the training of security.
Is a location inside the building required?
No. The entry log works on gate scans and KD badge events. Location from transmitters is an optional addition.
Let's talk about evidence of server room entries
We will show in a demo how badge events from your access control system connect with the permit and the log. No reader replacement and no card changes.
Let's talk