Rules that define the relationships between operational conditions/types within an operational group.

The operational conditions and types that are compatible with one another are defined within an operational group (for example, mechanical or electrical). These must therefore be assigned to the operational groups before the conflict rules are defined.

The system uses conflict rules to compare the current operational condition or type with the one to be tagged/untagged, and displays the result on the screen. Conflict rules can be general or user-defined.

No definitions are required. The system assumes that a combination of different operational types always leads to a conflict. The check produces the following results:

N = Note

E = Error message

• The operational type cannot be overwritten.

• Operational conditions do not have any effect on the conflict verification.
• It is not possible to define asymmetrical rules.

If conflict rules have been defined in Customizing, then the system differentiates between the following results in a check:

N = Note

W = Warning

E = Error message

• The operational type can be overwritten.

• Operational conditions do have an effect on the conflict verification.

• It is possible to define asymmetrical rules.
• The system interprets missing rules as errors.

For example, a user-defined conflict rule states that the condition LOCKED can follow the condition CLOSED, but the condition CLOSED is not allowed to follow the condition LOCKED.

In an operational group E (= electrical), there are two operational conditions ON and OFF, each with three operational types RED, YELLOW and WHITE. There are therefore six possible combinations of operational condition and operational type. When the rules are created, all of these combinations can also be reversed, so that a total of 36 (= 6 x 6) conflict rules are entered in Customizing.