Search

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

43 result(s) for Conditions

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

3.2 Specification parts

data access. Part 9 ( OPC 10000-9 ) - Alarms and Conditions Part 9 specifies use of OPC UA support for access to Alarms and Conditions . The base system includes support ... simple Events ; this specification extends that support to include support for Alarms and Conditions . Part 10 ( OPC 10000-10 ) - Programs Part 10 specifies OPC UA support for access to Programs
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

1 Scope

Scope This document specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address ... captured in standards such as IEC 62682 and ISA 18.2 . The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2 . Annex
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

3.1.17 Retain

state that is interesting for a Client wishing to synchronize its state of Conditions with the Server 's state
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.1 General

General This document defines an Information Model for Conditions , Dialog Conditions , and Alarms including acknowledgement capabilities. It is built upon and extends base Event handling which is defined ... Profiles (see 10000-7 for Profile definitions). Some systems may expose historical Events and Conditions via the standard Historical Access framework (see 10000-11 for Historical Event definitions
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.2 Conditions

Conditions Conditions are used to represent the state of a system or one of its components. Some common examples are: a temperature exceeding a configured limit a device needing maintenance ... This is independent of whether they are exposed in the AddressSpace . As mentioned above, Conditions represent the state of a system or one of its components. In certain cases, however
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.5 Condition state synchronization

Server will respond with a RefreshStartEventType Event . This Event is followed by the Retained Conditions . The Server may also send new Event Notifications interspersed with the Refresh related Event Notifications ... Condition state. A Client that wishes to display the current status of Alarms and Conditions (known as a "current Alarm display") would use the following logic to process
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.6 Severity, quality, and comment

Severity, quality, and comment Comment , Severity and Quality are important elements of Conditions and any change to them will cause Event Notification s. The severity of a Condition is inherited
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
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.1 General

exist in the AddressSpace. For example, an AlarmGroup might reference a number of Conditions that do not exist in the AddressSpace. The following sub clauses define the OPC UA Alarm
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.1 General

concept of states differentiating it from the base Event model. Unlike the BaseEventType , Conditions are not transient. The ConditionType is further extended into Dialog and AcknowledgeableConditionType , each of which
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

Variable with a Value that is an RPM, may be the ConditionSource for Conditions that are related to the motor as well as a temperature sensor associated with the motor ... AlarmManager , the AlarmManager shall recover the Enabled / Disabled states of all current conditions. If the system can not determine if the Condition is Enabled or Disabled , it shall be Enabled
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 ... have the same ConditionId . This allows higher level alarm management systems to operate on Conditions and to perform analysis of them. A Condition instance may be an Object that appears
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.7 ConditionRefresh Method

copies shall contain the same EventId . The Server issues Event Notifications of any Retained Conditions and Retained Branches of Conditions that meet the Subscriptions content filter criteria. Note that
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.8 ConditionRefresh2 Method

Notifier MonitoredItem in the Subscription . The Server issues Event Notifications of any Retained Conditions and Retained Branches of Conditions that meet the Subscriptions content filter criteria. Note that the EventId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.6.2 DialogConditionType

DialogConditionType The DialogConditionType is used to represent Conditions as dialogs. It is illustrated in Figure 12 and formally defined in Table 24 and Table 25 . Figure 12 - DialogConditionType Overview Table
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.4 Confirm Method

False can be confirmed. Comment A localized text that shall be applied to the Conditions . Method result codes in Table 38 (defined in Call Service) Table 38 - Confirm result codes
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.2 AlarmConditionType

representing a situation that has returned to a normal state. The transitions of Conditions to the inactive and Active states are triggered by Server specific actions. Subtypes of the AlarmConditionType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.3 Unshelve2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Conditions . 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.7 OneShotShelve2 Method

Method parameters Argument Description Comment A localized text that shall be applied to the Conditions . 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.9.1 Overview

Overview Conditions are used in specific application domains like Maintenance, System or Process. The ConditionClass hierarchy is used to specify domains and is orthogonal to the ConditionType hierarchy. The ConditionClassId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.3 ProcessConditionClassType

ProcessConditionClassType The ProcessConditionClassType is used to classify Conditions related to the process itself. Examples of a process would be a control system in a boiler or the instrumentation associated with
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.4 MaintenanceConditionClassType

MaintenanceConditionClassType The MaintenanceConditionClassType is used to classify Conditions related to maintenance. Examples of maintenance would be Asset Management systems or conditions, which occur in process control systems, which are related
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.5 SystemConditionClassType

SystemConditionClassType The SystemConditionClassType is used to classify Conditions related to the System. It is formally defined in Table 116 . System Conditions occur in the controlling or monitoring system process. Examples
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.6 SafetyConditionClassType

SafetyConditionClassType The SafetyConditionClassType is used to classify Conditions related to safety. It is formally defined in Table 117 . Safety Conditions occur in the controlling or monitoring system process. Examples
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.7 HighlyManagedAlarmConditionClassType

suppression or any number of other special behaviours. The HighlyManagedAlarmConditionClassType is used to classify Conditions as highly managed Alarms . It is formally defined in Table 118 . Table 118 - HighlyManagedAlarmConditionClassType definition
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.8 TrainingConditionClassType

TrainingConditionClassType The TrainingConditionClassType is used to classify Conditions related to training system or training exercises. It is formally defined in Table 119 . These Conditions typically occur in a training system ... generated as part of a simulation for a training exercise. Training Conditions might be process or system conditions. It is expected that other standards groups or vendors will define domain
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.9 StatisticalConditionClassType

StatisticalConditionClassType The StatisticalConditionClassType is used to classify Conditions related that are based on statistical calculations. It is formally defined in Table 120 . These Conditions are generated as part
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.10 TestingConditionClassType

TestingConditionClassType The TestingConditionClassType is used to classify Conditions related to testing of an Alarm system or Alarm function. It is formally defined in Table 121 . Testing Conditions might include
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.6 AuditConditionAcknowledgeEventType

AuditConditionAcknowledgeEventType This EventType is used to indicate acknowledgement or confirmation of one or more Conditions . It is formally defined in Table 126 . Table 126 - AuditConditionAcknowledgeEventType definition Attribute Value BrowseName AuditConditionAcknowledgeEventType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.12 HasCondition Reference type

semantic of this ReferenceType is to specify the relationship between a ConditionSource and its Conditions . Each ConditionSource shall be the target of a HasEventSource Reference or a sub type ... HasEventSource . The AddressSpace organisation that shall be provided for Clients to detect Conditions and ConditionSources is defined in Clause 6 . Various examples for the use of this ReferenceType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.13 Alarm & Condition status codes

Alarm & Condition status codes Table 137 defines the StatusCodes defined for Alarm & Conditions . Table 137 - Alarm & Condition result codes Symbolic Id Description Bad_ConditionAlreadyEnabled The addressed Condition
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.14.2 Communication problems

value of NULL and a StatusCode of Bad_CommunicationError. For Subscription s that contain Conditions for which the failure applies, the effected Conditions generate an Event, if the Retain field
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.14.3 Redundant A & C servers

Servers , it shall be identical. This applies to all standard Event s, Alarms and Conditions . This may be accomplished by sharing of information between redundant Server (such as actual Event
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.1 General

General The AddressSpace organisation described in this Clause allows Clients to detect Conditions and ConditionSources . An additional hierarchy of Object Nodes that are notifiers may be established to define
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.3 Adding Conditions to the hierarchy

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 ... ConditionType . Clients can locate Conditions by first browsing for ConditionSources following HasEventSource References (including sub-types like the HasNotifier Reference ) and then browsing for HasCondition References from all target Nodes
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.4 Conditions in InstanceDeclarations

Conditions in InstanceDeclarations Figure 28 shows the use of the HasCondition Reference and the HasEventSource Reference in an InstanceDeclaration . They are used to indicate what References and Conditions are available
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.2 AddressSpace examples

HasCondition References to expose the organization of areas and sources with their associated Conditions . This hierarchy is additional to a hierarchy provided with Organizes and Aggregates References . Figure B.5 illustrates ... Reference with Condition instances. Figure B.5 - HasCondition used with Condition instances In systems where Conditions are not available as instances, the ConditionSource can reference the ConditionTypes instead. This is illustrated
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.1 Overview

existing A&E COM Clients and Servers to connect to UA Alarms and Conditions components. Simply stated, there are two aspects to the migration strategy. The first aspect enables ... Alarms and Conditions Client to connect to an existing Alarms and Event s COM Server via a UA Server wrapper. This wrapper is notated from this point forward
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.2.3 Event categories

TRIP TripAlarmType There is no generic mapping defined for A&E COM sub- Conditions . If an Event Category is mapped to a LimitAlarmType then the sub Condition name
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.1 General

Server combined with a UA Client . It maps the Alarms and Conditions address space of UA A & C Server into the appropriate COM Alarms and Event Object s. Subclauses
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.3 Event Type mapping

D.3.3 Event Type mapping Since all Alarms and Conditions Event s belong to a subtype of BaseEventType , the A&E COM UA Proxy maps the subtype as received from
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.1 Concepts

Object receives that have a ConditionClassId or SubConditionClassId of LogEntryConditionClass . For example, since Events / Conditions / Alarms instance can be defined by PLC programs and exposed in a Server , the LogObject
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.12.2 DeviceHealthDiagnosticAlarmType

DeviceHealthDiagnosticAlarmType The DeviceHealthDiagnosticAlarmType is a specialization of the InstrumentDiagnosticAlarmType intended to represent abnormal device conditions as defined by NAMUR NE 107. This type can be used in filters for monitored ... Subtype of the 0:InstrumentDiagnosticAlarmType defined in OPC 10000-9 . Conformance Units DI HealthDiagnosticsAlarm Conditions of subtypes of DeviceHealthDiagnosticAlarmType become active when the device enters the corresponding abnormal state