# US 2014/0208167 A1 · Method and system for single point of failure analysis and remediation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0208167 A1
- Document ID: US20140208167A1
- Status: Published application
- Kind: A1
- Application number: 14/239,407
- Filed: 2011-10-28
- Published: 2014-07-24
- Earliest claimed: 2011-10-28
- Assignees: Hewlett-Packard Development Company, L.P.
- Inventors: Stefan Krampen; Kay Wolf
- Web page: https://patentgrep.com/patent/US20140208167A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/2257: {using expert systems}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the present invention disclose a method and system for single point of failure analysis (SPOF) and remediation. According to one embodiment, a SPOF analysis is performed based on component configuration information associated with a plurality of system components. Based on the SPOF analysis, at least one SPOF component is identified. In addition, remediation information for the identified SPOF is computed based on the component configuration information. The result of the SPOF analysis and the remediation information are then displayed to an operating user.

## Claims

### Claim 1

A computer-implemented method for single point of failure (SPOF) analysis and remediation, the method comprising:
performing a SPOF analysis based on configuration information of a plurality of system components;
identifying, based on the SPOF analysis, at least one SPOF component from the plurality of system components; and
determining remediation information for the at least one SPOF component based on SPOF analysis and configuration information; and
displaying results of the SPOF analysis and the remediation information to the operating user.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
defining the scope of the SPOF analysis; and
retrieving configuration information relating to components within the defined scope of the SPOF analysis.

### Claim 3 (depends on 2)

The method of claim 2, wherein the step of performing the SPOF analysis further comprises:
retrieving configuration information of the plurality of components from a SPOF database;
allocating, via a decomposition module, the plurality of components into separate logical units based on predefined rules; and
assessing, via a reliability module, a reliability rating of each component within the logical unit.

### Claim 4 (depends on 2)

The method of claim 2, wherein the step of performing the SPOF analysis further comprises:
identifying, via a dependency module, a dependability level of the plurality of components based on the reliability rating so as to determine at least one SPOF component having a dependability level below a predetermined threshold;
analyzing, via a remediation module, configuration information of affected components associated with the SPOF component so as to provide at least one remediation suggestion for the at least one SPOF component.

### Claim 5 (depends on 4)

The method of claim 4, further comprising
displaying, on a graphical user interface operated by a user, the remediation suggestion for the at least one SPOF component.

### Claim 6 (depends on 4)

The method of claim 4, wherein the dependability level includes the redundancy status of each of the plurality of components.

### Claim 7 (depends on 4)

The method of claim 4, wherein the dependency module is configured to output to the SPOF database a dependency diagram associated with the plurality of system components including a type of dependency and the number of dependencies for each component.

### Claim 8 (depends on 7)

The method of claim 7, wherein the dependability level of a component is based on the reliability level, the type of dependency, and the number of dependencies.

### Claim 9 (depends on 8)

The method of claim 8, wherein further comprising:
displaying, on a graphical user interface operated by a user, both an overview of risks and remediation costs associated with the identified SPOF component(s).

### Claim 10

A system for single point of failure (SPOF) analysis and remediation, the system comprising:
a SPOF engine configured to receive input data factors and configuration information associated with a plurality of system components, wherein the SPOF engine performs a SPOF analysis based on configuration information of a plurality of system components; and
a SPOF database analysis configured to store SPOF analysis information from the SPOF engine,
wherein at least one remediation option for an identified SPOF component is determined in response to the SPOF analysis; and
wherein results of the SPOF analysis and the at least one remediation option are displayed to an operating user.

### Claim 11 (depends on 10)

The system of claim 10, further comprising:
a configuration and management database for storing configuration information associated with each of the plurality of components.

### Claim 12 (depends on 10)

The system of claim 10, wherein the SPOF engine comprises:
a decomposition module configure to allocate the workload into separate logical units based on predefined rules;
a reliability module configured to a reliability rating of each component within the logical unit;
a dependency module configured to identify a dependability level of the plurality of components based on the reliability rating so as to determine at least one SPOF component having a dependability level below a predetermined threshold; and
a remediation module configured to analyze configuration information of affected components associated with the SPOF component so as to provide at least one remediation suggestion for the at least one SPOF component.

### Claim 13 (depends on 12)

The system of claim 12, wherein the dependability level includes the redundancy status of each of the plurality of components and is based on the reliability level, the type of dependency, and the number of dependencies.

### Claim 14 (depends on 12)

The method of claim 12, wherein the dependency module is configured to output to the SPOF database a dependency diagram associated with the plurality of system components including a type of dependency and the number of dependencies for each system component.

### Claim 15

A computer readable storage medium having stored executable instructions, that when executed by a processor, causes the processor to:
receive, via an operating user, a scope definition for a SPOF analysis;
retrieve, via a processor associated with a SPOF engine, configuration information relating to components within the defined scope of the SPOF analysis;
allocate, via a decomposition module associated with a SPOF engine, the plurality of components into separate logical units based on predefined rules;
assess, via a reliability module associated with a SPOF engine, a reliability rating of each component within the logical unit;
identify, via a dependency module associated with a SPOF engine, a dependability level of the plurality of components based on the reliability rating so as to determine at least one SPOF component having a dependability level below a predetermined threshold;
analyze, via a remediation module associated with a SPOF engine, configuration information of affected components associated with the SPOF component so as to compute at least one remediation suggestion for the at least one SPOF component;
display, via the processor and graphical user interface, a notification relating to at least one SPOF component and at least one remediation suggestion for said component to the operating user.
