Knowledge based machine initiated maintenance system

• US 5,394,543 A
• Filed: 03/30/1993
• Issued: 02/28/1995
• Est. Priority Date: 02/05/1991
• Status: Expired due to Fees

• Current Assignee: Storage Technologies Corporation (Oracle Corporation)
• Original Assignee: Storage Technologies Corporation (Oracle Corporation)
• Inventors: Hill, Fletcher L., Jurestovsky, Nancy R., Beal, David G.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): HUA, LY
• Application Number:
  US08/040,166
• Time in Patent Office: 700 Days
• Field of Search: 371/29.1, 371/20.1, 371/16.5, 371/4, 371/15.1, 395/575
• US Class Current: 714/26
• CPC Class Codes: G06F 11/2205 using arrangements specific to the hardware being tested
• CPC Class Codes: G06F 11/2257 using expert systems

Abstract

The knowledge based system functions in a machine initiated maintenance environment to provide efficient and timely maintenance of customer equipment. The knowledge based system provides the failure evaluation function through the use of an expert or knowledge based system that is installed in the customer equipment. The knowledge based system makes use of a set of rules and hypotheses to operate on data collected from various points within the customer equipment to monitor the operational integrity of the customer equipment. This knowledge based system identifies the occurrence of a failure within the customer equipment and functions using its rules, hypotheses and collected data to isolate the source of the error in the customer equipment and, whenever possible, "fence" or isolate the failed field replaceable unit that has caused the error.

Claims

1. A machine initiated maintenance apparatus connected to and colocated with a customer system for identifying failed field replaceable units in said customer system, which customer system includes a plurality of field replaceable units, each of which contains at least one operational element thereon, comprising:

means for detecting the presence of a failure in said customer system;

means for generating a failure report which contains data relevant to said detected failure, including an identification of the failure mode and all operational elements on all field replaceable units that were cooperatively operative during said detected failure;

means for storing said failure report;

means for maintaining a failure analysis history containing data identifying each of said field replaceable units and associated composite failure data representative of known field replaceable unit failures;

means for comparing, substantially contemporaneously with occurrence of said failure, said stored failure report with said failure analysis history;

means for identifying at least one failed field replaceable unit based on said comparison.

2. The apparatus of claim 1 wherein said comparing means includes:

means for generating a list of said elements which are common to a plurality of said failure reports;

means for mapping said listed elements to at least one field replaceable unit containing said listed elements.

3. The apparatus of claim 2 wherein said identifying means includes:

means for prioritizing said at least one field replaceable unit to identify a most likely failed field replaceable unit.

4. The apparatus of claim 3 further including:

means, responsive to the replacement of said identified most likely failed field replaceable unit and the subsequent reoccurrence of said detected failure within a predetermined period of time, for identifying a new most likely failed field replaceable unit.

5. The apparatus of claim 1 further comprising:

means, responsive to said stored failure report, for producing a failure severity indication which denotes the impact of said detected failure on said customer system.

6. The apparatus of claim 1 further comprising:

means, responsive to said stored failure report, for producing a failure persistence indication which denotes the difficulty required to remedy said detected failure.

7. The apparatus of claim 1 further comprising:

means, responsive to said detected failure, for activating said customer system to retry the operation active during said detected failure to determine the persistance of said detected failure.

8. The apparatus of claim 7 wherein said activating means repeatedly activates said customer system until said operation is successful or a predetermined number of attempts are initiated.

9. The apparatus of claim 1 further including:

means responsive to said comparing means failing to match said generated failure report with said composite failure data in said failure analysis history for producing a new composite failure data representative of said generated failure report;

means for appending said produced composite failure data to said failure analysis history.

10. A machine initiated maintenance apparatus connected to and colocated with a customer system for identifying failed field replaceable units in said customer system, which customer system includes a plurality of field replaceable units, each of which contains at least one operational element thereon, comprising:

means for detecting the presence of a failure in said associated customer system;

means for generating a failure report which contains data relevant to said detected failure, including an identification of the failure mode and all operational elements on all field replaceable units that were cooperatively operative during said detected failure;

means for storing said failure report;

means for maintaining a failure analysis history containing data identifying each of said field replaceable units and associated failure data;

means for comparing, substantially contemporaneously with occurrence of said failure, said stored failure report with said failure analysis history, including;

means for generating a list of said elements which are common to a plurality of said failure reports,

means for mapping said listed elements to at least one field replaceable unit containing said listed elements,

means for identifying at least one failed field replaceable unit based on said comparison, including;

means for prioritizing said at least one field replaceable unit to identify a most likely failed field replaceable unit;

means, responsive to the replacement of said identified most likely failed field replaceable unit and the subsequent reoccurrence of said detected failure within a predetermined period of time, for identifying a new most likely failed field replaceable unit;

means, responsive to said stored failure report, for producing a failure severity indication which denotes the impact of said detected failure on said customer system;

means, responsive to said stored failure report, for producing a failure persistence indication which denotes the difficulty required to remedy said detected failure;

means, responsive to said detected failure, for activating said customer system to retry the operation active during said detected failure to determine the recursiveness of said detected failure;

means responsive to said comparing means failing to match said generated failure report with said composite failure data in said failure analysis history for producing a new composite failure data representative of said generated failure report;

means for appending said produced composite failure data to said failure analysis history.

11. In a machine initiated maintenance apparatus connected to and colocated With a customer system, a method of identifying failed field replaceable units in said customer system, which customer system includes a plurality of field replaceable units, each of which contains at least one operational element thereon, comprising the steps of:

detecting the presence of a failure in said associated customer system;

generating a failure report which contains data relevant to said detected failure, including an identification of the failure mode and all operational elements on all field replaceable units that were cooperatively operative during said detected failure;

storing said failure report;

maintaining a failure analysis history containing data identifying each of said field replaceable units and associated composite failure data representative of known field replaceable unit failures;

comparing, substantially contemporaneously with occurrence of said failure, said stored failure report with said failure analysis history;

identifying at least one failed field replaceable unit based on said comparison.

12. The method of claim 11 wherein said step of comparing includes:

generating a list of said elements which are common to a plurality of said failure reports;

mapping said listed elements to at least one field replaceable unit containing said listed elements.

13. The method of claim 12 wherein said step of identifying includes:

prioritizing said at least one field replaceable unit to identify a most likely failed field replaceable unit.

14. The method of claim 13 further including the step of:

identifying, in response to the replacement of said identified most likely failed field replaceable unit and the subsequent reoccurrence of said detected failure within a predetermined period of time, a new most likely failed field replaceable unit.

15. The method of claim 11 further comprising the step of:

producing, in response to said stored failure report, a failure severity indication which denotes the impact of said detected failure on said customer system.

16. The method of claim 11 further comprising the step of:

producing, in response to said stored failure report, a failure persistence indication which denotes the difficulty required to remedy said detected failure.

17. The method of claim 11 further comprising the step of:

activating, in response to said detected failure, said customer system to retry the operation active during said detected failure to determine the recursiveness of said detected failure.

18. The method of claim 17 wherein said step of activating repeatedly activates said customer system until said operation is successful or a predetermined number of attempts are initiated.

19. The method of claim 11 further including the steps of:

producing, in response to failing to match said generated failure report with said composite failure data in said failure analysis history, a new composite failure data representative of said generated failure report;

appending said produced composite failure data to said failure analysis history.