Configurable Process Component Model for Volatile Business Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current business process management systems are inefficient for automating and managing management processes, which are volatile and require frequent changes, as existing technologies are costly and time-consuming, especially when it comes to documenting and automating management processes using traditional programming languages or special purpose Business Process Management software.

Innovation Solution

A process management system comprising a process model with predefined configurable process components, a process engine for configuring and generating user interface contents, and a user interface for presenting and conducting management processes, allowing for rapid reconfiguration and extension of management processes without modifying source code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional programming languages or special purpose Business Process Management software are used to automate management processes, then automation capability is improved, but implementation time and cost increase significantly

Engineering Contradiction:
Improveautomation capabilityVSAvoidimplementation time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The system segments business processes into discrete, configurable process components that can be independently selected and assembled. This allows rapid construction of automated processes by combining predefined components rather than programming from scratch, significantly reducing implementation time while maintaining automation capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by providing a library of pre-defined process components that have already been designed and validated. These components can be directly applied to management processes without requiring custom development, thereby reducing implementation time and cost while preserving automation functionality.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If traditional programming languages or special purpose Business Process Management software are used to automate management processes, then automation capability is improved, but cost increases

Engineering Contradiction:
Improveautomation capabilityVSAvoidcost
Core Design Contradiction:
Extent of automationVSQuantity of substance

Solution Approach 1:

By segmenting processes into reusable components, the system eliminates redundant development work. The same components can be applied across multiple processes, reducing overall implementation cost while maintaining full automation capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system enables copying of proven process components from one management process to another. This reuse of validated components reduces development cost and risk while maintaining automation effectiveness.

Inventive Principle:
Principle #26Copying

3Speed

If management processes are automated using existing systems, then processing speed is improved, but adaptability to changes deteriorates

Engineering Contradiction:
Improveprocessing speedVSAvoidadaptability to changes
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The system implements dynamics by making process configurations changeable without requiring code modification. Management processes can be dynamically adjusted by reconfiguring components through a user interface, allowing the system to adapt to changing business requirements while maintaining automated processing speed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary action by providing pre-configurable components that can be easily adjusted. This preliminary structure enables rapid adaptation to changes while preserving the benefits of automation, as components can be reconfigured without rebuilding the entire process.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If management processes are documented and automated using current technology, then process formalization is improved, but ease of modification deteriorates

Engineering Contradiction:
Improveprocess formalizationVSAvoidease of modification
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system combines formalization with ease of modification by using a configurable component model. Processes are formally defined through structured component configurations rather than informal documentation, yet these same configurations can be easily modified through a user-friendly interface without requiring technical expertise.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary action by providing pre-defined process components with formal structures. These components come with built-in validation and documentation, ensuring process formalization while allowing easy modification through configuration rather than code changes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7904302B2Method and system for business process management
Publication Date: 2011.03.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7904302B2 patent drawing
  • US7904302B2 patent drawing
  • US7904302B2 patent drawing

AI summary

A process management system comprises a process model, a process engine and a process user interface. The process model stores predefined configurable process metadata components of one or more business management processes. The process engine configures the process metadata components. The process engine also generates user interface contents for a specific management process based on a set of the process metadata components relevant to the specific management process. The process user interface presents the user interface contents for configuration of the process metadata components, and for conducting the specific management process using the generated user interface contents.