AIMS is automatically grouping components which are used in the same messaging pattern. In some cases, this functionality can create one big process which in real life should have been multiple smaller ones. This usually happens due to components that are shared between logical processes such as error routing components etc.

For instance, you have an Orders and Invoice process, both sharing the error routing components. Due to this setup, AIMS will group both the Orders and Invoice process together as one big messaging pattern. By moving the error routing components out of this group and to a new separate process, the existing big messaging pattern will be split into two smaller messaging patterns corresponding to Orders and Invoice process.

The video below shows how to split up such big processes into smaller logical units by removing the common components from the messaging pattern.