New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Resource Advisor - Performance Analytics Forum
Showing results for 
Search instead for 
Did you mean: 
Lt. Commander

For PAM all data streams are interval ending

As a matter of fact, only the Calculation Engine, with its [[TimestampPosition=>IntervalBeginning]] and [[TimestampPosition=>IntervalEnding]] directives makes the distinction. PAM and EEM do not have any concept of IntervalBeginning or IntervalEnding.

So, if your create a new calculated measurement, and in the expression that defines it you add a [[TimestampPosition=>IntervalBeginning]] directive, for example

Using a data series like:

7/20/2018 0:00           100

7/20/2018 1:00           200

7/20/2018 2:00           300

7/20/2018 3:00           400


when displaying this series in Trend Analysis you will get

Notice PAM is considering the individual values as IntervalEnding when displaying this series as 'raw data', in this case hourly

However, if you were to plot this data By Day (instead of By Hour as the previous screenshot) you will get

These values are obtained aggregating the hourly values as IntervalBeginning as expected given the directive that creates this data. For comparison, if the data would have been aggregated with IntervalEnding then the results would have been



So, if aggregation is applied, the Trend Analysis displays the results correctly, while 'raw data' (i.e. when no there is no aggregation) is displayed as IntervalEnding

Note: For this example, the series that has been used starts with a timestamp of  7/20/2018 0:00 with the value 100 and increases hourly by 100, so the last timestamp of this series 7/25/2018 0:00 has a value of 12100