Intelligent knowledge base for an alarm troubleshooting system
First Claim
Patent Images
1. A method of troubleshooting a controlled system, comprising:
- (a) providing a knowledge base of troubleshooting procedures, the knowledge base accessible using a computer having a graphical user interface;
(b1) storing the troubleshooting procedures in the knowledge base in a non-graphical file format;
(b2) converting the troubleshooting procedures from the non-graphical file format into a file format compatible with the graphical user interface;
(b3) verifying validity of the file format conversion performed at step (b2);
(b4) storing in the knowledge base the troubleshooting procedures converted at step (b2);
(b5) prioritizing the troubleshooting procedures associated with an operational problem in the controlled system in an order of probability to solve the problem; and
(c) presenting the troubleshooting procedures to a user in a graphical form using at least one step of a group of steps consisting of (i) presenting the procedures in an order of priority determined at step (b5), (ii) presenting the procedures containing an identifier of the operational problem, and (iii) presenting the procedures in an order defined by the user so that the user can use the troubleshooting procedures presented in the graphical form to troubleshoot the controlled system.
10 Assignments
0 Petitions
Accused Products
Abstract
A method and apparatus for troubleshooting information system use a graphical user interface (GUI) to a knowledge base of troubleshooting procedures for presenting the procedures in a graphical form, including a flow chart form and a decision tree form. In one embodiment, the troubleshooting procedures are further prioritized in an order of probability of solving a problem in a controlled system and retrieved in the prioritized order.
35 Citations
20 Claims
-
1. A method of troubleshooting a controlled system, comprising:
-
(a) providing a knowledge base of troubleshooting procedures, the knowledge base accessible using a computer having a graphical user interface;
(b1) storing the troubleshooting procedures in the knowledge base in a non-graphical file format;
(b2) converting the troubleshooting procedures from the non-graphical file format into a file format compatible with the graphical user interface;
(b3) verifying validity of the file format conversion performed at step (b2);
(b4) storing in the knowledge base the troubleshooting procedures converted at step (b2);
(b5) prioritizing the troubleshooting procedures associated with an operational problem in the controlled system in an order of probability to solve the problem; and
(c) presenting the troubleshooting procedures to a user in a graphical form using at least one step of a group of steps consisting of (i) presenting the procedures in an order of priority determined at step (b5), (ii) presenting the procedures containing an identifier of the operational problem, and (iii) presenting the procedures in an order defined by the user so that the user can use the troubleshooting procedures presented in the graphical form to troubleshoot the controlled system. - View Dependent Claims (3, 4, 5, 6, 7, 8, 11)
-
-
2. (canceled)
-
9. (canceled)
-
10. (canceled)
-
12. A troubleshooting information system, comprising:
-
a computer having a graphical user interface;
a knowledge base of troubleshooting procedures accessible using the computers the knowledge base including;
an information unit comprising at least one data bank of the troubleshooting procedures for at least one controlled system;
a prioritization tool for prioritizing the troubleshooting procedures;
a database of historical operational problems;
a depository of proposed troubleshooting procedures; and
a controller coupled to the computer and the knowledge base, the controller including a converter for converting the troubleshooting procedures into a file format compatible with the graphical user interface;
a search tool for retrieving the troubleshooting procedures from the knowledge base;
a verification tool for verifying the troubleshooting procedures against pre-determined conditions and requirements; and
a graphical tool for adding the troubleshooting procedures in a graphical form to the knowledge base. - View Dependent Claims (13, 14, 16, 17, 19, 20)
-
-
15. (canceled)
-
18. (canceled)
Specification