Configurable Workflow Engine for Ad Hoc Process Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current collaboration technologies are fragmented and lack scalability, failing to provide comprehensive solutions for distributed teams, with existing tools either being too structured and inflexible or too unstructured and difficult to analyze, and often requiring manual intervention for workflow management.

Innovation Solution

A configurable workflow engine that allows end users to define and automate processing steps for work items, enabling a smooth transition from unstructured to semi-structured or fully structured workflows, with features like automatic carry-over of incomplete tasks and user-defined local processes, integrated with a data storage system for structured and local work items.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If structured workflow systems are used, then trackability and process control are improved, but flexibility and adaptability to ad hoc processes deteriorate

Engineering Contradiction:
ImprovetrackabilityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The workflow system allows dynamic modification of process definitions during execution. Users can add, remove, or modify workflow steps while processes are running, enabling the system to adapt to changing requirements without losing trackability. The workflow engine maintains structured control while accommodating flexible changes through its dynamic process management capabilities.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The workflow is divided into manageable steps or tasks that can be independently defined, executed, and monitored. This segmentation allows the system to maintain structured trackability at each step while allowing flexible reconfiguration of individual steps without affecting the entire process structure.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If unstructured workflow methods are used, then flexibility and ease of operation are improved, but trackability and analysis capability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidtrackability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Users can define their own workflow processes without requiring extensive administrative intervention. The system provides tools for users to create, modify, and manage their own workflows, making the system easy to operate while maintaining structured trackability through automated workflow engine control.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If general purpose collaboration tools are used, then versatility is improved, but device complexity and configuration requirements deteriorate

Engineering Contradiction:
ImproveversatilityVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system allows configuration of workflow parameters such as task assignments, deadlines, and process steps without requiring complex system reconfiguration. Users can modify workflow behavior by changing parameters like who performs which task or when tasks are due, maintaining versatility while reducing configuration complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7885847B2End user oriented workflow approach including structured processing of ad hoc workflows with a collaborative process engine
Publication Date: 2011.02.08 SAP SE
  • US7885847B2 patent drawing
  • US7885847B2 patent drawing
  • US7885847B2 patent drawing

AI summary

In a structured workflow system, a configurable workflow engine provides mechanisms for executing and scheduling the work items in a defined way. End users use their discretion and define their own “local” processes and “local” rules for processing work items, or deviate from predefined processes. The configurable workflow engine might be installed at a server to organize workflows and business processes where end users can define processing steps for incoming work items by setting up rules and defining workflows as part of a local workflow structure. By defining these rules and workflows, the further processing steps of future incoming work items can be automated. When an administrator directs the workflow engine to move from a current phase to a next phase, the workflow engine deals with the incomplete items by allowing the administrator to carry over work items (or might do it automatically). End-user consultation might be included in the carry-over decisions. The carried over work items are added as parallel activities to the next phase. The workflow engine handles imposing and executing control flow dependencies between tasks, thus providing a smooth transition from totally unstructured work to semi-structured or completely structured work. When the workflow engine encounters semantically correlated work items/tasks, the process engine assumes that these work items/tasks belong to the same process instance.