Conditions determine which path of a control flow is passed.
Data types
The Data type attribute of the ERM attribute determines which operator can be used for the has as output connection. This connection leads from the function to the ERM attribute. Only the Text, Floating point number, Integer, and Boolean data types are relevant to the simulation. Boolean stands for the decision Yes (1) or No (0).
The following applies to the operators of the has as output connection:
Allocation := can be used for all data types.
Addition (+), subtraction (-), and multiplication (*) can be used only for floating point numbers and integers.
The comparison values of events that follow OR or XOR rules and are connected with an occurrence copy of the corresponding ERM attribute must match the ERM attribute's data type. For example, it does not make sense to use the Text data type and to check in the event following the OR or XOR rule whether the text is greater (>) than that specified in the ERM attribute. If you want to compare two conditions (ERM attributes) of a function, specify the Operand position attribute for both is compared to connections.
Modeling with an ERM attribute
Use an ERM attribute to control the progress of a process folder. The value resulting obtained during the simulation run is compared with the predefined value of the ERM attribute. This requires that an event directly follows a rule in each path. A rule is activated under the following conditions:
An is compared to connection must link a single ERM attribute to the event.
The Comparison operator event attribute must have been specified.
Depending on the ERM attribute type, the Comparison value, Comparison value (numeric), or Comparison value (logical) event attribute must have been specified.
The result of comparing the ERM attribute value of the process folder with the value of the ERM comparison attribute must be True. The values are compared on the basis of matching types. A numerical value is compared with the Comparison value (numeric) comparison attribute, a logical value is compared with the Comparison value (logical) comparison attribute. The entry for the Data type attribute in the ERM attribute determines which value pair is compared.
If it is an XOR rule, ensure that the value ranges do not overlap when modeling the conditions, so that only one path is activated.
If these conditions are met, the event is activated and the process folder is forwarded to the next control flow object. If not, the process folder waits at the rule.
Modeling with two ERM attributes
The progress of a process folder can be controlled using two ERM attributes: the value obtained during the simulation run is compared with the predefined values of two ERM attributes. The order in which the ERM attributes are checked is specified in the process. This requires that an event directly follows a rule in each path. A rule is activated under the following conditions:
An is compared to connection must link exactly two ERM attributes to the event.
Different values must have been specified for the Operand position attribute of both ERM attributes.
The Comparison operator event attribute must have been specified.
The result of comparing the two ERM attribute values on the basis of the operator (Comparison operator event attribute) must be True. The value of the ERM attribute with the lower operand position value is used to the left of the operator, the value of the ERM attribute with the higher operand position value is used to the right of the operator.
If it is an XOR rule, ensure that the value ranges do not overlap when modeling the conditions, so that only one path is activated.
If these conditions are met, the event is activated and the process folder is forwarded to the next control flow object. If not, the process folder waits at the rule.