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.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:
If you ignore a conflict, the status CONF (conflict) is also assigned to the technical object by the system. The system always assumes that the switch was performed.
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 technical object for which the conflict arose is, for example, untagged, then the conflict is automatically withdrawn.
See also:
Operational Cycle