5.8.20 NonExclusiveLimitAlarmType

The NonExclusiveLimitAlarmType is used to specify the common behaviour for Alarm Types with multiple non-exclusive limits. The NonExclusiveLimitAlarmType is illustrated in Figure 21.

Figure 21 – NonExclusiveLimitAlarmType

The NonExclusiveLimitAlarmType is formally defined in Table 97 and Table 98.

Table 97 – NonExclusiveLimitAlarmType definition
Attribute Value
BrowseNameNonExclusiveLimitAlarmType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Modelling
Rule
Subtype of the LimitAlarmType defined in clause 5.8.18.
HasSubtypeObjectTypeNonExclusiveLevelAlarmTypeDefined in Clause 5.8.21.2
HasSubtypeObjectTypeNonExclusiveDeviationAlarmTypeDefined in Clause 5.8.22.2
HasSubtypeObjectTypeNonExclusiveRateOfChangeAlarmTypeDefined in Clause 5.8.23.2
HasComponentVariableHighHighStateLocalizedTextTwoStateVariableTypeOptional
HasComponentVariableHighStateLocalizedTextTwoStateVariableTypeOptional
HasComponentVariableLowStateLocalizedTextTwoStateVariableTypeOptional
HasComponentVariableLowLowStateLocalizedTextTwoStateVariableTypeOptional
ConformanceUnits
A & C Non-Exclusive Limit
Table 98 – NonExclusiveLimitAlarmType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
HighHighStateHasPropertyVariableTrueStateLocalizedTextPropertyType
HighHighStateHasPropertyVariableFalseStateLocalizedTextPropertyType
HighStateHasPropertyVariableTrueStateLocalizedTextPropertyType
HighStateHasPropertyVariableFalseStateLocalizedTextPropertyType
LowStateHasPropertyVariableTrueStateLocalizedTextPropertyType
LowStateHasPropertyVariableFalseStateLocalizedTextPropertyType
LowLowStateHasPropertyVariableTrueStateLocalizedTextPropertyType
LowLowStateHasPropertyVariableFalseStateLocalizedTextPropertyType

The empty “Others” column indicates that no ModellingRule applies.

HighHighState, HighState, LowState, and LowLowState represent the non-exclusive states. As an example, it is possible that both HighState and HighHighState are in their True state. Vendors may choose to support any subset of these states. Recommended state names are described in A.1.

Four optional limits are defined that configure these states. At least the HighState or the LowState shall be provided even though all states are optional. It is implied by the definition of a HighState and a LowState, that these groupings are mutually exclusive. A value cannot exceed both a HighState value and a LowState value simultaneously.