Vendor Abstraction Layer for Data Center Deployment Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing procurement and deployment processes for data center infrastructure are time-consuming and complex, involving multiple validation points and requiring manual intervention, which can lead to delays and errors in upgrading capacity and introducing new equipment into production environments.

Innovation Solution

A temporally aware procurement and deployment system with a vendor abstraction layer that allows for automated configuration and validation of new equipment before physical arrival, using a policy-based domain architecture for coordinated change management across multiple vendors and components, enabling parallelization of timelines and reducing manual errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual procurement and deployment processes are used with multiple validation points, then system reliability is improved through thorough checking, but the deployment time and complexity increase significantly

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating virtual representations of infrastructure devices and validating configurations before physical deployment. The virtual device model allows configuration validation, capacity planning verification, and change management approval to be completed in advance, so that when the actual device arrives, deployment can proceed rapidly with minimal validation steps.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses virtual copies of infrastructure devices to represent physical devices in the network management system. These virtual devices replicate the functional and configurational characteristics of physical devices, allowing all validation, configuration, and approval processes to be performed on the virtual representation before the actual physical device is deployed, thereby separating the validation timeline from the physical deployment timeline.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If multiple validation checkpoints are implemented for capacity planning and upgrade verification, then manufacturing precision is improved, but the process complexity and number of steps increase

Engineering Contradiction:
Improveupgrade verification accuracyVSAvoidprocess complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system merges multiple validation functions into a unified virtual device modeling framework. Capacity planning validation, configuration verification, change management approval, and commissioning checks are all integrated into the virtual device representation, allowing a single comprehensive validation process to replace multiple separate checkpoints while maintaining all necessary verification accuracy.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The virtual device model serves multiple functions simultaneously: it represents the physical device, stores configuration data, validates capacity planning, tracks change management approvals, and enables pre-deployment testing. This multi-functional approach consolidates what would otherwise require separate systems and processes for each validation aspect.

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

3Productivity

If automated configuration and validation systems are implemented, then productivity is improved, but the initial system complexity and setup requirements increase

Engineering Contradiction:
Improvedeployment productivityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service automation where the virtual device model automatically triggers configuration generation, validation workflows, and deployment sequencing based on predefined policies and rules. Once the virtual representation is established, the system autonomously manages the entire deployment lifecycle without requiring manual intervention at each step, thereby achieving high productivity with minimal ongoing operational complexity.

Inventive Principle:
Principle #25Self-service

4Loss of time

If virtual device modeling and temporal awareness are used to parallelize procurement and deployment timelines, then loss of time is reduced, but the extent of automation and system sophistication increase

Engineering Contradiction:
Improveprocurement-deployment timelineVSAvoidautomation level
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The system performs all configuration validation, capacity planning verification, and change management approvals as preliminary actions on the virtual device model before the physical device is procured or arrives. This allows the procurement and deployment timelines to run in parallel, with the virtual representation being fully validated and ready-to-deploy while the actual hardware is being manufactured or shipped, thereby eliminating sequential waiting time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11431571B2Monitoring time-base policy domain architecture
Publication Date: 2022.08.30 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11431571B2 patent drawing
  • US11431571B2 patent drawing
  • US11431571B2 patent drawing

AI summary

Configuration management of devices from multiple vendors using a hardware abstraction capability is provided. Abstraction between a high-level representation and vendor specific terminology may assist in translating configuration commands and operational status indicators to a single consistent presentation interface. Information may be obtained from computer devices to represent operational metrics of a corporate network infrastructure. Collected metrics may be translated for consistency across vendors. Similarly, configuration commands may initially be provided without regard to vendor specific syntax. Utilizing the high-level abstracted representation, a user interface representation of operational status (without regard to vendor terminology) may be provided for a heterogenous rack of associated components from at least two different vendors. Collected data may be analyzed to provide predicted failure of components. Predicted failures may be further analyzed to provide a damage radius representative of potential impact caused by a predicted failure if that failure were to actually take place.