25.07.2014 Views

pdf download - Software and Computer Technology - TU Delft

pdf download - Software and Computer Technology - TU Delft

pdf download - Software and Computer Technology - TU Delft

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6.2 Recommendations Conclusions <strong>and</strong> Recommendations<br />

(MBD-2) does lead to entropy gain, <strong>and</strong> might be worth the costs of placing these sensors. Entropy<br />

can be used to decide which additional measurements are best.<br />

6.2 Recommendations<br />

The following recommendations help in establishing a fault diagnosis approach at PMS, that achieves<br />

higher dependability of Philips Cardio-Vascular Systems. Appendix D shows the ideal practice of a<br />

fault diagnosis process at PMS.<br />

• Currently, it is impossible to determine what fault(s) caused a certain failure. This must be<br />

solved, in order to evaluate the diagnostic performance of the current practice, <strong>and</strong> enable<br />

comparison with new approaches to fault diagnosis, such as MBD. The observations when a<br />

failure occurred are known <strong>and</strong> stored in the logs of each system, <strong>and</strong> by means of remote<br />

monitoring in a central database. The problem could be solved when Service Engineers insert<br />

their diagnosis of a failure, <strong>and</strong> what it did to recover the failure, into the central database.<br />

A tool must use the time of this insertion, <strong>and</strong> knowledge about which log entries contain<br />

observations about the failure, to link the diagnosis to the observations. For example, suppose<br />

a service engineers diagnoses a failure of the beam propeller movement of the frontal st<strong>and</strong>,<br />

namely fault scenario S13 (see Table 5.13). The database contains an ’error 11’ log entry. In<br />

the proposed situation, the service engineer records the failure ’beam propeller movement of<br />

the frontal st<strong>and</strong>’, the diagnosis that MBU is at fault, the replacement of the MBU, <strong>and</strong> the time of<br />

these actions. If the failure does not reoccur within short time, the automated tool concludes<br />

that the observables of the error 11 entry, with a time stamp close to the entry inserted by the<br />

service engineer, recovers the failure. Consequently, the central database must save the link<br />

between both the ’error 11’ entry <strong>and</strong> the entry inserted by the service engineer. This enables<br />

PMS to know what fault caused the failure.<br />

• Entropy is an important metric when developing MBD implementations. Its use as a feedback<br />

mechanism for constructing an optimal model, <strong>and</strong> optimal measurement points is very valuable.<br />

Research on how to achieve the highest entropy gain in fault diagnosis of the Philips<br />

Cardio-Vascular X-Ray Systems is valuable for research as well as business. Research is interested<br />

in the use of entropy in an industrial domain. Business could use entropy of diagnoses<br />

for developing very dependable medical systems, or in general, embedded systems.<br />

• Currently, the log entries of the Philips Cardio-Vascular X-Ray System logs do not contain<br />

sufficient data that can be used as observables in a MBD implementation. MBD <strong>and</strong> entropy<br />

are suitable mechanisms to decide which variables should be added to the log, or which additional<br />

sensors lead to the highest improvement of diagnostic performance. The approach for<br />

achieving this consists of the following steps: construct the model of a subsystem. Perform an<br />

entropy study to decide which measurements are best. If necessary, add sensors to the target<br />

system. Implement the mechanism to log the chosen variables. During runtime operation,<br />

the model <strong>and</strong> the logged observables must be fed to the MBD engine, resulting in a higher<br />

diagnostic performance.<br />

• The case study examined fault scenarios in which only one component was at false (single<br />

fault). Fault scenarios in which a failure is caused by multiple faults are likely to occur in<br />

reality, <strong>and</strong> implementing a MBD implementation that is able to accurately diagnose such<br />

fault scenarios could lead to higher dependability of the target system.<br />

70

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!