Our standard requires us to classify every object in the OpenBridge model according to an approved format. We are achieving this via Item Types which works well. However, when I upload the OpenBridge model to iTwin all of these item types are not visible. I'm not sure if they're lost or just not accessible. I then tried exporting to IFC from iTwin and this also did not contain the item types. I tried using the Prostructures IFC exporter in OpenBridge and this also did not carry the item types across into IFC.
Looking at this page here it looks like this is the solution: export item type to ifc - OpenBuildings | AECOsim | Speedikon | Forum - OpenBuildings | AECOsim | Speedikon - Bentley Communities
However, it appears that OpenBridge doesn't have these options.
If there isn't a solution to this at the moment, is there another form of export we can use that will carry Item Types with it?
Thanks for your help.
Unfortunately this is now confirmed as a defect. A defect has been logged, and will be investigated and fixed in a future release.
Hi Sri, has this been resolved for 2022 Release 1? This issue also results in no Item Types being visible in any other PowerPlatform product like ORD and Microstation.
Regards,
Mark
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
Looks like this only seems to work on newly created data - is there a way to "nudge" any pre-existing data to apply the Item Types to the native solids to be seen in Microstation and iTwin using this new version?
Please try to make a small change to force a bridge update, like changing the skew of a support line by 1 degree and then change it back to the original value. This should force the update of the item types for an already existing file.
Hi Sri, I have tested the new version of OBM (2022 R1), as you mentioned before Itemtypes do show up in Microstation and OpenBuildings, however, if I do .ifc export from OpenBuildings, I can't see it in .ifc file. How did you do the .ifc export to make it visible in BIMVision?
Jaimin Patel
I haven;t tried it myself but I am assuming that data added by OBM should be explicitly mapped (perhaps as generic elements, beams, columns, piles etc.) prior to the export to IFC process in OpenBuildings.
It will be most convenient if OBM can directly export IFC.