Fra Office Automation via BPM til tvær-organisatorisk Case Management og Citizen Development af Thomas Hildebrandt, ITU

Thomas Hildebrandt, hilde@itu.dk

Forbedrede ﬁnansielle processer med
Business Process Management ?
Fra Ofﬁce Automation via BPM til tvær-organisatorisk
Case Management og Citizen Development
Thomas Hildebrandt

Lektor & leder af Process and System Models gruppen ved
IT Universitetet i København

Get F’IT - 25. September 2012

IT
UNIVERSITY
OF
COPENHAGEN

Tuesday, September 25, 12

Get F’IT, BPM Seminar, 25. September, 2012 Thomas Hildebrandt, hilde@itu.dk

kort
om
mig
• PhD i datalogi (processbeskrivelser), Århus, 2000
• Forsker og underviser på IT Universitetet, 1999-
• Forskningsprojekter i it-støttede mobile og
tværorganisatoriske forretningsprocesser og
arbejdsgange (MDCC, Resultmaker, Exformatics)
• Leder af Proces og System modeller forskningsgruppe,
interessegruppe for Processer og IT, og videngruppe
for digitalisering og procesorientering (VidenDanmark)
• Nyt europæisk netværk for “Behavioral Types”
www.itu.dk/research/models 2 IT
UNIVERSITY
OF
COPENHAGEN



Overblik
• State-of-the-art:
Fra Ofﬁce Automation til BPMN 2.0
• Problemer/udfordringer:
Planlægningsoptimisme, ﬂeksibilitet, distribution
• State-of-the-future:
Case Management Modeling Notation (CMMN)
Behavioral/Session Types
Citizen Development
UNIVERSITY
OF
COPENHAGEN



State-‐of-‐the-‐art However, the focus is not on data but on process-related information (e.g., the
ordering of activities). Process mining is also related to monitoring and business
intelligence [41].

8 Conclusion
Process-aware information systems (PAISs) follow a characteristic life-cycle. Fig-
ure 13 shows the four phases of such a life-cycle [7]. In the design phase, the
processes are (re)designed. In the configuration phase, designs are implemented

• Process-Aware Information Systems
by configuring a PAIS (e.g., a WFMS). After configuration, the enactment phase
starts where the operational business processes are executed using the system con-
figured. In the diagnosis phase, the operational processes are analyzed to identify
problems and to find things that can be improved. The focus of traditional work-
flow management (systems) is on the lower half of the life-cycle. As a result there

• A shift from data orientation to
is little support for the diagnosis phase. Moreover, support in the design phase is
limited to providing an editor while analysis and real design support are missing.

process orientation:
Explicit process models
• Business Process Model and Figure 13: PAIS life-cycle.

Notation (BPMN) 2.0 - OMG
In this article, we showed that PAISs support operational business processes
by combining advances in information technology with recent insights from man-
agement science. We started by reviewing the history of such systems and then
focused on process design. From the many diagramming techniques available, we

Standard, 2011 (www.omg.org) chose one particular technique (Petri nets) to show the basics. We also emphasized
the relevance of process analysis, e.g., by pointing out that 20 percent of the more
than 600 process models in the SAP reference model are flawed [24]. We also

26

UNIVERSITY
OF
COPENHAGEN



BPM
eksempel “BPM on Top of SOA: Experiences from the Financial Industry”, BPM 2007
Steen Brahe, Industrial PhD, Danske Bank & IT University of Copenhagen

• Kundepakke: Forretningsprocess for salg af
pakkeløsning: kreditkort, netbankadgang, ...
• 10 forskellige systemer, 30 del-processer, 200
service-kald/menneskelige opgaver.
• Fra 200 pakker om dagen til 1800
• 80% automatisering
UNIVERSITY
OF
COPENHAGEN



BPM
eksempel “BPM on Top of SOA: Experiences from the Financial Industry”, BPM 2007
Best
Steen Brahe, Industrial PhD, Danske Bank & IT University of Copenhagen
Industry Paper

• Kundepakke: Forretningsprocess for salg af
pakkeløsning: kreditkort, netbankadgang, ...
• 10 forskellige systemer, 30 del-processer, 200
service-kald/menneskelige opgaver.
• Fra 200 pakker om dagen til 1800
• 80% automatisering
UNIVERSITY
OF
COPENHAGEN



BPM
anno
1979
• Ofﬁce automation: Zisman & Hammer ’77,
Computer Science and
Office Information Systems
By Clarence A. Ellis and Gary J. Nutt

IBM Business Deﬁnition Language, z
c
:=

Information Control Net (Ellis ’79 Xerox)

, Cus tamer

Billing File
+0
Order

j Fi le
Form

I

' - --- ----/--""
/

tJ .
-"" "

I

I
A
/

/.J
•
I

r
r
I

I

/ I
'" I

I
I

J

',---- ... _------_ .. _-..,.-'
ORDER PROCESSING

II

lL

F.igure 2
Customer
Request
Arrival

"
,

.
Brocess
Send Order
Log Request

Receive Order
Type Order

t Form
:1.

lOut
1:;;1
lOut
1
•

J
J

I
I
J

I

I
I

I
I
I

I
I
I
I
I
I
I

UNIVERSITY
OF
COPENHAGEN



BPM
anno
1979
By considering the specification language, the internal representation, and the design of a prototype

• Ofﬁce automation: Zisman & Hammer ’77,
Computer Science and
system using one unified model, Zisman has been able to study the office as a system rather than Office Information Systems
By Clarence A. Ellis and Gary J. Nutt

simply as a collection of isolated tasks and pieces of equipment. Although Zisman suggests the
IBM Business Deﬁnition Language,
language and the model need refinement, his basic notions will probably have great impact on the z
c
:=

Information Control Net (Ellis ’79 Xerox)
office of the future.

, Cus tamer

Billing File
+0
Order

j Fi le
Form

I

' - --- ----/--""
/

tJ .
-"" "

I

I
A
/

/.J
•
I

r
r
I

I

/ I
'" I

I
I

J

',---- ... _------_ .. _-..,.-'
ORDER PROCESSING

II

lL

F.igure 2
Customer
Request
Arrival

"
,

.
Brocess
Send Order
Log Request

Receive Order
Type Order

t Form
:1.

lOut
1:;;1
lOut
1
•

J
J

I
I
J

I

I
I

I
I
I

I
I
I
I
I
I
I

UNIVERSITY
OF
COPENHAGEN



BPM
anno
2011:
BPMN2.0

(Figur fra BPMN 2.0 Final Speciﬁcation, 2011)

UNIVERSITY
OF
COPENHAGEN



Hvad
skete
der
i
de
30
år?

UNIVERSITY
OF
COPENHAGEN



Hvad
skete
der
i
de
30
år?
• Sene 70‘ere/tidlige 80‘ere: Optimisme, men ikke
success - manglende standarder, primitive
brugergrænseﬂader og for rigide processer...

UNIVERSITY
OF
COPENHAGEN



Hvad
skete
der
i
de
30
år?
• Fra 90‘erne til nu: Service og process-standarder
(WfMC, Oasis, OMG), intuitive brugergrænseﬂader,
optimisme....

UNIVERSITY
OF
COPENHAGEN



Hvad
skete
der
i
de
30
år?
• Fra 90‘erne til nu: Service og process-standarder
(WfMC, Oasis, OMG), intuitive brugergrænseﬂader,
optimisme.... men stadig for rigide process-modeller...
“Good standards for business process
modelling are still missing and even today’s Process-Aware Information Systems:
WFMSs are too rigid” Design, Enactment, and Analysis
Wil M.P. van der Aalst
Department of Mathematics and Computer Science, Eindhoven Universit
nology, P.O. Box 513, NL-5600 MB Eindhoven, w.m.p.v.d.aalst@tue.nl

UNIVERSITY
OF
COPENHAGEN

Abstract. Process-aware information systems support operational busi
cesses by combining advances in information technology with recent
from management science. Workﬂow management systems are typical
Tuesday, September 25, 12 of such systems. However, many other types of information systems


Eksempel
• Arbejdsgangsbanken.dk - KL og KOMBIT
• Næsten 900 gode (best practice) og korrekte
(lovmedholdige) arbejdsgange modelleret i BPMN og
gjort frit tilgængelige

UNIVERSITY
OF
COPENHAGEN



Nogle
udfordringer....

UNIVERSITY
OF
COPENHAGEN



Nogle
udfordringer....
• Processer, opgavefordeling og
lovgivning ændrer sig konstant og er
afhængig af lokale forhold [Magnus Nilsson, ITU TR-2011-140]

UNIVERSITY
OF
COPENHAGEN



Nogle
udfordringer....

• Den samme hændelse optræder i ﬂere
processer/love - med forskellige navne

UNIVERSITY
OF
COPENHAGEN



Nogle
udfordringer....

• Den samme hændelse optræder i ﬂere •

Lov
om
Aktiv
beskæftigelsesindsats

(LBK
nr
1428
af
14/12/2009)

processer/love - med forskellige navne
•

Lov
om
Aktiv
socialpolitik

(LBK
nr
946
af
01/10/2009)

•

Lov
om
Arbejdsløshedsforsikring

(LBK nr 574 af 27/05/2010)

•

Lov om Integration af udlændinge

• Ingen formel sammenhæng mellem lov
(LBK nr 1062 af 20/08/2010)

•

Lov om Sygedagpenge

(LOV nr 563 af 09/06/2006)

og process •

Retssikkerhedsloven

(LBK
nr
1054
af
07/09/2010)

•

Datagrundlag

UNIVERSITY
OF
COPENHAGEN

(BEK nr 418 af 23/04/2010)


Computer
Supported
CooperaUve
Work
(CSCW)

• Nyt forskningsområde introduceret i 80‘erne -
fokus på at forstå hvordan folk samarbejder som
basis for at designe it-systemer der kan støtte
• Afhængigheder mellem og koordinering af opgaver
• Konkluderede allerede i ’83 at ofﬁce automation
systems “do not deal well with unanticipated
conditions” (Barber) og “were automating a
ﬁction” (Sheil)
[Schmidt & Bannon: Taking CSCW Seriously: Supporting Articulation Work, 1992]
UNIVERSITY
OF
COPENHAGEN



Mål
• Processstøtte
• Effektivitet, korrekthed, vedligeholdbarhed
• “Elasticitet” og ﬂeksibilitet på tværs af organisationer
• Bygge bro mellem regulationer/policies og processer

UNIVERSITY
OF
COPENHAGEN


any advances were made in the eighties. In the nineties, there again was a huge
Get F’IT, BPMthese systems. The number of WFMSs developed in Hildebrandt, hilde@itu.dk
interest in Seminar, 25. September, 2012 Thomas the past decade
and the many papers on workflow technology illustrate the revival of office infor-

Mål
mation systems. Today WFMSs are readily available. However, their application
is still limited to specific industries such as banking and insurance. As indicated
by Skip Ellis it is important to learn from these ups and downs. The failures in
the eighties can be explained by both technical and conceptual problems. In the
eighties networks were slow or not present at all, there were no suitable graphical
• Processstøtte
interfaces, and proper development software was missing. However, there were
also more fundamental problems: a unified way of modeling processes was miss-
• Effektivitet, korrekthed, vedligeholdbarhed
ing and the systems were too rigid to be used by people in the workplace. Most of
the technical problems have been resolved by now. However, the more conceptual

• “Elasticitet” og fleksibilitet på tværs af organisationer
problems remain. Good standards for business process modeling are still missing
and even today’s WFMSs are too rigid.

•
One of the great challenges of PAISs is to offer both support and flexibility.
Today’s systems typically are too regulationer/policies og processer
Bygge bro mellem rigid, thus forcing people to work around the
system. One of the problems is that software developers and computer scientists
are typically inspired by processes inside a computer system rather than processes
outside a computer. As a result, these engineers think in terms of control systems
rather than support systems. This explains that few of the existing WFMSs allow
for the so-called implicit choice, i.e., a choice resolved by Process-Aware Information Systems:
the environment rather
Design, Enactment, and Analysis
than the system. Wil M.P. van der Aalst
To summarize we would like to state that, although the relevanceNIVERSITY
OF
CisEindhoven University o
www.itu.dk/research/models nology, P.O. Box 513, U
of PAISs OPENHAGEN

Department of Mathematics and Computer Science,
IT
NL-5600 MB Eindhoven, w.m.p.v.d.aalst@tue.nl

12
undisputed, many fundamental problems remain to be solved. In the remainder support operational busines
Abstract. Process-aware information systems of
Tuesday, September 25, 12 cesses by combining advances in information technology with recent in


State-‐of-‐the-‐future
• Adaptive Case Management

• Communication-centered computing &
Behavioral types (protokoller/kontrakter)

• Brugerinddragelse (Generativity, citizen
developers)

UNIVERSITY
OF
COPENHAGEN



AdapUve
Case
Management
Keith Swensson: Mastering the Unpredictable

“Adaptive Case Management (ACM) is information technology that
exposes structured and unstructured business information (business
data and content) and allows structured (business) and unstructured
(social) organizations to execute work (routine and emergent
processes) in a secure but transparent manner.”

http://www.xpdl.org/nugen/p/adaptive-case-management/public.htm
UNIVERSITY
OF
COPENHAGEN



AdapUve
Case
Management


BPM

UNIVERSITY
OF
COPENHAGEN



AdapUve
Case
Management


BPM ACM

(case ﬁles)

UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
• OMG Request for Proposals (RFP) September 2009
Case Management Process Modeling (CMPM) udvidelse
til BPMN 2.0
(bmi/2009-09-23, www.omg.org/public_schedule)
• BizAgi, Cordys, IBM, Oracle, SAP og Singularity:
Case Management Modelling Notation (CMMN) V1.0
(stærkt inspireret af Guard-Stage-Milestone paradigme
udviklet ved IBM Research)
UNIVERSITY
OF
COPENHAGEN



Case
Management
RFP
http://www.omg.org/public_schedule/)

• A situation/case and desired outcome
• A subject: person, insurance claim, ...
• Actions/events to achieve the outcome
• Human judgment/decision-making
• No predeﬁned sequence
• Guidance, prompts, constraints & planning support
UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling

UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
• Afhængigheder mellem handlinger - ikke
eksplicit process-ﬂow

UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
14 Days
Opfølgning (response)
U LO

Open Hold meeting
case with DA

Betingelse
(condition)
Update
Case

UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
14 Days
U LO

Open Hold meeting
case with DA

Betingelse
(condition)
Update
Case

• Tillad dynamiske ændringer

UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
14 Days
U LO & DA LO

Open 3 Days Agree on Hold meeting
case date with DA

Betingelse
(condition)
Update
Case


UNIVERSITY
OF
COPENHAGEN



Case
Management
Modelling
14 Days
U Lo % Lo LO

Open 3 Days Propose Accept Hold meeting
case dates-LO + LO with DA

Betingelse 1 Day
%

(condition) DA
1 Day
% DA
+
Update
Propose Accept %
dates-DA DA
Case


UNIVERSITY
OF
COPENHAGEN


ribution of DCR Graphs [5]. As havioral type systems for distributed DCR Graphs.
distribution provides for any (cov-
vents, a set of corresponding local References:
1. Van der Aalst, Pesic.: DecSerFlow: Towards a truly declarative

Case
Management
Modelling
jections. service flow language. WS-FM 2006.
N
2. Hull et al.: Business Entities with Guard-Stage-Milestone Life-
prescribe
cycles: Managing Entity Interactions with Conditions and Events
sign
medicine
DEBS 2011

•
3. Hildebrandt and Mukkamala: Distributed Dynamic Condition Re-
end
N

treatment
Afhængigheder mellem handlinger - ikke
+
give
N

medicine %
%
+ N
don't
trust
sponse Structures. PLACES 2010
4. Hildebrandt, Mukkamala and Slaats: Designing a Cross-organizational
%
eksplicit process-flow Case Management System using Dynamic Condition Response Graphs.
EDOC 2011
ork, DCR Graphs have been ex- 5. Hildebrandt, Mukkamala and Slaats: Safe Distribution of Declar-
nd support for model checking of ative Processes. SEFM Opfølgning (response)
14 Days
2011
6. Hildebrandt and Zanitti: A Process-oriented Event-based Pro-
perties in SPIN [9]. A first version
U Lo % Lo
gramming Language DEBS2012
LO

3 Days
s-oriented Event-based Program-
Open Propose Accept Hold meeting
7. Trustworthy pervasive healthcare processes (TrustCare) research
project. Funded by The Danish Council for Strategic Research (grant Slaats og afhandling
Ph.d-projekt, Tijs
case dates-LO + LO with DA

L) [6] based on DCR Graphs and
Betingelse 1 Day
%

g context-sensitive reactive services #2106-07-0019) http://www.trustcare.dk/ af Rao R. Mukkamala
(condition) 8. DA
1 Day
Mukkamala. A Formal Model For Declarative Workflows - Dy-
% DA
d prototyped. +
namic Condition Response Graphs. PhD thesis.
Update
Case
Propose Accept %
9. http://tinyurl.com/dcrveri
dates-DA DA (se www.itu.dk/people/rao og
www.trustcare.dk)

• Tillad dynamiske ændringer Trustworthy Pervasive Healthcare Services project

Dynamic Condition Response (DCR) Graphs
Cross-organizational Case Management
Guard-Stage-Milestone Paradigm, IBM Research, NY
UNIVERSITY
OF
COPENHAGEN


Table 7.2 - BPMN Extended Modeling Elements

Behavioral
Types
Merging BPMN uses the term :merge; to refer to the
exclusive combining of two or more paths into
one path (also known as an OR-Join).
A Merging Exclusive Gateway is used to show
the merging of multiple Sequence Flows (see
upper figure to the right).
If all the incoming flow is alternative, then a
Gateway is not needed. That is, uncontrolled
flow provides the same behavior (see lower
figure to the right).

Table 7.2 - BPMN Extended Modeling Elements

Merging BPMN uses the term :merge; to refer to the
SimpleTreatmentChoreorgraphy
exclusive combining of two or more paths into
one path (also known as an OR-Join).

•
A Merging Exclusive Gateway is used to show
the merging of multiple Sequence Flows (see
upper figure to the right).

Tværorganisatoriske/globale
If all the incoming flow is alternative, then a
Gateway is not needed. That is, uncontrolled
Looping flow provides the same behavior (seefor loop-
BPMN provides 2 (two) mechanisms lower
result1 prescription
ing within a Process.
figure to the right).
See Next Two Figures
Nurse Doctor
Activity Looping The attributes of Tasks and Sub-Processes
will determine if they are repeated or per-

processer kan beskrives som
formed once (see page 197). There are two
Test1 Prescribe
types of loops: Standard and Multi-Instance. A
small looping indicator will be displayed at the
bottom-center of the activity.

not ok
Patient Patient
Sequence Flow Looping Loops can be created by connecting a Doctor Nurse

koreografier
Sequence Flow to an :upstream; object. An ok
object is considered to be upstream if that
Looping BPMN provides 2 (two) mechanisms for loop-
object has an outgoing Sequence Flow that Discharge
ing within series of other Sequence Flows, result2
leads to a a Process.
the last of which is an incoming Sequence See Next Two Figures
Nurse
Activity Looping Flowattributes of Tasks and Sub-Processes
The for the original object.
will determine if they are repeated or per-
formed once (see page 197). There are two
Test2
types of loops: Standard and Multi-Instance. A
small looping indicator will be displayed at the
bottom-center of the activity.
Patient
Sequence Flow Looping Loops can be created by connecting a Doctor
Sequence Flow to an :upstream; object. An
object is considered to be upstream if that
object has an outgoing Sequence Flow that
leads to a series of other Sequence Flows,
Figure 1. Workflow as BPMN 2.0 Choreography

• Men hvordan sikres at de interne/
the last of which is an incoming Sequence
Flow for the original object.

corresponding Process Matrix spreadsheet. We then demonstrate in Sec. 2.2 how
38
the process matrix workflow processes can be described compactly in multiparty
Business Process Model and Notation, v2.0

session types with assertions and symmetric sum types. Finally we overview the
prototype implementation in Sec. 2.3.

lokale processer følger koreografien? 2.1 Example Workflow as Choreography and Process Matrix

A simple CPG workflow involving three participants is described in Fig. 1 as a

• Behavioral Types: Beskriver
38 Business Process Model and Notation, v2.0
Choreograpy diagram in the Business Process Modelling Notation (BPMN) 2.0.
The described workflow is activated, when a patient is admitted (indicated by the

Betty:
start event). Then two tests are executed in parallel by a nurse. Note that each
activity box is a communication between the three participants with one initiator

protokollen for hver lokal process EU COST Action
(indicated in the white ribbon) and two receivers (indicated in the shaded ribbons).
Thus, the test results are sent by the nurse to both the patient and the doctor.
Each test may be repeated, as indicated by the repeating subprocess arrow, e.g. if
the test failed or the result was not clear. Then, depending on the results of the

der typecheckes før de køres tests, either the patient is discharged directly, or the doctor prescribes a drug to the
patient, sending the prescription to both the patient and the nurse. The workflow
is ended when the patient is discharged. The described workflow is a standard
paradigm in CPGs; that is, first a set of tests are performed and, depending on the
www.itu.dk/research/models 18 results, either more tests are performed, the patient isOF
COPENHAGEN

IT
UNIVERSITY
discharged, or a treatment

is executed. In this workflow the treatment consists of simply prescribing a drug
to the patient.

1.1.1 name height weight bP
dose from physical objects, minimising the !amount and attendant risks hilde@itu.dk
Get F’IT, BPM if healthy then set(abnorm); Hildebrandt, of manual
Seminar, 25. September, 2012
1.1.2 cave ever birth healthy Thomas
typing. We have only superficially touched cave then set(abnorm);
if
if ! upon the set(cyto)
ever birth then technical and usability chal-

Brugerinddragelse
lenges of developing user cavetx healthtx clients for tablet computers in comparison to
1.1.3 interface
1.1.4 rp cytotec
conventional PC clients, gU ia stet c et p ia
1.1.5 however. if ! gU ia then set(abnorm2);
uterus retroflekteret if ! stet c et p ia then set(abnorm2)
1.1.6 sttx gutx
3 Citizen Development/Generativity: then set(abnorm3);
Experiment: An End-user Developed Workflow
1.1.7
1.1.8
fHR cRL gA
clamydiatested clamydia negative
if ! clamydiatested
Så nemt som at bruge et regneark...negative then set(abnorm3);
rhesus negative signed form A
if ! clamydia
under 18 gA under 12
if rhesus negative then set(abnorm3);
Id Name D N Sif AN OPNA Seqreset(1.1.8);
under 18 then set(abnorm3); Log
if ! signed form then
Condition
1.1.1 Nurse evaluation R W Rif ! R under 12 then reset(1.1.8)
gA R
1.1.2 Patient History anti samtykke form B R R
1.1.9 rp antibiotics rp
1.2.0 pt informeret
D signed
W R R
1.1.3 Extended historygA ved op R R R R
1.2.1 op tid W abnorm
1.1.4 Preoperative treatment End-user developed workflow (Data).
Figure 10.
W R R R R cyto
1.1.5 Objective W R R R R
1.1.6 Extended objective
3.1 The Experiment W R R R R abnorm2
1.1.7 The experiment, which took a singleR R R
Ultrasound W day, was set-up as follows: DFL had access to
R
1.1.8 a computer where the server, the code generator and example spreadsheets were
Formalia W R R R R
available. To simplify the interface, all spreadsheets were placed on the desktop
1.1.9 Extended commands performed theR R R R server start. To learn the
and batch formalia W code generation and abnorm3
1.2.0 Information DFL did a small exercise under R R by one of the authors. - 1.1.9
syntax, for the patient R W instruction R 1.1.1
The workflow chosen by DFL model how a healthy woman gets an abortion,
1.2.1 Scheduletofor OP “a simplification Wthe simplest workflow I could find”.
according DFL was R R of R W 1.2.0
The developed workflow is shown in Fig. 9 and Fig. 10. The roles are: Doctor
(D), Nurse (N), Secretary (S), Anaesthesiologist (AN) and operation nurse (OPN).
An example screenshot from thedeveloped workflow (Flow). 11.
Figure 9. End-user running Android client is shown in Fig.
2nd International Symposium on Foundations of Health Information Engineering and Systems, 2012
3.2 Evaluation
www.itu.dk/research/models
To test the Generally the experiment turned out very successfully: DFL was easily able UNIVERSITY
OF
with the

developed software, we performed a simple experiment COPENHAGEN

19 IT
to use
help of a physician: Dorthe build her own workflow. The instructing author only had to
the spreadsheets to
Furstrand Lauritzen (DFL). The motivation behind


Brugerinddragelse
– Letting a medical professional use the tool, tests the hypothesis: the domain
expert can implement simple workflows, leading to a simpler and more flexible
development process, e.g.
• The domain experts might be able to make simple changes directly without

Citizen Development/Generativity:
involving the development team.
• The domain experts can use simple workflows to communicate more di-
rectly and e ciently with the development team.
Så nemt som at bruge et regneark...
Id Input Action
1.1.1 name height weight bP
1.1.2 cave ever birth healthy if ! healthy then set(abnorm);
if cave then set(abnorm);
if ! ever birth then set(cyto)
1.1.3 cavetx healthtx
1.1.4 rp cytotec
1.1.5 gU ia stet c et p ia if ! gU ia then set(abnorm2);
uterus retroflekteret if ! stet c et p ia then set(abnorm2)
1.1.6 sttx gutx
1.1.7 fHR cRL gA
1.1.8 clamydiatested clamydia negative if ! clamydiatested then set(abnorm3);
rhesus negative signed form A if ! clamydia negative then set(abnorm3);
under 18 gA under 12 if rhesus negative then set(abnorm3);
if under 18 then set(abnorm3);
if ! signed form A then reset(1.1.8);
if ! gA under 12 then reset(1.1.8)
1.1.9 rp antibiotics rp anti D signed form B
1.2.0 pt informeret samtykke
1.2.1 op tid gA ved op

Figure 10. End-user developed workflow (Data).
www.itu.dk/research/models The Experiment
3.1 20 IT
UNIVERSITY
OF
COPENHAGEN

Tuesday, September 25, 12 The experiment, which took a single day, was set-up as follows: DFL had access to

s importantBPM Seminar, 25. September, 2012uses the same generic Android Hildebrandt, hilde@itu.dk
Get F’IT, to stress that every participant Thomas
The GUI manager uses the generated code to make sure that the Android

Brugerinddragelse
used by the Doctor presents only the local process corresponding to the
ow relevant to the doctor, and the Android client used by the Nurse presents
e local process relevant to the Nurse. An example screenshot of the Android
running the example as the nurse role is shown in Fig. 8. It shows the
Citizen Development/Generativity:
ow in a state where the nurse has performed the lung test with a negative
Så nemt som at bruge et regneark...
and still needs to perform the throat test.

Figure 8. Screenshot from Android client logged in as Nurse role.
UNIVERSITY
OF
COPENHAGEN

9


Konklusion(er)
• State-of-the-art tillader at beskrive procedurer som
brugere og forretningsfolk kan forstå
• I praksis bryder videnarbejderen ofte med den idéelle
procedure og processer ændres før de tages i brug...
• Ringe support for compliancetjek, brugerinddragelse,
deling & decentral udvikling af distribuerede processer
• Forskere og OMG arbejder på fremtidige standarder
og teknologier for case management modelling,
distribuerede processer og brugerinddragelse
UNIVERSITY
OF
COPENHAGEN



Konklusion(er)
Næste møde i videngruppe for digitalisering og
processorientering (VidenDanmark.dk)
•State-of-the-art tillader atBrugerinddragelse
24. oktober - tema: beskrive procedurer som
brugere og forretningsfolk kan forstå
Næste seminar i interessegruppen for Processer og IT
•I praksis bryder videnarbejderen ofte med den idéelle
(Inﬁnit.dk) 13. processer ændres før de tages i brug...
november - Usabilityudfordringer i
procedure og
offentlige digitaliseringsprocesser
•Ringe support for compliancetjek, brugerinddragelse,
deling & decentral se nogle af jer igen :-)
(håber at udvikling af distribuerede processer
• Forskere og OMG arbejder på fremtidige standarder
og teknologier for case management modelling,
distribuerede processer og brugerinddragelse
UNIVERSITY
OF
COPENHAGEN


Fra Office Automation via BPM til tvær-organisatorisk Case Management og Citizen Development af Thomas Hildebrandt, ITU

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (7)

En vedette

En vedette (20)

Similaire à Fra Office Automation via BPM til tvær-organisatorisk Case Management og Citizen Development af Thomas Hildebrandt, ITU

Similaire à Fra Office Automation via BPM til tvær-organisatorisk Case Management og Citizen Development af Thomas Hildebrandt, ITU (20)

Plus de InfinIT - Innovationsnetværket for it

Plus de InfinIT - Innovationsnetværket for it (20)

Dernier

Dernier (20)

Fra Office Automation via BPM til tvær-organisatorisk Case Management og Citizen Development af Thomas Hildebrandt, ITU