| Auramaki, E. and M. Leppanen (1989). Exceptions and office information systems. Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process., Linz, Austria. |
.... to workflow exceptions (a conflict, after all, is just one type of exception) 9 This work also constitutes, we believe, a substantive and novel contribution to previous efforts on exception handling, which have been pursued in the context of workflow (Kunin 1982; Kreifelts and Woetzel 1987; Auramaki and Leppanen 1989; Karbe and Ramsberger 1990; Strong 1992; Mi and Scacchi 1993; Ellis, Keddara et al. 1995; Klein 1998) manufacturing control (Parthasarathy 1989; Katz 1993; Visser 1995) model based fault diagnosis (deKleer and Williams 1986; Krishnamurthi and Jr. 1989; Birnbaum, Collins et al. 1990; Friedrich, ....
Auramaki, E. and M. Leppanen (1989). Exceptions and office information systems. Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process., Linz, Austria.
.... AGENT SYSTEMS A critical challenge to creating effective agent based systems is allowing them to operate effectively when, as is typical for many domains ranging from manufacturing to office work to military information gathering, the operating environment is complex, dynamic, and error prone [1 5]. In such domains, we can expect to utilize a highly diverse set of agents; some have fairly sophisticated coordination capabilities, but many will be simple encapsulations of legacy applications. New tasks, agents and other resources can be expected to appear and disappear in unpredictable ways. ....
....we will have to be able to operate with agents whose design incorporates only the most basic capabilities. A few efforts have done some preliminary exploration of the use of distinct exception handling services. This work has occurred predominantly in the context of business process enactment [1 3, 5, 6], manufacturing control [7 9] and planning [10, 11] The process enactment and manufacturing work, in general, has either not evolved to the point of constituting a computational model, or has been applied to a very limited range of domains (e.g. just software engineering or flexible manufacturing ....
Auramaki, E. and M. Leppanen. Exceptions and office information systems. in Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process. 1989. Linz, Austria.
....exclusively on exceptions (e.g. failed operations, unexpected events) in the world manipulated by the agents, and not on exceptions concerning the agents themselves. Finally, there has been substantial work on detecting and resolving exceptions in computer supported cooperative work [41] 42] 43] [44] [45] and manufacturing control [46] 47] 48] but this has been applied to a very limited range of domains (e.g. just flexible manufacturing cell control) and exception types (e.g. just inappropriate task assignments) 6. Future Work We plan to pursue two concurrent lines of development in this ....
E. Auramaki and M. Leppanen, "Exceptions and office information systems," presented at Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process., Linz, Austria, 1989.
....unexpected events) in the world manipulated by the agents, and not on exceptions concerning the agents themselves. Finally, there has been substantial work on detecting and resolving exceptions in computer supported cooperative work (Mi and Scacchi 1993) Chiu, Karlapalem et al. 1997) Klein 1998) (Auramaki and Leppanen 1989) (Finkelstein, Gabbay et al. 1994) and manufacturing control (Fletcher and Misbah 1999) Adamides and Bonvin 1993) Katz 1993) but this has been applied to a very limited range of domains (e.g. just software engineering or flexible manufacturing cell control) and exception types (e.g. just ....
Auramaki, E. and M. Leppanen (1989). Exceptions and office information systems. Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process., Linz, Austria.
.... with research efforts scattered across disparate communities including real time systems (Burns and Wellings 1996) distributed systems (Mullender 1993) robotics (Hindriks, de Boer et al. 1998) computer supported cooperative work (Mi and Scacchi 1993) Chiu, Karlapalem et al. 1997) Klein 1998) (Auramaki and Leppanen 1989) (Finkelstein, Gabbay et al. 1994) manufacturing control (Fletcher and Misbah 1999) Adamides and Bonvin 1993) Katz 1993) planning (Traverso, Spalazzi et al. 1996) Howe 1995) Birnbaum, Collins et al. 1990) Broverman and Croft 1987) Firby 1987) and multi agent systems (Hgg 1996) Kaminka ....
Auramaki, E. and M. Leppanen (1989). Exceptions and office information systems. Proceedings of the IFIP WG 8.4 Working Conference on Office Information Systems: The Design Process., Linz, Austria.
....set of process templates that can be retrieved, compared and customized using the principles embodied in the Process Handbook. This work also constitutes, we believe, a substantive and novel contribution to previous efforts on exception handling, which have been pursued in the context of workflow [1, 9, 13, 18, 22, 25] manufacturing control [14, 23, 26] model based fault diagnosis [3, 7, 19] planning [3, 4] and failure mode analysis research [24] Most workflow research has focused on languages for expressing correctness preserving transforms on workflow models, providing no guidance however concerning which ....
E. Auramaki and M. Leppanen. Exceptions and office information systems. In B. Pernici and A.A. Verrijn-Stuart, editors: Office Information Systems: The Design Process, pp.167182, North Holland Publishing Co., 1989. 16
.... A critical challenge to creating effective agent based systems is allowing them to operate effectively when, as is typical for many domains ranging from manufacturing to office work to military information gathering, the operating environment is complex, dynamic, and error prone (Suchman 1983; Auramaki and Leppanen 1989; Karbe and Ramsberger 1990; Strong 1992; Mi and Scacchi 1993) In such domains, we can expect to utilize a highly diverse set of agents; some have fairly sophisticated coordination capabilities, but many will be simple encapsulations of legacy applications. New tasks, agents and other resources ....
....to operate with agents whose design incorporates only the most basic capabilities. A few efforts have done some preliminary exploration of the use of distinct exception handling services. This work has occurred predominantly in the context of business process enactment (Kreifelts and Woetzel 1987; Auramaki and Leppanen 1989; Karbe and Ramsberger 1990; Strong 1992; Mi and Scacchi 1993) manufacturing control (Parthasarathy 1989; Katz 1993; Visser 1995) and planning (Broverman and Croft 1987; Birnbaum, Collins et al. 1990) The process enactment and manufacturing work, in general, has either not evolved to the point ....
Auramaki, E. and M. Leppanen (1989). Exceptions and office information systems. Office Information Systems: The Design Process. Proceedings of the IFIP WG 8.4 Working Conference, Linz, Austria.
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