InnerWeb
Skip to main content

Implementation notes: site and building addressing

By the tenth site, the names of locations matter more than the transmitters themselves. The system administrator who sets up the plot, view, building, line and location structure creates the language that dispatchers, reports and permits will use. Below are implementation notes: the order, the rules and the georeferencing pitfalls at the map stage.

5
levels of location structure
Source: product documentation (card)
95
sites in the city project on one platform
Source: city project (card)
780
positions to name in the 10-site example
Source: sample calculation

Five levels of location structure

The location structure has five levels: plot, view (department), building, line and location. The view carries the georeference, meaning the link between the map and coordinates, and buildings are areas inside the view. This dependency has practical consequences: if the georeference of a view is wrong, all buildings inside it inherit the error.

The structure works at scale. The city project covers 95 sites of different geometry, over 120,000 m2 and 11,000 transmitters on one platform, with a separate configuration for each site. Shared addressing is the condition for such a project to remain readable.

Stage 1: fix the vocabulary before drawing the first map

Before starting work in the system, write down what each level means in your organization. Is a view a production department or the whole site area? Is a line a process line or a traffic route? Record the answers in a one-page glossary and apply the same one at all sites. Fixing names after ten sites are live requires work at each of them.

Number of positions per level, 10-site example

Number of positions per level, 10-site exampleHorizontal bar chart: 10 plots, 10 views, 40 buildings, 120 lines and 600 locations in a sample network of ten sites.0200400600positionsPlotsPlots: 10 positions10ViewsViews: 10 positions10BuildingsBuildings: 40 positions40LinesLines: 120 positions120LocationsLocations: 600 positions600
Source: Sample calculation: 10 sites, 1 view, 4 buildings, 3 lines per building, 5 locations per line

Stage 2: view and georeference

The view is the level at which the map is anchored in space. Start with control points that can be reliably identified on the ground: building corners, gate posts and characteristic road junctions. The more precisely you define them, the fewer errors the buildings inside the view will inherit.

The position of a worker is calculated from signals of many transmitters and averaged on the map, without GPS. The georeference does not replace the transmitters, but it decides where on the real terrain the calculated position will appear.

Typical mistake: shifting the whole view

If the map is shifted by a few metres relative to reality, all points in the view are shifted by the same amount. This is detected by comparing the position of a watch standing in a known place with its position on the map.

Typical mistake: different reference systems at neighbouring sites

With many sites, the same points may be defined in different systems. Set one system for the whole network and record it in the standard.

Stage 3: buildings as areas inside the view

A building is an area within a view, not a separate entity outside it. Draw the building outline inside the view, so that the worker's position passes smoothly from the road to the interior. Inside a building one transmitter per 100-200 m2 is usually assumed, and on plant roads roughly every 100 m, so the outline and the number of transmitters should match these proportions.

Stage 4: lines and locations

Lines and locations are the levels that most often appear in permits, alarms and rounds. Give them names that a person outside the maintenance department will understand. If the name of a location in an alarm is understood only by the administrator, the dispatcher loses time translating it.

Sample calculation: how many positions get created

To show the scale, assume sample figures: 10 sites, each with one view, 4 buildings, 3 lines per building and 5 locations per line. That gives 10 plots, 10 views, 40 buildings, 120 lines and 600 locations, a total of 780 positions that must be named consistently. These are sample assumptions, not data from a specific installation. They show that without a glossary, after a few sites, hundreds of positions appear whose names will collide.

List of pitfalls

The most common mistakes become visible only when working with the dispatcher:

  • No glossary of levels, so the same department has two different names at two sites.
  • Georeference of a view done from a photo, without control points on the ground.
  • Building outline drawn outside the view, so the position jumps.
  • Names of locations too general, such as 'hall' instead of 'hall 2, packing line'.
  • Renaming after the sites go live, without updating permits and reports.

Video

Frequently asked questions

Which level carries the georeference?

The view (department). Buildings are areas inside the view, so they inherit its georeference.

Does georeferencing replace the transmitters?

No. The position is calculated from signals of many transmitters. The georeference decides where on the terrain the calculated position will appear.

When should the naming be fixed?

Before the first map. Changing it after many sites are live requires corrections to permits, reports and maps at each of them.

Let us build a location glossary for your network

We will help design the plot, view, building, line and location structure and check the georeferencing on a pilot site.

Let's talk