TC00-1003 Issue 1.1 Workflow Reference Model Printed 19/11/98
Copyright 1993, 1994, 1995 Workflow Management Coalition Page 11 of 11
however, they do not typically exhibit a separation between the business procedure logic and the invocation of
the various application tools which may be required to support individual activities within the business process.
Over time, this is leading to a requirement to consolidate workflow capabilities to control the business
procedures with the ability to invoke traditional transaction application programs for appropriate parts of the
business process, as well as other types of application (document or office based, etc..) for other parts of the
business process.
2.2 5 Project Support Software
Software to handle complex IT application project development (eg IPSEs - "Integrated Project Support
Environments") has often provided a form of workflow functionality within the project environment, for
"transferring" development tasks between individuals and routing information between individuals to support
these tasks. In some cases this type of software has been generalised to support a wider, business-oriented view
of process and a wider range of application tools - offering a more general workflow capability.
2.2.6 BPR and Structured System Design Tools
Business Process Re-engineering tools have provided IT based support for the activities of analysing, modelling
and (re-)defining the core business processes of an organisation and the potential effects of change in such
processes or organisational roles and responsibilities associated with such processes. This may include analysis
of the process structure and information flows supporting it, the roles of individuals or organisational units
within the process and actions taken in response to different events, etc. A natural extension of such tools is to
facilitate the implementation of the process with IT support infrastructure to control the flows of work and
associated activities within the business process.
2.2.7 Separation of workflow functionality
The market for workflow has evolved from requirements across a spectrum of the IT industry and is likely to
continue to do so, with a wide range of products focussed on one or more particular aspects of the overall
workflow requirement. Some may be provided in conjunction with other areas of technology, such as image
processing or document management, others may be more general purpose. This multiplicity of products will
allow wide choice for individual implementation circumstances and is recognised as something to be
encouraged. However, it also increases the need for standards within the industry to enable different products to
work together and integrate within a consistent overall architecture.
The reference architecture described in this document provides a framework which separates the various
functions within a workflow environment and identifies various interface points at which product integration
and interworking may be accomplished. It forms the template within which the individual interfaces and
interchange specifications are being developed by the Coalition..
2.3. Product Implementation Model
Overview
Despite the variety in workflow products in the market, it has proved feasible to construct a general
implementation model of a workflow system which can be matched to most products in the marketplace thereby
providing a common basis for developing interoperability scenarios.