Convert AVEVA to IFC in your application
3D InterOp is a CAD interoperability SDK that lets your software read AVEVA files and write IFC, writing the AVEVA facets as faceted geometry, since AVEVA stores triangles rather than solids.
Spatial does not offer an online converter or a desktop conversion app. 3D InterOp is a component that software vendors embed in their own products.
- Reads AVEVA · Writes IFC
- Triangle mesh → faceted model
- C++ / C# APIs
AVEVA to IFC at a glance
AVEVA stores triangles; IFC can hold facets alongside exact solids, so the mesh is written as faceted geometry.
| AVEVA (source) | IFC (target) | |
|---|---|---|
| Full name | AVEVA review model (E3D Design, PDMS) | Industry Foundation Classes |
| Standard / owner | AVEVA | buildingSMART, ISO 16739 |
| File extensions | .rvm or .rvt, with .att, .attr, .dat or .txt attribute files | .ifc, .ifczip |
| Geometry | Tessellated geometry | Exact B-Rep and tessellated geometry |
| Assemblies / structure | Yes: plant hierarchy | Yes: spatial and element hierarchy |
| 3D InterOp support | Read only | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from AVEVA to IFC.
-
Preserved
Product structureThe AVEVA product structure is written to IFC.
-
Changes
Faceted geometryAVEVA stores triangles, so the IFC file holds faceted bodies, not solids. 3D InterOp doesn’t rebuild exact B-Rep from a mesh.
Why software vendors add AVEVA to IFC conversion
Open BIM deliverables
Many projects specify IFC deliverables. Writing it lets your users meet those requirements from your software.
Coordination and clash detection
Coordination tools gather models from every discipline in IFC. Your users can contribute without a round trip through another tool.
Facility and asset data
Owners and operators often receive building data as IFC for asset management after handover.
Things to check before you ship
- Written IFC versions: IFC2x3 to IFC4x3 ADD2 (.ifc).
- Exact B-Rep needs IFC4 or later; IFC2x3 files only get tessellation.
- Supported AVEVA input: .rvm or .rvt files with their attribute files.
- The AVEVA .rvt extension isn’t a Revit file: don’t route it to the Revit reader.
- Validate a sample of translated files in the target system your users actually work with.
Working with Spatial was a real milestone for us: Thanks to the powerful 3DInterOp library, we were able to successfully bring our complex CAD-based solutions to the cloud while remaining flexible to meet individual customer requirements. For us, Spatial is not just a technology partner, but a true enabler of our product strategy.
Dr. Arno Michelis, Founder, Simus Systems
Read the Case StudyAbout the formats
-
Source format
What is an AVEVA RVM file?
RVM files are review models exported from AVEVA E3D Design and PDMS, the plant and marine design systems. They describe the plant geometry and hierarchy, with attributes in a companion file.
-
Target format
What is an IFC (.ifc) file?
IFC is the open, vendor-neutral standard for exchanging building information models, maintained by buildingSMART and published as ISO 16739. It carries building elements with their geometry, properties and relationships.
Frequently asked questions
No. AVEVA stores triangles, and 3D InterOp writes them to IFC as faceted geometry. It doesn’t rebuild exact B-Rep from a mesh.
Yes. 3D InterOp reads the AVEVA product structure and writes it to IFC.
Write IFC4 or later to keep exact B-Rep: IFC2x3 files only get tessellation. 3D InterOp writes IFC2x3 to IFC4x3 ADD2.
No. The AVEVA .rvt extension isn’t a Revit file: route it to the AVEVA reader, with its attribute files.
3D InterOp reads .rvm or .rvt files with their attribute files, as visualization data.
3D InterOp writes IFC2x3 to IFC4x3 ADD2 (.ifc).
No. 3D InterOp reads AVEVA but doesn’t write it. To send data back to AVEVA users, write a neutral format they can import.
-
Building software that needs to convert AVEVA to IFC?
3D InterOp is an SDK that lets your application read AVEVA and write IFC alongside 30+ CAD and BIM formats.