Auxiliary User Interface for Batch Object Modification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional management and monitoring software for datacenters requires custom user interfaces for batch operations, which is time-consuming and costly, and lacks scalability for large datacenter environments.

Innovation Solution

The implementation of an auxiliary user interface that is automatically generated based on a primary user interface, allowing for batch modification of multiple objects without the need for custom interface design, using metadata and common data types to provide elements and values for editing, and is scalable for large groups of objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If custom user interfaces are designed for batch operations, then operational functionality is achieved, but development time and cost increase

Engineering Contradiction:
Improvebatch operation functionalityVSAvoiddevelopment time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system automatically generates a copy of the primary user interface elements and adapts them for batch operations. Instead of designing custom interfaces from scratch, the system replicates existing UI components and modifies them to handle multiple objects simultaneously, thereby reducing development time while maintaining operational functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The primary user interface is designed to serve multiple purposes: both single-object operations and batch operations. By making the interface universal, the system eliminates the need for separate custom interfaces for batch operations, reducing development time and maintenance overhead while providing comprehensive operational capability.

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

2Ease of operation

If custom user interfaces are designed for batch operations, then operational functionality is achieved, but development cost increases

Engineering Contradiction:
Improvebatch operation functionalityVSAvoiddevelopment cost
Core Design Contradiction:
Ease of operationVSEase of manufacture

Solution Approach 1:

The system automatically generates a copy of the primary user interface elements and adapts them for batch operations. Instead of designing custom interfaces from scratch, the system replicates existing UI components and modifies them to handle multiple objects simultaneously, thereby reducing development time while maintaining operational functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The primary user interface is designed to serve multiple purposes: both single-object operations and batch operations. By making the interface universal, the system eliminates the need for separate custom interfaces for batch operations, reducing development time and maintenance overhead while providing comprehensive operational capability.

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

3Adaptability or versatility

If conventional management software is used, then basic functionality is provided, but scalability for large datacenters is limited

Engineering Contradiction:
ImprovescalabilityVSAvoidsoftware architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically adapts the user interface based on the number and type of selected objects. When multiple objects are selected, the interface automatically transitions to batch operation mode, adjusting its behavior and capabilities accordingly. This dynamic adaptation enables scalability without requiring complex predefined architecture for different datacenter sizes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system segments the operational functionality into single-object and batch-operation modes, with a single interface that can handle both. By segmenting the functionality rather than creating separate interfaces, the system achieves scalability while maintaining architectural simplicity, as the same codebase serves both operational modes.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10078430B2Providing batch operations with an auxiliary user interface
Publication Date: 2018.09.18 VMWARE INC
  • US10078430B2 patent drawing
  • US10078430B2 patent drawing
  • US10078430B2 patent drawing

AI summary

A method for presenting an auxiliary user interface is described. A primary user interface comprising a plurality of objects is presented. In response to selecting a portion of the plurality of objects, access is granted to an auxiliary user interface. An auxiliary user interface is presented that allows for batch modification of the portion of the plurality of objects.