====== Activities performed in different rhytms belong to different processes ======
{{tag>process collaboration}}
If one activity is performed once per month and another every time a client's order received then there are two different processes.
===== ✔ How to =====
===== ✘ How NOT to =====
Flow_05txx3hFlow_1fo0r26Flow_05txx3hFlow_1i6r8h2Flow_1i6r8h2Flow_095hc6eFlow_095hc6eFlow_1fo0r26
===== Notes =====
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.
As for the price list, it's usually updated not by a schedule but in responce to market events that may happen any time.
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 =====
* [[single_process]]
===== Author(s) =====
--- //[[user:bell|Anatoly Belaychuk]] 2024-08-28 13:01//