Workflow
Workflow is defined by the WFMC as: "The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another".
At a basic level our eProcess workflow tool is a series of queues that deliver completed work from one user to another after the item has been processed.
Simple workflow technology that routes tasks from queue to queue has matured into more complex workflow management systems where all or part of the actual business process itself is managed. A workflow engine can:
- Interpret work
- Trigger specific actions
- Notify users
- Interact with external systems
- Manage service levels
Through the application of pre-defined business rules, verification of data and compiling of additional data from external sources, highly complex processes can be controlled and managed. Mitral Systems has developed the eProcess workflow engine and set of workflow tools that can be used to create either simple queue based workflows or more complex process based applications. This set of workflow tools can be utilised in several different scenarios and environments from Purchase Invoice approval through to areas such as mortgage application processing. There are many types of workflow and many areas in your business where our workflow engine and tool set can be used.
Production Workflow
The objective of Production Workflow is to manage large numbers of similar tasks to maximise productivity. Suitable tasks are automated to a point where human intervention is required only to manage work items that fall outside pre-determined process tolerances or rules.
Production Workflow can manage hugely complex processes, and is usually integrated with existing operational systems. Our workflow engine can be embedded into large applications where its role is to act as a Rules Engine.
Autonomous Workflow
An Autonomous Workflow management system is functional without any additional application software. For the deployment of an Autonomous Workflow solution, application systems that are external to the workflow management system are invoked at runtime and workflow relevant data is passed between the workflow participants.
Our workflow toolset has its own user interface and can be configured to access data from other applications. It is normally installed to support our M-store document management application. Autonomous Workflow can be very complex due to the interaction with other applications and data sources.
Embedded Workflow
We can embed our workflow toolset into your existing systems, for instance an Enterprise Resource Planning (ERP) system or payment and settlement systems. The workflow functionality is provided by the surrounding software. The workflow components are used to control the sequence of the application’s functions, to manage queues and to assist with exception processing.
AD-HOC
An ad hoc workflow system allows users to create and amend process definitions very quickly and easily to meet circumstances as they arise, so it is possible to have almost as many process definitions as there are instances of the definitions. Ad-Hoc Workflow maximizes flexibility in areas where throughput and security are not major concerns.
