Integrated Disaster Recovery Management System

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current IT disaster recovery plans are complex, siloed, and lack integration with non-IT systems and business processes, leading to ineffective audits, lack of accountability, and a reactive rather than proactive approach to disasters, with no real-time status monitoring of IT and non-IT systems during incidents.

Innovation Solution

An integrated disaster recovery management system (IDR-MS) that uses a tree network architecture to hierarchically organize IT and non-IT assets, applies properties and relationships to assets, and employs real-time communication through IoT devices and APIs to proactively manage disasters, ensuring accountability and coordination across systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If ITDR plans are prepared by IT professionals in silos with complex technical details, then the plans cover comprehensive technical aspects, but the plans become difficult for business representatives to understand and review

Engineering Contradiction:

Improvecompleteness of technical coverageVSAvoidunderstandability by business representatives

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the disaster recovery plan into multiple hierarchical levels: executive summary for leadership, business impact analysis for business representatives, and detailed technical appendices for IT professionals. Each segment contains only the information relevant to that audience, resolving the contradiction between technical completeness and ease of understanding.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces business impact analysis as an intermediary layer that translates technical ITDR requirements into business language. This intermediary enables business representatives to understand and review disaster recovery plans without requiring deep technical knowledge, while still ensuring technical completeness through structured information flow.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If ITDR plans are compiled as single comprehensive documents, then all technical details are included, but the plans cannot be effectively audited or challenged for inaccuracies

Engineering Contradiction:

Improvecompleteness of technical detailsVSAvoideffectiveness of audit and review

Core Design Contradiction:

ReliabilityVSMeasurement precision

Solution Approach 1:

The patent divides the comprehensive ITDR plan into separate auditable segments including business impact analysis, recovery strategies, and technical appendices. Each segment can be independently reviewed and validated by appropriate stakeholders, enabling precise auditing while maintaining overall technical completeness.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent establishes feedback mechanisms where business representatives can review and challenge the business impact analysis portion of the plan, and IT professionals can validate the technical appendices. This structured feedback process enables effective auditing of specific segments without requiring review of the entire complex document.

Inventive Principle:

Principle #23Feedback

3Device complexity

If traditional ITDR plans are used without integration with non-IT systems, then IT-specific recovery procedures are detailed, but coordination with business processes and non-IT systems is lacking

Engineering Contradiction:

Improvedetail of IT recovery proceduresVSAvoidintegration with business processes

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent merges IT disaster recovery procedures with business continuity planning by integrating business impact analysis, non-IT system recovery, and IT technical procedures into a unified disaster recovery framework. This combination ensures coordination across all systems and processes while maintaining detailed IT-specific procedures where needed.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal disaster recovery framework that handles both IT and non-IT systems through common structures like business impact analysis and coordinated recovery procedures. This multi-functional approach enables the same framework to address diverse recovery needs across different systems and business processes.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of manufacture

If disaster recovery plans are reactive rather than proactive, then response procedures are documented, but real-time monitoring and prevention capabilities are absent

Engineering Contradiction:

Improvesimplicity of response proceduresVSAvoidproactive disaster management capability

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent implements preliminary action through business impact analysis that identifies critical business functions and their recovery requirements before disasters occur. This advance planning enables proactive risk assessment and preparation, allowing organizations to take preventive measures and respond more effectively when disasters happen.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11783263B2Integrated disaster recovery management

Publication Date: 2023.10.10 PANDE RAKESH

AI summary

A disaster recovery is provided. A plurality of assets is connected in a plurality of tree networks, and the plurality of tree networks are interlinked to form a master mesh network. When an asset in the master mesh network is impacted, multiple alternate paths are determined to operationalize at least some of the impacted assets.