OPC Alarms and Events OverviewSecure Site · 2016. 6. 27. · OPC A&E Overview exele.com Event...

OPC Alarms and EventsOverview

Presented by Exelewww.exele.com

OPC A&E Software Productswww.exele.com

A L A R M A N D N O T I F I C A T I O N S O F T W A R E

OPC A&E Overview exele.com

Tag-based vs. Event based monitoring

• Data values and states identified by unique tag names

• Monitoring system must identify the desired tags

• Example: read voltage from ‘Area1.MachineA.voltage’ and determine if it is above a limit value

Tag-based

• Events sent to monitoring system as they occur

• Event details included in the event properties/fields

• Example: High voltage alarm received at 10:09 from MachineA in Area1

Event-based


What is OPC A&E

• Created by the OPC Foundation (opcfoundation.org)

• Vendor neutral

• An OPC A&E client (like TopView Events) can subscribe to events and perform actions such as

– Additional filtering

– Logging

– Viewing

– Notification

Standard for Alarm and Event delivery


OPC A&E Servers

• Kepware OPC A&E plug-in for KepServerEX

• Emerson DeltaV

• Iconics

• GE Proficy iFix

• Honeywell Experion

• Yokogawa Exaopc

• Others…

OPC A&E Servers vendors include:


OPC A&E Overview

• Sample facility and alarms – Bakery

• Overview of event fields

• How to receive events (subscriptions)

– Configurable subscription parameters

– Subscription filter

Topics


Example Facility - Bakery

BUILD1

MIX1A MIX1B

OVEN1

BUILD2

MIX2A MIX2B

OVEN2

• Mixers: low and high mixing speed alarms

• Ovens: low and high temperature alarms, rate-of-change temperature alarm


Event fields

• What happened? (high speed alarm went active)

• When did it happen? (10am this morning)

• What type of event occurred? (alarm/condition)

• Where did it happen? (Building 1)

• Who generated the event (Mixer1B)

Standard event fields plus vendor fields


“Primary” Event Fields

Area

Source

Area and Source

BUILD1

MIX1A

MIX1B

OVEN1

BUILD2

MIX2A

MIX2B

OVEN2

Bakery


“Primary” Event Fields

Event type

Category

Condition

Type, Category, Condition

Condition/alarm

Level

HI

LO

Rate-of-change

ROC Up

ROC Down

Bakery


Event Fields

• Condition: associated with the detection of some condition that generally requires some sort of response by the user or operator. Alarms are condition events.

• Tracking: typically involve an action taken (example: machine stopped)

• Simple: all other events

* Some event fields only available for certain event types

Bakery: all events are alarms/conditions

Type


Event Fields

• Groupings of events supported by an OPC A&E Server

• Each category contains a name (string) and an ID (integer).

• Category names must be unique within the OPC A&E Server.

• Each source may generate events for multiple event categories.

Bakery: Level (low/high) and Rate-of-change are categories

Category


Event Fields

• Area: a grouping of equipment. The available areas are defined by the OPC A&E Server.Bakery: BUILD1 and BUILD2 are our Areas.

• Source: reference to the object that generated the event. Available sources are defined in the OPC A&E Server.Bakery: MIX1A, MIX1B, OVEN1, MIX2A, MIX2B, and OVEN2 are our Sources

• Severity: The urgency of the event, 1-1000Bakery: we will define severity levels of 500 to Level alarms and 800 to rate-of-change alarms

Area, Source, and Severity


Event Fields (conditions)

• Event time The time that the event occurred

• Active time (event type = condition) Time that the condition became active (for single-state conditions), or the time of the transition into the current sub-condition (for multi-state conditions)

• MessageText that describes the event

Times and Messaging



• Quality: good, bad, uncertain

– Based on the quality of the data that generated the event

• Acknowledge required

– An indicator as to whether or not an acknowledgement is required

Quality and Acknowledge



• Condition name (event type = condition)A condition is a named state. An alarm is a special case of a condition.Bakery: HI, LO, ROC UP, and ROC DOWN are conditions.

• Subcondition name (event type = condition)If a condition is multistate, each sub-state is represented by a Subcondition. If a condition is single state, it has one subcondition whose value is equal to the condition.

Bakery: HI, LO, ROC UP, and ROC DOWN are conditions. We did not define subconditions therefore the event condition and subcondition will contain the same value.

Condition and subcondition



• Active state

• Acknowledged state

• Enable state

• Quality

• Severity

• Subcondition

• Message

• Vendor attribute

Changed: which condition properties changed



• Active

• Acknowledged

• Enabled

New State: which event properties are currently set


Subscriptions

• OPC A&E Server callback to the client

• Multiple subscriptions can be created by a client

• Subscription filter

– 5 event fields can be part of the filter

– The filter reduces the number of events sent to the client

• Subscription properties (delivery details)

– How often to send events, how many per callback, …

Client must create a subscription to receive events


Subscription Filter Event fields

1. Event Type

2. Category

3. Source (mask supported)

4. Area (mask supported)

5. Severity (range supported)

There are 5 subscription filter fields

Filter includes 4 of the 5 primary event fields discussed earlier plus severity

Condition/subcondition cannot be used as a subscription filter


Subscription Filter Example

The subscription should return allLevel conditions/alarms

from ovens in Build1 and Build2

with a severity between 500 and 1000

Bakery example using all 5 filter fields

(category and type)

(source and area)

(severity)


Browsing the OPC A&E Server

Event type (filter)

Category (filter)

Condition

Areas (filter)

Sources (filter)

Some subscription filter fields can be queried to assist in creating the subscription filter


Subscription Settings

• Active

• Buffer time (time between callbacks)

• Maximum size (events per callback)

• Keep-alive time

Client can request subscription settings


Detecting alarm/condition active

• Active, Acknowledged, Inactive, …

Condition events may arrive for

Detecting alarm/condition active:

• Event type: Condition

• New state: Active (the condition is active)

• Changed:

– Active (the active state just changed)

– Subcondition (the subcondition just changed)

Exele Information Systems, [email protected]+1 585 385 9740

OPC A&E Resources: www.exele.com/opcae

OPC Alarms and Events OverviewSecure Site · 2016. 6. 27. · OPC A&E Overview exele.com Event...

Documents

Transcript of OPC Alarms and Events OverviewSecure Site · 2016. 6. 27. · OPC A&E Overview exele.com Event...