Classification

About Classifications

Classifications define how elements of this specification are represented in the models.

To add and edit classifications, open a specification and you will find the card “Classifications”. There you can add Classifying Properties, Revit Mappings, and IFC Mappings.

Conditions vs. Requirements

There are two kinds of classification in LastBIM:

1. Conditions (DE: Prüfbedingungen) define whether a specification is applied to an element. If all conditions are met, the requirements of this specification will be applied to the element during checks and the attribution. This corresponds to the IDS applicability.

2. Requirements (DE: Anforderungen) will be checked for elements that are already classified as this specification via the conditions. This corresponds to the IDS requirements.

We will explore this further for the different classification types: Classifying properties, IFC mappings, and Revit mappings.

Classifying Properties

Choose “Classifying Properties” if you want to add a property with a given value as a Condition for this specification.

Having a classifying property means that the specification is only applied to an element in the model if it has a matching value for the classifying property.

For example: You use a property “Cost group” to identify elements. In the case of a load-bearing external wall (KG331), you can define the rule Cost group Equals 331 to apply the specification to those elements that have the property “Cost group” with the value “331”.

You can add multiple properties to classify the specification.

Revit Mappings

With Revit mappings you can assign specifications to Revit categories.

When adding a Revit mapping, you can decide whether it should be used as a Condition or a Requirement :

• Condition:
  When attributing, the specification can only be applied to the element when it has the given Revit category. When checking the model in Revit, the element will only be checked for the requirements of the specification if its Revit category matches the specification.

• Requirement:

  The elements are not identified as a given specification by the Revit category. But for elements that are classified by other Conditions it can be used to check if the correct Revit category was used for modeling.

Example: You add the Revit category “Walls” to a specification…

IFC Mappings

With IFC mappings, you can assign specifications to IFC entities and Predefined Types.

Manual vs. Automatic

You only have to define the IFC mapping for one IFC version. The others will be set automatically, as long as they are set to Automatic and the selected IFC mapping exists there.

By setting all to Manual, you could define a different IFC mapping for each IFC version if you want to.

Condition vs. Requirement

When adding an IFC mapping you can decide whether this should be used as a Condition or a Requirement :

• Condition:
  When checking the model, the element will only be checked for the requirements of the specification when its IFC entity and predefined type match the specification.

  When attributing an IFC file, the specification can only be applied to the element when it has the given IFC entity and predefined type. In authoring softwares the plugin sets the IFC mapping for the element after selecting the specification.

• Requirement:

  The elements are not identified as a given specification by the IFC entity and predefined type. But for elements that are classified by other Conditions it can be used to check if the elements were exported with the correct IFC entity and predefined type.

Example: Our specification is called “Load-bearing Wall”. Add an IFC mapping for version 4.3.2, with the IFC class “IfcWall” and the predefined type “SOLIDWALL”. The mappings for the other versions are automatically set.

• By setting the mapping as Condition, every IfcWall with Predefined Type “SOLIDWALL” will be checked for the requirements of our “Load-bearing “Wall”.

• By setting the mapping as Requirement, every element that is matched with our Load-bearing Wall by other Conditions, will be checked if it is properly modelled as IfcWall SOLIDWALL.

Combinations

You can always combine classifying properties, Revit mappings and IFC mappings.

Example:

• You use the IFC entity “IfcWall” as a Condition to classify walls, and additionally use the classifying “LoadBearing” property to differentiate between load-bearing and non-load-bearing walls.