Hierarchical Business Process Control Across Distributed Cloud Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Business Process Management (BPM) products struggle to control business processes across multiple different applications and systems, especially in cloud environments, and cannot define hierarchical dependencies spanning different systems or track sequential steps effectively.

Innovation Solution

A new methodology that allows for the definition of business processes down to a deeper level, including business sub-processes and their elements, with a service group hierarchy that enables control across different systems, using a central cloud service to manage process execution and data storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If business processes are defined across multiple applications and systems, then process coverage and completeness are improved, but system complexity and difficulty of control increase

Engineering Contradiction:
Improveprocess coverageVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments business processes into hierarchical components including process models, process definitions, process instances, and individual process steps. Each segment can be independently defined, controlled, and monitored within its own application or system, while the hierarchical structure enables coordinated execution across multiple systems. This segmentation reduces overall system complexity by breaking down complex cross-system processes into manageable, standardized units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces process definitions as intermediary artifacts that bridge multiple applications and systems. Process definitions serve as standardized interfaces that abstract the complexity of underlying system interactions, allowing process models to orchestrate operations across disparate systems without requiring direct integration between each system. This intermediary layer enables process coverage across multiple systems while shielding users from the underlying complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If hierarchical definition of business processes is implemented, then process control precision is improved, but setup complexity increases

Engineering Contradiction:
Improveprocess control precisionVSAvoidsetup complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent divides process definitions into hierarchical segments including process models, process definitions, process instances, and process steps. Each hierarchical level serves a specific control function: process models define the overall workflow, process definitions specify system interactions, process instances track execution state, and process steps represent individual actions. This segmentation enables precise control at each level while maintaining simplicity through standardized templates and automatic inheritance of properties from parent levels.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables preliminary definition of process models and process definitions before actual process execution. Process models can be designed and validated in advance, with process definitions pre-configured to specify system interactions and data mappings. This preliminary action allows organizations to establish precise control frameworks before deployment, reducing setup complexity during actual implementation by reusing pre-defined templates and configurations.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If process models are enacted with short turnaround times, then development cost is reduced, but control capability over distributed processes deteriorates

Engineering Contradiction:
Improvedevelopment speedVSAvoidcontrol capability
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent enables preliminary definition and validation of process models using standardized templates and graphical interfaces. Process models can be designed, simulated, and validated before deployment, ensuring control capability is built-in from the start. This preliminary action allows rapid enactment of process models with short turnaround times while maintaining control capability, as the control logic is pre-configured in the process definitions rather than being developed during deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses parameter-based process definitions that can be dynamically configured to adapt to different execution contexts. Process models define control logic in terms of configurable parameters that can be adjusted without changing the underlying process structure. This parameterization enables rapid deployment of process models across different systems and contexts while maintaining consistent control capability through centralized parameter management.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12632811B2Business process definition and control service
Publication Date: 2026.05.19 SAP SE
  • US12632811B2 patent drawing
  • US12632811B2 patent drawing
  • US12632811B2 patent drawing

AI summary

A new methodology for describing business processes and permissible process variants is introduced. Additionally, an allowed system status and involved master data objects with read and change authorization can be defined for process step. If a user wants to run the defined process in a BPM product, the system connection may be made from an authorized central solution manager system (connected to all systems in a landscape) so it is possible to run predefined processes. As soon as a process step shall be executed, a central cloud service can be executed. The central cloud service can access and analyze selected objects. The execution system, which may be a completely different system than the system that defined the business process, can then execute an associated process step, and a process pointer will store the data in involved systems and set a new status.