Business Level Agility is the ability for office workers to take control of the processes that run their organizations, to adapt their processes to their needs, and to respond to external change without involving programmers. Workflow and BPM are driving enterprise system architecture in a radical new direction that allows for Business Level Agility. Enterprise applications can be structured to separate the “who” and the “when” from the “what” and the “how”. The former aspect is ephemeral with a strong dependence upon people, skills, customs, cultures, and other things that are flexible. The latter aspect is relatively stabile with a strong dependence upon data structures, formal representations, and other concrete concepts. This talk will explain what this separation means, and how evolving standards will enable this transformation of the way we design our business critical IT infrastructure.

6. Relationships of Key Concepts

10. What is the Gap Between Business & IT?

11. Business & 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

12. 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

15. How Does Workflow Bridge the Gap?

16. 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

17. 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 Launches UI User accesses original UI directly background check create account check guidelines Human BPM/Workflow:

18. 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

19. 2002  Integration thru 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

20. 2005  Composite Services = 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

21. 2005  Composite Services = 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

22. 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)

23. 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.

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

27. 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

28. Agility  Business Driven Change 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

31. Standards Support

32. The Workflow Reference Model Process Definition Tools Interface 1 Interface 4 - Interoperability Interface 5 Workflow Enactment Service Other Workflow Enactment Service(s) Worklist Handler Interface 3 Interface 2 Invoked Applications Tool Agent Process Definition Import/Export Client Apps Typically Web Services Workflow Engine(s) see: www.wfmc.org/standards/docs/tc003v11.pdf BPMN XPDL Wf-XML SOAP BPEL Administration & Monitoring Tools Workflow Engine(s)

34. Industry Standards Stack Process Definition Process Execution Process Orchestration Choreography Definition WS-C (concrete) WS-BPEL (abstract) Monitoring & Audit WfMC IF5 Process State Notation WfMC Process and Activity State Models BPRI Wf-XML ASAP Notation UML AD BPMN Repository & Discovery UDDI Assurance WS-Security SAML Formats BPDM XPDL BPSS CPA/CPP BPR Transport Reliability ebXML-RM WS-RM ... Transport Layer HTTP JMS ... Data Format XML Encoding SOAP / Attachments WS-Addressing Data Definition XML-Schema End Point Definition WSDL Runtime Interaction Wf-XML ASAP WfMC WAPI Presentation X-Forms (concrete) WS-BPEL (abstract) XPDL BPMN

35. Timeline November 1998 October 2002 1997 XPDL 1.0 October 2005 May 2004 BPMN 1.0 1995 XPDL 2.0 WFMC BPMI 1993 OASIS OMG Reference Model Glossary XML WPDL 1996 1994 2000 BPEL Wf-XML Wf-XML 2.0 ASAP

36. BPMN - Modeling Notation

42. Design Interchange vs. Executable XPDL Design Tool A Execution Engine A BPEL, XPDL, or some engine specific format Design Tool B Execution Engine B BPEL, XPDL, or some engine specific format X This path generally not possible to support

44. Process Design Ecosystem Design Tool Design Tool Modeling Tools Optimization Tools Simulation Tools Execution Engine Execution Engine BPEL or some engine specific format BPEL or some engine specific format Repository (XPDL) Vendor A Vendor D ASAP Wf-XML Vendor B Vendor C

46. XPDL Support in Market