InnerWeb
Skip to main content

Mezzanines and half-landings on the floor map: recommendations for the integrator and designer

A mezzanine in a hall and a half-landing on a staircase are places where the building numbering and the numbering in the system drift apart. Below are seven recommendations for the IT integrator and the building designer on how to order the floors so that the selector P, 1, 2 does not mislead the dispatcher during an alarm.

2
minimum levels for the selector to appear
Source: card
12
buttons in the selector window
Source: card
0.55 m
thickness of line walls against 1.6 m building walls
Source: card

Who these recommendations are for

The recommendations are aimed at the IT integrator who builds the plant model on the map, and at the designer or investment manager who knows the layout of levels from the building documentation. These are two different perspectives, and that is where the ambiguity arises: the same level has one name in the design, another on the sign on the wall, and a third in the system.

The level selector appears only when the selected building has at least two levels, and the labels in the Polish version are P, 1, 2 and so on. The dispatcher therefore sees a short label, not the full name from the documentation, so its meaning has to be unambiguous.

Recommendation 1: one numbering rule for the whole plant

Decide before entering data whether the entrance level is called P or 0, and keep that rule in every building. Mixing rules within one plant means the dispatcher remembers the numbering of one building and applies it to another.

Write the numbering rule on one page and attach it to the implementation documentation. For the dispatchers a table is enough: the level in the design, the label on the selector, and the everyday name.

Thickness of walls on the interior map (m)

Thickness of walls on the interior map (m)Bar chart: a line wall is 0.55 m, a building wall is 1.6 m.00.511.52mLine or room wall: 0.55 m0.55 mLine or room wallBuilding wall: 1.6 m1.6 mBuilding wall
Source: Function card: line walls 0.55 m, building walls 1.6 m

Recommendation 2: a mezzanine is a separate level when people can stand and work on it

If people spend time on a mezzanine and their position is needed, treat it as a separate level in the model. If it is only a service platform that a person crosses in a few minutes, adding a level increases the number of buttons in the selector without any real benefit.

A practical criterion: during an incident, should the dispatcher be able to send help to that level, and not only to the hall? If yes, the level goes into the model.

Recommendation 3: name half-landings the way people on site say them

A half-landing has no number of its own in the selector unless it is a level in the model. Agree with the operating staff whether they call it the first floor with an index or a part of the stairwell. The everyday name should be recorded in the implementation documentation, so the dispatcher can translate it into a label without guessing.

A good practice is to mark the half-landings on a plan printed for security. A simple drawing with the selector labels saves time at the first conversation with the person on site.

Recommendation 4: fit the model to the structure of the plant

In a model of a multi-building plant the hall is a view or a department, the area is a building, and the line is a floor. In a single-hall model the hall is a hall, the area is a zone, and the line is a production line. The question about mezzanines and half-landings means something different in each of these models: in the first it concerns a level in a building, in the second usually a zone in the hall.

Before you enter data, decide which model fits the plant. Changing the model after the data is entered means rewriting the links.

Recommendation 5: do not overload the selector

Above 12 levels the selector shows a window of 12 buttons with arrows, and the mouse wheel scrolls the list by one level. Every extra level means extra scrolling. For buildings with a dozen or so levels, avoid entering levels that nobody visits.

If mezzanines and half-landings would push the number of levels above 12, consider whether some of them should be described as part of the neighbouring floor.

Recommendation 6: check the readability of walls and colours

The walls of the building the user is in are red, and the walls of a line or a room are blue. The walls of a line are 0.55 m thick, against 1.6 m for the building walls. For mezzanines the difference in thickness helps to tell the building wall apart from the wall of a local room.

In the acceptance trial, ask a person from the operating staff to describe what they see on the screen. If they confuse the red building walls with the blue room walls, that is a signal to simplify the model.

Recommendation 7: test with a person, not only with the documentation

The best test is a walk: a person with a phone moves from level to level, through the mezzanine and the half-landing, while a second person checks whether a double-click on that person on the map opens the correct floor. The documentation may be correct and the model wrong.

Record the result of the trial in the acceptance protocol, with the list of levels and a confirmation of the position on each.

Video

Frequently asked questions

Does every mezzanine have to be a separate level in the system?

No. A separate level makes sense when people work on it and their position is needed. A service platform alone usually does not need its own label.

How are the levels labelled in the selector?

In the Polish version the labels are P, 1, 2 and so on. The selector appears only when a building has at least two levels.

What about a building above 12 levels?

The selector then shows a window of 12 buttons with arrows, and the mouse wheel scrolls the list by one level.

Building the model of your floors?

We will go through the floor documentation with you and agree the numbering before the data reaches the map. Book a call.

Let's talk