Impact Notification System for IT Infrastructure Outages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional IT infrastructure lacks an effective method to assess the impact of outages and dependencies between components, especially in complex environments with many-to-many relationships, making it challenging to notify stakeholders and manage outages.

Innovation Solution

An impact notification system utilizing metadata mapping, which dynamically maintains information on component dependencies, allowing for granular impact assessments and notifications to stakeholders during outages, and includes a processor to map metadata from server, application, and component databases to predict and notify affected components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional IT infrastructure monitoring is used, then system operation continues, but impact assessment of outages and component dependencies cannot be effectively performed

Engineering Contradiction:
Improveimpact assessment capabilityVSAvoiddependency information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The system performs preliminary mapping of component dependencies and relationships before outages occur. The metadata mapping structure pre-establishes the relationships between IT components, applications, and stakeholders, enabling rapid impact assessment when outages happen without needing to discover dependencies in real-time during the outage event.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a metadata mapping structure as an intermediary layer between IT components and the monitoring system. This metadata layer captures and stores dependency information, component relationships, and stakeholder associations, serving as a mediator that enables the system to assess impact without direct real-time communication between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If comprehensive metadata mapping is implemented to track all component relationships, then impact notification accuracy improves, but system complexity increases

Engineering Contradiction:
Improvenotification accuracyVSAvoidmetadata mapping structure
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments the complex IT infrastructure into discrete, manageable metadata entities including components, applications, stakeholders, and their relationships. Each entity is independently mapped and stored in the metadata mapping structure, allowing the system to handle complexity through modular organization rather than monolithic tracking of all relationships simultaneously.

Inventive Principle:
Principle #1Segmentation

3Speed

If real-time monitoring of all IT components is performed, then outage detection speed improves, but resource consumption increases

Engineering Contradiction:
Improveoutage detection speedVSAvoidsystem resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The metadata mapping structure serves as an intermediary cache that stores preprocessed relationship information. When outages occur, the system queries this pre-established metadata rather than performing real-time discovery across all components, significantly reducing resource consumption while maintaining rapid detection and notification capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9639411B2Impact notification system
Publication Date: 2017.05.02 BANK OF AMERICA CORP
  • US9639411B2 patent drawing
  • US9639411B2 patent drawing
  • US9639411B2 patent drawing

AI summary

Methods for notifying, in the event of a power outage, planned maintenance activity, a plurality of stakeholders of an enterprise infrastructure. The enterprise infrastructure may include components and relationships between components. The components may include data centers, data center components, applications, application components, and any other suitable components. The relationships may include relationships between data centers and data center components, relationships between data center components and applications, relationships between applications and application components, relationships between applications and stakeholders. Methods may receive power outage information at an impact notification center. Methods may determine the effect of the power outage on remaining components of the enterprise infrastructure and based on the determination, identify affected components. Methods may notify stakeholders of the power outage, identify service components which might get impacted and perform impact analysis and capacity planning in case of any disaster event where a data center and/or location is impacted.