Dynamic Server Change Management via Transitioning Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current server change management systems lack flexibility and efficiency in transitioning virtual and physical servers between states, as they rely on predefined change mechanisms and do not effectively utilize server change objects to optimize changes based on current system states.

Innovation Solution

A system that includes a change manager to select and execute transitioning server change objects, allowing for dynamic state transitions of virtual and physical servers by encapsulating changes and providing an execution environment, which optimizes the change process by excluding unnecessary objects and enabling complex changes through server change groups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If predefined change mechanisms are used, then system stability is maintained, but adaptability to dynamic server states is reduced

Engineering Contradiction:
Improveadaptability to dynamic server statesVSAvoidchange management system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system transitions from static predefined change mechanisms to dynamic change selection. The change manager dynamically selects change objects based on current server states, allowing the system to adapt to varying conditions while maintaining a structured approach through the change object framework.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Changes are segmented into discrete change objects that can be independently selected and executed. This segmentation allows the system to handle complex changes as combinations of smaller, manageable units, improving adaptability without proportionally increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

2Productivity

If comprehensive change objects are used, then change completeness is improved, but execution efficiency is reduced

Engineering Contradiction:
Improvechange execution efficiencyVSAvoidnumber of change objects
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system applies partial action by selecting only the necessary change objects required to achieve the desired server state transition. The change manager evaluates current states and selects minimal sufficient change objects, avoiding execution of unnecessary changes while ensuring completeness of required transitions.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of time

If manual change processes are used, then control precision is maintained, but processing time increases

Engineering Contradiction:
Improvechange processing timeVSAvoidchange management automation
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The change manager autonomously selects and executes change objects based on current server states and desired outcomes. The system performs self-service by automatically determining which changes are needed and executing them without requiring manual intervention for each change decision, significantly reducing processing time while maintaining controlled precision through the structured change object framework.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8442958B2Server change management
Publication Date: 2013.05.14 CISCO TECHNOLOGY INC
  • US8442958B2 patent drawing
  • US8442958B2 patent drawing
  • US8442958B2 patent drawing

AI summary

In one embodiment, methods and systems for change management are described. A server system may include a physical server and a virtual server capable of being deployed on the physical server. A server change group may include one or more server change objects. Each server change object may represent a server change to be made to at least one of the physical server or the virtual server. A change manager may receive a request for a change to the server system, select transitioning change objects from among the server change objects to transition the server system from a current state to an expected state after implementation of the change, and execute the transitioning change objects to implement the change to the server system.