Convert AVEVA to 3DXML in your application
3D InterOp is a CAD interoperability SDK that lets your software read AVEVA files and write 3DXML, carrying the mesh data across without re-tessellating it.
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 3D XML
- Triangle mesh → triangle mesh
- C++ / C# APIs
AVEVA to 3DXML at a glance
Both formats store triangles, so the facets carry over without re-tessellation. The differences are in structure, appearance and metadata.
| AVEVA (source) | 3D XML (target) | |
|---|---|---|
| Full name | AVEVA review model (E3D Design, PDMS) | 3D XML |
| Standard / owner | AVEVA | Dassault Systèmes |
| File extensions | .rvm or .rvt, with .att, .attr, .dat or .txt attribute files | .3dxml |
| Geometry | Tessellated geometry | Tessellated geometry |
| Assemblies / structure | Yes: plant hierarchy | Yes |
| PMI | None | Graphical PMI |
| 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 3D XML.
-
Preserved
Mesh dataThe AVEVA facets are read and written to 3DXML without being re-tessellated.
-
Preserved
Product structureThe AVEVA product structure is written to 3DXML.
Why software vendors add AVEVA to 3DXML conversion
Lightweight review
3D XML carries tessellated geometry that opens much faster than the full CAD model, so design reviews and digital mockups stay responsive.
Sharing outside engineering
Marketing, training and sales teams rarely have CAD software. A 3D XML file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, 3D XML files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- Written 3DXML versions: 3D XML 4.3, as static tessellation.
- Only static tessellation is written, not XML 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.
- Test tessellation settings on your heaviest parts: finer meshes mean larger files.
- 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 a 3D XML (.3dxml) file?
3D XML is Dassault Systèmes’ lightweight XML-based format for sharing 3D product data. 3D InterOp reads and writes its tessellated representation, with product structure and graphical PMI.
Frequently asked questions
No re-tessellation is needed. 3D InterOp reads the AVEVA facets as visualization data and writes them to 3DXML.
Yes. 3D InterOp reads the AVEVA product structure and writes it to 3DXML.
3D InterOp writes 3D XML 4.3 with static tessellation. XML tessellation isn’t written.
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 3D XML 4.3, as static tessellation.
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 3DXML?
3D InterOp is an SDK that lets your application read AVEVA and write 3D XML alongside 30+ CAD and BIM formats.