ACIS Import-Export

On this page

Keep work moving when a partner sends ACIS

A customer sends a SAT file, while your application works with OCCT geometry. ACIS Import-Export connects those formats so users can review parts, run CAD operations, and prepare files for another system.

Use it in supplier-file processing, CAD editing tools, and conversion services that need ACIS reading and writing.

How it works

Choose a SAT or SAB file and load its shapes into your application. Apply geometry checks and any required repairs, then let users review or edit the model. To send a result back, choose a supported ACIS output version. The same model can also pass to a separate STEP or mesh writer.

Keep geometry, names, and colors together

Translate geometry and topology between ACIS and OCCT. Add document support when names and colors matter to selection, display, or reporting.

Configurable shape healing helps prepare incoming geometry. Set repair and approximation tolerances for the accuracy your application needs.

Support exchange in both directions

For SAT or SAB to STEP, combine ACIS import with an OCCT STEP writer. For STEP to ACIS, use STEP import followed by ACIS export.

ACIS writing supports output through version 7. Share the versions your partners use so we can confirm a compatible reading and writing route.

Handle files from different CAD releases

Partners may send SAT or SAB files from different CAD releases. Reader and writer version support determines which files can pass through the service and which ACIS version it can return.

A batch conversion service can apply consistent import, repair, and export settings. Files that need attention can be sent for review before delivery. This helps teams manage repeated supplier exchanges while keeping geometry quality and required part information in view.

Keep supplier exchange from delaying a project

A subcontractor may work in an ACIS-based system while your design team uses another CAD tool. Asking for a new export at every handoff adds waiting time, especially when several suppliers contribute parts. An application with ACIS reading and writing can provide a shared exchange step for those deliveries.

For example, a project team could review an incoming SAT model, check its geometry, and prepare a STEP copy for internal work. When a partner needs an ACIS result, the service can use an agreed output version within the writer’s supported range. Your application can retain the source file, selected settings, and review outcome with the job.

Purchasing and engineering teams then have a clear way to identify files ready for use and files needing a supplier response. Version compatibility and required part information become agreed delivery conditions, helping reduce repeated conversion requests.

Build a repeatable conversion service

Agree on source versions, output requirements, and the attributes that need to travel with geometry. A shared configuration helps teams apply the same preparation and quality checks across repeated jobs.

Compare other CAD exchange components, including Parasolid Import and DXF exchange. Discuss an ACIS workflow with a sample file and a receiving application.