Connecting People with Information

k-Flow is a solution that delivers sophisticated workflow functionality as a multi-threaded application and can be deployed across many different server and presentation platforms. The k-Flow architecture is designed using Java and XML and supports TCP/IP-based networks. 

k-Flow caters for business process design and re-use of process sub-flows in order to reduce deployment times of new or changing business processes.  Further, there may be issues that require actions such as collaboration or management approval that may reside outside a formalised business process.  In these cases, k-Flow offers the AHR module that enables users to forward work packages to co-workers and/or management. 

Creation of process definitions are simple as k-Flow supports serial and parallel processing of work, including timeouts (utilising a full business calendar), event handling, escalation and process hierarchies functions and integrates with email.  Essentially, it is software that provides complete application integration and puts technology back into the hands of the stakeholders.  It is simple enough that the business processes can be designed and maintained by the people that will use the system. 

The system provides enterprise application integration capability and fully integrates to Hummingbird products, ODMA-compliant applications and other third-party applications that present an application programming interface (API).

How Does it Work?

k-Flow’s ‘Process Designer’ component is user friendly and has an intuitive graphical interface which allows users with no or limited technical coding experience to design and build process definitions. Further, k-Flow's design component provides a graphical presentation along with the use of ‘drag and drop’ functionality, re-use of processes and ‘package definitions’ and intuitive point-and-click ‘wizards’.

The user has the ability to create activities (or task objects) dragging and dropping from a graphical menu to the actual design map. The benefit is that a Business Systems Administrator can quickly construct a process design map with immediate visual feedback. The map is intelligently coded as it is constructed yet is transparent to the design person.

Where decisions are required at an activity (or step), in-built wizards are provided to step a Business Systems Administrator through scenarios to ensure accurate and logical decisions are completed and routed accordingly. This advanced functionality minimises errors that could occur by manual intervention.

Each model consists of a process definition made up of a number of activities joined together by connectors. This forms a network of activities that can be navigated by the workflow server in response to external stimuli either from a workflow client (presentation layer), a timed response or an external system.

Key Functionality

	Dynamic Activity Linking (DAL) – DAL provides continuity between activities whereby the activity relationships and flows are preserved when activities and connectors are graphically repositioned for visual presentation.
	Process re-use – library of processes with version control.
	Package Definition & Re-use – a package definitions is a “virtual folder” that defines how information and data will be collected in a workflow. Once these packages are defined they can be re-used in many subsequent processes.
	Process Annotations – instant recognition and description of processes as a whole, decision, activities, etc.
	Task Lists – a step-by-step descriptive instruction set for operator to use in order to complete tasks without any process training. As an example, temporary staff can be placed in a workflow role and be able to complete activities with minimal or no training.
	Process Help – enables an organisation to plug-in “active quality” whereby operators are able to dynamically interrogate help or supporting files direct from a url within the process. This provides an organisation to continually update quality procedures independently of the process design.
	Event Handler Library – a library of decision-making objects are provided and additional handlers may be created and added/shared to the library. Robustness & Continuity – There is no need to take the workflow server down for backup or to put a new workflow process into and out of production.
	Failover – The workflow server software provides for hot failover, where is 2 or more workflow servers are implemented, and one fails, another workflow server automatically reconnects the clients with no loss of data.

	k-Flow Server - Production Workflow server
	k-Flow AHR - Ad Hoc Routing module
	k-Flow DC - Document Capture module
	X-Forms - XML form builder module
	Administration Client - Management tool for workflow administrator
	Design & Development Client - Management tool for workflow designer

Suggested Specifications:

	Operating System - Windows 2000 Advanced Server SP1, Windows 2000 Server SP1, Windows NT Server 4.0 with service pack 6a, UNIX, Linux with compatible Java VM.
	Processor - Dual Pentium III 900 Mhz
	Memory - 1 GB
	Disk Space - 18 GB available disk space, RAID Array (depends on volumes)