Abstract: A method of distributing workload in a workflow management system includes the step of calculating a load index for each engine of the workflow management system. The load index is calculated as an average activity execution delay attributable to the associated engine. The load indices indicate average execution latency between the start of consecutive activity nodes of a process due to engine loading exclusive of resource execution time. Workload is distributed across the plurality of engines in a load sensitive mode. In one embodiment, distribution switches from a load insensitive mode to a load sensitive mode for distributing processes when a maximum differential load index exceeds a first pre-determined threshold. Distribution switches from the load sensitive mode back to the load insensitive workload distribution mode for distributing processes when the maximum differential load index is less than a second pre-determined threshold.

Abstract: The present invention pertains to a system for simulating business processes. The system has data warehouse for storing historical execution data from executions of a first business process. The system also has a business process simulator coupled to the data warehouse and for simulating a second business process using the historical execution data as input parameters and for outputting simulated business process data.

Abstract: The present invention pertains to a system for simulating business processes. The system has data warehouse for storing historical execution data from executions of a first business process. The system also has a business process simulator coupled to the data warehouse and for simulating a second business process using the historical execution data as input parameters and for outputting simulated business process data.

Abstract: A method of distributing workload in a workflow management system includes the step of calculating a load index for each engine of the workflow management system. The load index is calculated as an average activity execution delay attributable to the associated engine. The load indices indicate average execution latency between the start of consecutive activity nodes of a process due to engine loading exclusive of resource execution time. Workload is distributed across the plurality of engines in a load sensitive mode. In one embodiment, distribution switches from a load insensitive mode to a load sensitive mode for distributing processes when a maximum differential load index exceeds a first pre-determined threshold. Distribution switches from the load sensitive mode back to the load insensitive workload distribution mode for distributing processes when the maximum differential load index is less than a second pre-determined threshold.

Abstract: Exception analysis, prediction, and prevention method and system. Exception analysis involves identifying the causes of exceptional behaviors (e.g., deviations from the predetermined standard of execution). Exception prediction involves predicting the occurrence of exceptions as early as possible during the process execution. Exception prevention involves taking actions to avoid exceptions. By performing exception analysis, prediction, and prevention, the occurrence of exceptions is reduced, thereby increasing business process quality.

Abstract: A method of identifying and analyzing business processes includes the step of populating a data warehouse database with data from a plurality of sources including an audit log. The audit log stores information from a plurality of instantiations of a defined process. The data is then analyzed to predict an outcome of a subsequent instance of the process. Data mining techniques such as pattern recognition are applied to the data warehouse data to identify specific patterns of execution. Once the patterns have been identified, the outcome of a subsequent instance of the process can be predicted at nodes other than just the start node. The probability of completion information can be used to modify resource assignments, execution paths, process definitions, activity priority, or resource assignment criteria in subsequent invocations of the defined process.