scispace - formally typeset
Search or ask a question

Showing papers on "Workflow published in 2000"


Book
David S. Linthicum1
01 Jan 2000
TL;DR: This practical guide to implementing an EAI solution leads you through all the major steps, including identifying sources of data, building the enterprise metadata model, process integration, identifying application interfaces, mapping information movement, selecting and applying the technologies, testing, and maintenance.
Abstract: Organizations that are able to integrate their applications and data sources have a distinct competitive advantage: strategic utilization of company data and technology for greater efficiency and profit. But IT managers attempting integration face daunting challenges--disparate legacy systems; a hodgepodge of hardware, operating systems, and networking technology; proprietary packaged applications; and more.Enterprise Application Integration (EAI) offers a solution to this increasingly urgent business need. It encompasses technologies that enable business processes and data to speak to one another across applications, integrating many individual systems into a seamless whole.Enterprise Application Integrationprovides a comprehensive examination of EAI. You will find an overview of EAI goals and approaches, a review of the technologies that support it, and a roadmap to implementing an EAI solution. You will also find an in-depth explanation of the four major types of EAI: data-level, application interface-level, method-level, and user interface-level. The book describes in detail the middleware models and technologies that support these different approaches, including: Application servers, including the use of Enterprise JavaBeans (EJB) and ActiveX Message-oriented middleware (MOM) and remote procedure calls (RPCs) Distributed objects, looking at CORBA and COM Database-oriented middleware and standards, including ODBC, JDBC, and OLE DB Java middleware standards Message brokers New process automation and workflow technologyThis practical guide to implementing an EAI solution leads you through all the major steps, including identifying sources of data, building the enterprise metadata model, process integration, identifying application interfaces, mapping information movement, selecting and applying the technologies, testing, and maintenance. Other key topics include integrating packaged applications such as SAP R/3 and PeopleSoft, integrating the supply chain using EAI, the role of XML, and process automation. Comprehensive, practical, and clearly written, this essential resource will help anyone involved in this important business area understand the nature of EAI, its tools and techniques, and how to apply it for a significant business advantage. 0201615835B04062001

835 citations


Journal ArticleDOI
01 Apr 2000
TL;DR: A visual verification approach and algorithm is presented that employs a set of graph reduction rules to identify structural conflicts in process models for the given workflow modeling language and provides insights into the correctness and complexity of the reduction process.
Abstract: The foundation of a process model lies in its structural specifications. Using a generic process modeling language for workflows, we show how a structural specification may contain deadlock and lack of synchronization conflicts that could compromise the correct execution of workflows. In general, identification of such conflicts is a computationally complex problem and requires development of effective algorithms specific for the target modeling language. We present a visual verification approach and algorithm that employs a set of graph reduction rules to identify structural conflicts in process models for the given workflow modeling language. We also provide insights into the correctness and complexity of the reduction process. Finally, we show how the reduction algorithm may be used to count possible instance subgraphs of a correct process model. The main contribution of the paper is a new technique for satisfying well-defined correctness criteria in process models. © 2000 Published by Elsevier Science Ltd. All rights reserved.

515 citations


Book ChapterDOI
01 Jan 2000
TL;DR: This chapter presents a method based on Petri nets that exploits the structure of the Petri net to find potential errors in the design of the workflow and allows for the compositional verification of workflows.
Abstract: Workflow management systems facilitate the everyday operation of business processes by taking care of the logistic control of work. In contrast to traditional information systems, they attempt to support frequent changes of the workflows at hand. Therefore, the need for analysis methods to verify the correctness of workflows is becoming more prominent. In this chapter we present a method based on Petri nets. This analysis method exploits the structure of the Petri net to find potential errors in the design of the workflow. Moreover, the analysis method allows for the compositional verification of workflows.

477 citations


Patent
07 Apr 2000
TL;DR: In this paper, an internet-based document management system is described, where an electronic document may be stored on an internet accessible server and accessed using a previously known web browser, downloaded for review or manipulation, and then returned to the server for access by further users.
Abstract: An internet-based document management system (17) and methods are provided wherein an electronic document may be stored on an internet-accessible server (20) and accessed using a previously known web browser, downloaded for review or manipulation, and then returned to the server for access by further users. The server is programmed to provide a plurality of services supported by a common database (25) and a document store (30), including storage and retrieval services, an electronic document delivery service, a document distribution service, a collaborative file sharing service and a workflow service. The system preferably also is programmed with a security function, a filtering function, accounting functions that enable detailed accounting of transactions occuring on the system, and a customization function that permits multiple service providers to utilize the common document management services of a server, while presenting end-users with distinct dedicated websites.

395 citations


Book ChapterDOI
06 Sep 2000
TL;DR: The work reported in this paper can be seen as the academic response to evaluations made by prestigious consulting companies, which define workflow patterns which are described imperatively but independently of current workflow languages.
Abstract: Conventional workflow functionality like task sequencing, split parallelism, join synchronization and iteration have proven effective for business process automation and have widespread support in current workflow products. However, newer requirements for workflows are encountered in practice, opening grave uncertainties about the extensions for current languages. Different concepts, although outwardly appearing to be more or less the same, are based on different paradigms, have fundamentally different semantics and different levels of applicability – more specialized for modeling or more generalized for workflow engine posit. By way of developmental insight of new requirements, we define workflow patterns which are described imperatively but independently of current workflow languages. These patterns provide the basis for an in-depth comparison of 12 workflow management systems. As such, the work reported in this paper can be seen as the academic response to evaluations made by prestigious consulting companies. Typically, these evaluations hardly consider the workflow modeling language and routing capabilities and focus more on the purely technical and commercial aspects.

389 citations


Journal ArticleDOI
TL;DR: This work describes the mechanism incorporating both transactions and exceptions and a validation technique allowing to assess the correctness of process specifications and presents a solution for implementing more reliable processes by using exception handling and atomicity.
Abstract: Fault tolerance is a key requirement in process support systems (PSS), a class of distributed computing middleware encompassing applications such as workflow management systems and process centered software engineering environments. A PSS controls the flow of work between programs and users in networked environments based on a "metaprogram" (the process). The resulting applications are characterized by a high degree of distribution and a high degree of heterogeneity (properties that make fault tolerance both highly desirable and difficult to achieve). We present a solution for implementing more reliable processes by using exception handling, as it is used in programming languages, and atomicity, as it is known from the transaction concept in database management systems. We describe the mechanism incorporating both transactions and exceptions and present a validation technique allowing to assess the correctness of process specifications.

360 citations


Patent
07 Apr 2000
TL;DR: An Internet-based document management system allows an electronic document to be stored on an Internet-accessible server and accessed using a previously known web browser, downloaded for review or manipulation, and then returned to the server for access by further users as discussed by the authors.
Abstract: An Internet-based document management system and methods are provided wherein access to the system and its services may be controlled through use of access tokens. The Internet-based document management system allows an electronic document to be stored on an Internet-accessible server and accessed using a previously known web browser, downloaded for review or manipulation, and then returned to the server for access by further users. The server is programmed to generate (237) and validate (243) access tokens and provide a plurality of services supported by a common database and document store, including storage and retrieval services, an electronic document delivery service, a document distributed service, a collaborative file sharing service and a workflow service. The system preferably also is programmed with a security function, a filtering function, accounting functions that enable detailed accounting of transactions occurring on the system, and a customization function that permits multiple service provider to utilize the common document management services of a server, while presenting end-users with distinct dedicated websites.

355 citations


Journal Article
TL;DR: CrossFlow as mentioned in this paper is a European research project aiming at the support of cross-organizational workflows in dynamic virtual enterprises, where service enactment is performed by dynamically linking the workflow management infrastructures of the involved organizations.
Abstract: In this report, we present the approach to cross-organizational workflow management of the CrossFlow project. CrossFlow is a European research project aiming at the support of cross-organizational workflows in dynamic virtual enterprises. The cooperation in these virtual enterprises is based on dynamic service outsourcing specified in electronic contracts. Service enactment is performed by dynamically linking the workflow management infrastructures of the involved organizations. Extended service enactment support is provided in the form of cross-organizational transaction management and process control, advanced quality of service monitoring, and support for high-level flexibility in service enactment. CrossFlow technology is realized on top of a commercial workflow management platform and applied in two real-world scenarios in the contexts of a logistics and an insurance company.

346 citations


Journal ArticleDOI
01 Apr 2000
TL;DR: The Bunge-Wand-Weber (BWW) representation model is proposed and used to analyze the five views - process, data, function, organization and output - provided in the Architecture of Integrated Information Systems (ARIS) popularized by Scheer.
Abstract: Process modeling has gained prominence in the information systems modeling area due to its focus on business processes and its usefulness in such business improvement methodologies as Total Quality Management, Business Process Reengineering, and Workflow Management. However, process modeling techniques are not without their criticisms [13]. This paper proposes and uses the Bunge-Wand-Weber (BWW) representation model to analyze the five views - process, data, function, organization and output - provided in the Architecture of Integrated Information Systems (ARIS) popularized by Scheer [39, 40, 41]. The BWW representation model attempts to provide a theoretical base on which to evaluate and thus contribute to the improvement of information systems modeling techniques. The analysis conducted in this paper prompts some propositions. It confirms that the process view alone is not sufficient to model all the real-world constructs required. Some other symbols or views are needed to overcome these deficiencies. However, even when considering all five views in combination, problems may arise in representing all potentially required business rules, specifying the scope and boundaries of the system under consideration, and employing a top-down approach to analysis and design. Further work from this study will involve the operationalization of these propositions and their empirical testing in the field. (C) 2000 Elsevier Science Ltd. All rights reserved.

325 citations


Journal Article
TL;DR: A detailed overview of the approach to cross-organizational workflow management developed in the CrossFlow project is given, realized on top of a commercial workflow management platform and applied in two real-world scenarios in the contexts of a logistics and an insurance company.
Abstract: This paper gives a detailed overview of the approach to cross-organizational workflow management developed in the CrossFlow project. CrossFlow is a European research project aiming at the support of cross-organizational workflows in dynamic virtual enterprises. The cooperation in these virtual enterprises is based on dynamic service outsourcing specified in electronic contracts. Service enactment is performed by dynamically linking the workflow management infrastructures of the involved organizations. Extended service enactment support is provided in the form of cross-organizational transaction management and process control, advanced quality of service monitoring, and support for high-level flexibility in service enactment. CrossFlow technology is realized on top of a commercial workflow management platform and applied in two real-world scenarios in the contexts of a logistics and an insurance company.

309 citations


Journal ArticleDOI
TL;DR: In this paper, the authors consider workflows distributed over a number of organizations and consider the minimal requirements any interorganizational workflow should satisfy, and how to decide whether such a workflow is consistent with an interaction structure specified through a message sequence chart.

Journal Article
TL;DR: To clearly identify the potential problems caused by change, a classification of change and potential errors is distinguished between transient and incessant errors, and syntactic and semantic errors.
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 momentary 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 the potential problems caused by changes. To structure these problems we use a partitioning based on five perspectives. Errors resulting from change limited to one of these perspectives and multiple-perspective errors are distinguished. To clearly identify the potential problems caused by change, we distinguish between transient and incessant errors, and syntactic and semantic errors. Based on a classification of change and potential errors we point out stepping stones for solving some of the problems.

Journal ArticleDOI
TL;DR: It is shown how verification of a typical process control specification, which is at the heart of most workflow specifications, can benefit from state-of-the-art Petri-net based analysis techniques.

Book ChapterDOI
05 Jun 2000
TL;DR: This paper investigates to what extent transformations are possible in the context of various syntactical restrictions (the most restrictive of which will be referred to as structured workflows) and provides a deep insight into the consequences of imposing such restrictions.
Abstract: While there are many similarities between the languages of the various workflow management systems, there are also significant differences. One particular area of differences is caused by the fact that different systems impose different syntactic restrictions. In such cases, business analysts have to choose between either conforming to the language in their specifications or transforming these specifications afterwards. The latter option is preferable as this allows for a separation of concerns. In this paper we investigate to what extent such transformations are possible in the context of various syntactical restrictions (the most restrictive of which will be referred to as structured workflows). We also provide a deep insight into the consequences, particularly in terms of expressive power, of imposing such restrictions.

DOI
01 Feb 2000
TL;DR: This document describes Version 1.0 of the Process Specification Language (PSL), an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools.
Abstract: This document describes Version 1.0 of the Process Specification Language (PSL). PSL is an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools. These tools would interoperate by translating between their native format and PSL. Then, any system would be able to automatically exchange process information with any other system via PSL.

Patent
25 Aug 2000
TL;DR: In this paper, a system, method and carrier medium for modeling a Financial Service Organization (FSO) business in a computer software program and for storing the model of the FSO business in database is presented.
Abstract: A system, method and carrier medium for modeling a Financial Service Organization (FSO) business in a computer software program and for storing the model of the FSO business in a database. An object-oriented business model representing the FSO may be created and stored in a business model database. The one or more business objects included in the business model may be configured to describe various products, methods, functions and properties associated with an FSO. A process map business object may describe a process workflow. The process workflow may identify a sequence of tasks to be performed by an FSO production system to process an FSO transaction. The sequence of tasks associated with an FSO transaction may be consistent with pre-defined business logic for the transaction. Selecting a task object from a plurality of task objects and transferring the task object to a process map display representing the process map business object may create the process workflow. Additional task objects may be transferred and connected to the transferred task objects in a manner consistent with the business logic. An FSO production system, which may be configured to process FSO transactions, may access the database to request data associated with a particular FSO transaction. On receiving the requested data from the business model database, the FSO production system may complete the processing of the FSO transaction.

Book ChapterDOI
Joachim Herbst1
31 May 2000
TL;DR: This contribution shows how the basic principle of the previous approach to sequential workflow induction can be generalized, so that it is able to deal with concurrency, and does not require unique activity nodes.
Abstract: There has recently been some interest in applying machine learning techniques to support the acquisition and adaptation of workflow models The different learning algorithms, that have been proposed, share some restrictions, which may prevent them from being used in practice Approaches applying techniques from grammatical inference are restricted to sequential workflows Other algorithms allowing concurrency require unique activity nodes This contribution shows how the basic principle of our previous approach to sequential workflow induction can be generalized, so that it is able to deal with concurrency It does not require unique activity nodes The presented approach uses a log-likelihood guided search in the space of workflow models, that starts with a most general workflow model containing unique activity nodes Two split operators are available for specialization

Journal ArticleDOI
01 Aug 2000
TL;DR: Principal goals to address in the development of adaptive workflow support are suggested, including strategies for avoiding exceptions, detecting them when they occur, and handling them at various levels of impact.
Abstract: The unpredictability of business processes requires that workflow systems support exception handling with the ability to dynamically adapt to the changing environment Traditional approaches to handling this problem have fallen short, providing little support for change, particularly once the process has begun execution Further, exceptions vary widely in their character and significance, challenging the application of any single approach to handling them We briefly discuss the classification of exceptions, highlighting differing impacts on the workflow model Based on this discussion, we suggest principal goals to address in the development of adaptive workflow support, including strategies for avoiding exceptions, detecting them when they occur, and handling them at various levels of impact We then identify a number of specific approaches to supporting these goals within the design of a workflow system infrastructure Finally, we describe the implementation of many of these approaches in the Endeavors workflow support system

Journal ArticleDOI
TL;DR: The issues and challenges related to managing change and time in workflows representing dynamic business processes are discussed and an analysis of workflow modifications and feasibility considerations for the automation of this process are provided.
Abstract: Business environments have become exceedingly dynamic and competitive in recent times. This dynamism is manifested in the form of changing process requirements and time constraints. Workflow technology is currently one of the most promising fields of research in business process automation. However, workflow systems to date do not provide the flexibility necessary to support the dynamic nature of business processes. In this paper we primarily discuss the issues and challenges related to managing change and time in workflows representing dynamic business processes. We also present an analysis of workflow modifications and provide feasibility considerations for the automation of this process.

Book ChapterDOI
01 Apr 2000
TL;DR: The paper uses the clinical domain to motivate and to elaborate the functionality needed to adequately support an advanced application environment and presents solutions for some issues based on the concepts elaborated in the ADEPT project.
Abstract: There is an increasing interest in changing information systems to support business processes in a more direct way. Workflow technology is a very interesting candidate to achieve this goal. Hence the important question arises, how far do we get using this technology? Is its functionality powerful enough to support a wide range of applications or is it only suitable for rather simple ones? And, if the latter is the case, are the missing functions of the “just to do” type or are more fundamental issues addressed? The paper uses the clinical domain to motivate and to elaborate the functionality needed to adequately support an advanced application environment. It shows that workflow technology is still lacking important features to serve this domain. The paper surveys the state of the art and it presents solutions for some issues based on the concepts elaborated in the ADEPT project.

Journal ArticleDOI
TL;DR: This paper describes a methodology for achieving an efficient implementation of clinical practice guidelines based on computational formalisms representing both medical and health care organisational knowledge, and shows that the 'workflow management' technology, widely used in business process automation, may be transferred to the health care setting.

Patent
26 Jul 2000
TL;DR: In this article, a method and system for generating workflow messages based on adding annotations to a file repository or database independent of an original document that they annotate is presented, which can track who has reviewed a document, whose proposed changes and/or comments require action by another person, and if everyone has reviewed the documents within the time constraints established.
Abstract: A method and system for generating workflow messages based on adding annotations to a file repository or database independent of an original document that they annotate. By separately storing the annotations in a searchable annotation repository, original documents can be preserved unchanged while still providing the ability to comment on the original document. By generating workflow messages, a system can track who has reviewed a document, whose proposed changes and/or comments require action by another person, and if everyone has reviewed the documents within the time constraints established.

Journal ArticleDOI
TL;DR: In this paper, a defeasible workflow framework is proposed to support exception handling for workflow management using ECA rules to capture more contexts in workflow modeling, and a case-based reasoning mechanism with integrated human involvement is used to improve the exception handling capabilities.
Abstract: In this paper, defeasible workflow is proposed as a framework to support exception handling for workflow management. By using the “justified” ECA rules to capture more contexts in workflow modeling, defeasible workflow uses context dependent reasoning to enhance the exception handling capability of workflow management systems. In particular, this limits possible alternative exception handler candidates in dealing with exceptional situations. Furthermore, a case-based reasoning (CBR) mechanism with integrated human involvement is used to improve the exception handling capabilities. This involves collecting cases to capture experiences in handling exceptions, retrieving similar prior exception handling cases, and reusing the exception handling experiences captured in those cases in new situations.

Proceedings ArticleDOI
04 Jan 2000
TL;DR: A process analysis tool (PISA) that can be employed to analyze the audit trail data of different workflow management systems in conjunction with target data from business process modeling tools is developed.
Abstract: Workflow management systems enable the exact and timely analysis of automated business processes through the analysis of logged audit trail data. Within the research project CONGO, we develop a process analysis tool (PISA) that can be employed to analyze the audit trail data of different workflow management systems in conjunction with target data from business process modeling tools. A working prototype has been completed that integrates data of the ARIS Toolset and IBM MQSeries Workflow. The analysis focuses on three different perspectives: processes and functions, involved resources, and process objects. We outline the economic aspects of workflow based process monitoring and control and the current state of the art in monitoring facilities provided by current workflow management systems and existing standards. After a discussion of the three evaluation perspectives, sample evaluation methods for each perspective are discussed. The concept and architecture of PISA are described and implementation issues are outlined before an outlook on further research is given.

Journal ArticleDOI
TL;DR: It is shown how a mathematical construct called a metagraph can be used to represent workflows, so that such questions can be addressed through formal operations, leading to more effective design of organizational processes.
Abstract: Agile manufacturing, fast-response micromarketing, and the rise of the virtual organization have led managers to focus on cross-functional business processes that link various divisions and organizations These processes may be realized as one or more workflows, each of which is an instantiation of a process under certain conditions Because an ability to adapt processes to workflow conditions is essential for organizational responsiveness, identifying and analyzing significant workflows is an important activity for managers, organization designers, and information systems specialists A variety of software systems have been developed to aid in the structuring and implementation of workflow systems, but they are mostly visualization tools with few analytical capabilities For example, they do not allow their users to easily determine which information elements are needed to compute other information elements, whether certain tasks depend on other tasks, and how resource availability affects information and tasks Analyses of this type can be performed by inspection, but this gives rise to the possibility of error, especially in large systems In this paper, we show how a mathematical construct called a metagraph can be used to represent workflows, so that such questions can be addressed through formal operations, leading to more effective design of organizational processes

Patent
28 Dec 2000
TL;DR: A classification-based content management system as discussed by the authors is a system that uses metadata to classify the content in such a way that the content may be quickly and easily managed, and provides advantages in a variety of aspects of the operation of the system.
Abstract: A classification based content management system provides a content management system in which large amounts of content may be quickly and easily managed. More specifically, the classification based content management system of the present invention uses metadata to classify the content in such a way that the content may be quickly and easily managed. The classification based content management system provides advantages in a variety of aspects of the operation of the system. The aspects of the operation of the system include storage, retrieval, access control and workflow management.

Patent
13 Oct 2000
TL;DR: In this article, a single intranet, internet, or World Wide Web-accessible interface is provided for, initiation of, interactive adjustments to, and access to the outputs of an integrated workflow of a plurality of analytical computer applications for characterization and analysis of traits and optimal management of the extraction of oil, gas, and water from a subsurface reservoir.
Abstract: A single intranet, internet, or World Wide Web-accessible interface is provided for, initiation of, interactive adjustments to, and access to the outputs of an integrated workflow of a plurality of analytical computer applications for characterization and analysis of traits and optimal management of the extraction of oil, gas, and water from a subsurface reservoir. By combining disparate analytical application tools in a seamless and remotely accessible, package, incompatibility problems caused by the disparate nature of petroleum analysis methods is reduced. The assumptions, analytic processes, and input data used for one analysis may be readily retrieved and re-evaluated for that reservoir or for future evaluations of the same or other reservoirs. Thus a flexible database of analysis tools and data may be implemented for access, input, and output of workflow and analytical data in the field, in conjunction with standard main computer servers, software and plug-ins, and portable remote computers.

01 Jan 2000
TL;DR: Workflow management is emerging as a challenging area for databases, stressing database technology beyond its current capabilities as discussed by the authors, and a convergence between workflow management and databases is occurring, a convergence is occurring.
Abstract: Workflow management is emerging as a challenging area for databases, stressing database technology beyond its current capabilities. Workflow management systems need to be more integrated with data management technology, in particular as it concerns the access to external databases. Thus, a convergence between workflow management and databases is occurring.

Journal ArticleDOI
TL;DR: The review suggests that the ideas developed in the earlier generations have not been supplanted by ideas from subsequent generations, and the ideas represent a continuum of progress along the three dimensions of workflow, structure, and extraction.

Journal ArticleDOI
19 Jun 2000
TL;DR: This work presents an adaptive exception manager and its Web-based interface for ADOME-WFMS with procedures for supporting: effective management of problem solving agents, cooperative exception handling, user-driven computer supported resolution of unexpected exceptions, and workflow evolution.
Abstract: Exception handling in workflow management systems (WFMSs) is a very important problem since it is not possible to specify all possible outcomes and alternatives. On the other hand, cooperative support for user-driven computer supported resolution of unexpected exceptions and workflow evolution at run-time is vital for an adaptive WFMS. We have been developing ADOME-WFMS as a comprehensive framework in which the problem of workflow exception handling can be adequately addressed. We present an adaptive exception manager and its Web-based interface for ADOME-WFMS with procedures for supporting the following: effective management of problem solving agents, cooperative exception handling, user-driven computer supported resolution of unexpected exceptions, and workflow evolution.