How to use the list
The list has 11 items and falls into four areas: radio, gateways, security and testing. Close each item with a record: who checked it, when and with what result. The record supports audit evidence and also makes it easier to extend the deployment to further halls later.
The deployment manager fills in the list together with the supplier and the IT department. Items in the security area need IT involvement, because they concern the connection of the gateway to the system.
Radio: band and parameters
The radio of the watch and the gateway works in the 869.525 MHz channel, within the 869.4-869.65 MHz sub-band with a power limit of 500 mW ERP and a 10% airtime limit. The watch transmits at +14 dBm, SF9, a 125 kHz width and a private sync word.
A frame lasts about 230 ms, so at a 120 s interval the airtime use is about 0.2%. With more watches, also calculate the occupancy of the whole channel: for 100 watches it is about 19%. If another system in the 868 MHz band exists on site, prepare a frequency plan before buying the gateways.
Division of checklist items by area
Gateways: coverage, power and internet access
Not every gateway at a plant has Wi-Fi, and the data from all gateways must reach the one that has internet access. For each gateway choose one way of connecting: Wi-Fi, Ethernet or PoE in halls with cabling, an LTE module where there is power and GSM coverage, or a repeater gateway with a hop counter of 2-3.
Power is the most common gap in pilots. A gateway in a place without permanent power is not a gateway, only a plan. Also check the enclosure and the environmental conditions of the mounting point, especially outdoors.
Gateway time
The time source for the watch is the gateway: it synchronises via SNTP and includes the UTC time in each acknowledgement. The gateway must therefore have access to a time server, and the IT department should allow it through the firewall.
Security: encryption, TLS and token
InnerWeb v2 protocol frames are encrypted with the AES-128-CCM algorithm, with an 8-byte authentication tag and counters that prevent frame replay. The gateway validates the TLS chain of the connection to the system and can send a gateway token, which the system enforces once the token list is set.
The order matters: first enter the token on the gateways, and only then turn on its enforcement in the system. In the reverse order the system would reject frames from gateways that do not yet have the token, which looks like a radio failure.
Pilot test and completion criteria
The pilot should cover a group of watches in different parts of the site: next to a gateway, at the edge of coverage and in a place without beacons. When the watch hears no beacon, the frame is still sent, and the system substitutes the last known location. Check whether the panel shows the battery, the status and the inactivity also from such places.
Define the completion criteria: the share of frames that reached the system, the SOS arrival time with confirmation on the watch, and the battery state after a week. Without numbers a pilot ends with an opinion, not a decision.
Checklist
Video
Frequently asked questions
What most often blocks a LoRa pilot?
No power at the gateway location, a gateway without access to the time server, or a token set only on the system side. All three items are on the list.
Does a gateway need Wi-Fi?
Not every one. At least one gateway must have internet access, and the others can pass frames through a repeater or have an LTE module or Ethernet.
Who should fill in the list?
The deployment manager with the supplier, and the items on TLS, the token and time together with the IT department.
Let us go through the list with your team
Before the LoRa pilot we will go through all the items of the list with the deployment manager and the IT department. Let us arrange a call.
Let's talk