Create property sets for IFC export
You can create property sets from template attributes and user-defined attributes, define properties for the attributes, and bind the Tekla Structures property sets to IFC entities for IFC export. You can save the property sets in property set configuration files.
You can use the default property sets, and you do not need to create any custom property sets if the default property sets work for you. You can also modify the default property sets. In addition, you can import buildingSMART property sets.
When Tekla Structures exports an IFC file, it uses the configuration file you selected in the Property sets list to export property sets with the exported IFC entities. The list of configuration files includes predefined files located in your environment folders and files stored in the \AdditionalPsets folder under the current folder.
The Property set definitions dialog box allows you to add and modify the property sets needed in the IFC export. The property set configuration files that you create, will be visible in both IFC2x3 export and IFC4 export.
We recommend that you define property sets only in the Property set definitions dialog box instead of modifying the file itself to ensure that the XML configuration files are valid.
(1) The name of the selected property set configuration file. In the list, you can see all the available configuration files stored in your environment folders, and select the desired file. The file is loaded automatically after selection.
Use the Save button to save the changes in the configuration file after you have added or modified the property sets. You can also give a new name for the configuration file and save it. New and modified configuration files are saved in the \AdditionalPsets folder under the current model folder. You can also read configuration files from the following folders:
Use the button to clear the contents of the displayed configuration file and create a new configuration file.
(2) To show in the list only the property sets and properties that you have selected using the Include check box, select Show only included.
(3) Property sets in the current configuration file. You can drag property sets up or down in the list.
(4) Search for a specific property set. The list of property sets might be very long, and the search could be very useful when you want to find and select a specific property set.
(5) Show only the property sets for the selected IFC entities.
(6) Show only the property sets for the selected IFC versions.
(7) To export all property sets and all properties in the list, select the Include check box on the title row for the property set or properties section. To export only the needed property sets and properties for different export purposes, select the check box next to a specific property set or property.
(8) Filters allowing you to further limit for which objects to export the property set. For example, specify a filter to further limit which IfcBeam objects to export the property set for, like for steel beams only.
(9) Command buttons for working with property sets:
Add buildingSMART property sets. The property sets beginning with Pset_ or Qto_ are buildingSMART property sets. The buildingSMART property sets are protected, and you cannot change the IFC entities that they are exported with, or edit the names of the properties they contain. However, you can edit the properties in the buildingSMART property sets, and select to include or exclude them.
Add a property set.
Edit the selected property set.
Delete the selected property set.
Duplicate the selected property set. You can then modify the property set so that the properties are the same but the filtering criteria are different, for example.
(10) Properties in the selected property set. You can drag properties up or down in the list.
(11) To enlarge the property set section or the property section, drag the dialog box divider up or down.
(12) Command buttons for working with properties:
Add a property in the selected property set.
Edit the selected property.
Delete the selected property from the selected property set.
Create a custom IFC property set configuration file
Add property sets
Add properties in a property set
The buildingSMART property sets are protected, and you cannot add properties in those. Property sets with names beginning with Pset_ or Qto_ are buildingSMART property sets. However, you can modify the properties included in buildingSMART property sets.
Add a buildingSMART property set
You can add buildingSMART property sets to property set configuration files.
Delete a property set
- In the Property set definitions dialog box, a custom property set configuration file.
- Select a property set from the property set list.
- Click the Delete selected property sets.
- To save the changes in property set configuration file, click Save.
Delete properties from a property set
The buildingSMART property sets (beginning with prefixes Pset_ or Qto_) are protected, and you cannot delete properties from those. However, you can exclude properties included in buildingSMART property sets, see section "Include or exclude property sets or properties" above.
- Open a property set configuration file in the Property set definitions dialog box.
- In the property set list, select a property set from which you want to delete a property.
- Select a property from the property list.
- Click the Delete selected property.
Duplicate a property set
When you want have a new property set that is very similar to an existing property set, you can duplicate the existing property set. You can then modify the property set so that the properties are the same but the filtering criteria is different, for example.
You cannot duplicate a buildingSMART property set.
Include or exclude property sets or properties
You can also exclude buildingSMART property sets and properties.
Property set configuration file contents
A property set configuration file contains the structure of the property sets, and the data definitions for the properties inside the property sets.
When configuring property sets for IFC export in XML format, two files are needed:
-
IfcPropertySetConfigurations.xsd is a schema file that describes the structure of the XML file and is used for validation of the XML file. This file is read when the software is started. There is only one schema file in your environment. You do not need to touch this file.
-
The XML file <configuration_file_name>.xml is the actual property set configuration file.
The modified configuration files are saved in the \AdditionalPSets folder under the model, and they are also read from the system, project, and firm folders.
- The property set XML configuration file
contains the following definitions:
- Template attribute or UDA name. Template attributes are read from contentattributes_global.lst and the user-defined attributes from the environment database.
- Data type, such as String, Integer, Float, Timestamp, Boolean, Logical, or planeanglemeasure.
- Unit type, such as length, area, volume, or mass.
- Unit value scaling of unitless UDA values. Conversion factor is added so that unitless values can be converted to correspond to the global units used in the IFC files. Area and volume units need these factors.
- Possibility to use default values.
- Possibility to ignore the set to export if template attribute or UDA does not have a value.
- Below is an example of the contents of a property set configuration XML
file.
<PropertySet referenceId="assemblies" isIgnored="false"> <Name>Tekla Assembly</Name> <Description>Assembly Properties</Description> <Properties> <Property xsi:type="PropertySingleValueType" optional="true" isIgnored="false"> <Name>Assembly/Cast unit Mark</Name> <PropertyValue xsi:type="StringValueType" stringType="IfcLabel"> <GetValue xsi:type="TemplateVariableType"> <TemplateName>ASSEMBLY_POS</TemplateName> </GetValue> </PropertyValue> </Property> <Property xsi:type="PropertySingleValueType" optional="true" isIgnored="false"> <Name>Assembly/Cast unit position code</Name> <PropertyValue xsi:type="StringValueType" stringType="IfcLabel"> <GetValue xsi:type="TemplateVariableType"> <TemplateName>ASSEMBLY_POSITION_CODE</TemplateName> </GetValue> </PropertyValue> </Property> <Property xsi:type="PropertySingleValueType" optional="true" isIgnored="false"> <Name>Assembly/Cast unit top elevation</Name> <PropertyValue xsi:type="StringValueType" stringType="IfcLabel"> <GetValue xsi:type="TemplateVariableType"> <TemplateName>ASSEMBLY_TOP_LEVEL</TemplateName> </GetValue> </PropertyValue> </Property> <Property xsi:type="PropertySingleValueType" optional="true" isIgnored="false"> <Name>Assembly/Cast unit bottom elevation</Name> <PropertyValue xsi:type="StringValueType" stringType="IfcLabel"> <GetValue xsi:type="TemplateVariableType"> <TemplateName>ASSEMBLY_BOTTOM_LEVEL</TemplateName> </GetValue> </PropertyValue> </Property>
- The configuration file also contains
the rules for binding the property sets to IFC entities:
- Binding to IFC entity type hierarchy including support for not only building elements but also for bolts, reinforcing bars, and assemblies.
- You have the possibility to use
limiting rules, such as Equal, NotEqual, LessThan, GreaterThan,
LessThanOrEqual, and GreaterThanOrEqual for numbers, and Equal and NotEqual
for texts.
If you want to add any limiting rules, you need to modify your custom property set configuration file using a suitable text editor.
- There can be any number of binding
rules for any property set, but only one property set definition for each
referenceId
. - You can bind different property sets to different IFC entity types. For example, a plate may have a different property set than a beam.
<PropertySetBind referenceId="assemblies"> <Rules> <Include entityType="IfcElementAssembly" subtypes="true" /> </Rules> </PropertySetBind>
- If no value is found for a property in the export, the export does not write the property set at all. To avoid this, add optional=true for that property in the property set.