Convert AVEVA to XCGM in your application
3D InterOp is a CAD interoperability SDK that lets your software read AVEVA files and write XCGM, 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 XCGM
- Triangle mesh → faceted B-Rep
- C++ / C# APIs
AVEVA to XCGM at a glance
AVEVA stores triangles; XCGM is an exact-geometry format. The mesh is written as faceted geometry: 3D InterOp doesn’t rebuild smooth surfaces from triangles.
| AVEVA (source) | XCGM (target) | |
|---|---|---|
| Full name | AVEVA review model (E3D Design, PDMS) | CGM native file |
| Standard / owner | AVEVA | Dassault Systèmes / Spatial (CGM Modeler) |
| File extensions | .rvm or .rvt, with .att, .attr, .dat or .txt attribute files | .xcgm |
| Geometry | Tessellated geometry | Exact B-Rep |
| Assemblies / structure | Yes: plant hierarchy | Yes |
| PMI | None | Semantic (read) |
| 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 XCGM.
-
Changes
Faceted geometryAVEVA stores triangles, so the XCGM file holds faceted bodies, not solids. 3D InterOp doesn’t rebuild exact B-Rep from a mesh.
Why software vendors add AVEVA to XCGM conversion
Hand models to kernel-based applications
Many CAD, CAM and CAE applications are built on the XCGM kernel. Writing XCGM gives them exact geometry they can load without another translation step.
Downstream modeling and analysis
An exact XCGM B-Rep can still be edited, meshed or machined by downstream tools, which a tessellated export would not allow.
Exchange within one ecosystem
Partners whose tools share the XCGM kernel often prefer to exchange XCGM files directly.
Things to check before you ship
- Written XCGM versions: R2012 to 2025 1.0.
- PMI and miscellaneous data aren’t written to XCGM.
- 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 XCGM (.xcgm) file?
XCGM is the native file format of the CGM geometric kernel, used by CGM Modeler and Dassault Systèmes applications. It stores exact B-Rep geometry.
Frequently asked questions
No. AVEVA stores triangles, and 3D InterOp writes them to XCGM as faceted geometry. It doesn’t rebuild exact B-Rep from a mesh.
No. PMI and miscellaneous data aren’t written to XCGM.
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 R2012 to 2025 1.0.
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 XCGM?
3D InterOp is an SDK that lets your application read AVEVA and write XCGM alongside 30+ CAD and BIM formats.