Hi, we have build up a deep-dive analysis on cycle times where viewers can select two activities to measure the throughput time for this subprocess. However, the time never matches the time on the Process Explorer when switching to Throughput Time (MEDIAN). Here is the formula we are using to calculate the throughput time between the selected activities from the drop down:
MEDIAN(CALC_THROUGHPUT(FIRST_OCCURRENCE[<%=From%>] TO FIRST_OCCURRENCE[<%=To%>], REMAP_TIMESTAMPS("_CEL_P2P_ACTIVITIES".“EVENTTIME”, <%=unit%>)))
The variables [<%=From%>], [<%=To%>] and <%=unit%> work fine and are correctly connected to the dropdown menu for the activities and the unit (I’ve ensured by hardcoding two activities and the respective unit as a test in the formula --> same result than with the variables and selecting the before hardcoded activities from the dropdown).
I guess the difference might come from different variants between two activities. How does the Process Explorer work for throughput times (taking all variants into account in the happy path for the throughput time between two activities or only taking the time for the currently shown variants)?
E.g. analysing “Release Purchase Requisition” to “Create Purchase Order Item”:
In the Process Explorer I’ve 146 hours between those two activities whereas in the subprocess calculated with the formula from above I end up with 166 hours. When selecting activities which are usually not followed after one another, the differences becomes significantly higher.