P. Barthelmess and J. Wainer, Workflow systems: A few definitions and a few suggestions, in: Proc. Conf. On Organizational Computing Systems (COOCS'95) (1995) pp. 138--147.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....similarity with a current one. There is another important consequence of the fact that workcases are stored: users that are not responsible for current activities being performed onto the workcase may have access to it. This is very important to deal with asynchronous events (or signal exception [BW95]) related to the workcase: the awareness of an asynchronous events may come to someone that is not currently working on that workcase a secretary receives a letter from the customer cancelling a purchase order while the purchase order is in the activity of production scheduling and that office ....

....of the flow of cases that varies from a totally new case to a standard case. The main task of the workflow management system is to determine when an activity ends what will be the next activity and who will perform it (the WFMS also has to perform synchronization of and joins and batch activities [BW95] but we will not discuss these issues in this paper) At the end of an activity the system verifies the two data items: next activity, next executor and if they are set, those will be the next activity and the executor of that activity. Given the characteristics of this case a user may decide ....

P. Barthelmess and J. Wainer, Workflow Systems: a few definitions and a few suggestions, in Proceedings of the 1995 ACM Conference on Organizational Comput- ing Systems (C00CS'95), N. Comstock and C.A. Ellis (eds.), pp la8-147, Milpitas, California, 1995.

....the run time system to assist users in coordinating and scheduling the tasks of a BP. Current process oriented WFMSs are applicable in a reliable and secure manner only if the BP to be supported is well structured and there is no need for ad hoc deviations or dynamic extensions at run time (see Barthelmess and Wainer, 1995; Ellis et al. 1995; Siebert, 1996; Reichert and Dadam, 1997a) As only few BPs are static in this sense, this significantly limits the benefit and the applicability of current workflow (WF) technology. As an example, consider BPs from the clinical domain (see Reichert et al. 1996, 1997b) where ....

....changes of WFs which are controlled by different distributed WF servers name a few examples. 5. Related Work It is widely recognized that state of the art WF technology does only provide rudimentary support for exception handling and for dynamic structural changes of running WF instances (see Barthelmess and Wainer, 1995; Ellis et al. 1995; Reichert et al. 1997a; Sheth and Kochut, 1997; Siebert, 1996) Both, in research and in commercial WFMSs, several directions can be made out that try to overcome these limitations. These approaches focus on . the provision of services for exception handling and for ad hoc ....

Barthelmess, P. and Wainer, J. (1995). Workflow Systems: a few Definitions and a few Suggestions. Proc. Conf. on Organizational Computing Systems (pp. 138-147). New York: ACM Press.

....activity. Compared with the print shop s workflow system, they were even less constraining in the ordering of the work done and therefore did not interfere with the smooth operation of day to day tasks. Furthermore, the overhead of use at the museum was relatively low. Barthelmess and Wainer [6] explore exceptions and propose viewing workflows as exception handling tools. This involves providing support for different kinds of exception handling actions, including mechanisms for recording who did what. This approach often leads to solutions that require data that were incorrect or missing ....

Barthelmess, P. and Wainer, J. Workflow Systems: a few definitions and a few suggestions. In Proceedings, COOCS'95. Conference on Organizational Computing Systems, (Milpitas, CA, 1995), ACM Press, 138-147.

....these applications by the university staff requires that the staff express their opinion on the application. Decision making is central to this workflow. A decision on each application is made on the basis of the combined opinions expressed. RSA is more complex than a simple workflow application [3] in which specific tasks are performed completely at each step in the workflow. In RSA all decisions are made to a stated level of confidence. These confidence factors play a key role in controlling the operation of this system to ensure that its performance is in line with determined strategic ....

Barthelmess, P. and Wainer, J. (1995) "Workflow Systems: a few definitions and a few suggestions" in proceedings 1995 ACM Conference on Organisational Computing Systems (COOCS'95), N. Comstock and C.A. Ellis (eds.), pp 138-147, Milpitas, California, 1995.

....for humans. Our ongoing work is also focused on connecting our technology with automated process enactment systems, such as workflow controllers and software agent systems. It is widely recognized that state of the art workflow technology provides very rudimentary support for exception handling [1, 4]. The result of our work will be a prototype implementation of a domain independent exception handling engine, which oversees the enactment of a workflow script, monitors for exceptions and decides (automatically for the most part) how to For a given process. retrieve list of possible ....

P. Barthelmess and J. Wainer, Workflow Systems: a few Definitions and a few Suggestions, Proc. Conf. On Organizational Computing Systems (COOCS'95) (1995) 138-147.

....for humans. Our ongoing work is also focused on connecting our technology with automated process enactment systems, such as workflow controllers and software agent systems. It is widely recognized that state of the art workflow technology provides only rudimentary support for exception handling [2, 9]. The result of our work will be a prototype implementation of a domainindependent exception handling engine, which oversees the enactment of a workflow script, monitors for exceptions and decides (automatically for the most part) how to intervene in order to resolve them. Given an ideal ....

P. Barthelmess and J. Wainer. Workflow Systems: a few Definitions and a few Suggestions. Proceeding of the Conf. On Organizational Computing Systems (COOCS'95), pp. 138-147, 1995.

....The state noanswer is the initial substate of the state expected. It is entered when the transition request enters the state expected. The sequence initial noanswer finished constitutes the normal execution of determining a registration number in our example. 4 Handling Exceptions Barthelmess and Wainer (1995) define an exception to be any departure of a work case from its prescribed flow. Hence, exceptions occur only on the activity instance level. There are also exceptions which can be expected in advance. Then they may be added to the execution scheme as a possible path. However, Abbott and Sarin ....

Barthelmess, P. and J. Wainer (1995). WorkFlow Systems: a few definitions and a few suggestions. In N. Comstock and C. Ellis (Eds.), Proc. of the Conf. on Organizational Computing Systems COOCS'95, New York, pp. 138--147. ACM Press.

....humans. Our ongoing work is primarily focused on connecting our technology with automated process enactment systems, such as workflow controllers and software agent systems. It is widely recognized that state of the art workflow technology provides very rudimentary support for exception handling [1, 4]. The result of our work will be a prototype implementation of a domain independent exception handling engine, which oversees the enactment of a workflow script, monitors for exceptions and decides (automatically for the most part) how to intervene in order to resolve them. Given an ideal ....

P. Barthelmess and J. Wainer. Workflow Systems: a few Definitions and a few Suggestions. Proc. Conf. on Organizational Computing Systems (COOCS'95), Aug. 13-16, 1995, pp. 138-147.

....particular independently from the end of other tasks does not ease the specification of ad hoc and administrative workflows. Furthermore, it is difficult to give a graphical representation of the flow structure, since the start of a task is not necessarily related to the end of another task. In [BW95] a taxonomy of activities and exceptions is introduced. A interesting proposal, absent in other workflow models, relate the definition of batch activities, i.e. activities that require control and data coordination among different instances of a workflow. A proposed example relates the ranking ....

Barthelmess, P., Wainer, J., Workflow systems: a few definitions and a few Suggestions, Conference on Organizational Computing System, 1996.

....of these models is destined to fail. Therefore, we only acknowledge the work that extended workflow models to accommodate the problems identified in Section 2. Zisman [37] presents a paper refereeing example that involves Petri nets and allows multiple instantiation of the reviewer net. In [7], batch oriented tasks were proposed, i.e. a task is executed for multiple instances at the same time. To allow for the batch oriented tasks, independent cases need to be synchronized. As an example, consider the task of selecting papers for a conference (task select in the example) All papers ....

P. Barthelmess and J. Wainer. Workflow systems: a few definitions and a few suggestions. In N. Comstock and C.A. Ellis, editors, Proceedings of the Conference on Organizational Computing Systems - COOCS'95, pages 138--147, Milpitas, California, September 1995. ACM Press.

....are discussed in Section 4. Concluding remarks complete the paper. 2 Office Work We propose that office work is mostly about achieving goals defined by rules of enterprises. In more modern WFMS, there has been a lot of emphasis on exception handling and ad hoc planning for special cases [BK95][BW95][BN95] SMM 94] These two concepts, exception handling and ad hoc planning, show that it is acceptable to neglect a planned processing in order to achieve the goals that were behind the process itself. For example, if the CEO of a company sends a memo that a particular customer s purchase should ....

P. Barthelmess and J. Wainer, Workflow Systems: a few definitions and a few suggestions, in Proceedings of the 1995 ACM Conference on Organizational Computing Systems (COOCS'95), N. Comstock and C.A. Ellis (eds.), pp 138-147, Milpitas, California, 1995.

....[1, 2] and cross organizational workflows [3, 4] etc. Any attempt to give a complete overview of these models is destined to fail. Therefore, we only acknowledge the work that extended workflow models to accommodate the problems identified in Section 2. Batch oriented tasks were discussed in [7]. Creation of multiple instances of tasks have been proposed by some, e.g. Casati et al. 9] multi tasks) Regatta system by Fujitsu [27] multi stage) Spade 1 [6] multiple active copies) 16 The idea to promote interaction to first class citizens was proposed in different settings. In the ....

P. Barthelmess and J. Wainer. Workflow systems: a few definitions and a few suggestions. In N. Comstock and C.A. Ellis, editors, Proceedings of the Conference on Organizational Computing Systems - COOCS'95, pages 138--147, Milpitas, California, September 1995. ACM Press.

....similarity with a current one. There is another important consequence of the fact that workcases are stored: users that are not responsible for current activities being performed onto the workcase may have access to it. This is very important to deal with asynchronous events (or signal exception [BW95]) related to the workcase: the awareness of an asynchronous events may come to someone that is not currently working on that workcase a secretary receives a letter from the customer cancelling a purchase order while the purchase order is in the activity of production scheduling and that office ....

....of the flow of cases that varies from a totally new case to a standard case. The main task of the workflow management system is to determine when an activity ends what will be the next activity and who will perform it (the WFMS also has to perform synchronization of and joins and batch activities [BW95] but we will not discuss these issues in this paper) At the end of an activity the system verifies the two data items: next activity, next executor and if they are set, those will be the next activity and the executor of that activity. Given the characteristics of this case a user may decide that ....

P. Barthelmess and J. Wainer, Workflow Systems: a few definitions and a few suggestions, in Proceedings of the 1995 ACM Conference on Organizational Computing Systems (COOCS'95), N. Comstock and C.A. Ellis (eds.), pp 138--147, Milpitas, California, 1995.

....handling chores [Saa94, SM89] If we could express more at model level, less effort would be spent treating those situations as exceptions. In fact, they would stop being exceptions, and become rule. Most description languages are not able to depict asynchronous events and batch activities [BW95] forcing these events and activities to be treated as exceptions. We will propose a model that adds support to such events and activities. Because both asynchronous events and batch activities are commonplace, we feel that better models can be built by being able to support them. Even very ....

....for production Redo scheduling to fill eventual gaps Abort Production Decide if production would be stopped or continued If decided to continue store the goods Take legal action Abort Delivery Store the goods Invoice generation Take legal action Abort 3.2. 2 Batch activities Batch activities [BW95] also pose some special representation problems. In this kind of activities, many individual workcases are brought together and suffer a collective action. This collective action usually involves grouping or ordering the workcases according to some criteria that take all workcases in ....

Barthelmess,P., Wainer, J. "Workflow Systems: a few definitions and a few suggestions, " to be published ACM Conference on Organizational Computing Systems (COOCS'95), San Jose, CA, 1995.

No context found.

P. Barthelmess and J. Wainer, Workflow systems: A few definitions and a few suggestions, in: Proc. Conf. On Organizational Computing Systems (COOCS'95) (1995) pp. 138--147.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC