NOTE: Bazefield Portal 8.6.1 and newer releases can follow asset time zones. This will impact the explanation here
Understanding the Data Export application's options and exported data's timestamps. This article describes how the application handles different time zones at the buffer layer and end user's own computer (exporting data from Bazefield's Portal).
The local time zone is used in certain other applications like the Alarm Log to display a local time view of the application.
Data Export Example
Note: If an aggregate is used, Bazefield displays "Hour Beginning" values. For instance, data values from a 1 hour average aggregate type displays a timestamp of 00:00:00 for data from 00:00:00 to 00:59:59.
Comparing the timestamp at the very beginning of the export to the beginning of your requested Data Export 'From" timeframe from the Portal can be helpful/
Choosing a "From" time in the Data Export App will take the time from your own machine and (with UTC disabled) pulls out data that is consistent with the server's timezone (a server core function).
- The User's computer's timezone affects the displayed 'time periods' seen and used in the portal.
- ! The data engine itself stores data in UTC time zone (historian).
- You may prefer to export data in the UTC format to easily make comparisons or troubleshoot issues.
- The core server functions operate in the data engine servers timezone which, in this example, is Mountain time.