RPA Execution Permission Management Across Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Robotic process automation (RPA) systems face challenges in ensuring reliable execution of software robots due to unavailable resources and lack of effective tracking and evaluation of performance and cost savings.

Innovation Solution

Implementing a cross-platform execution management system using an automation management server that interacts with a status database to determine resource availability and administrative requirements, allowing for controlled execution of software robots and recording milestones for performance monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If software robots are executed without centralized permission management, then execution speed is improved, but execution reliability deteriorates due to resource unavailability

Engineering Contradiction:
Improveexecution speedVSAvoidexecution reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary actions by checking resource availability and administrative requirements before software robot execution. The automation management server evaluates status data in the status database beforehand to determine execution permission, ensuring resources are available before the robot starts running. This prevents execution failures due to resource unavailability while maintaining efficient execution when permissions are granted.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If centralized execution management is implemented, then execution reliability is improved, but system complexity increases

Engineering Contradiction:
Improveexecution reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The automation management server serves as an intermediary between software robots and the status database. It centralizes the management of execution permissions by receiving requests from software robots, querying the status database for resource availability and administrative requirements, and returning permission decisions. This intermediary approach consolidates complexity into a single component rather than distributing it across multiple systems, making the overall architecture more manageable while ensuring reliable execution control.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If performance tracking is implemented, then evaluation capability is improved, but data collection overhead increases

Engineering Contradiction:
Improveperformance evaluation capabilityVSAvoiddata collection overhead
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements feedback by recording milestone data that reflects software robot execution performance. The milestone management server receives execution results and stores them in the status database, creating a feedback loop that provides performance information back to the system. This allows evaluation of software robot effectiveness and resource utilization without requiring continuous monitoring during execution, minimizing data collection overhead while maintaining precise evaluation capability through periodic milestone recording.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240255924A1Cross-platform execution management for robotic process automation systems
Publication Date: 2024.08.01 AUTOMATION ANYWHERE INC
  • US20240255924A1 patent drawing
  • US20240255924A1 patent drawing
  • US20240255924A1 patent drawing

AI summary

Robotic process automation (RPA) systems with improved execution management are disclosed. One aspect of certain embodiments can provide cross-platform execution management of software robots by operating an automation management server to receive and respond to a request for permission to execute a particular software robot. The automation management server can interact with a status database to obtain status data, administrative approvals and/or dependency data for the software robot to determine whether the software robot should be given permission to execute. Another aspect of certain embodiments can support milestone recordation after a software robot completes its execution. The milestone being recorded can denote that the corresponding software robot has executed and its execution status. The milestones can provide for greater performance and/or value monitoring.