Tech Talks

@stephen-king said in Revit IFC export settings:

Going off your response it seems that it will differ from project to project and isnt as simple as using one of the predefined setups given in Revit.

Well, that’s more or less depending on your used project template and how standardized your projects are. On the long shot it definitely makes sense to set up a streamlined workflow with resulting IFCs which are similiarly structured as you will do yourself a huge favor when you e.g. do not have to reconfigure Solibri Classifications/Rulesets/… all the time.

COBie is a good example - when you have the exact same COBie properties in all your projects you should indeed be able to use export settings which can be applied to all the projects. You can then proceed to Solibri and validate the IFC there before performing the take off or creating the COBie sheets.

However, take note that the first time you do it you will most likely need adopt the classifications according to your Property Mapping in Solibri to get it to work! Of course this also depends again on your used Revit template, the IFC Export Settings and its Property Mapping. I am not sure if there is even a standard COBie Property Mapping table available, but if I am pretty sure you would have to configure it according to your file anyhow.

How about creating a report, which has a bunch of issues, which have all required values in those lists? I believe you need several issues, since all of those are such, that only one value is allowed.

Store this report as a BCF file and open it to every SMC where you want to have those values, and they are available in all new issues as well.

Thanks @jsn for the clarification. Very interesting!

Hi @Noushed,

I test to create new issues, without to add description (no comments), and also they works.

I attach a video.
Kind regards,
Xavier Coll
EiPM
210107_Test_02.zip

@lasse-lindqvist hereby error log

error.log

@marchi
I Agree… Warnings are most of the time helpful

@jsn That is our usal workflow as well. but in this instance the software uses WCS as an origin.
This is t0 the best of my knowlege how this software handles things as im not working directly with the software

Thanks a lot for your fast answer, @matti-kannala
Kind regards,
Xavier Coll

@Joel,

Hello! This issue is known, and a fix is available in the beta version. Please test and let us know how it feels!

Kind regards,
Toni on behalf of the Solibri team

@Xavier said in Detect/list the elements INSIDE a space:

But when the elements and Spaces are in different IFC files, it’s not simple to solve it. Maybe it’s possible using a Clash rule, and list the results. Is there other more direct workaround?

Use nearest space relation or nearest space field:

In Information Takeoff you can use the both In Classification you can use only the field (hopefully we get this soon)

To find out more about nearest space: Search topics with “nearest space”

@Jim-persson said in Classification and Nearest Space:

Prefect i missed that you can make ITO editable complety. that solves this issue

Editable works only for classification and color column.

Tip: the color column can be set to take the colors from a classification column.

@lasse-lindqvist

Thanks for your answer, but this way I only get UNKNOWN as Type of the Related, but the Slab is definitely FLOOR in Solibri interface and SLAB in API -> component.getComponentType()

May you have one more hint for me, thanx a lot so far

Reinhard

Collection<Component> CT = component.getRelated(Relation.of(Relation.Type.DEFINES_BY_TYPE, Relation.Direction.BACKWARD)); if (CT.iterator().hasNext()==true) { String CTYPE = CT.iterator().next().getComponentType().toString(); }

@hkringsKUBUS said in Connection to BIMcollab not working:

Mystery solved: The server was temporarily unavailable. This has now been fixed.

Just tried to connect the new Beta and it seems not to be possible. Might this be server related as well?

0d7072fc-2b49-4407-8108-8c76a333fd15-image.png

Resulting in …

b193305f-1414-44e6-bfc2-bf181800671c-image.png

EDIT: Mystery solved - seems to be related to our IT restrictions and running the Beta with Admin rights.

Thanks for these hints! After testing some alternative model layouts (removing partial models), we found that it’s not an issue of graphics (or triangle count at all). It has been an issue of structural (hierarchical) depth of models. There was model of an road & infrastructure design platform, which exports storey in storey in storey and so on. Somehow Solibri gets confused by this modelling strategy (I’m too). Once we removed that model, it started to work fine again.

@dserdiukov wrote: https://society.solibri.com/topic/929/solibri-4k