Starting point: one building, seven levels
A furnace house in an insulation materials plant is rarely a single-level hall. It has service platforms, galleries above the furnace zone, a loading level and a technical level. In the scenario described, the building had seven levels, and the locations moved from the old register were labelled with room codes. Some codes started with a level number, others had no prefix at all.
The structure model has four tiers: view (department), building, line and location. A floor is a property of the building, not a separate tier. In a large-plant mode the editor path is view, building, line, location, so the level has to be assigned where the editor reads it: to the line or to the location.
The administrator's task was specific: after the migration in the test environment, each location must stand on the correct level, and an operator switching floors must see only what belongs to that level.
Assignment rule: level prefix and level 0 m
The migration rule for a building with seven levels has two parts. A line without an assigned floor goes to Level 0 m, that is the ground floor. Room codes with a prefix that is a level number go to the matching floor. A code starting with the digit for the third level lands on the third floor, without manual clicking.
The rule has one trap: a code without a prefix is not an error, it is simply the default position. Before the migration, the administrator should review the list of codes and mark those that deliberately stay on the ground floor. Otherwise the ground floor collects everything nobody recognised and loses its value as a source of information about where a machine really stands.
- Code with a level prefix: goes to the indicated floor.
- Line without a floor: goes to Level 0 m.
- Code without a prefix in a multi-level building: ground floor, flagged for review.
- Level change after migration: edit the location, do not rebuild the building.
Example distribution of 70 locations across floors
Mistake we avoid: a covered ground floor and other buildings' levels
The floor panel and floor rows are created only for a building with more than one level. When a building with a single ground floor still gets a panel, the editor starts showing other buildings' levels across the whole view. As a result, the ground floor of one hall can end up covered by the floors of another building.
That is why the furnace house scenario checks two things separately. First, whether the multi-level building has a floor panel. Second, whether single-level buildings in the same view do not have one. Only both conditions together give a map where switching to the seventh level of the furnace house does not switch off the ground floor of the neighbouring hall.
A control room operator who switches levels during hot work must not lose track of locations in the rooms next to it. A floor error is not a cosmetic issue on the map. It is the address of the work site in the permit.
Verification gate: compare levels the way the editor shows them
The editor draws a location without a floor on the ground floor. The migration check therefore has to compare levels as the editor renders them, not by the identifier alone. A location with an empty floor field and a location with the ground floor set explicitly look like the same place on screen.
Without this normalisation the gate reports false differences or, worse, lets real ones through. In the test we applied one rule: every gate has a red test, a deliberately broken example that the gate must stop. Only then does a green result on a building with seven levels prove anything.
Conclusions and order of actions for the plant
The scenario leads to a simple order. First, a list of multi-level buildings in the plant. Then the rule for room code prefixes. Then the migration in the test environment and a review of every floor in the editor. Finally the gates with red tests, and only then the move to production.
The effect for the end user is measurable in practice: the contractor choosing a place in a permit sees the room on the correct level, and the person accepting the permit knows the height at which the work will take place. This matters for work at height and hot work, where the level decides the reach of sparks and the evacuation route.
Example distribution of locations across levels
| Parameter | Value |
|---|---|
| Number of locations in the building | 70 locations |
| Number of levels | 7 levels |
| Share of ground floor | 26 % |
Result: 18 locations on the ground floor, 52 on the six floors above.
Note: Example calculation; the figures are assumptions for your own review, not data from a specific plant.
Checklist
Video
Frequently asked questions
How does the system treat a line without an assigned floor in a multi-level building?
A line without a floor goes to Level 0 m, that is the ground floor. The administrator should review such a list after the migration, because the ground floor must not become a bin for unrecognised positions.
Can room codes control the floor?
Yes. A code with a prefix that is a level number goes to the matching floor. A code without a prefix stays on the ground floor and requires a decision by the administrator.
Why does a single ground floor not get a floor panel?
The panel and floor rows are created only for a building with more than one level. With a single ground floor the editor would start showing other buildings' levels across the whole view.
How do you check that the floor migration is correct?
By comparing levels the way the editor renders them, and by running a red test for every gate. A green result without a red test is only a hypothesis.
Do you have a building on several levels?
Describe the floor layout and the way room codes are written. We will prepare a migration scenario in the test environment with the gates to check it.
Let's talk