BackStaff works as a complement for different types of plant software. A handy one is the Historian application and among these Ignition Tag Historian is a prevalent one. BackStaff can integrate with Ignition Tag Historian to
- Create indicators or event
- Show time trends
BackStaff Configuration for communication with Ignition Historian
The first step consists of creating a database connection, similar to the next example
Do not forget to test the connection, to validate the server name or IP address, as well as the user and password.
Query to pull data from Ignition Historian
At the end of this post, there is a stored procedure that retrieves the values of the different variables or tags within the Historian. This stored procedures already considers that the Tag Historian splits the information between different tables, uses a Unix type UTC stamp.
- ‘Avg’: Returns the average value
- ‘StdDev’: Returns the standard deviation
- ‘Min’: Returns the minimum
- ‘Max’: Returns the maximum
- ‘None’: Returns all the values in the interval with the time stamps and quality for each one
This query asks for the average value of the tag refrigeration/tower1/fanspeed between 2018-06-01 00:00:00 and 2018-07-07 00:00:00 CST with 1 second separation between values.
Based on this we can create an indicator for the average fan speed for the last 24 hours,
and those can be seen as part of a scorecard
Trends based on Ignition Historian Data
BackStaff is capable of storing in its database the information that reads from the Historian database. Nonetheless, it would be redundant information, so BackStaff is capable of doing trends based on queries from other databases.
For getting the data for the BackStaff trend, it is necessary to include the historical query into the IPGParametros table in the BackStaff IPGIndicadores table, for the field HISTORIAN-QUERY. The proper query is
BackStaff integration with Ignition Historian is pretty straightforward and can be ready in less than one hour.
Stored Procedure Code