RPA Bot Orchestration for Flexible Endpoint Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing robotic process automation (RPA) systems lack flexibility in assigning bots to host devices, managing task execution schedules, and integrating with remote network management platforms.

Innovation Solution

An architecture for RPA orchestration on a managed network that allows flexible assignment of bots to host devices, dynamic task scheduling, and integration with remote network management platforms, utilizing persistent storage and processors to manage bot deployments and executions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprises deploy multiple siloed custom software applications to meet specific operational needs, then functional versatility is improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improvefunctional versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal bot orchestration platform that can execute multiple types of automation tasks across different applications and systems. The platform provides standardized interfaces and common infrastructure that support diverse automation scenarios (data entry, workflow automation, system integration) without requiring separate specialized systems for each function, thereby reducing overall system complexity while maintaining versatility

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments automation functionality into modular bot components that can be independently deployed, managed, and scaled. Each bot represents a discrete automation unit that can be assigned specific tasks, and the orchestration platform manages these segmented units through standardized processes. This modular segmentation allows enterprises to build versatile automation capabilities while avoiding the complexity of monolithic custom software systems

Inventive Principle:
Principle #1Segmentation

2Extent of automation

If enterprises develop custom software applications to automate specific tasks, then task automation capability is improved, but development time and resource requirements increase

Engineering Contradiction:
Improvetask automation capabilityVSAvoiddevelopment time
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The patent implements pre-configured bot templates and standardized automation processes that can be deployed without extensive custom development. The orchestration platform provides ready-made automation patterns for common business scenarios (data processing, workflow automation, system integration) that can be quickly instantiated and customized, significantly reducing development time compared to building custom automation software from scratch

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables replication of successful automation patterns across different contexts through the bot orchestration platform. Once an automation process is developed and validated, it can be copied and deployed to multiple bots and endpoints with minimal additional development effort. This copying mechanism allows rapid scaling of automation capabilities without proportionally increasing development time or resources

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12271719B2Orchestration for robotic process automation
Publication Date: 2025.04.08 SERVICENOW INC
  • US12271719B2 patent drawing
  • US12271719B2 patent drawing
  • US12271719B2 patent drawing

AI summary

An example embodiment may involve persistent storage containing definitions of (i) assignments of bots to endpoints, (ii) software packages for execution by the bots, (iii) schedules for the bots to execute the software packages, and (iv) processes that associate the bots with the software packages and the schedules. This embodiment may also involve processors configured to: receive, from a computing device, a request for bot deployment, wherein the computing device includes a bot runtime; identify, in the processes, a bot assigned to an endpoint that is associated with the computing device, wherein the bot is associated with a software package and a schedule; and transmit, to the computing device, data including a representation of the bot, a copy of the software package, and a copy of the schedule, wherein reception of the data causes the bot to execute, using the bot runtime, the software package in accordance with the schedule.