An eventful day

Creating Historian events tags was the first "cool" thing i learned about the Wonderware Historian Server.

Historian event tags belong to what the suite currently now calls "classic event system". This tags can be configured to be trigger when any other analog or discrete tag has a particular value. When the event tag triggers a set of actions can occur:

• None
• Generic SQL
• Snapshot
• Email
• Deadband
• Summary

With Generic SQL the possibilities become limitless! When Generic SQL is chosen a button called Templates popup, push it and select send an email message, fixed test.

You know can see how we can actually use the variables @EventTagName and @EventTime to this information passed through a script.

If you add a linked server to the SQL where historian exists now you can connect historian with any given database.

A couple of things that you will need to keep in mind:

•  There is a limit amount of characters you can use with the Generic SQL option (you can overcome this by using store procedures)
• You will need to setup security correctly for functions, tables and or store procedures used by the event system. Wonderware events will run with a user created with the Wonderware historian installation
• The event system is not "real time", it will run on a scan basis. The scan works like a SQL Job so apply similar constrains to the scan time.