Process Assembly Line for RPA Robot Orchestration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Robotic Process Automation (RPA) systems are limited to addressing individual processes within specific industries and lack a mechanism for cross-industry application, with software robots unable to call or trigger each other, leading to complex programming requirements and deployment challenges.

Innovation Solution

The introduction of a 'process assembly line' architecture that organizes software robots to be duplicated and cloned across scenarios, allowing single-function robots to be adapted and integrated through API calling, with a central administrator triggering successor robots, enabling easier management and integration of multiple robots for complex tasks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software robots are organized in traditional RPA systems to address individual processes, then each process can be automated independently, but the system lacks cross-industry applicability and requires complex programming for each scenario

Engineering Contradiction:
Improvecross-industry applicabilityVSAvoidprogramming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the software robot system into modular components organized in assembly line architectures. Each robot performs specific tasks within defined stages, allowing independent development and reuse across different industries while reducing overall system complexity through standardized interfaces

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal robot templates and assembly line configurations that can be applied across multiple industries. By designing robots with standardized capabilities and interchangeable components, the system achieves cross-industry versatility without requiring custom programming for each scenario

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

2Productivity

If software robots are designed with multiple functionalities to handle complex situations, then fewer robots are needed, but the programming becomes increasingly complex and error-prone

Engineering Contradiction:
Improvenumber of robots requiredVSAvoidrobot programming complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides complex automation tasks into sequential stages, with each stage handled by a specialized single-function robot. This segmentation allows robots to remain simple while the assembly line configuration provides the overall complexity needed for sophisticated processes

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces assembly line managers and coordination layers that mediate between individual robots and the overall process. These intermediaries handle the complexity of orchestrating multiple robots, allowing each robot to remain simple while achieving complex outcomes through coordinated action

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If each software robot is programmed with complex processes to handle all functionality, then individual robots can operate independently, but deployment and management become challenging

Engineering Contradiction:
Improverobot independenceVSAvoiddeployment ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments robot functionality into modular components that can be independently deployed. Each robot contains only the specific functions needed for its stage, making deployment simpler while maintaining reliability through the coordinated assembly line structure

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables robot templates and assembly line configurations to be copied and reused across different deployments. Standardized robot designs with proven reliability can be replicated without reprogramming, simplifying deployment while maintaining consistent performance

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If traditional RPA systems are used without assembly line architecture, then implementation is simpler for single processes, but merging and scaling process lines is not possible

Engineering Contradiction:
Improveinitial implementation easeVSAvoidprocess line merging capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the automation system into standardized assembly line modules that can be independently implemented and then merged. Each module maintains simple implementation while the standardized interfaces enable seamless integration and scaling of multiple process lines

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal assembly line templates and standardized robot interfaces that work across different process types. This universality allows simple initial implementation for single processes while enabling the merging and scaling of multiple process lines through consistent architectural patterns

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

Data Source

PatentUS11794348B2Process assembly line with robotic process automation
Publication Date: 2023.10.24 SAP SE
  • US11794348B2 patent drawing
  • US11794348B2 patent drawing
  • US11794348B2 patent drawing

AI summary

In an example embodiment, a novel “process assembly line” solution is provided that organizes software robots in a manner that, once configured, allows them to be duplicated and cloned into multiple scenarios, including in organizational structures where one software robot is triggered or called by another software robot. Instead of designing software robots with multiple functionalities in each to perform complex situations, the process assembly line can utilize software robots with single functions. This aids developers in building robust software robots and reduces potential errors.