Convert AVEVA to DAE in your application
3D InterOp is a CAD interoperability SDK that lets your software read AVEVA files and write DAE, 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 COLLADA
- Triangle mesh → triangle mesh
- C++ / C# APIs
AVEVA to DAE 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) | COLLADA (target) | |
|---|---|---|
| Full name | AVEVA review model (E3D Design, PDMS) | COLLADA Digital Asset Exchange |
| Standard / owner | AVEVA | Khronos Group, ISO/PAS 17506 |
| File extensions | .rvm or .rvt, with .att, .attr, .dat or .txt attribute files | .dae, .zae |
| Geometry | Tessellated geometry | Triangle mesh |
| Assemblies / structure | Yes: plant hierarchy | Yes: scene 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 COLLADA.
-
Preserved
Mesh dataThe AVEVA facets are read and written to DAE without being re-tessellated.
Why software vendors add AVEVA to DAE conversion
Lightweight review
COLLADA 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 COLLADA file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, COLLADA files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- Written DAE versions: COLLADA 1.4.1 (.dae).
- The DAE writer is available through the UConnect interface only.
- 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 DAE (COLLADA) file?
COLLADA (.dae) is an XML-based open format from the Khronos Group for exchanging 3D scenes: meshes, materials, cameras and lights. It is common in visualization and AR/VR pipelines.
Frequently asked questions
No re-tessellation is needed. 3D InterOp reads the AVEVA facets as visualization data and writes them to DAE.
The DAE writer is available through the 3D InterOp UConnect interface.
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 COLLADA 1.4.1 (.dae).
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 DAE?
3D InterOp is an SDK that lets your application read AVEVA and write COLLADA alongside 30+ CAD and BIM formats.