Checking unwanted and unnecessary Properties
-
Hi everyone,
Solibri is perfect in checking information that is requested, but what about doing a check of unwanted information inside the IFC structure? In many cases, not only I receive IFCs with the necessary Properties, but also unnecessary properties. The latter should simply not be there because it is bloating the file and nobody uses that.
For example, at a certain stage of a project, the FireRating should not be exchanged. Hence, I would like to create an Issue, to remove this property.
I have tried to set up a Rule that could find this “garbage”, but was not able.
Does anyone know how to set up such a case?
Is it at all possible in Solibri to do such a rule?Thank you in advance
-
Try #203 Required Property Sets https://help.solibri.com/hc/en-us/articles/1500004738242-203-Required-Property-Sets. This rule should work if unnessesary properties belongs to property set, not to BIM Data tab
-
Hi @karolinamad
I have tried this rule. Sadly, it checks only the required sets and properties contained in the rule. Even in the explanation page, it states: “The Required Property Sets rule checks that the model contains the required property sets and properties.”I want to find the opposite. I want to find out which properties are there which are not required. Or is there an “inverse” option in the rule 203?
If I defined the rule 203 with just one property, it should deliver me all the other properties as an error. But what solibri rather does, it checks the components against this defined property. Therefore, if my components are fulfilling the rule, then it gives me an OK. It doesn’t care about the rest
-
@agroni This is possible with IDS. You can set a property prohibited.
-
@Pasi-Paasiala
Can you explain where this “prohibited” is contained?
To my knowledge, the IDS has only three operators: IsDefined, OneOf, Is. I did not find a possibility to prohibit or exclude something.
It is also not logical at this level to prohibit something, because you don’t know what you should prohibit. How do I know what type of “garbage” do I receive in the Model?I think the IDS should rather have a function:
Only the defined Properties and PropertySets are allowed in the IFC Schema.
In this case, everything else will be reported as an error. -
-
thanks @Pasi-Paasiala for the link.
As I stated previously, the “Prohibit” rule needs information in the IDS of what should be checked for prohibition.
As the example in GitHub:
The Wall should not contain Attribute RED. Hence, when RED is present in the model, the IDS will give an error.
We would need to prohibit then RED, GREEN, BLUE, etc…and the list is simply not predictable.As far as I understand the concept of IDS, we are going to be able to check ONLY the necessary information, which has been written down. The other irregularities outside this scope and are simply not going to be reported.
Let me explain you differently
Let’s assume you ordered a Pizza Margherita with Mozzarella, Tomato Sauce and Basilica leave. Upon delivery of your order, you realize that you pizza has also Salami, and Mushrooms in addition to the ordered ingredients. According to IDS, the check has passed, because your pizza has Mozzarella, Tomato Sause and Basilicy leave according to your requirements. You could prohibit in IDS the Mushrooms and Salami, but you would need to include also Onions, Rucola, Parmigiano, Prosciutto or in the worst case even Pineapple. The list is simply huge! I hope you understand where I am going with this -
@agroni If the property sets you accept follow some naming pattern, you could have a regular expression that matches all other property set names and prohibit all properties in those with a regular expression matching any string.
Copyright © 2025 Solibri Inc. | Powered by NodeBB