Conflict Rules
Definition
Rules that define the relationships between
operational conditions/types within an operational group.Use
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.
Structure
The system uses conflict rules to compare the current operational condition or type with the one to be switched, and displays the result on the screen. Conflict rules can be general or user-defined.
General Conflict Rules
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
User-Defined Conflict 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
Example
Example of general conflict rules:
If the operational conditions CLOSED and LOCKED belong to the same operational type, then their combination does not lead to a conflict.
Example of user-defined conflict rules:
For example, a user-defined conflict rule states that the operational condition LOCKED can follow the operational condition CLOSED, but the operational condition CLOSED is not allowed to follow the operational condition LOCKED.
Example calculation of the number of user-defined conflict rules:
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 defined in Customizing.