IT and Business Process Modelling course at IT University of Copenhagen (Lecture 1+2)

IT
UNIVERSITY
OF
COPENHAGEN

IT and Business Process Modelling
Business Process Modelling & Analysis
Thomas Hildebrandt

IT University of Copenhagen

www.itu.dk/people/hilde

hilde@itu.dk

!
!
First lecture of

IT and Business Process Modelling (BIMF, GBI)

& Business Process Modelling and Analysis (DBMA, DIM & SDT-SE)

!
January 26th, 2015

Partly based on lecture slides (ch 2) by M. Reichert and B.Weber, available at www.ﬂexible-processes.com

IT
UNIVERSITY
OF
COPENHAGEN

IT and Business Process Modelling & Analysis (BIMF & DBMA) Thomas Hildebrandt, hilde@itu.dk
BIMF/DBMA Lecture 1, January 26th, 2015
Road
Map
• 10-10.15: Learning Outcomes, Group project & Exam

• 10.15-10.45:What is a (Business) Process ?

• 11.00-11.45: Process-Aware Information Systems

• 12.30-14.00:Theory review-exercises in groups
2

IT
UNIVERSITY
OF
COPENHAGEN

Learning
Outcomes
(BSc)
3

IT
UNIVERSITY
OF
COPENHAGEN

Learning
Outcomes
(MSc)
4

IT
UNIVERSITY
OF
COPENHAGEN

DescripFon
at
learnit
5

IT
UNIVERSITY
OF
COPENHAGEN

Rough
outline
of
course
• Week 1-5: Business Process constraint mapping 
(ch 1-3+12 + research papers)

• Week 6-10: Pre-speciﬁed processes,  
ﬂexibility by design and compliance (Ch 4-6+10)

• Week 11-15: Ad-hoc changes, mining & evolution
(Ch 7-9+12 +18 + research papers)

• MSc must pick advanced topic: Ad-hoc changes (7),
Monitoring & Mining (8), Evolution (9), Compliance (10)
6

IT
UNIVERSITY
OF
COPENHAGEN

Group
Project
&
Exam
• During the course you will in groups (5 students)

• present a process constraint model (Feb 23rd)

• hand-in of your report (April 9)

• give feedback to software dev. group

• upload a ﬁnal report (May 19th in LearnIT)

• give a 8 min joint presentation of report at exam
followed by 8 min individual oral examination

7
learnit.itu.dk/course/view.php?id=1970132

IT
UNIVERSITY
OF
COPENHAGEN

What
is
a
Process
?
8
“A
process
is
a
speciﬁc
ordering
of
work
acFviFes
across
Fme
and

place,
with
a
beginning,
an
end,
and
clearly
deﬁned
inputs
and

outputs:
a
structure
for
acFon”
[Davenport
1993,
p.
5].

A process is a collection of activities/events,

ordered across time & space,

carried out by actors, and

depending on & producing data/resources.
Some activities/events start the process (the beginning)

Others are goals (the end)

A business process creates value for customers

(& the business)

IT
UNIVERSITY
OF
COPENHAGEN

Process
examples
• Booking a travel

• Delivering beer to customers

• Getting pain relief at the hospital

• Getting a new loan or credit card in the bank

• Helping an unemployed at the job-center to get a job
9
Who are the actors ? What are the activities/events ?
What are the goals, ending and starting events ?
How would you order the activities/events ?
What data/resources produced & used by activities ?

IT
UNIVERSITY
OF
COPENHAGEN

Hospital
process
example
10

IT
UNIVERSITY
OF
COPENHAGEN

Hospital
process
example
11
Actors ?

IT
UNIVERSITY
OF
COPENHAGEN

Hospital
process
example
12
Actions

& Events ?
Start ?
Goal ?
Data ?

IT
UNIVERSITY
OF
COPENHAGEN

Group
Exercise
(10-‐15
min)
• Discuss processes you know

• Describe (with post-it notes on A3 paper):

• Actors ?

• Activities/Events ?

• Starting (triggering) and Ending (goals) events ?

• Data & Resources used/produced ?

• Ordering of Activities/Events ?

• Put A3 paper on the black-board (with group name)
13

IT
UNIVERSITY
OF
COPENHAGEN

Summary
&
Discussion
14
• Easy to identify activities/events ?

• What is the right level of detail ?

• Is there a relation between data dependencies and
ordering of events ?

• Can (some of) the activities/events be repeated/
skipped ?

• How do we represent the dependencies ?

IT
UNIVERSITY
OF
COPENHAGEN

Time
for
a
break!
15

IT
UNIVERSITY
OF
COPENHAGEN

Process-aware
Information Systems (PAIS)
What ?
Why ?
How ?

IT
UNIVERSITY
OF
COPENHAGEN

What
are
PAIS
&
why
bother?
17
• Process-Aware Information Systems (PAIS) =
Information systems that are aware of the (business/
workﬂow) processes they support

• The motivations & goals are typically to improve
efﬁciency, quality, agility and document compliance

IT
UNIVERSITY
OF
COPENHAGEN

Process
characterisFcs
18
• Long-running (from seconds to years)

• Persisted state

• Sleeps most of the time

• Orchestrates system and/or human actors

• Understood (and managed) by business analysts

• Adaptable

• Reusable
a domain speciﬁc architecture and
languages for business processes
execution (and management) ?

IT
UNIVERSITY
OF
COPENHAGEN

How
to
make
a
PAIS
?
19
• PAIS introduce an extra architectural layer, separating
the process logic from the application code

• Typical examples include Business Process,Workﬂow
and Case Management Systems (BPMS,WfMS & CMS)

• Often used with a Service Oriented Architecture (SOA)

IT
UNIVERSITY
OF
COPENHAGEN

Process
&
Service
Oriented
Architecture
20
offer
workenactment
service
management
tools
design tools
run-time data
process
data
organizational
data
perform
work worker
management
designerhistorical
data
case
dataapplications
Figure 9: The architecture of a PAIS.
ng a simple workflow process. Work is offered through so-called work queues.
One worker can have multiple work queues and one work queue can be shared
among multiple workers. The window in the middle shows the set of available
work queues (left) and the content of one of these work queues (right). The bottom
window shows an audit trail of a case. The three windows show only some of the
capabilities offered by contemporary workflow management systems. It is fairly
Process-Aware Information Systems:
Design, Enactment, and Analysis
Wil M.P. van der Aalst
Department of Mathematics and Computer Science, Eindhoven University of Tech-
nology, P.O. Box 513, NL-5600 MB Eindhoven, w.m.p.v.d.aalst@tue.nl
Abstract. Process-aware information systems support operational business pro-
cesses by combining advances in information technology with recent insights
from management science. Workflow management systems are typical examples
of such systems. However, many other types of information systems are also
“process aware” even if their processes are hard-coded or only used implicitly
(e.g., ERP systems). The shift from data orientation to process orientation has in-
creased the importance process-aware information systems. Moreover, advanced
analysis techniques ranging from simulation and verification to process mining
and activity monitoring allow for systems that support process improvement in
various ways. This article provides an overview of process-aware information
systems and also relates these to business process management, workflow man-
agement, process analysis techniques, and process flexibility.
Keywords: Process-Aware Information Systems, Workflow Management, Busi-
ness Process Management, Petri Nets, Process Mining, Process Verification, Sim-
ulation
1 Introduction
Information technology has changed business processes within and between enter-
prises. More and more work processes are being conducted under the supervision
of information systems that are driven by process models. Examples are work-
flow management systems such as FileNet P8, Staffware, WebSphere, FLOWer
and YAWL and Enterprise Resource Planning (ERP) systems such as SAP and
Oracle. Moreover, many domain specific systems have components driven by
(process) models. It is hard to imagine enterprise information systems that are
unaware of the processes taking place. Although the topic of business process
management using information technology has been addressed by consultants
1
Web-services

internal services (e.g. database)
e.g. electronic

forms or case
management tool
processes are (re)designed. In the configuration phase, designs are
by configuring a PAIS (e.g., a WFMS). After configuration, the ena
starts where the operational business processes are executed using th
figured. In the diagnosis phase, the operational processes are analyz
problems and to find things that can be improved. The focus of tra
flow management (systems) is on the lower half of the life-cycle. A
is little support for the diagnosis phase. Moreover, support in the d
limited to providing an editor while analysis and real design suppor
Figure 13: PAIS life-cycle.
In this article, we showed that PAISs support operational busin
by combining advances in information technology with recent insig
agement science. We started by reviewing the history of such sys
focused on process design. From the many diagramming techniques
chose one particular technique (Petri nets) to show the basics. We als
the relevance of process analysis, e.g., by pointing out that 20 perce
than 600 process models in the SAP reference model are flawed [
26

IT
UNIVERSITY
OF
COPENHAGEN

Example:
Financial
BPM
on
top
of
SOA
21
• Customer packet: Business process for
creating ﬁnancial products (credit cards,
internet bank access,etc)

• 10 different systems, 30 sub processes, 200
service calls/human tasks.

• From 200 packets a day to 1800 a day

• 80% automation
Steen Brahe, Industrial PhD, Danske Bank & IT University of Copenhagen
Best

Industry
Paper

“BPM on Top of SOA: Experiences from the Financial Industry”, BPM 2007

IT
UNIVERSITY
OF
COPENHAGEN

Three
trends...
• From Programming to Orchestration

• From Data orientation to Process orientation

• From Design to Re-design and dynamic growth
22

IT
UNIVERSITY
OF
COPENHAGEN

Not
an
enFrely
new
idea
Early research in Office Automation

Describing office work as flow-graphs
(Petri Net)
23
zc
:=
Computer Science and
Office Information Systems
By Clarence A. Ellis and Gary J. Nutt
• Zisman & Hammer 1977

• IBM Business Definition Language (BDL)

• Information Control Net [Ellis 1979 Xerox]

IT
UNIVERSITY
OF
COPENHAGEN

InformaFon
Control
Net
24
ORDERPROCESSING
LogRequest
TypeOrder
SendOrder
ReceiveOrder
BrocessII
J
I
I
•
:1.1
Customer
Request
Arrival
lL
-""/
I
I
r
•r
J/.I
I
A/I
"
Order
Form
'"I
+0I,Custamer
JjFile
I
IIBillingFile
I
I
I
J
I
J
I
I
I
I
I
I
I
/
I,
lOut"
1:;;1tJ.lOut.I
tForm'--------/--""
',----..._------_.._-..,.-'
F.igure2
[C. Ellis, 1979]
used by SCOOP are document generators; electronic mail senders and receivers; file services, and
media schedulers.
Although the complexity and number of the special purpose systems may grow large as the office
automation area grows, the monitor (or office operating system supervisor) can remain relatively
constant. Zisman provides guidelines and frameworks for a high level non-procedural specifications
language, and that contains a document definition section for declaring all documents needed, an
activity initiation section for describing when each activity can be performed and an activity detail
section. The activity detail section describes the detail tasks to be done when the activity is initiated
by a few basic operations, wen-known to an office analyst. Procedure descriptions in this language
could then be translated into an augmented Petri net and run using the execution monitor, SCOOP.
By considering the specification language, the internal representation, and the design of a prototype
system using one unified model, Zisman has been able to study the office as a system rather than
simply as a collection of isolated tasks and pieces of equipment. Although Zisman suggests the
language and the model need refinement, his basic notions will probably have great impact on the
office of the future.

IT
UNIVERSITY
OF
COPENHAGEN

Business
Process
Model
and
NotaFon
(BPMN)
2.0
25
Figure from the BPMN 2.0 Final Speciﬁcation, 2011

IT
UNIVERSITY
OF
COPENHAGEN

30
years:
What
happened?
• Optimism in late 70ties and early 80ties

• Not any real success... lack of standards and too rigid

• 90ties to now:

• Graphical User Interfaces

• Internet, Service and
Process standards
26
(but still too rigid...)

IT
UNIVERSITY
OF
COPENHAGEN

Workﬂow
Management
CoaliFon
(WfMC)
1993
27
Workflow Engine(s)
Process Definition
Tools
Other Workflow
Engines
Workflow Client
Applications
Invoked
Applications
(e.g. Webservices)
Administration and
Analysis Tools
WfMC Workﬂow Reference Model 1995
(IBM, HP, Fujitsu, ..
Graphical process
notations/ languages
(BPMN, EPCs, UML Activity
Diagrams, Petri Net, ...)
Export language

(BPMN-XML,XPDL,WSFL,WS-BPEL,..)
Service access, addressing and
description languages

(WSDL, abstract WS-BPEL, ..)
Human Task languages
(BPEL4PEOPLE, BPMN2.0)
DB
Instance run-time &
persistence

format
Query languages

IT
UNIVERSITY
OF
COPENHAGEN

Many
modelling
standards
-‐
converging
to
BPMN
28
R. Shapiro,WfMC, 2010
IBM WSFL 1.0
MS XLANG 1.0
BPEL4WS 1.0
BPEL4WS 1.1 WS-BPEL 2.0
OASIS
CMMN 1.0
(BETA)
2013

IT
UNIVERSITY
OF
COPENHAGEN

An
example
BPMN
process
29
A pre-speciﬁed process for planning a surgery:
(Example 2.3,

Fig 2.2, page 13-14)

IT
UNIVERSITY
OF
COPENHAGEN

Zooming
in
on
OutpaFent
Dept
30

IT
UNIVERSITY
OF
COPENHAGEN

Diﬀerent
perspecFves
31
Business
Function 1
...
Business
Function
2
Business
Function
3
Business
Function 4
Business
Function n
..
.
!
business functions
Function
Perspective
EXECUTABLE PROCESS MODEL
control flow:
order & execution
constraints
Behavior
Perspective
data objects &
data flow
Information
Perspective
time constraints
(e.g., activity deadlines)
Time
Perspective
organizational model
(actors, roles,
organizational units)
Organization
Perspective
activity implementations &
application services
Operational
Perspective

IT
UNIVERSITY
OF
COPENHAGEN

FuncFon
PerspecFve
32
atomic
complex

IT
UNIVERSITY
OF
COPENHAGEN

Behavior
PerspecFve
33
Alternative
/choice
Sequence
Parallel

IT
UNIVERSITY
OF
COPENHAGEN

Behavior
as
constraints
34
A constraint based
(declarative) model describes
what & why rather than how
(Declare)

IT
UNIVERSITY
OF
COPENHAGEN

Behavior
as
constraints
35
A constraint based
(declarative) model describes
what & why rather than how
(Declare)

IT
UNIVERSITY
OF
COPENHAGEN

Constraints
as
DCR
Graphs
36

IT
UNIVERSITY
OF
COPENHAGEN

Data-‐centric/OO
behavior
37
In a data-driven/centric process the behavior is described
by state of data attributes

(belonging to objects/business entities)

IT
UNIVERSITY
OF
COPENHAGEN

InformaFon/InteracFon
38

IT
UNIVERSITY
OF
COPENHAGEN

OrganizaFonal
39

IT
UNIVERSITY
OF
COPENHAGEN

OperaFonal
PerspecFve
40
COBOL
PL1
.NET
SAP
Java
service
Enterprise Service Bus (ESB)
service service
Risk Department Credit Department Customer Department
Task
Sub
Process
Sub
Process
Data interoperability standards, e.g. HL7 for
healthcare data and XBRL for business/ﬁnance
(Time perspective)

IT
UNIVERSITY
OF
COPENHAGEN

Components of a PAIS
offer
workenactment
service
management
tools design tools
run-time data
process
data
organizational
data
perform
work worker
management
designerhistorical
data
case
dataapplications
Figure 9: The architecture of a PAIS.
ing a simple workﬂow process. Work is offered through so-called work queues.

IT
UNIVERSITY
OF
COPENHAGEN

Components of a PAIS

IT
UNIVERSITY
OF
COPENHAGEN

Build
vs.
Run-‐Fme
43
(may be combined if we allow adaptation)

IT
UNIVERSITY
OF
COPENHAGEN

Build-‐Fme
veriﬁcaFon
• Functional: Refer to taxonomies (naming) & attributes

• Behavior: Deadlocks? Livelocks? Soundness ?

• Information: Missing, wrong or unnecessary data ?

• Organisation: Missing actors or authorizations ?

• Operation:Assigned application services to all atomic
activities ?
44
Veriﬁcation concerns all process perspectives:

IT
UNIVERSITY
OF
COPENHAGEN

Run-‐Fme
Environment
• Process instance life-cycles

• Activity instance life-cycles

• Work-item life-cycles
45

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
life
cycle
46
(may be extended to allow adaptation)

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
state
47
When an instance is running it is in a particular state

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
state
48
DCR Graphs can also represent instance state

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
state
49

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
state
50

IT
UNIVERSITY
OF
COPENHAGEN

Process-‐instance
state
51

IT
UNIVERSITY
OF
COPENHAGEN

AcFvity-‐instance
life-‐cycle
52
Each individual activity has a life-cycle too

IT
UNIVERSITY
OF
COPENHAGEN

Human
acFviFes
53
Enabled, human activities create work items to work lists
Depends on actor assignment and organizational model

IT
UNIVERSITY
OF
COPENHAGEN

Work-‐item
life-‐cycle
54

IT
UNIVERSITY
OF
COPENHAGEN

Summary
• Process-aware Information Systems

• Know the logic of the supported processes

• Ensure ordering constraints are satisfied

• Controls flow of data

• Knows application services and work-items
assigned to automated and human activities

• Enables end-users to monitor and trace executions

• Future:Allow run-time, verified adaptation
55

IT
UNIVERSITY
OF
COPENHAGEN

Exercises
• Do exercise 2.1-2.4 in your groups and write down
your answers. Use your own process examples or
the one below
56

IT and Business Process Modelling course at IT University of Copenhagen (Lecture 1+2)

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à IT and Business Process Modelling course at IT University of Copenhagen (Lecture 1+2)

Similaire à IT and Business Process Modelling course at IT University of Copenhagen (Lecture 1+2) (20)

Dernier

Dernier (20)

IT and Business Process Modelling course at IT University of Copenhagen (Lecture 1+2)