ACIS Geometry Kernel

Definition & Context

ACIS (originally Alan, Charles, Ian's System) is a geometric modeling kernel developed by Spatial (Dassault Systèmes subsidiary) that provides B-Rep (boundary representation) solid modeling capabilities to host CAD applications. AutoCAD, BricsCAD, SpaceClaim, and approximately 50 other products embed ACIS for solid/surface operations.

The kernel supports: precise NURBS surfaces, analytic surfaces (planes, cylinders, cones, spheres, tori), Boolean operations, blending (fillets/chamfers), sweeps, lofts, shelling, and topology queries. Data is serialized in SAT (text) or SAB (binary) file formats. AutoCAD's ACISOUT/ACISIN commands export/import native kernel data.

ACIS differs from Parasolid (used by SOLIDWORKS, NX) in its tolerance handling, healing algorithms, and surface intersection strategies. Translation between ACIS-based and Parasolid-based CAD often introduces tiny geometric mismatches at surface boundaries requiring healing operations.

Why It Matters

Because ACIS underpins solid modeling in AutoCAD, BricsCAD, SpaceClaim, and dozens of other products, knowing how it behaves explains why some geometry survives a round-trip and some does not. When a model moves between an ACIS host and a Parasolid host (SOLIDWORKS, NX), differences in tolerance and surface-intersection handling are what produce slivers, gaps, and failed Booleans.

Understanding the kernel helps you pick the right exchange path — a neutral STEP export usually travels better than a raw SAT hand-off between different kernels — and lets you heal problems at their source (stitching, tolerance) instead of patching symptoms downstream.

Best Practices

• Use SAT format (text-based) for debugging geometry issues — open in any text editor to inspect entity topology
• When exchanging between ACIS and Parasolid hosts, export via STEP AP214 to minimize kernel translation artifacts
• Set appropriate tolerance values (typically 1e-6 for mechanical, 1e-4 for architectural) before Boolean operations
• Validate solid topology after complex Boolean chains with CHECKSOLID or equivalent host commands
• Prefer the binary SAB format for production file exchange — 3-5x smaller than SAT with faster parsing

Common Pitfalls

• ACIS version mismatches cause import failures — older hosts cannot read SAT files written by newer kernel versions
• Slivers and micro-edges from imprecise Boolean operations accumulate and eventually crash downstream operations
• ACIS does not natively support mesh/facet bodies — importing STL into ACIS-based CAD requires conversion to B-Rep
• Stitching open surfaces into solids fails when edge gaps exceed the session tolerance — increase tolerance or heal edges first

References & Further Reading

• https://www.spatial.com/products/3d-acis-modeling

Related Concepts

Explore more Multi-platform topics in our Multi-platform knowledge base, or browse the full terminology index.

For structured learning, see our Multi-platform learning path.

Enterprise Production Implementation & GstarCAD 2027 Workflow

• Database Serialization & Binary Fidelity: Ensure all entities and symbol table records associated with ACIS Geometry Kernel are authored on standardized ISO 13567 layers rather than Layer 0 or Defpoints, and verify lossless round-trip persistence in native DWG (AC1032) format.