Tools & Software — ProM — iDHM

An interactive data-aware process discovery tool based on the ideas of the heuristics miner combined with classification techniques.



An interactive data-aware process discovery tool based on the ideas of the heuristics miner combined with classification techniques. The iDHM implements a process discovery method that uses the data attributes to distinguish infrequent paths from random noise by using classification techniques. Data- and control-flow of the process are discovered together.

Traces from the event log may be filtered by using a SQL-like query syntax ①. Generally, the output is presented in form of a C-Net, but other output formats such as Petri net or Data Petri net can also be chosen ②. The heuristic used for each step of the iDHM can be configured ③. Several thresholds are used to configure the heuristics ④. At the bottom of the screen a legend explains the used color coding ⑤. Edges can be selected to show more information ⑥.


ProM Package: DataAwareCNetMiner
ProM Plug-ins: Interactive Data-aware Heuristic Miner
Sources: ProM SVN
Related Publications:



Download the currently ProM nightly builder at Use the ProM package manager to install the package DataAwareCNetMiner (don’t ask about why it is named like this). The package should be available in the current ProM nightly build distribution and is scheduled to be released in ProM 6.7.


Provided Plug-ins

Interactive plug-ins, which provide everything in one interactive tool.

  • Interactive Data-aware Heuristic Miner
Non-interactive plug-ins, which provide the option to convert C-Nets to various other representations:
  • Convert Causal net (C-Net) to Petri net
  • Convert Data-aware Causal Net (DC-Net) to DPN


The required input for the Interactive Data-aware Heuristic Miner is an event log in XES format. The iDHM is tested with the efficient XES implementation of the XESLite package. The In Memory variant is advisable for most even logs:


Initially, a suitable event classifier that determines which attributes are considered as activity names needs to be selected:


The main user interface of the interactive DHM consists of two panels: the discovered model on the left and the parameter settings on the right. There is also a tab-component on the top, which can be used to instantiate multiple instances of the interactive DHM and quickly remember and compare the obtained results.


Discovered Model

The discovered model is visualized using the GraphViz package (thanks Sander). By default the discovered model is shown as a Causal Net (C-Net). It is possible to zoom, pan, and change various settings of the GraphViz panel. An overview of the settings can be obtained by hovering over the question mark (?) in the lower right corner of the panel.
Bindings of the C-Net can be selected to obtain more information on the frequency with which a binding was activated. Edges of the C-Net can be selected to obtain the dependency measure score. Moreover, by right-clicking on the activities, a tabular overview on its input- and output bindings can be obtained.

main selection

Dependencies that are included based on discovered data conditions are highlighted with red color. For those edges, selection shows the discovered rule, the classification quality measure (which defaults to Cohen’s kappa), and the variance of the quality measure over the 10 times 10-fold cross validation. Moreover, with a right-click on the edge, the discovered rule can be further investigated: the classifier can be visualized, detailed evaluation statistics and additional statistics such as the ROC and PRC curve of the underlying classifier can be shown.

main data selection

Finally, conformance checking techniques can be applied on the C-Net and the event log. Activities and bindings are color-coded based on their frequency of occurrence according to the event log. The size of the binding dots also scales with their frequency of occurrence.
Moreover, conformance problems are diagnosed: events that are not represented in the model are shown as yellow bar (log move) and activity executions in the model that are not observed in the log as a purple bar (model move). Additionally, we add a small circle of the respective color to the top left of the activity to indicate the presence of conformance issues.

main conformance


parameters overview

  • Input: Traces: Filters full traces based on a SQL-like query language. The help button can be used to get an overview of the syntax. A right-click with the mouse shows the available attributes and vallues that can be filtered on.
  • Output: Process model: Changes the model notation that is shown. The standard choices are:
    • Directly-follows Graph
    • Dependency Graph
    • Causal net (C-Net)
    • Data Causal net (DC-Net)
    • Data Petri net (DPN)
    • Petri net
    Moreover, it is also possible to show the underlying dependency graph, the directly follows relations, and all dependency relations.
  • Export: Exports the model to the ProM workspace.
  • Data-aware Config: Configuration of the classifier used to discover conditional dependencies.
  • Expert Mode: Shows rarely used parameters and expert options
  • Frequency: Adjusts the used observation frequency threshold: θobs
  • Dependency: Adjusts the used dependency threshold: θdep
  • Bindings: Adjusts the used binding threshold: θbin
  • Conditions: Adjusts the used data condition threshold: θcon
  • Decisions: Adjusts the used data condition threshold: θcon
  • Long Term: Activates the standard Long-term-dependency heuristic.
  • All Tasks Connected: Activates the standard All-tasks-connected heuristic, i.e., all activities are shown and connected, regardless of the thresholds.
  • Accepted Connected: Activates the Accepted-connected heuristic, i.e., only the minimum number of activities and dependencies that do not fulfill the threshold are added.

Plug-in Development

Plug-ins need to be annotated with the following two Java annotations:


There are five types of plug-ins that can be developed for the iDHM. Each type of plug-in needs to implement one of the following interfaces:

There are also abstract default implementations available for each of these interfaces, which may simply the implementation of the required methods. As an example, Flexible Heuristics Miner plug-in is implemented as follows:
package org.processmining.dataawarecnetminer.extension.dependencies;

import org.processmining.dataawarecnetminer.common.MinerContext;
import org.processmining.dataawarecnetminer.extension.DefaultHeuristicPlugin;
import org.processmining.dataawarecnetminer.extension.HeuristicPlugin;
import org.processmining.dataawarecnetminer.interactive.methods.MethodConfiguration;
import org.processmining.dataawarecnetminer.mining.classic.HeuristicsCausalGraphBuilder;
import org.processmining.dataawarecnetminer.model.DependencyAwareCausalGraph;
import org.processmining.dataawarecnetminer.model.EventRelationStorage;
import org.processmining.framework.plugin.annotations.KeepInProMCache;

public class DependencyHeuristicExtensionFHMImpl extends DefaultDependencyHeuristicFactory {

	private static class DependencyHeuristicFHMImpl extends DefaultDependencyHeuristic {

		private HeuristicsCausalGraphBuilder fhmGraphBuilder;

		public DependencyHeuristicFHMImpl(EventRelationStorage eventStorage) {
			this.fhmGraphBuilder = new HeuristicsCausalGraphBuilder(eventStorage);

		public DependencyAwareCausalGraph computeDependencies(MinerContext context, MethodConfiguration configuration) {

		protected DependencyHeuristicConfig configureHeuristicCausalGraphMiner(MethodConfiguration configuration) {
			DependencyHeuristicConfig config = new DependencyHeuristicConfig();

			return config;


	public DependencyHeuristic newInstance(EventRelationStorage eventStorage) {
		return new DependencyHeuristicFHMImpl(eventStorage);

	public String getName() {
		return "Flexible Heuristics Miner";

	public String getReference() {
		return "AJMM Weijters, JTS Ribeiro. Flexible Heuristic Miner. DOI: 10.1109/CIDM.2011.5949453";