Information about leading BPMS products
As the generic foundations of the BPMS concept have already been explained, here we would like to present one of the leading BPMS products: e-Work from Metastorm, Inc.
e-Work brings all typical functionality of the BPMS platform. Below you will find its full technical specification.
Metastorm e-Work
Overview
Metastorm e-Work is a Business Process Management Systems (BPMS) platform for automating people-intensive administrative and management processes.
It is a flexible production-strength BPMS system, supporting a very large number of processes, users, and transactions. It can access data from any ODBC data source, make use of external forms, integrate at an API level with a number of document management systems, and exchange mail with most email clients. More importantly it can easily integrate ALL these systems via one simple user interface, then present that interface to the user in the two most popular Windows clients, Internet Explorer and Outlook 2000.
Architecture
The e-Work architecture is as shown. The e-Work engine runs on a Windows NT or 2000 server, and requires either SQL Server or Oracle as underlying database. Typically, one engine can handle around 5 user steps per second (125,000 steps in prime shift); multiple engines can run against one control database for high volume applications. The web server is normally Microsoft IIS; multiple IIS servers are also fully supported.
e-Work forms are true thin forms, so highly suitable for Internet operation. They are created once in the designer and automatically rendered for the client in use.
Components
Server
The workflow server (engine) runs on Windows NT or Windows 2000, makes use of MTS and communicates with clients via either DCOM or TCP/IP. It uses IIS as its web server and supports Microsoft SQL Server, Oracle or Access (only for testing) as its underlying databases via ODBC. It communicates with 3rd party applications via DCOM, BizTalk or databases.
Designer
With all workflow packages a key element is the method you use to design the workflow procedures. e-Work has one of the most fully featured, easy-to-use designers on the market today. You define your procedures by visualising them as a graphical map, then adding the detail behind each stage and action using a wizard.
Process Maps
e-Work uses a state transition diagram to describe the process flow. That means that actions can be directly mapped, rather than being hidden in event condition tables, and action buttons can be automatically generated on e-Work forms. Supported are:
- user and group steps
- system steps
- common steps.
Forms
e-Work forms are created using the designer. Forms are re-usable across steps and processes. Once designed, an e-Work form can be displayed through any client (Outlook, Explorer or GroupWise). You can mix and match clients and the form has only to be built once. For flexibility, external forms can also be used, and intermixed with e-Work forms in one process, and linked directly to the e-Work engine.
e-Work forms provide a very full set of controls including:
- file attachment
- date-time picker
- memo field
- signature
- grid control
Additional controls and validations are available through server-side or client-side scripts.
Clients
e-Work integrates seamlessly with Explorer, Outlook and GroupWise. All clients offer as default a to-do list (Inbox), a ’New Forms’ list (new processes available to the user) and a Watch list (personalised monitoring of system activity and workload). The Watch List allows managers etc to continuously monitor events in their business units and to intervene when necessary in any process, at any time. With the explorer client, anyone with web access can take part in an e-Work process (internet and intranet). The Explorer client presents these within an Outlook folder. Notification of new work can be delivered to the Outlook inbox if required.
Integration Facilities
e-Work can access data from any ODBC data source, make use of external forms, integrate at an API level with a number of document management systems (including I-Manage and DocsFusion), and exchange mail with SMTP or MAPI email clients including Microsoft Exchange. With Release 5.2, e-Work supports XML.
Software Developer’s Kit
This is available for advanced use of e-Work components, for example calling e-Work services from within other applications, and building bespoke clients. Extensive sample code is provided.
Product family
Metastorm e-Work is made up of several modules. For more details please see the Metastorm website.
Required Components
- e-Work server pack
- e-Work user license.
The e-Work server pack is the initial building block for any e-Work system. It includes one license for e-Work designer, e-Work engine, e-Work users and roles, e-Work administrator, and server extensions for IE5.
An e-Work user license is required for any person who wishes to connect to e-Work and participate in e-Work processes. Metastorm supplies extensions to provide client services to an Internet Explorer Version 5 browser, Microsoft Outlook 2000 and Novell GroupWise Version 5.5. The e-Work SDK provides the facilities for developers to provide e-Work client services in other clients. A user license is required no matter what client software is used.
Optional Components
- e-Work designer
- e-Work public web access
- e-Work integration modules
- e-Work software developer’s kit.
The e-Work public web access allows unregistered users to initiate new items in a process without having to sign on to the e-Work system. It is typically used by organizations to allow potential customers to indicate interest in or request further information about a product or service.
The integration modules allow directories to be used as a single point of administration for the maintenance of e-Work users and the roles they hold.
