1.2 Hierarchy

An CAE™ model is made of objects, such as Parts, Instances, Mesh, Job, etc. These objects have a hierarchy. That is, they are ordered from the bottom (a Part) up to a final .inp file that can be processed by Abaqus™. Each object is built from simpler objects, in this sequence, which is listed in Module:, above the WS:

  1. Part

  2. Property

  3. Assembly

  4. Step

  5. Interaction

  6. Load

  7. Mesh

  8. Job

Each objects is built using the preceding objects plus a host of other objects. For example a Part is built with points, lines, etc.

An important piece of advice is this: build the features of your model as soon as possible in the hierarchy.

For example, add boundary conditions to the Assembly rather than to the Mesh. In this way, you can re-mesh without having to re-apply the boundary conditions. They will carry automatically from the Assembly to every mesh that you later create–over an over again, automatically, without your intervention.

Another example: Create sets on a Part, rather than doing it on an Instance, or worse yet on a Mesh. The sooner you do it, the more freedom you have to change downstream objects with all previous features carried over automatically.