InnerWeb
Skip to main content

Guide: extending the pilot to more sites

A pilot of one area usually ends with the question of how to move on to further sites without building everything again. The answer lies in the order: first the location structure, then the transmitters, then the site configuration, and only at the end the number of users. Below are the steps that let you extend the deployment on the same platform.

95
sites on one platform in the municipal project
Source: karta
11,000
transmitters in the municipal project
Source: karta
5
levels of the structure: plot, view, building, line, location
Source: karta

Why extend on the same platform

In a municipal project one platform serves 95 sites of different geometry: over 120,000 m2, 11,000 transmitters and an accuracy below 1.5 m. Each site has its own configuration, but all of them run on a shared server, so the operator does not maintain many systems. This is the model that the team extending the pilot aims for.

For the project team this has a simple consequence: the pilot is not a separate product to be replaced, but the first site of the target structure. That is why the locations and the configuration are already named in the pilot the way they will be named across the whole network.

Step 1: record the location structure

The structure has levels: plot, view (division), building, line and location. The view carries georeferencing, and buildings are areas inside it. If the pilot covered one view, the next site is added as the next view or the next plot, without changing the logic of what already works.

Before adding a site, set the naming rules at all levels, buildings and lines included. Consistent names make reporting and finding events across the whole network easier, and changing names after an expansion is burdensome.

From a typical area to the municipal project

From a typical area to the municipal projectBar chart: 100 transmitters typically cover about 20,000 m2, and the municipal project with 95 sites covers over 120,000 m2.025,00050,00075,000100,000125,000m2 of area covered by transmitters100 transmitters (typical): 20,000 m2 of area covered by transmitters20,000100 transmitters (typical)Municipal project (95 sites): 120,000 m2 of area covered by transmitters120,000Municipal project (95 sites)
Source: Field card: coverage of a typical package of 100 transmitters and the total area of the municipal project

Step 2: count and place the transmitters

The placement rule is fixed: plant roads about every 100 m, and inside a building one transmitter per 100-200 m2. The position is calculated from the signals of several transmitters averaged on the map, and it works without GPS. For a new site, a plan with building areas and road lengths is therefore enough.

For the preliminary budget, the proportion from the offer is useful: 100 transmitters cover typically about 20,000 m2, that is on average one transmitter per 200 m2. Multiply the area of the site by this proportion, and then verify it on the plan, because the geometry of the plant can change it.

Step 3: configure the site separately

The configuration of each site is separate: the pulse period, inactivity, notifications and permissions. The pulse period of the LoRa watches is set in the panel within 30-3600 s, with a default of 120 s, and the change reaches the devices in response to the next pulse. This way a new site takes over the parameters of the pilot and changes only what its work requires.

The team records in one document what is common to all sites and what is local. Common settings go into the template, local ones into the configuration of the site.

Working without stable Wi-Fi

On sites without a good network, actions that change data performed in the browser are queued locally, and the server recognises repetitions. This applies to the actions covered by the queue, not to all functions, so the team checks the list of these actions for each new site.

Step 4: add users and licences

The number of licences is increased last, once the structure and the transmitters are ready. The price list scales with volume: a server with 10 licences costs PLN 800, with 50 licences PLN 2,500, with 100 licences PLN 4,000 net per month (indicative price ranges from deployments in 2025-2026; individual quote). The cost per licence falls from PLN 80 to PLN 40, so joining sites to one platform lowers the average cost per person.

For each new site the team appoints a local administrator and a person on the dispatcher side, who are responsible for acceptance, training and closing alarms.

Audit evidence: how to show that the extension was controlled

The duty to ensure safe working conditions arises from art. 207 of the Polish Labour Code (Kodeks pracy). The system provides evidence for an audit, not a guarantee of compliance, so the documentation of an extension should contain: the location structure, the transmitter plan, the site configuration and the acceptance protocol.

Such a set for each site lets the team show an auditor that the subsequent sites were commissioned in the same order and under the same rules. It is also the simplest way to keep a uniform standard across many sites.

Checklist

Video

Frequently asked questions

Does the extension require a change of platform?

No. Subsequent sites are added to the same platform, and each has its own configuration. The municipal project serves 95 sites this way.

Where should one start with a new site?

With the location structure: plot, view, building, line, location. Only then are the transmitters and the configuration planned.

Are sites without good network coverage supported?

Actions covered by the local queue are queued, and the server recognises repetitions. This applies to selected actions, so their list is checked for each site.

We will plan the extension of your pilot

Book a call with the project team. We will go through the order of steps for your next sites and calculate the number of transmitters.

Let's talk