Applying Consistent Level Naming
Different physical levels must use different names. Names and Z values must remain consistent across all disciplines.
Check in the IFC Viewer
Always check levels, elements and properties in an IFC viewer to ensure accuracy and alignment across disciplines before submission.
IFC Viewers and Tools
Use a suitable IFC viewer to review the exported model and its spatial structure.
View IFC Viewers & 3rd Party Tools ↗| Discipline | Storey Name | Z Value (m) | Purpose |
|---|---|---|---|
| Architectural | 1st Storey | 3.000 | Architectural floor level |
| MEP | 1st Storey | 3.000 | Architectural floor level |
| Structural | 1st Storey_SFL | 2.950 | Structural slab underside level |
Structural levels may use a suffix (e.g., _SFL)
when the structural floor level is at a different
elevation from the architectural level.
Illustrative comparison of level names and Z values across three discipline models.
✓
Good Practices
- Agree on naming conventions and level Z values at project start.
- Use consistent level names across all disciplines.
- Use suffixes such as _SFL only when levels are at different elevations.
- Coordinate and verify levels using the same reference model.
×
Common Issues
- Using different names for the same physical level.
- Using different Z values for the same level.
- Missing suffixes for structural levels at different elevations.
- Changing level names or Z values without coordination.
◎
Key Takeaway
Use the same names and Z values for the same physical level across all disciplines.
Use different names (e.g., _SFL) only when the level is at a different elevation.
| Storey | Valid Example | Invalid Example |
|---|---|---|
| Above-ground floors |
|
|
| Mezzanine floor for above-ground floors |
|
|
| Split floor for multi-storey car park building |
|
|
| Below-ground floors |
|
|
| Attic floors |
|
|
| Roof floors |
|
|
| Differentiate storeys between blocks/datums |
|
|