Secrets of the IFC format title

The Secrets of the IFC Format part 3

Introduction

Here’s a quick reminder. In the previous article of the series –Secrets of the IFC format -, I introduced classes in the IFC schema. You could find out that the class is an attribute template. Thus, no matter which program the IFC file was exported from, its attributes will always be saved in the same format. You have also learned what relationships are and how attributes are inherited within the IFC schema family tree.

The objects’ attributes (Name, Type, Height, etc.) are defined by a “rigid” schema in the form of a template (previous post – graphic). Of course, it has its pros and cons. It is very convenient when exporting objects and their attributes to an IFC file. Great. But what if there is no attribute in the template of a given class that we would like to assign to a given object? The number and type of information we assign to the objects may vary depending on a project’s stage, the country, industry, etc. Since it is still hard to standardize all this information, the number of attributes assigned to classes in the IFC schema is reduced to the necessary minimum. And that does not mean we can do nothing about it. The IFC schema meets such requirements by Properties, which we can almost freely assign to objects. In this post, I am going to focus on this particular topic.

1 Attributes vs. Properties

  • Attributes (the number and the value type are part of the IFC object template – a graphic from the previous post). These attributes form an integral part of the schema. You cannot delete or modify them. Removing an attribute from the schema will simply ruin its structure, and it will be impossible to open the IFC file.

  • Properties, as opposed to attributes, give us the freedom to create. We decide how many and what type of properties we wish to create and assign to an object. They are not included in the schema, hence if they are modified or deleted, the structure of the schema is not damaged.

Many programs have built-in configurators that allow adding properties to objects. As a result, we can easily create our own property sets from information available in a given program or create completely new properties, so-called UDA (user defined attributes).

2 What are properties??

Let’s try to understand how IFC Properties are created and how to connect them to an object (class) so that after exporting IFC, they are visible in any IFC file viewer.

2.1 Creating Properties

Then let’s create a new property for the wall class (IfcWall) from scratch. May it be, for instance, a 20 mm thick plaster.

To make additional properties understandable for the software reading an IFC file, it is necessary to use… standard schematic templates. A little confusing? Or perhaps quite sensible.

As I have already mentioned, the IFC schema is like a family tree with many branches, mutual dependencies. It also has an individual IfcProperty template. IfcProperty is special as it is a separate family tree in the IFC ecosystem. In the previous article, you could read, that the superior template for all of them is the ancestor of the entire IFC genealogical tree – IfcRoot. Well, the Ifc Property template is independent of the Ifc Root. Have a look:

Ifc Property, Ifc schema
IfcProperty (source: https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/)

This template contains two attributes Name (i.e. name for our newly assigned property) and a description.

Ifc Property has two descendants (Ifc property graphic is divided into IfcSimpleProperty and IfcComplexProperty). 

IFCProperty tree
IfcProperty tree

Our example is extremely simple, so let’s focus on the Ifc Simple property template. It has no new attributes, yet has 6 branches (descendants).

  • Single: simple value. Text, number, true/false;
  • Enumerated: limits the selection of one value from a predefined list of possible values;
  • Bounded: allows to define a minimum and maximum value in one property, for example, tolerance;
  • Table: the entire table of values, for example, a size table for a valve;
  • Reference: link to another object;
  • List: many values on the list;

In our example, we are going to use IfcPropertySingleValue. 

The template has two attributes:

  • Nominal value
  • Unit

This is the property template that we will add to our wall object. 

IFC Attribute table
IfcPropertySingleValue attribute table

2.2 Adding properties to an object

We have a completed property template with attributes… and what’s next. You should combine this template with the object. We have to put the template into the main IFC schema family tree.

Here, a template can help us – IfcPropertyset, property set template.

IfcPropertySet
IfcPropertySet(source: https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/)

As you can see IfcPropertyset is already related to the most important IfcRoot template. Thus it has the attributes inherited from Ifcroot – Name and GUID number. However, the most important in this case is the attribute – “HasProperties”. This is the place where our independently created properties connect to the main schema tree.

IfcPropertySet attribute table
IfcPropertySet - Attribute table

2.3 Referring a property set to an object

The last step (I promise) involves assigning a set of properties to our wall.

Naturally, in this case, everything is planned, and it is possible due to relationships (IfcRelationships – see the previous article from the series).

With IfcRelDefines, it is possible to combine a set of properties with an object, in our example – with a wall.

First, we will summarize all the above information:

  1. The Ifc schema consists of templates and attributes defining each object (class).
  1. The attributes cannot be modified or deleted.
  2. There is an individual IfcProperty “tree” for creating your own unique object properties (classes).
  3. We create properties through the IfcProperty template.
  4. We combine the property set template IfcPropertySet with the main tree.
  5. We establish a set of properties with an object through the IfcRelDefines schema relations.

And… that’s it.  

You might get questions in your head. What is the point? Does it really have to be so complicated? 

 

By doing so, I just wanted to show, in simple terms, the mechanism of adding more information to the Objects.

3 ....and how does it look like in practice?

Using Tekla Structures software I will show you that this is not as complicated as it might seem above.

In Tekla Structures, I created User Defined Atribute (UDA) – an additional property for the wall object.

The IFC export option allows you to use the properties we have created.

The IFC file created in this way will then be opened in three different browsers:

Ifc properties, ifc model BimVision
IfcWall additional property in BIM Vision viewer
ifc model properties, ifcwall properties solibri
IfcWall additional property in Solibri viewer
ifc model properties, ifcwall properties trimble connect
IfcWall additional property in Trimble Connect viewer

As you can see, regardless of what IFC browser we view our wall in, an additional property of 20 mm thick plaster is shown along with other attributes.

Summary

If you are still wondering why you should add additional information to objects in the IFC model, read Marcin Pszczółka’s article “What is the best file format in BIM?” in which he shows that by assigning additional properties to objects he doesn’t have to wait for the IFC for infrastructure.

Model-based designs, which are increasingly popular, are based on the ability to assign all this information to an object that we would traditionally place in the drawing.

I’m curious if you also use your own property sets when exporting an IFC file or rely only on the basic information generated by a native program.

Did you like that post ? Share it with others !

We spend a lot of time and effort creating all of our articles and guides. It would be great if you could take a moment to share this post !

Share:

Share on facebook
Share on twitter
Share on linkedin

Comments: