Business Process Management (BPM) Lecture 2: Introduction to BPMN

Size: px
Start display at page:

Download "Business Process Management (BPM) Lecture 2: Introduction to BPMN"

Transcription

1 MTAT Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN Marlon Dumas marlon.dumas ät ut. ee

2 Process Modelling Management 2

3 What is a Model? Prepare shipment Ship goods Register order (Re)send bill Archive order Receive payment Requirement for material has arisen Contact customer Purchase Requisition Requisition released for scheduling agreement schedule/sa release Purchase requisition released for purchase order Purchasing Goods received Inbound delivery entered Purchase order created Goods Receipt Goods receipt posted Warehouse/ Stores Material is released Invoice received TO item confirmed without differences Transfer order item is confirmed Invoice Verification Payment must be effected 3

4 Purposes of Process Modeling Process Documentation Process Compliance / Improvement Risk Management Knowledge Management Enterprise Systems Process Cost Analysis/Simulation Workflow Management Document Management Software Evaluation/ Selection Enterprise Architecture Michael Rosemann 4

5 Popular Process Modelling Purposes 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% 70.00% 80.00% 90.00% % Recker et al. (2005) 5

6 Process Modeling Intention: As-Is versus To-Be (Wreden, 1999) Process models can document the present situation (As-is modelling) or describe an targeted situation ( To-be modelling) Start F1 E1 F2 E2 F5 10 Minute(s) E5 F3 E3 F4 20Minute(s) Start F1 E1 F2 F6 E6 Present situation ti As-is models act as a blue print for analyzing how processes are executed today E2 Targeted situation To-be models act as a road map for creating the most efficient processing for new business initiatives 6

7 Process Modelling Viewpoints Organization Who? What? Function When? Process Which? Data / Service / Product 7

8 Process Modelling Viewpoints What (functional l perspective) ) What tasks/function are happening in the process Who (resource perspective) Who does these activities When (control-flow perspective) In what order do they occur Which (resource and data perspective) Which resources (i.e. materials, technology) is used in the process Which data is created/produced by the process 8

9 Process Model Granularity 9

10 Process Model Granularity Main process (area): Personnel management Business process: Personnel recruitment Partial process: Select applicant Work step: Enter applicant data Elementary activity: Assign applicant number 10

11 Process Modeling Languages For business analysts Business Process Modelling Notation ti (BPMN) Event-driven Process Chains (EPC) IDEF0, IDEF3 Flowcharts, data-flow diagrams (system analysis) UML Activity Diagrams (system analysis) For business programmers Business Process Execution Language (BPEL) Yet Another Workflow Language (YAWL) State machines and variants And many, many more 11

12 Purposes of Process Modeling Measu ures for Improv vement Organizational Analysis AS IS Process Models Process Analysis & Design TO BE Process Models Abstract Models EPC, BPMN Communication, simulation, activitybased costing Process Evaluation Process Metrics Target Valu ues Process Enactment & Monitoring Process Implementation Executable Pro ocess Mode els Detailed Models BPEL, State Machines Data types, conditions, data mappings, fault handling Integration, testing, deployment 12

13 Process Modeling Notations: EPC 13

14 Process Modeling Notations: BPMN 14

15 Process Specification Language: YAWL 15

16 Executable Process Specification Language: BPEL 16

17 BPMN Business Process Modeling Notation Originally developed by Business Process Management Initiative (BPMI) Handed over to Object Management Group (OMG) in 2005 Inspired by cross-functional flowcharts Supported by many tools: IBM Websphere Business Modeler ARIS, Oracle BPA Telelogic System Architect (now IBM) ITP Commerce Process Modeler for Visio Oryx ( t h i t d /O Savvion, Lombardi, BizAgi,... 17

18 BPMN from miles A process model in BPMN is called a Business Process Diagram (BPD) A BPD is essentially a graph consisting of four types of elements (among others): 18

19 Example An Order Management process is triggered by the reception of a purchase order from a customer. The purchase order has to be checked against the stock re the availability of the product(s) requested. Depending on stock availability the purchase order may be confirmed or rejected. If the purchase order is confirmed, the goods requested are shipped and an invoice is sent to the customer. 19

20 Order Management Process in BPMN 20

21 A little bit more on Gateways Exclusive Decision / Merge Indicates locations within a business process where the sequence flow can take two or more alternative paths. Only one of fthe paths can be taken. Depicted by a diamond shape that may contain a marker that is shaped like an X. Parallel Fork / Join Provide a mechanism to synchronize parallel flow and to create parallel flow. Depicted by a diamond shape that must contain a marker that is shaped like a plus sign. 21

22 Revised Order Management Process 22

23 Organisational modelling In general, organisational modelling encompasses: People, departments, units, services, partners, clients, suppliers Roles, entities, actors, Responsibilities, duties, skills, 23

24 Organisational Elements in Process Models Basic abstractions: Resource (participant, actor, user, agent) A resource can execute certain tasks for certain cases. Human and/or non-human (e.g. printer): limited capacity. Resource class: Set of resources with similar characteristics A resource class is typically either a: Role (skill, competence, qualification) Classification based on what a resource can do or is expected to do Group (department, team, office, organizational unit) Classification based on the organization. 24

25 Roles vs. Groups Eindhoven Purchase Sales Amsterdam groups Kees Mies Koos Sjaak Pim Truus Ivone Ad Kevin Jan Anita Frank Secretary Sales_clerk Office_worker Manager roles Wil van der Aalst 25

26 Organisational Modelling in BPMN Bad news: BPMN does not support the concepts previously discussed Organisational modelling in BPMN = Lanes Pools Performers So: Use pools and lanes to capture resource classes 26

27 Pool BPMN Elements Pools Pools represent business process participants. They are used to partition a set of activities from other pools. Horizontal vs. vertical Can be a business entity or a business role. Each BPD contains at least one pool. A Pool acts as the container for the Sequence Flow between activities. The Sequence Flow cannot cross the boundaries of a Pool. The interaction between Pools, e.g., between two collaborating organizations, is shown through Message Flow. 27

28 BPMN Elements Message Flows Message Flow Depicted by a dashed line with an open arrowhead. Represent the flow of messages between two separate process participants that are prepared to send and receive them. A Message Flow can connect directly to the boundary of a Pool. Represents an informative message to that participant. A Message Flow can cross the boundaries and connect directly to a Flow Object within that Pool. Represents a message that triggers certain action. 28

29 Order Management example (ctd.) The Order Management process now includes the customer as a process participant... The Order Management process is started when a customer places a purchase order. The purchase order has to be checked against the stock re the availability of the product(s). Depending on stock availability the purchase order may be confirmed or rejected. If the purchase order is confirmed, the goods requested are shipped and an invoice is sent to the customer. The customer makes then makes the payment. 29

30 Order Management BPD with Swimlanes er Supplie Customer 30

31 BPMN Elements Swimlanes Lanes represent sub-partitions within a pool. They are used to organize and categorize activities. Horizontal vs. vertical Meaning is not specified by BPMN, Lanes are often used for internal roles (e.g., Manager, Associate), systems (e.g., an enterprise application), an internal department (e.g., shipping, finance), etc. Both Sequences Flow and Message Flow can cross the boundaries of Lanes. Lanes can be nested: E.g., an outer set of Lanes for company departments and then an inner set of Lanes for roles within each department. 31

32 Order Management example (ctd.) The process now includes two departments within the supplier organization... The purchase order received by the Sales & Distribution department has to be checked against the stock. The order details are sent to the Warehouse department that returns an availability notification. If the purchase order is confirmed, the Warehouse department collects the shipping details from the customer and ships the goods. The Sales & Distribution ib ti department t sends an invoicei to the customer who then makes the payment. 32

33 Corresponding BPD 33 Supplier Customer Warehouse Sales & Distribution

34 BPMN Artifacts Data Objects are a mechanism to show how data is required or produced by activities. Are depicted by a rectangle that has its upper-right corner folded over. Represent input and output of a process activity. Annotations are a mechanism for the modeller to provide additional text information to the diagram reader. Are depicted by open-ended rectangles. Text annotations do not affect the flow of the process. Groups are a visual mechanism to logically group diagram elements informally. Are depicted by a rounded corner rectangle with a dashed line. The grouping does not affect the sequence flow and does not change the meaning of the elements contained within the group. 34

35 BPMN Connections Associations are used to link artifacts such as text or data objects with flow objects. Are depicted by a dotted line. Can be directed or undirected. They can be used to show inputs and outputs of activities. 35

36 Order Management example (ctd.) Let s have a look at some artifacts... The Purchase Order document serves as an input to the stock availability check. Based on the outcome of this check, the status of document is updated, either to approved or rejected. Include the relevant documents in the process model. Also, for visualization purposes, all parts of the processes that use or update the purchase order should be highlighted. 36

37 Order Processing Model with Artifacts Purchase Order Confirm order Send invoice Check stock availability Update PO: [approved] Update PO: [rejected] Ship goods Reject order Order handling 37

38 BPMN Main Elements - Recap Connections Swimlanes Message Flow Flow Objects Artifacts Text Annotation Gateway 38

39 BPMN Flow Elements Recap 39