I have a situation that I’m not sure if there is one good solution to it …
I attached some codes to model elements. Then I started adding new layers to those elements. Because the elements were single layer before adding the code, the code is attached to the “product” level of the element. And then when adding layers, the code should move to the one layer it is applicable to.
In this case it was a concrete floor, measurement of the code is in m3. Then I added some insulation and floor finishing. Now those are added to the volume of the product. Thus resulting in too large of a value. Luckily the error was caught in time for quotation, thanks to my colleague.
I believe that for most/all cases when there are multiple layers to a product, the code should be added to the individual layers and not the product/assembly. That is at least the case for codes relating to pricing.
(Unfortunately?) the choice was made in Qonic to treat all kinds of classifications/codification that is not the ifcClass the same. So both classification like SfB on ‘systems’ as well as codification for BoQ on ‘materials/components’. That means it isn’t automatically a logic workflow to push attached codes to the already-existing layer when new layers are added (in case of single-layer product). Might be a setting to the code library if it should default to ‘system’ (/product/assembly) or component (/layer/BuildingElementPart).