Convert ASAT to CATProduct in your application
3D InterOp is a CAD interoperability SDK that lets your software read ASAT files and write CATProduct, with exact B-Rep geometry carried across and nothing tessellated.
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 ACIS assembly · Writes CATProduct
- Exact geometry → exact geometry
- C++ / C# APIs
ASAT to CATProduct at a glance
Both formats store exact geometry, so the model stays exact. The differences are in the product data each one can carry.
| ACIS assembly (source) | CATProduct (target) | |
|---|---|---|
| Full name | ACIS assembly, text (ASAT) and binary (ASAB) | CATIA V5 Product (assembly) |
| Standard / owner | Spatial (3D ACIS Modeler) | Dassault Systèmes |
| File extensions | .asat, .asab | .CATProduct |
| Geometry | Exact B-Rep | Exact B-Rep (in the referenced parts) |
| Assemblies / structure | Yes | Yes |
| PMI | Assembly-level PMI written as attributes | Semantic and graphical |
| 3D InterOp support | Read and write | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from ACIS assembly to CATProduct.
-
Preserved
Exact geometrySolids and surfaces stay exact B-Rep. The model is never reduced to a triangle mesh.
-
Preserved
Product structureThe ASAT product structure is written to CATProduct.
Why software vendors add ASAT to CATProduct conversion
Deliver in your customer’s CAD format
Aerospace and automotive OEMs often require supplier data in CATProduct. Writing it lets your users meet that requirement directly from your application.
Exact geometry, ready to edit
CATProduct keeps exact B-Rep geometry, so the receiving engineer can measure, modify or machine the model in CATIA.
No neutral-format round trip
Writing CATProduct directly avoids an extra STEP or IGES step, and the loss each extra translation can add.
Things to check before you ship
- Written CATProduct versions: CATIA V5 R15 to V5-6 R2026.
- A CATProduct written by 3D InterOp can’t reference files in other formats.
- Supported ASAT input: ACIS R1 to 2026 1.0.
- 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 ASAT (.asat) file?
ASAT and ASAB are the assembly versions of the ACIS save file, in text and binary form. They store the product structure of models built on Spatial’s 3D ACIS Modeler kernel.
-
Target format
What is a CATProduct (.CATProduct) file?
A CATProduct file is a CATIA V5 assembly. It defines the product structure and positions, and references the CATPart files that hold the geometry.
Frequently asked questions
Yes. Both formats store exact B-Rep geometry, so the model is translated without being tessellated into triangles.
Yes. 3D InterOp reads the ASAT product structure and writes it to CATProduct.
No. A CATProduct written by 3D InterOp can’t reference files in other formats.
3D InterOp reads ACIS R1 to 2026 1.0.
3D InterOp writes CATIA V5 R15 to V5-6 R2026.
Yes. 3D InterOp reads and writes both formats, so CATProduct to ASAT is supported too.
-
Building software that needs to convert ASAT to CATProduct?
3D InterOp is an SDK that lets your application read ACIS assembly and write CATProduct alongside 30+ CAD and BIM formats.