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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.4 Optimal Fault Diagnosis<br />

State-of-the-Practice<br />

Fault diagnosis at PMS<br />

• false alarm: If a component is diagnosed to be faulty while it is healthy, costs increase.<br />

At least, if you assume that the diagnosis is being used to bring the system in a better<br />

state 3 .<br />

• missed diagnosis: If a component is diagnosed healthy while it is not, a failure is likely<br />

to reoccur <strong>and</strong> degrade the dependability.<br />

2. Speed of diagnosis. The sooner an error <strong>and</strong> its fault is identified, the less impact a failure<br />

has. A fast diagnostic process increases the availability of the system. In other words, the<br />

customer downtime will be minimized.<br />

3. Low Uncertainty. Also known as diagnostic resolution or isolability. This is the extent to<br />

which a diagnostic process is able to minimize the set of suspicious components. It can be<br />

measured by using entropy. The more a root cause of failure is isolated, the less repair time<br />

is needed. Consequently, costs decrease <strong>and</strong> the availability of the system increases.<br />

4. Context independency. If the successful working of the diagnostic process highly depends on<br />

forces outside the sphere of influence of the company, obviously risks increase (e.g., dependance<br />

on employees, network of others, etc.).<br />

5. Low development costs. Development costs are all the costs that have to made prior to the<br />

start of the diagnostic process. These are the costs for developing all the diagnostic tools (e.g.,<br />

supporting artifacts, training sessions for troubleshooters, other prepare actions that precede<br />

the operational phase).<br />

6. Low runtime costs. Runtime time costs are all the costs that the company makes to keep the<br />

diagnostic process up <strong>and</strong> running.<br />

7. Explanation facility. The justification of a diagnosis helps in evaluating diagnostic decisions.<br />

It increases the trust in a dependable operation of the system. Also, the quality of the system<br />

can be evaluated <strong>and</strong> improved.<br />

8. Adaptability. Design changes occur frequently. There is always need for more/other functionality<br />

<strong>and</strong> better internal working. Therefore, the ability of a diagnostic process to cope<br />

with design changes is a prime concern. A failing in this ability results in a decrease of all<br />

other attributes that are listed in this list.<br />

The following items would add to perfectness, but are outside the scope of this thesis:<br />

• Robustness. This refers to the extent to which a diagnostic process can h<strong>and</strong>le unexpected<br />

situations.<br />

• Novelty Identifiability. The ability to detect <strong>and</strong> diagnose faults that did not occur before.<br />

• Ability to deal with multiple faults.<br />

• Reasonable storage <strong>and</strong> computational requirement.<br />

Although these 4 items are important attributes in an ideal approach to fault diagnosis, the work<br />

that this thesis presents does not discuss these items. However, the technique presented in Chapter<br />

4 could deal with these items, but in the case study of 5 the diagnostic performance in respect to<br />

robustness, novel identifiability, multiple faults, <strong>and</strong> storage <strong>and</strong> computation requirement is not<br />

examined.<br />

3 At PMS this means that a component that is diagnosed as unhealthy will be replaced.<br />

16

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

Saved successfully!

Ooh no, something went wrong!