Unanticipated Faults Research Articles

Model-based reasoning in diagnostic expert systems for chemical process plants

A prototype expert system, called MODEX, for locating the cause(s) of a set of abnormalities in a chemical process id described. We discuss a methodology that aids the developement of expert systems which are process-independent, transparent in their reasoning, and capable of diagnosing a wide diversity of faults. The domain knowlege of the system is based on qualitative reasoning principles and captures physical interconnections between equipment units as well as causal relationships among process state variables. The inference strategy uses model-based reasoning for analyzing the plant behavior. Using a variant of the technique adopted from fault tree synthesis, an initially observed abnormal symptom is considered to be a top level event and a tree structure is constructed as the system searches for a basic event to which the fault can be traced. The diagnostic reasoning process is driven by a problem reduction strategy. The knowledge base is process-independent, thereby enhancing the generality of the expert system. Reasoning from first-principles with the aid of causal and fault models facilitates the diagnoses of novel or unanticipated faults. The system does not assume a single causal origin for all initially observed faults in the chemical process. Moreover, the system has the ability to locate multiple basic causes of a fault. The methodology also permits one to investigate the causal origins of multiple, unrelated, faults. The system provides explanations to user queries at various degrees of detail. Two test cases are discussed in detail.

Software reliability

The paper discusses the basic concepts underlying the issue of software reliability, and argues that programmed exception handling is inappropriate for dealing with suspected software errors. Instead it is shown, using an example program, how exception handling can be combined with the recovery block structure. The result is to improve the effectiveness with which problems due to anticipated faulty input data, hardware components, etc., are dealt with, while continuing to provide means for recovering from unanticipated faults, including ones due to residual software design errors.

Software reliability

The paper discusses the basic concepts underlying the issue of software reliability, and argues that programmed exception handling is inappropriate for dealing with suspected software errors. Instead it is shown, using an example program, how exception handling can be combined with the recovery block structure. The result is to improve the effectiveness with which problems due to anticipated faulty input data, hardware components, etc., are dealt with, while continuing to provide means for recovering from unanticipated faults, including ones due to residual software design errors.

Software reliability

The paper discusses the basic concepts underlying the issue of software reliability, and argues that programmed exception handling is inappropriate for dealing with suspected software errors. Instead it is shown, using an example program, how exception handling can be combined with the recovery block structure. The result is to improve the effectiveness with which problems due to anticipated faulty input data, hardware components, etc., are dealt with, while continuing to provide means for recovering from unanticipated faults, including ones due to residual software design errors.