The ExclusiveLimitStateMachineTypedefines the state machine used by AlarmConditionTypesthat handle multiple mutually exclusive limits. It is illustrated in Figure 19.

image023.png

Figure 19– ExclusiveLimitStateMachineType

It is created by extending the FiniteStateMachineType. It is formally defined in Table 93and the state transitions are described in Table 94.

Table 93– ExclusiveLimitStateMachineType definition

Attribute

Value

BrowseName

ExclusiveLimitStateMachineType

IsAbstract

False

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the FiniteStateMachineType

HasComponent

Object

HighHigh

StateType

HasComponent

Object

High

StateType

HasComponent

Object

Low

StateType

HasComponent

Object

LowLow

StateType

HasComponent

Object

LowToLowLow

TransitionType

HasComponent

Object

LowLowToLow

TransitionType

HasComponent

Object

HighToHighHigh

TransitionType

HasComponent

Object

HighHighToHigh

TransitionType

ConformanceUnits

A & C Exclusive Limit

Table 94– ExclusiveLimitStateMachineType Additional References

SourceBrowsePath

References

IsForward

TargetBrowsePath

HighHighToHigh

FromState

True

HighHigh

ToState

True

High

HasEffect

True

AlarmConditionType

HighToHighHigh

FromState

True

High

ToState

True

HighHigh

HasEffect

True

AlarmConditionType

LowLowToLow

FromState

True

LowLow

ToState

True

Low

HasEffect

True

AlarmConditionType

LowToLowLow

FromState

True

Low

ToState

True

LowLow

HasEffect

True

AlarmConditionType

The component Variablesof the ExclusiveLimitStateMachineTypehave additional Attributesdefined in Table 95.

Table 95 ExclusiveLimitStateMachineType Attribute values for child Nodes

BrowsePath

Value Attribute

HighHigh

0:StateNumber

1

High

0:StateNumber

2

Low

0:StateNumber

3

LowLow

0:StateNumber

4

LowToLowLow

0:TransitionNumber

34

LowLowToLow

0:TransitionNumber

43

HighToHighHigh

0:TransitionNumber

21

HighHighToHigh

0:TransitionNumber

12

The ExclusiveLimitStateMachineTypedefines the sub state machine that represents the actual level of a multilevel Alarm when it is in the Activestate. The sub state machine defined here includes High, Low, HighHighand LowLowstates. This model also includes in its transition state a series of transition to and from a parent state, the inactive state. This state machine as it is defined shall be used as a sub state machine for a state machine which has an Activestate. This Activestate could be part of a “level” Alarmor “deviation” Alarmor any other Alarmstate machine.

The LowLow, Low, High, HighHighare typical for many industries. Vendors can introduce sub-state models that include additional limits; they may also omit limits in an instance. If a model omits states or transitions in the StateMachine, it is recommended that they provide the optional Property AvailableStatesand/or AvailableTransitions(see 10000-16).