P. Struss 447
Actually, this purpose, which varies according to the type of system and the practi-
cal context of the task, ought to influence the nature of the expected diagnostic result
and also the diagnostic process itself. For instance, on-board diagnostics for a vehicle
subsystem should aim at the discrimination between classes of faults that, due to their
nature and criticality, require different immediate recovery and safety actions, whereas
off-board diagnosis of the same subsystem is focusing on discrimination between dif-
ferent suspect components in order to find the ones that need to be replaced. Usually,
there is no need for continued discrimination if this does not influence the choice of
the remedial action. Although this issue is both obvious and fundamental to diagnosis,
it has been mainly ignored in theoretical work, and there are (too) few contributions
to treating this means-end relationship in a general and systematic way [58].
In fact, in the context of real diagnosis work processes, the interdependency often
becomes even tighter, bidirectional and more complex, because the respective activ-
ities become intermingled: (partial) repair actions may be carried out to support the
overall diagnosis process. As pointed out earlier,the focus on faultlocalization in early
work on diagnosis can be explained by an (implicit) focus on replacement of com-
ponents as the remedial action. However, component replacement is but one special
instance of actions for moving a system back to a healthy state and, in fact, impossible
in some applications (e.g., space craft outside an orbit).
The diagnostic and testing theories and systems presented above are attempts to
automate reasoning tasks, namely to infer diagnoses from observations and to pro-
pose informative observations based on the previous results. However, in particular
in an industrial environment, in general, it is not these reasoning activities that are
expensive, but efforts spent on acting, such as de-assembling a device, installing mea-
surement equipment, and repairing the device. Compared to this, the time and cost
spent on thinking is often negligible, and the result of this thinking matters only if it
contributes to optimizing the overall workflow. The chance for diagnostic solutions to
be really employed in practice is heavily reduced if they are not designed and devel-
oped under this perspective. It should be noted, though, that the above considerations
apply only in a restricted way to on-board diagnostics, because they do not trigger
directly expensive human activities.
These considerations motivate work aiming at model-based generation of propos-
als for remedies, at an integrated perspective on diagnosis, testing, and applying reme-
dies, and at the integration of planning with model-based problem solving. Remedies
can involve a whole range of different actions that need to be reflected in model-based
systems in different:
• replacement of components that are suspect of failing usually leaves the struc-
ture of the device (and, hence, of the model) unchanged and simply changes
the behavior mode (if successful); however, sometimes, a component may be
replaced by one with different parameters or of a different type,
• reconfiguration exploits the structural redundancy of a device, which might
achieve the specified purpose in different ways and even under fault conditions.
Aircraft and space craft are equipped with redundant subsystems for critical
functions, and power networks are huge networks of switches that enable the
generation of different topologies with different paths between voltage sources
and sinks; since the components that modify the topology (switches, valves,etc.)