1 / 31

Enhancing Workflow Management System with Planning Tools Using Colored Petri Nets

This research study explores augmenting a workflow management system with planning facilities using Colored Petri Nets. The main motivation behind this enhancement is to address inefficient resource utilization in the hospital domain and to support planned work in current workflow management systems. The approach involves integrating planning and monitoring functionalities into the workflow language. A conceptual model, developed using CPN Tools, includes features such as communicating work items, rescheduling appointments, and routing cases. The implementation phase required three months of work and resulted in the addition of 8000 lines of code to the system. Experiments conducted revealed a more complete design with improved abstraction from implementation details. Future work includes the evaluation of alternative planning approaches and component replacement in the CPN model.

javan
Télécharger la présentation

Enhancing Workflow Management System with Planning Tools Using Colored Petri Nets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Augmenting a Workflow Management System with Planning Facilities using Colored Petri Nets Ronny Mans TU/e, AMC Nick RussellTU/e Wil van der Aalst TU/e Arnold Moleman AMC Piet Bakker AMC

  2. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  3. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  4. Motivation • Workflow management systems: • workitems are offered via a worklist • Performed at an arbitrary point in time when a resource becomes available.

  5. Motivation • Hospital domain (doctors view). • Many appointments: • Patients • Staff meetings • … • Reason: • Expensive resource • Limited availability

  6. Motivation • Problem: people are used to work in a planned way which is not supported by current workflow management systems • Patient preferences • How to extend Workflow Management Systems • with planning facilities?

  7. Motivation • Rescheduling • Unused blocks in agenda • Inefficient use of resources • Monitoring • Limited time left for finishing tasks • Extension of WfMS with monitoring facilities to avoid rescheduling

  8. Research Question How to add planning and monitoring facilities to WfMS? Integration

  9. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  10. Approach WF language augmented with planning functionality • Understand problem domain • Experimentation • rapid prototyping

  11. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  12. Workflow language (WF-net) Flow tasks Schedule tasks

  13. Workflow language (WF-net) • Duration • Roles • Involvement of patient

  14. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  15. Conceptual model • Developed using • CPN Tools • 27 pages • 169 places • 377 transitions • 950 lines ML code 3 months of man-work (one person)

  16. Conceptual model

  17. Conceptual model • Communicating workitems • Worktray • Agenda • Manipulation of appointments • reschedule • reassign • reschedule to specific time • Planning problem • (re)scheduling of appointments • generate warning(s) • Routing of cases • Execution of tasks • Offering workitems

  18. Graph (Planning problem)

  19. Conceptual model

  20. Planning problem • (Re)schedule tasks • Warnings Cancellation of a case Appointments for resource

  21. Receive planning problem [no other planning problem] Conversion • Determine first sched tasks need to be (re)scheduled • If (re)sched then calc earliest time • Determine relevant info for tasks to be (re)scheduled • Determine first sched tasks whether warning is needed

  22. [all schedule tasks for case are scheduled andalso succeeding sched tasks need to be (re)scheduled] • Determine sched tasks to be (re)scheduled • If (re)sched then calc earliest time • Determine relevant info for tasks to be (re)scheduled • Automatic (re)scheduling • Find first opportunity for • One resource specified for each role • Patient • If found, book appointment • [no sched tasks need to be (re)scheduled] • Remove planning problem

  23. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  24. Implementation • 3 months of man-work • (one person) • 8000 lines of code

  25. Implementation

  26. Implementation Rescheduling of MRI Appointment needed

  27. Implementation

  28. Overview • Motivation • Approach • Workflow language • Conceptual model • Implementation • Experiences and conclusions

  29. Experiences and conclusions • Design and implementation of wf system offering planning and monitoring facilities • Workflow language • Conceptual model (CPNs) • Experimentation • More complete design • Abstraction from implementation details/language specific issues • Implementation

  30. Future work • “Replace” components in the CPN model by its concrete implementation • Evaluate alternative planning approaches using various performance indicators

  31. Questions???

More Related