Check: Conflict
Use
Obligatory check whether the required operational conditions/types of a technical object to be switched can also be switched within an operational group.
Key Features
A conflict record is written by the system at the start of a tagging phase. This entry is only deleted again once the item has been untagged or temporarily untagged.
At the start of each operational phase, the system checks all available conflict records to see whether the operational conditions/types required for a technical object can also be switched in the Operational WCD. This check is based on general and user-defined conflict rules, which are checked for tagging, untagging and temporary untagging.
Activities
In the case of a conflict, you can:
Stop switching and remove the conflict
Ignore the conflict and continue switching. However, this requires a special authorization.
If you ignore a conflict, the system also assigns the status CONF
(conflict)
to the item. The system always assumes that the switching was carried out.
Example
The operational condition/type A generates conflicts. If you ignore these conflicts, then A is the new operational condition/type for the system.
If during lockout/tagout, the item for which the conflict arose is, for example, untagged, then the conflict is automatically withdrawn.
Note
To support you, the switching is visualized both on the maintenance- and switching screen of the Operational WCD as follows:
The tagging condition/type or untagging condition/type displayed does not match the current operational condition/type.
See also: