The following process models can be used for setting up the process landscape/process hierarchy.
Model name |
Model type number |
---|---|
Value-added chain diagram |
12 |
EPC |
13 |
Function allocation diagram |
14 |
PCD |
18 |
EPC (material flow) |
50 |
PCD (material flow) |
51 |
EPC (column display) |
134 |
EPC (row display) |
140 |
EPC (table display) |
154 |
EPC (horizontal table display) |
173 |
Enterprise BPMN collaboration diagram |
272 |
Enterprise BPMN process diagram |
273 |
The following chapters include a modeling example of the process landscape.
Process modeling at level 1 - Value-added chain diagram (VACD)
The overview process model is the central model at level 1. This is modeled using the value-added chain diagram model type. This core process overview is used as the entry model.
The object type used is Function (OT_FUNC). The hierarchy between the objects is represented by the is process-oriented superior or is process-oriented subordinate connection. In ARIS Risk & Compliance Manager, only a tree structure for hierarchies is allowed. Therefore, each function can only have one superior function. The following model types can be assigned to an object type in a VACD:
Object type |
Assigned model type |
---|---|
Function [Value-added chain] |
VACD |
Function [Value-added chain] |
Function allocation diagram |
Thus, a hierarchy element is created in ARIS Risk & Compliance Manager for each relevant function. Exception: The top hierarchy element already exists in ARIS Risk & Compliance Manager.
Process modeling at level 2 - Value-added chain diagram (VACD)
The value-added chain diagram is used as the model at level 2. Level 2 is used to represent the main processes and to map the context of the sub-processes located at level 3.
The same conventions apply as for the core processes modeled as a value-added chain.
The following model types can be assigned to an object type in the VACD:
Object type |
Assigned model type |
Function |
EPC |
Function |
Function allocation diagram |
Process modeling at level 3 - Event-driven process chain (EPC)
You can describe a company's processes using an EPC. It is based on the logical and chronological sequence of the activities to be carried out. In addition, a sequence of functions and resulting events is used. These lean processes can be supplemented by additional objects (organizational units, positions, roles, application systems, etc.) containing extended information.
The following model types can be assigned to an object type in an EPC:
Object type |
Assigned model type |
---|---|
Function |
EPC |
Function |
Function allocation diagram |
Attribute mappings: Function (ARIS) to Process hierarchy element (ARCM)
ARIS attribute |
API name |
ARCM attribute |
M* |
Notes |
---|---|---|---|---|
Name |
AT_NAME |
name |
X |
|
|
|
isroot |
|
True only for the top hierarchy element. |
|
|
type |
|
Process hierarchy (value 4) |
Description/ |
AT_DESC |
description |
|
Provides more details about the element, for example, its purpose. |
|
|
status |
X |
Status is true (if active) |
Sign-off- |
AT_AAM_SIGN_OFF |
signoff |
|
Only relevant for Sign-off Management. |
Model link |
AT_AAM_MOD_LINK |
modellink |
|
|
|
|
modelguid |
|
GUID of the model containing an occurrence of the function. The first available process model (EPC, VACD, etc.) is selected. |
|
|
model_name |
|
Name of the model (see above) |
Object link |
AT_AAM_OBJ_LINK |
objectlink |
|
|
GUID of object |
|
objectguid |
|
|
|
|
children |
|
Subordinate hierarchy element |
*The M column specifies whether the attribute is a mandatory field.