Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 3,856 papers for “workflow flexibility”
Hajo A. Reijers · TU/e Research Portal · 2006
It is argued in this position paper that a workflow management system is potentially a powerful solution to bring more flexibility to the management of business processes. At the same time, the technical difficulties of integrating such systems in a business environment prevent this advantage to materialize up to this day
Cited by 25Open access
Ronny S. Mans, Wil M. P. van der Aalst, Nick C. Russell et al. · Lecture notes in business information processing · 2009
Cited by 16
Mans, RS Ronny, Wil M. P. van der Aalst, Nick Russell et al. · Pure Amsterdam UMC · 2009
Currently, many hospitals are investigating the use of workflow management systems in order to provide support for healthcare processes. However, contemporary workflow management systems fall short in supporting care processes which require flexible execution options. In this paper, we investigate the flexibility requirements that need to be satisfied in order to support various kinds of healthcare processes Our evaluation shows that different systems need to be used in conjunction with each other in order to fully support the various types of care processes.
Cited by 1
Shazia Sadiq, Wasim Sadiq, Maria Orlowska · 2001
Abstract: Workflow technology is currently being deployed in quite diverse domains. However, the element of change is present in some degree and form in almost all domains. A workflow implementation that does not support the process of change will not benefit the organization in the long run. Change can be manifested in different forms in workflow processes. In this paper, we first present a categorization of workflow change characteristics and divide workflow processes into dynamic, adaptive and flexible processes. We define flexibility as the ability of the workflow process to execute on the basis of a loosely, or partially specified model, where the full specification of the model is made at runtime, and may be unique to each instance. To provide a modeling framework that offers true flexibility, we need to consider the factors, which influence the paths of (unique) instances together with the process definition. We advocate an approach that aims at making the process of change part of the workflow process itself. We introduce the notion of an open instance that consists of a core process and several pockets of flexibility, and present a framework based on this notion, which makes use of special build activities that provide the functionality to integrate the process of defining a change, into the open workflow instance. 1
Cited by 0
Alessandra Agostini, Giorgio De Michelis · Lecture notes in computer science · 2000
Cited by 98
Verwaart, Tim · Socio-Environmental Systems Modeling · 2005
Cited by 0Open access
HACHICHA, Rim, BARKAOUI, Kamel · OpenGrey (Institut de l'Information Scientifique et Technique) · 2007
Cette thèse est consacrée à la modélisation formelle et la gestion des systèmes workflows. Nous nous intéressons à apporter une solution à l'un des principaux problèmes des systèmes workflows est celui de la flexibilité : les modèles aussi bien que les systèmes actuels ne sont pas suffisamment flexibles et adaptables. Dans ce but, nous proposons un modèle de tâches et d'acteurs précisant les relations formelles entre les tâches workflow et les acteurs et permettant une assignation flexible des acteurs ux activités workflow. L'allocation des tâches workflows est fondée sur le concept de distance acteur/tâche et sur le processus de formation de coalitions d'agents. le modèle permet de vérifier l'interchangeabilité des acteurs et la cohérence des tâches workflows suite à l'évolution de l'environnement. Nous proposons une architecture orientée agent distribuée intégrant le modèle formel et permettant de réaliser les fonctionnalités requises par les systèmes workflows. Cette architecture est capable de s'adapter de façon réactive aux changements tout en assurant la réutilisabilité du système Workflow. Nous avons implémenté le modèle sur la plate forme JADE en utilisant le système expert JESS et nous l'avons validé sur une réelle application.
Cited by 0Open access
Deiters, W., Goesmann, T., Löffeler, T. · Publikationsdatenbank der Fraunhofer-Gesellschaft (Fraunhofer-Gesellschaft) · 2000
S.303-313
Cited by 6
Shazia Sadiq, Wasim Sadiq, See Profile et al. · 2001
Cited by 0
RS Ronny Mans, Wil M. P. van der Aalst, NC Nick Russell et al. · Munich Personal RePEc Archive (Ludwig Maximilian University of Munich) · 2008
Currently, many hospitals are investigating the use of workflow management systems in order to provide support for healthcare processes. However, contemporary workflow management systems fall short in supporting care processes which require flexible execution options. In this paper, we investigate the flexibility requirements that need to be satisfied in order to support variouw kinds of healthcare processes. Our evalution shows that different systems need to be used in conjunction with each other in order to fully support the various types of care processes.
Cited by 1
Gower, Michelle, Kowalik, Mikolaj, Lust, Nate B. et al. · Zenodo (CERN European Organization for Nuclear Research) · 2022
Data processing pipelines need to be executed at scales ranging from small runs up through large production data release runs resulting in millions of data products. As part of the Rubin Observatory's pipeline execution system, BPS is the abstraction layer that provides an interface to different Workflow Management Systems (WMS) such as HTCondor and PanDA. During the submission process, the pipeline execution system interacts with the Data Butler to produce science-oriented execution graphs from algorithmic tasks. BPS converts this execution graph to a workflow graph and then uses a WMS-specific plugin to submit and manage the workflow. Here we will discuss the architectural design of this interface and report briefly on the recent production of the Data Preview 0.2 release and how the system is used by pipeline developers.
Cited by 0Open access
Michelle Gower, Mikołaj Kowalik, Nate B. Lust et al. · arXiv (Cornell University) · 2022
Data processing pipelines need to be executed at scales ranging from small runs up through large production data release runs resulting in millions of data products. As part of the Rubin Observatory's pipeline execution system, BPS is the abstraction layer that provides an interface to different Workflow Management Systems (WMS) such as HTCondor and PanDA. During the submission process, the pipeline execution system interacts with the Data Butler to produce a science-oriented execution graph from algorithmic tasks. BPS converts this execution graph to a workflow graph and then uses a WMS-specific plugin to submit and manage the workflow. Here we will discuss the architectural design of this interface and report briefly on the recent production of the Data Preview 0.2 release and how the system is used by pipeline developers.
Cited by 2Open access
Gower, Michelle, Kowalik, Mikolaj, Lust, Nate B. et al. · Zenodo (CERN European Organization for Nuclear Research) · 2022
Data processing pipelines need to be executed at scales ranging from small runs up through large production data release runs resulting in millions of data products. As part of the Rubin Observatory's pipeline execution system, BPS is the abstraction layer that provides an interface to different Workflow Management Systems (WMS) such as HTCondor and PanDA. During the submission process, the pipeline execution system interacts with the Data Butler to produce science-oriented execution graphs from algorithmic tasks. BPS converts this execution graph to a workflow graph and then uses a WMS-specific plugin to submit and manage the workflow. Here we will discuss the architectural design of this interface and report briefly on the recent production of the Data Preview 0.2 release and how the system is used by pipeline developers.
Cited by 0Open access
Aalst, van der, W.M.P., Basten, T., Verbeek, H.M.W. et al. · TU/e Research Portal · 1999
Today’s information systems do not support adaptive workflow: either the information system abstracts from the workflow processes at hand and focuses on the management of data and the execution of individual tasks via applications or the workflow is supported by the information system but it is hard to handle changes. This paper addresses this problem by classifying the types of changes. Based on this classification, issues such as syntactic/semantic correctness, case transfer, and management information are discussed. It turns out that the trade-off between flexibility and support raises challenging questions. Only some of these questions are answered in this paper; most of them require further research. Since the success of the next generation of workflow management systems depends on the ability to support adaptive workflow, it is important to provide answers for the questions raised in this paper.
Cited by 2
Petra Heinl, Stefan Horn, Stefan Jablonski et al. · 1999
Flexibility has recently grown to be one of the major research topics in the area of workflow management. In this paper we focus on flexibility of workflow management applications, in contrast to flexibility of the implementation of workflow management systems. In a case study we show the necessity of flexibility in workflow management applications. This flexibility can roughly be classified into flexibility, which is provided by the workflow type, and flexibility, which goes beyond the scope of the workflow type and has additionally to be provided by a workflow management system. We call this flexibility by selection and flexibility by adaption, respectively. We point out that the modeling process as a main aspect of flexibility by adaption has to be treated as a CSCW scenario. The classification leads to a structured overall concept for flexibility in workflow management applications.
Cited by 191
Aalst, WMP Wil van der, Basten, AA Twan, Verbeek, HMW Eric et al. · TU/e Research Portal (Eindhoven University of Technology) · 2000
Today’s information systems do not support adaptive workflow: either the information system abstracts from the workflow processes at hand and focuses on the management of data and the execution of individual tasks via applications or the workflow is supported by the information system but it is hard to handle changes. This paper addresses this problem by classifying the types of changes. Based on this classification, issues such as syntactic/semantic correctness, case transfer, and management information are discussed. It turns out that the trade-off between flexibility and support raises challenging questions. Only some of these questions are answered in this paper; most of them require further research. Since the success of the next generation of workflow management systems depends on the ability to support adaptive workflow, it is important to provide answers for the questions raised in this paper.
Cited by 1
Fan Yu · 2001
Workflow management system (WfMS) has been used to provide a powerful computation environment for integration of different applications and cooperation of different organizations within enterprise. In the current research field of workflow technologies, the distributed workflow engines have gradually caught more and more attentions, and the scalability and flexibility of the whole system are the two critical factors to successful implementation of the distributed workflow system. In this paper, a distributed workflow system with high scalability and high flexibility that runs on different enterprise function domains is introduced. Meanwhile, relevant concept of domain, system infrastructure, implementation of a process instance, and global control mechanism are also presented.
Cited by 0
M. Voorhoeve · 2008
Abstract: Today’s information systems do not support adaptive workflow: either the information system abstracts from the workflow processes at hand and focuses on the management of data and the execution of individual tasks via applications or the workflow is supported by the information system but it is hard to handle changes. This paper addresses this problem by classifying the types of changes. Based on this classification, issues such as syntactic/semantic correctness, case transfer, and management information are discussed. It turns out that the trade-off between flexibility and support raises challenging questions. Only some of these questions are answered in this paper; most of them require further research. Since the success of the next generation of workflow management systems depends on the ability to support adaptive workflow, it is important to provide answers for the questions raised in this paper. 1.
Cited by 0
A. Aldeeb, Keeley Crockett, M. J. Stanton · 2007
Cited by 0Open access
Lilia Gzara · HAL (Le Centre pour la Communication Scientifique Directe) · 2005
International audience
Cited by 0