Example scenarios
- Last UpdatedJan 16, 2024
- 3 minute read
Scenario 1: A first, isolated maintenance action (down event)
The first scenario shows the behavior for a single action that causes downtime. Action 1 will cause two events to be created. Event 1 is the down event, while Event 2 is the up event. Initially, the function level will be 100, while Event 1 will request a lower function level, e.g. 50. This is how the decision tree will be traveled (follow the gray line):
Scenario 2: Coincidental maintenance: two down events
This second scenario describes the situation below. Here, two maintenance actions take place on the same system. Both would cause downtime, but a system that is already down, cannot go down again. We discuss the evaluation of Event 2, the moment Action 2 requests a down-event, while Event 1 already was a down-event. Here is how we traverse the decision tree:
The current function level is lower than 100, because Event 1 already caused the function level to be lowered. Let’s assume it is set to 0 (zero). This means Event 2 will cause a number of things:
-
Segment 1 will be ended, while Segment 2 will be started
-
For Segment 1, downtime will be written on Action 1
-
Based on the scoring mechanism, downtime for Segment 2 will be written on Action 1, or Action2
In the decision tree, this means the following route is followed:
-
The answer here is ‘no’, since Event 1 already caused the function level to be lowered (to zer0)
-
The answer here is ‘no’ again, since Event 2 requests the function level to go to zero again
-
Here the answer is ‘yes’, because Event 2 causes the function level to remain at zero
-
Segment 1 will be ended, and downtime for this segment will be written for Action1 (last remembered)
-
Now apply the scoring mechanism to determine whether for Segment 2 the downtime will be written for Action 1 or for Action 2. Refer to the scoring mechanism to learn how this works
The basics around assigning downtime to actions are now covered. However, downtime assignment is a bit more complex. The following paragraph discusses downtime assignment in more detail.