The level model in one sentence
The plant structure has successive levels: plot, view (division), building, line and location. In the large-facility plant mode, the editor path is View, Building, Line, Location. Each practice below follows from the fact that this model is hierarchical and that a higher level sets the frame for the lower ones.
Practice 1: a view is a division, not a hall
In conversations with production, a hall means a building, but in the data model the level called a hall is a view, meaning a plant division or part of the plant. Buildings are areas inside it. Name views so that they can hold further buildings: the name of a division or part of the plant, not the number of a single hall.
The mistake here is costly: the view holds the georeferencing and the orthophoto, so rebuilding it forces the map to be calibrated again.
Number of levels in the plant structure model
Practice 2: floors only where they exist
Floor levels and the multi-level marker are created only for buildings with more than one level. A building with ground floor only does not get a floor row, because the level panel would show other buildings' floors. The rule is easy to check: if a building has one level, the data contains no floors.
In an expansion this keeps things tidy: adding a single-storey warehouse does not add stray rows to the level panel across the whole view.
Practice 3: lines as disjoint fields
Lines inside a building cannot inherit the full outline of the building or overlap on the same level. They get disjoint fields inside the building. When two lines share an area, the position of a person or machine in the shared zone is ambiguous, and reports and risks are assigned to the wrong line.
If two workstations physically touch, set the boundary through the middle of the passage, not through the middle of the machine.
Practice 4: the outline reduced by the wall thickness
Building children fit inside the outline reduced by the wall thickness. In the documentation example this is 1 m from each side. The migration gate requires zero lines extending beyond the footprint, so a line drawn on the outer edge of a wall is rejected before saving. Practice: set the margin once for the plant and apply it to all buildings.
Practice 5: assign data at the right level
Documents, audio and video recordings are assigned at each level of the plant hierarchy, with inheritance down the tree. Risks are assigned to locations at each level and to the type of hot work. Assign an instruction shared by the division to the view, and a workstation instruction to the location, so that materials are not duplicated on every line.
What to avoid
Do not use names that change with the organization (a manager's name, a project number). The structure has to survive a reorganization, so names should describe the place, not the people.
Checklist
Video
Frequently asked questions
Is a view the same as a building?
No. A view is a division or part of the plant, and buildings are areas inside it.
Why a wall margin in the line outline?
Building children fit inside the outline reduced by the wall thickness, and the migration gate requires zero lines outside the footprint. The margin prevents correctly drawn lines from being rejected.
Should a floor be created for a single-storey building?
No. Floors are created only for buildings with more than one level.
Let's review your plant structure
We will propose names and a split of levels that will hold further halls without fixes. Ask for a structure review.
Let's talk