...
Processing time is entered on each activity
The process has no loop because no minimum term can be calculated anymore (see CPM module deactivated)
Exact Exactly one terminating end has to be included in the process model (a normal end event is not sufficient)
CPM calculation is activated in the process
...
The critical path for processes with multiple ends is can be calculated under the assumption that there is a “positive” process endby using the https://tim-doc.atlassian.net/wiki/spaces/DE/pages/304480257/PredefinedDecisionHandler?search_id=339a3f31-993e-4859-8340-c71de9af28db. The following example clarifies the approach.
...
The process consists of three activities with a duration of one hour each. However, the process can terminate after task 1 and task 2 respectively. Based on this assumption, the process can either have a duration of one hour, two hours or three hours. In order to provide a consistent , process independent CPM calculation, the system calculates the critical path based on the “positive” process end. For the process on hand the critical path is therefore calculated considering Task 1, Task 2 and Sell Producthas to be informed which path is the most probable one by defining it via https://tim-doc.atlassian.net/wiki/spaces/DE/pages/304480257/PredefinedDecisionHandler?search_id=339a3f31-993e-4859-8340-c71de9af28db .
Processes with loops
The CPM calculation for processes with loops is done in similar fashion. Instead of assuming a positive process end, the critical path is calculated while ignoring the process' loopsEither all loop transitions are marked by “_loop” in their name or by using the https://tim-doc.atlassian.net/wiki/spaces/DE/pages/304480257/PredefinedDecisionHandler?search_id=339a3f31-993e-4859-8340-c71de9af28db . This is because a CPM calculation with loops is not possible. Loops can be run through arbitrarily. Therefore, the critical path can only be calculated, while ignoring process loops entirely. The following example clarifies the approach.
...