Hi All,
I imported an OpenRoads Design model to AECOsim SS6 to add instance data and part definitions to the 3D model.
In the workflow first I converted all the OpenRoad elements to smart solid and than added part definitions. After I added the instance data to the elements.
But when I open the property window of any element, the quantification attributs are showing zeros.
Is there a way to make it work? How can we make AECOsim to calculate the quantities of the smart solid elemnets?
On the project we use AECOsim SS6 and OpenRoads Design Connect version.
Thanks,
Andras
vid
Hi Andras,
Quantification in ORD is getting quite advanced now and you also have Asset Manager to bulk apply Item Types as well - Do you really need to go through the exercise of adding Part Definitions in OBD?
There is also IFC Mesh export in there now and works quite well. As Dominic stated, there is no Road IFC schema yet, but it exports with a generic BuildingElementProxy one for now - hopefully Item Type property export will also be included in IFC exports soon.
One question I do have - how are you converting ORD Meshes to solids, we've never been able to get to work.
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023.1 | ProjectWise CE 3.4
Aren't the quantities there in OpenRoads? They should be reportable. I am not familiar with ORD but I think that the terrain elements are meshes... which should still be able report volumes without conversion to SmartSolids.
Maybe you should convert to SmarSolids in ORD, check that the quantities are there before importing/copying through in OBD.
BTW
IFC- for Roads does not exist at the moment. Planned for IFC5. You can not just use the schema for buildings for roads. It looks like your client's BEP is a bit sloppily written aka aspirational ?
You may want to contact your Bentley account manager. Ref 277305
the client needs IFC file, that is why I put the model in OBD and add instance data.
I tried it in OBD but it didn't work to add instance data to smart solid, the quantities attributes are still zeros and don't recognize the thickness of elements.
Andras,
if you have Openroads, why don't you extract the quantities there instead of converting to OBD?