Software Robot Orchestration Using Integration-Action Pairs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current robotic process automation (RPA) systems lack the ability to seamlessly integrate with multiple platforms and adapt to new tasks, leading to inefficiencies and increased manual intervention, as they are not designed to handle complex operations or learn from user interactions effectively.
Innovation Solution
A software robot orchestration system that configures to operate across various platforms, decomposes tasks into integration-action pairs, learns from user actions, and performs intelligent exception decisioning to adapt and execute tasks autonomously, while ensuring secure and efficient task execution through access management and natural language processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current RPA systems are used to automate tasks, then task execution is achieved, but the systems lack the ability to integrate with multiple platforms and adapt to new tasks
Solution Approach 1:
The patent segments task execution into discrete integration-action pairs, where each pair represents a modular unit of functionality. This allows the system to handle complex multi-platform operations by breaking them down into manageable, reusable components that can be independently configured and executed across different platforms without increasing overall system complexity
Solution Approach 2:
The patent creates a universal integration-action pair framework that can operate across multiple platforms and execution environments. The same integration-action pair structure can be applied to different platforms (ERP systems, CRM systems, cloud services, etc.), providing multi-functionality and adaptability without requiring platform-specific complex configurations
2Productivity
If software robots are configured to handle complex tasks across multiple platforms, then task versatility increases, but manual intervention and training requirements increase
Solution Approach 1:
The patent performs preliminary action by pre-configuring integration-action pairs that encapsulate complex task logic and platform-specific configurations in advance. When a task needs to be executed, the system retrieves and applies these pre-configured pairs, eliminating the need for manual intervention during execution and reducing training time as users can leverage existing configured pairs
Solution Approach 2:
The patent implements feedback mechanisms where the software robot learns from user corrections and interactions. When users manually intervene to correct or modify task execution, this feedback is captured and used to automatically update the integration-action pairs, continuously improving automation efficiency while reducing future manual intervention requirements
3Extent of automation
If software robots perform intelligent exception decisioning, then autonomous decision-making improves, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary exception decisioning layer that sits between task execution and system control. This intermediary handles autonomous decision-making for exceptions by evaluating predefined criteria and taking appropriate actions, providing high-level automation without requiring complex decisioning logic throughout the entire system, thus maintaining manageable system complexity
Data Source
AI summary
An embodiment configures a software robot to operate collaboratively with a plurality of platforms within a work environment. The embodiment decomposes, via the software robot, a request to perform a task received from one of the platforms, into at least one integration-action pair. An integration in this pair represents a configuration to operate on an execution platform within the plurality of platforms where a function is to be executed; an action in the pair represents the function to be performed on the execution platform. Responsive to the determination that the at least one integration-action pair does not exist in a database of integration-action pairs, the embodiment trains the software robot to perform the function on the platform.