ACIS Import-Export Component

On this page

Read and write ACIS SAT and SAB files

The ACIS Import-Export SDK connects ACIS data with Open CASCADE Technology (OCCT) shapes. It handles geometry and topology, with an XDE layer for names and colors. SAT is the text representation; SAB is the binary representation.

Use this component to integrate ACIS exchange into a CAD application or a conversion pipeline. Direct support for an application’s native file format is a separate requirement from support for its ACIS exports.

Geometry translation and attribute handling

The geometry layer translates between ACIS entities and OCCT shapes in both directions. Applications can use BRep conversion on its own or combine it with XDE for names and colors. The XDE API exposes those attributes and their associations for application processing and subsequent export.

Automatic Shape Healing is available during translation, with operations configurable through resource files. The documented handling of complex ACIS geometry includes approximation where necessary for entities from ACIS 5.0 and later. For such inputs, approximation and repair tolerances belong in the conversion configuration and in output-quality checks.

Output configuration should reflect the receiving system’s representation and version requirements. A source file’s readable ACIS version and the writer’s supported output version are separate compatibility decisions.

SAT or SAB to STEP

Read the ACIS input into OCCT shapes or an XDE document, inspect the translation result, and use the OCCT STEP writer for output. Reopen the result and check model units, shape validity and any required names or colors.

Shape healing can help address source geometry and topology issues. Healing and approximation settings should follow the application’s accuracy requirements; translation is not a promise that every source entity and attribute transfers unchanged.

STEP to SAT or SAB

For the reverse workflow, use OCCT’s STEP reader followed by the commercial ACIS writer. Select an output version supported by both the component delivery and the receiving application.

The published component description specifies ACIS output through version 7. Confirm the current writer limits and the required SAT/SAB variant during evaluation. Import and export version coverage must be considered separately.

Conversion requirements

Requirement	Integration decision
SAT/SAB to STEP	Commercial ACIS reader plus OCCT STEP writer
STEP to SAT/SAB	OCCT STEP reader plus commercial ACIS writer; verify target version
Geometry and topology	Translate through OCCT shapes and inspect the result
Names and colors	Use XDE and check the attributes required by the target application
Source geometry repair	Configure healing and validate the resulting tolerances

Compare this route with Parasolid import, DXF exchange and the supported CAD formats.

Evaluate ACIS exchange

Specify the source system, SAT/SAB version, conversion direction, target application and required output version. Include the OCCT release, deployment platform and attributes that matter to the workflow.

Request an ACIS SDK evaluation or discuss custom CAD data exchange integration.