Hybrid BPM Bridge for Process-Event Runtime Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing business process management (BPM) systems struggle to seamlessly integrate process-oriented and event-based methods within a service-oriented architecture (SOA), limiting their ability to adapt to different business processes and optimize efficiency.

Innovation Solution

A system and method that supports collaborative working of process-oriented and event-based BPM methods by employing a bridge to integrate process-oriented and event-based runtime modules, allowing for the transformation of business models into hybrid execution models at runtime, enabling end-to-end BPM implementation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a process-oriented method is adopted for BPM, then the business process is intuitive and easy to model, but it is not conducive to modification and limited to information access

Engineering Contradiction:
Improveease to modelVSAvoidmodification capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the business process model into process-oriented parts (for intuitive modeling) and event-based parts (for flexibility and modification). This allows different sections of the same business process to utilize different execution models based on their specific requirements, resolving the contradiction between ease of modeling and modification capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges process-oriented execution models and event-based execution models into a unified hybrid framework. This combination allows the system to leverage the intuitive nature of process-oriented approaches while simultaneously incorporating the flexibility and adaptability of event-based approaches, thus resolving the technical contradiction.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If an event-based method is adopted for BPM, then the system is loosely-coupled and easy to modify, but it is not intuitive enough and complicated to model

Engineering Contradiction:
Improveease to modifyVSAvoidease to model
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the business process model into process-oriented parts (for intuitive modeling) and event-based parts (for flexibility and modification). This allows different sections of the same business process to utilize different execution models based on their specific requirements, resolving the contradiction between ease of modeling and modification capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal execution framework that can handle both process-oriented and event-based execution models. This multi-functional system provides a unified interface for modeling while supporting diverse execution styles, making the system both intuitive to model and easy to modify.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If BPM systems integrate multiple execution models, then the system can adapt to different business processes, but the system complexity increases

Engineering Contradiction:
Improveadaptability to different business processesVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a process model transformer as an intermediary component that automatically transforms process models into appropriate execution models (process-oriented or event-based). This mediator handles the complexity of model transformation internally, allowing the system to support multiple execution models without exposing the complexity to users, thus resolving the contradiction between adaptability and system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If process models are transformed into different execution models, then the system can optimize performance, but the transformation process adds complexity

Engineering Contradiction:
Improveexecution efficiencyVSAvoidtransformation process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a process model transformer as an intermediary component that automatically transforms process models into appropriate execution models (process-oriented or event-based). This mediator handles the complexity of model transformation internally, allowing the system to support multiple execution models without exposing the complexity to users, thus resolving the contradiction between adaptability and system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The process model transformer operates autonomously to transform process models into optimized execution models based on predefined criteria and rules. This self-service mechanism eliminates the need for manual transformation processes, reducing operational complexity while maintaining high execution efficiency through automatic optimization.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10726361B2Collaborative working of business process management methods
Publication Date: 2020.07.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10726361B2 patent drawing
  • US10726361B2 patent drawing
  • US10726361B2 patent drawing

AI summary

The collaborative working of process-oriented and event-based business process management (BPM) methods in a service-oriented architecture (SOA) is supported. The execution models of the business process include process-oriented execution models and event-based execution models. The process-oriented execution models and the event-based execution models are executed at runtime. A bridge implements the interaction between the process-oriented runtime execution and the event-based runtime execution.