Manifest-Enabled Analytics Deployment Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Provisioning an analytics platform is time-consuming and prone to human errors due to the complexity of deploying and configuring multiple software tools in virtualized datacenter and cloud computing environments, where lack of standards and disjointed systems create bottlenecks and require extensive human interaction.

Innovation Solution

A manifest-enabled deployment engine that automates the deployment of analytics platforms by using a manifest file to specify machines and tools, determine deployment order, select appropriate tool deployers, and deploy tools in a standardized manner through a single API call, thereby reducing manual intervention and improving speed and quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual deployment and configuration of software tools is performed, then flexibility and adaptability are maintained, but deployment time and human error increase significantly

Engineering Contradiction:
Improvedeployment speedVSAvoiddeployment quality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The deployment engine automatically performs deployment and configuration tasks without human intervention. The system reads deployment manifests, determines deployment orders, selects appropriate deployers, and executes deployments autonomously, eliminating manual errors while maintaining flexibility through configurable manifests.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The deployment engine acts as an intermediary between deployment manifests and target systems. It parses manifests, determines deployment orders, selects deployers, and manages the entire deployment process, separating human operators from direct system manipulation while ensuring consistent, repeatable deployments.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple separate systems and teams are used to manage credentials, perform scans, patch, configure backups, and operate tools, then security and quality control are improved, but system complexity and coordination overhead increase

Engineering Contradiction:
Improvesecurity and quality controlVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The deployment engine merges multiple deployment-related functions into a single integrated system. It handles credential management, dependency resolution, deployer selection, and deployment execution in one unified platform, reducing the need for multiple separate systems while maintaining security and quality controls through standardized processes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The deployment engine is designed as a universal platform that can handle various deployment scenarios and tool types through a single interface. It supports multiple deployers and tool types, managing diverse deployment needs through one multi-functional system rather than requiring separate specialized systems for each function.

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

3Manufacturing precision

If standardized deployment processes are implemented, then repeatability and quality are improved, but adaptability to different environments and tools may be reduced

Engineering Contradiction:
Improvedeployment repeatabilityVSAvoidenvironment compatibility
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The system uses deployment manifests that contain configurable parameters and variables. These manifests can be customized for different environments and tools while maintaining the same standardized deployment process. The engine parses and adapts manifest parameters to match specific deployment contexts, ensuring both repeatability and adaptability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The deployment process is segmented into distinct, modular components: manifest parsing, dependency resolution, deployer selection, and deployment execution. Each component is independent and can be configured separately through manifests, allowing standardized processes to adapt to different environments through modular configuration rather than requiring process changes.

Inventive Principle:
Principle #1Segmentation

4Manufacturing precision

If comprehensive quality assurance activities are performed, then deployment quality is improved, but deployment time and resource requirements increase

Engineering Contradiction:
Improvedeployment qualityVSAvoiddeployment duration
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs quality assurance checks automatically as part of the standardized deployment process. Deployment manifests include predefined validation rules and quality checks that are executed during the deployment workflow, ensuring quality without requiring separate, time-consuming QA activities. The engine validates manifests, checks dependencies, and verifies deployments automatically.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10713029B2Manifest-enabled analytics platform deployment engine
Publication Date: 2020.07.14 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10713029B2 patent drawing
  • US10713029B2 patent drawing
  • US10713029B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for provisioning an analytics platform. The methods, systems, and apparatus include actions of obtaining a manifest for a platform to be deployed where the manifest specifies machines and tools to deploy on the machines, determining an order to deploy the tools on the machines based on the manifest, selecting, based on the manifest file, tool deployers that are configured to deploy particular tools on machines from among multiple tool deployers, and deploying the tools on the machines with the tool deployers that are selected and in accordance with the order that is determined.