Search

Scope: Core (OPC-10000-*) All specs

32 result(s) for StateMachine

OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.7 ConditionRefresh Method

Event would be generated since there is no change to the StateMachine , but the limit on a Refresh would indicate 90, when the original Event had indicated 100. The Server
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.8 ConditionRefresh2 Method

changed to 90 no new Event would be generated since no change to the StateMachine , but the limit on a Refresh would indicate 90, when the original Event had indicated
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.2 AlarmConditionType

play/generated as long as the Alarm is active and unacknowledged, unless the silence StateMachine is included, in which case it may also be silenced by this StateMachine . The SilenceState ... that it is being reported on. Not all Clients will make use of this StateMachine , but it allows multiple Clients to synchronize audible Alarm states. Acknowledging an Alarm shall automatically
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.19.2 ExclusiveLimitStateMachineType

omit limits in an instance. If a model omits states or transitions in the StateMachine , it is recommended that they provide the optional Property AvailableStates and/or AvailableTransitions
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.1 Overview

returned to service. This section describes ReferenceTypes that can be used by a StateMachine to indicate that a specific Effect on Alarm s caused by the transition of a StateMachine ... describe the state of a process, system or equipment can vary, but an example StateMachine is provided in Annex
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.2 HasEffectDisable

instances of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are disabled, If the target is an Alarm instance then the given Alarm instance is disabled ... InverseName MayBeDisabledBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C StateMachine Trigger
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.3 HasEffectEnable

instances of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are enabled If the target is an Alarm instance then the given Alarm instance is enabled ... InverseName MayBeEnabledBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Trigger
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.4 HasEffectSuppressed

instance of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are suppressed, If the target is an Alarm instance then the given Alarm instance is suppressed ... InverseName MayBeSuppressedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Suppression Trigger
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.5 HasEffectUnsuppressed

instance of that AlarmType are no longer suppressed below the Object containing the StateMachine , if the target is an Alarm instance then the given Alarm instance is no longer suppressed ... InverseName MayBeUnsuppressedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Suppression Trigger
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

F.1 Overview

longer used, until the tank is returned to service. This section describes a StateMachine that can be deployed as part of a system designed and used to reflect the current ... system, this sample is just an illustration. The current state from the StateMachine is applied to all items in the HasNotifier hierarchy below the object with which the StateMachine
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

F.2 SystemStateStateMachineType

actual selection of States and Transitions would depend on the deployment of the StateMachine . If the StateMachine were being applied to a tank or other part of a process ... described States and Transitions . The transitions are defined in Table F.2 . The StateMachine supports six possible states including: Operating , ShuttingDown , StartingUp , Shutdown , OutOfService , Maintenance . It supports 12 possible Transitions
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

A.2.6.2 DomainDownloadType

extended components defined by the DomainDownload Type. Note the references to two sub State Machine Types , TransferStateMachine and FinishStateMachine . The DomainDownloadType omits references to the Reset Program Control Method ... HasComponent Method Resume Mandatory HasComponent Object FinalResultData BaseObjectType Mandatory Table A.3 specifies the Transfer State Machine type that is a sub State Machine of the DomainDownload Program Type . This definition
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.3 Definition of state machine

type is called a finite state machine. Therefore, we distinguish between StateMachineType and StateMachine and their subtypes like FiniteStateMachineType . The StateMachineType specifies a description of the state machine, that ... states, transitions, etc., whereas the StateMachine is an instance of the StateMachineType and only contains the current state. Each StateMachine contains information about the current state. If the StateMachineType
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.1 Overview

minimal example which illustrates how these Types can be used to describe a StateMachine . See OPC 10000-9 and OPC 10000-10 for additional examples of StateMachines . Figure ... StateMachine Information Model
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.2 StateMachineType

GeneratesEvent ReferenceType to indicate which Event(s) could be produced by the StateMachine . Subtypes may add Methods which affect the state of the machine. The Executable Attribute is used ... machine. The generation of AuditEvents for Methods is defined in OPC 10000-4 . A StateMachine may not be active. In this case, the CurrentState and LastTransition Variables shall have
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.3 StateVariableType

StateVariableType is the base VariableType for Variables that store the current state of a StateMachine as a human readable name. The StateVariableType is formally defined in Table 2 . Table ... available continuation options. StateMachines produce Events which may include the current state of a StateMachine . In that case Servers shall provide the Name , Number and EffectiveDisplayName of the StateVariableType
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.5 TransitionVariableType

base VariableType for Variables that store a Transition that occurred within a StateMachine as a human readable name. The SourceTimestamp for the value specifies when the Transition occurred. This value
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.6 FiniteStateMachineType

StateType ObjectType. Each State shall have a BrowseName which is unique within the StateMachine and shall have a StateNumber which shall also be unique across all States defined ... StateMachine . Be aware that States in a SubStateMachine may have the same StateNumber or BrowseName as States in the parent machine. A concrete subtype of FiniteStateMachineType shall define at least
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.7 FiniteStateVariableType

subtype of StateVariableType and is used to store the current state of a Finite StateMachine as a human readable name. The FiniteStateVariableType is formally defined in Table 7 . Table
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.16 HasSubStateMachine

SourceNode (the state) and the TargetNode (the SubStateMachine ) shall belong to the same StateMachine . Therefore, the SourceNode shall be referenced from the ObjectType FiniteStateMachineType or one of its subtypes
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.17 TransitionEventType

used to generate an Event identifying that a Transition of a StateMachine was triggered. It is formally defined in Table 17 . Table 17 - TransitionEventType Attribute Value BrowseName TransitionEventType IsAbstract True ... BaseEventType . The inherited Property SourceNode shall be filled with the NodeId of the StateMachine instance where the Transition occurs. If the Transition occurs in a SubStateMachine , then the NodeId
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.18 AuditUpdateStateEventType

used to generate an Event identifying that a Transition of a StateMachine was triggered. It is formally defined in Table 18 . Table 18 - AuditUpdateStateEventType Attribute Value BrowseName AuditUpdateStateEventType IsAbstract True ... AuditUpdateMethodEventType . The inherited Property SourceNode shall be filled with the NodeId of the StateMachine instance where the State changed. If the State changed in a SubStateMachine , then the NodeId
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.19 Special Restrictions on subtyping StateMachines

Special Restrictions on subtyping StateMachines In general, all rules on subtyping apply for StateMachine types as well. Some additional rules apply for StateMachine types. States and Transitions are not instantiated ... same TransitionNumber shall be defined on the subtype. All references defining the StateMachine ( HasCause , HasEffect , FromState , ToState , HasSubStateMachine, HasGuard ) shall be replicated in the subtype as well. If InstanceDeclarations
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.1 StateMachineType using inheritance

StateMachineType using inheritance In Figure 7 an example of a StateMachine is given using the Notation defined in OPC 10000-3 . First, a new StateMachineType is defined, called "MyStateMachineType
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.3 StateMachineType using containment

using containment Figure 9 gives an example of an ObjectType not only representing a StateMachine but also having some other functionality. The ObjectType "MyObjectType" has an Object ... MyComponent" representing this other functionality. But it also contains a StateMachine "MyStateMachine" of the type "MyStateMachineType". Objects of "MyObjectType" also contain such
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.4 Example of a StateMachine having Transition to SubStateMachine

Example of a StateMachine having Transition to SubStateMachine The StateMachines shown so far only had Transitions between States on the same level, that is, on the same StateMachine . Of cause ... possible and often required to have Transitions between States of the StateMachine and States of its SubStateMachine . Because a SubStateMachine can be defined by another StateMachineType and this type
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.5 Example of a StateMachine adding a SubStateMachine on a Subtype

Example of a StateMachine adding a SubStateMachine on a Subtype When a subtype of FiniteStateMachineType having States extends the StateMachine , it is not allowed to add additional States , but instead ... added to existing States . The example in Figure 12 shows a very simple StateMachine with two States . Figure 12 - Example of a StateMachine with two States In Figure
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.1 Overview

Overview This section describes extensions to the StateMachine model allowing choices and guards on StateMachines
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.2 ChoiceStateType

true and a Transition can be determined. If this is not the case, the StateMachine is non-well formed. To avoid this, the specific ElseGuardVariableType can be used, which ... Transitions is used. The algorithm to determine the Transition is server-specific. A sample StateMachine using a ChoiceState is given in Figure 16 . It provides a simplified representation
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.4 GuardVariableType

GuardVariableType The GuardVariableType provides the information of a Guard of a Transition in a StateMachine . A Guard indicates, if the Transition can be used or not. The Guard defines ... Guard in a human-readable way, that can be used to display the StateMachine . This base GuardVariableType does not define a machine-readable semantic of the Guard . The calculation
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.5 ExpressionGuardVariableType

mandatory Property Expression provides a ContentFilter , that shall be evaluated on the Object the StateMachine belongs to. This is a machine-readable semantic of the Guard . If the ContentFilter evaluates ... Variables defined on the StateMachineType and are validated on the instance of the StateMachine . If the definition of the Variable is not owned directly by the StateMachine but for example
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.7 Example of a StateMachine using a ChoiceState and Guards

Example of a StateMachine using a ChoiceState and Guards Taking the sample StateMachine of Figure 16 its representation in the OPC UA AddressSpace is shown in Figure 17 as RobotStateMachineType ... SimpleOperand OnPath and the Literal value "True". Figure 17 - Example of a StateMachine using ChoiceState and Guards