← CAD and mesh conversion guides

OCCT conversion workflows

STEP XML to ACIS SAT / SAB

Convert STEP XML to ACIS SAT / SAB. Prepare source geometry, select the target writer and verify placements and supported attributes.

Build this conversion into your application with OCCT readers, writers and the commercial components identified below.

Ask about this workflow
Input interface
OCCT3D STEP XML reader
Processing route
CAD and mesh exchange
Output interface
OCCT3D ACIS writer

Read STEP XML for ACIS SAT / SAB output

A STEP XML-to-ACIS SAT / SAB workflow connects the STEP XML reader to the ACIS SAT / SAB writer. Select the model items and output representation needed by the receiving application.

Read STPX, STPA, STPZ or STPZX with the STEP XML component. The interface supports BRep and mesh representations together with assemblies, names, colors and attributes available in the native STEP data used by the file.

Translate precise geometry into ACIS

Inspect whether each selected part contains BRep, mesh or both. A mesh writer can reuse suitable triangles or tessellate CAD surfaces. A precise-geometry writer needs BRep input; storing triangles in a STEP XML file does not reconstruct analytic surfaces.

Use the ACIS writer for supported BRep geometry and select SAT or SAB for the receiving application. The published component description lists output through ACIS version 7; confirm the delivery and recipient version. A mesh-only input needs another route rather than an implied reconstruction of smooth CAD surfaces.

Check the ACIS SAT / SAB result

Check nested assembly placements and the relationship between attributes and their model items. Information retained by the reader still needs a compatible mapping in the destination writer.

Reopen the file in the recipient and check topology, surface coverage, units and supported attributes. Include translated curved surfaces and multi-body models in the comparison. Reading a file successfully is only the first check when the next task is a modeling operation.

Discuss this conversion with the producing and receiving applications, representative files and required geometry and attributes. Compare the reader/writer catalog when a different representation is needed.

Conversion integration

Build a STEP XML to ACIS SAT / SAB workflow

Share the source and receiving applications, representative files, required attributes and throughput. We can scope SDK evaluation or an integrated conversion service.