0% found this document useful (0 votes)
96 views14 pages

06 Advanced Modelling Rework Repetition

This document discusses advanced process modeling techniques in business process modeling including rework and repetition, handling events and exceptions, incorporating business rules, and using structured and unstructured loops. It provides examples of using block-structured repetition with loop activities, arbitrary cycles, multi-instance activities, and ad-hoc sub-processes.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
96 views14 pages

06 Advanced Modelling Rework Repetition

This document discusses advanced process modeling techniques in business process modeling including rework and repetition, handling events and exceptions, incorporating business rules, and using structured and unstructured loops. It provides examples of using block-structured repetition with loop activities, arbitrary cycles, multi-instance activities, and ad-hoc sub-processes.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Chapter 4: Advanced Process Modeling

Contents
1. More on Rework and Repetition
2. Handling Events
3. Handling Exceptions
4. Processes and Business Rules
5. Recap
Chapter 4: Advanced Process Modeling

Contents
1. More on Rework and Repetition
2. Handling Events
3. Handling Exceptions
4. Processes and Business Rules
5. Recap
More on rework and repetition

XOR-join: entry XOR-split: exit point


point

Structured
cycle (SESE
fragment)

SESE = Single Entry Single Exit fragment, i.e. a fragment delimited by a single entry
node and a single exit node (there are no other incoming arcs into the fragment or
outgoing arcs from the fragment)
Block-structured repetition: Loop Activity

BPMN also provides the loop activity construct to allow the repetition of a task or
sub-process
Example: block-structured repetition
Completion
condition
Until Response is approved

Finalise
Assign Investigate
Ministerial
Ministerial Ministerial
Response
Enquiry Enquiry
Ministerial Ministerial
Enquiry Enquiry
received finilized

Prepare Review
Ministerial Ministerial
Response Response
Enquiry Response
investigated reviewed

Must have a
decision activity
Loop Activity or (Arbitrary) Cycle?
Arbitrary Cycles

Arbitrary = unstructured, i.e. it can have multiple entry and exit nodes (non-SESE).

entry point entry point exit point

exit point

7
Example: multi-instance activity

Procurement
In procurement, typically a quote is to be obtained from all preferred
suppliers (assumption: five preferred suppliers exist). After all quotes
are received, they are evaluated and the best quote is selected. A
corresponding purchase order is then placed.

Dalam pengadaan, biasanya penawaran harga diperoleh dari semua pemasok


pilihan (asumsi: ada lima pemasok pilihan). Setelah semua penawaran
diterima, penawaran tersebut dievaluasi dan dipilih penawaran terbaik.
Pesanan pembelian yang sesuai kemudian ditempatkan.
Solution: without multi-instance activity

Procurement
Parallel repetition: multi-instance activity

Provides a mechanism to indicate that an activity is executed multiple


times concurrently

Useful when the same activity needs to be executed for multiple entities
or data items, such as:
 Request quotes from multiple suppliers
 Check the availability for each line item in an order separately
 Send and gather questionnaires from multiple witnesses in the context of an
insurance claim
Solution: with multi-instance activity

Procurement

cardinality
Our order-to-cash example…
now with pools, messages and MI markers
Uncontrolled Repetition: Ad-hoc sub-process

Contains activities to be executed in arbitrary order and number of times

May define order of sub-set of activities by sequence flow

Completion
Can be used in an early version of a process diagram condition
when the order of execution is still unknown
Until all KPIs reviewed
Example: Ad-hoc sub-process

14

You might also like