Quick answer: level of detail convention
Review focus: level of detail convention.
The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. Because EBUNGE movable wall panels are individually movable, suspended from a top track, cross the opening without a floor track, and park at a planned stacking position, the model must show the overhead route, the clear floor line and the parking zone as coordinated geometry rather than as a generic wall object. This article sets out a planning framework for naming, classifying and detailing those elements. It does not replace project-specific support, acoustic and dimensional confirmation.
Why Federated Coordination Breaks Down Around Movable Partitions
Project review term: level of detail convention.
Movable partitions sit at the intersection of architecture, structure and services. A panel that looks correct in plan can conflict with a beam, a duct or a ceiling void once the federated model is combined. The failure is rarely geometric alone; it is usually a naming and detail-level failure. One discipline models a single wall object, another models a track, and a third assumes a floor guide that does not exist in a top-hung system.
When element names and level of detail are not agreed, coordination meetings spend time decoding the model instead of resolving clashes. The framework below is deliberately evidence-bounded: it defines how to describe and coordinate the partition, not how to promise performance that must be confirmed per project.
Define the Element Taxonomy Before Modelling Begins
Coordination scope: level of detail convention.
Start with a short, controlled vocabulary. Every movable partition assembly should decompose into recognisable parts: the panel leaf, the top track or suspension route, the stacking or parking zone, and the opening or clear passage. Each part receives a stable name and a classification code that survives model federation.
A workable convention separates the assembly from its components. The assembly name describes the room or zone it serves; the component names describe function, not manufacturer marketing language.
A Naming Pattern That Survives Federation
Use a fixed field order, for example: system type, location, component, and instance. Consistency matters more than the specific words chosen. If one team writes ‘MovableWall’ and another writes ‘Partition_Mov’, automated checks and filters will not group them.
Classification and Parameter Discipline
Attach parameters that carry coordination meaning: opening width, clear height, parking direction and route type. A parameter field is a container, not a certification.
Set Level of Detail by Project Stage, Not by Habit
Checklist focus: level of detail convention.
Level of detail should rise as decisions are made. Early stages need enough geometry to test space planning and route feasibility. Later stages need enough definition to coordinate the top track, the stacking zone and the surrounding structure. Over-modelling early creates false precision; under-modelling late creates site surprises.
The convention should state what each level must show and, equally important, what it must not imply. A simplified panel at concept stage must not be read as a confirmed construction detail.
| Stage | Model focus | Coordination question |
|---|---|---|
| Concept | Opening extent, parking zone, route intent | Does the layout allow straight, turning or stacking routes? |
| Developed design | Track line, panel array, clear floor line | Does the overhead route stay continuous and supported? |
| Coordination | Interfaces with structure, ceiling and services | Are clashes resolved before fabrication drawings? |
| Construction | Confirmed dimensions and support locations | Has the project-specific review been signed off? |
Coordinate Track, Stack and Panel Geometry Together
Review focus: level of detail convention.
The top track, the panel array and the parking position are one system. Modelling them separately without a shared origin or reference plane invites misalignment.
Because panels cross the opening without a floor track, the model should show a clear floor line along the partition route. This is a coordination statement, not a performance claim. It helps the team check that no floor hardware or threshold is assumed where none is intended.
Route Review: Straight, Turning and Stacking
Straight, turning and stacking routes should be reviewed from the layout. Each proposed movement path requires a continuous connected overhead route and project-specific support review. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings.
Parking and Stacking Zones
Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it. The model should reserve the parking zone as real space, not as a nominal annotation, so that adjacent services and finishes are coordinated around it.
Document the Evidence Boundary in the Model
Project review term: level of detail convention.
A federated model is not a performance certificate. The convention should include an evidence note stating which attributes are design intent and which require project-specific confirmation.
Any acoustic requirement must be confirmed against the specific project, assembly and test evidence available for that configuration.
Evidence note: finish options such as laminate, melamine, fabric, leather, glass and other approved surfaces describe appearance and surface selection. They do not, by themselves, confirm cleaning compatibility, structural capacity, acoustic performance or a application reference.
A Practical Coordination Checklist for Project Teams
Coordination scope: level of detail convention.
- Agree the element naming pattern and classification codes before modelling starts.
- Define what each level of detail must show, and what it must not imply.
- Model the top track, panel array and parking zone from a shared reference.
- Show the clear floor line along the partition route.
- Review straight, turning and stacking routes against the layout.
- Record which attributes are design intent and which need project confirmation.
- Confirm pass-door requirements and project documentation with the supplier.
- Schedule a federated review before fabrication or procurement stages.
Frequently Asked Questions
What is a movable partition BIM element naming level of detail convention?
It is a documented agreement that defines how movable partition elements are named, classified and detailed at each project stage so that federated models remain readable and coordinated across disciplines.
Should the model show a floor track for a top-hung movable partition?
No. EBUNGE movable partition panels are suspended from a top track and cross the opening without a continuous floor running track or floor hardware along the partition line. The model should show a clear floor line instead.
How detailed should the partition model be at concept stage?
Enough to test opening extent, parking zone and route intent.
Can the BIM model confirm acoustic performance?
No.
What finish information can be included in the model?
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. These describe surface selection and should not be read as evidence of cleaning compatibility or other performance.
Who should confirm support and dimensional requirements?
Support, acoustic and dimensional requirements are project-specific and should be confirmed by the responsible project team with the supplier before the model is treated as construction-ready.
Conclusion and Next Step
A clear naming and level-of-detail convention turns the movable partition from a coordination risk into a predictable part of the federated model. Define the taxonomy early, raise detail with each stage, coordinate track, stack and panel geometry from a shared reference, and state the evidence boundary openly. Named venues and room types are examples only; movable partitions can be considered wherever flexible spatial division, combination or reconfiguration is required.
To discuss pass-door requirements, project documentation and drawing coordination for your specific layout, contact the EBUNGE team. You can also review the movable wall product context and the project planning resources before your next federated coordination review.