CSS 496 Business Process Re-engineering for BS(CS)

1. CSS 496 Business Process Re-engineering for BS(CS) Chapter 2: Workflow Management Khurram Shahzad mks@ciitlahore.edu.pk Based on Petia, Marlon, Aalst and Weske Lectures

2. Workflow Management • The important achievement of workflow management is explicit representation of process structures in process models and controlled enactment of business processes according to these models • The goal of workflow is to manage the flow of work so that right work is performed by right person at right time

3. Workflow Management • Workflow is the automation of a business process, in whole or part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules

4. Workflow Management A workflow management system (WFMS) is a software package that can be used to support the definition, management and execution of workflow processes A workflow management system is a software systems that defines, creates, and manages the execution of workflows through the use of software, running one or more workflow engines, which is able to interpret the process definition, interact with workflow participants, and, where required, invoke the use of IT tools and applications

5. Informal Workflow

6. Business Process Management • “True Business Process Management is an amalgam of traditional workflow and the 'new' BPM technology. It then follows that as BPM is a natural extension of – and not a separate technology to – Workflow, BPM is in fact the merging of process technology covering 3 process categories: interactions between (i) people-to-people; (ii) systems-to-systems and (iii) systems-to-people – all from a process-centric perspective. This is what true BPM is all about.” Jon Pyke, CTO Staffware.

7. WFMS, EAI, BPMS

8. Enterprise Systems Architectures

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. DC Example

11. DC Example • Adding a step

12. DC example

13. DC Example

14. DC Example

15. DC Example

16. DC Example

17. DC Example

18. DC Example

19. DC Example

20. DC Example • The manager’s view Monitoring and managing processes and cases Managing users/groups

21. DC Example

22. Audit Trail

23. Event Driven Process Chains (ARIS/SAP)

24. Complex Process

25. Classification of Workflows • System Workflows • A system workflow consists of activities that are implemented by software systems without any user involvement • Human Interaction Workflows • Workflows in which humans are actively involved and interact with information systems are called human interaction workflows

26. Classification of Workflows • System Workflows • A system workflow consists of activities that are implemented by software systems without any user involvement • Human Interaction Workflows • Workflows in which humans are actively involved and interact with information systems are called human interaction workflows