Overview f OPC Alarms and Events Cpyright 2016 EXELE Infrmatin Systems, Inc. EXELE Infrmatin Systems (585) 385-9740 Web: http://www.exele.cm Supprt: supprt@exele.cm Sales: sales@exele.cm
Table f Cntents Overview f OPC A&E... 3 OPC A&E Overview and Terminlgy... 4 Sample Facility - Bakery... 4 Event Type and Categry... 5 Event Area and Surce... 6 Event Severity... 6 Brwsing the OPC A&E Server... 7 OPC A&E Event Fields... 7 Type... 7 Categry... 7 Area... 7 Surce... 7 Severity... 8 Event time... 8 Message... 8 Active time (event type = cnditin)... 8 Cnditin name (event type = cnditin)... 8 Subcnditin name (event type = cnditin)... 8 Quality (event type = cnditin)... 8 Changed (event type = cnditin)... 8 New State (event type = cnditin)... 10 Acknwledge required (event type = cnditin)... 10 OPC A&E Subscriptins... 11 Active... 11 Buffer time... 11 Maximum size... 11 Keep-alive time... 11 Filter... 11 Filter Mask... 12 Detecting alarm/cnditin active... 13 Filter Masks... 14 2
Overview f OPC A&E OPC A&E is a standard that allws alarm and event generatrs t reprt the details f their events t clients. An OPC A&E client (TpView Events) can subscribe t the events withut knwledge f the specifics f the underlying alarm generatr. Each OPC A&E event cntains details such as: The type f event The area and surce f the event Severity Event message Example OPC A&E Servers include: Emersn DeltaV (mre) Icnics (mre) Kepware (mre) GE Prficy ifix (mre) Hneywell Experin (mre) Ykgawa Exapc (mre) See www.pcfundatin.rg fr mre infrmatin n OPC A&E. 3
OPC A&E Overview and Terminlgy T receive OPC A&E events, a client must create a subscriptin with the OPC A&E Server. Each subscriptin defines details f the desired events (subscriptin filter) and settings that define the sme details f event delivery. Each OPC A&E event cntains basic infrmatin such as what happened (high level alarm) and when (at 10am this mrning) as well as additinal details such as the type f event (rate-f-change alarm), where it happened (prcessing area 9) and wh generated the event (tank 94). Each OPC A&E Server vendr can use these fields t prvide meaningful event infrmatin t clients. Sample Facility - Bakery T help explain OPC A&E we will use the fllwing sample facility: A Bakery facility has 2 buildings, BUILD1 and BUILD2. Each Building cntains 2 mixers and 1 ven. BUILD1 BUILD2 MIX1A and MIX1B OVEN1 MIX2A and MIX2B OVEN2 The mixers have alarms fr lw/high mixing speed (rpm < lw limit OR rpm > high limit). The vens have alarms fr lw/high temperature (temperature < lw limit OR temperature > high limit) and rate-f-change alarms (temperature change mre than 1 degree up OR dwn within a specified perid f time) 4
Event Type and Categry OPC A&E defines 3 event types: Simple, Tracking, and Cnditin. Alarms fall under the Cnditin event type. Each event type can cntain categries f alarms. TYPE = Simple, Tracking, r Cnditin Categry 1 Categry 2 If the event type is Cnditin, each categry can define a list f pssible cnditins TYPE = Cnditin Categry 1 Categry 2 Cnditin 1 Cnditin 2 Cnditin 3 Bakery Example (see Sample Facility - Bakery) Event type = Cnditin Categry = Level Cnditin = HI Cnditin = LO Categry = Rate f Change Cnditin = ROC UP Cnditin = ROC DOWN 5
Event Area and Surce Each OPC A&E event cntains a surce name. Each surce exists within an area. Area 1 Surce 1 Surce 2 Area 2 Surce 3 Surce 4 Bakery example (see Sample Facility - Bakery) The Areas are ur buildings, and the Surces are the mixers and vens Area = BUILD1 Surce = MIX1A Surce = MIX1B Area = BUILD2 Surce = OVEN1 Surce = MIX2A Surce = MIX2B Surce = OVEN2 Event Severity Each OPC A&E event cntains a severity value frm 1-1000 Bakery Example (see Sample Facility - Bakery) Mixer lw/high alarms (speed): severity = 500 Oven lw/high alarms (temperature): severity = 500 Oven rate-f-change alarms (temperature): severity = 800 6
Brwsing the OPC A&E Server The OPC A&E Specificatin prvides a mechanism fr a client t query the OPC A&E Server fr sme supprted field values. If implemented by the Server, a client can query the fllwing infrmatin Event Type Categries Cnditins Areas Surces The ability t query this infrmatin can assist with the definitin f a subscriptin filter. See Filter fr mre infrmatin n the subscriptin filter. OPC A&E Event Fields The OPC A&E standard defines the available event fields. Sme fields are available fr all event types while ther fields are specific t ne event type. The vendr can als supply a set f vendr attributes t prvide infrmatin beynd the standard list f event fields. When describing the event fields, we may use example infrmatin frm ur Sample Facility - Bakery. Nte: The fllwing list f OPC A&E event fields des nt include a few fields used internally by OPC A&E clients. Type Cnditin: assciated with the detectin f sme cnditin that generally requires sme srt f respnse by the user r peratr. Alarms are cnditin events. Tracking: typically invlve an actin taken (example: machine stpped) Categry Simple: all ther events Categries are grupings f events supprted by an OPC A&E Server. Each categry cntains a name (string) and an ID (integer). All 3 event types supprt categries but each categry can include events f nly ne type. Each surce may generate events fr multiple event categries. Categry names must be unique within the OPC A&E Server. Bakery: Level (lw/high) and Rate-f-change are categries Area An area is a gruping f equipment. The available areas are defined by the OPC A&E Server. Bakery: BUILD1 and BUILD2 are ur Areas. Surce A reference t the bject that generated the event. A surce culd be a prcess tag, a device, r a subsystem. Available surces are defined in the OPC A&E Server. 7
Bakery: MIX1A, MIX1B, OVEN1, MIX2A, MIX2B, and OVEN2 are ur Surces Severity The urgency f the event. This maybe a value in the range f 1 1000. Lw severities are meant fr infrmatinal alarms, and high severities indicate critical issues. Bakery: we will define severity levels f 500 t Level alarms and 800 t rate-f-change alarms Event time The time that the event ccurred. Message Message text that describes the event. Active time (event type = cnditin) Time that the cnditin became active (fr single-state cnditins), r the time f the transitin int the current sub-cnditin (fr multi-state cnditins). Cnditin name (event type = cnditin) A cnditin is a named state. An alarm is a special case f a cnditin, ne which is deemed t be abnrmal and requiring special attentin. Bakery: HI, LO, ROC UP, and ROC DOWN are cnditins. Subcnditin name (event type = cnditin) Cnditins maybe single state, r multi-state. A multi-state cnditin is ne whse state encmpasses multiple ranges r sub-states which are f interest. Fr example, a Level Alarm cnditin may have multiple sub-states including HI and HIHI. Each sub-state is represented by a Subcnditin. Subcnditins must be mutually exclusive. If a cnditin is single state, it has ne subcnditin whse value is equal t the cnditin. Bakery: HI, LO, ROC UP, and ROC DOWN are cnditins. We did nt define subcnditins therefre the event cnditin and subcnditin will cntain the same value. Quality (event type = cnditin) Indicates the quality f the underlying data items upn which this cnditin is based. The three basic quality values are Gd, Bad, and Uncertain. As an example, a HI cnditin event may be generated by a measurement value with an uncertain quality. The event quality wuld als be uncertain. Changed (event type = cnditin) Indicates which prperties f the cnditin have changed t have caused the OPC A&E Server t send the event. The changed prperties can include: Active state Acknwledged state Enable state Quality 8
Severity Subcnditin Message Vendr attribute 9
New State (event type = cnditin) Indicates the event prperties f the cnditin which are currently set. The new state can include: Active Acknwledged Enabled Nte: New state des nt indicate that an item has changed. It indicates that the item is currently set. As an example, a cnditin/alarm may ccur and then later be acknwledged while the alarm is still active. Tw events arrive: ne fr the alarm active and ne fr the acknwledge. In bth events the New State value f Active is set because the alarm is active. In the secnd event the New State value f Acknwledged is als set. See Detecting alarm/cnditin active fr infrmatin n detecting new alarm events. Acknwledge required (event type = cnditin) An indicatr as t whether r nt an acknwledgement is required. 10
OPC A&E Subscriptins An OPC A&E client can cnfigure ne r mre subscriptins. Each subscriptin defines: The OPC A&E Server Details f the desired events (subscriptin filter) Settings that define the details f event delivery An OPC A&E client des nt ask fr new events frm the subscriptin. An OPC A&E subscriptin creates callbacks t the client - as new events ccur the client s methd fr prcessing is called with the new events (the callback ). The subscriptin prperties allw the client t cntrl sme details f event delivery. A few f these settings are requests that can be verridden by the OPC A&E Server. Active Indicates if the subscriptin shuld receive events r nt Buffer time The minimum time between sending f events t the client Maximum size The maximum number f events that will be sent t the client in ne callback Keep-alive time Requests the OPC A&E Server t send heartbeat events if n real events have been sent. This allws a client t knw that the subscriptin is healthy even if real events are nt ccurring. Filter The subscriptin can specify a filter based n five event field values. See OPC A&E Event Fields fr mre infrmatin n each event fields. Event type: ne r mre event types (simple, tracking, cnditin) Severity: a range f allwed severity levels specified as lw severity thrugh high severity. Severity is a value frm 1-1000. Categry: ne r mre event categries Area: ne r mre areas r area masks (wildcards) Surce: ne r mre surces r surce masks (wildcards) * It may be pssible t query the OPC A&E Server fr a list f categries, cnditins, areas, and surces. See Brwsing the OPC A&E Server. If multiple fields are specified in the filter they are lgically AND d tgether. Example: filter EventType=Cnditin, Area=BUILD1 includes events with event type = Cnditin AND area = BUILD1 If the same field is specified multiple times in the filter they are lgically OR d tgether. Example filter Area=BUILD1, Area=BUILD2 includes events with event type = BUILD1 r BUILD2. 11
Filter Mask Area and Surce subscriptin filters can include a mask t allw a range f values. The mask can include wildcard characters (*,?, ) t match multiple values. See Filter Masks fr mre infrmatin n mask syntax and rules. 12
Detecting alarm/cnditin active Once a subscriptin and subscriptin filter have been cnfigured, an OPC A&E client can start receiving events. After specifying a subscriptin filter that nly returns alarm/cnditin events, events may arrive due t: A Cnditin ging active A Cnditin changing subcnditins (e.g. HI t HIHI) A Cnditin being Acknwledged A Cnditin ging inactive In OPC A&E clients such as TpView, the user may nly be interested in events where a cnditin becmes active (change int alarm frm inactive state) r a subcnditin has changed (e.g. alarm remains active and subcnditin changes frm HI t HIHI). TpView fr OPCA&E allws the user t perfrm additin filtering f incming events based n all relevant fields f an OPC A&E event. This additinal filter, cnfigured as part f the Events Tag filter, allws the user t detect alarm/cnditin events. The fllwing cnfiguratin f the Events Tag filter shuld detect alarm/cnditin events. * Yu shuld view the events f yur OPC A&E subscriptin t verify the States and Changed fields f the desired events. Cnfigure the OPC A&E subscriptin filter event type = cnditin (and ptinally severity, categry, area, and surce) Once events are received, check fr the fllwing event fields by cnfiguring the Events Tag event filter: Event type: Cnditin (shuld be true due t the subscriptin filter) New state: Active (the state f the cnditin is currently active) Changed: Subcnditin (a subcnditin just changed) In mst OPC A&E Servers the subcnditin will change fr new alarms (Active state just changed) and subcnditin changes (e.g. HI t HIHI) Active (the active state just changed) This setting is ptinal and can be used if yu are nly interested in new alarms and nt subcnditin changes. In mst OPC A&E Servers the Active state will change when a new alarm ccurs. 13
Filter Masks Filter masks are supprted in the OPC A&E subscriptin filter. Characters in mask string:? Any single character. * Zer r mre characters. # Any single digit (0-9). [charlist] Any single character in charlist. [!charlist] Any single character nt in charlist. A grup f ne r mre characters (charlist) enclsed in brackets ([ ]) can be used t match any single character and can include almst any character cde, including digits. Nte: T match the special characters left bracket ([), questin mark (?), number sign (#), and asterisk (*), enclse them in brackets. The right bracket (]) can't be used within a grup t match itself, but it can be used utside a grup as an individual character. By using a hyphen (-) t separate the upper and lwer bunds f the range, charlist can specify a range f characters. Fr example, [A-Z] results in a match if the crrespnding character psitin in string cntains any uppercase letters in the range A-Z. Multiple ranges are included within the brackets withut delimiters. Other imprtant rules fr pattern matching include the fllwing: An exclamatin pint (!) at the beginning f charlist means that a match is made if any character except the characters in charlist is fund in the string. When used utside brackets, the exclamatin pint matches itself. A hyphen (-) can appear either at the beginning (after an exclamatin pint if ne is used) r at the end f charlist t match itself. In any ther lcatin, the hyphen is used t identify a range f characters. When a range f characters is specified, they must appear in ascending srt rder (frm lwest t highest). [A-Z] is a valid pattern, but [Z-A] is nt. The character sequence [] is cnsidered a zer-length string ("") 14