Surveying cellular connectivity for fixed IoT

A postcode result describes an area under a set of modelling assumptions. It cannot account fully for a particular equipment enclosure, basement, wall construction or surrounding machinery. A phone held outside the building is also a different test from an industrial modem operating inside a closed cabinet.

Begin with the proposed mounting point and the complete installation. Record the building, floor, room or asset reference, cabinet position and whether doors or covers are open. Note the device model, modem variant, firmware, SIM profile and power supply. Photograph the position where appropriate so that a later engineer can reproduce it without relying on a description such as near the window.

Netavo's multi-network IoT service uses its own mobile core and provides access to all four UK networks. Multiple access options are useful inputs to a site assessment, but each permitted network still needs to be considered at the relevant location. A network that performs well beside the installer may behave differently once the device is mounted.

Netavo supplies the multi-network SIM service. The survey, the antenna choice and the installation sit with the installer or the customer, and this commissioning record is what to ask them for.

Signal bars are a simplified presentation chosen by the equipment vendor. They are helpful for a quick indication but poor evidence for comparing devices or returning to a site months later. Where the modem exposes them, capture measurements such as RSRP, RSRQ and SINR alongside the selected network and radio technology.

For LTE, RSRP describes reference-signal received power, RSRQ describes reference-signal quality, and SINR describes the relationship between the useful signal and interference plus noise. Read those values using the equipment supplier's guidance, such as Teltonika's explanation of mobile signal measurements. Do not apply one universal pass threshold to every modem, band and workload. A stronger power reading does not necessarily mean a cleaner or more usable connection.

Record application outcomes at the same time. Can the unit register, establish data service, resolve its destination and send a message that the server acknowledges? How long does this take? Can it receive a configuration response or complete an expected update? A speed test alone does not answer these questions for a small telemetry device.

For EV charging, a useful test might follow the charger's actual management exchange rather than a laptop download. Keep the device and application supplier involved so the acceptance criteria reflect their supported operation. Record failed attempts as well as successes; intermittent failures are part of the result, not observations to discard.

Test with the enclosure closed and the installation powered as it will be in service. Where practical, repeat at different times and during representative site activity. Changes in surrounding equipment, vehicles or occupancy can alter the installation conditions, while network loading can change application performance. A single successful session proves only that one session worked.

If an antenna is required, use the equipment supplier's supported antenna arrangement. Record its model, position, orientation and cable details. Longer cable runs introduce loss, so moving an antenna is not automatically an improvement. Check environmental suitability, mounting permissions and safe installation requirements with the responsible installer. Keep the evidence about what was installed, not merely what was proposed.

Repeat the application test after any change in position, antenna or configuration. Include a controlled device restart and confirm that service returns without an engineer manually selecting a network. Where the operating requirement includes recovery from coverage loss, agree an appropriate test method with the suppliers and record the result.

Finish with a commissioning record that names the test date, person, equipment configuration, networks observed, measurements, application outcomes and unresolved limitations. Give every limitation an owner and a next action. Preserve this alongside the asset register and use it as the baseline after firmware changes or a reported fault. The objective is a supported installation that performs its job, not an attractive signal reading captured before the cabinet door was closed.