Tytuł: Wprowadzenie. Kluczowe elementy BPM

Tytuł: Wprowadzenie. Kluczowe elementy BPM Autor: Piotr SAWICKI Zakład Systemów Transportowych WMRiT PP piotr.sawicki@put.poznan.pl www.put.poznan.pl/~piotr.sawicki www.facebook.com/piotr.sawicki.put Przedmiot: Zarządzanie procesami transportowo-logistycznymi Specjalność: Logistyka transportu Wersja: 204.0.06 Agenda Kluczowe elementy wykładu WPROWADZENIE Cel i zakres wykładu. Poznajmy się. Kluczowe pojęcia. BPM BUSINESS PROCESS MANAGEMENT Cykl życia BPM. Główne fazy. NOTACJE I NARZĘDZIA BPM Kluczowe notacje różnice i podobieństwa ŹRÓDŁA WIEDZY O BPM Literatura podstawowa i uzupełniająca PODSUMOWANIE Pewnie są pytania :-) 2

Wprowadzenie Cel i zakres wykładu! Cel zdefiniowanie pojęć kluczowych dla całego przedmiotu nakreślenie obszaru zainteresowania w ramach przedmiotu ustalenie zasad współpracy 3 Wprowadzenie Cel i zakres wykładu! Kluczowe pytania co to jest: proces, klient,, BPM? z jakich głównych faz składa się cykl życia BPM? z jakich narzędzi będziemy korzystać na zajęciach i jaka jest ich dostępność? z jakiej literatury można / należy korzystać przygotowując się do zajęć? 4 2

Wprowadzenie Poznajmy się Piotr SAWICKI (bio) absolwent PP - WMRiP (studia magisterskie) i PW - WT (obrona rozprawy doktorskiej) wykładowca pracownik PP, WMRiT, Zakład Systemów Transportowych doradca - konsultant w zakresie optymalizacji biznesowej, ponad 50 projektów autor książki: Wielokryterialna optymalizacja procesów w transporcie, ITE, Radom, 203 doświadczenie zawodowe: F5 Konsulting Sp. z o.o., Instytut Logistyki i Magazynowania w Poznaniu, IDS Scheer Polska Sp. z o.o. (obecnie Stware AG.) 5 Wprowadzenie Poznajmy się a teraz WY nazywam się zarządzanie procesami kojarzy mi się z w zajęciach najważniejsze dla mnie jest 6 3

Wprowadzenie Proces wg. Melão i Pidd, 2000 b) 2. Zarządzanie procesami 29 2. Zarządzanie procesami 29 tywa postrzegania procesu jako konstrukcji społecznej według Arlbjørna tywa postrzegania procesu jako konstrukcji społecznej według Zasoby Arlbjørna i Hauga oraz Melão i Pidda zdecydowanie różni się od wcześniejszych. ludzkie i Hauga oraz Melão i Pidda zdecydowanie różni się od wcześniejszych. Pion A Pion B Pion C a) b) a) b) Proces transformacji Pion A Pion B Pion C Pion A Pion B Pion C Proces jako mechanizm deterministyczny Zadania i Technologia Zasoby ludzkie d) Złożony system o charakterze dynamicznym 7 Zasoby ludzkie Proces Proces transformacji transformacji Zadania Zadania i i Technologia Technologia Transformacja poprzez ludzi Wprowadzenie c) c) d) d) 2 Proces wg. Melão i Pidd, 2000 3 5 7 4 6 Regulator Regulator Regulator Regulator 2 2 Poziom Poziom Poziom Poziom 3 3 Regulator 3 Regulator 6 Regulator 3 Regulator 6 Poziom 4 Poziom 4 Poziom 2 Poziom 2 Regulator 7 Regulator 7 Regulator 4 Regulator 5 Regulator 4 Regulator 5 Transformacja Transformacja poprzez poprzez ludzi ludzi 2 2 3 5 3 5 7 4 4 6 6 7 Proces jako zbiór powiązanych pętli Proces jako konstrukcja społeczna 8 Rys. 2.. Porównanie czterech kluczowych podejść do rozumienia procesu Rys. 2.. Proces Porównanie jako: a) czterech mechanizm kluczowych o charakterze podejść deterministycznym, do rozumienia procesu b) złożony system o charakterze Proces dynamicznym, jako: a) mechanizm c) zbiór o powiązanych charakterze deterministycznym, pętli, d) konstrukcja społeczna b) złożony system o charakterze dynamicznym, własne podstawie: c) zbiór Arlbjørn powiązanych i Haug [8], pętli, Melão d) konstrukcja i Pidd [75] społeczna Źródło: opracowanie Źródło: opracowanie własne na podstawie: Arlbjørn i Haug [8], Melão i Pidd [75] 4 Autorzy podkreślają, że proces realizowany jest przede wszystkim przez ludzi, Autorzy podkreślają, że proces realizowany jest przede wszystkim przez ludzi,

Wprowadzenie Proces wg. Sawicki P. (203) 2" Dane, zdarzenia, oczekiwania, wymogi Czynności Logika, kolejność, związki przyczynowoskutkowe PROCES Zasoby Wykonawcy, wyposażenie techniczne, informacja, kapitał, materiały, energia Rezultaty Rezultaty, wyniki! Proces to: ustrukturyzowany zbiór czynności realizowanych z wykorzystaniem niezbędnych zasobów przetwarza elementy wejściowe w oczekiwane rezultaty przebieg kształtują interakcje wewnętrzne w procesie, z otoczeniem wewnętrznym (inne procesy) i zewnętrznym (rynek i klienci) 2" 9 Wprowadzenie Proces vs. struktura organizacyjna Potrzeba Zamówienia Wzór nowego Rozwój nowego Przyjęte zamówienia Obsługa zamówień Controling finansowy Rentowność Kampania promocyjna Promowanie Zaspokojona potrzeba Surowce Dostępne surowce Zaopatrzenie Proukcja Gotowy wyrób Dostawca Dystrybucja Zrealizowana dostawa 0 5

Wprowadzenie Proces vs. struktura organizacyjna A. Orientacja funkcjonalna B. Orientacja procesowa ZARZĄD ZARZĄD i rozwój Sprzedaż Logistyka Produkcja Finanse i księgowość Marketing i rozwój Sprzedaż Logistyka Produkcja Finanse i księgowość Marketing Potrzeba Zamówienia Wzór nowego Rozwój nowego Przyjęte zamówienia Rentowność Kampania promocyjna Promowanie Zaspokojona potrzeba Obsługa zamówień Controling finansowy Surowce Dostępne surowce Zaopatrzenie Proukcja Gotowy wyrób Dostawca Zrealizowana dostawa Dystrybucja - komunikacja Wprowadzenie Proces vs. struktura organizacyjna vs. klient ZARZĄD i rozwój Sprzedaż Logistyka Produkcja Finanse i księgowość Marketing Potrzeba Zamówienia Wzór nowego Rozwój nowego Przyjęte zamówienia Obsługa zamówień Controling finansowy Rentowność Kampania promocyjna Promowanie Zaspokojona potrzeba Surowce Dostępne surowce Zaopatrzenie Proukcja Gotowy wyrób Dostawca Dystrybucja Zrealizowana dostawa ZEwnętrzny WEwnętrzny 2 6

BPM mngt Cykl życia BPM Analiza - Wymagania biznesu - Niezbędne zasoby - Możliwości poprawy - Optymalizacja, symulacja - Obserwacja - Kontrola efektów - Regularna realizacja procesu Doskonalenie Monitoring Cykl zarządzania procesem (BPM) Modelowanie Konfiguracja - Formalny zapis procesu - Uruchomienie procesu - Przeszkolenie wykonaw. - Ustalanie parametrów funkcjonalnych 3 BPM Cykl życia BPM Analiza - Wymagania biznesu - Niezbędne zasoby - Formalny zapis procesu - Możliwości poprawy - Optymalizacja, symulacja - Obserwacja - Kontrola efektów - Regularna realizacja procesu Doskonalenie 4 Monitoring Cykl zarządzania procesem (BPM) 3 Modelowanie 2 Konfiguracja - Uruchomienie procesu - Przeszkolenie wykonaw. - Ustalanie parametrów funkcjonalnych 4 7

BPM Kluczowe elementy BPM Doskonalenie Monitoring Analiza Modelowanie Konfiguracja! Analiza, projektowanie i modelowanie (.) Jak identyfikować / budować proces? Rola klienta, oczekiwań i wymagań w definiowaniu procesu (.2) Istota budowy modelu po co modelować? Architektura procesów (.3) Przegląd notacji procesu (w tym: BPMN, EPC, YAWL itp.), oraz narzędzi do modelowania (w tym: ARIS, igrapx, BizzAgi, Adonis, i.in.). Podobieństwa i różnice 5 BPM Kluczowe elementy BPM Doskonalenie Monitoring Analiza Modelowanie Konfiguracja! Analiza, projektowanie i modelowanie (.4) Modelowanie procesów: Notacja EPC - narzędzie ARIS BA (.5) Modelowanie procesów: Notacja BPMN - narzędzie ARIS BA (.6) Modelowanie w praktyce: warsztaty 6 8

BPM Kluczowe elementy BPM Doskonalenie Monitoring Analiza Modelowanie Konfiguracja! Analiza, projektowanie i modelowanie Modelowanie co to takiego? odzwierciedlenie rzeczywistości z wystarczająca dokładnością 7 BPM Kluczowe elementy BPM Analiza! Konfigurowanie Doskonalenie Monitoring Modelowanie Konfiguracja 2 (2.) Podstawowa konfiguracja procesu: określenie zakresu odpowiedzialności w procesie, obieg dokumentów, wsparcie procesu narzędziami IT (2.2) Raportowanie i dokumentowanie procesów: opis stanowisk, zakres wsparcia procesu przez IT, itp. (2.3) Zastosowanie symulacji ARIS Simulator do konfiguracji procesu 8 9

BPM Kluczowe elementy BPM Analiza! Doskonalenie Monitoring 3 Modelowanie Konfiguracja (3.) Przydział zasobów do zadań w procesie. Definiowanie mierników procesu: wydajność procesu, czas trwania procesu, stopień wykorzystania zasobów 9 BPM Kluczowe elementy BPM Analiza!, monitorowanie i doskonalenie Doskonalenie 4 Monitoring Modelowanie Konfiguracja (4.) Jak doskonalić procesy? Doskonalenie procesów poprzez symulację. Kluczowe założenia i pojęcia. Korzystanie z zaawansowanych opcji narzędzia statystyki (kolejki, wąskie gardła, słabe punkty, ) (4.2) Zastosowanie narzędzia ARIS Simulator do przebudowy procesu (4.3) Zastosowanie optymalizacji symulacyjnej w doskonaleniu procesów wykorzystanie ARIS BS. 20 0

Narzędzia i notacje w BPM Notacje modelowania Wpłynęło zlecenie na pojazd do8eur Wpłynęło zlecenie na pojazd 32EUR Zlecenie! Notacja - język modelowania 4.7 Process Modeling Notation procesu istnieją różne koncepcje opisu! EPC ang. -driven chain diagram (Scheer, 999) Na koncie klienta widnieją zaległe płatności Na koncie klienta brak jest zaległych płatności opisu przebiegu i zasobów wiarygodności klienta Baza klientów 2 Wprowadzanie zlecenia do systemu System dyspozytorski możliwości warunkowego przyjęcia zlecenia Baza klientów final version paper that will be printed in conference proceedings. In case paper is rejected, join gateway is triggered. To clarify behaviour split gateway, outgoing sequence flows are associated with Zamówienie respective annotations. dostępne Table 0.93 and ir Markers 4.7 Process Modeling Notation 2 Warunkowo w systemie The participants that cooperate in context a combrak możliwości przyjęto realizacji zlecenia zlecenie do municate by sending and that receiving messages. diagrams, final version paper will be printed In in conference proceedings. realizacji Top messages arepaper represented by message Typically a message flow connects In case is rejected, joinflow. gateway is triggered. clarify and betable 0.93 To ir Markers Non Nonan activity one participant to an activity or an event anor participant. haviour split gateway, outgoing sequence flows are associated with (abstract or global), Depending on kind diagram respective annotations. message flows can link pairs flow objects, pools, and events. Detailed rules Top TablePrzydzielanie 0.93 and ir Markers The participants that cooperate in context a comsystem NonOdmowa zlecenia Dyspozytor on messagebyflow connections are discussed below. Flow is used to Baza Nondyspozytorski municate sending and receiving messages. In A diagrams, do pojazdu realizacji klientów show flow messages by between twlow. participants are prepared to send zlecenia messages are represented message Typicallythat a message flow connects Top and receive m. In BPMN, two separate Pools in Diagram will represent Nonan activity one participant to an activity or an event anor participant. Non two participants (e.g., entities or roles). a Depending on kind diagram (abstract or global), poinformowano The notational elements BPMN regarding transactional behaviour message flows can link pairs flow objects, pools, Table and events. Detailed rules Oczekiwanie na o braku możliwości 0.93 and Chwilowo and ir brakmarkers Zlecenie es (transaction groups, compensation flow, cancellation) dostępność realizacji zlecenia dostępnych przydzielono do on message flow connections are discussed below. A Flow is used to wolnych pojazdów will not be covered, because ir semantics is not laid out in sufficient detail pojazdów pojazdu jest zbyt długie show flow messages between two participants that are prepared to send and precision. Top and receive m. In BPMN, two separate Pools in Diagram will represent Non Non two participants (e.g., entities or roles). Table 0.93 and ir Markers The notational elements BPMN regarding transactional behaviour zleceń play es (transaction groups, compensation flow, since and cancellation) a central role in management, y are Top will not be covered, because ir semantics is not out in sufficient detail glue between situations in organizations andlaid es that will be en Nonand precision. can be partitioned Rys. 2.7. Model procesu weryfikacji i przydziału zlecenia przewozowego do realizacji, opracowany w notacji EPC acted if se situations occur. in a Table 0.9 Send Task model associations Attribute Name Description/Usage messageref: [0..] A for messageref attribute MAY be entered. This indicates that will be sent by Task. The in this context is equivalent to an out-only message pattern (Web service). One or more corresponding outgoing Flows MAY be shown on diagram. However, display Flows is NOT REQUIRED. The is applied to all outgoing Flows and will be sent down all outgoing Flows at completion a single instance Task. operationref: Operation This attribute specifies operation that is invoked by Send Task. implementation: string = ##webservice This attribute specifies technology that will be used to send and receive s. Valid values are "##unspecified" for leaving implementation technology open, "##WebService" for Web service technology or a URI identifying any or technology or coordination protocol A Web service is default technology. A Send Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a filled envelope marker that distinguishes shape from or Task types (as shown in Figure 0.3). A Receive Task is a simple Task that is designed to wait for a to arrive from an external Participant (relative to Process). Once has been received, Task is completed. A Receive Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes an unfilled envelope marker that distinguishes shape from or Task types (as shown in Figure 0.5). If instantiate attribute is set to true, envelope marker looks like a (as shown in Figure 0.6). Dział transportu Wpłynęło zleceniedata na pojazd do8eur Object Zlecenie Termination Brak zaległości Rule Task. Valid values are "##unspecified" for leaving Figure 0.4 - The Send Task and Receive Task class diagram implementation technology open, "##WebService" for Web service technology or a URI identifying any or technology or coordinationtheprotocol. Send Task inherits attributes and model associations Activity (see Table 0.3). In addition following System dyspozytorski The default technology for this task is unspecified. Wprowadzanie zlecenia do Script Task constraints apply when Send Task references a : The Send Task has at most one inputset and one Data Input. If Data Input is present, it MUST have an ItemDefinition equivalent to one defined by associated. At execution time, when Send Task is executed, data automatically moves from Data Input on Send Task into to be sent. If Data Input is not present, will not be populated with data from Process. systemu 26 A Script Task is executed by a engine. modeler or implementer defines a script in atable language that additional model associations Send Task. 0.9 presents Process Model Notation, v2.0 Figure 0.7 - A User Task ObjectTheand engine can interpret. When Task is ready to start, engine will execute script. When script is completed, Task See User Task on page 63 within larger section Human Interactions User for details User Tasks. Task will also be completed. 60! events can have di erent triggers. Dyspozytor A User Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a human figure marker that distinguishes shape from or Task types (as shown in Figure 0.7). Annotation Table 7.2 - BPMN Extended Modeling Elements s provide information about what Activities require to be performed and/or what y produce (see page 205), s can represent a singular object or a collection objects. Data Input and Data Output provide same information for Processes. A User Task is a typical workflow Task where a human performer performs Task with assistance a Manual Task stware application and is scheduled through a task list manager some sort. A Manual Task is a Task that is expected to be performed without aid any execution engine or User Task a roundedlocation. corner rectangle that MUST be drawn with a single thin line and includes a human figure any application. An example this could be a telephone technician installing aatelephone at ais customer marker that distinguishes shape from or Task types (as shown in Figure 0.7). Manualrectangle Task is a that rounded corner that MUST be drawn with and a single thin line and includes A Script Task is a roundedacorner MUST berectangle drawn with a single thin line includes a marker that a hand figure distinguishes shape in from or 0.20). Task types (as shown in Figure 0.7). distinguishes shape frommarker orthat Task types (as shown Figure wolny pojazd 26 Przydzielanie 3! zamówienia do Association Datav2.0 Process Model Data and Notation, Object Objects provide information about what pojazdu 26 Data Objec (Collection) Manual Task See Manual Task on page 65 within larger section Human Interactions for details Manual Tasks. Data Input BPMN uses term fork to refer to dividing a path into two or more parallel paths (also known as an AND-Split). It is a place in Process where activities can be performed concurrently, rar than sequentially. Za$ Data Output 64 A is used to depict contents a communication between two Participants (as defined by a PartnerRole or a PartnerEntity see on page 93). Zlecenie Chwilowy brak wolnych pojazdów A Manual Task is a Task that is expected to be performed without aid any execution engine or any application. An example this could be a telephone technician installing a telephone at a customer location. Data Output A Rule Task provides a mechanism for Process to provide input to a Rules Engine and Data to getinput A Manual Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a hand figure output calculations that Rules Engine might provide.process The InputOutputSpecification Model and Notation, v2.0 marker distinguishes shape from or Task types (as shown in Figure 0.7). Task (see page 2) will allow Process to send data to and receive data from that Rules Engine. Rule Fork przydzielone do pojazdu See User Task on page 63 within larger section Human Interactions for details User Tasks. Figure 0.20 - A Script Task Object `$ Zlecenie Activities require to be performed and/or what y produce (see page 205), s Task Object can represent a Figure singular 0.7 object -oraa User collection objects. Data Input and Data Output provide same information for Processes. Figure 0.8 - A Manual Task Object Data Objec (Collection) events can have di erent triggers. Swimlanes Dostępne pojazdy Table 7.2 - BPMN Extended Modeling Elements Fig. 4.80. types in BPMN, Object Management Group (2006) Lane Non This attribute specifies technology that will be used to implement implementation: string = 6 ##unspecified Sequence Flow ActivitiesFig. 4.80.Place types in BPMN, Object Management Group (2006) A Script Task object shares same shape as Task, which is a rectangle that has rounded corners. However, re Zbyt długi okres Flow is a graphical marker in upper left corner shape that indicates that Task is a Script Task (see Figure Group Order oczekiwania na 0.). Pool A User Task is a typical workflow Task where a human performer performs Task with assistance a stware application and is scheduled through a task list manager some sort. Figure 0.5 - A Receive Task Object Gateways Termination User Task Non `$ A Receive Task object shares same shape as Task, which is a rectangle that has rounded corners. However, re is an unfilled envelope marker ( same marker as a catch ) in upper left corner shape that indicates that Task is a Receive Task. Figure 0.3 - A Send Task Object A Receive Task is ten used to start a Process. In a sense, Process is bootstrapped by receipt. In order for Receive Task to instantiate Process its instantiate attribute MUST be set to true and it MUST NOT have any incoming Sequence Flow. 4! BPMN v.2.0 ang. modeling notation (OMG, 20) inne: Petri-net, YAWL, UML, (Waske, 202; Sawicki, 203) Receive Task The actual Participant from which is received can be identified by connecting Receive Task to a Participant using a Flows within definitional Collaboration Process see Table 0.. Non Table 0.93 and ir Markers into three types, based on ir position in : start events(po korektach) Zax $$ are used to trigger es, intermediate events can delay es, or y can occur during es. events signal termination es. Odmowa Top play a central rolefor in management, since y are The notational elements event trigger types are shown in Figure 4.80. A Rule Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a marker realizacji distinguishes shape from or Task types (as shown in Figure 0.9). glue between situations in organizations and es that will be that en Nonzlecenia Brak możliwości Poinformowano Table 0.93 and ir Markers acted if se situations occur. in a can be partitioned realizacji zlecenia klienta o braku Rule możliwości realizacji into three types, based on ir position in : start events możliwości zlecenia are used to trigger es, intermediate events can delay es, or y warunkowego Stwierdzone przyjęcia zlec. can occur during es. events signal termination es. 4.7 Process Modeling Notation 209 Top- zaległości Figure 0.9 - A Rule Task Object Wpłynęło zlecenie The notational elements for event trigger types are shown in Figure 4.80. Baza klientów na pojazd 32EUR The Rule Task inherits attributes and model associations Activity (see Table 0.3). Table 0. Non presents additional attributes Rule Task. Warunkowo wiarygodności przyjęto zlecenie associations Rule klienta Table 0. Rule Task attributes and model do realizacji Artefacts Connecting ObjectsDescription/Usage Attribute Name Flow Objects A Rule Task object shares same shape as Task, which is a rectangle that has rounded corners. is used to depict contents However, re is a graphical marker in upper left corner A shape that indicates that Taskisaa communication between two Participants (as Rule Task (see Figure 0.). defined by a PartnerRole or a PartnerEntity see on page 93). Fork 26 Odrzucenie zlecenia BPMN uses term fork to refer to dividing a path into two or more parallel 63 paths (also known as an AND-Split). It is a place in Process where activities can be performed concurrently, rar than Figure 0.8 - A Manual Task Object sequentially. There are two options: See Manual There are two options: Task on page 65 within larger section Human Interactions for details Manual Tasks. Outgoing Sequence Flows can be used (see figure top-right). This represents uncontrolled flow is preferred method for most situations. Outgoing Sequence Rule Flows can be used (see figure top-right). This representsa uncontrolled flow istask provides Rule preferred method for most situations. a mechanism for Process to provide input to a Rules Engine and to get output calculations that Rules Engine might provide. The InputOutputSpecification to and receive data from Rules Engine. A Parallel Gateway can be used (see figure bottom-right). This will be used rarely, usually in combination with or Gateways. A Parallel Gateway can be used (see Task (see page 2) will allow Process to send data figure bottom-right). This will be used rarely, usually in combination with or A Rule Task object shares same shape as Gateways. 2 26 Task, which is a rectangle that has rounded corners. However, re is a graphical marker in upper left corner shape that indicates that Task is a Rule Task (see Figure 0.). Fig. 4.78. Process Modeling Notation: categories elements Rys. 2.9. Model procesu weryfikacji i przydziału zlecenia przewozowego do realizacji, opisany w notacji BPMNProcess v.2.0model (poand korektach) Notation, v2.0 26 63 Since goal this example is to introduce core elements, simplifications are in place: model provides a simplified view how review es are actually conducted. In addition, re are many authors and re are also many reviewers. For convenience, just one author and one reviewer are shown. As will be discussed below, situations in which multiple participants are involved in same role cannot be covered conveniently. The pools in this example represent roles and not concrete participants in a. Each role at run time has multiple concrete participants who are actually involved in instance. The BPMN standard indicates that a pool represents a participant in a. It is also acts as a swimlane and a graphical container for partitioning a set activities from or pools, usually in context B2B situations. The starts when PC Chair is asked to organize scientific program a conference. This is reflected by start event at PC Chair. An event is something that happens during course a Wpłynęło zlecenie. These events a ect Wpłynęło flow zlecenie and usually have na pojazd pojazd 32EUR a cause (trigger) or an impact (result). na are circles with open centres do8eur to allow internal markers to di erentiate di erent triggers or results. The activity enacted first is publication a call for papers with detailed information on conference, such as name and location, and also information regarding topics addressed by conference. The receipt a message can be an event that is Zlecenie relevant for. This concept is used in sample when published call for papers activity sends a message that author receives. Receiving thiswiarygodności message is represented by start event author. The cause this event is receiving klienta 36 Narzędzia i notacje w BPM Wpłynęło zlecenie na pojazd 32EUR 26 Notacja EPC Baza klientów Wpłynęło zlecenie na pojazd do8eur wiarygodności klienta Wprowadzanie zlecenia do systemu Przydzielanie zlecenia do pojazdu NaChwilowo koncie klienta brak Zlecenie dostępnych przydzielono do widnieją zaległe pojazdów pojazdu płatności zleceń Zamówienie dostępne w systemie System dyspozytorski Na koncie klienta brak jest zaległych płatności Na koncie klienta widnieją zaległe płatności Na koncie klienta brak jest zaległych płatności System dyspozytorski Zlecenie Baza klientów 36 Baza klientów możliwości warunkowego przyjęcia zlecenia Warunkowo przyjęto zlecenie do realizacji Dyspozytor Oczekiwanie na dostępność wolnych pojazdów jest zbyt długie Brak możliwości realizacji zlecenia Baza klientów Odmowa realizacji zlecenia a poinformowano o braku możliwości realizacji zlecenia 22 Rys. 2.7. Model procesu weryfikacji i przydziału zlecenia przewozowego do realizacji, opracowany w notacji EPC (po korektach)

Depending on kind diagram (abstract or global), The notational elements BPMN regarding transactional behaviour message flows can link pairs flow objects, pools, and events. Detailed rules es (transaction groups, compensation flow, and cancellation) on message flow connections are discussed below. A Flow is used to will not be covered, because ir semantics is not laid out in sufficient detail show flow messages between two participants that are prepared to send and precision. and receive m. In BPMN, two separate Pools in Diagram will represent two participants (e.g., entities or roles). The notational elements BPMN regarding transactional behaviour es (transaction groups, compensation flow, since and cancellation) play a central role in management, y are will not be covered, because ir semantics is not laid out in sufficient detail glue between situations in organizations and es that will be enand precision. acted if se situations occur.notacja in a can be partitioned Narzędzia i notacje w BPM BPMN 2.0 into three types, based on ir position in : start events Zax $$ Escala into three types, based on ir position in to : start events are used trigger es, intermediate events can delay es, or y Zax $$ are used to trigger es, intermediate events can delay es, or y can occur during es. events signal termination es. can occur during es. events signalodmowa termination es. play a central rolefor in management, since y are The notational elements event trigger types are shown in Figure 4.80. Conditi realizacji play a central in management, since y are glue between situations in organizations and es that will berole enzlecenia are The notational elements for event trigger types shown in Figure 4.80. A Rule Task is a round Table 0.93 and ir Markers acted if se situations occur. in a can be partitioned distinguishes shape from o in organizations and es that will be that eninto three types, based on irglue positionbetween in situations : start events możliwości E are used to trigger es, intermediate events can delay es, or y warunkowego przyjęcia zlec. acted if se situations occur. in a can be partitioned can occur during es. events signal termination es. Notation 4.7 Process Modeling 209 The notational elements for event trigger types are shown in Figure 4.80. Rule Baza klientów types, based on ir position in into three : start events Compe możliwości wiarygodności klienta Artefacts are used to triggerconnecting es, intermediate events can delay es, or y Objects warunkowego Flow Objects Stwierdzone przyjęcia zlec. can occur during es. events signal termination es. Sequence Flow System dyspozytorski Process Modeling Notatio Wprowadzanie4.7 zaległości Conditi Figure 0.9 A Rule T Wpłynęło zlecenie zlecenia do The notational elements for event trigger types are shown in Figure 4.80. na pojazd 32EURsystemu The Rule Task inherits ActivitiesFig. 4.80.Place types in BPMN, Object Management Group (2006) presents additional attributes Flow Termina Group Order wiarygodności `$ Table 0. Rule Tas events can have di erent triggers. klienta Rule Przydzielanie Artefacts! In case paper is rejected, join gateway is triggered. To clarify be haviour split gateway, outgoing sequence flows are associated with respective annotations. Table 0.93 and ir Markers 4.7 Process Modeling Notation 2 The participants that cooperate in context a comtable 0.93 and ir Markers municate by sending and that receiving messages. diagrams, final version paper will be printed In in conference proceedings. Top messages arepaper represented by message Typically a message flow connects In case is rejected, joinflow. gateway is triggered. clarify and betable 0.93 To ir Markers Non Nonan activity participant activity sequence or an event anor participant. haviour one split gateway, to anoutgoing flows are associated with (abstract or global), Depending on kind diagram respective annotations. Messa message flows can link pairs flow objects, pools, and events. Detailed rules Top Table 0.93 and ir Markers Top The participants that cooperate in context a com Nonon messagebyflow connections are discussed below. Flow is used to Nonmunicate sending and receiving messages. In A diagrams, Sub-Proce show flow messages by between twlow. participants are prepared to send messages are represented message Typicallythat a message flow connects Non Top 0.9 Send Task model associations Table and receive m. In BPMN, two separate Pools in Diagram will represent Escalat Nonan activity one participant to an activity or an event anor participant. Interruptin Non two participants (e.g., entities or roles). Attribute Name Description/Usage Depending on kind diagram (abstract or global), The notational elements BPMN regarding transactional behaviour messageref : [0..] A for messageref attribute MAY be entered. This indicates that message flows can link pairs flow objects, pools, Table and 0.93 events. Detailed rules and ir Markers es (transaction groups, compensation flow, and cancellation) will be sent by Task. The in this context is on message flow connections are discussed below. A Flow is used to will not be covered, because ir semantics is not laid out in sufficient detail equivalent to an out-only message pattern (Web service). One or more show flow messages between two participants that are prepared to send corresponding outgoing Flows MAY be shown on diagram. and precision. Top However, display Flows is NOT REQUIRED. The and receive m. In BPMN, two separate Pools in Diagram will represent Nonis applied to all outgoing Flows and will be sent down Non two participants (e.g., entities or roles). Table 0.93 all and Flows ir Markers outgoing at completion a single instance Task. The notational elements BPMN regarding transactional behaviour operationref: Operation This attribute specifies operation that is invoked by Send Task. play es (transaction groups, compensation flow, since and cancellation) a central role in management, y are implementation: string = Top- specifies technology that will be This attribute used to send and receive will not be covered, because ir semantics is not out in sufficient detail glue between situations in organizations andlaid es that will be en NonCompe ##webservice s. Valid values are "##unspecified" for leaving implementation Nonand precision. can be partitioned acted if se situations occur. in a! Table 0.9 Send Task model associations Attribute Name Description/Usage messageref: [0..] A for messageref attribute MAY be entered. This indicates that will be sent by Task. The in this context is equivalent to an out-only message pattern (Web service). One or more corresponding outgoing Flows MAY be shown on diagram. However, display Flows is NOT REQUIRED. The is applied to all outgoing Flows and will be sent down all outgoing Flows at completion a single instance Task. operationref: Operation This attribute specifies operation that is invoked by Send Task. implementation: string = ##webservice technology open, "##WebService" for Web service technology or a URI This attribute specifies technology that will be used to send and receive s. Valid values are "##unspecified" for leaving implementation technology open, "##WebService" for Web service technology or a URI identifying any or technology or coordination protocol A Web service is default technology. any or technology or coordination protocol A Web service is Table 0.93 identifying and ir Markers default technology. A Send Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a filled envelope marker that distinguishes shape from or Task types (as shown in Figure 0.3). Receive Task Receive Task A Receive Task is a simple Task that is designed to wait for a to arrive from an external Participant (relative to Process). Once has been received, Task is completed. A Rule Top Nonis a simple Task that is designed to wait for a to arrive from an external Participant Non(relative to Process). Once has been received, Task is completed. Poinformowano Brak możliwości realizacji zlecenia Participant using a Flows within definitional Collaboration Process see Table 0.. A Receive Task is ten used to start a Process. In a sense, Process is bootstrapped by receipt. In order for Receive Task to instantiate Process its instantiate attribute MUST be set to true and it MUST NOT have any incoming Sequence Flow. Rule A Receive Task object shares same shape as Task, which is a rectangle that has rounded corners. However, re is an unfilled envelope marker ( same marker as a catch ) in upper left corner shape that indicates that Task is a Receive Task. Figure 0.3 - A Send Task Object Stwierdzone zaległości A Receive Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes an unfilled envelope marker that distinguishes shape from or Task types (as shown in Figure 0.5). If instantiate attribute is set to true, envelope marker looks like a (as shown in Figure 0.6). Wpłynęło zlecenie na pojazd 32EUR Figure 0.5 - A Receive Task Object Dział transportu 4! Brak zaległości Dyspozytor Flow Objects Annotation Table 7.2 - BPMN Extended Modeling Elements s provide information about what Activities require to be performed and/or what y produce (see page 205), s can represent a singular object or a collection objects. Data Input and Data Output provide same information for Processes. 60 zamówienia do pojazdu Datav2.0 Process Model Data and Notation, Object Objects provide information about what 4! Fork A is used to depict contents a communication between two Participants (as defined by a PartnerRole or a PartnerEntity see on page 93). Dział transportu Data Input There are two options: Chwilowy brak wolnych pojazdów Sequence See User Task on page 63 within larger section Human Interactions for details User Tasks. Figure 0.8 - A Manual Task Object Data Objec (Collection) Manual Task See Manual Task on page 65 within larger section Human Interactions for details Manual Tasks. Wpłynęło zleceniedata na pojazd do8eur 64 Zlecenie A Manual Task is a Task that is expected to be performed without aid any execution engine or any application. An example this could be a telephone technician installing a telephone at a customer location. Data Output A Rule Task provides a mechanism for Process to provide input to a Rules Engine and Data to getinput A Manual Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a hand figure output calculations that Rules Engine might provide.process The InputOutputSpecification Model and Notation, v2.0 marker distinguishes shape from or Task types (as shown in Figure 0.7). Task (see page 2) will allow Process to send data to and receive data from that Rules Engine. Rule Object A Rule Task object shares same shape as Task, which is a rectangle that has rounded corners. is used to depict contents However, re is a graphical marker in upper left corner A shape that indicates that Taskisaa communication between two Participants (as Rule Task (see Figure 0.). Fork BPMN uses term fork to refer to dividing a path into two or more parallel 63 paths (also known as an AND-Split). It is a place in Process where activities can be performed concurrently, rar than Figure 0.8 - A Manual Task Object sequentially. There are two options: See Manual Task on page 65 within larger section Human Interactions for details Manual Tasks. implementation: string = 6 ##unspecified Flow 26 Odrzucenie zlecenia Zlecenie defined by a PartnerRole or a PartnerEntity see on page 93). A User marker t 26 Figure 0.20 - A Script Task Object Data Output Termination BPMN uses term fork to refer to dividing a path into two or more parallel paths (also known as an AND-Split). It is a place in Process where activities can be performed concurrently, rar than sequentially. Activities require to be performed and/or what y produce (see page 205), s Task Object can represent a Figure singular 0.7 object -oraa User collection objects. Data Input and Data Output provide same information for Processes. A User stware Connecting Objects Attribute Name Table 7.2 - BPMN Extended Modeling Elements User Ta Zlecenie przydzielone do pojazdu Figure 0.5 - A Receive Task Object Association Data Objec (Collection) Lane 26 A corners. User Task is a typical workflow Task where a human performer performs Task with assistance a A Script Task object shares same However, re Manual Taskshape as Task, which is a rectangle that has rounded stware application and is scheduled through a task list manager some sort. is a graphical marker in Aupper left corner shape that indicates that Task is a Script Task (see Figure Manual Task is a Task that is expected to be performed without aid any execution engine or User Task a roundedlocation. corner rectangle that MUST be drawn with a single thin line and includes a human figure 0.). any application. An example this could be a telephone technician installing aatelephone at ais customer events can have di erent triggers. Swimlanes Pool A Script Task is executed by a engine. modeler or implementer defines a script in atable language that additional model associations Send Task. 0.9 presents Process Model Notation, v2.0 Figure 0.7 - A User Task ObjectTheand engine can interpret. When Task is ready to start, engine will execute script. When script is completed, Task See User Task on page 63 within larger section Human Interactions User for details User Tasks. Task will also be completed. Fig. 4.80. types in BPMN, Object Management Group (2006) Za$ Data Input. If Data Input is present, it MUST have an ItemDefinition equivalent to one defined by associated. At execution time, when Send Task is executed, data automatically moves from Data Input on Send Task into to be sent. If Data Input is not present, will not be populated with data from Process. Script Task Zbyt długi okres oczekiwania na Process Model and Notation, v2.0 marker that distinguishes shape from or Task types (as shown in Figure 0.7). wolny pojazd 26 Manualrectangle Task is a that rounded corner that MUST be drawn with and a single thin line and includes A Script Task is a roundedacorner MUST berectangle drawn with a single thin line includes a marker that a hand figure distinguishes shape in from or 0.20). Task types (as shown in Figure 0.7). distinguishes shape frommarker orthat Task types (as shown Figure Dostępne pojazdy Gateways Termination Figure 0.4 - The Send Task and Receive Task class diagram Zlecenie Termination A User Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a human figure Description/Usage marker that distinguishes shape from or Task types (as shown in Figure 0.7). This attribute specifies technology that will be usedato implement Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes an unfilled Receive Rule Task. Valid values are "##unspecified" for leaving implementation technology open, "##WebService" for envelope marker that distinguishes shape from or Task types (as shown in Figure 0.5). If instantiate Web service technology or a URI identifying any or technology or coordinationtheprotocol. attributes and model associations Activity (see Table 0.3). In addition following attribute constraints is Send settask toinherits true, marker like a (as shown in Figure 0.6). apply when Send Taskenvelope references a : The Send looks Task has at most one inputset and one The default technology for this task is unspecified. implementation: string = 6 ##unspecified Wpłynęło zlecenie na pojazd do8eur NonA Receive Task object shares same shape as Task, which is a rectangle that has rounded corners. However, re User Task Warunkowo is an unfilled envelope marker ( same marker as a catch ) in upper left corner shape that A User Task is a typicalprzyjęto workflow Task where a human performer performs Task with assistance a zlecenie do realizacji indicates that Task is a Receive Task. Table 0. Rule Task attributes and model associations stware application and is scheduled through a task list manager some sort. Attribute Name A Receive Task is ten used to start a Process. In a sense, Process is bootstrapped by receipt. In order Receive Task to instantiate Process its instantiate attribute MUST be set to true Top-for and it MUST NOT have any incoming Sequence Flow. Non- Figure 0.9 - A Rule Task Object The Rule Task inherits attributes and model associations Activity (see Table 0.3). Table 0. presents additional attributes Rule Task. Rule klienta o braku The actual Participant from which is received możliwości realizacjican be identified by connecting Receive Task to a Participant using a Flows within zlecenia definitional Collaboration Process see Table 0.. `$ Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a marker A Receive Task distinguishes The actual Participant from which is received can be identified by connecting that Receive Task to a shape from or Task types (as shown in Figure 0.9). Brak zaległości W Script Task Termin A Script Task is executed by a bu Figure engine can interpret. When See Use Task will also be completed. ActivitiesFig. 4.80.Place types in BPMN, Object Management Group (2006) A Script Task object shares sa Flow a graphical marker in upper l Group 23is0.). Order Fig. 4.78. Process Modeling Notation: categories elements Outgoing Sequence Flows can be used (see figure top-right). This represents uncontrolled flow is preferred method for most situations. A Parallel Gateway can be used (see figure bottom-right). This will be used rarely, usually in combination with or Gateways. Outgoing Sequence Rule Flows can be used (see figure top-right). This representsa uncontrolled flow istask provides Rule preferred method for most situations. a mechanism for Process to provide input to a Rules Engine and to get output calculations that Rules Engine might provide. The InputOutputSpecification to and receive data from Rules Engine. A Parallel Gateway can be used (see Task (see page 2) will allow Process to send data figure bottom-right). This will be used rarely, usually in combination with or A Rule Task object shares same shape as Gateways. Task, which is a rectangle that has rounded corners. However, re is a graphical marker in upper left corner shape that indicates that Task is a Rule Task (see Figure 0.). Manual A Manu any appl Model and Notation, v2.0 Rys. 2.9. Model procesu weryfikacji i przydziału zlecenia przewozowego do realizacji, opisany w notacji BPMN v.2.0model (poprocess korektach) Process and Notation, v2.0 Manu A Script Task is a roundedacorne events can have di erent triggers. 63 distinguishes shape frommarker ort Since goal this example is to introduce core elements, simplificagateways Association tions are in place: model provides a simplified view Annotation how Termination review es are actually conducted. In addition, re are many authors and re are also many reviewers. For convenience, just one author and one Fig. 4.80. types in BPMN, Object Management Group (2006) Figure Data Objec (Collection) reviewer are shown. As will be discussed below, situations in which multiple See Ma Figure 0.20 A Script Task Obje participants are involved in same role cannot be covered conveniently. Busines The pools in this example represent roles and not concrete participants in a Data Input Data Output A Busin ARIS who co to takiego? outp events can have di erent triggers. 64. EachSwimlanes role at run time has multiple concrete participants Task (se are actually involved in instance. The BPMN standard A Busin Process Model and Notation, v2.0 Process Model and Notation, v2.0 Howeve indicates that a pool represents a participant in a. It is also acts as a Rule Ta Zlecenie swimlane and a graphical container for partitioning a set activities from or pools, usually in context B2B situations. The starts when PC Chair is asked to organize scientific Za$ program a conference. This is reflected by start event at PC Chair. An event is something that happens during course a. These events a ect flow and usually have a cause (trigger) or an impact (result). are circles with open centres to allow internal markers to di erentiate di erent triggers or results. The activity enacted first is publication a call for papers with detailed information on conference, such as name and location, and also Rys. 2.9. weryfikacji i przydziału zlecenia przewozow information regarding topics addressed by conference. TheModel receipt procesu a message can be an event that is relevant for. This concept is used in sample when published call for papers activity sends a message that author receives. Receiving this message is represented by 36 start event author. The cause this event is receiving 36 36 Dyspozytor Table 7.2 - BPMN Extended Modeling Elements s provide information about what Activities require to be performed and/or what y produce (see page 205), s can represent a singular object or a collection objects. Data Input and Data Output provide same information for Processes. A is used to depict contents a communication between two Participants (as defined by a PartnerRole or a PartnerEntity see on page 93). Fork BPMN uses term fork to refer to dividing a path into two or more parallel paths (also known as an AND-Split). It is a place in Process where activities can be performed concurrently, rar than sequentially. Lane Pool Narzędzia i notacje w BPM There are two options: Outgoing Sequence Flows can be used (see figure top-right). This represents uncontrolled flow is preferred method for most situations. A Parallel Gateway can be used (see figure bottom-right). This will be used rarely, usually in combination with or Gateways. Fig. 4.78. Process Modeling Notation: categories elem Since goal this example is to introduce core elements, s tions are in place: model provides a simplified vie review es are actually conducted. In addition, re are many and re are also many reviewers. For convenience, just one author 24 reviewer are shown. As will be discussed below, situations in which participants are involved in same role cannot be covered conven The pools in this example represent roles and not concrete particip. Each role at run time has multiple concrete particip actually involved in instance. The BPMN Piotr Sawicki are Zarządzanie procesami 2 indicates that a pool represents a participant in a. It is also

Źródła wiedzy Bibliografia materiały wykładowe Sawicki P. http:// www.put.poznan.pl/~piotr.sawicki 25 Źródła wiedzy Bibliografia Scheer A.-W. ARIS Process Modeling Springer, 2000 Davis R., Brabänder E. ARIS Design Platform. Getting started with BPM Springer, 200 26 3

Źródła wiedzy Bibliografia Weske M., Process Management. Concepts, Languages, Architectures Springer, 202 Scheer A-W., Abolhassan R., Jost W., Kirchmer M. Process Excellence. ARIS in Practice Springer, 2004 27 Źródła wiedzy Bibliografia Gabryelczyk R. ARIS w modelowaniu procesów biznesu Difin, 200 studia i rozprawy Piotr SAWICKI WIELOKRYTERIALNA OPTYMALIZACJA PROCESÓW W TRANSPORCIE Sawicki P. Wielokryterialna optymalizacja procesów w transporcie ITE, Radom, 203 28 4

Podsumowanie Bibliografia Melão N., Pidd M., A conceptual framework for under-standing and modeling. Information System Journal, 2000, vol. 0, no. 2, s.05-29. Object Management Group, model and notation (BPMN) Version 2.0, January 20, http://www.omg.org/spec/ BPMN/2.0 (dostęp: 08.02.203) Sawicki P., Wielokryterialna optymalizacja procesów w transporcie. ITE, Radom, 203 Scheer A.W., ARIS - Process Frameworks, Berlin, Springer-Verlag, 999. Weske M., Process Management. Concepts, Languages, Architectures. Springer-Verlag Berlin Heidelberg, 202 29 Podsumowanie Zapraszam do dyskusji i zadawania pytań 30 5

Tytuł: Wprowadzenie. Kluczowe elementy BPM Autor: Piotr SAWICKI Zakład Systemów Transportowych WMRiT PP piotr.sawicki@put.poznan.pl www.put.poznan.pl/~piotr.sawicki www.facebook.com/piotr.sawicki.put Przedmiot: Zarządzanie procesami transportowo-logistycznymi Specjalność: Logistyka transportu Wersja: 204.0.06 6