To efficiently manage a large process landscape, it can be broken down into modules. These modules can be connected via interfaces. Process modules can form a hierarchy or process architecture.

Typical process modules are Requirements Engineering, Design, or Project Management. As process modules can be used to separate common from specific processes, a “Design” process module could be used to contain the common elements in a “Engine Design” and “Transmission Design” process module. See process variant management for more info.

The only difference between a process and a process module is that a process module can be added to other processes or process modules, whereas a process can not be added anywhere else.

A process module resides in a workspace just like a normal process. In fact, the only thing that differentiates process modules from processes is this setting, which can be changed via the Management > Settings menu.

SCREENSHOT

If this setting is set to “Process Module”, the module can be added to other processes.

Only valid versions of a process module can be added to other processes. This increases the consistency within your process architecture. Before adding a module to another process, a process version needs to be created and set as the Valid Version. See process version management for more info how to do this.

To add a module to a process, switch to the process you would like to add the module to, and go to the Management > Process Modules menu.

SCREENSHOT

In the first tab, you can find the list of already added modules. In the second tab you can find the list of processes that the current module has been added to.

Click or tap on Add module to add a new process module.

- Create new workspace

- Select “Add Modules”

- Spot the outdated modules

- Update them one by one or multiple in sequence

- Remote associations

- Become normal associations when both modules are added to one process