The Step Summary area contains a Duration column, which displays the length of time that the step took to execute. This value represents the time to execute for the activity:

Therefore, it would seem logical that the duration time of the subprocess or call activity would equal the sum of the durations of all the steps in the subprocess, or the duration of the callable process.

However, the duration may actually be greater than the sum of its internal objects. This is because the subprocess or call activity duration also includes communication time, as well as time taken by minor transport delays caused by network latency.

In addition, when the WaitForSubprocess value in the service pub.prt.SubprocessModel is set to false for a dynamic reference process, the call activity step in the parent is shown as ended as soon as the child instance is started. Therefore, the duration for that step iteration in the parent is initially very short. After the child instance completes, the duration value changes to the actual duration of the child instance. Monitor computes the duration from the start record to whatever the last record is for a step.

In cases where you use the dynamic reference process method to initiate multiple instances of a child model, the duration value represents the duration of the longest of the child instances that were run, and not the sum of all the durations of all the children.