Who these recommendations are for
The recommendations are aimed at the head of network maintenance, who is responsible for several dozen small sites with no permanent staff: sewage pumping stations, balancing tanks, water pumping stations, small treatment plants. Such sites have no porter or security guard, and entries are made by the utility's own crews and external contractors.
The goal is not to build a fortress, but to answer three questions after every entry: who was there, why, and whether they had the right to be there. Each recommendation concerns one decision that is worth making deliberately, rather than discovering it during the first inspection.
Recommendation 1: treat the scan as a control act
A scan of a QR badge or an RFID card gives a verdict on whether the person may be on site: whether they hold valid training, qualifications for hazardous work, a permit in progress and an active account. The scan at the gate is itself a control act and records the entry. There is therefore no need to enter the person separately in a logbook.
The decision on your side: who scans and with what. At sites without power and network the simplest option is scanning with the service technician's phone, and at sites with KD access control the event can be taken from the existing system.
BLE transmitter density by environment
Recommendation 2: plan for work without connectivity
Some sites have no permanent coverage. Actions that change data in the field without Wi-Fi are queued locally in the device's browser and replayed once the network returns. The backend recognises repeats, so resending does not create duplicates.
The practical conclusion: do not require the technician to wait for coverage before entering data. Require that after the visit they return to a place with a network before closing the working day, and check that the queue has been emptied.
Recommendation 3: name who is responsible for lone work
For lone work, technology alone is not enough: responsibility for the alarm must also be assigned. Stillness detection works on two sides: the app analyses the sensors, and the server independently measures time, and only when both agree is the full alarm triggered. Someone has to receive that alarm.
Set up a shift duty roster for receiving alarms and a stand-in for weekends. The system will send a push notification and an email to the people responsible, but the list of those people is an organisational decision.
Recommendation 4: do not lose alarms when the network is blocked
If the utility's network blocks all outgoing traffic from the application host, alarm webhooks are stored durably and an external poller collects them over an incoming channel. The alarm is not lost. It is worth settling this with the IT department at the design stage, so that the firewall is not a surprise.
The conversation with IT should cover whether the poller may query the host and from which address. Without such a channel, alarms will wait in the system instead of reaching the dispatcher.
Recommendation 5: transmitters only where location makes sense
Position is calculated from signals of several BLE transmitters averaged on the map, and the system works without GPS. Inside buildings, the rule of thumb is 1 transmitter per 100–200 m², and on plant roads about every 100 m. For a small pumping station of a few dozen square metres, location inside the chamber does not require a dense network.
The optional network on subscription is 100 transmitters for PLN 700 net per month, with no equipment purchase, typically covering about 20,000 m² (indicative range from 2025–2026 deployments; individual quotation). Calculate separately for each site, based on its area, rather than using one average for the whole network.
Recommendation 6: require a change log
Changes to permits, the taxonomy of hazardous work, training results, automation rules and inspection routes are saved with their author and time. For sites that nobody looks at every day, this is the only place from which it is possible to reconstruct who changed the access rules.
Review this log at the start of each quarter. What interests you are changes made outside working hours and unusual extensions of permissions.
Recommendation 7: start with a few sites
Do not try to cover the whole network at once. Choose three or four sites of different character: one with connectivity, one without, one used by external contractors. Such a selection will show all the variants, and the cost of a mistake will be small. The detailed plan is on the page about the pilot of entry control at water network sites.
Video
Frequently asked questions
Does every site need a transmitter network?
No. Transmitters are an option on request and make sense where the employee's location is needed. For small sites a scan and a register are often enough.
What if there is no coverage at the site?
Actions are queued locally on the device and replayed when the network returns, and repeats are recognised.
Does the scan replace the entry logbook?
Yes, because the scan records the entry and gives a verdict on permissions, so a separate entry is not needed.
Where can you see who changed the access rules?
In the change log, which records the author and time of changes to permits, training, rules and inspection routes.
Let's make a list of your sites
We will go through the seven decisions together on the example of your network and point out the sites where it is worth starting.
Let's talk