Dear Process Observer community,

In one of our previous posts, we showed you how to extract process log information from Process Observer in the MXML format as well as how to then import and analyze it with ProM. While ProM is a free open source tool, which requires a certain level of expertise to be able to use it, we alternatively used Fluxico’s Disco. Fluxicon is a spin-off of the University of Eindhoven (which developed ProM) and their product Disco is a professional variant of the process mining tool, being more user-friendly and so more suitable for day-by-day use in business.

The good thing about using Disco is that it can use and import the Process Observer data extraction in the MXML format that we generated for the ProM case. So all you need to do is to install notes 1832016 and 2011730– as described in the previous article, and run the extraction report. Disco can then import the generated file imported. Click ‘Open file’ to import the exported MXML file from the local PC:

/wp-content/uploads/2014/11/disco_open_file_583755.png

In the example shown, we extracted Process Observer data from a process orchestrated with Process Object built by SAP Process Object Builder (aka “POL”). Note: SAP Process Object Builder is an own SAP product with an own license. It is not part of Process Observer (component of the SAP Business Suite)

Process Objects are used inside Process Object Builder to orchestrate service-based processes, such as “loan” processes in Banking. For more information about the integration of Process Objects with Process Observer, see Logging & Tracing.

The scenario being discussed is a “mobile loan” scenario. It allows customers to buy goods in retail stores and to pay with a loan. Process Object Builder calls the services needed for executing this process.

/wp-content/uploads/2014/11/pol_process_583756.png

The complete (click-through) demonstration can be found here: http://demo.tdc.sap.com/SpeedDemo/694212576a084610/

The process is executed in phases:

  • “Start”
  • “Create”: Retrieve customer data, Retrieve limit
  • “Check”: Check limit
  • “Execute”: Create loan, and so on

A positive creation and execution ends with a confirmation, problems during execution result in a failed state. Inconsistent data (such as a limit issue) may lead to an error. If the decision is to cancel the process, compensation might be needed before it ends in a cancelled state.

After the import, Disco shows the process flow including the error situations:

/wp-content/uploads/2014/11/mining_overview_583760.png

Note that the shown process map is simplified by not showing some of the less frequent paths in the flow. The level of detail of the shown process map can be adjusted interactively in the software.

In addition to the absolute frequency of the steps and paths, the tool shows the performance of the execution, highlighting execution bottlenecks. For example, in the following illustration, a more detailed process map is shown with the cumulative times between the state changes for all cases (visual mark-up and leading metric) and the average times between them (in a smaller font). 

/wp-content/uploads/2014/11/performance_view_583761.png

Filtering allows you to set the focus to certain process variants, or processes, in which certain steps occur (for example only processes with errors) and finally to drill down to the level of single cases for further analysis:

/wp-content/uploads/2014/11/instance_view_583762.png

To evaluate the process further on the service call level, we have created a specific extraction report, exposing the “callable business entities” logged in Process Observer as steps. The resulting data allows for the analysis of the process data on a deeper level, for example, allowing you to evaluate the performance of processes with errors:

/wp-content/uploads/2014/11/analysis_view_583765.png

For us, it was surprising to see how easily we could evaluate our process data. While we did this all on test data in our own systems, we are now in the phase of evaluating this approach with a real customer.

Try evaluating your own scenario with Process Observer and Disco. You may download a demo version of Disco from the Fluxicon website: http://fluxicon.com/disco/ and request an extended evaluation license (to import larger files) from anne@fluxicon.com. A Disco project file (containing the different views from this article) that can be imported with the demo version can be downloaded here.

To gain deeper insight into Process Objects and Process Object Builder, see http://help.sap.com/pobuilder10 or contact Karsten Egetoft.

Stay tuned for more Process Observer use cases!

Bernd
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply