Enterprise Application Integration and Process Modelling

1. Enterprise Application Integrationand Process Modelling Erik Perjons DSV, KTH/SU

2. Why focusing on business processes? • re-engineering the business processes to make them more effective/efficient • easy to understand for non-technical people • discover and adopt to changed customer demands • automate the activities in business processes

3. Stove pipe problem Production Market Shipment Purchase Customer service Management

4. Production Shipment Market Management Purchase Customer service Business processes cross departments

5. Production Shipment Market Management Purchase Customer service Solution: Integrated IT systems

6. Why problem integrating IT systems? • Different platforms, programming languages, and formats • No interfaces • Legacy systems with no documentation • Different semantics in the systems (different meanings of e.g. ”customer”, ”region”, ”product”) • Need of a routing mechanism

7. Production Market Management Customer service Purchase Problem: Constantly changing business processes

8. Integration solutions • ERP and Enterprise systems • - replace existing IT systems with • a new one • EAI middleware • - integrate existing IT systems • Electronic collaboration solutions (B2B solutions) • - integrate the suppliers’ and customers’ systems • Data warehousing • - extract some data from existing IT systems and load it into a new system for decision support

9. Production Shipment Market Management Customer service Purchase ERP systems/Enterprise systems

10. Integration solutions • ERP and Enterprise systems • - replace existing IT systems with a new one • EAI middleware • - integrate existing IT systems (RPC, CORBA, XML, Message Broker, BPMS) • Electronic collaboration solutions (B2B solutions) • - integrate the suppliers’ and customers’ systems • Data warehousing • - extract some data from existing IT systems and load it into a new system for decision support

11. Production Shipment Market Management Customer service Purchase EAI: Point-to-Point solutions

12. Production Market Management Customer service Purchase EAI: Many-to-Many solutions

13. Application A Application A Application A Application A Application B Application B Application B BPMS Message Broker Application C Application C Application C Application D Application D Person A Point-to-point Many-to-many - Message Brokers Many-to-many - BPMS Message Brokers and BPMS

14. Business Process Management Systems (BPMS) also called Process Brokers, Process Automation Systems, Workflow Management Systems - directly executable business models - support process design (modelling), execution, analysis, simulation and optimisation of business processes - automate the business processes, or the information flow

15. Categorisation of Business Process Modelling Languages • Static-oriented languages • visualise the input and output from activities, but not the logical order/time, e.g. IDEF0, data flow diagram • Activity-oriented languages • decribes which activities follows and precede another in a process, e.g EPC, UML activity diagram • State-oriented languages • describes which states follow and precede another in a process, e.g UML state diagram • Communication oriented languages • - focus on the interaction between prople and systems, and between systems, e.g UML sequence diagram, BML, SDL

16. Basic process language concepts • Four basic process language concepts, which have the following intuitive meaning: • A time point is an instant in time, not further decomposible • An event is an noteworthy occurence • A state shows the condition of a process and can be represented in several way, e.g. as a set of attribute values • A activity is something that is performed in a process

17. Different meaning of basic terms • Two examples (there are more): State State State State State State Activity Activity Event Event Time points Time points

18. Meta models and reference meta model [Rosemann&Green, 2002]

19. Bokinfo Budgetinfo Lev.info Beställnings rutin Beställnings mottagande Katalog- kontroll Budget kontroll An- ställd Bok- handel Data flow diagram

20. UML Activity Diagram [Fowler&Scott, 1997]

21. UML State Diagram [Fowler&Scott, 1997]

22. Business Modelling Language (BML)

23. Business Modelling Language (BML)

24. Business Modelling Language (BML)

25. Process Broker project • The purpose of the project is to investige BPMS (Process Brokers), in particular: • business process modelling languages • method for application and process integration

26. Process Broker project - Telecom case

27. Vita Nova project The purpose of the project is to investige the potential of BPMS in Health and Medical Services DSV’s assignment is to develop a framework for evaluating business processes models, BPMS and methods for integrating business processes

28. Loosely-Structured Business Processes project • The purpose of the project is to investige BPMS for loosely-structured business processes • focused on goal and state modelling • try to define patterns for such business processes • case studies: decision-making and lobbying

29. ebXML and EC4 project - ebXML is a global standard developed by UN/CEFACT and OASIS - EC4 stands for Electronic Commerce and Collaboration Center - aims at disseminate knowledge about electronic commerce and collaboration among researchers, students and SME

30. Integration solutions • ERP and Enterprise systems • - replace existing IT systems with a new one • EAI middleware • - integrate existing IT systems • Electronic collaboration solutions (B2B solutions) • - integrate the suppliers’ and • customers’ systems • Data warehousing • - extract some data from existing IT systems and load it into a new system for decision support

31. B2B - Electronic CollaborationIntegration Shipment Production Market Customer service Management Purchase Suppliers Customers

32. Company 3 Company 2 Business Processes spanning several organisations Company 1 P1.3 P1.1 P1.4 P1.2

33. ebXML Electronic CollaborationIntegration Levels

34. Register and Store Publish and provide service Find, request and bind service SOA Web services and CORBA are different implementations of Service Oriented Architecture (SOA) Service Broker Find Publish Service Requestor Service Provider Request & Bind

35. Integration solutions • ERP and Enterprise systems • - replace existing IT systems with a new one • EAI middleware • - integrate existing IT systems • Electronic collaboration solutions (B2B solutions) • - integrate the suppliers’ and customers’ systems • Data warehousing • - extract some data from existing IT systems and load it into a new system for decision support

36. The back room The front room BI/Analysis/OLAP Data warehouse External sources Extract Transform Load (ETL) Serve Query/Reporting Operational DBs/ OLTPs/TPSs Data marts Data mining Falö aöldf flaöd aklöd falö alksdf Front end tools End user applications Data sources Legacy systems OLTP/TP systems Back end tools Data staging area ”The data warehouse” OLAP servers Data warehousing architecture

37. Data warehousing definition ”Data warehousing is a collection of decision support technologies, aimed at enabling the knowledge worker (executive, manager, analyst) to make better and faster decisions.” [Chaundhuri&Dayal, 1997]