Scale and capacity
Question 1: when should LoRaWAN be considered at all? When the site approaches about 200-300 watches or when the client requires a standard. Below this threshold the simpler protocol is usually sufficient. LoRaWAN is an option, not the default decision.
Question 2: how many watches per gateway? In the LoRaWAN option, an 8-channel grid and adaptive data rate (ADR) provide capacity on the order of a thousand watches per gateway. This is an order of magnitude, which is confirmed by measurement at a specific site, taking into account alarm traffic and building structure.
Channels and ADR
Question 3: why 8 channels? Many channels allow the transmissions of devices to be spread out, so collisions are rarer than on a single channel. Question 4: what does ADR do? It adjusts the data rate to the radio conditions of each device: a watch close to the gateway can transmit faster and shorter, and a distant one more slowly but with greater range. This reduces the occupancy of the link and the battery consumption.
Gateway capacity versus the decision threshold
Keys and security
Question 5: what do the keys look like? In the LoRaWAN option the keys are per device. Each watch has its own key, so the loss of one does not force a key change across the whole fleet. For the IT department this means simpler procedures after a device is lost or stolen.
Backend and bridge
Question 6: do the application and its configuration have to change? No. With the LoRaWAN option the backend does not change its contract. A thin bridge decodes the data from the network server and passes it on as one more gateway. From the InnerWeb point of view it is another source channel for heartbeats, which is why the location and alarm logic stays unchanged.
Question 7: what does the bridge decode? The data from the network server in a form the backend understands, that is, the heartbeat information: the beacons heard, the signal strength, the battery state and the status.
Where it runs
Question 8: does it require the cloud? No. An on-premise deployment means the system runs in the plant network, without the cloud. InnerWeb works as an independent system complementing the client's existing systems: access control, time and attendance, HR and ERP. The network server and the bridge are set up in the same network.
Questions to measure before the decision
Before ordering the gateway it is worth answering the questions that this FAQ cannot answer: what is the layout of buildings and metal structures, where the gateway is to stand, how it will be powered, how long it must keep working after a power failure, who maintains the network server, and what the procedure for replacing a watch looks like. Measuring the range on a group of watches under real conditions is more important than catalogue figures.
Video
Frequently asked questions
Does LoRaWAN require changing the backend?
No. The backend contract stays, and the bridge decodes the data from the network server.
Can I keep the system in the plant network?
Yes, an on-premise deployment means the system runs in the plant network, without the cloud.
What does ADR do?
It selects the data rate to the radio conditions of the device, which limits the occupancy of the link.
Are the keys shared across the fleet?
No. In the LoRaWAN option the keys are per device.
Let's talk about the beacon layout at your plant
We will show the map, the readings and the configuration on your site plan. Book a short conversation with the InnerWeb team.
Let's talk