Why ACIS needs an assembly format
A SAT file stores ACIS entities such as bodies, faces and edges. An assembly, however, is built around a top-level assembly model that is not itself an entity, so it can’t be written to a plain SAT file. ASAT solves this: it is a SAT-based format that records the assembly model, its sub-assemblies and component instances, and the part geometry they reference.
ASAB contains the same data in binary form. Binary files are smaller and faster to read and write, so ASAB is the usual choice in production, while ASAT is useful for debugging and for sharing test cases with support teams.