Terminology

Please be aware of the following terms and their context:

Process Editor. GUI for process executor
(Process) Statement. Single execution step in a routine
(Process) Routine. Executable sequence of statements saved in a process executor. See also Process implementation.
Requirements. List of special statements, part of the routine.
Product. Refers typically to Product instance, but can also mean product type in some contexts.
Process Flow group. A grouping of Product types specifically used for defining Process flow sequences and material flow. Each Product type is a member of exactly one Flow group at all times.
Process flow sequence. A sequence of Flow steps defined for a Process Flow Group in the Process flow editor.
Flow step. One step in process Flow Group´s flow sequence. One Flow Step may contain one or more Process Groups.
Process transition. Explicit move from one Process step to another in a Process flow sequence.

Process implementation. Actual independent implementation of a abstract Process in a Process Executor.
Process. An abstract definition of an operation that a machine can perform. The term "Process" can refer either to Process implementation or Process group depending on the context.
Process group. All Process implementations with the same name form a process group.
Transport controller. Implementation of the transport controller behavior. Usually specialized to one type of transport and in a dedicated component. Handles transport of Product instances one Transport link at a time.
Transport link. A one-directional logical connection between two Transport nodes. Tied to a single Transport controller that implements the link.
Transport node. Implementation of transport node behavior. Logically a place where something can be transported to or transported from.
Transport solution. A computed route from one Transport node to another. Contains the references to the Transport links a Product instance should travel through to reach the destination Transport node.
Assembly Product Type. Subcategory of a Product Type that represents an assembly. It defines how to form an assembly from multiple Product Types. Creating a single assembly can create multiple Product Instances.
Assembly Instance. Subcategory of a Product Instance that represents an assembly with one or more items. It contains assembly structure metadata, which allows advanced handling based on the current and desired state. Each Assembly Instance has an “empty” dynamic component of its own, onto which any other Product Instances that are currently part of this assembly are attached hierarchically. Assembly Instance is defined by the Assembly Product Type.
Assembly Step. Represents a subset of the Assembly Type’s contained parts that are usually assembled or disassembled together as a single production step. Assembly Steps have a hierarchical relationship with each other within the same Assembly Type. Each Assembly Step also has an Assembly Pattern.
Assembly Pattern. A collection of Assembly Slots, which form a reusable definition of what (i.e. Product Types) should be placed where (i.e. position and orientation). Assembly Patterns can also exist independently from Assembly Types.
Assembly Slot. Definition of a single logical storage location (position and orientation) and what (i.e. Product Types) should or can be placed into it. Assembly slots are owned by their parent Assembly Pattern.
Assembly Order. Defines or “selects” a subset of Assembly Steps from an Assembly Product Type. This object can then be passed to various assembly-related statements to do their specific operation for those selected steps. Common operations are to bring in and assemble Part Instances into the Assembly Instance (Transport In statement) or disassemble and take them away (Transport Out statement).
Part Product Type. Subcategory of a Product Type that represents only a single product. Creating a Part Product Type always creates exactly one Product Instance (a Part Instance).
Part Instance. Subcategory of a Product Instance that always represents exactly one item and has a single dynamic component for physical representation. It is defined by the Part Product Type.
Product instance. An object created during the simulation and defined by the Product Type. Typically, it is an actual product that moves in the production. Product Instance is a general term that includes both Assembly instance and Part Instance.
Product type. Definition of a product (Part Product Type or Assembly Product Type) from which Product Instances can be created into the simulation. Contains all information needed to create the Product Instances of this type.
Product Instance Bundle. A collection of Product Instances created by attaching their dynamic components together. Product Instance Bundles don’t have assembly structure metadata and are generally handled like Part Instances by PM statements and other logic. Note that there is no such concept as Product Type Bundle.
Transport system. It is formed of Transport Links (between Transport Nodes) in different Flow Groups and Transport Controllers responsible for the transportation via the links. The Transport System's routing information is used, for example, when the Source in a TransportIn statement is "From Previous Process", and the Destination in a TransportOut statement is "To Next Process" or "To Transport Node". Otherwise, no Transport Solution will be assigned to the product, and the transport must be done without the Transport System and Transport Controllers.