Master-Minion RPA Orchestration for Workflow Branching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current robotic process automation (RPA) technologies lack the ability for master RPA robots to orchestrate and control minion RPA robots effectively, limiting their capability to handle complex tasks that require data retrieval, decision-making, and branching logic.
Innovation Solution
Implementing a system where a master RPA robot determines tasks for minion RPA robots, either embedded within or part of a pool, to execute specific workflows, allowing for deterministic or probabilistic task initiation, data retrieval, and decision-making, while the master robot continues or suspends its operations based on minion robot outputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RPA robots are executed individually to carry out their respective workflows, then each robot can operate independently with simple control logic, but the system lacks the capability to handle complex tasks requiring coordination and data sharing between robots
Solution Approach 1:
The patent divides the RPA system into master robots that orchestrate workflows and minion robots that execute specific tasks. This segmentation allows complex tasks to be broken down into manageable components, with the master robot handling coordination and decision-making while minion robots handle execution, thereby increasing adaptability without proportionally increasing overall system complexity
Solution Approach 2:
The master robot acts as an intermediary between the centralized conductor application and multiple minion robots. It receives task requests from the conductor, processes them using its own workflow logic, and distributes appropriate tasks to minion robots. This intermediary layer enables complex task coordination while maintaining a relatively simple structure at each individual robot level
2Adaptability or versatility
If a centralized conductor application controls all RPA robots, then scheduling and coordination are centralized, but the system lacks distributed decision-making capability and flexibility in handling unknown actions
Solution Approach 1:
The patent implements local quality by enabling master robots to make decisions autonomously based on their local workflow logic and the specific task context. Instead of all decisions being made centrally by the conductor application, the master robot can evaluate unknown actions, determine whether to execute them locally or delegate to minion robots, and make real-time decisions without constant central intervention, thereby distributing decision-making capability
Solution Approach 2:
The control architecture is made dynamic by allowing the master robot to adapt its behavior based on task requirements. The master robot can dynamically determine whether to execute tasks itself, delegate to embedded minions, or request from pooled minions, creating a flexible control structure that adjusts to different workflow scenarios rather than following rigid centralized scheduling
3Productivity
If RPA robots do not control other RPA robots, then the system maintains simple execution logic, but it cannot implement branching logic or delegate tasks dynamically based on runtime conditions
Solution Approach 1:
The patent merges the workflow execution capability with the robot control capability in the master robot. The master robot combines its own workflow logic with the ability to dynamically control and delegate to minion robots, creating a unified entity that can both process workflows and make real-time decisions about task distribution, thereby improving productivity through dynamic delegation while managing complexity through integration
Data Source
AI summary
Embedded and/or pooled robotic process automation (RPA) robots are disclosed. A master robot initiates one or more RPA robots in a deterministic and/or probabilistic manner. For instance, when a step in an RPA workflow of the master robot is encountered where an action is not clear, some data is missing, there are multiple possible branches, etc., one or more embedded and/or pooled minion robots may be called upon by the master robot to determine the next action to take, to retrieve missing data, to determine which branch is appropriate, etc. The master robot may perform orchestration functionality with respect to the minion robot(s).