As a continuation of the blog – BPI with BPM – Made easy! – Part 1, this blog elucidates how the process KPIs could be measured with SAP NetWeaver BPM. Though the much anticipated BAM (Business Activity Monitoring) component of BPM might provide the required KPI metrics at the human task level, for the approach suggested in the part 1 of this blog, there is a need to measure the KPIs for off-the-system human tasks.

Using Intermediate Message Events and Reporting activities (Judiciously !).

Intermediate message events and reporting activities can be used in combination with each other to do the job. The process model below shows a pattern that could be adopted for capturing the required KPIs for a process that is fully composed of off-the-system human tasks.

The use of multiple Intermediate Message Events for each of the external business events might must be determined very carefully as wrong usage will create on adverse effects on the BPM runtime. This will provide a good starting point to measure the exact process performance of the business processes even without having a fully integrated BPMN process model. This would also help to showcase the capabilities of BPM and further stream line the processes through the iterative BPM lifecycle.

The KPIs captured with the help of reporting activities could be further used to create the required KPI dashboards using Visual Composer (VC). The articles listed below provide the details on building the VC KPI dashboards.

Steps to Implement Reporting activity in BPM for process status tracking

6 Sample SAP NetWeaver BPM 7.20 Dashboards implemented with Visual Composer

It is also advised to refer to the article to understand the do’s and don’ts with Intermediate Message Events.

The approach suggested in this article is by no means the best possible one. It just highlights one of the possible approaches that could be employed to measure the KPIs for off-the-system tasks. Care must be taken to ensure the right correlation conditions are defined for each of the intermediate message events in the process model.