Optional check whether a technical object, which should be tagged/untagged and thereby obtain a new operational condition or type, does not already have another operational condition/type not yet confirmed in the system within an operational group.

At the start of each operational phase, an activity, that is, a change in the operational condition/type is notified. 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.

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.

If another entry already exists using an intended operational condition/type, the technical object can not be tagged/untagged, unless the intended operational condition/type and the one already available have been entered as permissible in Customizing.

You cannot ignore the check. However, you can change or deactivate it.

There are three operational work clearance documents – WCD 1, WCD 2 and WCD 3. In each operational work clearance document, the technical object Valve A should be tagged/untagged as follows:

You exit the lockout/tagout for operational work clearance document 1. This means that you have set the status to Tag. Before you confirm this, operational work clearance documents 2 and 3 should also be tagged. The check will not generate a message for the tagging of operational work clearance document 2 because the technical object Valve A retains the same tagging condition as in operational work clearance document 1. However, the tagging of operational work clearance document 3 is stopped because the tagging condition is different from the work clearance document already exited.