How Event Periods Transform Data into Information

Let’s take the Filler 1 Electricity (kWh) totalizer example a little further. For Filler 1, the Tag Historian is storing data related to the Filler’s current product run. The detailed data relating to the Product is very useful in terms of adding additional context to the information we “lift” out of the Tag Historian.


Flow understands the start and end of event periods.  In this example, Flow starts an event when the value of the Product changes from 0 to a positive number.  Flow ends the event when the value of the Product goes back to 0.  Flow then “overlays” the event period onto the kWh detail and calculates how many kWh were used during that production run:

14027.9(00:51:43)– 14079.8(09:49:14)= 51.9 kWh

By repeating this process and mapping the Product to a reportable description, a simple summary report of the kWh used per production run, per product can be produced as follows:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request