1. 
   start and end activities:
   This cannot be done in the analysis but has to be set in the datamodel.
2. 
   The more complex question:
   a) I guess this should work by removing teh start and ende columns in your activities example. Good thing to know is that Celonis groups records by the unique combinations of the dimension values. Because start & ende are included, this results in 3 rows. If you remove/hide these 2 dimensions, there should be the 2 rows you expect. You KPI duration is already a SUM so that should work as desired.
   b) Where is target time stored? Is this per case? Or is this a global thing which you can store in a variable?
   c) and d) should follow if a) is solved, so lets focus on a) first
   

Hi Joos,

thanks for the reply!

1. I know it should be in the datamodel, but where? Celonis only offers me to select CASE, ACTIVITY, TIMESTAMP and optional SORTING no second timestamp
2. The target time can be unique for every combination of CASE and WORKCENTER. In order to avoid redundance, I created another table in data model. Looks like this now:

image694268 6.19 KB

Took me a while, but now I can the correct results with these formulas:

DURATION = SUM(MINUTES_BETWEEN(EVENTLOG_csv.START, EVENTLOG_csv.ENDE))

TIME_PER_PIECE = KPI(DURATION) / AVG(PU_AVG(DOMAIN_TABLE(CASES_csv.CASE), CASES_csv.QUANTITY))

DEVIATION = KPI(TIME_PER_PIECE) -AVG(PU_AVG(DOMAIN_TABLE(TARGETS_csv.ARBEITSPLATZ, TARGETS_csv.CASE), TARGETS_csv.TARGET_PROCESS))

image728121 3.88 KB

Am I on the right track so far? Now how do I make use of the results in DEVIATION for further calculations, e.g. average on work center (should be 0,666)?

Best wishes

Patrick

Hi,

I found the solution by myself. The problem was in my data model. Before it looked like this:

CASES <-- (1:n)-- ACTIVITIES --(n:1)> TARGET TIMES

Therefore I was not able to pull QUANTITY from the CASES-Table. I switched the model to:

ACTIVITIES --(n:1)> TARGET TIMES (n:1)> CASES

And after a few changes to the KPIs I reached the desired solution and was also able to create a histogram! Guess it took me a while to understand how PU-functions work

Thanks for helping, @joosbuijs!