Convert AVEVA to STP in your application
3D InterOp is a CAD interoperability SDK that lets your software read AVEVA files and write STP, 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 STEP
- Triangle mesh → faceted B-Rep
- C++ / C# APIs
AVEVA to STP at a glance
AVEVA stores triangles; STEP is an exact-geometry format. The mesh is written as faceted geometry: 3D InterOp doesn’t rebuild smooth surfaces from triangles.
| AVEVA (source) | STEP (target) | |
|---|---|---|
| Full name | AVEVA review model (E3D Design, PDMS) | Standard for the Exchange of Product model data |
| Standard / owner | AVEVA | ISO 10303 — AP203, AP214, AP242 |
| File extensions | .rvm or .rvt, with .att, .attr, .dat or .txt attribute files | .stp, .step |
| Geometry | Tessellated geometry | Exact B-Rep |
| Assemblies / structure | Yes: plant hierarchy | Yes |
| PMI | None | Graphical and semantic (AP242) |
| 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 STEP.
-
Preserved
Product structureThe AVEVA product structure is written to STP.
-
Changes
Faceted geometryAVEVA stores triangles, so the STP file holds faceted bodies, not solids. 3D InterOp doesn’t rebuild exact B-Rep from a mesh.
Why software vendors add AVEVA to STP conversion
Supplier and OEM exchange
STEP is the ISO standard most supply chains specify for exchanging 3D models. Writing it lets your users send data to partners on any CAD system.
Model-based definition
STEP AP242 can carry semantic PMI next to exact geometry, so your users can share models together with their manufacturing data.
Long-term archiving
As an ISO standard independent of any CAD vendor, STEP is widely used to archive product data.
Things to check before you ship
- Written STP versions: AP203, AP214 or AP242 (.stp, .step or .stpx).
- 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 a STEP (.stp) file?
STEP is the ISO 10303 standard for exchanging 3D product data between CAD systems. Its application protocols range from exact geometry (AP203, AP214) to full model-based definition with PMI (AP242).
Frequently asked questions
No. AVEVA stores triangles, and 3D InterOp writes them to STP 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 STP.
The STEP writer supports AP203, AP214 and AP242, with AP214 as the default. Your application sets the version at export; semantic PMI is written to AP242 only.
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.
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 STP?
3D InterOp is an SDK that lets your application read AVEVA and write STEP alongside 30+ CAD and BIM formats.