The Process Performance dashboard

You can use the Process Performance dashboard in Heritage Process Portal to get an overview of the processes that you are responsible for. You can identify processes that need attention, go to individual instances, and act to bring them back on track.

If you are responsible for more than one process, you can select the process to work on from the dashboard summary page. The Process Performance dashboard for an individual process contains the following pages:

Prerequisites

To work with the Process Performance dashboard, the following prerequisites apply:
  • To see the Process Performance dashboard, you must be a member of the Process Owner team.
  • To see a specific process, you must be a member of the team that is assigned to the Expose Performance Metrics setting for the business process definition. Only the default snapshot is considered when determining whether you have access to a process.
  • To see timing intervals in the Average Duration section, they must be specified for the business process definition.

Overview page

This page contains charts and graphs that help you visualize the progress of process instances. You can use the data that is provided to identify instances that need attention. In addition, you can filter the data using the search filter. All days and times are based on your time zone.
Attention:
  • If your administrator deleted completed instances from the system, these instances are not included in the performance statistics.
  • Versions of IBM® BPM earlier than V8.5 do not store the completion date for process instances. Depending on how your administrator set up the Heritage Process Portal index, the average instance duration and instance completion statistics might not include instances that were completed in an earlier version of IBM BPM.
The Overview page has the following sections:
Quick Stats
Provides an overview of the instances that are in progress. This section includes the average instance duration, and the total number of instances in progress, which are categorized as overdue, at risk, and on track instances. An at risk instance is determined by the average time to complete instances of this process. For example, if an instance is due today but people need three days on average to complete the outstanding work on the instance, then the instance is considered to be at risk.
Actions that you can take
  • Identify instances that are overdue or at risk by using the pie chart to filter the list of instances. Clear the filter by clicking the selected pie slice again.
Turnover Rate
Provides an overview of the rate at which process instances are started and closed; closed instances include both completed and terminated instances. The trend line indicates how the process is performing in general and whether the work on it is catching up or falling behind based on the difference between the instance arrival and closure rates.
Actions that you can take
  • Change the time interval that is used on the x-axis. For example, to investigate the instance closure or arrival rate during a day, change the time interval to Hours.
  • See the net change for a bar in the chart by hovering over the bar.
Average Duration
Provides different views of the average length of time that it takes to complete the tasks in the process. Only the statistics for closed instances are included in the views; closed instances include both completed and terminated instances.
Tip: If several tasks are close together on the timeline, use the zoom slider to see these tasks in more detail. However, the zoom slider is not available if the process completes in less than 10 minutes.
Tasks
The completed tasks in the process are shown as bars in the Gantt chart. The length of a bar indicates the average time that it takes to complete the task. The opacity of the bars indicates the percentage of instances in which the task occurs. The bars in the chart are staggered according to the average start time.

Reworked tasks are indicated by an extra bar on the chart; a bar is added every time that the task is reworked. A reworked task is a task that is performed multiple times. The reason for the rework might be because the work on the task does not meet the completion criteria. For example, if the work on a task requires an approval, and the approval is rejected, then the work on the task must be repeated one or more times until it is approved. The length of the bar indicates the average amount of time that is spent doing rework for the activity.

Timing Intervals
The bars in the chart show the average duration for the timing intervals.
Instances in Progress
Provides a list of the instances in progress. You can use the Quick Stats pie chart or the search filter to filter this list to identify the instances that need attention. Clear the filter by clicking the selected pie slice again.
Actions that you can take
  • See a summary of the instance that shows by how much an overdue or at risk instance might miss the deadline by hovering over an entry in the list.
  • Pin open the instance summary if, for example, you want to compare several instances at the same time.
  • See the instance details by selecting the entry in the instances list. The instance details page is shown.

Diagram page

This page shows the overall status of the tasks in the open instances. Based on the information in the status indicators, you can identify which tasks are causing bottlenecks.

Actions that you can take
  • Identify instances that need attention by clicking the status indicator for a task. The instances list is filtered to show the instances that contain this task.
  • See the tasks in linked processes or subprocesses by double-clicking the corresponding symbol in the diagram.
  • See the instance details by selecting the entry in the instances list. The instance details page is shown.