Business Process Data Capture via GUI Sensor Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business process monitoring systems require manual modification of source code and programming for adding BAM interceptors, which is cumbersome and inflexible, limiting the ability to dynamically capture and transfer data from specific business process portions to user-defined destinations.
Innovation Solution
A graphical user interface (GUI) is used to select business process portions for data capture and define sensors, which automatically generate metadata for data capture and transfer to user-identified destinations, eliminating the need for manual code modifications and allowing dynamic configuration of sensors and data transfer routes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual modification of source code is used to add BAM interceptors, then data capture capability is achieved, but system complexity and ease of operation deteriorate
Solution Approach 1:
The patent introduces a visual orchestration tool as an intermediary between the user and the business process system. This tool provides a graphical user interface that mediates the complex code modification process, allowing users to configure data capture through drag-and-drop operations without directly modifying source code. The intermediary translates user-friendly visual configurations into the necessary technical implementations.
Solution Approach 2:
The patent replaces the mechanical system of manual code editing and programming with an automated visual configuration system. Instead of requiring users to physically edit source code files and compile programs, the system uses graphical interface elements and automated code generation to achieve the same data capture functionality, significantly reducing operational complexity.
2Adaptability or versatility
If manual code modification is required for BAM interceptor setup, then data capture is enabled, but device complexity and time consumption increase
Solution Approach 1:
The system enables self-service by allowing users to configure monitoring capabilities through an intuitive graphical interface without requiring programming expertise. The visual orchestration tool provides self-documenting configuration options and automated processing, eliminating the need for users to understand complex code structures or compilation processes.
Solution Approach 2:
The patent implements preliminary action by pre-configuring the system with standardized data capture templates and predefined interceptor patterns. These pre-prepared configurations can be directly applied to common business process scenarios, eliminating the need for users to create monitoring solutions from scratch and reducing setup complexity.
3Adaptability or versatility
If programming is required for data transfer configuration, then data transfer functionality is achieved, but ease of operation and productivity worsen
Solution Approach 1:
The patent uses copying by allowing users to replicate and reuse configuration templates across multiple business process scenarios. Once a data transfer configuration is created for one scenario, it can be copied and adapted for similar scenarios, dramatically reducing configuration time and improving productivity while maintaining flexibility.
Solution Approach 2:
The visual orchestration tool provides universal configuration capabilities that work across different data transfer scenarios and destinations. The same graphical interface and configuration methods can be used regardless of the specific business process or target system, making the system versatile without requiring scenario-specific programming.
Data Source
AI summary
A graphical user interface (GUI) displays a flow of activities of a business process, including any portion thereof from which capture of data is permitted. The GUI receives, in an operation, at least an indication of a business process portion from which data is to be captured (“sensor”), an identification of an endpoint to which captured data is to be transferred, and a type of the endpoint which identifies (through a mapping) a predetermined software. A sensor may be added any number of times (through a single GUI or though multiple GUIs) by repeatedly performing the operation. Also, a given sensor may be associated with multiple endpoints. Computer(s) executing the business process check whether or not a sensor is present, on execution of the business process portion, and if present, then execute the corresponding predetermined software(s) to transfer data from the sensor directly to the respective endpoint(s).


