Revit Parameters

(in A-lab template)

In Revit, parameters are used to define and store information about elements in your project. There are two main types of parameters: Project Parameters and Shared Parameters.

Project parameters are specific to a single Revit project file. They are stored within the project file and can only be used within that project. Project parameters are useful for adding custom information to your project, such as project-specific details.

Shared parameters are parameter definitions that can be used in multiple Revit projects. They are stored in a (or multiple) separate shared parameter file and can be loaded into any Revit project. Shared parameters are useful for defining consistent information across multiple projects, such as A-lab's standardized parameter set-up.

Both Shared and Project Parameters can be included in schedules, but only Shared Parameters can be used to tag elements in your project. In general, it is recommended to use shared parameters whenever possible to streamline your workflow, enhance communication, and maintain consistency throughout your Revit projects.

To ensure consistency across projects, a standard set of shared parameters is automatically integrated into every new Revit project. If A-Lab parameters exist that correspond to Revit parameters, they always should override Revit parameters with the same purpose.

To streamline our workflow, we'll be using two Shared Parameter files. The first, managed by the X-lab, is available on the server U:\BIM-Revit\A-lab ContentManagement\X_LAB\ALAB_BIM_Shared Parameters.txt, and it's write-protected for security purposes. The second file is project-specific and should be placed in the corresponding project folder for the team to maintain.

If you need to change or switch the Shared Parameter file, simply navigate to the Manage tab, select Shared Parameters, and click Browse... to locate the desired file within the Edit Shared Parameters dialog box.

change / switch Shared Parameter file

Here you can find a description of the latest A-lab Shared Parameters included in the project template.

latest A-lab Shared Parameter file, group <BIM>

latest A-lab Shared Parameter file, group <20x>

We grouped the parameters to make them organized and easier to find:

• ALAB_BIM TITLEBLOCK Containing all parameters belonging exclusively to the titleblock.

• ALAB_BIM RAMME Containing all parameters belonging exclusively to the plan frame.

• ALAB_20x Containing all parameters belonging exclusively to building system 20x.

• ALAB_TOOLS Swing Containing all parameters belonging exclusively to A-lab Tools Swing
• ALAB_TOOLS SharedElevations Containing all parameters belonging exclusively to A-lab Tools SharedElevations
• ALAB_BIM Containing parameters from mixed building systems and categories.

Now, here are the parameters:

• ALAB_20x_Gulvlist (instance) This parameter describes the type of skirting board used in rooms. Parameter syntax: GU-T01 Required: from MMI350

• ALAB_20x_Gulvoverflate (instance) This parameter describes the type of floor covering used in rooms. Parameter syntax: GU-Bb01 Required: only in MMI300

• ALAB_20x_Himlingsoverflate (instance) This parameter describes the type of ceiling used in rooms. Parameter syntax: HI-M01

  Required: only in MMI300

• ALAB_20x_Kvalitetsnivå (instance) This parameter describes the equipment qualitiy of rooms: Parameter syntax: Enkel, God, Høy etc. Required: from MMI200

• ALAB_20x_Overflatebehandling (instance) This parameter describes the type of finishing used in rooms. Parameter syntax: OB-Ma01

  Required: only in MMI300

• ALAB_20x_Veggoverflate (instance) This parameter describes the type of walls covering used in rooms. Parameter syntax: GL-T01

  Required: only in MMI300

• ALAB_BIM_AcousticRating (type / instance) This parameter contains the soundproofing value of multiple building systems. It is used as a Type Parameter e.g. in predefined wall types, yet it can also be used as an Instance Parameter to assign a unique value to a particular element. Parameter syntax: xx dB Required: from MMI350

• ALAB_BIM_Beslag (type) This parameter describes the door fittings. It is used as a Type Parameter in predefined door types. Parameter syntax: xxx Required: from MMI300

• ALAB_BIM_Buildingstorey (instance) This parameter maintains a consistent connection between an element and the level it belongs to, regardless of the various methods Revit uses to assign a level to an element. This parameter is automatically populated through a routine in AnkerDB. Parameter syntax: U1, 01, 02 etc. Required: from MMI100

• ALAB_BIM_Buildingzone (instance) This parameter maintains a consistent connection between an element and a specific zone within a building or site. This parameter is automatically populated through a routine in AnkerDB , extending its usage to a range of additional data points (e.g. Acoustic Rating, Fire Rating, etc.). Parameter syntax: Bygg A, Bygg B, Bygg C etc. Required: from MMI100

• ALAB_BIM_DoorSwing (instance) This parameter identifies the swing side that a door or window opens into with A-lab Tools Swing, and stores the information to which room the swing is facing in a designated parameter. Parameter syntax: venstre, høyre Required: from MMI350
• ALAB_BIM_Dørautomatikk (instance) This parameter describes if a door is automatically closed. Parameter syntax: (boolean) Required: from MMI300

• ALAB_BIM_FireRating (type / instance) This parameter describes the fireproofing value of multiple building systems. It is used as a Type Parameter e.g. in predefined wall types, yet it can also be used as an Instance Parameter to assign a unique value to a particular element. Parameter syntax: E xx, EI xx, EIR xx etc. Required: from MMI350

• ALAB_BIM_G-Verdi (instance) This parameter describes the g-value of windows. Parameter syntax: 0.5 Required: from MMI350

• ALAB_BIM_GroupWorkset (instance) This parameter helps to easily assign grouped elements to the Bygningsdeltabel, without having to break or edit the group. This allows you to quickly assign these elements to a common Workset or select them using filters. Parameter syntax: 23x, 24x, 25x etc. Required: if applicable
• ALAB_BIM_IsExternal (type) This parameter describes the information about whether a building system is intended for the facade or inside the building. It is utilized as a Type Parameter e.g. in predefined wall types. Parameter syntax: (boolean) Required: from MMI200

• ALAB_BIM_Lambda-Verdi (instance) This parameter describes the Lambda-value of outer walls with doors and windows and of the roof. Parameter syntax: 0,7 W/mK Required: from MMI350

• ALAB_BIM_LoadBearing (type) This parameter describes the information about whether a building system is intended for structural / load bearing purpose. It is utilized as a Type Parameter e.g. in predefined wall types. Parameter syntax: (boolean) Required: from MMI200

• ALAB_BIM_LockedMark (instance) This parameter locks the room association of a door or window using A-lab Tools Swing, particularly when there's already been a delivery of door schedules or typical details, and you're only reviewing and modifying the door or window numbering for a select number of doors or windows. Parameter syntax: (yes / no) Required: from MMI350
• ALAB_BIM_LT-Verdi (instance) This parameter describes the LT-value of windows. Parameter syntax: 60% Required: from MMI350

• ALAB_BIM_Lysåpning (instance) This parameter describes the glazing opening of windows. Parameter syntax: 925x2140mm Required: from MMI300

• ALAB_BIM_MMI (instance) This parameter stores the MMI according to the project agreement, e.g. per building, per level, per zone, per building system, etc. Parameter syntax: MMIxxx Required: from MMI100
• ALAB_BIM_OriginalSwing (type) This parameter indicates the opening direction of a door or window, as stored in the according family. A-lab Tools Swing uses this information for room assignment. Parameter syntax: left / right Required: from MMI350
• ALAB_BIM_ReverseRoom (instance) This parameter in A-lab Tools Swing allows you to set whether the room assignment of the opening side or of the opposite room is written to the parameter ALAB_BIM_Romtilhørighet. This is useful, e.g. for shaft doors or escape routes. Parameter syntax: yes / no Required: from MMI350
• ALAB_BIM_Romtilhørighet (instance) This parameter is populated by A-lab Tools Swing with the room assignment of doors and windows. Parameter syntax: H.03025 Required: from MMI350
• ALAB_BIM_SharedBottomElevation (instance) This parameter is populated by A-lab Tools Shared Elevation with the bottom of a building element relative to Havnivå.

  Parameter syntax: 90210 Required: if applicable

• ALAB_BIM_SharedTopElevation (instance) This parameter is populated by A-lab Tools Shared Elevation with the top of a building element relative to Havnivå.

  Parameter syntax: 88210 Required: if applicable

• ALAB_BIM_Sparkeplate (instance) This parameter describes if a door has a kickboard or not. Parameter syntax: (boolean) Required: from MMI350

• ALAB_BIM_Spikerslag (type) This parameter describes if a wall is a stud wall or not. It is used as a Type Parameter in predefined wall types. Parameter syntax: (boolean) Required: from MMI350

• ALAB_BIM_Terskeltype (instance) This parameter describes the threshold type of a door. Parameter syntax: ID-T01 Required: from MMI350

• ALAB_BIM_U-Verdi (instance) This parameter describes the u-value of outer walls with doors and windows and of the roof. Parameter syntax: 0,7 W/m²K Required: from MMI350

• ALAB_BIM_Vernestatus This parameter indicates whether there is a (historic) preservation requirement. Parameter syntax: (boolean) Required: from MMI300

You can also find an Excel spreadsheet on the server that contains all the parameters, sortable by category, MMI, and usage:

U:\BIM-Revit\A-lab ContentManagement\X_LAB\ALAB_BIM_Parameters.xlsx

It may be necessary to add additional internal or project-specific parameters. A-lab has defined its own syntax for this.

All parameters for internal usage follow the same logic:

ALAB_[GROUP]_[NAME] where [GROUP] = BIM for unspecified parameters, for specified parameters use the three digit code from Bygningsdeltabel. [NAME] = Unambiguous parameter naming This could result in: ALAB_BIM_ColorCode (applied to multiple elements of a building) ALAB_23x_FacadeOrientation (applied to all facade elements of a building) ALAB_244_AccessControl (applied to doors inside a building)

All parameters for project specific usage follow the same logig:

ALAB_[CLIENT] or [PROJECT]_[NAME] where [CLIENT] = parameter that is required by a client [PROJECT] = parameter that is not required by a client, but project-specific [NAME] = Unambiguous parameter naming This could result in ALAB_BM_Kontrollområde (client 'Betonmast') ALAB_E1_Building (project 'Elvely E1') ALAB_V11_Zone (project 'Elvebygget V9-11')