Showing papers on "Workflow published in 1997"

Dynamic and generic process automation system

Abstract: GPAE is a dynamic and generic object-oriented process automation engine that provides workflow management (WFM) services in a heterogeneous distributed computing environment. This invention decouples process definitions, run-time process management, and process execution agents. The system consists of three major parts: (a) a build time part used to capture and store process definitions, and to request the enactment of a process; (b) a run time part used to schedule, execute, and monitor the requested process; (c) a CORBA bus to plug-in software applications needed to execute processes, and to allow interactions among the system components. This GPAE invention, based on CORBA, and event-driven and constraint propagation models, provides near optimal scheduling and resource allocation schemes. This invention is generic, scalable, flexible, and enables the process automation in a distributed heterogeneous platform environment, while sharing global resources and services efficiently.

Workflow management employing role-based access control

Abstract: A workflow sequence specified by a process definition is managed by a workflow management system which enacts each segment in the order specified by that process definition. Role-based access control (RBAC) is used to define membership of individuals in groups, i.e., to assign individuals to roles, and to then activate the roles with respect to the process at appropriate points in the sequence. Any individual belonging to the active role can perform the next step in the business process. Changes in the duties and responsibilities of individuals as they change job assignments are greatly simplified, as their role memberships are simply reassigned; the workflow process is unaffected.

Mechanism for heterogeneous, peer-to-peer, and disconnected workflow operation

Abstract: A mechanism for heterogeneous, peer-to-peer, and disconnected workflow execution across a network infrastructure. Performer Agent entities provide a homogeneous view of humans, applications, and heterogeneous workflow systems and components that act as Performers on the network by executing Tasks. Source Agent entities provide a homogeneous view of heterogeneous service requesters such as workflow scripts executing on different workflow systems, which generate Activities that need to execute on Performers as Tasks. Task Request and Task Response messages are used to standardize the communication between Source Agents and Performer Agents, along with other messages for controlling and queuing Tasks. Workflow systems interact with each other as peers using this mechanism by sending workflow execution requests, workflow script templates, and workflow execution environments to each other. Disconnected operation is handled by ensuring the continuous availability of Source Agents and Performer Agents on the network and providing a mechanism for Sources to disconnect from Source Agents and Performers to disconnect from Performer Agents.

System for automated workflow in a network management and operations system

Abstract: Methods and systems for automating the dissemination and processing of alarm reports received from a telecommunications network are provided. Alarm reports, which are provided to network monitors by a network management system, correspond to alarms that are generated by the telecommunications network. Network monitors view these alarm reports and group them together to form event reports. The network monitors then use the event reports to produce trouble reports that are processed by a trouble management system. The trouble management system dispatches field engineers to repair networks anomalies in accordance with these trouble reports. An automated workflow system provides automated alarm report dissemination and processing. The automated workflow system provides a graphical interface to view and manipulate alarm reports and to automatically create and handle event reports and trouble tickets. The workflow system also allows network monitors to identify which network component within the telecommunications network generated a specific alarm and to append telecommunications network site and topology data to event reports. The automated workflow system also tracks the status of the trouble tickets subsequent to their creation and automatically updates associated event and alarm reports.

Plans as situated action: an activity theory approach to workflow systems

Abstract: Within the community of CSCW the notion and nature of workflow systems as prescriptions of human work has been debated and criticised. Based on the work of Suchman (1987) the notion of situated action has often been viewed as opposed to planning work. Plans, however, do play an essential role in realising work. Based on experiences from designing a computer system that supports the collaboration within a hospital, this paper discusses how plans themselves are made out of situated action, and in return are realised in situ. Thus, work can be characterised as situated planning. This understanding is backed up by Activity Theory, which emphasises the connection between plans and the contextual conditions for realising these plans in actual work.

Workflow-based applications

Abstract: A significant number of companies are reengineering their business to be more effective and productive. Consequently, existing applications must be modified, and new applications must be written. The new applications typically run in a distributed and heterogeneous environment, performing single tasks in parallel, and demanding special transaction functionality for the supporting environments. Workflow-based applications offer this type of capability. In this paper, their principal advantages are derived and set in context to transaction, object, and CASE (computer-assisted software engineering) technology. In particular, a method is proposed to develop these workflow-based applications in a cohesive and consistent way.

Method and apparatus for distributed workflow building blocks of process definition, initialization and execution

Abstract: A workflow system that automates the definition and execution of a procedure that can be carried out according to defined rules among agents. Agents may be individual users, work groups, organizations, or automatic systems. Automation is used to guarantee that all the individual activities are taken in the defined sequence, form, and time. The system separates the three basic elements necessary to perform a procedure--a co-ordination service, an organization service, and a transport service. The coordination service ensures proper sequence of the activities of the procedure. The organization services identifies a particular agent to perform a task within a procedure. The agent selection can be made when the procedure is defined, or it can be deferred until an instance using the procedure is performed. The transport service is used to move information between agents and an information service, which holds instance data, while processing an instance.

A Formal Foundation for Distributed Workflow Execution Based on State Charts

Abstract: This paper provides a formal foundation for distributed workflow executions. The state chart formalism is adapted to the needs of a workflow model in order to establish a basis for both correctness reasoning and run-time support for complex and large-scale workflow applications. To allow for the distributed execution of a workflow across different workflow servers, which is required for scalability and organizational decentralization, a method for the partitioning of workflow specifications is developed. It is proven that the partitioning preserves the original state chart's behavior.

System for distributed workflow in which a routing node selects next node to be performed within a workflow procedure

Abstract: A workflow system that automates the definition and execution of a procedure that can be carried out according to defined rules among agents. Agents may be individual users, work groups, organizations, or automatic systems. Automation is used to guarantee that all the individual activities are taken in the defined sequence, form, and time. The system separates the three basic elements necessary to perform a procedure--a co-ordination service, an organization service, and a transport service. The coordination service ensures proper sequence of the activities of the procedure. The organization services identifies a particular agent to perform a task within a procedure. The agent selection can be made when the procedure is defined, or it can be deferred until an instance using the procedure is performed. The transport service is used to move information between agents and an information service, which holds instance data, while processing an instance.

Workflow Handbook 1997

Abstract: THE WORLD OF WORKFLOW. Introducing Workflow. The Business Impact of Workflow. Applications of Workflow. Implementing Workflow. The Future of Workflow. WORKFLOW STANDARDS. The Workflow Reference Model. WAPI Specification the Workflow Client Application Programming Interface. WAPI Naming Conventions. The WfMC Glossary. THE DIRECTORY. WfMC Structure and Membership Details. Workflow Management Coalition Member Directory. Appendices. Further Reading and Sources of Information. Indexes.

Workflow and Process Automation: Concepts and Technology

Abstract: Preface. 1. Introduction. 2. Process Technology. 3. Workflow Technology. 4. Transactional Aspects of Workflows. 5. Ongoing Research in Workflow and Process Automation. 6. State of the Industry. References. Index.

Workflow object compiler with user interrogated information incorporated into skeleton of source code for generating executable workflow objects

Abstract: A message driven processor operates as middleware between clients and back-end hosts or servers in a large client-server system to reduce the number of concurrent sessions required to be supported by the network and to allow a common client user interface to divergent back-end systems. High level requests from a client in support of a business function are translated into workflows which may involve multiple requests to back-end servers by the message driven processor. Information resulting from workflows and information retrieved from back-end servers may be integrated into a single reply message to the requesting client.

Workflow management method and apparatus

Abstract: A workflow management method in a workflow system including a workflow server and tables for holding processes includes storing in a table a plurality of definition information sets for individually defining workflows for a plurality of processes included in a job for processing a plurality of works to be circulated, wherein the plurality of definition information sets each have a process ID, a process name, and a user role ID, and at least one of the plurality of definition information set has predetermined data for connecting processing defined by another definition information set in the user role ID, and storing in a table a work management information set created for each of the plurality of works subjected to processing by the job, the work management information set having a process ID, a process name, a user role ID, and a flag representative of whether or not workflow processing corresponding to processing of each work has been terminated. The process ID has a process ID indicative of the location of the other definition information set when the user role ID includes the first predetermined code indicating that the workflow processing is defined in the other definition information set. After copying and updating one of the plurality of stored definition information sets, the one definition information set can be stored in the table. A table can be provided for storing therein a process management information set having a utilization permission flag indicative of whether or not the plurality of definition information sets, stored in the table, may be copied. A table can also be provided for storing a suspended work information set including an ID of one of the plurality of works to be circulated, and a workflow ID indicative of a workflow in which the one work should be suspended.

Design and implementation of a virtual information system for agile manufacturing

Abstract: In the new and emerging agile manufacturing paradigm, where multiple firms cooperate under flexible virtual enterprise structures, there exists a great need for a mechanism to manage and control information flow among collaborating partners. In response to this pressing need, this paper addresses the design and implementation of an agile manufacturing information system integrating manufacturing databases dispersed at various partner sites. We propose a framework in which: (1) information is modeled in a hierarchical fashion using object-oriented methodology (OOM); (2) information transactions are specified by the workflow hierarchy consisting of partner workflows; (3) information flow between partners is controlled by a set of distributed workflow managers (WM) interacting with partner knowledge bases, which reflect partner specific information control rules on internal data exchange, as well as inter-partner mutual protocols for joint partner communications; (4) the prototype system is accomplished using the World Wide Web based on a client-server architecture. The overall approach and system provides within a dynamic environment, where virtual partnerships are synthesized in response to specific business initiatives, a dynamic and flexible mechanism to support partner information exchange and to keep the dispersed information consistent.

Executable workflows: a paradigm for collaborative design on the Internet

Abstract: This paper introduces a directed hypergraph modelthat supports (1) workflow composition and reconfigurationwhile accessing and executing programs, data, and computingresources across the Internet, (2) synchronous and asynchronouspeer-to-peer interaction between members of anyteam during workflow composition and execution, (3) synchronousand asynchronous peer-to-workflow interaction betweenany team member and any object in the workflow.Given a library of program and data nodes, editing theworkflow and its execution is as intuitive as the hierarchicalschematic design capture and simulation.Examples of multi-sitemulti-user applications demonstrate that the proposedworkflow implementation provides a user-friendly paradigmfor distracted and collaborative team design.

A framework for dynamic changes in workflow management systems

Abstract: Current workflow management systems (WFMSs) are only applicable in a reliable and secure manner if the business process (BP) to be supported is well structured. As ad hoc deviations from preplanned BPs are rather the norm and form a key part of process flexibility, this limits the applicability of today's workflow (WF) technology significantly. We present a framework for the support of ad hoc structural changes of WFs. Basic to our approach is a conceptual, graph based WF model which has a formal foundation in its syntax and operational semantics. Based upon this model, we have developed a complete and minimal set of change operations which support users in modifying the structure of WFs at runtime, while preserving their correctness and consistency.

Generating process models from workflow logs

Abstract: A computer-implemented method, apparatus, and article of manufacture that constructs graph models from logs of past, unstructured executions of the given process. The graph model so produced conforms to the dependencies and past executions present in the log. By providing graph models that capture the previous executions of the process, this technique allows easier introduction of a workflow system and evaluation and evolution of existing processes.

Method and apparatus for utilizing a standard transaction format to provide application platform and a medium independent representation and transfer of data for the management of business process and their workflows

Abstract: The present invention is a method and apparatus which is used to enable application developers to generate workflow enabled applications which request services from the workflow server component of the workflow system, remotely and indirectly using messaging, shared databases or inter-process communications. The present invention provides a standard transaction format (STF) for accessing such a workflow system through STF processors via messaging, updates to the shared databases or inter-process communications. Workflow enabled applications are used by users to act and participate in business processes and enable users and managers to observe and query the status of workflows and business processes.

Method for executing a procedure that requires input from a role

Abstract: A method for executing a workflow that requires input from a role is disclosed. A workflow is executed in a first process until an operation requiring input from a role is detected. Continuation information is stored indicating the workflow operation requiring input from the role. The request for input from the role is then communicated to a computer-user identified with the role. Later, after receiving input from the computer user, execution of the workflow is resumed in a second process based on the continuation information, starting at the operation that required input from the role. The operation that required input from the role is executed based on the response received from the computer-user identified with the role.

Transactions in Transactional Workflows

Abstract: Workflow management systems (WFMSs) are finding wide applicability in small and large organizational settings. Advanced transaction models (ATMs) focus on maintaining data consistency and have provided solutions to many problems such as correctness, consistency, and reliability in transaction processing and database management environments. While such concepts have yet to be solved in the domain of workflow systems, database researchers have proposed to use, or attempted to use ATMs to model workflows. In this paper we survey the work done in the area of transactional workflow systems. We then argue that workflow requirements in large-scale enterprise-wide applications involving heterogeneous and distributed environments either differ or exceed the modeling and functionality support provided by ATMs. We propose that an ATM is unlikely to provide the primary basis for modeling of workflow applications, and subsequently workflow management. We discuss a framework for error handling and recovery in the METEOR2 WFMS that borrows from relevant work in ATMs, distributed systems, software engineering, and organizational sciences. We have also presented various connotations of transactions in real-world organizational processes today. Finally, we point out the need for looking beyond ATMs and using a multi-disciplinary approach for modeling large-scale workflow applications of the future.

Plans as Situated Action: An Activity Theory Approach to Workflow Systems

Abstract: Within the community of CSCW, the notion and nature of workflow systems as prescriptions of human work has been debated and criticised. Based on the work of Suchman (1987) the notion of situated action has often been viewed as opposed to planning work. Plans, however, do play an essential role in realising work. Based on experiences from designing a computer system that supports the collaboration within a hospital, this paper discusses how plans themselves are made out of situated action, and in return are realised in situ. Thus, work can be characterised as situated planning. This understanding is backed up by Activity Theory, which emphasises the connection between plans and the contextual conditions for realising these plans in actual work.

From contemporary workflow process automation to adaptive and dynamic work activity coordination and collaboration

Abstract: This position paper outlines a research agenda for researchers in the area of workflow. We believe that today’s workflow systems should evolve to what is termed as work coordination and collaboration systems (WCCSs). A WCCS will (a) adapt to various changes in the organization (including its interactions with external organizations) and the organizational processes by being able to change the processes definitions as well as change the processes and component activities while they are being enacted or executed, and (b) support a unified framework for managing coordination, collaboration, and information- based decision making activities that naturally occur as part of organizational processes. A WCCS can then not only support automation of the routine and well defined processes, but also support better human involvement and manage more complex, dynamic, and higher value mission critical processes. This can lead to significantly improved productivity and quality of results . It is further suggested that a multidisciplinary approach is an essential element of the part toward developing WCCSs.

On Correctness Issues in Conceptual Modelling of Workflows.

Abstract: The conceptual modeling of workflows is the first, and arguably the most important, step towards understanding business processes A well-defined workflow conceptual model leads to the development of an effective and reliable workflow application This paper presents a graphical modeling technique for workflows We introduce four graphical modeling objects: task, condition, synchronizer, and flow Using the four modeling objects, following workflow modeling constructs are identified: ordering, alternative, exclusive join, concurrency, synchronization, iteration, start/stop, nesting, and contingency It is possible to easily get into error situations while building large workflow specifications We present a set of constraints for ensuring the correctness of workflow specifications The concepts introduced in this paper are applied as a foundation to the development of a CASE tool for the modeling and syntactical verification of workflow graphs

The Chautauqua workflow system

Abstract: Chautauqua is an exploratory workflow management system designed and implemented within the Collaboration Technology Research group (CTRG) at the University of Colorado. This system represents a tightly knit merger of workflow technology and groupware technology. Chautauqua has been in test usage at the University of Colorado since 1995. The article discusses Chautauqua-its motivation, its design, and its implementation. The emphasis is on its novel features, and the techniques for implementing these features.

Knowledge-based techniques to increase the flexibility of workflow management

Abstract: This paper describes how knowledge-based techniques can be used to overcome problems of workflow management in engineering applications. Using explicit process and product models as a basis for a workflow interpreter allows us to alternate planning and execution steps, resulting in an increased flexibility of project coordination and enactment. To gain the full advantages of this flexibility, change processes have to be supported by the system. These require an improved traceability of decisions and have to be based on dependency management and change notification mechanisms. Our methods and techniques are illustrated by two applications: Urban land-use planning and software process modeling.

Geo-Opera: Workflow Concepts for Spatial Processes

Abstract: A Process Support System provides the tools and mechanisms necessary to define, implement and control processes, i.e., complex sequences of program invocations and data exchanges. Due to the generality of the notion of process and the high demand for the functionality they provide, process support systems are starting to be used in a variety of application areas, from business re-engineering to experiment management. In particular, recent results have shown the advantages of using such systems in scientific applications and the work reported in this paper is to be interpreted as one more step in that direction. The paper describes Geo-Opera, a process support system tailored to spatial modeling and GIS engineering. Geo-Opera facilitates the task of coordinating and managing the development and execution of large, computer-based geographic models. It provides a flexible environment for experiment management, incorporating many characteristics of workflow management systems as well as a simple but expressive process modeling language, exception handling, and data and metadata indexing and querying capabilities.

Ad-hoc workflow: problems and solutions

Abstract: The paper introduces ad hoc workflow, adding flexibility to traditional workflow. A problem that stems from the added flexibility is the need to support end users in the selection and modification of the process for a specific case. We propose a class of Petri nets to describe workflow processes, featuring safeness and guaranteed termination. A set of transformation rules with sufficient power for this class is given that can be implemented in a graphical editor. A second problem is monitoring the work being done. The solution is to approximate the states of the cases being treated by the states of a few standard cases.

ePERT: extending PERT for workflow management systems

Abstract: Workflows management systems support the definition and execution of business processes. While business process reeingeneering tools use time information to simulate and optimize processes, themanagement of time is hardly supported in workflows systems. We introduce a concept for time management for workflows systems. It consists of calculating internal deadlines for all activities within a workflows, checking time constraints and monitoring time at run-time. For the calculation of internal deadlines we extend the netdiagram technique PERT to support the structures usually found in workflows. At run-time this time information is used to pro-acticely avoid time errors and reactively resolve time failures. The concept has been implemented in our prototype workflows management system Panta Rhei.

A distributed execution environment for large-scale workflow management systems with subnets and server migration

Abstract: If the number of users within a workflow management system (WFMS) increases, a central workflow server (WF-server) and a single local area network (LAN) may become overloaded. The approach presented in the paper describes an execution environment which is able to manage a growing number of users by adding new servers and subnets. The basic idea is to decompose processes into parts which are controlled by different WF-servers. That is, during the execution of a workflow instance its execution (step) control may migrate from one WF-server to another. By selecting the appropriate physical servers (for hosting the WF-servers) in the appropriate LANs, communication costs and individual WF-server workload can be reduced significantly.

RainMan: a workflow system for the internet

Abstract: As individuals and enterprises get interconnected via global networks, workflows that scale beyond traditional organizational boundaries and execute seamlessly across these networks will become relevant. We address the problem of designing a scalable workflow infrastructure for the Internet that supports both flexibility in workflow participation and interoperability between heterogeneous workflow system components. RainMan is a distributed workflow system developed in Java that lives naturally on the Internet. RainMan is a loosely-coupled collection of independent services that cooperate with each other rather than a monolithic system. Some of the useful features of RainMan are browser-based workflow specification, participation, and management, and dynamic workflow modification. The RainMan system is based on RainMaker, our generic workflow framework that defines a core set of well-defined interfaces for workflow components.