Conditional IT Runtime Control via Pairing Constructs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current IT environments lack the tools and infrastructure to manage availability and recovery effectively, leading to unpredictable downtime, costly failures, and labor-intensive manual processes, with existing solutions being inflexible and proprietary, making it difficult to achieve consistent recovery across diverse resources and platforms.

Innovation Solution

A Business Resiliency Management System that enables conditional management of IT environments through runtime analysis of pairing constructs, allowing for dynamic evaluation and control of resource pairings, redundancy configurations, and automated recovery workflows to align with business objectives, integrating availability management with normal business operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual management techniques are used to align availability management with IT infrastructure, then flexibility in customizing recovery actions is improved, but labor intensity and time consumption increase significantly

Engineering Contradiction:
Improveflexibility in customizing recovery actionsVSAvoidlabor intensity
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The system enables automatic discovery and evaluation of pairing constructs between business applications and IT resources. The runtime engine automatically monitors, evaluates, and controls management actions without requiring manual intervention, allowing the system to self-manage availability and recovery operations while maintaining customizable recovery policies.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary evaluation of pairing constructs and establishes recovery policies before failures occur. By pre-configuring pairing relationships and recovery actions, the system can automatically respond to failures without requiring manual assessment at the time of incident, reducing labor intensity while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If disparate point products are integrated to create end-to-end availability solutions, then coverage scope is improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improvecoverage scopeVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system merges multiple availability management functions into a unified platform that handles monitoring, evaluation, and control of pairing constructs across diverse IT resources. By consolidating these functions into a single system rather than integrating disparate point products, the solution reduces integration complexity while maintaining comprehensive coverage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The availability management system is designed as a universal platform capable of managing pairing constructs across different business applications, IT resources, and failure scenarios. This multi-functional approach eliminates the need for separate point products for different scopes, reducing integration complexity while maintaining broad coverage.

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

3Measurement precision

If manual assessment is performed for every change in application or infrastructure, then accuracy in impact analysis is improved, but response time and productivity decrease

Engineering Contradiction:
Improveaccuracy in impact analysisVSAvoidresponse time
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system continuously monitors pairing constructs and automatically evaluates the impact of changes in real-time. By implementing continuous feedback loops that track relationships between business applications and IT resources, the system maintains accurate impact analysis without requiring manual reassessment for every change, thus improving response time while preserving accuracy.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system pre-establishes pairing constructs and evaluates potential impacts before changes are implemented. By performing preliminary impact analysis and having recovery policies ready in advance, the system can quickly respond to actual failures without requiring time-consuming manual assessment at the moment of incident.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8346931B2Conditional computer runtime control of an information technology environment based on pairing constructs
Publication Date: 2013.01.01 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8346931B2 patent drawing
  • US8346931B2 patent drawing
  • US8346931B2 patent drawing

AI summary

Management of an Information Technology (IT) environment is conditionally controlled based on runtime analysis of resource pairing constructs. Resource pairings are provided, and evaluated based on the current state of the environment. This real-time information is then used in performing managerial tasks, the results of which are effected by the runtime conditions.