Showing papers on "Workflow technology published in 1998"

The application of Petri-nets to workflow management

Abstract: Workflow management promises a new solution to an age-old problem: controlling, monitoring, optimizing and supporting business processes. What is new about workflow management is the explicit representation of the business process logic which allows for computerized support. This paper discusses the use of Petri nets in the context of workflow management. Petri nets are an established tool for modeling and analyzing processes. On the one hand, Petri nets can be used as a design language for the specification of complex workflows. On the other hand, Petri net theory provides for powerful analysis techniques which can be used to verify the correctness of workflow procedures. This paper introduces workflow management as an application domain for Petri nets, presents state-of-the-art results with respect to the verification of workflows, and highlights some Petri-net-based workflow tools.

Adept _flex —Supporting Dynamic Changes of Workflows Without Losing Control

Abstract: Today‘s workflow management systems (WFMS_s) are only applicable in a secure and safe manner if the business process (BP) to be supported is well-structured and there is no need for ad hoc deviations at run-time. As only few BPs are static in this sense, this significantly limits the applicability of current workflow (WF) technology. On the other hand, to support dynamic deviations from premodeled task sequences must not mean that the responsibility for the avoidance of consistency problems and run-time errors is now completely shifted to the (naive) end user. In this paper we present a formal foundation for the support of dynamic structural changes of running WF instances. Based upon a formal WF model (ADEPT), we define a complete and minimal set of change operations (ADEPT_flex) that support users in modifying the structure of a running WF, while maintaining its (structural) correctness and consistency. The correctness properties defined by ADEPT are used to determine whether a specific change can be applied to a given WF instance or not. If these properties are violated, the change is either rejected or the correctness must be restored by handling the exceptions resulting from the change. We discuss basic issues with respect to the management of changes and the undoing of temporary changes at the instance level. Recently we have started the design and implementation of ADEPT_workflow, the ADEPT workflow engine, which will make use of the change facilities presented in this paper.

Mining Process Models from Workflow Logs

Abstract: Modern enterprises increasingly use the workflow paradigm to prescribe how business processes should be performed. Processes are typically modeled as annotated activity graphs. We present an approach for a system that constructs process models from logs of past, unstructured executions of the given process. The graph so produced conforms to the dependencies and past executions present in the log. By providing models that capture the previous executions of the process, this technique allows easier introduction of a workflow system and evaluation and evolution of existing process models. We also present results from applying the algorithm to synthetic data sets as well as process logs obtained from an IBM Flowmark installation.

Three Good Reasons for Using a Petri-Net-Based Workflow Management System

Abstract: Currently, the Dutch Customs Department is building a nationwide information system to handle all kinds of declarations related to the import and export of goods. For this purpose the Petri-net-based Workflow Management System (WFMS) named COSA has been selected. During the selection process, it turned out that there are several reasons for insisting on a Petri-net-based WFMS. The three main reasons for selecting a Petri-net-based WFMS are discussed in this paper. In our opinion these reasons are also relevant for many other projects involved in the selection or implementation of a WFMS.

Modeling and Analysis of Workflows Using Petri Nets

Abstract: A workflow system, in its general form, is basically a heterogeneous and distributed information system where the tasks are performed using autonomous systems Resources, such as databases, labor, etc are typically required to process these tasks Prerequisite to the execution of a task is a set of constraints that reflect the applicable business rules and user requirements In this paper we present a Petri Net (PN) based framework that (1) facilitates specification of workflow applications, (2) serves as a powerful tool for modeling the system under study at a conceptual level, (3) allows for a smooth transition from the conceptual level to a testbed implementation and (4) enables the analysis, simulation and validation of the system under study before proceeding to implementation Specifically, we consider three categories of task dependencies: control flow, value and external (temporal) We identify several structural properties of PN and demonstrate their use for conducting the following type of analyses: (1) identify inconsistent dependency specifications among tasks; (2) test for workflow safety, ie test whether the workflow terminates in an acceptable state; (3) for a given starting time, test whether it is feasible to execute a workflow with the specified temporal constraints We also provide an implementation for conducting the above analyses

From Centralized Workflow Specification to Distributed WorkflowExecution

Abstract: Current workflow management systems fall short of supporting large-scale distributed, enterprise-wide applications. We present a scalable, rigorously founded approach to enterprise-wide workflow management, based on the distributed execution of state and activity charts. By exploiting the formal semantics of state and activity charts, we develop an algorithm for transforming a centralized state and activity chart into a provably equivalent partitioned one, suitable for distributed execution. A synchronization scheme is developed that guarantees an execution equivalent to a non-distributed one. This basic solution is further refined in order to reduce communication overhead and exploit parallelism between partitions whenever possible. The developed synchronization schemes are compared in terms of the number and size of synchronization messages.

Workflow management system for an automated credit application system

Abstract: A workflow management system for an automated credit application processing system. The workflow management system automatically coordinates the workflow among various workgroups and entities involved in the credit application process. The steps and rule tests that define an organization's workflow are customized according to the workflow requirements and process steps for each organization. The workflow manager allows application steps to be processed simultaneously by various entities involved in the loan application process. Workgroups are defined for each pre-configured workflow definition. Each workgroup is associated with a particular set of functions. A workgroup queue is provided for each workgroup. Workgroup queues contain active or pending steps associated with the workgroup. In operation, users can obtain status information by viewing data from the various workgroup queues. A relational database management system is used to link a plurality of tests with each workflow process step that is defined for particular workflow. The tests are linked to rule elements which are linked to database elements that are linked to functions that alter the database elements. Accordingly, when a function is executed, the workflow management system automatically determines which particular workflow process steps are potentially affected by the executed function. Then, the workflow management system evaluates those steps to determine their status and to further determine the process steps to be activated next.

System and process allowing collaboration within and between enterprises for optimal decision making

Abstract: A computer implemented process for enterprise collaboration is provided. The process includes designing a workflow where the workflow has at least one heterocast split and at least one heterocast join. The heterocast split and the heterocast join allow at least one activity to be parameterized, and at least one of the parameters comprising nodes within a node group. The workflow is then instantiated such that the at least one activity is instantiated as a plurality of activities each tailored to a particular node in the node group. The process then involves deploying the workflow including distributing the activities over the nodes in the node group, and executing the workflow to provide multi-enterprise collaboration

System and method for managing the workflow for processing service orders among a variety of organizations within a telecommunications company

Abstract: A system and method for managing the workflow for processing Service Orders among a variety of organizations within a telecommunications company. The system and method coordinates all of the tasks and activities related to order processing among the various entities within the telecommunications company. Workflows are used to model business procedures used for processing Service Orders. Each workflow comprises a plurality of workflow steps. Business process models are depicted as workflow diagrams. Upon receipt of a Service Order, an appropriate Work Plan is selected based on information within the Service Order. Each workflow step is assigned a Resource and is scheduled for completion. The Workflow steps are then placed in In-boxes associated with the selected Resource. Once the processing steps have been scheduled, a current work step is calculated. Notification messages are sent to the appropriate systems to notify them to begin activity associated with the current work step. The system is automatically notified when the current work step is complete, so that the next work step can be processed in a similar fashion. Detailed statistical information is maintained for audit and reporting purposes. Users log-on to remote workstations coupled with a company-wide Intranet or the like. From the remote workstations, users from various organizations view their In-boxes and other detailed information about Service Orders according to selectable requests. Workflow steps can be transferred and re-assigned using the remote workstations. Detailed statistical information is maintained for audit and reporting purposes. Reports reflecting the effectiveness of workforce management and work administration is obtained.

Development framework for case and workflow systems

Abstract: A workflow processing framework provides common objects and business processes for the creation of an enterprise-wide workflow processing system. Conventional workflow, database and other platforms are accessed using standardized protocols. The use of common objects providing robust functionality while being insulated from the specific platforms used to implement the workflow processing system enable the common objects to be reused to perform many functions in many different lines of business without modification. If necessary, foundation objects are written to utilize the existing platforms more fully than permitted by standardized protocols. The business processes are generalized as much as possible, but are customized as required to fit the enterprise environment.

Object-oriented workflow for multi-enterprise collaboration

Abstract: A computer implemented process is disclosed for enterprise collaboration. The process includes instantiating an object-oriented workflow where the object-oriented workflow comprises objects associated with activities to be performed within the workflow. The objects of the object-oriented workflow are then deployed across enterprise boundaries to nodes on which associated activities are to be performed. After deployment, the deployed objects are executed to provide multi-enterprise collaboration with the activities communicating data using objects that carry both data and behavior. Further, in one embodiment, the process further includes creating in-memory object models at nodes which objects executing at the nodes can access.

System and method for performing consistent workflow process execution in a workflow management system

Abstract: A system for allowing consistent execution of a workflow process in a computer-enabled workflow management system is described The workflow process includes at least one sequence of workflow actions, having at least one set of parallel workflow actions and being configured as a number of nodes interconnected by arcs Each node defines and executes at least one of the workflow actions The system includes a workflow process database accessible by the nodes of the workflow process to read and write data items when executing the workflow actions The system also includes a module for maintaining execution consistency among the workflow actions when the nodes access the workflow process database to read and write the data items in carrying out the workflow actions A computer-implemented method for consistently executing a workflow process in a workflow management system is also described

WebWork: METEOR _2 ‘s Web-Based Workflow Management System

Abstract: METEOR_2 workflow management systems consist of both (1) design/build-time and (2) run-time/enactment components for implementing workflow applications. An enactment system provides the command, communication and control for the individual tasks in the workflow. Tasks are the run-time instances of intra- or inter-enterprise applications. We are developing three implementations of the METEOR_2 model: WebWork, OrbWork and NeoWork. This paper discusses WebWork, an implementation relying solely on Web technology as the infrastructure for the enactment system. WebWork supports a distributed implementation with participation of multiple Web servers. It also supports automatic code generation of workflow applications from design specifications produced by a comprehensive graphical designer. WebWork has been developed as a complement of its more heavyweight counterparts (OrbWork and NeoWork), with the goal of providing ease of workflow application development, installation, use and maintenance. At the time of this writing, WebWork has been installed by several of the LSDIS Lab‘s industrial partners for testing, evaluation and building workflow applications.

Integrating machine learning and workflow management to support acquisition and adaptation of workflow models

Abstract: Current workflow management systems (WFMS) offer little aid for the acquisition of workflow models and their adaptation to changing requirements. To support these activities we propose to integrate machine learning and workflow management. This enables an inductive approach to workflow acquisition and adaptation by processing traces of manually enacted workflows. We present a machine learning component that combines two different machine learning algorithms. In this paper we focus mainly on the first one, which induces the structure of the workflow, based on the induction of hidden markov models. The second algorithm, a standard decision rule induction algorithm, induces transition conditions. The main concepts have been implemented in a prototype, which we have validated using artificial process traces. The induced workflow models can be imported by the business process management system ADONIS.

Method and apparatus for creating adaptive workflows

Abstract: A scheduling engine and an associated workflow engine may be configured to build workflows that describe sequences of tasks to be performed in a dynamically changing environment. The workflow engine may be configured to monitor the execution of the tasks within the environment and to provide the scheduling engine with information regarding deviations of task executions from the workflows. When such deviations are detected, the workflow engine may trigger the scheduling engine to rebuild the workflows for as yet uncompleted tasks. The scheduling engine may receive the information regarding the deviations via a declarative model of the physical environment. In general, the tasks may be a set of job requests to be processed in a manufacturing environment (e.g., a print shop). Also, the scheduling engine may be made up of an aggregate planner and a detailed scheduler. Aggregate plans for the jobs may be first made for the jobs and then passed to the detailed scheduler for timelining, etc. Building the aggregate plans may be accomplished by selecting a subset of the job requests according to a procedure for packing bins representing the resources of the manufacturing plant.

Verification problems in conceptual workflow specifications

Abstract: Most of today's business requirements can only be accomplished through integration of various autonomous systems which were initially designed to serve the needs of particular applications. In the literature workflows are proposed to design these kinds of applications. The key tool for designing such applications is a powerful conceptual specification language. Such a language should be capable of capturing interactions and cooperation between component tasks of workflows among others. These include sequential execution, iteration, choice, parallelism and synchronisation. The central focus of this paper is the verification of such process control aspects in conceptual workflow specifications. As is generally agreed upon, that the later in the software development process an error is detected, the more it will cost to correct it; it is thus of vital importance to detect errors as early as possible in the systems-development process. In this paper some typical verification problems in workflow specifications are identified and their complexity is addressed. It will be proven that some fundamental problems are not tractable and we will show what restriction is needed to allow termination problems to be recognized in polynomial time.

Flexible modeling and execution of workflow activities

Abstract: While today's workflow management systems are well suited for the controlled execution of completely specified processes, support for dynamically changing processes is rather weak. However, new applications in the business domain and in non-traditional domains like the natural sciences or laboratory environments require support for flexibility like user interventions in workflow executions and dynamic modifications. Based on an activity meta model and an activity instance model, the paper discusses dynamic modifications and user interventions and shows how their implications to activity models and to concurrent and future activity instances can be described. Finally, we show how the basic concepts presented in the paper are realized in a prototypical implementation.

Flexible exception handling in the OPERA process support system

Abstract: Exceptions are one of the most pervasive problems in process support systems. In installations expected to handle a large number of processes, having exceptions is bound to be a normal occurrence. Any programming tool intended for large, complex applications has to face this problem. However, current process support systems, despite their orientation towards complex, distributed, and heterogeneous applications, provide almost no support for exception handling. This paper shows how flexible mechanisms for failure handling are incorporated into the OPERA process support system using a combination of programming language concepts and transaction processing techniques. The resulting mechanisms allow the construction of fault-tolerant workflow processes in a transparent and flexible way while ensuring reusability of workflow components.

Managing evolving workflow specifications

Abstract: Dynamic evolution of workflow models due to process (re)engineering activities and dynamic changing situations of the real process is one of the most important challenges in workflow management. The authors present an approach for the management of evolving workflow specifications which copes with the evolution of a workflow schema and the dynamic modification of workflow instances. The approach is based on the integrated modeling of workflow schema and instance elements, the separated definition of 'what to do' and 'how to do' in the workflow schema, late binding of workflows at run-time, and the versioning of the workflow schema. On this basis, they support lazy, eager, and selective propagation as well as local customization of instances and their upward propagation. Furthermore, they address the problem of managing consistent configurations of the versioned entities of a workflow schema. In their workflow-specific versioning approach, the consistency of the workflow configuration is guaranteed and hence the version mechanism is transparent to the user.

Workflow management system wherein ad-hoc process instances can be generalized

Abstract: In workflow management software, task objects describing a successfully-completed workflow process instance are copied The copied task objects are then generalized in the relevant variables thereof, so that the entire workflow process is thus generalized for direct re-use in an amended workflow process definition In this way, ad-hoc amendments to the workflow process, such as those initiated by the persons who collaborate in the work process, can be easily incorporated into a new work process

Failure handling and coordinated execution of concurrent workflows

Abstract: Workflow management systems (WFMSs) coordinate the execution of applications distributed over networks. In WFMSs, data inconsistencies can arise due to: the interaction between steps of concurrent threads within a workflow (intra-workflow coordination); the interaction between steps of concurrent workflows (inter-workflow coordination); and the presence of failures. Since these problems have not received adequate attention, this paper focuses on developing the necessary concepts and infrastructure to handle them. First, to deal with inter- and intra-workflow coordination requirements we have identified a set of high level building blocks. Secondly, to handle failures we propose a novel and pragmatic approach called opportunistic compensation and re-execution that allows a workflow designer to customize workflow recovery from correctness as well as performance perspectives. Thirdly based on these concepts we have designed a workflow specification language that expresses new requirements for workflow executions and implemented a run-time system for managing workflow executions while satisfying the new requirements. These ideas are geared towards improving the modeling and correctness properties offered by WFMSs and making them more robust and flexible.

Workflow system for rearrangement of a workflow according to the progress of a work and its workflow management method

Abstract: A workflow system comprises a workflow definition unit, a workflow operation/control unit, and a workflow estimation/prediction unit, the workflow definition unit further includes, as the definition items, rearrangement definition description that is a list of workflow rearrangement algorithms, the workflow estimation/prediction unit further includes a task finish time inquiry unit for examining the finish prediction time of each task, a completion time prediction unit for predicting the completion time of the workflow operation, a definition analytical unit for analyzing the rearrangement definition description, so to supply the analyzed description of rearrangement definition, a rearrangement algorithm library for providing rearrangement algorithms, and a rearrangement unit for, according to the analyzed description of rearrangement definition, taking out a necessary rearrangement algorithm from the rearrangement algorithm library to execute the same.

Pre-locking scheme for allowing consistent and concurrent workflow process execution in a workflow management system

Abstract: A system for allowing consistent execution of a workflow process in a computer-enabled workflow management system is described. The system includes a workflow process database accessible by the workflow process. The workflow process includes at least one sequence of workflow actions, having at least one set of parallel workflow actions and being configured as a plurality of nodes interconnected by arcs. Each node defines at least one of the workflow actions and reading and writing data items when executing the workflow actions. A first module is provided to lock all data items in the workflow process database that are specified for access by the workflow process from being accessed by other workflow processes during execution of the workflow process before the execution of the workflow process is commenced. A second module is provided to release all the locked data items from being locked after the workflow process has been executed such that execution consistency and concurrency of the workflow process is maintained. A computer implemented method for allowing consistent execution of a workflow process in a computer-enabled workflow management system is also described.

Workflow Applications to Research Agenda: Scalable and Dynamic Work Coordination and Collaboration Systems

Abstract: A workflow is an activity involving the coordinated execution of multiple tasks performed by different processing entities [KS 95]. These tasks could be manual, or automated, either created specifically for the purpose of the workflow application being developed, or possibly already existing as legacy programs A workflow process is an automated organizational process involving both human (manual) and automated tasks.

Scientific workflow management by database management

Abstract: In several working environments, production involves repeated executions of certain procedures. A workflow describes the individual tasks performed in these procedures and their interrelationships. Current workflow management systems (WFMSs) use a database management system (DBMS) to store task descriptions, and implement all workflow functionality in modules that run on top of the DBMS. Motivated by scientific workflows, we propose a much more DBMS-centric architecture, in which conventional database technology provides much of the desired scientific WFMS functionality. A key element of our approach is viewing the workflow as a web of data objects interconnected with active links that carry process descriptions. The workflow is fully defined as a database schema, and its execution is the gradual buildup of an instance of this schema through the active object links. For our work, we use the modeling and querying tools of Horse, the object-oriented DBMS that we have developed in the context of the Zoo Desktop Experiment Management Environment.

Workflow distributing apparatus and method

Abstract: A system and apparatus for automatically executing process steps by processing devices transmitted, over a communication channel, using a workflow file to specify the process steps. Devices are used to edit, initiate, and observe workflow execution. Editing comprises selecting process steps, executing parameter selection software supplied by the processing device, and drawing links between icons. Once workflow execution is initiated, workflow data is passed from one processing device to the next. Each processing device performs the process step specified by the workflow file with the selected parameters and optionally sends status information to observing devices. This sequence continues until all process steps are executed or an error occurs.

Coordination in Workflow Management Systems - A Rule-Based Approach

Abstract: Coordination is a key requirement of software systems where different parts have to be adjusted in order to reach a common goal. A prominent example thereof are workflow management systems (WFMS). They in particular require flexible mechanisms to realize different kinds of coordination, which are called coordination policies. This need for flexibility emerges from the fact that coordination policies in WFMS are subject to frequent changes caused by the business environment. Flexibility is required in different directions, ranging from a dynamic evolution of existing policies to proper reactions to unpredictable situations. Active object-oriented database systems (AOODBS) along with their basic mechanism in terms of Event/Condition/Action (ECA) rules seem to be a promising technology in order to cope with these requirements. ECA rules allow for an event-driven realization of context- and time-dependent behavior which constitutes a major property of coordination policies. By encapsulating coordination policies within ECA rules, general knowledge can be represented independently from specific business processes. This both eases modification of coordination policies and enhances their reusability. To demonstrate the power of this approach, the paper identifies various coordination policies required within different areas of WFMS and outlines their mapping to ECA rules.

System and method for processing and tracking telecommunications service orders

Abstract: A system and method for tracking and processing Service Orders for a telecommunications company. Workflows are used to model business procedures used for processing Service Orders. Each Workflow comprises a plurality of Workflow steps. Business process models are depicted as Workflow diagrams. The Workflow diagrams are stored in a library in a database. Work plans comprising a plurality of Workflow steps and associated data and are derived from information found in the Workflow diagrams. Upon receipt of a Service Order, an appropriate work plan is selected based on information within the Service Order. Each Workflow step is assigned a resource and is scheduled for completion with a start and a stop date and placed in the in-boxes associated with the selected resource. Users log-on to remote workstations coupled with a company-wide Intranet or the like. From the remote workstations, users from various organizations view their in-boxes and other information about current Service Orders. Such information includes detailed information about the Service Orders including, progress data, current, future and past Workflow step data, responsible groups, computer systems and organizations, whether schedules are maintained, and whether jeopardy points have been missed. If a Service Order is delayed, users can immediately determine information about the delay and take corrective action before it becomes critical. Workflow steps can be transferred and re-assigned using the remote workstations. Detailed statistical information is maintained for audit and reporting purposes. Reports reflecting the effectiveness of workforce management and work administration is obtained.

Evaluation of Workflow Management Systems - A Meta Model Approach

Abstract: The automated enactment of processes through the use of workflow management systems enables the outsouring of the control flow from application systems. By now a large number of systems, that follow different workflow paradigms, are available. This leads to the problem of selecting the appropriate workflow management system for a given situation. In this paper we outline the benefits of a meta model approach for the evaluation and comparison of different workflow management systems. After a general introduction on the topic of meta modeling the meta models of the workflow management systems WorkParty (Siemens Nixdorf) and FlowMark (IBM) are compared as an example. These product-specific meta models can be generalized to meta reference models, which helps to specify a workflow methodology. Exemplary, an organizational reference meta model is presented, which helps users in specifying their requirements for a workflow management system.