Multi-tenant Workflow Automation via Routine Chaining

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing tools for managing multi-tenancy architectures in cloud computing are complex to build and maintain, particularly for small users, and lack efficient solutions for automating IT workflows and handling real-time events.

Innovation Solution

A system that allows users to define and execute workflows by chaining routines, using a markup language to encode workflows for execution in either real-time or non-real-time computing engines, leveraging a scalable and distributed complex event processing infrastructure, and providing a domain-specific language for simple and robust workflow management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If existing open source tools are used to manage multi-tenancy architectures, then automation of IT workflows is possible, but the system becomes complicated to build and maintain

Engineering Contradiction:
Improveworkflow automationVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system segments workflow management into reusable, modular routines that can be independently developed, stored, and combined. Each routine represents a discrete unit of automation logic that can be chained with others to form complete workflows, reducing overall system complexity while maintaining high automation capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer consisting of the routine repository and workflow orchestration mechanism. This intermediary abstracts the complexity of automation logic from end users, providing a simplified interface where users can chain pre-defined routines without needing to understand the underlying complex automation framework.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If a multi-tenant architecture is implemented to serve multiple users, then resource efficiency is improved, but managing different tenants' workflows becomes more complex

Engineering Contradiction:
Improveresource efficiencyVSAvoidmulti-tenancy management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements a universal routine repository and workflow management framework that serves all tenants through a single multi-tenant software instance. The same infrastructure handles workflow definition, storage, and execution for multiple tenants, eliminating the need for separate systems per tenant while maintaining tenant-specific workflow customization through the chaining mechanism.

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

3Ease of repair

If workflows are encoded using markup language for both human-readable and machine-readable formats, then ease of maintenance is improved, but processing time increases

Engineering Contradiction:
Improveworkflow maintainabilityVSAvoidworkflow processing time
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

The system creates and maintains copies of workflow definitions in multiple formats simultaneously. The markup language version serves as the authoritative human-readable copy for maintenance purposes, while compiled or interpreted versions serve as machine-executable copies for efficient runtime processing, eliminating the need to parse markup during execution.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10452433B2Event-driven multi-tenant computer-management platform
Publication Date: 2019.10.22 KASEYA INT
  • US10452433B2 patent drawing
  • US10452433B2 patent drawing
  • US10452433B2 patent drawing

AI summary

Computer implemented techniques comprise instructions configured to cause a processor to obtain routines, receive a user defined set of obtained routines to form a chain of at least two routines, produce the chain of the at least two routines according to the user defined set of routines, receive a user defined designation of the chain as a workflow, and produce by the computing system the designated workflow.