Important
-
Rules are available in Solibri Advanced and Premium, with full editing access.
-
Rules can be viewed in read-only mode in Solibri Starter and Essential if they are already present in the SMC File.
This article describes how the Property Values Must Be from Agreed List rule works and how you can configure the rule.
The correct use of textual property values, such as construction types, is important. For example, quantity takeoff and thermal analysis programs rely heavily on this information for mapping components to their internal, more precise representation. With the Property Values Must Be from Agreed List rule, you can validate that the values of specific properties of specific components have been defined based on your own, project-based list.
This article covers the following topics:
Related articles:
Important
Running this rule with the default values doesn't give useful results; this rule has to be configured before use.
Some construction data requires you to specify that property has a restricted set of values. With this rule, you can check that the specified components have values derived from an agreed list. The list of agreed property values typically varies in national standards, building codes, and also in different types of projects. Therefore, this rule has to be configured for each project separately. The configured rule can then be used for checking any number of models in the same project.
This rule you checks if the components you have listed in the Components to Check filter table with that specific property, matches with the allowed value. The rule checks the listed values row by row, until it finds the matching row. These values can be imported into the filter using external excel worksheet. These values must be textual, string type values. This rule will return issues if the value is not included in the list, is incorrectly written or is completely missing.
In the rule parameters, you can define the components you wish to check and the allowed property values.
Components to Check:
Select the components to check.
-
You can define components with specific properties to be checked. You can also set all components to be checked and define them more specifically in in the Allowed Property Values table below.
Allowed Property Values:
The values can be listed either manually or imported using an Excel spreadsheet. For more information on using external data in rule parameters, see here.
-
Component: Add a row to the table and select the component type.
-
Property: Specify the property value you want to check.
-
Allowed Value: Type the value which is allowed for the selected property.
Tip
If the types resemble each other, you can use wild card characters * and ?.
Tip
For this rule, we have an example spreadsheet which you can fill in. You can find it in the Examples folder or download it at the end of this article).
Case Sensitiveness:
-
If checked, the property values in the rule make a distinction between lower and uppercase letters. For example, if you have specified that one of the allowed construction type patterns for walls is EW*, and a wall has construction type ew1, the rule creates an issue only if the Case Sensitiveness option is checked.
The rule returns issues in the following cases:
-
Property value is missing
-
Property value has been incorrectly written
-
Properties have values that does not match with the list
-
If case sensitiveness is activated: upper or lower case format for the text doesn't match the requirements
Results:
The rule creates two types of categories for issues:
-
Unknown <Property> values: If the model contains components with property values which do not match those listed, an issue is created for each distinct value.
-
No value: If components of the selected type don't have the selected property value, an issue is created. All components with same type are grouped into separate issues.
Reported Data:
The Property Values Must Be from Agreed List rule has a report, which contains a table with all Component, Property, and Value combinations and the number of components matching them. You can export the table to Excel for further analysis.
When rule #9 is used as the parent rule, the output components can be any components. When rule #9 is used as the sub-rule, the input components can be a any components. You can read more about gatekeeper rules here.
The example rules in Solibri include the following use cases:
-
System Names Must Be from Agreed List: This rule checks that only property values that have been agreed upon are used in the model.
-
Wall Construction Types Must Be From Agreed List: This rule checks that only construction types that have been agreed upon are used in the model.