BPMN 2.0 – Business Process Model and Notation with ADONIS BOC Group - Trust in more than 20 years of experience in IT-supported management!

Pools and Lanes Relations

A task is an atomic activity within a process flow. The symbol marks a collapsed sub-process which describes a detailed process flow.

Without a defined type Designed to send a message to an

external participant

Designed to wait for a message to arrive from an external participant

Carried out manually by a human performer

Executed by a human performer (software

application asistance)

Evaluates business rules

Executed by a business process

engine

Carried out auto-mati-cally (e.g. web service)

A call activity identifies a point in the process where a global process or a global task is used.

A pool is the graphical representation of a participant in collaboration. A collapsed pool represents an external participant whose process details are unknown or irrelevant.

Lanes represent responsibilities within a pool and could represent a role, a depart- ment or an IT-system.

The collaboration diagram depicts the interaction between several processes. Each process is placed in its own pool interacting with other processes via message flows. Processes with details of which are unknown or are of no importance for the viewer are represented as a black-box pool.

Conversation and choreography are further diagram types in BPMN 2.0. Due to the fact that these diagrams are currently not considered to be very significant to business process diagramming, we will not go into further detail here. Nevertheless they can be fully modelled in ADONIS.

A transaction is a specialised type of sub- process which has a special behaviour that is controlled by a transaction protocol.

An event sub-process allows capturing an event in the context of a process or sub-process.

Activities: Markers:

Stru

ctur

e Lev

el

Proc

ess M

aps,

Prod

uct C

atalo

gues

Type of Activities:

Proc

ess F

low

Leve

l

Busin

ess P

roce

ss D

ia -gr

ams,

Sub-

proc

esse

s

Data

Integrated process view in ADONIS – BPMN 2.0 fit for business

Artifacts

Gateways

Collaboration Diagram

Exclusive Gateway: Diverging: it routes the sequence flow to exactly one of the outgoing branches. Converging: it waits for one incoming branch to complete be-fore activating the outgoing flow.

Exclusive Event-based Gateway (instantiate): the occurrence of one of the subsequent events starts a new process instance.

Parallel Gateway (AND): Diverging: all outgoing branches are activated simultaneously. Converging: it waits for all in-coming branches to complete before triggering the outgoing flow.

Parallel Event-based Gateway (instantiate): the occurrence of all subsequent events starts a new process instance.

Event-based Gateway: represents a branching point in the process where the alternative paths that follow the gateway are based on intermediate events or on receiving tasks.

Gateways are used to control the process flow through sequence flows as they converge and diverge within a process.

Complex Gateway: complex converging and diverging behaviour that is not captured by other gateways.

Inclusive Gateway (OR): Diverging: it waits for all activated branches to complete before triggering the outgoing flow. Converging: depending on the fulfilled con-ditions one or more branches are activated

A Data Input is an external input for the entire process. It can be read by an activity. A Data Output is a variable available as result of the entire process.

A Data Object represents information flowing through the process, such as business documents, e-mails, letters etc.

A Collection Data Object represents a collection of information (e.g. a list of order items).

A Data Store is a place where the process can read or write stored data, e.g. a database or a filing cabinet.

A Message is used to depict the contents of a communication between two participants.

The Group object is an artifact that provides a visual mechanism for the grouping of diagram elements that belong in the same category.

Text annotations are a mechanism for a modeller to provide additional text information for the reader of a diagram.

Pool

Lev

el

Proc

ess E

nviro

nmen

t

The process architecture is illustrated through the use of process maps. Process maps can reference other process maps or link directly to BPMN 2.0 business process dia-grams and the process flow level.

The detailed processes are modelled as BPMN 2.0 business process diagrams and could - if needed as in the case of sub-processes - be linked to each other through dynamic references. Their tasks can reference single reusable elements on the pool level: roles, risks and controls, IT-systems, documents etc.

Working Environment Model:Role pool, Organisational chart

Risk and Control Catalogue:Integration with ICS and ERM

IT-System Model:IT-Architecture Management

Document Model:Linking of templates/instructions

An event is something that “happens” during the course of a process and is either triggered by something external or by the process itself.

Events affect the flow of the process. Examples of events are, e.g., the start or the end of an activity, a change of a document status or a message which is received or sent.

Frequently used Intermediate Events:

Unspecified - an unclassified event; as an intermediate event it is able to illustrate a status change and can only be throwing.

Message - illustrates every kind of information exchange and can be catching (receive) or throwing (send).

Timer - acts as a delay mechanism based on a specific point in time or a time period and can only be catching.

Imprint: publisher and manufacturer: BOC Products & Services AG, place of publishing and manufactoring: Vienna; © Copyright BOC Products & Services AG, Vienna. The BOC Management Office as well as ADOSCORE, ADONIS, ADOLOG, ADOIT, ADONIS:Community and ADOIT:Community are registered trademarks of the BOC Products & Services AG. All of the content is protected. All other named brands are property of the respective companies. All changes can only be made with a written letter of agreement from the BOC Products & Services AG. Reproductions in any form are only allowed with the Copyright remark. Publications and translations need a written letter of agreement from the BOC Products & Services AG.

Sub-Process

Loop

Parallel Multi-instance

Sequential Multi-instance

Ad-Hoc

Compensation

Sequence Flow: defines the execution flow in a business process and is not allowed to cross a pool boundary

Conditional Flow: has a condition that defines whether or not the sequence flow will be used

Default Flow: will be used when none of the condition expressions of the other outgoing sequence flows evaluate to true

Message Flow: A message flow is used to show the flow of messages between two participants (pools). Not to be used within a pool

Activities Events

Here

you c

an fin

d fur

ther in

forma

tion a

bout

our p

rodu

cts an

d ser

vices

: www

.boc

-gro

up.co

m

BOC

Prod

ucts

& S

ervic

es A

GOp

erng

asse

20b,

1040

Vien

na, A

ustria

Ph

one:

+43-

1-90

5 10 7

1-0,

eMail

: info

@bo

c-gr

oup.

com

* often used

* * *

Annotation

ADONIS

ADONIS:Community EditionThe free BPM tool.