Responsive Process Management Platform Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing business infrastructure software components, such as business visibility, event processing, and process management systems, lack effective mechanisms for integrated communication and interaction, relying on complex and custom 'glue' code, which hinders real-time monitoring and management of business processes across disparate systems.

Innovation Solution

A responsive process management platform that integrates business visibility, event processing, and process management systems using standardized messages, enabling real-time monitoring and collaboration across internal and external systems, with features like common user interfaces, data analysis, and alert mechanisms to manage exception conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate business infrastructure components (visibility, event processing, process management systems) are integrated using custom glue code, then communication between components is achieved, but system complexity and difficulty of revision increase

Engineering Contradiction:

Improvecommunication capabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces standardized event schemas and message formats as intermediaries between business infrastructure components. These standards act as mediators that enable communication without requiring custom glue code, thereby reducing system complexity while maintaining reliability of inter-component communication

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates universal event schemas that can be used across multiple business components and systems. These standardized schemas serve multiple purposes: event notification, data exchange, and process coordination, eliminating the need for component-specific communication protocols and reducing overall system complexity

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate business infrastructure components are used, then existing legacy systems can be maintained, but real-time monitoring and collaboration capabilities are lost

Engineering Contradiction:

Improvelegacy system compatibilityVSAvoidreal-time visibility

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments the integration solution into independent layers: standardized event schemas for data representation, event notification mechanisms for real-time communication, and process management components for coordination. This segmentation allows legacy systems to remain unchanged while adding real-time monitoring capabilities through the standardized event layer

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The standardized event schemas and notification mechanisms serve as intermediaries that bridge legacy systems and modern process management capabilities. These intermediaries enable real-time event capture and propagation without requiring changes to legacy systems, thus preserving legacy compatibility while eliminating information loss

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If custom glue code is used to integrate business components, then communication is established, but ease of operation and maintenance deteriorate

Engineering Contradiction:

Improveintegration functionalityVSAvoidease of revision

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent changes the fundamental parameters of integration from custom-coded connections to standardized message-based communication. By adopting universal event schemas and standardized protocols, the system transforms integration from a complex programming task into a configuration-based process, dramatically improving ease of operation and maintenance

Inventive Principle:

Principle #35Parameter changes

4Adaptability or versatility

If business processes execute in external systems, then system flexibility is maintained, but monitoring and management capabilities are reduced

Engineering Contradiction:

Improveprocess execution flexibilityVSAvoidprocess visibility

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements preliminary action by establishing standardized event notification mechanisms before processes execute in external systems. Event schemas are predefined and registered in advance, enabling automatic capture and propagation of process events as they occur, thus maintaining full visibility without restricting execution flexibility

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10528906B2System and method for responsive process management driven by business visibility and complex event processing

Publication Date: 2020.01.07 PROGRESS SOFTWARE CORP

AI summary

A business process management (BPM) system, a business event processing system, and a business visibility system are integrated into a responsive process management platform using standardized messages to permit communication and collaboration among the systems. The BPM system has the capability to model and execute at least one monitoring process including at least one monitoring workstep. This monitoring process makes visible in the BPM system processes of interest that are executing in external systems. The business event processing system and/or the business visibility system have tools to allow users to easily configure those systems to sense events and send appropriate standardized messages to the other systems, can extract and send data to the BPM system, and can send alerts to the BPM system.