Why classification is the first question
An employee location and access control system sits on the border of two worlds. On one side it is business software: databases, accounts, attendance reports. On the other, a receiver antenna mounted in the turbine hall passes data to a server in the technology network. The decision on which side the system is considered determines who receives it, who has access to it and which architecture requirements must be met.
An integrator who does not settle this before the quote will get the offer in one version, and after talking with the automation department will have to add servers, VLANs and procedures that were not in the quote.
Stage 1: meeting with the automation department
Before the quote, plan a conversation with the head of automation or the OT lead. Bring a diagram in the PERA model, levels 0-6 with DMZ 3.5, and show where the system is to stand. Assume the OT network is separated by firewalls and no host has interfaces in two levels.
Settle three things in writing: whether the application servers stand in the OT network or in IT, whether data from the antennas leaves only through the main antennas to the OT VLAN, and whether the buyer foresees local operation without a connection to the manufacturer.
Share of main antennas, small antennas and reserve in the concept
Stage 2: architecture and VLANs
If the system goes into OT, the architecture includes separate VLANs for management, backup and monitoring, logs to SIEM, VPN access with 2FA and a jump host in the OT DMZ. Each of these elements has a cost: design time, hardware, maintenance.
In the concept for a large energy site the receiver network counted several thousand points, of which about 13% were main antennas with LAN and PoE. These main antennas are the points of contact with the OT network, so their number translates directly into the number of ports, cables and agreements with automation.
Stage 3: local operation and the alarm queue
The automation department often blocks all outbound traffic from application hosts. The system must then work in a mode in which alarm webhooks are stored in a durable queue, and an external poller picks them up over an inbound channel. The alarm is not lost, and outbound traffic stays closed.
A buyer from the energy sector may also require local operation in the OT network without a connection to the manufacturer, frames signed with the buyer's keys and a device trust procedure covering X-ray inspection of samples and control of firmware and keys. Set these requirements before the quote, because they change the scope of work.
Stage 4: what InnerWeb does not do and who is responsible for it
InnerWeb is a software producer. It does not produce access control readers and does not sell access cards: it integrates with the client's existing access control system and connects its events with qualifications, permits, attendance and time recording. For classification this matters, because part of the system (access readers) is already classified on the client's side, and only the software layer is added.
Record this division in the offer. The tap event is passed by the access control system, so the IT or OT side of the access control owner is the party to agreements on the webhook.
Quoting pitfalls
The first pitfall is a quote without a site visit. A scope that in the concept included a site visit, BLE propagation measurements, placement design per floor, integration with OT, system adjustment and training is hard to close honestly based only on a list of buildings.
The second pitfall is the hidden cost of classification: only after the OT decision does it turn out that a jump host, separate service accounts and a change procedure approved by automation are needed. The third is simultaneity: the IT team and the OT team do not receive the same documents at the same time.
In the concept for a large energy site, converting the quote to one wristband gave a figure of the order of 500 PLN one-off and about 5 PLN per month. These are indicative ranges from 2025-2026 rollouts; the individual estimate is separate, and the OT classification may move it up or down.
Checklist
Video
Frequently asked questions
Why does classification affect the price?
OT requires additional architecture elements: separate VLANs, a jump host in the OT DMZ, VPN with 2FA and logs to SIEM. Each adds design time and maintenance.
Who is responsible for the access control readers?
The access control vendor. InnerWeb does not produce readers or sell access cards, it only receives tap events from the existing system.
What if the OT network blocks outbound traffic?
Alarm webhooks are stored in a durable queue, and an external poller collects them over an inbound channel. The alarm is not lost without opening outbound traffic.
Let's agree the classification before the quote
We will prepare the PERA diagram and a list of questions for the automation department, so the quote does not change after the first meeting.
Let's talk