Convert IFC models into native AVEVA E3D models
Reuse IFC geometry, classifications, property sets, and metadata in AVEVA E3D. ModelSwap converts civil and structural content into native E3D objects.
How can an IFC model become native E3D data?
An IFC model carries far more than a visual representation: it contains 3D geometry, object classes, property sets, and relationships. E3D teams still need this information rebuilt as native engineering objects to edit the model and use their usual workflows.
The usual approaches
Direct IFC import
A direct IFC import brings the geometry and available attributes into E3D. The elements remain generic, however: they do not gain the E3D logic needed for editing, deliverables, specifications, or synchronization.
Manual remodelling
Teams can recreate the IFC content manually in E3D and re-enter the relevant data. This repeats information already present in the IFC model and must be repeated whenever the source changes.
ModelSwap: a structured conversion workflow
ModelSwap reads IFC geometry, object classes, and property sets to rebuild native E3D objects. The result follows your modelling standards, specifications, and data rules.
How ModelSwap works
ModelSwap maps IFC geometry, classifications, and property sets to native E3D objects.
Conversion disciplines and outcomes in AVEVA E3D
Civil
Expected outcomeIFC walls, slabs, and civil elements rebuilt as intelligent E3D objects such as STWALL, GWALL, and FLOOR.
Structural
Expected outcomeIFC structural steel rebuilt as native GENSEC members.
| Discipline | Expected outcome |
|---|---|
Civil | IFC walls, slabs, and civil elements rebuilt as intelligent E3D objects such as STWALL, GWALL, and FLOOR. |
Structural | IFC structural steel rebuilt as native GENSEC members. |