Starting point: 95 sites that are not alike
The city project covered 95 sites of very different shapes and functions. Together that is over 120,000 m2 of area covered by localization. If each site were treated as a separate system, there would be 95 installations to maintain, 95 sets of passwords and 95 different ways of reporting. If one geometry pattern were forced on everyone, the local maps would lose their meaning.
This is exactly the dilemma a network operator of stations, warehouses or service points faces: the sites share common rules but have different plans. That is why it is worth looking at how it was solved at city scale.
Solution: one shared platform and a separate configuration per site
The core of the solution is a split of responsibility. The platform is one: it has a common user account base, a common way of recording events and a common interface for the dispatcher. The configuration is local: each site has its own map, its own transmitter layout and its own settings.
The location structure keeps this in order. The system provides levels: plot, view, building, line and location. A view carries the georeference, and buildings are areas inside the view. As a result, a site with a complicated plan does not force changes on the others.
What is shared
The rules are shared: how pulses are sent, the data structure, the alarm rules and the interface. Someone who learned to operate one site can handle the other 94 without training from scratch.
What is local
Local are the geometry of the site, the number and position of transmitters, place names and thresholds that reflect local risk. This is the field where sites rightly differ.
Server cost per license at different scale
Scale and accuracy: figures from the project
The project runs 11,000 transmitters and location accuracy is below 1.5 m. The position does not come from a single transmitter but from signals of many, averaged on the map, and it does not require GPS. This matters inside buildings and where satellite reception is weak.
For clarity: the arithmetic average is about 116 transmitters per site (11,000 divided by 95). This is only an average from the given indicators, not a description of the layout at any particular site. For industrial plants the layout recommendations are different: plant roads are covered roughly every 100 m, and inside a building one transmitter per 100-200 m2 is assumed.
Lessons for a network operator
Four conclusions from the city project can be transferred to a network of stations, warehouses or service sites.
- Standardize rules, not plans: one platform and one alarm logic, but each site keeps its own map.
- Plan the location structure upfront: fix the names of views, buildings and lines before adding the first site, because changing the addressing later costs time.
- Scaling pays off on price: the price list falls with volume, as described on the page about the configuration standard.
- Keep field truth: if the local service indicates that a point on the map is shifted, correct it locally without changing the pattern.
Economics of scale: what changes with the number of sites
The price list scales with volume. A server with 10 licenses costs 800 PLN net per month, with 50 licenses 2,500 PLN and with 100 licenses 4,000 PLN net per month. Transmitter leasing is 7 PLN per unit up to 500 units and 3.5 PLN above 6,000 units. These are indicative ranges from 2025-2026 deployments; pricing is individual.
Per license, the server costs 80 PLN with 10 licenses, 50 PLN with 50 and 40 PLN with 100 (calculated from the given amounts). The more sites, the lower the unit cost, and the administration stays in one place.
What this case does not say
The city project has its own context and does not replace an analysis of your own network. Conditions can differ: building density, accuracy requirements and the organization of service. That is why, before scaling, it is worth launching one or two pilot sites and checking what stays shared and what stays local. Only then is the standard copied to other sites.
Video
Frequently asked questions
Did 95 sites require one shared map?
No. The platform is shared, but each site has its own configuration and its own map. That was the design assumption of the project.
Where does the accuracy below 1.5 m come from?
The position is calculated from signals of many transmitters and averaged on the map. It is not based on GPS.
Can these figures be transferred to another network of sites?
Partly. Conclusions about structure and standardization are general, but the number of transmitters and the prices are set individually.
Plan a standard for your network of sites
Let us talk about what should be shared in your network and what should stay local. We will prepare a plan of pilot sites.
Let's talk