Level, Floor, Storey ISO 19650-2, SIA 0270, ISO 4157-1, IFC

In the complex world of Building Information Modeling (BIM), maintaining consistency and clarity in every aspect of a project is crucial. One essential element that often goes overlooked is the naming of #Levels (#Floor, #Storey) within #Revit #BIM projects. Proper level naming not only facilitates better project coordination but also ensures data integrity and efficiency. In this article, we'll explore why standardized level naming is so important, outline effective guidelines, and provide practical tips for implementation.ntroduction

Introduction

Proper level naming in Revit BIM projects is more than just a clerical task - it's foundational to the success of any BIM endeavor. Inconsistent level naming can lead to confusion, miscommunication, and errors that ripple through the entire project lifecycle. By adopting standardized level naming conventions, teams can enhance coordination, improve efficiency, and ensure the accuracy of data.

Understanding Level

Levels in Revit are essential tools used to define vertical heights or stories within a building (Figure 1). They are finite horizontal planes that act as references for level-hosted elements, such as roofs, floors, and ceilings. Just as grids divide a building volume into vertical planes, levels divide it into horizontal planes. This fundamental organization helps in managing and referencing various elements throughout the BIM process. Help | About Levels | Autodesk

Maximize image

Edit image

Delete image

Figure 1: Building division using Levels and Grid to horizontal and vertical planes

In analytical models (Figure 2, right), the position of levels is as important as the position of grids. Levels represent horizontal planes that serve as critical reference points for the structural analysis of the building. Therefore, when setting up the structural frame (Figure 2, left), it is crucial to organize grids and levels based on the structural analytical models (Figure 2, right), ideally passing through the center of structural elements such as floors, walls, and columns (Figure 3). This alignment simplifies the coordination between disciplines and ensures that the analytical models accurately reflect the physical structure of the building. The architectural grids and levels should align with the positions of the structural analytical model levels and grids to ensure consistency and accuracy across different models.

Minimize image

Edit image

Delete image

Figure 2: Physical (left) and analytical (right) models grids and levels position

However, this approach can conflict with IFC standards (Figure 7), which typically place levels at the top of structural floors. To resolve this, the final decision on the placement of levels should be made by the project team, ensuring that the chosen method aligns with both the structural and architectural needs of the project, as well as any relevant standards.

Maximize image

Edit image

Delete image

Figure 3: Physical and analytical models location

For new projects, it is relatively easy to set levels and grids in the center of elements. However, for existing buildings modeled from 3D point cloud scans, this becomes a complicated task because you cannot easily identify the structural frame core layer of floors and walls. In such cases, levels are often placed on top of floor finishes and to the side of wall finishes. This should be taken into consideration when combining existing buildings with new buildings to ensure consistency and accuracy across the project.

Minimize image

Edit image

Delete image

Figure 4: Physical and 3D point cloud scan model levels and grid location

Common Issues Caused by Inconsistent Level Naming

Inconsistent level naming can result in a range of issues, including:

• Difficulty in locating specific levels or views

• Misalignment in interdisciplinary collaboration

• Increased time spent on correcting errors and miscommunications

• Challenges in maintaining data integrity and project documentation

Standardization According to Industry Standards

SIA 0270

The Swiss standard SIA 0270 provides guidelines for level naming and building story identification (Figure 5) to ensure clarity and consistency. Following this standard helps in maintaining uniformity across Swiss projects and aligns with national requirements.

Minimize image

Edit image

Delete image

Figure 5: Overview of floor heights

SIA-Shop Produkt - 'D 0270 / 2018 D - Anwendung der BIM-Methode - Leitfaden zur Verbesserung der Zusammenarbeit (Dokumentationen => Allgemeine Grundlagen)'

ISO 4157-1

This part of ISO 4157 specifies requirements for designation systems and a designation code for buildings, including spaces (Figure 6), building elements and components.

Maximize image

Edit image

Delete image

Figure 6: Numbering of storeys

ISO 4157-1:1998 - Construction drawings — Designation systems — Part 1: Buildings and parts of buildings

ISO 19650-2

This document specifies requirements for information management, in the form of a management process, within the context of the delivery phase of assets and the exchanges of information within it, using building information modelling.

This document can be applied to all types of assets and by all types and sizes of organizations, regardless of the chosen procurement strategy. In this article I use ISO 19650-2 British annex.

ISO 19650-2:2018 - Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling — Part 2: Delivery phase of the assets

IFC (Industry Foundation Classes)

IFC is a standardized data model used to describe building and construction industry data. Ensuring level names are compliant with IFC parameters enhances interoperability and data sharing between different software platforms.

A #storey is (if specified) associated to a building (Figure 7). A storey may span over several connected storeys. Therefore storey complex provides for a collection of storeys included in a building. A storey can also be decomposed in (horizontal) parts, where each part defines a partial storey.

In split level houses, a storey is split into two or more partial storeys, each with a different elevation. It can be handled by defining a storey, which includes two or more partial storeys with the individual elevations.

The IfcBuildingStorey is used to build the spatial structure of a building (that serves as the primary project breakdown and is required to be hierarchical). The spatial structure elements are linked together by using the objectified relationship IfcRelAggregates.

In #Revit, each #BuildingStory is represented by a #Level with the "Building Story" parameter value set to true. Typically, #structural levels are marked as "Building Story", while architectural floor finish levels are not. To make a clear difference between the Revit Name parameter in the Levels category and the level name used in IFC, it is recommended to add two additional instance parameters to the Levels category: IfcName and IfcDescription.

General IFC File Organization:

Project

--Site

-- -- Building

-- -- -- Building Storey

-- -- -- -- Element Category

-- -- -- -- -- Element

-- -- -- -- -- <...>

-- -- -- Building Storey

-- -- -- Building Storey

-- -- -- <...>

5.4.3.10 IfcBuildingStorey - IFC4.3.2.0 Documentation (buildingsmart.org)

Minimize image

Edit image

Delete image

Figure 7: Example showing the use of base quantities for building storeys

Importance of Standardized Level Naming

Benefits for Project Coordination and Efficiency

Standardized level naming brings numerous benefits to BIM projects:

1. Improved Coordination - clear and consistent level names ensure that all team members are on the same page, facilitating smoother communication and collaboration.

2. Enhanced Efficiency - when levels are named according to a set standard, it becomes easier to locate and manage views, reducing the time spent on searching and correcting errors.

3. Data Integrity - standardized naming helps maintain the accuracy and reliability of project data, which is crucial for both current and future use.

Guidelines for Effective Level Naming

Core Principles and Rules

To establish an effective level naming convention, consider the following guidelines:

1. Include Essential Information - Level names should contain key details such as discipline, zone, elevation, and floor number. This ensures that anyone reviewing the project can quickly understand the context and purpose of each level.

2. Maintain Consistency - Use a uniform structure for all level names to ensure clarity and avoid confusion. Consistency helps team members locate and reference levels efficiently across the entire project.

3. Use Simple and Clear Labels - Avoid overly complex or ambiguous names that could lead to misunderstandings. Clear and straightforward naming helps prevent errors and facilitates easier communication among team members.

4. Optimize for Efficiency - consider keyboard and mouse usage to streamline data management and access. By incorporating all necessary information directly into the level name, you minimize the need for additional clicks and mouse movements, saving time and reducing the likelihood of mistakes.

5. Standardize Elevation Precision - Ensure that all elevation values end in zero to maintain precision.

Minimize image

Edit image

Delete image

Figure 8: Level naming convention

Examples of Level Naming Conventions

Minimize image

Edit image

Delete image

Table 1: Level naming convention

Minimize image

Edit image

Delete image

Table 2: Level naming convention extended

Correct Naming Convention

• AA-A-00A-+00.000 (Figure 8, Table 1 and 2) - This name includes the building volume (zone) (AA), role or discipline (A), specific level identifier (00A), and elevation (altitude) (+00.000).

Incorrect Naming Convention

• Level1_Main_Floor - This name is too vague and does not provide enough information for effective coordination.

Detailed Explanation of Guidelines

Volume (Zone)

Represent the building in the model (e.g., AA for building A). Project specific codes for divisions should be detailed in the project space statement. The project specific codes should not conflict with the standard codes given in (Table 3).

Minimize image

Edit image

Delete image

Table 3: Volume (according to ISO 19650-2 Standard)

Buildings belonging to the same project shall be with a principal and an individual designation, for example BUILDING A, BUILDING B, etc. (Figure 8).

The designation for a part of a building shall consist of a principal designation, completed with a systematic letter or numeric designation, for example BUILDING 2 PART 1, BUILDING 2 PART 2, BUILDING 2 PART 3, etc. (Figure 9)

Minimize image

Edit image

Delete image

Figure 9: Project division to Buildings and Building Parts. Example of designation of buildings and parts of buildings according to ISO 4157-1

If project buildings division to parts is not enough for efficient working with Revit models so it is recommended to divide parts to sub-parts. In such case additional digit will be used to represent division of building part (Figure 10).

Minimize image

Edit image

Delete image

Figure 10: Building part division to additional parts for smaller models

Role (Discipline)

Indicate the discipline (e.g., A for architecture, S for structure, ISO 19650-2 British annex). This coding is eficient becouse you need only 1 symbol (Table 4).

Minimize image

Edit image

Delete image

Table 4: Role (according to ISO 19650-2 Standard)

Level Identifier

Use a numeric or alphanumeric code to specify the level (Table 5).

Where a container documents a single building level (floor) or location, the code for that level should be used. Where a container documents multiple levels, a distinct code should be used. The standard codes for the spatial divisions of the project should be used wherever possible.

Project-specific codes for divisions should be detailed in the project space statement. The project-specific codes should not conflict with the standard codes.

Minimize image

Edit image

Delete image

Table 5: Level names in file naming (according to to ISO 19650-2 and SIA 0270 Standard)

A storey is a space between two consecutive floor planes or the space between a floor plane and a roof, bounded by physical limits (floors, ceiling, and walls), including its exterior walls and other relevant parts of the building (Figure 11). Each storey shall be consecutively from the bottom to the top, starting with 1 at the lowest level usable for any purpose (Figure 11, a). Zero Shall designate the space that is situated immediately below the lowest level usable for any purpose according to ISO 4157-1

Minimize image

Edit image

Delete image

Figure 11: Building storeys numbering according to: a) ISO 4157-1; b) SIA 0270

The numbering applies not only to the usable space of a given storey but also to the physical limits bounding this space, for example, the load-bearing floor and ceilings above the storey, the walls and the ceilings in the storey, etc. The upper face level of the load-bearing building part indicates the transition level from one storey to the next storey (Figure 12 and 13).

Minimize image

Edit image

Delete image

Figure 12: Building transition between storeys according to ISO 4157-1

Minimize image

Edit image

Delete image

Figure 13: Building transition to IFC

When there are differences inside a building, for example, mezzanine, offset level, landing, ramp, etc., every necessary indication shall be given in order to avoid errors. These indications shall be in the form of levels or listed abbreviations and placed beside the numbering of the storey concerned. Staircases shall have the same numbering as the storey in which they are situated, whether or not they have half-landings.

The designation for the part of a storey, when the documentation is divided into several drawings, shall consist of the designation of the storey, completed by a systematic numeric or letter designation (Figure 14).

Minimize image

Edit image

Delete image

Figure 14: Building transition between storeys when there are differences in inside a building according to ISO 4157-1

Elevation (Altitude)

Clearly state the elevation with the required precision (e.g., +00.000). Elevations should be presented with three digits after the decimal point (e.g., +-0.000 m). This uniformity helps in sorting and organizing levels effectively. For example, if the maximum elevation is +99.990 m, use two digits for meters: +00.100, -00.100, +25.350, -25.350. For elevations up to +999.990 m, use three digits: +000.100, -000.100, +025.350, -025.350, +205.350, -205.350.

Implementation Tips

Practical Advice for BIM Environment

Implementing these guidelines in a BIM environment requires a strategic approach:

1. Utilize Revit Features - leverage Revit tools to automate the application of naming conventions. For instance, use the Project Browser to organize views by level and discipline.

2. Team Training - conduct regular training sessions to ensure all team members understand and adhere to the naming standards.

3. Documentation - create a comprehensive documentation of the naming conventions and make it accessible to all project participants.

Tools and Features in Revit

Revit offers several tools that can assist in maintaining consistent level naming:

• View Templates - Use view templates to standardize the appearance and naming of views.

• Project Parameters - Define project parameters that can be used to tag levels with the required information.

• Level Identity Data Options - In Revit, each level has options for "Structural" and "Building Story". The "Building Story" parameter should be set to true for all levels that represent actual building stories. Typically, structural levels are marked as "Building Story", while architectural levels may not be. This distinction helps in organizing and identifying levels correctly in both Revit and IFC files.

Ensuring Adherence to Standards

Consistency can be maintained by:

• Regular Audits - conduct periodic audits to check for compliance with naming standards.

• Feedback Mechanism - establish a feedback mechanism where team members can report issues or suggest improvements.

Conclusion

Standardized level naming is a simple yet powerful practice that can significantly enhance the efficiency, coordination, and data integrity of Revit BIM projects. By following the outlined guidelines and implementing the practical tips, BIM professionals can ensure smoother project execution and long-term benefits. We encourage all BIM practitioners to adopt these best practices and share their experiences to further refine and improve the process.

Incorporating standardized level naming into your Revit BIM projects is a step towards greater clarity, efficiency, and success. Embrace these guidelines and witness the positive impact on your project outcomes.

Examples of Naming Conventions

Below you can take a look at some examples of Revit level naming. One side is sorted by elevation and another by name. Vote for the version you like the most in the comments. Write your Cons and Pros for the selected version. Sugest your level name version.

Minimize image

Edit image

Delete image

Figure 15: Level naming example 01

Minimize image

Edit image

Delete image

Figure 16: Level naming example 02

Minimize image

Edit image

Delete image

Figure 17: Level naming example 03

Minimize image

Edit image

Delete image

Figure 18: Level naming example 04

Minimize image

Edit image

Delete image

Figure 19: Level naming example 05

Minimize image

Edit image

Delete image

Figure 20: Level naming example 06

Minimize image

Edit image

Delete image

Figure 21: Level naming example 07

Minimize image

Edit image

Delete image

Figure 22: Level naming example 08

Minimize image

Edit image

Delete image

Figure 23: Level naming example 09

Minimize image

Edit image

Delete image

Figure 24: Level naming example 10

Minimize image

Edit image

Delete image

Figure 25: Level naming example 11

Minimize image

Edit image

Delete image

Figure 26: Level naming example 12

Minimize image

Edit image

Delete image

Figure 27: Level naming example 13

Minimize image

Edit image

Delete image

Figure 28: Level naming example 14

Minimize image

Edit image

Delete image

Figure 29: Level naming example 15

Minimize image

Edit image

Delete image

Figure 30: Level naming example 16

Minimize image

Edit image

Delete image

Figure 31: Level naming example 17

Minimize image

Edit image

Delete image

Figure 32: Level naming example 18

Minimize image

Edit image

Delete image

Figure 33: Level naming example 19

Minimize image

Edit image

Delete image

Figure 34: Level naming example 20

Minimize image

Edit image

Delete image

Figure 35: Level naming example 21

Minimize image

Edit image

Delete image

Figure 36: Level naming example 22

Minimize image

Edit image

Delete image

Figure 37: Level naming example 23

Minimize image

Edit image

Delete image

Figure 38: Level naming example 24

Minimize image

Edit image

Delete image

Figure 39: Level naming example 24