General Discussion

Hi, This is a known bug and is logged to be fixed. The COBie project has to be the first project opened once Solibri is started otherwise this happens. Simply close the project (save if required), shutdown Solibri and then restart Solibri opening the same project, load your COBie settings and the calculate button should now be available.

@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.

Edit: Integration seems to work again. Not sure why.

Hi Mathieu, The Identification rule has a check box for identifying where this occurs
Check the option and the supply the component that it needs to cross i.e. a BWIC or Fire Seal using the filter / filter with classifications.

image.png

We have a update coming soon to this rule which will allow you to check for different scenarios.
image.png

230 works like a charm. Thanks for helping out!

Were you ever able to resolve the issue? A client of ours has the same problem and we’re not sure whats causing it. Now we have a ton of duplicates in our Database. Did the problem go away by itself and do you know at what Version it stopped?

What I remember from our models is that this only happens if the shortname was indeed taken beforehand.
So the bug is that Solibri isn’t checking if the shortname has been changed, it just keeps throwing out the message regardless of any change.

@Matti-Kannala

Thank you very much for providing some definitions.

I am still getting inconsistencies in the Elevation outputs in Solibri in the Location tab.

Are you able to help with the following?

I am simply reviewing a file with IfcSlab elements at 12ft. storey heights in order to understand the Solibri Elevation properties. There is a basement level slab and ground, first and second floor level slabs, then a roof slab. The lowest slab is defined as an IfcSlab_BASESLAB and the highest level slab is an IfcSlab_ROOF element. All the intermediate floors are IfcSlab_FLOOR elements. The slabs are all 12" thick. The origin is set to the underside of the ground floor slab although I have also experimented with it at the top of the ground floor slab but this seems to generate greater inconsistencies.

On upper floors, Solibri seems to take the IfcBuildingStorey Elevation as being to the underside of the IfcSlab; for a basement floor (IfcSlab_BASESLAB) and ground floor (IfcSlab_FLOOR), Solibri is reading the IfcBuilding Storey Elevation as the top of slab. Is this correct? Should there be this difference? The top level IfcBuildingStorey seems to run from the underside of the IfcSlab_FLOOR to the top side of the IfcSlab_ROOF. Is that correct? Is there a preferred elevation for the model origin to be set so that Solibri returns accurate IfcBuildingStorey elevation data?

Lastly, is there any Solibri documentation that explains how all these elevation properties fit together?

This is exactly what the resources are designed for. Please make sure that you are using the UK resources, set your components in the COBie set up area so that all other classifications only try to classify these components.

(1) The ITO collects data from a Classification (2) (but is renamed Category).
(3) The Classification is one of the ones from the resources called COBie Type - Category - Uniclass 2015
(4) The classification allows you to map the locations for the codes which it then automatically ensures that these are valid values.
(5) These classified components are then passed to the ITO and then automatically into the sheet.

image.png

You can change the location of where the classification searches for the values by editing the classification and changing the headers.

image.png

Use the Export sheet to ensure the values do not get corrupted when the locations are changed. The second column references a classification value where as the third column uses a property set. If you change these to different data locations i.e. a classification to a propertyset etc then the values in the that field will all be reverted to * values. Hence exporting the sheet first, change the locations and then you can clear the sheet and re-import from the exported version to keep all the values with the new headers.

If you log into the Solution Center you can change from product to Training and Documentation. Here you will find the COBie reference guide that will help you understand the workflow.

I see that you have all walls and all floors in your filters. How many walls and floors are in your project? Although all walls can be set for the filters it real design was for compartmentation walls and floors. We would have to have a look at the files in question. Please can you log a support issue related to this and we will investigate further.

Not only the description, but also other parameters can be predefined at rule level.
https://society.solibri.com/topic/2455/rule-level-predefined-issue-details-issue-presets?_=1718287384797

Is there any way to change the name of results?

I’m also interesting in this possibilitie

Hi @Max-Niras,

Before that I also had the same problem as you took a lot of time to do it and often repeated it in each project, this is my way:

Read Clash reports from Solibri and load data into the Revit design model. Can double click into cell status and it will change to “Done,” so can easily see which clashes are fixed and save the info for the next time. Can also filter by Responsibility or Status. When click on a row, it shows the clash location in the model, making it easy to fix the error, search, and save a lot of time.
Does anyone have any ideas to further solve this problem?

98251c30-b2e4-437e-9986-e00635c5615d-image.png