Workflow Activity Instance Management via Co-Process Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing process modeling languages struggle to efficiently manage multiple instances of activities, leading to inefficient resource utilization and lack of control over long-running processes, as they often require aggregation of results to determine suitability or address changes during execution.
Innovation Solution
A system comprising an activity handler, a co-process handler, and a mediator that maintains activity state data and workflow data for multiple instances of a process model, allowing for real-time monitoring, control, and informed decision-making through the execution of a co-process model based on this data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple instances of activities are executed in parallel without centralized management, then productivity increases, but loss of information increases and reliability decreases
Solution Approach 1:
The patent introduces a mediator component that acts as an intermediary between the activity handler and co-process handler. This mediator manages the interaction between parallel activity instances and co-processes, maintaining activity state data and coordinating information flow. The mediator ensures that state information is properly tracked and shared across multiple parallel instances, preventing information loss while enabling high throughput execution.
2Productivity
If multiple instances of activities are executed in parallel without centralized management, then productivity increases, but reliability decreases
Solution Approach 1:
The patent implements feedback mechanisms where the activity handler maintains activity state data and provides this information to the co-process handler through the mediator. The co-processes can read activity state data and make decisions based on current process conditions, creating a feedback loop that enables reliable control of parallel activities. This feedback system ensures that even with multiple parallel instances, the overall process remains controllable and reliable.
3Adaptability or versatility
If activity state data is maintained and shared across multiple instances, then adaptability increases, but device complexity increases
Solution Approach 1:
The patent segments the system into distinct functional components: an activity handler responsible for executing activities and maintaining state data, a mediator for coordinating communication, and a co-process handler for managing co-processes. This segmentation allows each component to have a specific responsibility, making the overall complex system manageable through modular design. The activity state data is maintained in a structured manner that can be selectively accessed by different components based on their needs.
4Loss of time
If aggregation of results is delayed until completion of all instances, then loss of time increases, but manufacturing precision decreases
Solution Approach 1:
The patent enables preliminary actions by allowing co-processes to be executed during the runtime of activity instances, rather than waiting for all instances to complete. The co-process handler can read activity state data and execute co-processes based on intermediate results, enabling early decision-making and interventions. This preliminary action capability reduces time loss while maintaining decision accuracy by base
5Adaptability or versatility
If co-processes are executed based on activity state data, then adaptability increases, but device complexity increases
Solution Approach 1:
The patent implements a universal co-process mechanism that can handle multiple types of operations and decisions through a single framework. The co-process handler provides a unified interface for executing different co-processes based on activity state data, whether for monitoring, decision-making, or intervention purposes. This multi-functional approach increases adaptability while managing complexity through a standardized mechanism rather than requiring separate specialized systems for each function.
Data Source
AI summary
A first instance and a second instance of an activity of a process model may be executed, the first instance, the second instance, and the activity being associated with activity state data describing one or more states thereof. A co-process associated with the first instance, the second instance, and the activity may be spawned, and the co-process may be executed based on the activity state data.