Throughput Time differs in OLAP table and other Components

Hi!

I am using the same simple formula to calculate the average throughput time in the OLAP table and in the Gauge Component. OLAP table has dimensions (e.g. Job Family). The case is a Vacancy ID, and there are 2 basic tables in the data model: dimensions table (containing Job Family attribute) and facts table (activity table for the Vacancy status changes) where Vacancy ID is a key. So the data model is pretty simple as well.

Could you please help me to figure out why I am constantly getting different results when I am comparing throughput time calculated based on OLAP table selection with the throughput time calculated by a single component (e.g. Gauge or Throughput Time Search)?

Throughput Time Difference

Throughout Time formula:

TRIMMED_MEAN

(CALC_THROUGHPUT

(ALL_OCCURRENCEE'Process Start'] TO

ALL_OCCURRENCER'Process End'], REMAP_TIMESTAMPS("GTO_Application_Workflow_csv"."CHANGE DATE", DAYS)))

This topic can be related to https://www.celopeers.com/s/question/0D50700000GC6pMCAT/throughput-calculation-data-discrepancy and

https://www.celopeers.com/s/question/0D50700000GC78UCAT/getting-different-average-throughput-times-between-components-using-same-formula

Page 1 / 1

I've manually recalculated throughout for a small data sample in excel, and I've got the same result as using the Gauge component in Celonis. So the figures under question are the ones in the OLAP table.

Hi Mariana,

Did you also check this with an OLAP table where you only have the displayed formula as a KPI (i.e. removing all the other dimensions/KPIs)? It could be that due to a formula in another column, not all the cases could be bound in the dimension, thus leaving rows out.

For instance, if the employees column is empty (which is used in your table), it could be that those rows are not included also in the throughput time calculation.

Hi Mariana,

Did you also check this with an OLAP table where you only have the displayed formula as a KPI (i.e. removing all the other dimensions/KPIs)? It could be that due to a formula in another column, not all the cases could be bound in the dimension, thus leaving rows out.

For instance, if the employees column is empty (which is used in your table), it could be that those rows are not included also in the throughput time calculation.

Hi Jan-peter,

I've got your point, thank you very much for processing this question. I've tried hiding all the other fields except for the one which calculates throughput. Still, the deviation persists.

Throughput Time Difference2

Reply

ANY QUESTION?

MORE CELONIS

CHECK US IN

Reply

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded

ANY QUESTION?

MORE CELONIS

CHECK US IN