Introduction.
In a world of dynamic and discontinuous change, companies are constantly requested to adapt themselves to new conditions so that they are prepared to survive and flourish in an increasingly competitive environment. In such a dynamic landscape, they must re-examine the ways they treat their knowledge assets and they are identifying new and reorganising existing processes in which they can exploit them more effectively in the future. In this pressure cooker, only organizations with reliable end-to-end processes will be versatile enough to do more with what they have and adaptable enough to change fast. Therefore, efficient management of knowledge intensive processes has attracted increasing attention.
The latest buzzwords of semantic technologies operating on the semantic web qualifies as an enabling technology which can support structured as well as unstructured aspects of the knowledge intensive processes. Hence it aids a number of roles a knowledge worker has to fill in a business process oriented environment:
1)Support for process participants in the standardized but still flexible execution of business processes and
2)Support for process engineers in the definition of such standardized processes based on existing work practice.
The goal of our approach is to resolve the dilemma of flexibility for knowledge workers versus organizational needs for standardization and control by supporting the grass roots development and evolution of workflows.
The Knowledge Worker and the adhoc process.
Knowledge work is work with a large amount of creative activities (as opposed to routine work) which run within or across a set of business processes. Knowledge processes describe distributed, organisational work and the workers rely on knowledge as their critical work resource, searching, analysing, and synthesising information, and in collaborating with others to generate new knowledge.
Knowledge Workers are primarily controlled by goals instead of tasks, and they have significant freedom in structuring their activities themselves (such as timing and procedures). This freedom calls for new types of processes, processes which resolve the dilemma of flexibility for knowledge workers versus organizational needs for standardization.
We refer to such processes as ad hoc processes, which consist of defined inputs and outputs, but leave the way to accomplish the defined outputs up to the knowledge workers and their specific context. They also allow for the agile but uniform handling of structured and unstructured process parts.
Disparate Views- The organisation and the individual process perspective.
The organisational perspective revolves around work flow management systems which boosts productivity by increasing the degree of standardisation and transparency, enabling traceability of past process executions, allowing effective controlling and monitoring mechanisms, and permitting easier synchronization and coordination of networked and interdependent activities. The emphasis is on execution down to the smallest detail.
The way BPM has evolved has been primarily focused on improving the productivity of the blue-collar worker who were expected to follow what has been modelled by the business owners, and expected to accomplish their tasks from task lists in the order mentioned, and in a measured manner.
The individual perspective on the other hand is represented by the field of Computer Supported Cooperative Work (CSCW- first coined by Irene Greif and Paul M. Cashman in 1984.) which supports knowledge workers in coordinating and negotiating work tasks, in the exchange of information within a specific work context, and collaboratively coming up with solutions to common problems.
This approach is mainly unstructured with respect to processes and focuses on information exchange and collaborative sense making. Consequently CSCW approaches are characterized by lacking process transparency, traceability, standardization and control. Both technical approaches, workflow management and CSCW, can be improved to allow the efficient definition of ad hoc processes, their automatic analysis and mapping to standard processes, and the automatic adaptation of workflows.
According to a number of experts in the field, over the last decade there has been a shift from “data-aware” information systems to “process-aware” information systems (PAIS) such as Workflow Management Systems (WfMS). Although it is appreciated that PAIS have made a significant contribution to increase the productivity of employees, there is also a widely regarded view that their rigidity restricts their applicability .
Ad-hoc processes require the process engine to give up (a little bit of) control. The engine no longer describes the entire business logic as one interconnected flow chart, but rather relies on the input of end users (i.e. the expert or knowledge worker), rules (for inspecting data related to the case) or external events.
Tools that merge unstructured and structured concepts.
There are various tools which permits the description of semi-structured processes like this, using an ad-hoc sub-process.
Drools Flow for example allows end users to specify, execute and monitor (a part of) their business logic using these processes. Also IBM introduced “Dynamic Human Workflows” in its WebSphere Process Server, which allows run-time users to rearrange some details of the flow during its execution so that it evolves differently than the way it was defined at design time effectively giving it case handling capabilities.
Finally here, another aid is called The Decorator which is essence is an object oriented structural pattern, invented by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. The Decorator is a pattern that can add additional responsibilities to a process in a dynamic way. Decorators provide an agile way for extending functionality. This blanket term for this area is called Adaptive Case Management (ACM).
The unique feature of combining business processes with business rules and event processing allow for the versatility at runtime. For example end users can flag what tasks to execute, rules and processes can trigger certain tasks and work collaboratively since rules can be associated with the ad-hoc sub-process to automatically trigger certain tasks when the sub-process is activated, or conditionally based on the available data.
For example the unique features of combining business processes with business rules and event processing, could be very useful in more data-based processes, like for example claim management. In this case, the tasks that need to be executed are largely dependent on the available case data. It might be more intuitive to model this as a number of independent process fragments (one for example to request additional information from the owner, one to delegate the claim to another person, etc.). Here, rules could again be really helpful to automatically derive the current state whenever the claim is updated.
The Blended Process – Adaptive Process Discovery.
Presently, it’s difficult to separate ACM from BPM, because most processes blend together elements of both unstructured and structured processes. Maybe one of the best ways of accommodating all value added aspects of the process is to define the start and end points and figure out the bit in the middle through adaptive process discovery.
Every time there is an instance of the process kicked off it’s tracked as it travels across the enterprise and touches the participants, it’s not modelled up front and this is the key part. Once there have been enough instances tracked and discovered there is an element of probabilistic vs. deterministic branching to try to predict on previous behaviour where the work package or item will go next. This iterative process informs the structured aspects of the process while accommodating the dynamic creative unstructured elements.