We are trying to convert a model from OpenPlant to IFC with AECOsim.
This should be pretty straightforward, because AECOsim reads the OpenPlant's elements propierties.
We have tried a few options here and there but with no effect.
Here is the tank with the propierties from OpenPlant we want to export.
1 - IFC_WORKSET = 2
2 - Exported as IFC 4 Reference View. Results: (NO DATA)
3 - Creating a new family / part (PLUMBING - TANK) and Mapping (no warnings at exporting)
4 - Same result and no DATA
5 - Adding an istance data (Catalog type and istance - Storage tank) and mapping Storage tank as IfcTank
It exports the istance data but not the data from the OpenPlant's model.
What are we missing here? Why does not the data from the element export to the ifc element?
What do we need to configure or map or do to make this happen? If you need more information don't hesitate to ask.
i think you are missing a crucial step. All ifc objects have a predefined list of properties. these are grouped into ifc property sets or psets for short. you have done both the family and part , and datagroup mapping so far this only gives you the highlevel mapping. you need to map the individual tank properties to the individual ifc tanks properties or psets. for those properties that do not have a direct mapping you will have to create a custom pset definition and include that in the mapping settings.
I will ask if we have published a wiki on this and get back to you.
Bentley Systems, Manchester UK
Thank you for your response Brenden, looking forward to this wiki.
Meanwhile i'll try to solve it where you are pointing at.
Curious why you are using IFC and not i.Models?
we are trying to import it to navisworks, but almost all geometry is lost in the process (with the data too).
This is the configuration window:
The final result imported into Navisworks:
We have read lots of articles or wikis, but we do not get the desired result.
If you know an optimal way of doing it, please let me know.
Best regards, Fran
Are you refering to this option?
Because we would need to instance all elements (thousands) of the model and that is non viable.
Our main goal is to load the dgn model into Navisworks.
The DGN file crashes navisworks and the i.model does not load the geometry nor the data.