This chart depicts a basic configuration enabling detection of unexpected situation, by linking the functional unit to a resilience-oriented Exception handler. Solid lines denote interfaces required for the operation of the basic configuration. Dotted lines denote behavior as in the original design.
The operators, considered to be part of the system, have a key role in the self control, by controlling the machine, constraining its behavior according to the operational rules .
In order to control the machine, the operators need to be aware of faults, so that they can compensate for them. However, the operators need assistance from the machine, in helping to detect and identify the faults.
The Exception handler is a basic add-on, enabling detection of various surprising hazards due to exceptional situations, including unexpected states and events.
The information about the faults is obtained by tracking the changes in the machine states and comparing the actual situation and activity to those described in a model of normal operation .
At run-time, the operators should set the effective scenario ( modes) and the Exception handler should generate alarm signals about hazards.
At run-time, the Exception handler generates reports with statistics about recurring incidences (
When testing (debugging) and troubleshooting the Exception handler, the system administrator triggers pseudo-faults of the functional unit and configures the Exception handler.
Updated on 11 May 2017.