Automated Provisioning System for Multi-Tenanted Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multi-tenanted platforms face inefficiencies due to manual processes in provisioning, upgrading, and tracking solutions, leading to increased time, maintenance costs, and limitations in simultaneous customer provisioning and future component additions.

Innovation Solution

A processor-implemented method and system for provisioning solutions in a multi-tenanted platform that automates the process by receiving requests, generating tickets, selecting bundles, provisioning components, scheduling queue tables, and executing scripts to create solution tables, enabling automated end-to-end customer onboarding and upgradation without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual processes are used for provisioning, then flexibility in handling individual customer requests is maintained, but time consumption and error rates increase significantly

Engineering Contradiction:
ImproveManual control flexibilityVSAvoidCustomer provisioning time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The provisioning process is segmented into distinct automated components: bundle selection based on customer requests, queue table generation with provisioning records, scheduled execution at predefined intervals, and script-based implementation. This segmentation allows each step to be independently optimized and executed automatically, reducing overall provisioning time while maintaining process control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the operational parameters from manual intervention to automated scheduling and execution. By implementing scheduled tasks that automatically fetch queued data and execute provisioning scripts at predefined intervals, the system transforms the provisioning process from labor-intensive manual operations to time-efficient automated operations with configurable execution parameters.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If manual provisioning processes are used, then individual customer requests can be handled, but simultaneous provisioning of multiple customers is not possible

Engineering Contradiction:
ImproveIndividual request handlingVSAvoidSimultaneous provisioning capacity
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The provisioning system is designed with universal capabilities to handle multiple customer requests simultaneously through a common automated framework. The queue table structure and scheduled execution mechanism can process multiple provisioning records in parallel, allowing the system to serve multiple customers at the same time while maintaining individual customization through bundle selection based on specific customer requests.

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

Solution Approach 2:

The system uses template-based bundle selections that can be copied and customized for different customers. Once a provisioning configuration is established for one customer, it can be replicated and adapted for other customers through the same automated process, enabling simultaneous provisioning while maintaining individual request specificity through parameter customization.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If manual provisioning is performed, then custom configurations can be made, but maintenance costs and complexity increase

Engineering Contradiction:
ImproveCustom configuration capabilityVSAvoidProvisioning system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The provisioning system performs self-service through automated bundle selection, queue table generation, and script execution. The system automatically selects appropriate bundles based on customer requests, generates the necessary provisioning records, and executes the provisioning process without requiring manual configuration for each customer. This self-service automation reduces maintenance complexity while preserving adaptability through configurable bundle parameters.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The queue table acts as an intermediary between customer requests and provisioning execution. It stores provisioning records that bridge the gap between high-level customer requirements and detailed implementation scripts, automating the translation process and reducing the complexity of direct manual configuration while maintaining customizability through the record structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If existing provisioning systems are used, then current solutions can be deployed, but adding new components in the future is restricted

Engineering Contradiction:
ImproveCurrent solution deploymentVSAvoidFuture component addition
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The provisioning system is designed dynamically to accommodate future changes. The bundle selection mechanism and queue table structure allow for easy addition of new components and configurations. When new solutions need to be deployed, they can be integrated as new bundles or provisioning records without restructuring the entire system, enabling both reliable current deployments and flexible future adaptability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3745265B1System and method of provisioning, upgrading and tracking solutions in a multi tenanted platform
Publication Date: 2023.04.12 TATA CONSULTANCY SERVICES LTD
  • EP3745265B1 patent drawingFigure 1
  • EP3745265B1 patent drawingFigure 2
  • EP3745265B1 patent drawingFigure 3A

AI summary

Embodiments of the present disclosure, implements method of provisioning set of solutions in a multi tenanted platform, by (a) receiving, a request for the set of solutions; (b) generating, a ticket for the request associated with at least one solution from the set of solutions; (c) selecting, a bundle based on the requested associated with the at least one solution; (d) provisioning, the selected bundle by the ticket for the at least one requested solution to obtain a provisioned bundle; (e) scheduling, the provisioning queue table at a predefined interval to obtain a plurality of provisioning records; (f) determining, at least one class for the provisioned bundle from the plurality of provisioning records; (g) provisioning, the at least one requested solution and a solution table is created in the schema; and (h) updating, status of the provisioning and notifying to a user.