If a property turns red after you assign it to a parameter group, it doesn’t necessarily mean the value is missing from your model. In many cases, the property exists - but it is stored in a different property group than the one defined in your information requirements.
Why this happens
When you assign a property group (property set) to a requirement, Plannerly expects to find the property in that exact group during model validation.
For example, if your requirement expects:
- Fire Rating in DoorCommon
…but your IFC model contains:
- Fire Rating in IFC Parameters
Plannerly considers the expected property to be missing because it cannot find it in the specified group. As a result, the property is displayed in red.
Understanding validation colors
Plannerly uses different colors to indicate different validation results:
- Red – The expected property could not be found. This includes cases where the property exists but is located in the wrong property group.
- Orange – The property was found, but its value does not meet the validation criteria, or its unit of measurement is incorrect.
- Green – The property was found in the expected property group, its value meets the defined validation criteria, and its unit of measurement matches the expected unit.
When should you use property groups?
Property groups are especially useful when working with buildingSMART’s openBIM standards, such as Information Delivery Specifications (IDS), where property sets are part of the standard and are required for validation.
If your project is not based on an IFC or IDS workflow, property groups may not provide additional value and can make validation more restrictive.
Consider using tags or types instead
If your goal is simply to organize, filter, or manage your information requirements, you may prefer using Tags or Types instead of property groups.
Types
Types allow you to categorize requirements and quickly filter related properties.
Tags
Tags are fully customizable and a single requirement can have multiple tags. They are ideal for creating flexible filters and organizing information without affecting model validation.
How Plannerly validates properties
During model checking, Plannerly verifies several aspects of each property:
- The property exists.
- It is located in the expected property group (if one is defined).
- The property value satisfies the configured verification rule.
- The unit of measurement matches the expected unit.
Because the property group is part of the validation, placing a property in a different group causes Plannerly to treat it as missing, even if the property itself exists elsewhere in the model.
