system:inmation supports the OPC A&E standard and provides new functionality to create, handle and historize alarms and events. 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 system:inmation. The table below summarizes the A&E source types and the corresponding system:inmation handling object.
|A&E Source||Handling Object||Description||Handling Object Icon||Placement|
|OPC A&E Server/ Datasource||Event Stream||Reports all Alarms and Events from and OPC A&E server according to the OPC specification||Event Stream objects are created directly beneath the A&E Server/Datasource object in the I/O Model tree. Reports all A&E from the server|
|Alarm Generator||Internal Event Stream||Reports A&E from Alarm Generator objects that generate alarms based on the value of Boolean I/O items||Internal Event Stream objects are created directly below the Server/Datasource object that contains the Boolean data item (+Alarm Generator object)|
|Scripted Events||Script Events||Reports all A&Es from objects that create Lua scripted A&Es||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||Event Tracker objects are created beneath the Dropzone datasource that is configured to issue tracking events|
system: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 subcriptions and an explantion of A&E message fields can be found in the OPC Connectivity section of the inmation Wiki. 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 system: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.
Alarms and events can be generated from other sources other than OPC A&E servers. The Alarm Generator object generates A&E events from numeric data sources 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 object.
Alarms and events can also be generated from Lua scripts executed by objects in the I/O model tree. system:inmation provides a Lua function, inmation.setevent(), that creates an event with configurable message, severity and timestamp. The setevent function can only be implemented in Lua script executing objects that are located underneath the Connector object in the I/O Model tree. See the Lua Scripting section of the inmation Wiki for more details on the setevent function. Scripted events are visualized and historized by the Script Events object (see table above for information about placement of Script Events object).
Files that are imported into system: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.