The NonExclusiveLimitAlarmTypeis used to specify the common behaviour for Alarm Typeswith multiple non-exclusive limits. The NonExclusiveLimitAlarmTypeis illustrated in Figure 21.

image025.png

Figure 21– NonExclusiveLimitAlarmType

The NonExclusiveLimitAlarmTypeis formally defined in Table 97and Table 98.

Table 97– NonExclusiveLimitAlarmType definition

Attribute

Value

BrowseName

NonExclusiveLimitAlarmType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the LimitAlarmType defined in clause 5.8.18.

HasSubtype

ObjectType

NonExclusiveLevelAlarmType

Defined in Clause 5.8.21.2

HasSubtype

ObjectType

NonExclusiveDeviationAlarmType

Defined in Clause 5.8.22.2

HasSubtype

ObjectType

NonExclusiveRateOfChangeAlarmType

Defined in Clause 5.8.23.2

HasComponent

Variable

HighHighState

LocalizedText

TwoStateVariableType

Optional

HasComponent

Variable

HighState

LocalizedText

TwoStateVariableType

Optional

HasComponent

Variable

LowState

LocalizedText

TwoStateVariableType

Optional

HasComponent

Variable

LowLowState

LocalizedText

TwoStateVariableType

Optional

ConformanceUnits

A & C Non-Exclusive Limit

Table 98– NonExclusiveLimitAlarmType Additional Subcomponents

BrowsePath

References

NodeClass

BrowseName

DataType

TypeDefinition

Others

HighHighState

HasProperty

Variable

TrueState

LocalizedText

PropertyType

HighHighState

HasProperty

Variable

FalseState

LocalizedText

PropertyType

HighState

HasProperty

Variable

TrueState

LocalizedText

PropertyType

HighState

HasProperty

Variable

FalseState

LocalizedText

PropertyType

LowState

HasProperty

Variable

TrueState

LocalizedText

PropertyType

LowState

HasProperty

Variable

FalseState

LocalizedText

PropertyType

LowLowState

HasProperty

Variable

TrueState

LocalizedText

PropertyType

LowLowState

HasProperty

Variable

FalseState

LocalizedText

PropertyType

The emptyOthers” column indicates that no ModellingRuleapplies.

HighHighState, HighState, LowState, and LowLowStaterepresent the non-exclusive states. As an example, it is possible that both HighStateand HighHighStateare 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 HighStateor the LowStateshall be provided even though all states are optional. It is implied by the definition of a HighStateand a LowState, that these groupings are mutually exclusive. A value cannot exceed both a HighStatevalue and a LowStatevalue simultaneously.