BPM tools


Published on

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

BPM tools

  1. 1. Business Process Management Tools Understand your processes and choose the appropriate TOOLS DOOR Ing. R.H.W. Claassens MIM VOOR Interpolis 23 augustus 2004
  2. 2. Outline <ul><li>B usiness P rocess M anagement </li></ul><ul><li>H uman 2 H uman BPM </li></ul><ul><li>S ystem 2 s ystem BPM </li></ul><ul><li>B usiness 2 B usiness BPM </li></ul>
  3. 3. Business Process Management <ul><li>Definition from a Business Viewpoint </li></ul><ul><ul><li>Business process management is the concept of continuously defining, analyzing, and improving a business process. </li></ul></ul>defining analyzing <ul><li>Improving </li></ul><ul><li>More effective </li></ul><ul><li>More efficient </li></ul><ul><li>(faster, cheaper) </li></ul><ul><li>More flexible </li></ul><ul><li>More satisfying </li></ul>
  4. 4. Business Process <ul><li>Definitions from a Business Viewpoint </li></ul><ul><li>business process is a recipe for achieving a commercial result. Each business process has inputs, method and outputs. The inputs are a pre-requisite that must be in place before the method can be put into practice. When the method is applied to the inputs then certain outputs will be created. </li></ul><ul><li>A business process is a collection of related structural activities that produce a specific outcome for a particular customer. </li></ul><ul><li>A business process can be part of a larger, encompassing process and can include other business processes that have to be included in its method. </li></ul><ul><li>The business process can be thought of as a cookbook for running a business ; &quot;Answer the phone&quot;, &quot;place an order&quot;, &quot;produce and invoice&quot; might all be examples of a Business Process. </li></ul>
  5. 5. BPM “ BPM is the general term for the services and tools that support explicit process management (such as process analysis, definition, execution, monitoring and administration), including support for human and application-level interaction.” ( Gartner, 2003) “ Supporting business processes using methods, techniques, and software to design, enact, control, and analyze operational processes involving humans, organizations, applications, documents and other sources of information.” (W.M.P. van der Aalst , A. H.M. ter Hofstede , M. Weske, 2003) “ BPM is not a new discussion, but rather a fundamental shift in the availability of integrated tools by which to enable many of the BPM concepts that have been heretofore nothing but pages in a textbook.&quot; (Delphi, 2001)
  6. 6. Modeling Results: Company A: Reduced underwriting cycle from 10 days to two hours while reducing processing costs by 40 percent in less than three months. Company B: Reduced training costs/time of service representatives by producing automated documentation in three weeks. Government: Reduced time to construct buildings by three months and raised the effectiveness of building inspectors. Risks of Not Understanding Processes: Company X: Wasted $100 million in building a customer service workbench by not simulating throughput times of service calls. Company Y: Sustained several days of systems’ downtime by not understanding the complete effects of a new compound flow. Your Company: How much time and money is wasted in your processes? To Manage Business Flows, or Not ?? Copyright © 2002
  7. 7. A Process <ul><li>IDEF0/ICOM-diagram </li></ul>transformed or consumed to produce outputs specify conditions to produce correct means that support execution Inputs outputs controls mechanisms Data or object Produced
  8. 8. A Process Place Transition Place Petrinets Petrinets <ul><li>IDEF0/ICOM-diagram versus Petrinets </li></ul>Inputs outputs controls mechanisms Semi-formal: Abstraction of the real world Formal: A further Abstraction of the real world specify conditions to produce correct data or object produced transformed or consumed to produce outputs means that support execution
  9. 9. Business process expert or end user Business process modeling expert S5 P12 P13 P14 P15 P16 P17 t12 t13 t14 t15 t16 t17 t18 O2 P19 t' t&quot; p&quot; A formal Process model : Petrinet <ul><li>The model (& tool) supply: </li></ul><ul><li>Validation and Verification </li></ul><ul><ul><li>Deadlock detection </li></ul></ul><ul><ul><li>Starvation detection </li></ul></ul><ul><ul><li>Validation of test sets </li></ul></ul><ul><li>Analyses en simulation </li></ul><ul><ul><li>Stepwise process simulation </li></ul></ul><ul><ul><li>Critical path analysis </li></ul></ul><ul><ul><li>Process cost analysis </li></ul></ul><ul><ul><li>Completion time analyses </li></ul></ul><ul><ul><li>Quantitative stochastic simulation </li></ul></ul><ul><ul><li>Analyses of resource utilization </li></ul></ul><ul><li>The model is: </li></ul><ul><li>Hard to read and understand </li></ul><ul><li>There are no relations with the </li></ul><ul><ul><li>Organizational structure </li></ul></ul><ul><ul><li>Physical locations </li></ul></ul><ul><ul><li>The data flows </li></ul></ul><ul><ul><li>The information systems </li></ul></ul><ul><ul><li>The business rules </li></ul></ul>
  10. 10. Sales department Shipment planning department Order planning department Should (also) help the client to better understand his process Business Process Analyses tools
  11. 11. Business process models <ul><li>Can become large, and hard to manage </li></ul><ul><ul><li>Business Process Analyses tools might be necessary </li></ul></ul>
  12. 12. Outline <ul><li>B usiness P rocess M anagement </li></ul><ul><li>H uman 2 H uman BPM </li></ul><ul><li>S ystem 2 s ystem BPM </li></ul><ul><li>B usiness 2 B usiness BPM </li></ul>
  13. 13. A Process <ul><li>An ordinary activity in an administrative environment </li></ul>Inputs outputs controls mechanisms Human resource software application ------ ------ Human readable Physical document Machine readable storage Input = = Output Controls=Human/machine dialogue
  14. 14. A Process Human resource software application Human resource software application Human resource software application Human resource software application ------ ------ Physical Transport ------ ------ Physical Transport ------ ------ Physical Transport ------ ------ Physical Transport Physical Transport <ul><li>An ordinary process in an administrative environment </li></ul>
  15. 15. Process improvement <ul><li>Document imaging and document routing </li></ul>Human resource software application Human resource software application Human resource software application Human resource software application ------ ------ Scan index ------ ------ Human readable Physical document Human readable Electronic Image Electronic transport And automated routing Image viewer Image viewer Image viewer Image viewer archive
  16. 16. Opportunities for improvement <ul><ul><li>No transport and (intermediate) storage of physical documents </li></ul></ul><ul><ul><ul><li>Reduction of document handling costs </li></ul></ul></ul><ul><ul><ul><li>Reduction of physical storage costs </li></ul></ul></ul><ul><ul><li>Location independent access to relevant documents </li></ul></ul><ul><ul><ul><li>Improvement of productivity </li></ul></ul></ul><ul><ul><li>Accessibility to unlimited number of copies of the document </li></ul></ul><ul><ul><ul><li>Time span reduction </li></ul></ul></ul>
  17. 17. Possible risks and concerns <ul><ul><li>Performance problems caused by a lack of network- and processing capacity </li></ul></ul><ul><ul><ul><li>The need for infrastructure upgrades </li></ul></ul></ul><ul><ul><li>The need for more advanced workstations and printers </li></ul></ul><ul><ul><ul><li>The need for an upgrade of devices </li></ul></ul></ul><ul><ul><li>Privacy and confidentiality </li></ul></ul><ul><ul><ul><li>More complex security measures </li></ul></ul></ul>
  18. 18. Process improvement <ul><li>Workflow management </li></ul>Human resource software Application UI WFM-UI WFM-UI Human resource WFM-UI Human resource software Application UI WFM-UI WFM Application Workflow control data & Workflow relevant data WFM-UI Human resource Work List Form Process definitions Work List Work List Work List
  19. 19. Opportunities for improvement <ul><ul><li>Minimization of data-entry and data-compare activities </li></ul></ul><ul><ul><ul><li>Cost reduction </li></ul></ul></ul><ul><ul><ul><li>Reduction of data quality issues </li></ul></ul></ul><ul><ul><li>Preventive and afterwards control of administrative rules </li></ul></ul><ul><ul><ul><li>Automated control (four eyes principle) </li></ul></ul></ul><ul><ul><li>Intelligent work distribution and redistribution </li></ul></ul><ul><ul><ul><li>Task simplification and differentiation </li></ul></ul></ul><ul><ul><li>Automated process monitoring </li></ul></ul><ul><ul><ul><li>Wait-time thresholds </li></ul></ul></ul><ul><ul><ul><li>Scheduled work thresholds </li></ul></ul></ul><ul><ul><li>Process statistics </li></ul></ul><ul><ul><ul><li>Improved work staff planning </li></ul></ul></ul><ul><ul><ul><li>Productivity monitoring </li></ul></ul></ul><ul><ul><li>Ad-hoc rerouting </li></ul></ul>
  20. 20. Possible risks and concerns <ul><ul><li>Mismatch between the human tasks and the workflow concept of the tools </li></ul></ul><ul><ul><ul><li>The straitjacket of the formalized navigation and user interaction </li></ul></ul></ul><ul><ul><li>Mismatch between reality and modeled workflow </li></ul></ul><ul><ul><ul><li>Incomplete and unreliable input data </li></ul></ul></ul><ul><ul><ul><li>Exceptions in the standard flow </li></ul></ul></ul><ul><ul><li>Application integration issues </li></ul></ul><ul><ul><ul><li>Many existing applications are hard to open up </li></ul></ul></ul><ul><ul><ul><li>Unreliable communication and transaction protocols </li></ul></ul></ul><ul><ul><li>Integration constraint between various BPM-tools </li></ul></ul>
  21. 21. Source: WfMC reference model Worklist Handler Generates References Manipulate Interact via Invokes Invokes Definition Tool Interpreted by External product/data Software component System control data maintain use update (Supervisor) Organisation/ Role Model Workflow control data Workflow Relevant Data Data Build Time Run Time WfMC Workflow Reference Model User Interface Process Definition Work List Application(s) May reference Workflow Application Data WFM Engine(s) Application(s) may refer to Workflow Enactment Service Administration & Control
  22. 22. Workflow concepts : View 2 Low value processes High Value Business processes Production Collaborative Administrative Ad Hoc Loan Origination Insurance claims Accounting Tech doc creation Expense reports Purchase approvals Budgeting “ Transaction workflow” “ Process management” “ E - Forms” “ Groupware” FYI Routing Review and Approve Product brand mgmt. Software development Repetitive process Unique processes Source: BIS Strategic Decisions Workflow Application Segments
  23. 23. <ul><li>Workflow Application Segments </li></ul><ul><li>A d-hoc workflows do not have a well-defined process model to follow. The execution path is more or less determined at runtime, and is basically controlled by humans. These are generally not mission critical, and accomplish the flow of information among people within the organization. </li></ul><ul><li>Production workflows are also predictable and repetitive. They have well defined process models. These usually involve a number of information systems that may be heterogeneous and distributed. Production workflow management systems are thus, more complex and critical than ad-hoc or administrative. </li></ul><ul><li>Administrative workflows are based on simple, repetitive and predictable processes. The ordering and coordination of tasks can thus be automated. However, these too, like ad-hoc workflows, do not involve complex information processing systems, and are generally not mission critical. </li></ul><ul><li>Collaborative workflows are characterized by high mission criticality. They are mostly controlled by humans, and lack a well-defined process model. Thus most of the task ordering and coordination is determined at runtime by the workflow participants. </li></ul>Workflow concepts : View 2
  24. 24. explicitly structured implicitly structured ad-hoc structured unstructured data-driven process-driven ad-hoc workflow groupware production workflow case handling Workflow concepts : View 3
  25. 25. 1. Written request 2. Search name Data entry Under- Writer 3 WFM activity Role Role 1 3. Register request 4. Check blacklist 2 4 5. BKR-check 6. VIS-check 6. 2 time name entry 7. Print 8. Produce label 5 6 7 <ul><li>The large amount of transfers results into an inefficient proces with relative long duration </li></ul><ul><li>Exception handling is hard to implement </li></ul>Transfer to WFM-engine Production Workflow
  26. 26. 1.Writen request 2. Register request 3. Check 2.1. Search name 2.2. Register request 2.3. Check black list 3.1. BKR-check 3.2. VIS-check Data entry Under- writer 4. Final check and completions 2 4.1.2 time name entry 4.2.Print 4.3.Produce label 1 WFM activity Rol Case steps Rol Case steps <ul><li>A small amount of transfers results in a efficient process with a relative short duration </li></ul><ul><li>Exception handling becomes easier to implement </li></ul>Transfer to WFM-engine Case handling
  27. 27. <ul><ul><li>There are no clear market leaders </li></ul></ul><ul><ul><ul><li>Many mergers, splits, new products and product discontinuations </li></ul></ul></ul><ul><ul><li>Limited support of Workflow-related standards </li></ul></ul><ul><ul><li>Slow adoptions of new developments (existing vendors) </li></ul></ul><ul><ul><li>Operation systems </li></ul></ul><ul><ul><ul><li>Unix, Windows, Linux </li></ul></ul></ul><ul><ul><ul><li>WWW </li></ul></ul></ul><ul><ul><ul><li>Java/J2EE </li></ul></ul></ul><ul><ul><ul><li>XML/BPEL </li></ul></ul></ul>Possible risks and concerns
  28. 28. Outline <ul><li>B usiness P rocess M anagement </li></ul><ul><li>Human2Human BPM </li></ul><ul><li>S ystem 2 s ystem BPM </li></ul><ul><li>B usiness 2 B usiness BPM </li></ul>
  29. 29. Process improvement <ul><li>A2A coupling </li></ul>Human resource software Application API Human resource software Application API Human resource software Application API Additional code Additional code Additional code
  30. 30. Process improvement <ul><li>EAI </li></ul>Human resource software Application API Human resource software Application API Broker application Human resource software Application API
  31. 31. Process improvement Broker application <ul><li>EAI – Based on distributed Transactions </li></ul>Human resource software Application API Human resource software Application API Human resource software Application API The availability and performance becomes highly depended on the participating applications and the network Centralized control for a short period of time
  32. 32. Process improvement <ul><li>EAI – Based on asynchronous messaging </li></ul>Human resource software Application API Human resource software Application API Human resource software Application API The state of the total system becomes fuzzy and unpredictable Broker application Control in respect to routing and not in respect to the actual overall state
  33. 33. Process improvement <ul><li>EAI – Based on BPM (=WFM for systems) </li></ul>Human resource software Application API Human resource software Application API Human resource software Application API More overview and coordination over a long period of time Broker application Overall control <ul><li>API’s can/will be replaced by more open services </li></ul><ul><li>Easy Integration with human2human BPM </li></ul>
  34. 34. Web Services Process - “Orchestration&quot; <ul><li>Business Process Execution Language for Web Services (BPEL4WS) </li></ul><ul><li>Define flow as abstract series of activities </li></ul><ul><li>Each activity is implemented by a WSDL interface </li></ul><ul><li>Provides means for handling shared state, compensations, faults etc. </li></ul><ul><li>Expose a process as a web service </li></ul>Web Service Orchestration Activity 1 Shared state and context Public Private Web Service Web Service WSDL Interface WSDL Interface WSDL Interface Activity 2 Activity 3 Individual application transactions
  35. 35. Outline <ul><li>B usiness P rocess M anagement </li></ul><ul><li>Human2Human BPM </li></ul><ul><li>System2system BPM </li></ul><ul><li>Business2Business BPM </li></ul>
  36. 36. B2B Middleware XML <ul><li>Flat file </li></ul><ul><li>EDI </li></ul><ul><li>ebXML </li></ul><ul><li>other … </li></ul>Partner Interface ERP EJB/JMS RDBMS Conversation Transformations State-/ Document Mgmt Business Process Management System Service Interface Business Document XML XML XML Process EAI connectors Interfacing with partners
  37. 37. <ul><li>Orchestration </li></ul><ul><ul><li>executable process (that interacts with other web services) </li></ul></ul><ul><ul><li>control from the perspective of one business partner </li></ul></ul><ul><ul><li>for implementation </li></ul></ul><ul><ul><li>workflow </li></ul></ul><ul><li>Choreography </li></ul><ul><ul><li>sequence of messages </li></ul></ul><ul><ul><li>public message exchanges </li></ul></ul><ul><ul><li>for collaboration </li></ul></ul><ul><ul><li>protocols </li></ul></ul>Orchestration versus Choreography
  38. 38. Opportunities for improvement <ul><ul><li>Reduced transaction cost </li></ul></ul><ul><ul><li>Faster responses </li></ul></ul><ul><ul><li>Business Process Outsourcing </li></ul></ul>
  39. 39. Possible risks and concerns <ul><ul><li>Security risks </li></ul></ul><ul><ul><li>Reliability of the protocol </li></ul></ul><ul><ul><li>The lack of industry standards </li></ul></ul><ul><ul><li>Lack of knowledge and experience </li></ul></ul><ul><ul><ul><li>Be careful with Human2Human BPM experts </li></ul></ul></ul><ul><ul><li>New unproved business models </li></ul></ul>
  40. 40. Business Process Management Tools Understand your processes and choose the appropriate TOOLS