1. WfMC Forum Poland 2007 Tutoriel WfMC France 2007 BPM in Practice: Understanding & Implementing BPM Justin Brunt WfMC Vice Chair, Sr. Product Manager TIBCO Ken Mei WfMC External Relations Committee Michael zur Muehlen Professor, Stevens Institute of Technology Nathaniel Palmer WfMC Executive Dire ctor Keith Swenson, Technical Committee Chair, WfMC, VP R&D, Fujitsu Computer Systems

2. Workflow, BPM, & New Enterprise Architecture Keith Swenson Technical Committee Chairman WfMC Vice President of R&D Fujitsu Computer Systems

7. Relationships of Key Concepts

11. Business Processes Are Cross-functional

14. What is the Gap Between Business & IT?

15. Business and IT: Two Different Audiences Business IT Concerned with only those goals that can be translated into tested, reliable, secure systems Concerned with business goals both manual & automatable Social structures, working hours, vacation schedules, learning skills, changing positions System structure, 7x24, scalability System to system. platform independence robust & fully automated. User interface, choosing among list of tasks, reassigning, manual handling of exceptional occasions. Change processes in days Change processes in months ? ? ? ? ? ? Legacy CRM ERP Supply Chain Sales Marketing Finance Procurement

16. The Bridge Between Human & System CRM Legacy ERP Supply Chain Sales Marketing Finance Procurement Business IT Enterprise Service Bus Web Service Orchestration Presents the right user interface, to the right person at the right time. Notifies & reminds people Automated activities make calls to the ESB and Composite Services in response to user actions. EAI Composite Services WS-Orchestration Web Services Resources Adapters Forms GUI Roles Assignee Expressions Timers Human BPM / Workflow

19. How Does Workflow Bridge the Gap?

20. 1990  Workflow in the Brain Enterprise Application A “ Account Management” Background Check Conformance Guidelines Application Logic in Monolithic Program UI “Screens” list Accts new Acct update Acct delete Acct

21. 1993  Workflow Assist in Sequence Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic in Monolithic Program UI “ Screens” list Accts new Acct update Acct delete Acct background check create account check guidelines Launches UI User accesses original UI directly Human BPM/Workflow:

22. 1996  Distribute Work Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic in Monolithic Program UI “ Screens” list Accts new Acct update Acct delete Acct background check create account check guidelines Launches

23. 2002  Backend converted to Web Services Enterprise Application A “ Account Management” Background Check Conformance Rules Application Logic Service Oriented Architecture Exposed Web Services list Accts new Acct update Acct delete Acct enter info create account bg check rules Review UI connects user to process engine, not the back-end applications

24. 2005  Composite Services Give IT Agility Old Rules Enterprise Application A “ Account Management” Background New Rules list Accts new Acct update Acct delete Acct enter info create account call 1 Review ESB / BPEL Application Logic Exposed Web Services Composite Service

25. 2005  Composite Services Give IT Agility Old Rules Background New Rules list Accts new Acct update Acct delete Acct enter info create account call 1 Review ESB / BPEL Application Logic Exposed Web Services Composite Services

26. Human Activities Have Three Phases Review Automated phase before to prepare for the task Wait phase for Human to do the work, includes timers and escalation logic Automated phase after to take care of results of the task User Interface (while waiting) Note: this notation is not standard!

27. 2008  Simplify as “Human Steps” Enterprise Application A “ Account Management” Background Conformance Rules Application Logic Exposed Web Services list Accts new Acct update Acct delete Acct call 1 Review ESB / BPEL enter info Composite Service To People: Looks like two steps! Much simpler.

30. Human Process Management vs. Enterprise Application Integration

40. Business Level Agility

41. Step 1  Draw Human Process Review enter info First: a business analyst draws the “human” process Business Analyst John

42. Top Down Design: Step 2  Add Integration Enterprise Application A “ Account Management” Background Conformance Rules list Accts new Acct update Acct delete Acct call 1 Review ESB / BPEL enter info Second: Service Invocation Added by IT Expert IT Integration Expert Robert

43. Agility = Business Driven Change w/o Programming Enterprise Application A “ Account Management” Background Rules list Accts new Acct update Acct delete Acct call 1 Review ESB / BPEL enter info News Flash! Some other bank sued! Need to respond quickly to avoid risk! legal check

47. Process Thought Leadership