InnerWeb
Skip to main content

Recommendations: multi-site configuration standard

With one site, configuration takes care of itself. By the third site, differences start to appear. Below are seven recommendations for the board of a network operator: what to unify right away and what to deliberately leave local, so that scaling does not end with ten versions of the same system.

120 s
default watch pulse period (range 30-3600 s)
Source: product documentation (card)
80 PLN
server cost per license with 10 licenses
Source: calculated from the price list
40 PLN
server cost per license with 100 licenses
Source: calculated from the price list

Who this standard is for

For the board, the operations director and the solutions architect in organizations that have from several to dozens of sites with different layouts: stations, warehouses, service points and small plants. The standard does not impose one map. It defines which decisions are made once for the whole network and which the site makes on its own.

The reference point is the city project with 95 sites on one platform, where a shared platform coexists with a separate configuration for each site. This principle is worth transferring to your own network.

Seven recommendations before the third site

The recommendations follow the sequence of decisions: first what is shared across the network, last how the work on the standard itself is organized.

1. Set one naming scheme for locations

The structure has levels: plot, view, building, line and location. Record what each level means in your network and require every site to use the same levels. Shared names make consolidated reports easier and let staff move between sites.

2. Choose one rule for placing transmitters

Adopt a baseline rule: plant roads roughly every 100 m, and inside a building one transmitter per 100-200 m2. The position is calculated from signals of many transmitters and averaged, so a fixed rule gives repeatable quality without GPS. Allow deviations only with a local justification.

3. Unify the watch pulse period

The pulse period is set in the panel: default 120 s, range 30-3600 s. The change reaches the devices in response to the next pulse, without reflashing the fleet. Adopt one period for all standard sites and a separate, shorter one for sites with elevated risk.

4. Define a shared alarm profile

Set the no-movement warning and alarm thresholds and the escalation rules centrally. For reference, in a working production deployment the no-movement alarm warns after 20 s, and after a further 30 s without a response it raises an alarm. You will adjust the profile to your own risk, but all sites should start from the same one.

5. Keep geometry and checkpoints local

Maps, transmitter positions and round checkpoints belong to the site. The people on site know where the tank is and where the fence ends. Forcing one plan would destroy the sense of location.

6. Match the license and transmitter scale to the growth plan

The price list scales with volume: a server with 10 licenses costs 800 PLN, with 50 licenses 2,500 PLN and with 100 licenses 4,000 PLN net per month, and transmitter leasing is 7 PLN per unit up to 500 units and 3.5 PLN above 6,000. Do not buy licenses for the first site at a scale that will be too small after a year. These are indicative ranges from 2025-2026 deployments; pricing is individual.

7. Name an owner of the standard

One person or team maintains the standard document and approves deviations. Without an owner the standard falls apart after a few months, because every site adds its own exceptions.

Monthly server cost by number of licenses

Monthly server cost by number of licensesBar chart: 800 PLN for 10 licenses, 2,500 PLN for 50 licenses and 4,000 PLN for 100 licenses.01000200030004000PLN net per month10 licenses: 800 PLN net per month80010 licenses50 licenses: 2500 PLN net per month250050 licenses100 licenses: 4000 PLN net per month4000100 licenses
Source: Price list; indicative ranges from 2025-2026 deployments; individual pricing

What the numbers show: cost per license

The price list gives the server cost per license: 80 PLN with 10 licenses, 50 PLN with 50 and 40 PLN with 100 (calculated from the given amounts). The difference between the first and the last threshold halves the unit cost. For the board this is an argument to plan volume in advance rather than buy licenses one at a time.

How to roll out the standard in stages

The safest sequence is two pilot sites. On them, check the naming, the pulse period, the alarm profile and the transmitter rule. After corrections, the standard is saved as the pattern for the third and subsequent sites.

Each new site goes through the same short path: location structure, map, transmitters, alarm profile and round routes. Deviations from the standard are recorded in a register, so that after a year you know where they came from.

What the standard does not replace

The standard does not replace the risk assessment of each site. The duty to ensure safe working conditions results from Article 207 of the Labour Code, and the system provides evidence for an audit, not a guarantee of compliance. The standard organizes the configuration, but the owner of each site decides the thresholds for that site.

Video

Frequently asked questions

Does the standard mean identical maps at every site?

No. The standard covers rules: naming, pulse period and alarm profile. Maps and checkpoints remain local.

Can the pulse period be changed after deployment?

Yes. It is set in the panel in the range 30-3600 s, and the change reaches the watches in response to the next pulse, without reflashing.

How many sites are needed as pilots?

Usually two different sites. The first teaches the rules, and the second checks whether the standard works with a different geometry.

Sources

Set the standard before the third site

We will walk you through the list of shared and local decisions for your network and propose two pilot sites.

Let's talk