Showing papers on "Workflow published in 1994"

Experiences with workflow management: issues for the next generation

Abstract: Workflow management is a technology that is considered strategically important by many businesses, and its market growth shows no signs of abating. It is, however, often viewed with skepticism by the research community, conjuring up visions of oppressed workers performing rigidly-defined tasks on an assembly line. Although the potential for abuse no doubt exists, workflow management can instead be used to help individuals manage their work and to provide a clear context for performing that work. A key challenge in the realization of this ideal is the reconciliation of workflow process models and software with the rich variety of activities and behaviors that comprise “real” work. Our experiences with the InConcert workflow management system are used as a basis for outlining several issues that will need to be addressed in meeting this challenge. This is intended as an invitation to CSCW researchers to influence this important technology in a constructive manner by drawing on research and experience.

An Overview of Repository Technology

Abstract: A repository is a shared database of information about engineered artifacts We define a repository manager to be a database application that suPports checkout/checkin, version and configuration management, notification, context management, and workflow control Since the main value of a repository is in the tools that use it, we discuss technical issues of integrating tools with repositories We also discuss how to implement a repository manager by layering it on a DBMS, focusing especially on issues of programming interface, performance, distribu,; tion, and interoperability

Implementing agent coordination for workflow management systems using active database systems

Abstract: A new way to enact business processes in enterprises is to deploy workflow technology. Workflow systems are proactive computer systems, which orchestrate the execution of long-living processes. Process agents, i.e. members of the organization structures of an enterprise, are in charge of executing processes and process steps. Workflow management systems have do associate appropriate process agents to processes proactively. We call this task process agent coordination. We show that ECA rules implemented on top of active database systems are suitable to facilitate agent coordination in workflow management systems. >

Ethnography and design

Abstract: Recent articles by Suchman and her colleagues address the tension between ethnography and design. "Ethnographers develop a descriptive understanding of the lifeways of the group studied. Ethnographers describe how people actually behave, not how they ought to behave.., descriptive instead of prescriptive" (Blomberg, Giacomi, Mosher and Swenton-Wall, 1993, pp. 123-127). "Our reluctance to translate our practice directly into design terms was met with frustration from the design community... Rather than feeling inadequate in the face of demands that our work produce design implications, we began to resist those demands" (Suchman, 1994, pp. 30-31). These ethnographers do explore ways to engage design, but we feel that recognizing the ethnographers' deep professional bias against intervention is important in understanding the dialogue between Suchman and Winograd, as well as in positioning the unquestionably valuable contributions of ethnography to design. Suppose that a group of people has reached a degree of skilled proficiency at a task. Further suppose that technology could be introduced that would enable the group to reach a satisfying and higher level of achievement. A crucial question is: How often could such a group move from its initial "peak" to the higher

The PIF Process Interchange Format and Framework PIF Working Group

Abstract: This document describes the first version of the Process Interchange Format (PIF, version 1.0). The goal of this work is to develop an interchange format to help automatically exchange process descriptions among a wide variety of business process modeling and support systems such as: workflow software, flow charting tools, process simulation systems, and process repositories. Instead of having to write ad hoc translators for each pair of such systems, each system will only need to have a single translator for converting process descriptions in that system into and out of the common PIF format. Then any system will be able to automatically exchange basic process descriptions with any other system. The current PIF format includes a core set of object types (such as activities, actors, and prerequisite relations) that can be used to describe the basic elements of any process. The PIF format also includes a framework for extending the core set of object types to include additional information needed in specific applications. These extended descriptions are exchanged in such a way that the common elements are interpretable by any PIF translator and the additional elements are interpretable by any translator that knows about the extensions. The PIF format was developed by a working group including representatives from several universities and companies and has been used for experimental automatic translations among systems developed independently at three of these sites. This document is being distributed in the hopes that other groups will comment upon the interchange format proposed here and that this format (or future versions of it) may be useful to other groups as well.

A client/server architecture for distributed workflow management systems

Abstract: A specific task of distributed and parallel information systems is workflow management, In particular, workflow management system execute business processes that run on top of distributed and parallel information systems. Parallelism is due to performance requirements and involves data and applications that are spread across a heterogeneous, distributed computing environment. Heterogeneity and distribution of the underlying computing infrastructure should be made transparent in order to alleviate programming and use. We introduce an implementation architecture for workflow management systems that meets best these requirements. Scalability (through transparent parallelism) and transparency with respect to distribution and heterogeneity are the major characteristics of this architecture. A generic client/server class library in an object-oriented environment demonstrates the feasibility of the approach taken. >

Policy resolution in workflow management systems

Abstract: We introduce policy resolution (PR) for workflow management systems (WFMS) as service to assign work to agents. Policy resolution is a framework for defining arbitrary role and organization models together with operations suiting the needs of workflow management systems.<>

Automating workflows for service order processing: integrating AI and database technologies

Abstract: We have developed an AI-based architecture that automatically manages workflows, and we have implemented a prototype that executes on top of a distributed computing environment to help a telecommunications company better provide a service that requires coordination among many operation support systems and network elements. The activities involve several database systems, user interfaces, and application programs. >

Towards effective implementation of a pediatric asthma guideline: integration of decision support and clinical workflow support.

Abstract: Successful local implementation of national guideline recommendations requires attention to factors that promote clinician compliance. Design of a computerized system is described that will implement recommendations from a recently published guideline for outpatient management of childhood asthma exacerbations. Logical analysis of the guideline shows that it is incomplete and contains several ambiguities that must be addressed before the guideline can be operationalized. Once the user-audience is defined guideline decision points are examined and a structured data entry system is devised. Support of clinicians' workflow is provided by an integrated capability for encounter documentation, dosage calculation, and prescription-writing. A pen-based, graphical interface represents an appropriate platform for implementation of the system because of its ease of use and portability.

Method and apparatus for managing business processes

Abstract: A workflow management system which performs eight key functions: i) notifies the user that he or she has a step to begin or to complete (Names/Routings); ii) provides the user with the proper tools to complete a task (Transaction Manager); iii) provides the user with the proper information to complete a task (Workflow Server); iv) allows the user to see where a task fits in the overall process (Schedule); v) manages the proper reminders, alerts, and follow-ups to keep the process moving (Transaction Manager); vi) automates certain standard procedures; vii) integrates with the organization's existing business systems; and viii) provides simple application program interfaces that allow developers to develop new custom applications that are workflow-enabled (Workflow Updater)

Trigger modelling for workflow analysis

Abstract: Trigger modelling is a technique that is meant to assist in the analysis of workflows in order to automate (parts of) the workflow. The simplicitity of the technique makes it usable for workflow analysts in practice. The technique has a formal semantics, which makes it suitable for support by CASE tools. It has been validated by user experiments and by building a prototype.

The GroupFlow System: A Scalable Approach to Workflow Management between Cooperation and Automation

Abstract: In this paper, we will discuss business relevance factors, architectural concepts, tool approaches, and user-interface samples of the GroupFlow environment GroupFlow offers business process and technology frameworks to set up versatile and flexible workflow systems for distributed information management within organizations and with their outside communication partners We regard the synergetic approaches being used in the GroupFlow architecture — for the frontend client-workplaces of the several user typologies as well as for the distributed backend server components — as innovative The GroupFlow environment perhaps best can be profiled around integrating concepts that are typically referred to as workgoup computing or Groupware on the one hand, and workflow management or business process design on the other

A system and method for artwork design and production

Abstract: A system and method for artwork design and production is disclosed. The system includes an artwork preparation administrator (100) and a plurality of operation units (102 to 112) each of which performs at least one of a multiplicity of different artwork preparation tasks. The administrator (100) includes a workflow manager (114) and a workflow definition unit (116) for managing the production of a user-defined workflow having a multiplicity of artwork preparation tasks. The workflow manager (114) includes a) apparatus for initiating operation of selected operation units, b) apparatus for receiving and processing task information from the selected operation units when they perform one of the artwork preparation tasks and c) apparatus for producing a process list. The process list includes processed task information from at least one of the artwork preparation tasks and is ordered in accordance with a portion of the workflow which has at least one artwork preparation task therein.

Organization Models for Cooperative Office Applications

Abstract: Regulated communication and cooperation between members of an enterprise relies on organization structures of the enterprise. This is explained in the introduction implying that an organization model is necessary for realizing application systems to support this type of cooperative work. The main part of this paper describes the Organization and Resources Management system ORM which makes it possible to build organization models and use them in application systems. As an example, the use of ORM in a workflow management system is described. ORM stores its models in a relational database with an SQL interface and implements a set of automatic inheritance rules for authority assignments to organizational entities. These rules follow common organizational practice. Problems of implementing these features with a relational database are discussed. Finally, directions for future developments and exploration areas are suggested.

A Multimedia Enhanced CSCW Teleservice for Wide Area Cooperative Authoring of Multimedia Documents

Abstract: This paper presents the concept and general architecture of a multimedia enhanced CSCW teleservice that controls and monitors cooperative multiauthoring processes for possibly multimedia documents. Involved authors can be worldwide geographically dispersed. The instantiation of such a process is performed by submitting a workflow specification including multimedia directives which informally describe corresponding authoring activities. Document components completed in preceding authoring activities can be specified as activity input. The document data are fully incorporated within the workflow artifacts. The central component is a multimedia archive that provides integrated workflowand document management functionality. A multimedia mail teleservice designed for public networks is used as communication means. Using the proposed CSCW teleservice, authoring processes can be completed in a smooth, reliable, and timely manner. Authors are relieved from tasks that bear a high potential for workflow violations and delay.

Temporal Reasoning for Automated Workflow in Health Care Enterprises

Abstract: We have demonstrated through example clinical scenarios, and results with our temporal reasoner Tachyon that temporal reasoning can be a valuable tool for managing and improving the workflow of business processes, particularly in healthcare. We have also identified areas where Tachyon can be extended to provide even more support for automated workflow.

Building a Laboratory Information System Around a C++-Based Object-Oriented DBMS

Abstract: However, MapBase also turned out to share many characteristics of classical information systems: it provides a central repository of carefully administered, mission-critical data used by clients written in many languages and running on a variety of hardware. In addition, our laboratory emphasizes continuous process re-engineering, with the result that MapBase’s schema must evolve rapidly in order to reflect the current experimental workflow.

Automating workflows for service provisioning: integrating AI and database technologies

Abstract: Workflows are the structured activities that take place in information systems in typical business environments. These activities frequently involve several database systems, user interfaces, and application programs. Traditional database systems do not support workflows to any reasonable extent. Usually, human beings must intervene to ensure their proper execution. We have developed an architecture based on AI technology that automatically manages workflows. This architecture executes on top of a distributed computing environment. It has been applied to automating service provisioning workflows; an implementation that operates on one such workflow has been developed. This work advances the Camel Project's goal of developing technologies for integrating heterogeneous database systems. It is notable in its marriage of AI approaches with standard distributed database techniques. >

Intelligent validation and routing of electronic forms in a distributed workflow environment

Abstract: This paper describes a knowledge-based system for improving the efficiency of automated workflow systems by 1) ensuring the correctness and completeness of data contained on forms that are originated and transmitted electronically, and 2) generating an electronic "routing slip" that reflects who must approve the form. The system uses a form-independent validation engine and form-specific constraints to check that electronic forms are filled out correctly. If no errors are detected during validation, the system uses information on the form to generate a list of individuals and/or organizations that must approve it. The system, implemented in CLIPS and running on Macintosh computers, communicates with an off-the-shelf electronic forms package via AppleScript and can operate within the Apple Open Collaboration Environment (AOCE). The system has successfully validated and generated approval paths for approximately ten different types of forms, and is easily extended to new forms. >

Keeping Workflow Models as Simple as Possible

Abstract: Workflow Management Systems are composed of two basic components: the Workflow Model and the Workflow Execution Module. The former devoted to supporting the designer of a workflow support system, while the latter executes it when a workflow is started by any authorized user. We claim that the simpler the Workflow Model, the more flexible and adaptive the Workflow Execution Module. That is, the two main components of a Workflow Management System are not merely inter-related: if the former allows simple models and complex behaviours, then the latter is able to support execution and changes in an effective manner. In this paper we present a new Workflow Model based on a small subclass of Elementary Net Systems whose elements are simple and highly readable models that, thanks to some nice mathematical properties of that class, allow us to generate a large class of behaviours from those models. Moreover we will show that some interesting features proposed in the literature to enhance the usability of Workflow Management Systems can be easily embedded within it.

Development of a Multimedia Archiving Teleservice Using the DFR Standard

Abstract: In this paper, we describe the development of an archiving system according to the BERKOM teleservice “Multimedia Archiving” defined recently. This teleservice is utilized for storage and retrieval of multimedia documents. It can be exploited in applications that require document pools, information services, and workflow management. As a basis of our system we use the ISO/IEC standard “Document Filing and Retrieval (DFR)”. We have chosen the following approach for the integration of multimedia documents within the DFR environment. (1) A specific attribute for DFR-Documents is introduced to model multimedia documents. (2) A dual stack is used separating transmission of discrete data and continuous data like audio and video. An architecture based on this solution is outlined. Especially, the usage of an object-oriented database management system for the storage of multimedia documents is motivated. As an application scenario we describe a multimedia calendar of events.Finally, we evaluate our concepts and describe further developments.

Modeling cooperative work for workflow management

Abstract: Characteristic to workflow management is modeling of workflow of manual coordination activities and automated production activities. Conceptual models are used to analyze and describe workflow, though most of these models are not very suitable for representing and relating both coordination activities and production activities. In the Input-Process-Output paradigm, workflow is modeled in terms of processes and data flow, whereas the Customer-Supplier paradigm defines conversation patterns between the actors. The rather intimate relationship between actor interactions and processual structures is recorded in neither of them. In this paper, we suggest to extend the IPO paradigm with concepts for coordination activities. We introduce actors and services as a separate model, and show how two-way flows, ports and rules help us model cooperative and manual aspects in data flow diagrams.

A framework for automatic improvement of workflows to meet performance goals

Abstract: Business performance improvement is arguably the most important factor in the development or reengineering of a business information system. We present a framework that, given a model of a business information system and a performance goal, helps determine the modifications required in the model in order to meet the performance goal. The framework includes: an executable system model based on workflows, triggers, and execution resources; an execution environment that measures system performance; improvement operators that can modify the system model; and an automatic improvement mechanism that uses AI search techniques to guide the modification of the system model to meet a performance goal. >

Archives and the new information architecture of the late 1990s. Commentaries

Abstract: While hardware capabilities will increase dramatically through the end of this decade, the real change in electronic technology will be the spread of an information architecture. This architecture will change the model of how we interact with computerbased information. The spread of new software technologies, such as object-oriented software, workflow, document-centric computing, and database-centric computing, will change substantially our traditional information-processing model. Of greatest interest to archivists will be the potential of this change to integrate today's diverse information search and retrieval strategies and technologies.

The fifteenth level (keynote address)

Abstract: The burgeoning workflow software industry did about $200 million business in the U.S. in 1993 and is expected to reach $2.5 billion in 1996. Workflow systems are based on a different conception of work than that on which the entire architecture of operating systems is based. The new conception of work is concerned with the fulfillment of commitments made between people, whereas operating systems treat work as the execution of computational tasks. (1)

A Transaction-Oriented Workflow Activity Model

Abstract: The combination of workflow systems and database management systems significantly facilitates the design and reliable management of complex business processes. In this paper we present a high-level workflow activity description language and an advanced transaction mechanism to design long running activities. The strength of our model is the simplicity of the language and the application independent transaction facility which supports highly concurrent and reliable execution of workflow activities.

Systems will be people too

Abstract: In the few decades that computers have been used by society, our perception of them and their uses has developed several times; computation machine, data processing system, information processing system Another development is occurring today; process support system By 2001 this development will itself be established and become the basis for the next development in the continuing evolution of our use of machines To date, we have concentrated on satisfying the information needs of the individual Our development methods and the infrastructure products we use all assume a model in which the computer takes information in from the individual, stores and processes it, and makes it available again to the individual In the coming years, those information needs will still have to be satisfied, but increasingly within a much larger context; that of the group carrying out a business process The products are currently leading the way, suggesting solutions; workflow management, workgroup computing, document image processing etc The challenge for the late 1990s is to develop the systematic methods that will take us from requirements to group support system in a reliable and predictable way, in the same way that the structured methods of the 1970s worked for our data- and information-oriented systems