This article describes what targets are and how you can use them in rules. The article covers the following topics:
Introduction to Targets
Targets are the model components you want a rule to check. Different rule types require different model components as input variables. A rule type may require one or several model components as input for the rule. Targets help to define precisely these individual inputs.
Targets are created as separate instances, so they are not rule-specific but can be (re)used in different rules to specify which components are to be covered. All targets are gathered in a library and can be managed on the Targets tab. You can add several targets to your rules and use the same targets in multiple rules.
For each target, you can specify the criteria it needs to match. In this way, you can create separate targets to represent, for example:
- All walls
- External walls
- Load-bearing walls
On the Targets tab, you can see a list of targets you can use in the rules. You can sort the targets by target name or owner (person who has created the target). You can also see the date when the target was created:
To view the details of a target, click the target name on the list:
On the list of targets, there are several predefined targets created by Solibri. These can be duplicated, so it’s easy to create your targets based on the existing ones. You can also create new targets from scratch if you wish.
You can only edit and delete the targets you have created yourself (=you are the owner).
Targets and the IFC Schema Version
Targets are described independently of the model content or authoring tool used to be always applicable and valid. To ensure this, each target specifies an IFC Entitiy, which specifies the starting point for subsequent target criteria. As the IFC schemas have evolved along the consecutive versions, partly different entities are supported - therefore, the corresponding IFC schema version (for example IFC2x3) must also be selected.
Some IFC Entities are compatible with several IFC Schemas, but not all. For example, IFC4 includes some IFC Entities, such as IfcChimney, which do not exists in IFC2x3. This means that your target may be compatible with other IFC Schema versions. However, you'll be notified if your target is incompatible with other versions.
When you create a new target, the default IFC Schema version selected is IFC 2x3. You can change the version if you need to use IFC Entities or attributes and properties that are not available in the currently selected IFC schema.
The rule where the target is used must support the same IFC schema as the target.
If needed, you can duplicate the target and create a separate version to cover the incompatible IFC schema.