Private LoRaWAN Deployment for Industrial Sites

Define the monitoring service before counting gateways

A factory collecting tank levels every few minutes has a different requirement from a maintenance team requesting vibration features from operating machinery. Identify the measurement, collection interval, transmission interval and useful arrival time for each device group. Record whether a delayed reading is still useful and how the user should recognise missing information. These decisions determine the network workload and the evidence needed at handover.

Include engineering, operations and the people responsible for the site's IT connection. A gateway installation can involve roof access, electrical work, antenna mounting, an equipment enclosure and approval to connect to a network. Agree those responsibilities early. The project schedule should include the actual access windows and approvals alongside equipment delivery, configuration and the time needed to observe representative operating conditions.

Build an endpoint register tied to the site drawing

Give each proposed endpoint an identifier and a location that someone else can find. Record the mounting surface, intended height, orientation and surrounding materials. A position beside an open doorway can behave differently once the door closes or a vehicle parks beside it. Identify basement rooms, metal cabinets, plant corridors, tanks and changing stock layouts as specific survey conditions.

An annotated drawing should show candidate gateways and the endpoints each position is intended to serve. Mark positions that are inaccessible during the initial visit and state how they will be tested later. For existing instruments, record the available output and its connection to the proposed LoRaWAN device. A radio survey and a measurement-interface survey answer different questions, and both belong in the installation scope.

Use a link budget to guide the survey

A preliminary link budget brings together transmitter power, antenna characteristics, cable and connector losses, the expected path and receiver capability. It helps identify a plausible arrangement and the locations requiring careful investigation. Keep the assumed equipment and configuration with the calculation so a later antenna or cable substitution can be reviewed against the original design.

The site survey checks those assumptions in the actual environment. Received signal strength and signal-to-noise ratio are useful observations, interpreted with the data rate and receiver information. A favourable reading at one moment is one part of the evidence. Capture repeated transmissions and the conditions around them, particularly where machinery, traffic or stored material changes the radio path. Interference observations should identify the equipment and method used to collect them.

Test the intended installation, including difficult positions

Survey equipment should represent the proposed device, antenna, enclosure and mounting arrangement as closely as practical. Document any differences. Holding a test device in the air outside a cabinet may be useful for diagnosis, but the acceptance record needs observations at the installed location. Include doors closed, normal plant operation and representative stock or vehicle conditions where they affect the path.

Compare candidate gateway positions using the same endpoint test method. Retain unsuccessful results as well as successful ones so the placement decision is understandable. A revised antenna position, an additional gateway or a different endpoint mounting arrangement can then be evaluated against the same requirement. For a structured record, use the industrial LoRaWAN coverage survey checklist and its editable worksheet.

Size traffic around the real reporting pattern

Network planning includes the number of devices, payload sizes, transmission intervals, radio settings and expected downlink use. A single test device reporting slowly cannot represent a completed installation whose devices all report together. Review whether scheduled transmissions can be distributed over time, and include joins, retries and configuration traffic in the proposed operating pattern.

Adaptive data rate can adjust transmission parameters for suitable devices and conditions. Record how it will be used and what configuration the survey actually exercised. An installation with changing obstructions needs observation under those changes. The acceptance plan should establish the behaviour of the intended operating configuration, including the settling period or additional observations needed after configuration changes, rather than relying only on an initial connectivity demonstration.

Connect radio reception to useful application data

A message may be heard by more than one gateway. The network server handles that reception information, while the application needs one correctly decoded business record. Trace a test reading from the endpoint through network processing to the report. Verify the device identity, engineering unit, timestamp and treatment of duplicate or delayed deliveries at the application boundary.

Define the difference between the time of measurement and the time of arrival. Some devices transmit a current reading; others send accumulated counts or retained samples. The decoder and report must preserve that meaning. When the user opens a tank or machine view, freshness should refer to the relevant measurement history. A gateway's online indicator alone does not establish that every endpoint is supplying current data.

Specify gateway power and 4G backhaul as part of the service

Assess the intended power point, enclosure, environmental exposure and maintenance access. Where continuity through an electrical interruption matters, size the backup arrangement for the agreed equipment load and operating period. Include the gateway, router and supporting network equipment in that assessment. A powered gateway still needs a working onward path to its network server or the retention behaviour specified by the design.

For 4G backhaul, check service at the proposed router and antenna position and under relevant operating conditions. Record SIM ownership, data charges, remote access and the route for resolving a connectivity fault. If a secondary connection is included, define what changes during failover and how recovery is tested. The handover should identify which component retains readings during an interruption and the actual limits established for that configuration.

Assign network-server and application ownership

The project may use an existing approved network-server environment or include a new instance in the scope. Name the owner of device provisioning, access permissions, backups, software maintenance and incident response. Access for the customer and service provider should follow their agreed responsibilities. Keep operational identifiers and configuration records available to authorised staff through the handover process.

At the application boundary, agree the payload decoder, device naming, units, alarm rules and destination reports. Identify who approves a change when a device firmware version alters the payload. The private and public LoRaWAN network guide explains architecture choices; this deployment service specifies the people, installation work and test records needed to put the chosen arrangement into operation.

Accept each endpoint against its intended task

Agree numerical thresholds, test duration and representative conditions before commissioning. A remote level trend and an operator response workflow may need different freshness criteria. List any conditions that were simulated or remain untested. The acceptance record should support a clear decision about each endpoint, including remedial work and a retest owner where the requirement has not yet been demonstrated.

Price the installation and its continuing responsibilities

The quotation should separate survey work, devices, gateways, antennas, mounting, power provision, 4G equipment, network-server configuration, application integration and commissioning. Include roof or high-level access and any site services needed during installation. State which existing equipment and interfaces the proposal assumes will be retained, and what discovery could change the scope after the survey.

Recurring costs may include platform hosting, connectivity, software support, instrument maintenance, battery replacement and site visits. Ask how a replacement device is provisioned and how the asset register is updated. Expansion should be priced against the next group of endpoints and their conditions. An accepted installation provides useful evidence for expansion, while new buildings, obstructions and workloads still require their own review.

Prepare a practical first enquiry

Send the site drawing, endpoint locations, measurement types, required reporting intervals and available power and backhaul information. Identify difficult access areas and the person who owns the resulting operational report. This allows an initial discussion to focus on the survey boundary, installation responsibilities and the records needed to accept the first stage.

The Industrial IoT service connects this network to wider monitoring and integration work. For coordinating instruments, existing systems and customer responsibilities across a project, use the IoT solutions overview. The deployment scope can then be written around a defined set of endpoints and the decisions their readings need to support.

Frequently asked questions

Technical references

The Things Network: RSSI and SNR explains the signal observations used during a survey. Its adaptive data rate documentation describes transmission-parameter adjustment. Sources reviewed 5 November 2026. The installation sequence and acceptance matrix above are project-scoping materials, with values and responsibilities set for the actual site.