1 / 72

Workflow Management Systems : Functions, architecture, and products.

Eindhoven University of Technology Faculty of Technology Management Department of Information and Technology P.O. Box 513 5600 MB Eindhoven The Netherlands w.m.p.v.d.aalst@tm.tue.nl. Workflow Management Systems : Functions, architecture, and products. Wil van der Aalst. Outline.

ida
Download Presentation

Workflow Management Systems : Functions, architecture, and products.

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. Eindhoven University of Technology Faculty of Technology Management Department of Information and Technology P.O. Box 513 5600 MB Eindhoven The Netherlands w.m.p.v.d.aalst@tm.tue.nl Workflow Management Systems: Functions, architecture, and products. Wil van der Aalst

  2. Outline • Architecture • Staffware • Other systems: • Oracle BPEL • COSA • FLOWer • SAP workflow

  3. Focus on "classical" workflow management systems, but ... Four types of "workflow-like" systems: • Information systems with hard-coded workflows (process& organization specific). • Custom-made information systems with generic workflow support (organization specific). • Generic softwarewith embedded workflow functionality (e.g., the workflow components of ERP, CRM, PDM, etc. systems). • Generic softwarefocusing onworkflow functionality (e.g., Staffware, MQSeries Workflow, FLOWer, COSA, Oracle BPEL, Filenet, etc.).

  4. WfMC Reference model

  5. Interfaces Weak! Demo’s Published in Handbook

  6. Examples of systems • COSA (demo) • Staffware • FLOWer • …

  7. Staffware • Leading workflow management system (typically 25 percent of the global “pure” workflow market). • Staffware PLC is headquartered in Maidenhead UK and has offices in 19 countries. • Focus on performance and reliability rather than functionality (e.g., infinite scalability, fault tolerance, etc.) • In the remainder, we present a small case study that is used to: • introduce the design tool and modeling language of Staffware, • show the management/administrator tools of Staffware, • demonstrate the end-user’s view of Staffware, and • show the need for analysis.

  8. WfMC reference model (1) (2) (3)

  9. checkA pay register checkB reject A small case study: Double Check (DC) • Processing of insurance claims involving registration, two checks, and a payment of rejection • Five tasks: • register (register insurance claim) • checkA (check insurance policy) • checkB (check damage reported) • pay (pay for the damage) • reject (inform customer about rejection) • Registration is followed by two checks which can be handled in parallel. • Each of the checks results in “OK” or “not OK”. • If both are OK, pay otherwise reject. • Three roles: register (for task register), checks (for both checks), and pay/reject (for final tasks).

  10. Staffware: The designer’s view

  11. Building blocks start stop step (i.e., task) wait (i.e., AND-join) event step condition (i.e., XOR-split) complex router (OR-join/AND-split) automatic step

  12. Basic semantics of a step AND-split OR-join Same for complex routers, conditions (input: OR, output: each branch is AND), other types of steps, etc.

  13. Advanced semantics withdraw construct time-out construct

  14. Defining the process Double Check (DC)

  15. Adding a step

  16. Defining a step

  17. Defining a step (2)

  18. Defining forms and case variables

  19. Building a sequence

  20. Another step definition

  21. Another form definition

  22. Adding a set in parallel

  23. Another step definition

  24. Synchronizing two flows

  25. Another step definition

  26. Defining conditions

  27. The alternative route

  28. Another step definition

  29. Staffware: The manager/administrator’s view Monitoring and managing processes and cases Managing users/groups

  30. Managing users

  31. Managing groups

  32. Managing processes and cases

  33. Monitoring individual cases

  34. The end-user’s view

  35. Selecting and executing the first step

  36. Executing one of the two parallel steps

  37. Executing the other one

  38. Executing the final step

  39. Audit trail

  40. Analysis of Staffware processes 6 runs (8 sequences) are possible!

  41. Example audit trails One not OK Both OK

  42. Example audit trails (2) Both not OK (seq) Both not OK (par)

  43. Analysis using Woflan

  44. Improved process

  45. Possible scenario’s

  46. Analysis using Woflan

  47. Some more examples ...

  48. Four types of "workflow-like" systems: • Information systems with hard-coded workflows (process& organization specific). • Custom-made information systems with generic workflow support (organization specific). • Generic softwarewith embedded workflow functionality (e.g., the workflow components of ERP, CRM, PDM, etc. systems). • Generic softwarefocusing onworkflow functionality SAP Business Workflow/Webflow (SAP AG) FLOWer (Pallas Athena) Oracle BPEL (Oracle) Staffware (TIBCO) COSA (COSA GmbH)

  49. SAP Business Workflow/Webflow (SAP AG) Staffware (TIBCO) Oracle BPEL (Oracle) COSA (COSA GmbH) FLOWer (Pallas Athena)

More Related