Hi!
IN AECOsim, the objects have two internal ID:- AECOsim Guid- AECOsim Element IDWhen we export to IFC:- "AECOsim Guid" is converted in a kind of "IFC Guid"- "AECOsim Element ID" is joined in "Ifc Description" property with other values, and it disappears as a standalone property.Then, only "AECOsim Element ID" is the value that let us to follow the lifecycle of the objects. But it's difficult to control the lifecycle of the objects, if the unique ID disappears as a standalone property in the ifc export.Then, how to export to IFC the "AECOsim Element ID" in a comprensible, standalone and unique property?Are there any way to do it "automatically"?
Are were any way to know the algorithm transformation between "AECOsim Guid" and "IFC Guid"?
I attach an image to explin it.
Thanks a lot!
Xavier C.A.
EiPM
Hi Xavier,
1) The 'ABD-GUID' is compressed to an 'IFC-GUID' as per IFC specification:
The IFC specification uses an unique identifier for object instances that follows the universal unique identifier standard UUID with its implementation as a globally unique identifier GUID. The generated GUID is compressed for exchange purpose following a published compression function. The compressed GUID is called "IFC-GUID" here.
For further information, please see http://www.buildingsmart-tech.org/implementation/get-started/ifc-guid/ifc-guid-summary?searchterm=guid
The FZK Viewer shows both GUIDs, while Solibri only shows the 'IFC-GUID':
2) The ABD-Element ID is Bentley specific and of no use to receiving applications, but used for IfcElement description prefixed with the Type description and model name; see IFC file
#48=IFCWALLSTANDARDCASE('0_Tb$28vT8NA5hJjQv9lEi',#16,'Concrete-12','12" Concrete Wall :0, test GUID.dgn, Design Model:11890','Concrete-12',#54,#47,$);
So, to follow the lifecycle of an object, don't use the ABD-Element ID, but the IFC-GUID.
Regards,
Volker
Answer Verified By: EiPM_Xavi
Any update for this? According to my exploration, as long as AECOsim can save its Element ID in the IfcElement.Tag property, Solibri Model Checker will be able to pick it up from there to the BATID field as hown in the screenshot of the original post. It will be faster to find elements by Element ID compared to traversing the entire model and looking for GUID. Thanks.
bump...
If iModel 2.0 has a bridge app for IFC, it would be good to understand how Enhancement 616065: 'Users would like GUIDs assigned to elements on IFC export to be consistent for the lifespan of the elements' will be implemented.
Hi Huan,
As best I can tell, Enhancement 616065 as described above is resolved in ABD CONNECT Edition.