Differences

This shows you the differences between two versions of the page.

--- en:rule:different_rhytms [2024-08-28 13:15] – Embedded diagram updated Anatoly Belaychuk
+++ en:rule:different_rhytms [2024-11-02 13:54] (current) – [Notes] Anatoly Belaychuk
@@ Line 1: / Line 1: @@
-====== 0-TBD Activities performed in different rhytms are separate processes ======
+====== Activities performed in different rhytms belong to different processes ======
 {{tag>process collaboration}}
-{{en:underconstruction.png?nolink&200|}}
+If one activity is performed once per month and another every time a client's order received then there are two different processes.
-Short description.
 ===== ✔ How to =====
@@ Line 90: / Line 87: @@
 ===== Notes =====
-  * Extra comments (optional)
+From performers' (organizational, functional) point of view, they update the price list first, then develop the sales plan and finally fulfill the deal.
+Yet BPMN diagram should be treated literally so if we depict the process this way (see [[#how not to]]) then it would mean that we close exactly one deal per month, which obviously is not the case.
-===== Exceptions =====
+As for the price list, it's usually updated not by a schedule but in responce to market events that may happen any time.
-  * Exceptions, if any
+Therefore, there are three different events in this case, namely a voluntaristic decision to adjust the price list, a monthly deadline for a sales plan, and a purchase request obtained from a client.
+It means three different (yet connected) processes.
+The [[#how to]] diagram depicts them as black box pools, assuming that each process would be expanded on a separate diagram.
+BPMN spec doesn't allow to connect a data association to a pool so one need to use directed associations here (which looks exactly the same).
 ===== See also =====
-  * References to similar rules (optional)
+  * [[single_process]]
 ===== Author(s) =====
  --- //[[user:bell|Anatoly Belaychuk]] 2024-08-28 13:01//