Method and system for assessing availability of complex electronic systems, including computer systems

• US 6,895,533 B2
• Filed: 03/21/2002
• Issued: 05/17/2005
• Est. Priority Date: 03/21/2002
• Status: Expired due to Fees

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Gray, William M., Wiebe, Lawrence D., Piet, Peter M., Kolovson, Curtis P.
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): Bonura, Timothy M.
• Application Number:
  US10/104,524
• Publication Number:
  US 20030182599A1
• Time in Patent Office: 1,153 Days
• Field of Search: 714/25, 714/47, 714/48
• US Class Current: 714/47.3
• CPC Class Codes: G06F 11/008 Reliability or availability analysis

Abstract

A semi-automated availability-assessment system and methodology. A comprehensive questionnaire providing detailed information about the hardware and operating-system components and configuration of a system, application-and-database-software components and configuration of the system, data related to other potential sources of unplanned downtime, and data related to potential sources of planned downtime is received. The information contained in the received questionnaire is processed in several steps. First, hardware and operating-system-component-and-configuration information is extracted in order to conduct a Markov-chain availability analysis of the overall system hardware and operating system to provide a first intermediate result. Application-and-database-software component and configuration information, along with data and estimates related to software component failure and recovery rates, as well as relevant data for other potential sources of unplanned downtime, are extracted from the questionnaire and compiled together to form a second intermediate result. Information related to maintenance and other planned activities that result in planned system downtime are extracted from the questionnaire and compiled together as a third intermediate result. Finally, the intermediate result sets are combined in a deterministic manner to produce a final availability assessment for the system.

Claims

1. A method for determining an availability of a complex system, the method comprising:

receiving information related to system-hardware components and operating-system components and configuration and compiling a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components;

receiving information related to non-operating-system software components and configurations and compiling a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations;

receiving information related to planned system downtimes and compiling a third, intermediate, system-availability-related result with respect to the planned system downtimes;

combining the first, second, and third intermediate system-availability-related results to produce a combined availability result; and

determining the availability of the complex system by calculating the availability of the complex system from the combined availability result.

2. The method of claim 1 wherein receiving information related to system-hardware components and operating-system components and configuration and compiling a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components further comprises:

receiving a completed questionnaire that includes information related to system-hardware components and operating-system components and configuration; and

extracting from the received, completed questionnaire information related to system-hardware components and operating-system components and configuration;

computing the first, intermediate, system-availability-related result from the extracted information related to system-hardware components and operating-system components and configuration.

3. The method of claim 2 wherein information related to system-hardware components and operating-system components and configuration includes component failure and recovery rates.

4. The method of claim 1 wherein receiving information related to non-operating-system software components and configurations and compiling a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations further comprises:

receiving a completed questionnaire that includes information related to non-operating-system software components and configurations;

extracting from the received, completed questionnaire information related to non-operating-system software components and configurations; and

computing the second, intermediate, system-availability-related result from the extracted information related to non-operating-system software components and configurations.

5. The method of claim 4 wherein information related to non-operating-system software components and configurations includes information related to component failure and recovery rates for application software and database components and configurations.

6. The method of claim 1 wherein receiving information related to planned system downtimes and compiling a third, intermediate, system-availability-related result with respect to the planned system downtimes further comprises:

receiving a completed questionnaire that includes information related to planned system downtimes;

extracting from the received, completed questionnaire information related to the planned system downtimes; and

computing the third, intermediate, system-availability-related result from the extracted information related to the planned system downtimes.

7. The method of claim 1 wherein the information related to system-hardware components and operating-system components and configuration is combined with hardware and operating-system component failure and recovery rate data and input into a Markov-chain analysis in order to compute the first intermediate availability.

8. The method of claim 1 wherein received information is input into a spreadsheet program that includes algorithm specifications for computing intermediate, system-availability-related results, for combining intermediate, system-availability-related results to produce the combined availability result, and for calculating the availability of the complex system from the combined availability result.

9. The method of claim 1 further including, prior to determining the availability of the complex system by calculating the availability of the complex system from the combined availability result:

receiving additional data and re-computing an intermediate, system-availability-relates result; and

re-combining the re-computed intermediate, system-availability-related result with previously computed, intermediate, system-availability-related results to produce a refined combined availability result; and

calculating the availability of the complex system from the refined combined availability result.

10. The method of claim 1 further including, prior to determining the availability of the complex system by calculating the availability of the complex system from the combined availability result:

modifying data and re-computing an intermediate, system-availability-related result;

re-combining the re-computed intermediate, system-availability-related result with previously computed, intermediate, system-availability-related results to produce a refined combined availability result; and

calculating the availability of the complex system from the refined combined availability result.

11. The method of claim 1 further including, prior to determining the availability of the complex system by calculating the availability of the complex system from the combined availability result:

modifying an algorithm specification for computing an intermediate, system-availability-related result and re-computing the intermediate, system-availability-related result;

re-combining the re-computed intermediate, system-availability-related result with previously computed, intermediate, system-availability-related results to produce a refined combined availability result; and

calculating the availability of the complex system from the refined combined availability result.

12. A set of computer instructions, encoded in a computer-readable medium, that direct a computer to:

receiving information related to system-hardware components and operating-system components and configuration and compiling a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components;

receiving information related to non-operating-system software components and configurations and compiling a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations;

receiving information related to planned system downtimes and compiling a third, intermediate, system-availability-related result with respect to the planned system downtimes;

combining the first, second, and third intermediate system-availability-related results to produce a combined availability result; and

determining the availability of the complex system by calculating the availability of the complex system from the combined availability result.

13. A complex-system availability, encoded in a computer readable or human-readable medium, determined by:

receiving information related to system-hardware components and operating-system components and configuration and compiling a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components;

receiving information related to non-operating-system software components and configurations and compiling a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations;

receiving information related to planned system downtimes and compiling a third, intermediate, system-availability-related result with respect to the planned system downtimes;

combining the first, second, and third intermediate system-availability-related results to produce a combined availability result; and

determining the availability of the complex system by calculating the availability of the complex system from the combined availability result.

14. A first system for determining an availability of a second, complex system, the first system comprising:

a means for soliciting and receiving information related to system-hardware components and operating-system components and configuration, non-operating-system software components and configurations, and planned system downtimes for the second, complex system;

a means for computing

a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components,

a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations, and

a third, intermediate, system-availability-related result with respect to the planned system downtimes;

a means for combining the first, second, and third intermediate system-availability-related results to produce a combined availability result; and

a means for determining the availability of the second, complex system by calculating the availability of the second, complex system from the combined availability result.

15. The system of claim 14 wherein the means for soliciting and receiving information related to system-hardware components and operating-system components and configuration, non-operating-system software components and configurations, and planned system downtimes includes:

sending a questionnaire soliciting information related to system-hardware components and operating-system components and configuration, non-operating-system software components and configurations, and planned system downtimes;

receiving a completed questionnaire that includes information related to system-hardware components and operating-system components and configuration, non-operating-system software components and configurations, and planned system downtimes; and

extracting from the received, completed questionnaire information related to system-hardware components and operating-system components and configuration, non-operating-system software components and configurations, and planned system downtimes.

16. The system of claim 14 wherein the means for computing a first, intermediate, system-availability-related result with respect to the system-hardware components and operating-system components, a second, intermediate, system-availability-related result with respect to the non-operating-system software components and configurations, and a third, intermediate, system-availability-related result with respect to the planned system downtimes comprises a spreadsheet program initialized with computational formulas.