![Deadline-based escalation in process-aware information systems [An article from: Decision Support Systems]](https://www.ebooknetworking.net/books/B00/0PD/bigB000PDT60W.jpg)
Deadline-based escalation in process-aware information systems [An article from: Decision Support Systems]
Description
This digital document is a journal article from Decision Support Systems, published by Elsevier in 2007. The article is delivered in HTML format and is available in your Amazon.com Media Library immediately after purchase. You can view it with any web browser.
Description:
Decision making in process-aware information systems involves build-time and run-time decisions. At build-time, idealized process models are designed based on the organization's objectives, infrastructure, context, constraints, etc. At run-time, this idealized view is often broken. In particular, process models generally assume that planned activities happen within a certain period. When such assumptions are not fulfilled, users must make decisions regarding alternative arrangements to achieve the goal of completing the process within its expected time frame or to minimize tardiness. We refer to the required decisions as escalations. This paper proposes a framework for escalations that draws on established principles from the workflow management field. The paper identifies and classifies a number of escalation mechanisms such as changing the routing of work, changing the work distribution or changing the requirements with respect to available data. A case study and a simulation experiment are used to illustrate and evaluate these mechanisms.
Description:
Decision making in process-aware information systems involves build-time and run-time decisions. At build-time, idealized process models are designed based on the organization's objectives, infrastructure, context, constraints, etc. At run-time, this idealized view is often broken. In particular, process models generally assume that planned activities happen within a certain period. When such assumptions are not fulfilled, users must make decisions regarding alternative arrangements to achieve the goal of completing the process within its expected time frame or to minimize tardiness. We refer to the required decisions as escalations. This paper proposes a framework for escalations that draws on established principles from the workflow management field. The paper identifies and classifies a number of escalation mechanisms such as changing the routing of work, changing the work distribution or changing the requirements with respect to available data. A case study and a simulation experiment are used to illustrate and evaluate these mechanisms.
