Convert AVEVA E3D models into native Autodesk Revit models
Bring AVEVA E3D engineering data into Revit. ModelSwap targets the native Revit families used by your project.
→
How can an E3D model become a native Revit model?
A visual exchange is not enough when Revit teams need editable, project-ready model data. They need native elements that follow the project family strategy.
The usual approaches
IFC export and generic primitives
An IFC import displays the geometry and retains some properties. The elements remain generic: they do not become native Revit families that teams can edit, document, and coordinate within the project.
Manual remodelling
Manual remodelling recreates the elements in the project's Revit families. It takes significant effort and must be repeated whenever the E3D model changes.
ModelSwap: a structured conversion workflow
ModelSwap converts E3D geometry and data into native Revit elements. Each element is mapped to the families and standards already defined in your project.
How ModelSwap works
ModelSwap maps source data to native Revit objects through reusable conversion rules.
Conversion disciplines and outcomes in Revit
Civil
Expected outcomeNative, editable Revit walls, slabs, and civil elements mapped to project families.
Structural
Expected outcomeNative, editable Revit structural elements mapped to project families.
Piping
Expected outcomeNative, editable Revit piping elements mapped to project families.
| Discipline | Expected outcome |
|---|---|
Civil | Native, editable Revit walls, slabs, and civil elements mapped to project families. |
Structural | Native, editable Revit structural elements mapped to project families. |
Piping | Native, editable Revit piping elements mapped to project families. |