Computer Supported Mobile Adaptive Business Processes for 3gERP - - PowerPoint PPT Presentation

computer supported mobile adaptive business processes for
SMART_READER_LITE
LIVE PREVIEW

Computer Supported Mobile Adaptive Business Processes for 3gERP - - PowerPoint PPT Presentation

Computer Supported Mobile Adaptive Business Processes for 3gERP Systems Thomas Hildebrandt Kjeld Schmidt * , Arne J. Glenstrup, Mikkel Bundgaard, Magnus Nilsson, Espen Hjsgaard, Tim Hallwyl, Tijs Slaats Programming, Logic and Semantics (PLS)


slide-1
SLIDE 1

Thomas Hildebrandt

Kjeld Schmidt*, Arne J. Glenstrup, Mikkel Bundgaard, Magnus Nilsson, Espen Højsgaard, Tim Hallwyl, Tijs Slaats Programming, Logic and Semantics (PLS) & Design and Organization of IT (DOIT) IT University of Copenhagen

*Department of Organization, CBS

3gERP workshop - Microsoft Dynamics Academic Alliance Copenhagen Business School, November 18th, 2008

Computer Supported Mobile Adaptive Business Processes for 3gERP Systems

slide-2
SLIDE 2

Road Map

Motivation and requirements for mobile ERP The CosmoBiz research project

Microsoft Dynamics Mobile Framework & Development Tools Extensible and Higher-order Business Process Languages

Conclusions and Future work

2

slide-3
SLIDE 3

Motivation and requirements

3

slide-4
SLIDE 4

Motivation and requirements

Give mobile workers access to ERP systems

3

slide-5
SLIDE 5

Motivation and requirements

Give mobile workers access to ERP systems Salesmen, Homecare, Healthcare, construction work

3

slide-6
SLIDE 6

Motivation and requirements

Give mobile workers access to ERP systems Salesmen, Homecare, Healthcare, construction work Must allow for disconnected operation

3

slide-7
SLIDE 7

Motivation and requirements

Give mobile workers access to ERP systems Salesmen, Homecare, Healthcare, construction work Must allow for disconnected operation Can not move entire ERP system to the PDA

3

slide-8
SLIDE 8

Motivation and requirements

Give mobile workers access to ERP systems Salesmen, Homecare, Healthcare, construction work Must allow for disconnected operation Can not move entire ERP system to the PDA Focused & specific tasks => role-based & task-driven

3

slide-9
SLIDE 9

Motivation and requirements

Give mobile workers access to ERP systems Salesmen, Homecare, Healthcare, construction work Must allow for disconnected operation Can not move entire ERP system to the PDA Focused & specific tasks => role-based & task-driven Must be flexible and (re)configurable

3

slide-10
SLIDE 10

Supporting specific and focussed tasks: From Data to Process-oriented

4

ERP back-end Clients (role based access control) Todays ERP

slide-11
SLIDE 11

Supporting specific and focussed tasks: From Data to Process-oriented

5

ERP back-end Clients: role based access and task-driven (process-oriented) Tomorrows ERP

slide-12
SLIDE 12

Supporting specific and focussed tasks: From Data to Process-oriented

6

ERP back-end Clients: role based access and task-driven (process-oriented) Mobile ERP

slide-13
SLIDE 13

Supporting specific and focussed tasks: From Data to Process-oriented

6

ERP back-end Clients: role based access and task-driven (process-oriented) Mobile ERP

slide-14
SLIDE 14

Supporting specific and focussed tasks: From Data to Process-oriented

6

ERP back-end Clients: role based access and task-driven (process-oriented) Mobile ERP

?

Disconnected operation

slide-15
SLIDE 15

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation

slide-16
SLIDE 16

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation

slide-17
SLIDE 17

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation Deploy processes (tasks) on mobile client

slide-18
SLIDE 18

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation Deploy processes (tasks) on mobile client Replicate relevant data

slide-19
SLIDE 19

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation Deploy processes (tasks) on mobile client Replicate relevant data

slide-20
SLIDE 20

Microsoft Dynamics Mobile Development Tools (June 2007)

7

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Disconnected task-driven operation Deploy processes (tasks) on mobile client Replicate relevant data

slide-21
SLIDE 21

Tasklet Orchestration

<userRole xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Flow"> <orchestrations> <orchestration text="Customer detail"> <tasklets> <tasklet name="CustomerDetailTasklet"> <actions> <open text="Contact" tasklet="CustomerContactDetailTasklet"> </open> <open text="Credit Limit" tasklet="CustomerCreditLimitDetailTasklet"> </open> </actions> </tasklet> <tasklet name="CustomerContactDetailTasklet"> </tasklet> <tasklet name="CustomerCreditLimitDetailTasklet"> </tasklet> </tasklets> </orchestration> <orchestration text="New Customer"> ... <!-- Contact Details --> <tasklet name="ContactDetails" text="Contact Details" type="CustomerContactDetailTasklet.CustomerContactDetailTasklet, CustomerContactDetailTasklet"> <actions> <previous priority="1" text="Previous"> </previous> <exitOrchestration text="Finish"/> </actions> </tasklet> </tasklets>

</orchestration>

</orchestrations> </userRole>

8

slide-22
SLIDE 22

9

http://msdn.microsoft.com/en-us/library/cc160851.aspx

Asynchronous requests back to ERP system

slide-23
SLIDE 23

Achievements & Challenges

XML orchestrations of tasklets allow easy customization by 3rd party developers Processes and data separate... Still some gluing and C# coding need to be done

10

slide-24
SLIDE 24

Computer Supported Mobile Adaptive Business Processes (CosmoBiz)

Research Project funded by the Danish Research Agency (2007- 2011)

Aim: Extensible business process languages and execution architecture for mobile & adaptive ERP Partners: IT University of Copenhagen (ITU) & Mobile Applications Group at Microsoft Development Center Copenhagen (MDCC) Approach:

Research in Computer Supported Cooperative Work (field studies) Research in Design of Domain Specific Languages (formal models) Software Development (Mobile applications group, MDCC)

11

slide-25
SLIDE 25

CosmoBiz research so far and in the near future

eXtensible Formalization of Business Process Execution (bigraphs) Higher-order mobile embedded Business Process Execution Language (HomeBPEL) Extensible Process Execution Engine Field studies & Domain specific process languages

12 [MTCOORD’05,COORDINATION’06] [COORDINATION’08]

slide-26
SLIDE 26

Higher-order Mobile Embedded Processes?

Higher-order: Business process management processes as business processes (e.g. deployment, adaption delegation) Mobile embedded: Support disconnected operation by moving sub processes

13 mobile sales ERP-proxy mobile client deployment service ERP back-end

slide-27
SLIDE 27

Higher-order Mobile Embedded Processes?

Higher-order: Business process management processes as business processes (e.g. deployment, adaption delegation) Mobile embedded: Support disconnected operation by moving sub processes

13 mobile sales ERP-proxy mobile client deployment service ERP back-end mobile sales

slide-28
SLIDE 28

Higher-order Mobile Embedded Processes?

Higher-order: Business process management processes as business processes (e.g. deployment, adaption delegation) Mobile embedded: Support disconnected operation by moving sub processes

13 mobile sales ERP-proxy mobile client deployment service ERP back-end mobile sales

slide-29
SLIDE 29

Higher-order Mobile Embedded Processes?

Higher-order: Business process management processes as business processes (e.g. deployment, adaption delegation) Mobile embedded: Support disconnected operation by moving sub processes

13 mobile sales ERP-proxy mobile client deployment service ERP-proxy ERP back-end mobile sales

slide-30
SLIDE 30

Extensible Formalization and HomeBPEL - a few details

14

slide-31
SLIDE 31

Business process execution today

Workflow Engine(s) Process Definition Tools Other Workflow Engines Workflow Client Applications Invoked Applications (e.g. Webservices) Administration and Analysis Tools

slide-32
SLIDE 32

Business process execution today

Workflow Engine(s) Process Definition Tools Other Workflow Engines Workflow Client Applications Invoked Applications (e.g. Webservices) Administration and Analysis Tools

slide-33
SLIDE 33

Business process execution today

<?xml version="1.0" ?> <process name="salesman" xmlns="http://schemas.xmlsoap.org/ws/2004/03/business-process/" xmlns:sales="..." xmlns:xsd="..."> <documentation> A very small example of a BPEL process </documentation> <partnerLinks> ... </partnerLinks> <variables> <variable name="price" type="xsd:int"/> <variable name="customerid" type="xsd:string"/> <variable name="salesmanid" type="xsd:string"/> <variable name="record" type="sales:record"/> </variables> <sequence> <receive partnerLink="..."" portType="..."

  • peration="login" variable="salesmanid"/>

<receive partnerLink="..."" portType="..."

  • peration="customer" variable="customerid"/>

<invoke partnerLink="..." portType="..."

  • peration="checkrecord" inputVariable="customerid"
  • uputVariable="record"/>

<!-- calculate price --> <reply partnerLink="..." portType="..."

  • peration="customer" variable="price"/>

</sequence> </process>

Workflow Engine(s) Process Definition Tools Other Workflow Engines Workflow Client Applications Invoked Applications (e.g. Webservices) Administration and Analysis Tools

compilation

slide-34
SLIDE 34

Business process execution today

<?xml version="1.0" ?> <process name="salesman" xmlns="http://schemas.xmlsoap.org/ws/2004/03/business-process/" xmlns:sales="..." xmlns:xsd="..."> <documentation> A very small example of a BPEL process </documentation> <partnerLinks> ... </partnerLinks> <variables> <variable name="price" type="xsd:int"/> <variable name="customerid" type="xsd:string"/> <variable name="salesmanid" type="xsd:string"/> <variable name="record" type="sales:record"/> </variables> <sequence> <receive partnerLink="..."" portType="..."

  • peration="login" variable="salesmanid"/>

<receive partnerLink="..."" portType="..."

  • peration="customer" variable="customerid"/>

<invoke partnerLink="..." portType="..."

  • peration="checkrecord" inputVariable="customerid"
  • uputVariable="record"/>

<!-- calculate price --> <reply partnerLink="..." portType="..."

  • peration="customer" variable="price"/>

</sequence> </process>

Workflow Engine(s) Process Definition Tools Other Workflow Engines Workflow Client Applications Invoked Applications (e.g. Webservices) Administration and Analysis Tools

slide-35
SLIDE 35

Business process execution today

<?xml version="1.0" ?> <process name="salesman" xmlns="http://schemas.xmlsoap.org/ws/2004/03/business-process/" xmlns:sales="..." xmlns:xsd="..."> <documentation> A very small example of a BPEL process </documentation> <partnerLinks> ... </partnerLinks> <variables> <variable name="price" type="xsd:int"/> <variable name="customerid" type="xsd:string"/> <variable name="salesmanid" type="xsd:string"/> <variable name="record" type="sales:record"/> </variables> <sequence> <receive partnerLink="..."" portType="..."

  • peration="login" variable="salesmanid"/>

<receive partnerLink="..."" portType="..."

  • peration="customer" variable="customerid"/>

<invoke partnerLink="..." portType="..."

  • peration="checkrecord" inputVariable="customerid"
  • uputVariable="record"/>

<!-- calculate price --> <reply partnerLink="..." portType="..."

  • peration="customer" variable="price"/>

</sequence> </process>

Workflow Engine(s) Process Definition Tools Other Workflow Engines Workflow Client Applications Invoked Applications (e.g. Webservices) Administration and Analysis Tools

Execution semantics of BPEL hidden (and fixed) in engine

slide-36
SLIDE 36

Extensible Formalization and Execution Engine

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-37
SLIDE 37

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-38
SLIDE 38

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-39
SLIDE 39

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-40
SLIDE 40

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

  • Bonus: Native XML

Execution format - easy to persist, distribute and move

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-41
SLIDE 41

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

  • Bonus: Native XML

Execution format - easy to persist, distribute and move

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-42
SLIDE 42

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

  • Bonus: Native XML

Execution format - easy to persist, distribute and move

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-43
SLIDE 43

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

  • Bonus: Native XML

Execution format - easy to persist, distribute and move

Engine

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-44
SLIDE 44

Extensible Formalization and Execution Engine

  • Describe Process Language

with XML Schema

  • Describe Semantics of

Process Language by XML rewrite rules

  • Parametrize Engine with

Schema and rewrite rule

  • Bonus: Native XML

Execution format - easy to persist, distribute and move

Engine

  • Milners Bigraphical Reactive

Systems are an ideal metamodel for formalizing XML rewriting

[MTCOORD’05,COORDINATION’06]

Rewrite rules

slide-45
SLIDE 45

XML rewriting example

Engine

<?xml version="1.0" ?> <instance name="transfer"> <variables> <variable name="accountA"> 42 </variable> <variable name="accountB"> <variable name="accountC"> </variables> <sequence> <assign> <copy> <from var="accountA"/> <to var="accountB"/> </copy> </assign> <next> <assign> <copy> <from var="accountB"/> <to var="accountC"/> </copy> </assign> </next> </sequence> </instance>

slide-46
SLIDE 46

XML rewriting example

Engine

<?xml version="1.0" ?> <instance name="transfer"> <variables> <variable name="accountA"> 42 </variable> <variable name="accountB"> <variable name="accountC"> </variables> <sequence> <assign> <copy> <from var="accountA"/> <to var="accountB"/> </copy> </assign> <next> <assign> <copy> <from var="accountB"/> <to var="accountC"/> </copy> </assign> </next> </sequence> </instance>

<?xml version="1.0" ?> <process name="transfer"> <variables> <variable name="accountA"> 42 </variable> <variable name="accountB"> 42 </variable> <variable name="accountC"/> </variables> <sequence> <empty/> <assign> <copy> <from var="accountB"/> <to var="accountC"/> </copy> </assign> </sequence> </process>

slide-47
SLIDE 47

XML rewriting example

Engine

<?xml version="1.0" ?> <process name="transfer"> <variables> <variable name="accountA"> 42 </variable> <variable name="accountB"> 42 </variable> <variable name="accountC"/> </variables> <sequence> <empty/> <assign> <copy> <from var="accountB"/> <to var="accountC"/> </copy> </assign> </sequence> </process>

assign variables copy variable variable from to accountA accountB sequence P P1 P2 P3 instance transfer

slide-48
SLIDE 48

XML rewriting example

Engine

assign variables copy variable variable from to accountA accountB sequence P P1 P2 P3 instance transfer variables variable variable accountA accountB sequence P P1 P3 instance transfer P1

slide-49
SLIDE 49

Bigraph rewriting

Engine

assign variables copy variable variable from to accountA accountB sequence P P1 P2 P3 instance transfer variables variable variable accountA accountB sequence P P1 P3 instance transfer P1

slide-50
SLIDE 50

Tasklet orchestration revisited

  • implemented prototype

tasklet orchestration language

  • extended with BPEL- like

conditional control flow

<tasklet assembly ="IOTasklet" name="IOTasklet" type="MD"> <input type="constant" name="ToShow" value="How much is 19*16"/> </tasklet> <if> <condition>19*16 &lt; [Result]</condition> <tasklet assembly ="IOTasklet" name="IOTasklet" type="MD"> <input type="constant" name="ToShow" value="Isn't that a bit much?"/> </tasklet> <elseif> <condition>19*16 > [Result]</condition> <tasklet assembly ="IOTasklet" name="IOTasklet" type="MD"> <input type="constant" name="ToShow" value="That's a bit low!"/>

</tasklet>

</elseif> <else> <sequence> <sequence> <tasklet assembly ="IOTasklet" name="IOTasklet" type="MD"> <!--Tasklet1View--> <input type="constant" name="ToShow" value="Correct!"/> </tasklet> </sequence> <sequence> </sequence> </sequence> </else> </if>

slide-51
SLIDE 51

HomeBPEL Extensions

</subLinks> <variables> <variable name="treatment_template"> <process name="treatment_template">...</process> </variable> <variable name="x" /> <variable name="y"><from>true()</from></variable> </variables> <sequence>

<thaw subLink="treatment" variable="treatment_template" /> <invokeSub subLink="treatment" operation="consultation" inputVariable="y" outputVariable="y" /> <freeze subLink="treatment" variable="x" /> <invoke partnerLink="patient" operation="run" inputVariable="x" outputVariable="y" /> </sequence>

19 [COORDINATION’08]

slide-52
SLIDE 52

HomeBPEL Extensions

</subLinks> <variables> <variable name="treatment_template"> <process name="treatment_template">...</process> </variable> <variable name="x" /> <variable name="y"><from>true()</from></variable> </variables> <sequence>

<thaw subLink="treatment" variable="treatment_template" /> <invokeSub subLink="treatment" operation="consultation" inputVariable="y" outputVariable="y" /> <freeze subLink="treatment" variable="x" /> <invoke partnerLink="patient" operation="run" inputVariable="x" outputVariable="y" /> </sequence>

Allow process descriptions as values

19 [COORDINATION’08]

slide-53
SLIDE 53

HomeBPEL Extensions

</subLinks> <variables> <variable name="treatment_template"> <process name="treatment_template">...</process> </variable> <variable name="x" /> <variable name="y"><from>true()</from></variable> </variables> <sequence>

<thaw subLink="treatment" variable="treatment_template" /> <invokeSub subLink="treatment" operation="consultation" inputVariable="y" outputVariable="y" /> <freeze subLink="treatment" variable="x" /> <invoke partnerLink="patient" operation="run" inputVariable="x" outputVariable="y" /> </sequence>

Allow process descriptions as values Allow for thawing a process as a subprocess and invoke services inside it

19 [COORDINATION’08]

slide-54
SLIDE 54

HomeBPEL Extensions

</subLinks> <variables> <variable name="treatment_template"> <process name="treatment_template">...</process> </variable> <variable name="x" /> <variable name="y"><from>true()</from></variable> </variables> <sequence>

<thaw subLink="treatment" variable="treatment_template" /> <invokeSub subLink="treatment" operation="consultation" inputVariable="y" outputVariable="y" /> <freeze subLink="treatment" variable="x" /> <invoke partnerLink="patient" operation="run" inputVariable="x" outputVariable="y" /> </sequence>

Allow process descriptions as values Allow for thawing a process as a subprocess and invoke services inside it Allow subprocesses to be dynamically frozen

19 [COORDINATION’08]

slide-55
SLIDE 55

HomeBPEL Extensions

</subLinks> <variables> <variable name="treatment_template"> <process name="treatment_template">...</process> </variable> <variable name="x" /> <variable name="y"><from>true()</from></variable> </variables> <sequence>

<thaw subLink="treatment" variable="treatment_template" /> <invokeSub subLink="treatment" operation="consultation" inputVariable="y" outputVariable="y" /> <freeze subLink="treatment" variable="x" /> <invoke partnerLink="patient" operation="run" inputVariable="x" outputVariable="y" /> </sequence>

Allow process descriptions as values Allow for thawing a process as a subprocess and invoke services inside it Allow subprocesses to be dynamically frozen Allow for sending processes

19 [COORDINATION’08]

slide-56
SLIDE 56

Conclusions

Process-oriented architecture supports customizable task-driven ERP access Light-weight orchestration on PDA allows disconnected operation XML rewriting/bigraphical reactive systems allows extensible languages, engines and formalizations Higher-order Business Process Language allows to describe process management as business process

20

slide-57
SLIDE 57

Conclusions

Process-oriented architecture supports customizable task-driven ERP access Light-weight orchestration on PDA allows disconnected operation XML rewriting/bigraphical reactive systems allows extensible languages, engines and formalizations Higher-order Business Process Language allows to describe process management as business process

20

Processes as data !

slide-58
SLIDE 58

Ward Pharmacy

flowchart flowchart Work sheed Patient

+

Doctor

+

pharmacist

+

pharmacist assistent Work sheed flowchart

+

Pharmacist

+

Nurse flowchart

  • Pt. A
drug X

+

  • Pt. A
drug X

+

  • Pt. A
drug X

+

Patient

+

Nurse/ doctor

!"#"$%&'()% *+$,-$%-( .%"$+/",+ 0%)+)&)123045

  • 1
13 7 3 17 30 Activity Activity Activity Activity Activity Activity O O O O O O O O O O O O O

6)78'+# 9( &%)##"# :1);< &'$%+ General Guidelines General Guidelines =)&$1 0%$&+>&" 47>-"1>,"

session Dosage session session session D sign P sign N sign Lab res. N adm

Future work

21

slide-59
SLIDE 59

Ward Pharmacy

flowchart flowchart Work sheed Patient

+

Doctor

+

pharmacist

+

pharmacist assistent Work sheed flowchart

+

Pharmacist

+

Nurse flowchart

  • Pt. A
drug X

+

  • Pt. A
drug X

+

  • Pt. A
drug X

+

Patient

+

Nurse/ doctor

!"#"$%&'()% *+$,-$%-( .%"$+/",+ 0%)+)&)123045

  • 1
13 7 3 17 30 Activity Activity Activity Activity Activity Activity O O O O O O O O O O O O O

6)78'+# 9( &%)##"# :1);< &'$%+ General Guidelines General Guidelines =)&$1 0%$&+>&" 47>-"1>,"

session Dosage session session session D sign P sign N sign Lab res. N adm

Future work

Field studies of mobile work processes and coordination

21

slide-60
SLIDE 60

Ward Pharmacy

flowchart flowchart Work sheed Patient

+

Doctor

+

pharmacist

+

pharmacist assistent Work sheed flowchart

+

Pharmacist

+

Nurse flowchart

  • Pt. A
drug X

+

  • Pt. A
drug X

+

  • Pt. A
drug X

+

Patient

+

Nurse/ doctor

!"#"$%&'()% *+$,-$%-( .%"$+/",+ 0%)+)&)123045

  • 1
13 7 3 17 30 Activity Activity Activity Activity Activity Activity O O O O O O O O O O O O O

6)78'+# 9( &%)##"# :1);< &'$%+ General Guidelines General Guidelines =)&$1 0%$&+>&" 47>-"1>,"

session Dosage session session session D sign P sign N sign Lab res. N adm

Future work

Field studies of mobile work processes and coordination BPEL-like process languages not really flexible...

21

slide-61
SLIDE 61

Ward Pharmacy

flowchart flowchart Work sheed Patient

+

Doctor

+

pharmacist

+

pharmacist assistent Work sheed flowchart

+

Pharmacist

+

Nurse flowchart

  • Pt. A
drug X

+

  • Pt. A
drug X

+

  • Pt. A
drug X

+

Patient

+

Nurse/ doctor

!"#"$%&'()% *+$,-$%-( .%"$+/",+ 0%)+)&)123045

  • 1
13 7 3 17 30 Activity Activity Activity Activity Activity Activity O O O O O O O O O O O O O

6)78'+# 9( &%)##"# :1);< &'$%+ General Guidelines General Guidelines =)&$1 0%$&+>&" 47>-"1>,"

session Dosage session session session D sign P sign N sign Lab res. N adm

Future work

Field studies of mobile work processes and coordination BPEL-like process languages not really flexible... Domain specific and declarative process languages

21

slide-62
SLIDE 62

Ward Pharmacy

flowchart flowchart Work sheed Patient

+

Doctor

+

pharmacist

+

pharmacist assistent Work sheed flowchart

+

Pharmacist

+

Nurse flowchart

  • Pt. A
drug X

+

  • Pt. A
drug X

+

  • Pt. A
drug X

+

Patient

+

Nurse/ doctor

!"#"$%&'()% *+$,-$%-( .%"$+/",+ 0%)+)&)123045

  • 1
13 7 3 17 30 Activity Activity Activity Activity Activity Activity O O O O O O O O O O O O O

6)78'+# 9( &%)##"# :1);< &'$%+ General Guidelines General Guidelines =)&$1 0%$&+>&" 47>-"1>,"

session Dosage session session session D sign P sign N sign Lab res. N adm

Future work

Field studies of mobile work processes and coordination BPEL-like process languages not really flexible... Domain specific and declarative process languages Types for secure higher-order processes and process interaction

21

slide-63
SLIDE 63

Future work

Field studies of mobile work processes and coordination BPEL-like process languages not really flexible... Domain specific and declarative process languages Types for secure higher-order processes and process interaction

21

Thank you for your attention! www.cosmobiz.org & www.trustcare.eu