scispace - formally typeset
Search or ask a question

Showing papers on "Workflow published in 2001"


Book
01 Jan 2001
TL;DR: This book provides a basic overview of workflow terminology and organization, as well as detailed coverage of workflow modeling with Petri nets, to provide a comprehensive introduction to workflow management.
Abstract: This book offers a comprehensive introduction to workflow management, the management of business processes with information technology. By defining, analyzing, and redesigning an organization's resources and operations, workflow management systems ensure that the right information reaches the right person or computer application at the right time. The book provides a basic overview of workflow terminology and organization, as well as detailed coverage of workflow modeling with Petri nets. Because Petri nets make definitions easier to understand for nonexperts, they facilitate communication between designers and users. The book includes a chapter of case studies, review exercises, and a glossary. A special Web site developed by the authors, www.workflowcourse.com, features animation, interactive examples, lecture materials, exercises and solutions, relevant links, and other valuable resources for the classroom.

1,971 citations


Journal Article
TL;DR: Workflow Management as mentioned in this paper is an overview of workflow terminology and organization, as well as detailed coverage of workflow modeling with Petri nets, which facilitates communication between designers and users, and includes case studies, review exercises, and a glossary.

1,336 citations


Journal ArticleDOI
TL;DR: An initial evaluation of the experiences in using the event-based architectural style and a classification of some of theevent-based infrastructures presented in the literature are provided.
Abstract: The development of complex distributed systems demands the creation of suitable architectural styles (or paradigms) and related runtime infrastructures. An emerging style that is receiving increasing attention is based on the notion of event. In an event-based architecture, distributed software components interact by generating and consuming events. An event is the occurrence of some state change in a component of a software system, made visible to the external world. The occurrence of an event in a component is asynchronously notified to any other component that has declared some interest in it. This paradigm (usually called "publish/subscribe", from the names of the two basic operations that regulate the communication) holds the promise of supporting a flexible and effective interaction among highly reconfigurable, distributed software components. In the past two years, we have developed an object-oriented infrastructure called JEDI (Java event-based distributed infrastructure). JEDI supports the development and operation of event-based systems and has been used to implement a significant example of distributed system, namely, the OPSS workflow management system (WFMS). The paper illustrates the main features of JEDI and how we have used them to implement OPSS. Moreover, the paper provides an initial evaluation of our experiences in using the event-based architectural style and a classification of some of the event-based infrastructures presented in the literature.

696 citations


Book ChapterDOI
TL;DR: It is shown that, given an appropriate clarification of their semantics, activity diagrams are able to capture situations arising in practice, which cannot be captured by most commercial Workflow Management Systems.
Abstract: If UML activity diagrams are to succeed as a standard in the area of organisational process modeling, they need to compare well to alternative languages such as those provided by commercial Workflow Management Systems. This paper examines the expressiveness and the adequacy of activity diagrams for workflow specification, by systematically evaluating their ability to capture a collection of workflow patterns. This analysis provides insights into the relative strengths and weaknesses of activity diagrams. In particular, it is shown that, given an appropriate clarification of their semantics, activity diagrams are able to capture situations arising in practice, which cannot be captured by most commercial Workflow Management Systems. On the other hand, the study shows that activity diagrams fail to capture some useful situations, thereby suggesting directions for improvement.

401 citations


Book
15 Feb 2001
TL;DR: Filled with real-world examples and practical techniques, this book is a seamless methodology for process redesign and information systems development that integrates use-case analysis and process workflow modeling to easily span the gap between management and IT.
Abstract: From the Publisher: If you're looking to create new workflow systems or redesign existing business processes for your enterprise, look no further than this concise, new hands-on book. Providing proven techniques for identifying, modeling, and redesigning business processes, and explaining how to implement workflow improvement, this book helps you define requirements for systems development or systems acquisition. By showing you how to build visual models for illustrating workflow, the authors help you to assess your current business processes and see where process improvement and systems development can take place. This book brings the two distinct disciplines of management and information technology together especially for high-tech professionals who need to improve the way work gets done to maintain a competitive edge. Addressing such hot topics as enterprise resource planning (ERP) applications and enterprise application integration (EAI), you learn how to manage these complex, new schemes not as technology-based changes, but as the process redesign projects they truly are. Plus, understanding process workflow modeling allows you to get a better handle on implementing a complete business process for successful e-commerce initiatives. Filled with real-world examples and practical techniques, you get a seamless methodology for process redesign and information systems development that integrates use-case analysis and process workflow modeling to easily span the gap between management and IT. What's more, the visual modeling you learn from this book shows you not only how to improve your enterprise, but where trouble spots might occur and how to avoid common pitfalls. What'smore, because the book is structured as an on-the-job guide, you don't have to read it all before getting started. It features clear summaries, project checklists, and other aids that make it a logical guide to keep on your reference shelf and put to use every day.

362 citations


Journal ArticleDOI
TL;DR: In this paper, the authors present eFlow, a system that supports the specification, enactment, and management of composite e-services, modeled as processes that are enacted by a service process engine.

361 citations


Journal ArticleDOI
TL;DR: The authors may not be able to make you love reading, but production workflow concepts and techniques will lead you to love reading starting from now.
Abstract: We may not be able to make you love reading, but production workflow concepts and techniques will lead you to love reading starting from now. Book is the window to open the new world. The world that you want is in the better stage and level. World will always guide you to even the prestige stage of the life. You know, this is some of how reading will give you the kindness. In this case, more books you read more knowledge you know, but it can mean also the bore is full.

350 citations


Journal ArticleDOI
TL;DR: A way of mapping workflow into Petri nets, which can be used as a basis for such systems as well as an agreed and standard modelling technique.

327 citations


Book ChapterDOI
04 Jun 2001
TL;DR: It is explained that the P2P approach yields an interorganizational workflow which is guaranteed to realize the behavior specified in the public workflow.
Abstract: This paper describes in an informal way the Public-To-Private (P2P) approach to interorganizational workflows, which is based on a notion of inheritance. The approach consists of three steps: (1) create a common understanding of the interorganizational workflow by specifying a shared public workflow, (2) partition the public workflow over the organizations involved, and (3) for each organization, create a private workflow which is a subclass of the respective part of the public workflow. Using an example, we explain that the P2P approach yields an interorganizational workflow which is guaranteed to realize the behavior specified in the public workflow.

299 citations


Journal ArticleDOI
TL;DR: Woflan as mentioned in this paper analyzes workflow process definitions downloaded from commercial workflow products using state-of-the-art Petri-net-based analysis techniques to locate the source of a design error.
Abstract: Workflow management technology promises a flexible solution for business-process support facilitating the easy creation of new business processes and modification of existing processes. Unfortunately, today’s workflow products have no support for workflow verification. Errors made at design-time are not detected and result in very costly failures at run-time. This paper presents the verification tool Woflan. Woflan analyzes workflow process definitions downloaded from commercial workflow products using state-of-the-art Petri-net-based analysis techniques. This paper describes the functionality of Woflan emphasizing diagnostics to locate the source of a design error. Woflan is evaluated via two case studies, one involving 20 groups of students designing a complex workflow process and one involving an industrial workflow process designed by Staffware Benelux. The results are encouraging and show that Woflan guides the user in finding and correcting errors in the design of workflows. Received 27 September 2000; revised 8 March 2001

287 citations


Journal ArticleDOI
TL;DR: The field of workflow automation, the subject of this special issue of Information Systems Frontiers, is introduced and basic definitions and frameworks are provided to aid understanding of workflow management technologies.
Abstract: Workflow management systems, a relatively recent technology, are designed to make work more efficient, integrate heterogeneous application systems, and support interorganizational processes in electronic commerce applications. In this paper, we introduce the field of workflow automation, the subject of this special issue of Information Systems Frontiers. In the first part of the paper, we provide basic definitions and frameworks to aid understanding of workflow management technologies. In the remainder of the paper, we discuss technical and management research opportunities in this field and discuss the other contributions to the special issue.

Journal ArticleDOI
TL;DR: A number of currently available PDM systems that have embraced web-technologies are reviewed, and some industrial implementations are presented, showing how this new infrastructure enhances a traditional PDM system.

Book ChapterDOI
27 Nov 2001
TL;DR: This paper introduces the notion of an open instance that consists of a core process and several pockets of flexibility, and presents a framework which makes use of special build activities that provide the functionality to integrate the process of defining a change, into the open workflow instance.
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.

Patent
04 May 2001
TL;DR: In this paper, a tree-structured workflow control and report selection control allow users to easily display data and generate reports, without having to actively determine the various measures and dimensions to be displayed in various interactive views of the data and various simple and advanced reports.
Abstract: A tree-structured workflow control and a tree-structured report selection control allow users to easily display data and generate reports, without having to actively determine the various measures and dimensions to be displayed in various interactive views of the data and various simple and advanced reports. By linking predetermined sets of dimensions, measures and views to predetermined workflow control entries and report selection entries in a tree structure having labels on the branches and leaves that are logically related to the associated predetermined sets, the user can immediately obtain a data visualization perspective or a report without having to actively select the particular dimensions and measures for display, and without having to actively arrange the selected dimensions into a multi-dimensional view. The user can also alter the particular dimensions and/or measures being displayed and associate the user's selection with a new predetermined entry in the tree-structured workflow and report selection controls.

Patent
02 Oct 2001
TL;DR: In this article, a workflow engine for rendering instant credit decisions includes a workflow designer, a web site interface, a database, checklists created by the workflow designer and associated with at least one loan offering, and a messaging system for brokering messages between a consumer and a lender.
Abstract: A workflow engine for rendering instant credit decisions includes a workflow designer (24), a web site interface, a database, checklists created by the workflow designer and associated with at least one loan offering, and a messaging system for brokering messages between a consumer and a lender. The workflow engine accepts web-based loan applications, processes the loan applications programmatically (38), and renders a loan decision within seconds. The workflow engine uses checklists to evaluate loan applications (96). Each checklist is associated with one loan offering and one lender. Multiple lenders offer multiple loan offerings through the system to compete for consumer/borrowers. The system evaluates loan applications and renders a programmatic loan decision without human intervention (100), subject to verification of the application data.

Proceedings ArticleDOI
01 May 2001
TL;DR: The requirements and solutions in this paper address the scalability of existing security solutions, the separation of inter-organizational workflow security from concrete organization level security enforcement, and the enforcement of fine-grained access control for inter- Organizational workflow.
Abstract: As more businesses engage in globalization, inter-organizational collaborative computing grows in importance. Since we cannot expect homogeneous computing environments in participating organizations, heterogeneity and Internet-based technology are prevalent in inter-organizational collaborative computing environments. One technology that provides solutions for data sharing and work coordination at the global level is inter-organizational workflow. In this paper, we investigate the access control requirements for inter-organizational workflow. We then present access control solutions for inter-organizational workflow based on our implementation. Many of the requirements and solutions in this paper address the scalability of existing security solutions, the separation of inter-organizational workflow security from concrete organization level security enforcement, and the enforcement of fine-grained access control for inter-organizational workflow.

Patent
Wayne F. Miller1, Alan Tsu-I Yaung1
28 Jun 2001
TL;DR: In this paper, a plurality of graphical user interfaces (GUI) panels are displayed through which a user may define nodes of a workflow and associate at least one action and user with each node.
Abstract: Provided is a method, system, and program for generating a workflow. A plurality of graphical user interfaces (GUI) panels are displayed through which a user may define nodes of a workflow and associate at least one action and user with each node. During workflow execution of each node, the associated user performs the associated action. Further, multiple nodes define actions that process at least one object that is routed through multiple nodes of the workflow. A workflow model is generated from information entered into the GUI panels including the nodes and workflow defined by the user through the GUI panels that process the at least one object. The workflow model is transformed into a workflow definition language (WDL) file. The WDL file is then transferred to a workflow server, wherein the workflow server interacts with a database to implement the workflow model defined in the WDL file in the database. When executing the implementation of the workflow, a request by one user associated with one node is received to access the node when no other user is accessing the node. The user requesting access to the node is granted access to the node to perform the action associated with the node. The node is locked to prevent other users associated with the node from accessing the node. The lock on the node is released when the user granted access to the node completes the action associated with the node, wherein other users can access the node after the lock is released.

Proceedings ArticleDOI
03 Jan 2001
TL;DR: This paper presents the formal foundation and conceptual design of dynamic adaptations in an object-oriented workflow management system based on the CORBA object- oriented middleware, and describes in some detail how workflow schemas are represented.
Abstract: While the different aspects of flexible workflow management are still under discussion, the ability to adapt the structure of running workflow instances to modified workflow schemas is an important property of a flexible workflow management system. In this paper, we present the formal foundation and conceptual design of dynamic adaptations in an object-oriented workflow management system. We describe in some detail how workflow schemas are represented. The system architecture, based on the CORBA object-oriented middleware, is overviewed, and the implementation of dynamic adaptations is sketched. An example introduces the graphical user interface of the system and shows a dynamic adaptation.

Patent
05 Jun 2001
TL;DR: Workflow management system and method with personal subflows as discussed by the authors includes a workflow definition including an activity to be performed by a personal subflow, and a decision agent cooperates with the server in the scheduling of work items by considering participant-provided data and a branch expression associated with a current personal sub-flow activity.
Abstract: Workflow management system and method with personal subflows. A workflow system includes a workflow definition including an activity to be performed by a personal subflow. The personal subflow is defined by personal subflow activities and branch expressions associated with the subflow activities. A server interprets the workflow definition and facilitates the scheduling and routing of work items in the system. A client receives work items from the server and displays information therefrom to a participant. The client also receives data and control commands from the participant. A decision agent cooperates with the server in the scheduling of work items by considering participant-provided data and a branch expression associated with a current personal subflow activity.

Proceedings Article
11 Sep 2001
TL;DR: This paper describes the architecture and implementation of a tool suite that enables exception analysis, prediction, and prevention of deviations from the desired or acceptable behavior and shows experimental results obtained by using the tool suite to analyze internal HP processes.
Abstract: Business process automation technologies are being increasingly used by many companies to improve the efficiency of both internal processes as well as of e-services offered to customers. In order to satisfy customers and employees, business processes need to be executed with a high and predictable quality. In particular, it is crucial for organizations to meet the Service Level Agreements (SLAs) stipulated with the customers and to foresee as early as possible the risk of missing SLAs, in order to set the right expectations and to allow for corrective actions. In this paper we focus on a critical issue in business process quality: that of analyzing, predicting and preventing the occurrence of exceptions, i.e., of deviations from the desired or acceptable behavior. We characterize the problem and propose a solution, based on data warehousing and mining t We then describe the architecture and implementation of a tool suite that enables exception analysis, prediction, and prevention. Finally, we show experimental results obtained by using the tool suite to analyze internal HP processes.

Patent
Alan Tsu-I Yaung1
28 Jun 2001
TL;DR: In this article, a workflow class implements methods and objects to provide information on and control of workflows, and a work item class implements a set of objects to manipulate work items when executing one workflow.
Abstract: Provided is a method, system, and program for executing a workflow. A workflow class implement methods and objects to provide information on and control of workflows. A work list class implements methods and objects to provide information on and manipulate work items assigned to the workflows. A work item class implements methods and objects to provide information on and manipulate work items when executing one workflow.

Journal ArticleDOI
TL;DR: This paper describes an approach for calculating a safe change region and explains how to deal with the dynamic change bug, which can lead to duplication of work, skipping of tasks, deadlocks, and livelocks in workflow management.
Abstract: Adaptability has become one of the major research topics in the area of workflow management. Today's workflow management systems have problems dealing with both ad-hoc changes and evolutionary changes. As a result, the workflow management system is not used to support dynamically changing workflow processes or the workflow process is supported in a rigid manner, i.e., changes are not allowed or handled outside of the workflow management system. In this paper, we focus on a notorious problem caused by workflow change: the “dynamic change bug” (Ellis et al.s Proceedings of the Conference on Organizational Computing Systems, Milpitas, California, ACM SIGOIS, ACM Press, New York, 1995, pp. 10–21). The dynamic change bug refers to errors introduced by migrating a case (i.e., a process instance) from the old process definition to the new one. A transfer from the old process to the new process can lead to duplication of work, skipping of tasks, deadlocks, and livelocks. This paper describes an approach for calculating a safe change region. If a case is in such a change region, the transfer is postponed.

Journal ArticleDOI
TL;DR: The paper presents a classification of possible exceptions, and shows how the sequence of tasks described by a guideline may be altered, at the implementation level, in order to meet actual user needs, while maintaining guideline intentions as much as possible.

Patent
27 Nov 2001
TL;DR: In this article, the authors present a computer-implemented method of managing documents related to a patent application. But they do not describe how the system is used to transfer the documents from the server system to the client system.
Abstract: A computer-implemented method of managing documents related to a patent application. In one embodiment the method includes storing a first workflow rule on a server system where the first workflow rule causes the server system to generate a message that requests approval to prepare a patent application for an invention disclosure and route the message to a second client system upon receipt of a first signal indicating a request to submit the invention disclosure for approval. The method also includes storing a first invention disclosure in a database accessible by said server system; receiving, at the server system, a first signal from a first client system indicating a request to submit the first invention disclosure for approval. Upon receipt of the first signal, the server system then executes the first workflow rule to generate a message requesting approval of a second client system to prepare a patent application from the first invention disclosure and communicate the message to the second client system.

Patent
07 Sep 2001
TL;DR: In this article, the authors present an automated workflow management for a series of workflow tasks by mapping the workflow tasks to a collaborative workflow process comprising: roles, users, business processes and computer executable activities.
Abstract: Currently lacking are effective and accurate tools to help petroleum traders and logistics personnel to make better decisions, collaborate in real-time and negotiate deals in a private and secure environment. The present invention addresses this and other needs in the industry. In particular, the present invention provides automated workflow management for a series of workflow tasks by mapping the workflow tasks to a collaborative workflow process comprising: roles, users, business processes and computer executable activities. A workflow object is received that supplies information used to set particular attributes of the roles, the users, the business activities and the computer executable activities of the collaborative workflow process. Information and data objects are shared electronically among the users performing certain of the roles. At least one of the activities is automatically executed, such that the workflow is automatically managed.

01 Jan 2001
TL;DR: The process mining technique proposed in this paper can deal with noise and can also be used to validate workflow processes by uncovering and measuring the discrepancies between prescriptive models and actual process executions.
Abstract: Contemporary workflow management systems are driven by explicit process models, i.e., a completely specified workflow design is required in order to enact a given workflow process. Creating a workflow design is a complicated time-consuming process and typically there are discrepancies between the actual workflow processes and the processes as perceived by the management. Therefore, we propose a technique for process mining. This technique uses workflow logs to discover the workflow process as it is actually being executed. The process mining technique proposed in this paper can deal with noise and can also be used to validate workflow processes by uncovering and measuring the discrepancies between prescriptive models and actual process executions.

Patent
02 Oct 2001
TL;DR: A workflow engine for rendering instant workflow decisions includes a workflow designer, a web site interface, a database, checklists created by the workflow designer and associated with at least one workflow process, and a messaging system for brokering messages as mentioned in this paper.
Abstract: A workflow engine for rendering instant workflow decisions includes a workflow designer, a web site interface, a database, checklists created by the workflow designer and associated with at least one workflow process, and a messaging system for brokering messages. The workflow engine uses checklists to evaluate workflow processes. Each checklist is associated with one workflow decision. The workflow checklist is an object=based representation of the sequential ordering of functions within the workflow engine. Administrative tools allow an end-user to modify workflow checklists and their associated parameters without recompiling or rebooting the system.

Journal ArticleDOI
TL;DR: This paper introduces and advocates the use of interacting proclets, i.e. lightweight workflow processes, so that by promoting interactions to first-class citizens it is possible to model complex workflows in a more natural manner.
Abstract: The focus of traditional workflow management systems is on control flow within one process definition. The process definition describes how a single case (i.e. workflow instance) in isolation is handled. For many applications this paradigm is inadequate. Interaction between cases to support communication and collaboration is at least as important. This paper introduces and advocates the use of interacting proclets, i.e. lightweight workflow processes. By promoting interactions to first-class citizens it is possible to model complex workflows in a more natural manner. In addition, the expressive power and flexibility are improved compared to the more traditional workflow modeling languages.

Proceedings ArticleDOI
30 Sep 2001
TL;DR: This paper presents the software package FLOWer, which fully supports a paradigm shift to overcome workflow technology problems: workflows should not be driven by pre-specified control-flows but by the products they generate.
Abstract: In the last decade, workflow technology has become one of the building blocks for realizing enterprise information systems. Unfortunately, the application of contemporary workflow management systems is limited to well-defined and well-controlled environments. In practice, workflow technology often fails because of limited flexibility. We advocate a paradigm shift to overcome this problem: Workflows should not be driven by pre-specified control-flows but by the products they generate. This paper presents the software package FLOWer which fully supports this paradigm shift.

Journal Article
TL;DR: This paper presents an original framework for specifying, enacting and supervising e-services on the Web based on XML and rules-based support for products/services description and workflow mediation across organizations.
Abstract: The growth of the Internet and the Web is revolutionizing the way companies interact with their suppliers, partners, and clients, by enabling a substantial automation of the full spectrum of their business activities. As we move into the 21st century economy, the primary form of automation will be B2B e-commerce, in which enterprises interact with each other through entirely automated means. As an example, consider an electronic market place in a vertical industry segment, in which suppliers and buyers tie into a common IT infrastructure to exchange goods and services. This forms a supply chain in which buyers need (a) to investigate possible suppliers, (b) to check the terms and conditions under which suppliers can do business, (c) to interoperate with the suppliers enterprise support systems, i.e., workflows, and (d) to monitor ordering/purchasing for possible delays, unexpected events, react to such events, etc. This paper presents an original framework for specifying, enacting and supervising e-services on the Web. This framework is based on XML and rules-based support for products/services description and workflow mediation across organizations. Traditionally, WorkFlow Management Systems (WFMS) have focused on homogeneous and centrally controlled environments for binding people and processes within the boundary of a single organization. In the context of B2B e-commerce, WFMSs need to support collaboration between various autonomous parties, some of which may even have conflicting business goals. More precisely, they must cope with heterogeneous enterprise support environments (e.g., through different WF systems), to model the interaction of independent partners by abstracting the internal details of their activities (e.g., through different WF schemas), and finally to facilitate flexible linking and monitoring of inter-enterprise processes (e.g., through different WF enactments). To address these challenges we are currently developing a workflow mediation middleware which relies on three basic technologies: (a) the XRL workflow specification language [13, 18] for representing in XML heterogeneous workflow schemas and enactments, (b) an XML query language [4, 5] for manipulating both complex product and service descriptions, and (c) the Vortex rule-based language [12, 6] that supports heuristic reasoning in order to take on-line business decisions during the workflow execution. During recent years, workflow interoperation has received considerable attention. Numerous research projects and prototypes have been proposed [16, 2] while basic interoperability between various vendor WFMSs has been a subject of standardization efforts by the Object Management Group (see Workflow