Dynamic RPA Resource Binding for Workflow Deployment Flexibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Robotic Process Automation (RPA) systems require complex management and troubleshooting, often necessitating collaboration between multiple entities, which can lead to productivity issues and discourage adoption due to runtime malfunctions and lack of user-friendly resource management.
Innovation Solution
An RPA orchestrator manages multiple software robots by receiving an RPA package with encoded workflows and resource specifications, determining resource availability, and exposing a user interface to indicate resource availability, allowing users to assign workflows and edit resource characteristics independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If conventional RPA systems are implemented with multiple entities managing robots, then robot functionality and automation capability are improved, but system complexity and troubleshooting difficulty increase
Solution Approach 1:
The patent combines resource management capabilities directly into the orchestrator UI, merging previously separate functions (resource provisioning, monitoring, and troubleshooting) into a single integrated interface. This allows users to manage RPA robots, queues, and resources without needing separate tools or expert collaboration, thus reducing system complexity while maintaining automation capability.
Solution Approach 2:
The system enables users to independently provision and manage RPA resources through the orchestrator UI without requiring expert intervention. Users can directly interact with queues, monitor resource availability, and troubleshoot issues themselves, eliminating the need for multiple entities and reducing system complexity while preserving full automation functionality.
2Reliability
If RPA resources are managed by multiple entities, then resource availability and reliability are improved, but ease of operation deteriorates due to coordination requirements
Solution Approach 1:
The orchestrator UI is designed as a universal interface that handles multiple functions including resource provisioning, queue management, robot assignment, and troubleshooting. This multi-functional design allows a single user interface to manage all RPA operations without requiring users to coordinate with multiple specialized entities, improving ease of operation while maintaining resource availability through centralized management.
Solution Approach 2:
The orchestrator acts as an intermediary between users and RPA resources, abstracting the complexity of resource management behind a unified interface. Users interact with the orchestrator rather than directly managing multiple resources and entities, which simplifies operations while the orchestrator ensures reliable resource availability through centralized coordination.
3Productivity
If default resource locations are used in RPA workflows, then deployment speed is improved, but adaptability to different environments deteriorates
Solution Approach 1:
The system dynamically manages resource locations through the orchestrator, allowing resource paths and configurations to be adjusted based on the deployment environment. Instead of using fixed default locations, the orchestrator can provision resources at appropriate locations and update workflow assignments accordingly, maintaining both rapid deployment through automation and adaptability to different environments.
Solution Approach 2:
The orchestrator enables parameter changes for resource locations and paths without requiring workflow redesign. Users can modify resource configurations through the orchestrator UI, and these parameter changes are automatically propagated to affected workflows, preserving deployment speed while enabling environmental adaptability.
Data Source
AI summary
In some embodiments, a workflow specification includes a set of default characteristics of a resource required by a robotic process automation (RPA) robot tasked with executing the respective workflow. Some embodiments enable a user to change the respective default characteristics (e.g., relocate and/or rename a file) without changing the workflow specification per se. Such changes may be performed via a user interface of an RPA orchestrator managing the execution of multiple RPA robots.