This rule checks that given textual properties of components have values that have been agreed upon. The list of agreed property values typically varies from project to project, so this rule must be configured for each project. The configured rule can then be used for checking any number of models from the same project.
This rule catches the following cases:
Property value is missing
Property value has been misspelled
Properties have values that have not been agreed upon are used in the model
The correct use of textual property values, such as, construction types is important. For example, quantity take-off and thermal analysis programs rely heavily on this information for mapping components to their internal, more precise representation.
Running this rule with the default values does not give useful results; this rule has to be configured before use.
The rule parameters are:
Components to Check:
The Filter Parameter table allows you to select your components more precisely to get more specific results. The selected disciplines in the previous discipline parameter have been converted in a row in the Filter Parameter table as shown in the screenshot.
Allowed Property Values:
The table has three columns: Component, Property, and Allowed Value. In the first column, you select the Component Type you want to check (Wall, Slab, Roof, etc.). In the second column, you specify the property value you want to check. In the third column, you need to type one of the acceptable property values in the project. You can use wildcard characters if the types resemble each other. You can also read values to this table from Excel.
Set this check box selected, if the property values if the rule should make a distinction between lower- and upper-case letters. For example, you have specified that one of the allowed construction type patterns for walls is “EW*”, and a wall has construction type “ew1”, you will get an issue only when this option is checked.
Analysing the results:
This rule creates two type of categories for issues, if needed:
Unknown values: If the model contains components whose property values do not match those listed, an issue is created for each distinct value.
No value: This issue is created, when the model contains components of the selected type that don't have the selected property value. All same type components are grouped into issue of their own.
The rule reports all Component, Property, and Value combinations and the number of components matching them.
The rule does not have any tools.