Hi @joren.kamer12 

Can you please tell us how you are calculating the avg throughput time based on the priority_display_value?

Usually we need minimum two activity or event to calculate the avg throughput time.

I can see some blank value as well for priority_display_value dimension.

Hi Rohit,

Thank you for your reply. I have tried four different methods of calculating the avg throughput time for priority 4 incidents.

Yesterday, three of them yielded the same result and one differed.

However, now I notice a difference. Now it is 2 vs 2.

With method 1&2 I get a different result from method 3 & 4

1:

use the standard formula and apply a selection through attribute selection. Where I navigate to priority_display_value and select '4 - Low'.

Standard formula = AVG(CALC_THROUGHPUT(ALL_OCCURRENCER'Process Start'] TO ALL_OCCURRENCEC'Process End'], REMAP_TIMESTAMPS("_CLS_CHANGE_ACTIVITY"."EVENTTIME", DAYS)))

2: use the component filter: FILTER "change_request"."priority_display_value" = '4 - Low' in combination with the same formula

3: use a CASE WHEN statement directly in the formula:

AVG(

  CASE WHEN "change_request"."priority_display_value" = '4 - Low'

  THEN

  CALC_THROUGHPUT(ALL_OCCURRENCEC'Process Start'] TO ALL_OCCURRENCE�'Process End'], 

  REMAP_TIMESTAMPS("_CLS_CHANGE_ACTIVITY"."EVENTTIME", DAYS))

  ELSE NULL END)

4: Create an olap table. Where dimension = Priority_display_value

and KPI = AVG(CALC_THROUGHPUT(ALL_OCCURRENCEn'Process Start'] TO ALL_OCCURRENCE['Process End'], REMAP_TIMESTAMPS("_CLS_CHANGE_ACTIVITY"."EVENTTIME", DAYS)))

Case count is significant: 30,594 for priority 4