Workflow

A workflow is a depiction of a sequence of operations, declared as work of a person, work of a simple or complex mechanism, work of a group of persons, [See e.g., ISO 12052:2006, [http://www.iso.org] ] work of an organization of staff, or machines. Workflow may be seen as any abstraction of real work, segregated in workshare, work split or whatever types of ordering. For control purposes, workflow may be a view on real work under a chosen aspect, [See e.g., ISO/TR 16044:2004, [http://www.iso.org] ] thus serving as a virtual representation of actual work.

A workflow is a model to represent real work for further assessment, e.g., for describing a reliably repeatable sequence of operations. More abstractly, a workflow is a pattern of activity enabled by a systematic organization of resources, defined roles and mass, energy and information flows, into a "work process" that can be documented and learned. [See e.g., on workflow patterns [http://www.workflowpatterns.com/documentation/documents/BPM-06-22.pdf] ] [See e.g., workflow pattern analysis [ftp://ftp.informatik.uni-stuttgart.de/pub/library/medoc.ustuttgart_fi/STUD-2052/STUD-2052.pdf] ] Workflows are designed to achieve processing intents of some sort, such as physical transformation, service provision, or information processing.

Workflow concepts are closely related to other concepts used to describe organizational structure, such as silos, functions, teams, projects, policies and hierarchies. Workflows may be viewed as one primitive building block of organizations. The relationships among these concepts are described later in this entry.

The term "workflow" is used in computer programming to capture and develop human to machine interaction. Workflow software aims to provide end users with an easier way to orchestrate or describe complex processing of data in a visual form, much like flow charts but without the need to understand computers or programming.

Related concepts

The concept of workflow is closely related to several other fields in operations research and other fields that study the nature of work, either quantitatively or qualitatively, such as artificial intelligence (in particular, the sub-discipline of AI planning) and ethnography. The term "workflow" is more commonly used in particular industries, such as printing, and professional domains, where it may have particular specialized meanings.

# Processes: A process is a more specific notion than workflow, and can apply to physical or biological processes, for instance. In the context of concepts surrounding work, a process may be distinguished from a workflow by the fact that it has well-defined inputs, outputs and purposes, while the notion of workflow may apply more generally to any systematic pattern of activity (such as all processes occurring in a machine shop).
# Planning and scheduling: A plan is a description of the logically necessary, partially-ordered set of activities required to accomplish a specific goal given certain starting conditions. A plan, when augmented with a schedule and resource allocation calculations, completely defines a particular "instance" of systematic processing in pursuit of a goal. A workflow may be viewed as an (often optimal or near-optimal) realization of the mechanisms required to repeatedly execute the same
# Flow control is a control concept applied to workflows to divert from static control concepts applied to stock, that simply managed the buffers of material or orders, to a more dynamic concept of control, that manages the flow speed and flow volumes in motion and in process. Such orientation to dynamic aspects is the basic foundation to prepare for more advanced job shop controls, as just-in-time or just-in-sequence.
# In transit visibility is a monitoring concept that applies to transported material as well as to work in process or work in progress, i.e., workflows.

Historical development

In the 1980s, the term "workflow" was first used in its modern form in the software industry by Filenet vice president David Siegel.Fact|date=March 2008 The company called its business process automation software "Workflo".

In 1995, the publishing industry studied how traditional publishing processes could be re-engineered and streamlined into digital processes in order to reduce lagtime, as well as substantial printing and shipping costs for delivering print copies of books and journals to warehouses and subscribers. The term "electronic workflow" was used to describe the publishing process, from online delivery of digital manuscripts to the posting of content on the web for online access.

The development of the concept of workflow occurred over a series of loosely defined, overlapping, eras.

Pre-history

Many historical projects, such as the pyramids and cathedrals, required highly organized labor. The idea that one can create value by studying the nature of work itself can be attributed to Adam Smith.Fact|date=June 2008

Beginnings in manufacturing

The modern history of workflows can be traced to F. W. Taylor [Taylor, 1919] and H. Gantt. Together they launched the study of the deliberate, rational organization of work in the context of manufacturing. The types of workflow of concern to Taylor and his contemporaries primarily involved mass and energy flows. These were studied and improved using time and motion studies. While the assembly line remains the most famous example of a workflow from this era, the early thinking around work was far more sophisticated than is commonly understood. The notion of "flow" was more than a sequential breakdown of processing. The common conceptual models of modern operations research, including flow shops, job shops and queuing systems [Pinedo, 2001] can be found in evolved forms in early 20th century industry.

Information based workflows began to grow during this era, although the concept of an "information" flow lacked flexibility. A particularly influential figure was Melvil Dewey (inventor of the eponymous Dewey Decimal System), who was responsible for the development of the hanging file folder. This era is thus identified with the simplest notions of workflow optimization: throughput and resource utilization.

The cultural impact of workflow optimization during this era can be understood through films such as Chaplin's classic "Modern Times." These concepts did not stay confined to the shop floor. One magazine invited housewives to puzzle over the fastest way to toast three slices of bread on a one-side, two-slice grill. The book "Cheaper by the Dozen" introduced the emerging concepts to the context of family life.

Maturation and growth

The invention of the typewriter and the copier helped spread the study of the rational organization of labor from the manufacturing shop floor to the office. Filing systems and other sophisticated systems for managing physical information flows evolved. Two events provided a huge impetus to the development of formalized information workflows. First, the field of optimization theory matured and developed mathematical optimization techniques. Second, World War II and the Apollo program were unprecedented in their demands for the rational organization of work.

The classic management tome "The Organization Man" culturally captured the nature of work in this era.

Quality era

During the 1980s two aspects of workflow organization drew heavy criticism. First, the methods pioneered by Taylor modeled humans as simple automatons. The classical industrial-style organization of work was critiqued as being both dehumanizing and suboptimal in its use of the potential of human beings. Maslow's hierarchy of needs, which describes human needs for self-actualization and creative engagement in work, became a popular tool in this critique. This issue was acknowledged, but did not gain much traction otherwise.

The second critique had to do with quality. Workflows optimized for a particular time became inflexible as work conditions changed. Quality, in both analytic and synthetic manifestations, transformed the nature of work through a variety of movements, ranging from total quality management to Six Sigma to more qualitative notions of business process reengineering (Hammers and Champy, 1991). Under the influence of the quality movement, workflows became the subject of much scrutiny and optimization efforts. Acknowledgement of the dynamic and changing nature of the demands on workflows came in the form of recognition of the phenomena associated with critical paths and moving bottlenecks. [Goldratt, E., 1996]

The experiences with the quality movement made it clear that information flows are fundamentally different from the mass and energy flows which inspired the first forms of rational workflows. The low cost and adaptability of information flows were seen as enabling workflows that were at once highly rational in their organization and highly flexible, adaptable and responsive. These insights unleashed a whole range of information technology at workflows in manufacturing, services and pure information work. Flexible manufacturing systems, just-in-time inventory management, and other highly agile and adaptable systems of workflow are products of this era.

Virtual workflow era

The Internet bust of the early years of the 21st century led to a period of caution towards ambitious conceptualizations of smart workflows. Today, a variety of actors in the economy are addressing more comprehensive models of work that are rational, flexible, take full advantage of globalized distributed work, and allow humans to use their full creative potential. An interesting development in this area is the rise of the apparently anarchic organizations that have evolved in the open source software community.

Examples

The following examples illustrate the variety of workflows seen in various contexts:

# In military planning, a "concept of operations" is a workflow that defines particular mission types
# In machine shops, particularly job shops and flow shops, the flow of a part through the various processing stations is a work flow
# Insurance claims processing is an example of an information-intensive, document-driven workflow
# Wikipedia editing is an example of a stochastic workflow
# The Getting Things Done system is a model of personal workflow management for information workers

Features and phenomenology

# Modeling: Workflow problems can be modeled and analyzed using graph-based formalisms like Petri nets.
# Measurement: Many of the concepts used to measure scheduling systems in operations research are useful for measuring general workflows. These include throughput, processing time, and other regular metrics.
# Specialized connotations: The term "workflow" has specialized connotations in information technology, document management and imaging. Since 1993, one trade consortium specifically focused on workflow management and the interoperability of workflow management systems has been the Workflow Management Coalition.
# Scientific workflows: Found wide acceptance in the fields of bioinformatics and cheminformatics in the early 2000s, where they successfully met the need for multiple interconnected tools, handling of multiple data formats and large data quantities. Also, the paradigm of scientific workflows was close to the well-established tradition of Perl scripting in life-science research organizations, so this adoption represented a natural step forward towards a more structured infrastructure setup.
# Human-machine interaction: Several conceptualizations of mixed-initiative workflows have been studied, particularly in the military, where automated agents play roles just as humans do. For innovative, adaptive, collaborative human work the techniques of human interaction management are required.

Workflow improvement theories

The key driver to gain benefit from the understanding of the workflow process in a business context is that the throughput of the workstream path is modelled in such a way as to evaluate the efficiency of the flow route through internal silos with a view to increasing discrete control of uniquely identified business attributes and rules and reducing potential low efficiency drivers. Evaluation of resources, both physical and human is essential to evaluate hand-off points and potential to create smoother transitions between tasks. Several workflow improvement theories have been proposed and implemented in the modern workplace. These include:

# Six Sigma
# Total Quality Management
# Business process reengineering
# Lean systems

As a way of bridging the gap between the two, significant effort is being put into defining "workflow patterns" that can be used to compare and contrast different workflow engines across both of these domains.

Workflow components

A workflow can usually be described using formal or informal flow diagramming techniques, showing directed flows between processing steps. Single processing steps or components of a workflow can basically be defined by three parameters:
#input description: the information, material and energy required to complete the step
#transformation rules, algorithms, which may be carried out by associated human roles or machines, or a combination
#output description: the information, material and energy produced by the step and provided as input to downstream steps.

Components can only be plugged together if the output of one previous (set of) component(s) is equal to the mandatory input requirements of the following component. Thus, the essential description of a component actually comprises only in- and output that are described fully in terms of data types and their meaning (semantics). The algorithms' or rules' description need only be included when there are several alternative ways to transform one type of input into one type of output – possibly with different accuracy, speed, etc.

When the components are non-local services that are invoked remotely via a computer network, such as Web services, additional descriptors (such as QoS and availability) also must be considered.

Workflow applications

Many software systems exist to support workflows in particular domains. Such systems manage tasks such as automatic routing, partially automated processing and integration between different functional software applications and hardware systems that contribute to the value-addition process underlying the workflow.

ee also

*Bioinformatics workflow management systems
*Business process automation
*Business process management
*Business process modeling
*Business-driven development
*Computer-supported collaboration
*Enterprise content management
*Process architecture
*Process-driven application
*Smart contracts

References

Further reading

*Layna Fischer (ed.): 2007 BPM and Workflow Handbook, Future Strategies Inc., ISBN-13: 978-0-9777527-1-3
*Layna Fischer: "Workflow Handbook 2005", Future Strategies, ISBN 0-9703509-8-8
*Layna Fischer: "Excellence in Practice, Volume V: Innovation and Excellence in Workflow and Business Process Management", ISBN 0-9703509-5-3
*Keith Harrison-Broninski. "Human Interactions: The Heart and Soul of Business Process Management". ISBN 0-929652-44-4
*Holly Yu: "Content and Work Flow Management for Library Websites: Case Studies", Information Science Publishing, ISBN 1-59140-534-3
*Wil van der Aalst, Kees van Hee: "Workflow Management: Models, Methods, and Systems", B&T, ISBN 0-262-72046-9
*Marlon Dumas, Wil van der Aalst, Arthur ter Hofstede: "Process-Aware Information Systems", Wiley, ISBN 0-471-66306-9
*Setrag Khoshafian, Marek Buckiewicz: "Introduction to Groupware, Workflow and Workgroup Computing", John Wiley & Sons, ISBN 0-471-02946-7
*Rashid N. Kahn: "Understanding Workflow Automation: A Guide to Enhancing Customer Loyalty", Prentice Hall, ISBN 0-13-061918-3
*Dan C. Marinescu: "Internet-Based Workflow Management: Towards a Semantic Web", John Wiley & Sons, ISBN 0-471-43962-2
*Frank Leymann, Dieter Roller: "Production Workflow: Concepts and Techniques", Prentice Hall, ISBN 0-13-021753-0
* Michael Jackson, Graham Twaddle: "Business Process Implementation: Building Workflow Systems", Addison-Wesley, ISBN 0-201-17768-4
*Alec Sharp, Patrick McDermott: "Workflow Modeling", Artech House Publishers, ISBN 1-58053-021-4
*Toni Hupp: "Designing Work Groups, Jobs, and Work Flow", Pfeiffer & Company, ISBN 0-7879-0063-X
*Gary Poyssick, Steve Hannaford: "Workflow Reengineering", Adobe, ISBN 1-56830-265-7
*Dave Chaffey: "Groupware, Workflow and Intranets: Reengineering the Enterprise with Collaborative Software", Digital Press, ISBN 1-55558-184-6
*Wolfgang Gruber: "Modeling and Transformation of Workflows With Temporal Constraints", IOS Press, ISBN 1-58603-416-2
*Andrzej Cichocki, Marek Rusinkiewicz, Darrell Woelk: "Workflow and Process Automation Concepts and Technology", Kluwer Academic Publishers, ISBN 0-7923-8099-1
*Alan R. Simon, William Marion: "Workgroup Computing: Workflow, Groupware, and Messaging", McGraw-Hill, ISBN 0-07-057628-9
*Penny Ann Dolin: "Exploring Digital Workflow", Delmar Thomson Learning, ISBN 1-4018-9654-5
*Gary Poyssick: "Managing Digital Workflow", Prentice Hall, ISBN 0-13-010911-8
*Frank J. Romano: "PDF Printing & Workflow", Prentice Hall, ISBN 0-13-020837-X
*James G. Kobielus: "Workflow Strategies", Hungry Minds, ISBN 0-7645-3012-7
*Alan Rickayzen, Jocelyn Dart, Carsten Brennecke: "Practical Workflow for SAP", Galileo, ISBN 1-59229-006-X
*Alan Pelz-Sharpe, Angela Ashenden: "E-process: Workflow for the E-business", Ovum, ISBN 1-902566-65-3
*Stanislaw Wrycza: "Systems Development Methods for Databases, Enterprise Modeling, and Workflow Management", Kluwer Academic/Plenum Publishers, ISBN 0-306-46299-0
*"Database Support for Workflow Management", Kluwer Academic Publishers, ISBN 0-7923-8414-8
* [http://www.lri.fr/~mbl/cgi-bin/getpdf?Trends-CSCW/chap2.pdf Clarence A. Ellis: "Workflow technology"] , Computer Supported Co-operative Work, M. Beaudouin-Lafon (ed.), John Wiley & Sons, Chichester, UK, 1999, pp. 29-54
*Matthew Searle: "Developing With Oracle Workflow"

External links

* [http://www.workflowpatterns.com/ Workflow patterns]
* [ftp://ftp.informatik.uni-stuttgart.de/pub/library/medoc.ustuttgart_fi/STUD-2052/STUD-2052.pdf Pattern-based analysis of workflows]
*" [http://citeseer.ist.psu.edu/dellen97knowledge.html Knowledge Based Techniques to Increase the Flexibility of Workflow Management] " by Barbara Dellen, Frank Maurer, Gerhard Pews
* [http://www.theserverside.com/articles/article.tss?l=Workflow The State of Workflow] May 2004 article by Tom Baeyens
* [http://www.wi-inf.uni-essen.de/FGFrank/ecomod/index.php?workflow=default&&lang=en Business Process Modelling vs. Workflow Management]
* [ftp://ftp.informatik.uni-stuttgart.de/pub/library/medoc.ustuttgart_fi/DIP-2787/DIP-2787.pdf How to create workflows oriented on business goals]
* [http://www.wfmc.org/ Workflow Management Coalition]
*