Alarm Source Types

Using Event Stream and Tracker objects in the I/O Model tree, alarms and events from OPC servers, Dropzone data sources, Boolean I/O items and scripted events can be reported and archived. Alarms and events produced from different sources are handled and reported by different objects in inmation. The table below summarizes the A&E source types and the corresponding inmation handling object.

Table 1. Alarm and Events Sources and Corresponding Handling Object
A&E Source Handling Object Description Handling Object Icon Placement

OPC A&E and OPC UA Servers

Event Stream

Reports all Alarms and Events from OPC A&E and OPC UA servers according to the relevant OPC specification

icon event stream32

Event Stream objects are created directly beneath the OPC A&E and OPC UA Server Datasource objects in the I/O Model tree.

Alarm Generator

Internal Event Stream

Reports A&E from Alarm Generator objects that generate alarms based on the values of numeric or boolean I/O items (and RedItems).

icon event stream32

Internal Event Stream objects are created directly below the Server/Datasource object that contains the I/O item (+Alarm Generator object)

Scripted Events

Script Event

Reports all A&Es from objects that create Lua scripted A&Es

icon event scripted32

Script Event objects are created beneath Connector objects or lower in the I/O Model tree. Report scripted events from objects on the same hierarchical level or lower

Dropzone Datasource

Event Tracker

Reports all tracking events from dropzone sources and adds them to the Production Calendar Display

icon event tracker32

Event Tracker objects are created beneath the Dropzone datasource that is configured to issue tracking events

OPC A&E Server/Datasource

inmation contains an OPC A&E client and has full connection capability to OPC A&E servers. An overview of the OPC A&E specification, including subscriptions and an explanation of A&E message fields can be found in the OPC Connectivity section. The entire OPC A&E specification can be downloaded at the OPC Foundation website.

Alarms and events originating from an OPC A&E server can be visualized in inmation using the Event Stream object. This object reports all alarm and events messages sent from the OPC A&E server and can be configured to filter messages according to the event type or severity. All alarms and events reported by the Event Stream object can be historized.

OPC UA A&C Events

The system supports OPC UA A&C (Alarms & Conditions) in the OPC UA client. An overview of the OPC UA Events specification, including subscriptions, Event Types and Event Notifiers can be found in the OPC Connectivity UA Events section.

Events originating from an OPC UA server can be viewed in DataStudio by using the Event Stream object and visualized by adding them to an Event View display. The Event Stream object reports all event messages sent from the OPC UA server and can be configured to filter messages by adding objects to the OPC UA A&C filter options. All events reported by the Event Stream object can be historized.

OPC UA Event Type Attributes can be disabled or enabled below OPC UA Datasources to control the information processed by the system.

Alarm Generator

Alarms and events can be generated from other sources other than OPC A&E servers. The Alarm Generator object generates A&E events from data producing items (I/O Items, Red Items) converting them into de facto A&E sources. The A&E messages from Alarm Generator objects take the same form as OPC A&E and can be configured for severity and alarm message. The A&E messages are visualized and historized using the Internal Event Stream. The Alarm Generator supports three generation types: Digital Alarms, Level Alarms and Discrete Value Alarms. Digital Alarms can be configured below boolean items, sending alarms on the rising or the falling edge. Level Alarms can be configured below items producing numeric data and will send alarms when pre-configured limits are crossed. Specific Discrete Value Alarms will be raised whenever the numeric data of the I/O item equals one of the specified values.

Scripted Events

Alarms and events can also be generated from Lua scripts executed by objects in the I/O model tree. inmation provides a Lua function, syslib.setevent, that creates an event with configurable message, severity and timestamp. Scripted events are visualized and historized by the Script Events object (see table above for information about placement of Script Events object).

Dropzone Datasource

Files that are imported into inmation using Dropzone datasources can also be used to generate alarms and events. The Dropzone datasource can be configured to issue tracking events based on the timestamps and information contained in the file or filename. The Event Tracker object visualizes the tracking events issued and adds them to the Production Calendar display.