Workflow Management System for User Action Accountability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing workflow management systems lack assurance and accountability regarding user performance, as users often skip steps deemed redundant, and subsequent reviews fail to indicate skipped steps or responsible users.

Innovation Solution

A workflow management system that includes a data repository for storing workflow plans, an event engine for monitoring and selecting workflows, a plan engine for executing plans, and a portal engine for communicating with users through a user interface, ensuring that pending user actions are tracked and completed, and providing accountability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users are provided with workflow steps without monitoring mechanisms, then ease of operation is improved, but reliability deteriorates due to inability to ensure step completion

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

Solution Approach 1:

The system implements feedback mechanisms where the workflow management system monitors and receives completion status from users. The portal engine receives completed user actions from external user interfaces and communicates with the plan engine to update workflow status, ensuring reliable tracking of step completion while maintaining ease of use.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Users interact with the system through self-service interfaces where they can view pending actions, mark actions as complete, and receive notifications. The system automatically tracks completion and updates workflow state without requiring manual review or intervention, maintaining ease of operation while ensuring reliability.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If users are not required to confirm completion of steps, then ease of operation is improved, but loss of information increases due to inability to track skipped steps

Engineering Contradiction:
Improveease of operationVSAvoidloss of information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system provides feedback to users about pending actions and completion status. The portal engine communicates with users through external interfaces, providing notifications and status updates that inform users of their completion obligations while automatically tracking whether steps are completed, skipped, or blocked.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary tracking mechanism where the plan engine and portal engine serve as mediators between workflow execution and user actions. These intermediaries automatically record completion status, track skipped steps, and maintain information about who performed actions and when, without requiring direct user confirmation for each detail.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If manual tracking of user actions is not implemented, then device complexity is reduced, but loss of information increases due to lack of accountability

Engineering Contradiction:
Improvedevice complexityVSAvoidloss of information
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The workflow management system performs self-tracking of user actions through automated mechanisms. The plan engine automatically adds pending user actions to the database and removes them upon completion, while the portal engine automatically receives and processes completed actions from user interfaces, eliminating the need for manual tracking and reducing complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual tracking mechanisms with automated electronic processing. The database automatically stores and manages pending actions, the portal engine automatically communicates with users and tracks completion status, and the plan engine automatically updates workflow state, substituting manual administrative tasks with automated system processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Productivity

If workflow steps are not monitored for completion, then productivity is improved by reducing monitoring overhead, but reliability deteriorates due to inability to ensure execution

Engineering Contradiction:
ImproveproductivityVSAvoidreliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements efficient feedback loops where users receive notifications about pending actions and can complete them through simple interface interactions. The portal engine automatically receives completion signals from users and communicates with the plan engine to update workflow state, providing reliable completion tracking without requiring extensive monitoring overhead.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The workflow management system continuously tracks the state of pending actions and maintains workflow execution without interruption. The plan engine continuously monitors the pending user actions database and automatically updates workflow status upon completion, ensuring continuous progress and reliable execution while minimizing monitoring overhead through efficient database operations.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8880591B2Workflow management in distributed systems
Publication Date: 2014.11.04 SYMPHONYAI IND DIGITAL MFG INC
  • US8880591B2 patent drawing
  • US8880591B2 patent drawing
  • US8880591B2 patent drawing

AI summary

The workflow management system provides automatic management and execution of workflows that include both automated and user-driven actions. The system monitors connected external systems and/or users for the occurrence of events, which trigger the execution of one or more workflow plans. Each workflow plans consists of a plurality of actions and user actions to be performed in a sequential manner. Actions are executed automatically by the system, but user actions are executed asynchronously due to the inclusion of users in the workflow plan. The system handles the asynchronous nature of user actions by maintaining a pending user action database that users can access to view pending user actions, complete user actions, and reserve user actions for subsequent completion.