Distributed Business Process Integration Model

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed business processes lack a standardized integration model for configuring, integrating, and monitoring message exchange between loosely coupled or heterogeneous business applications, making it difficult to adapt to dynamic changes and optimize resource efficiency.

Innovation Solution

A system with a delivery model and a configuration model using aggregated and expanded multigraphs to define business processes at design time and runtime, respectively, along with transformation modules to automate integration configuration and monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If workflow-based applications are used to execute specific business processes, then business process execution capability is improved, but flexibility to adapt to dynamic changes deteriorates

Engineering Contradiction:
Improvebusiness process execution capabilityVSAvoidflexibility to adapt to changes
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The business process is segmented into modular workflow components that can be independently configured and executed. The integration model separates the delivery model (design-time) from the configuration model (runtime), allowing process definitions to be divided into reusable segments that can be adapted without redefining entire processes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic adaptability through the configuration model that allows runtime modification of business process parameters. The transformation module enables dynamic conversion between delivery and configuration models, permitting processes to adapt to changing business conditions while maintaining structured execution.

Inventive Principle:
Principle #15Dynamics

2Manufacturing precision

If business processes are defined according to a process definition in a workflow builder tool, then process execution standardization is improved, but configurability to company-specific needs deteriorates

Engineering Contradiction:
Improveprocess execution standardizationVSAvoidconfigurability to company-specific needs
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The integration model applies local quality by allowing different levels of standardization and customization at different points in the process. The delivery model provides standardized process definitions while the configuration model enables company-specific adaptations, allowing each organization to configure standard processes to their local needs.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system enables configurability through parameter changes in the configuration model. Company-specific needs are addressed by modifying process parameters, variables, and configuration settings without changing the core process definition, allowing standardization to be maintained while adapting to specific organizational requirements.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If distributed business processes are implemented across heterogeneous systems, then system integration capability is improved, but monitoring and configuration complexity deteriorates

Engineering Contradiction:
Improvesystem integration capabilityVSAvoidmonitoring and configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The integration model provides universality by creating a standardized framework that works across heterogeneous systems. The delivery and configuration models serve multiple functions: defining processes, configuring implementations, and enabling monitoring. This universal model simplifies integration across different systems while maintaining the ability to monitor and configure complex distributed processes.

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

Solution Approach 2:

The transformation module acts as an intermediary between the delivery model and configuration model. It mediates the complexity by automatically transforming standardized process definitions into system-specific configurations, reducing the burden of manual configuration and monitoring across heterogeneous distributed systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Speed

If the time required for execution of business processes is minimized, then execution speed is improved, but resource efficiency deteriorates

Engineering Contradiction:
Improveexecution speedVSAvoidresource efficiency
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The configuration model enables partial execution and selective activation of process components. Instead of always executing complete business processes, the system can activate only necessary portions based on runtime conditions, reducing both execution time and resource consumption by avoiding unnecessary process steps.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7383267B2Standardized integration model for distributed business processes
Publication Date: 2008.06.03 SAP SE
  • US7383267B2 patent drawing
  • US7383267B2 patent drawing
  • US7383267B2 patent drawing

AI summary

A system and method for integrating distributed business processes that govern message exchange between loosely coupled business applications. The system and method includes the use of an integration scenario. The integration scenario includes a delivery integration model that defines one or more design time business processes. The integration scenario further includes a configuration integration model that defines a runtime configuration of the one or more design time business process. Transformation modules are provided to transform the integration scenario from the delivery integration model to the configuration integration model, and vice versa.