Email notification via SMTP
Email remains one of the simplest and most common notification and alerting methods. The Email notification Plug-in works with the simple SMTP protocol and thus has easy access to almost any mail system. With the Email notification Plug-in you can create your own email templates for various alerting functions and fill them at precisely definable times with data from connected systems such as OPC UA, SAP, SQL databases, REST, MQTT and many more.
The graphical designer allows you to project your own email alerting according to application-specific requirements (see example).
Achieve More with Combined Systemen
In production, systems work with important data – data that is vital for the production value chain. Easy connectivity, which is established with the OPC Router, seaks to get the right data to the right people just in time, making production a value-rich experience by optimizing data transfers.
Industry 4.0 via Email
Industry 4.0 relies on fast and automated data exchange. The Email plug-in keeps human communication in focus and ensures optimized information distribution.
About the OPC Router
That’s how easy it is.
The transfer object of the Email notification plug-in offers individual email template configurations. When a transfer is prompted the current data is transferred and sent via SMTP.
Text and variables
The text of the email notification can be provided with any placed variables. The variables are described with values during the transfer from outside.
consignees, consignor, subject
The fields consignees, consignor and subject are available as standard data fields for each email and can be freely described with data. Dynamic emails are sent for each application case.
The Email notification plug-in does not have trigger functions of its own but uses the standard trigger function the OPC Router offers.
The Email notification plug-in reads out all variables contained in the email template.
The variables are automatically configured as data fields inside the transfer object and can be written to with any given value of various data types. During the writing process an automatic conversion occurs: The data is converted into a “string” (i.e. sequence of characters).
In this example, data is loaded from OPC UA with the OPC UA Client Plug-in and from a Microsoft SQL database with the Microsoft SQL Plug-in. They are supplemented by variables, constants and a file as an attachment. The file for the attachment is loaded with the script function from the OPC Router Basic Plug-in. All data is finally written into the email template and the email for the alert is created. In this example, the email is sent when an OPC trigger is triggered, which checks the data point of a PLC for an alarm condition.
How do Transfer Objects, Trigger and Browsing work?
The connections the OPC Router establishes between systems can be addressed with the core functions of the OPC Router. Depending on the nature of the respective plug-in, functions vary, which is due to the functional scope of the respective connceted systems.
Sources and Destinations
Transfer objects are the sources and destinations inside the OPC Router. They contain data fields with read and write functions. Depending on the respective interconnected system, the possible configuration scope of sources and destinations may vary.
Homegeinity on the Outside – Heterogeinity on the Inside
Triggers determine execution time of data connections. Various Triggers can be used for these connectiongs, independent of transfer object type. Within each connection, several triggers can be used together via AND/OR-connections.
Searching and Finding Data Fields
Easy browsing also makes data field configuration easy when establishing transfer objects in order to establish the respective interface connection. The browsing mechanisms may vary, depending on the system and its available plug-in.
Reading out Structures
Many plug-ins that are available for the OPC Router offer easy search and selection tools for quick identification of respective data fields without the need for specific knowledge about inherent subsystems. The user can easily browse through the data. Data source structures may vary according to the specification of each respective plug-in.