Definition

The system behavior is defined as the system response to triggers.

Expected behavior

The behavior is expected if it complies with rules stored in the knowledge base. It is unexpected otherwise.

The goals of resilience-oriented design include preventing hazards and protecting from hazard. To protect from a hazard, we need to detect it. Detection may be reliable if it is automated.

In order to enable automatic detection, we need to formalize the rules defining what we mean by controlled operation, and normal operation. The rule knowledge base provides a compressed form of the scenarios, situations and activity.

How to use

The guidelines in this section may be used to specify the rules about the design scope (the operational states)  and the constraints scope (the operational procedures), regarding the following situations:

• In routine operation, namely, functional operation (such as production), maintenance, testing, training, etc.
• In exceptional situations, following a disturbance, during the recovery, until resuming normal operation
• Defining the default behavior in unexpected situations.

Updated on 22 Dec 2016.