Search

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

81 result(s) for Condition

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.9 Condition

Condition generic term that is an extension to an Event Note 1 to entry: A Condition represents the conditions of a system or one of its components and always exists
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

6.9 Alarm related guidance

Alarm related guidance OPC UA supports a robust Alarm and Condition information model which includes the ability to disable alarms, shelve alarms, and to generally manage alarms. Alarm processing
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.2 Active

Active alarm state in which the alarm condition is true Note 1 to entry: This definition is copied from ISA 18.2 / IEC 62682 . Note 2 to entry: Other common terms ... Standing" for an Active Alarm and "Cleared" when the Condition has returned to normal and is no longer Active
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.7 ConditionClass

ConditionClass Condition grouping that indicates in which domain or for what purpose a certain Condition is used Note 1 to entry: Some top-level ConditionClasses are defined in this document
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.8 ConditionBranch

ConditionBranch specific state of a Condition Note 1 to entry: The Server can maintain ConditionBranches for the current state as well as for previous states
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.9 ConditionSource

ConditionSource element which a specific Condition is based upon or related to Note 1 to entry: Typically, it will be a Variable representing a process tag (e.g. FIC101
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.11 Disable

configured such that the Alarm will not be generated even though the base Alarm Condition is present Note 1 to entry: This definition is copied from EEMUA Publication 191 . Note
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.2 Conditions

that requires a user to confirm some step in the process before proceeding Each Condition instance is of a specific ConditionType . The ConditionType and derived types are sub-types ... ConditionTypes supported by a Server are exposed in the AddressSpace of the Server . Condition instances are specific implementations of a ConditionType . It is up to the Server whether such instances
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.3 Acknowledgeable Conditions

base ConditionType . AcknowledgeableConditions expose states related to acknowledged or confirmed in a Condition . An AckedState and a ConfirmedState extend the EnabledState defined by the Condition . The state model is illustrated ... some logic internal to the Server . For example, acknowledgment of a related Condition may result in this Condition becoming acknowledged, or the Condition may be set up to automatically Acknowledge
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.4 Previous states of Conditions

Previous states of Conditions Some systems require that previous states of a Condition are preserved for some time. A common use case is the acknowledgement process. In certain environments ... also be used for other use cases where snapshots of previous states of a Condition require additional actions
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.5 Condition state synchronization

Condition state synchronization When a Client subscribes for Events , the Notification of transitions will begin at the time of the Subscription . The currently existing state will not be reported. This ... until a new state change occurs. Clients can obtain the current state of all Condition instances that are in an interesting state, by requesting a Refresh for a Subscription
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.6 Severity, quality, and comment

change to them will cause Event Notification s. The severity of a Condition is inherited from the base Event model defined in 10000-5 . It indicates the urgency ... Condition and is also commonly called alarm priority or 'priority', especially in relation to Alarms in the ProcessConditionClassType . Severity is defined to have a range of 1-1000, but this
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.7 Dialogs

been wound and is ready for inspection. The Server would activate a Dialog Condition indicating to the user that an inspection is required. Once the inspection has taken place
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.8 Alarms

Active state and other states like Shelving state and Suppressed state to a Condition . The state model is illustrated in Figure 5 . The complete model with all states is defined ... state machine model An Alarm in the Active state indicates that the situation the Condition is representing currently exists. When an Alarm is an inactive state it is representing
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.10 Condition instances in the AddressSpace

Condition instances in the AddressSpace Because Conditions always have a state ( Enabled or Disabled ) and possibly many sub-states it makes sense to have instances of Conditions present ... AddressSpace . If the Server exposes Condition instances they usually will appear in the AddressSpace as components of the Objects that "own" them. For example, a temperature transmitter that
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.11 Alarm and Condition auditing

Alarm and Condition auditing The OPC UA Standards include provisions for auditing. Auditing is an important security and tracking concept. Audit records provide the "Who", "When ... Event . The standard AuditEventTypes defined in 10000-5 already include the fields required for Condition related audit records. To allow for filtering and grouping, this document defines a number
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.1 General

General The Alarm and Condition model extends the OPC UA base Event model by defining various Event Types based on the BaseEventType . All of the Event Types defined in this ... document can be further extended from domain to Server specific Alarm and Condition Types . Instances of Alarm and Condition Types may be optionally exposed in the AddressSpace in order
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.2 Two-state state machines

EffectiveDisplayName of the EnabledState could contain "Active/HighHigh" to specify that the Condition is active and has exceeded the HighHigh limit. Other optional Properties of the StateVariableType have
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.3 ConditionVariable

ConditionVariable Various information elements of a Condition are not considered to be states. However, a change in their value is considered important and supposed to trigger an Event Notification . These
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.4.2 HasTrueSubState ReferenceType

subordinate state of the True super state. If more than one state within a Condition is a sub state of the same super state (i.e. several HasTrueSubState References exist
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.4.3 HasFalseSubState ReferenceType

subordinate state of the False super state. If more than one state within a Condition is a sub state of the same super state (i.e. several HasFalseSubState References exist
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.1 General

General The Condition model extends the Event model by defining the ConditionType . The ConditionType introduces the concept of states differentiating it from the base Event model. Unlike the BaseEventType , Conditions ... extended into Dialog and AcknowledgeableConditionType , each of which has their own sub-types. The Condition model is illustrated in Figure 10 and formally defined in the subsequent tables
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

ConditionType The ConditionType defines all general characteristics of a Condition . All other ConditionTypes derive from it. It is formally defined in Table 8 and Table 9 . The False state ... NodeId is set to NULL. The SourceNode Property is the Node, which the Condition is associated with, it may be the same as the InputNode for an Alarm
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.3 Condition and branch instances

Condition and branch instances Conditions are Objects which have a state which changes over time. Each Condition instance has a ConditionId as an identifier which uniquely identifies it within ... Server . This Condition (and it representative ConditionId) follows the same rules associated with Nodes (and their representative NodeIds ) in the AddressSpace (see 10000-3 ). Therefore, once a Condition is created
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.4 Disable Method

Disable Method The Disable Method is used to change a Condition instance to the Disabled state. Normally, the NodeId of the object instance as the ObjectId is passed ... Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall allow Clients to call the Disable Method by specifying ConditionId as the ObjectId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.5 Enable Method

Enable Method The Enable Method is used to change a Condition instance to the enabled state. Normally, the NodeId of the object instance as the ObjectId is passed ... Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall allow Clients to call the Enable Method by specifying ConditionId as the ObjectId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.6 AddComment Method

AddComment Method is used to apply a comment to a specific state of a Condition instance. Normally, the NodeId of the Object instance is passed as the ObjectId ... Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the AddComment Method by specifying ConditionId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.7 ConditionRefresh Method

ConditionRefresh Method ConditionRefresh allows a Client to request a Refresh of all Condition instances that currently are in an interesting state (they have the Retain flag set). This includes previous ... states of a Condition instance for which the Server maintains Branches . A Client would typically invoke this Method when it initially connects to a Server and following any situations, such
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.8 ConditionRefresh2 Method

ConditionRefresh2 Method ConditionRefresh2 allows a Client to request a Refresh of all Condition instances that currently are in an interesting state (they have the Retain flag set) that are associated ... prior states if those states still need attention. In particular, this is True for Condition instances where previous states still need acknowledgement or confirmation. Table 23 specifies the AddressSpace representation
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.6.1 General

General The Dialog Model is an extension of the Condition model used by a Server to request user input. It provides functionality similar to the standard Message dialogs found ... Server specific response options in the ResponseOptionSet and by adding additional functionality to derived Condition Types
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.1 General

General The Acknowledgeable Condition Model extends the Condition model. States for acknowledgement and confirmation are added to the Condition model. AcknowledgeableConditions are represented by the AcknowledgeableConditionType which is a subtype
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.2 AcknowledgeableConditionType

AcknowledgeableConditionType inherits all Properties of the ConditionType . AckedState when False indicates that the Condition instance requires acknowledgement for the reported Condition state. When the Condition instance is acknowledged the AckedState ... state also requires acknowledgement, the Server shall create a branch of the Condition instance as specified in 4.2 . Clients are expected to keep track of all ConditionBranches where AckedState
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.3 Acknowledge Method

Acknowledge Method The Acknowledge Method is used to acknowledge an Event Notification for a Condition instance state where AckedState is False. Normally, the NodeId of the object instance is passed ... ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Acknowledge Method by specifying ConditionId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.4 Confirm Method

Confirm Method The Confirm Method is used to confirm an Event Notifications for a Condition instance state where ConfirmedState is False. Normally, the NodeId of the object instance is passed ... ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Confirm Method by specifying ConditionId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.2 AlarmConditionType

True EnabledState . ActiveState/Id when set to True indicates that the situation the Condition is representing currently exists. When a Condition instance is in the inactive state ( ActiveState/Id when ... optional Property MaxTimeShelved is used to set the maximum time that an Alarm Condition may be shelved. The value is expressed as duration. Systems can use this Property to prevent
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.5 Reset Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Reset Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.6 Reset2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Condition . If the Comment argument is NULL (both locale and text are empty) it shall
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.7 Silence Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Silence Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.8 Suppress Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Suppress Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.9 Suppress2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Condition . If the Comment argument is NULL (both locale and text are empty) it shall
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.10 Unsuppress Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Unsuppress Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.11 Unsuppress2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Condition . If the Comment argument is NULL (both locale and text are empty) it shall
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.12 RemoveFromService Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the RemoveFromService Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.13 RemoveFromService2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Condition . If the Comment argument is NULL (both locale and text are empty) it shall
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.14 PlaceInService Method

passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the PlaceInService Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.15 PlaceInService2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Condition . If the Comment argument is NULL (both locale and text are empty) it shall
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.1 Overview

typically used when an Alarm is continually occurring on a boundary (i.e. a Condition is jumping between High Alarm and HighHigh Alarm , always in the Active state). The OneShotShelving will ... transition is also a system generated transition; this transition is generated when the Condition goes to an inactive state. Figure 16 - Shelve state transitions The ShelvedStateMachineType includes a hierarchy
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.2 Unshelve Method

Unshelved state. Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed to the Call Service ... However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the Unshelve Method by specifying ConditionId as the ObjectId where
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.4 TimedShelve Method

described in Table 82 ). Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed ... Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the TimedShelve Method by specifying ConditionId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.5 TimedShelve2 Method

value of this Property. Comment A localized text that shall be applied to the Condition . Method Result Codes in Table 85 (defined in Call Service) Table 85 - TimedShelve2 result codes
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.6 OneShotShelve Method

OneShotShelved state. Normally, the MethodId found in the Shelving child of the Condition instance and the NodeId of the Shelving object as the ObjectId are passed to the Call Service ... However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the OneShotShelve Method by specifying ConditionId as the ObjectId where
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.2 OffNormalAlarmType

OffNormalAlarmType The OffNormalAlarmType is a specialization of the DiscreteAlarmType intended to represent a discrete Condition that is considered to be not normal. It is formally defined in Table 106 . This
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.3 SystemOffNormalAlarmType

SystemOffNormalAlarmType This Condition is used by a Server to indicate that an underlying system that is providing Alarm information is having a communication problem and that the Server may have ... invalid or incomplete Condition state in the Subscription . Its representation in the AddressSpace is formally defined in Table 107 . Table 107 - SystemOffNormalAlarmType definition Attribute Value BrowseName SystemOffNormalAlarmType IsAbstract False References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.4 TripAlarmType

TripAlarmType is a specialization of the OffNormalAlarmType intended to represent an equipment trip Condition . The Alarm becomes active when the monitored piece of equipment experiences some abnormal fault such ... motor shutting down due to an overload condition. It is formally defined in Table 108 . This Type is mainly used for categorization. Table 108 - TripAlarmType definition Attribute Value BrowseName TripAlarmType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.1 Overview

ConditionType hierarchy. The ConditionClassId Property of the ConditionType is used to assign a Condition to a ConditionClass . Clients can use this Property to filter out essential classes. OPC UA defines
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.2 BaseConditionClassType

BaseConditionClassType BaseConditionClassType is used as class whenever a Condition cannot be assigned to a more concrete class. Servers should use a more specific ConditionClass , if possible. All ConditionClass Types derive
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.10 TestingConditionClassType

Alarm function. It is formally defined in Table 121 . Testing Conditions might include a condition to test an alarm annunciation such as a horn or other panel. It might also ... used to temporarily reclassify a Condition to check response times or suppression logic. It is expected that other standards groups or vendors will define domain-specific sub-types. Table
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.2 AuditConditionEventType

Unless a subtype overrides the definition, the inherited Properties of the Condition will be used as defined. The inherited Property SourceNode shall be filled with the ConditionId . The SourceName shall ... Disable , Enable , Acknowledge, etc. ). This EventType can be further customized to reflect particular Condition related actions
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.3 AuditConditionEnableEventType

This EventType is used to indicate a change in the enabled state of a Condition instance. It is formally defined in Table 123 . Table 123 - AuditConditionEnableEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.8 AuditConditionShelvingEventType

This EventType is used to indicate a change to the Shelving state of a Condition instance. It is formally defined in Table 128 . Table 128 - AuditConditionShelvingEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.9 AuditConditionSuppressionEventType

This EventType is used to indicate a change to the Suppression state of a Condition instance. It is formally defined in Table 129 . Table 129 - AuditConditionSuppressionEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.10 AuditConditionSilenceEventType

This EventType is used to indicate a change to the Silence state of a Condition instance. It is formally defined in Table 130 . Table 130 - AuditConditionSilenceEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.11 AuditConditionResetEventType

This EventType is used to indicate a change to the Latched state of a Condition instance. It is formally defined in Table 130 . Table 131 - AuditConditionResetEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.12 AuditConditionOutOfServiceEventType

This EventType is used to indicate a change to the OutOfService State of a Condition instance. It is formally defined in Table 132 . Table 132 - AuditConditionOutOfServiceEventType definition Attribute Value BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.11.4 RefreshRequiredEventType

Server or in the subsystem below the Server that could or does invalidate the Condition state of a Subscription . Its representation in the AddressSpace is formally defined in Table ... Refresh2 When a Server detects an Event queue overflow, it shall track if any Condition Event s have been lost, if any Condition Event s were lost, it shall issue
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.12 HasCondition Reference type

VariableType Node or one of their InstanceDeclaration Nodes . The TargetNode shall be a Condition instance declaration or a ConditionType . The following rules for instantiation apply: All HasCondition References used ... ReferenceType shall be an Object , Variable or Method Node . The TargetNode shall be a Condition instance or a ConditionType . Table 136 - HasCondition ReferenceType Definition Attributes Value BrowseName HasCondition InverseName IsConditionOf
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.14.2 Communication problems

some implementation of an OPC UA A & C Server , the Alarms and Condition are provided by an underlying system. The expected behaviour of an A & C Server when ... with the communication failure contain a StatusCode of Bad_CommunicationError for the value. A Condition of the SystemOffNormalAlarmType shall be used to report the communication failure to Alarm Clients
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.3 Adding Conditions to the hierarchy

HasCondition is used to reference Conditions . The Reference is from a ConditionSource to a Condition instance or - if no instance is exposed by the Server - to the ConditionType . Clients ... HasNotifier hierarchy. The Variable LevelMeasurement and the Object "Device B" Reference Condition instances. The Object "Tank A" Reference s a ConditionType (MySystemAlarmType) indicating that a Condition
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.2 Server maintains current state only

support previous states and therefore do not create and maintain Branches of a single Condition . Figure B.1 shows an Alarm as it becomes active and then inactive and also ... lists the values of the state Variables . All Events are coming from the same Condition instance and therefore have the same ConditionId . Figure B.1 - Single state example Table B.1 - Example
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.3 Server maintains previous states

This example is for Servers that are able to maintain previous states of a Condition and therefore create and maintain Branches of a single Condition . Figure B.2 illustrates ... lists the values of the state Variables . All Events are coming from the same Condition instance and have therefore the same ConditionId . Figure B.2 - Previous state example Table B.2 - Example
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.4 Server current-State Model with Suppression

lists the values of the state Variables . All Events are coming from the same Condition instance and therefore have the same ConditionId . The Client subscription includes an event filter that ... column is sent. Figure B.3 - SuppressedState and OutOfServiceState example Table B.3 - Example of a Condition that is Suppressed / OutOfService EventId Active Suppressed State OutOf Service State Retain Retain sent Event
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.2 AddressSpace examples

Organizes and Aggregates References . Figure B.5 illustrates the use of the HasCondition Reference with Condition instances. Figure B.5 - HasCondition used with Condition instances In systems where Conditions are not available ... illustrated with the example in Figure B.6 . Figure B.6 - HasCondition reference to a Condition type Figure B.7 provides an example where the HasCondition Reference is already defined in the Type
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

Annex C Mapping to EEMUA (Informative)

this can be accomplished with the Acknowledge Method . Active Alarm Active = True An Alarm Condition which is on (i.e. limit has been exceeded and Condition continues to exist). Alarm Message ... defined in 10000-5 .) Text information presented to the Operator that describes the Alarm Condition . Alarm Priority Severity Property (defined in 10000-5 .) The relative importance assigned to an alarm
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.3 Event categories

constructed by appending the text 'EventType' to the Description of the Event Category. For Condition Event Types the text 'AlarmType' is appended to the Condition Name. These ObjectType Node ... depends on the A&E Event Type, the Event Category Description and the Condition Name; however, the best mapping requires knowledge of the semantics associated with the Event Categories
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.5 Event subscriptions

dwEventType Set to the NodeId of the ConditionClassType for the Event Category of a Condition Event Type. Set to the NodeId of BaseConditionClassType Node for non- Condition Event Types. ConditionClassName ... dwEventType Set to the BrowseName of the ConditionClassType for the Event Category of Condition Event Type. To set "BaseConditionClass" non- Condition Event Types. ConditionName szConditionName - BranchId - Always
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.6 Condition instances

D.2.6 Condition instances Condition instances do not appear in the UA Server address space. Condition s can be acknowledged by passing the EventId to the Acknowledge Method defined ... AcknowledgeableConditionType . Condition s cannot be enabled or disabled via the COM A&E Wrapper
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.7 Condition Refresh

D.2.7 Condition Refresh The COM A&E Wrapper does not store the state of Condition s. When ConditionRefresh is called the Refresh Method is called
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.3 Event Type mapping

Server to one of the three A&E Event types: Simple, Tracking and Condition . Figure D.2 shows the mapping as follows: Those A & C Event s which ... Event s which are ConditionType are marked as A&E Event type Condition . Those A & C Event s which are of any subtype except AuditEventType or ConditionType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.4 Event category mapping

D.3.4 Event category mapping Each A&E Event type (e.g. Simple, Tracking, Condition ) has an associated set of Event categories which are intended to define groupings ... Event s. For example, Level and Deviation are possible Event categories of the Condition Event type for an A&E COM Server . However, since A & C does
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.5 Event Category attribute mapping

Proxy The following items are present only for A&E Condition-Related Events szConditionName UA ConditionType Property: ConditionName szSubConditionName UA ActiveState Property: EffectiveDisplayName wChangeMask Calculated within Alarms and Events ... proxy wNewState: OPC_CONDITION_ACTIVE A & C AlarmConditionType Property: ActiveState Events mapped as non-Condition Events and those that do not derive from AlarmConditionType are set to ACTIVE
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.6 Event Condition mapping

D.3.6 Event Condition mapping Event s of any subtype of ConditionType are designated COM Condition Event s and are subject to additional processing due to the stateful nature of Condition ... Event s. COM Condition Event s transition between states composed of the triplet ENABLED|ACTIVE|ACKNOWLEDGED. In UA A & C, Event subtypes of ConditionType only carry a value which