Check: Time Frame
Use
Optional check that is used to ensure that further switcheson a technical object are only executed if an operational condition/typeis confirmed as executed.
At the start of each operational phase, an activity, that is, a change in the operational condition/type, is announced. As long as you do not confirm the execution of this activity, it remains undefined in the system, even if it has already been executed.
Therefore, no further operations can be executed.
Features
At the start of the operational phase, the system logs the operational condition/type, which the technical object should obtain for each operational group. This entry is only deleted again when you confirm the new operational condition/type.
However, if another entry already exists using an intended operational condition/type, the technical object cannot be switched, unless the intended operational condition/type and the existing operational condition/type agree according to the criteria defined in the application profile.
Activities
You cannot skip the check. However, you can change or deactivate it.
Example
There are three Operational WCDs – WCD 1, WCD 2 and WCD 3. In each Operational WCD, the technical object
ValveA
should be switched as follows:
Operational WCD |
Technical Object |
Tagging Condition |
|---|---|---|
WCD 1 |
Valve A |
ON |
WCD 2 |
Valve A |
ON |
WCD 3 |
Valve A |
OFF |
Note
This is a simplified example, in which both the same operational group and the same operational type are assumed.
You exit the tagging for Operational WCD1. This means that you set the status to
BTG (Tag)
. Before you confirm execution, Operational WCDs 2 and 3 should also be tagged. The check does not generate a message for the tagging of Operational WCD2, because the technical object
ValveA
is to be set to the same tagging condition as Operational WCD1. However, the tagging of Operational WCD3 is prevented, because the tagging condition is different from that already triggered.
See also: