I think one of the easiest ways is to use "Case Explorer". Here you can find the case duration and by clicking on each case you can find the case´s activities and their duration. 

True. I see the duration. In the Training environment, the values are filled with "1s". To have real numbers, would not be necessary to have an activity table with two timestamps: time start and time end? In other case, the timestamp says only when the activity started. The next activity and time stamp tell about the start of this activity. This time difference contains both, the duration of the previous activity and the waiting time in between.

I had the same concern. I find that in the typical engagements that's not relevant, mainly as each activity tends to be an IT transaction, thus you can assume a negligible duration and no queuing of cases.

But, let's say you have manual activities. Like 2 departments using a kanban approach (thus, queues) and that the "trasmission" of a case between the stations is "physical" (like sending a report by mail)... then you can't find the time in each of the station (that will be the "activity" duration), nor the "transmission" duration (that hasn't a clear correlation with Celonis concepts, I think)

I imagine that in logistics, or manufacturing, and maybe other domains, this can be a problem.

Just my 0,02 €

Hi Guillermo,

that is my concern too. I work often with lab processes, and between activities, there are waiting times for different reasons. For my customers, or as the owner of a process, it would be really interesting to know the duration of the activities, and the duration of the "waiting times" between the activities, because there are many external and internal factors that can influence them.

My example would be the processing of samples in a laboratory. The order entry doesn't occur necessarily at the same time as the sample entry, therefore there is a time in between, that depends on the logistic that will deliver this sample.

I guess you can add TIME_END and/or DURATION fields to the activity table, and then use them for Process Explorer KPI's and others.... but it is a workaround....