Differences

This shows you the differences between two versions of the page.

--- alarm_analysis.assettimezone:asset_time_zone [2020/07/15 16:41] – [Viewing Alarm Analysis data in other Apps] su
+++ alarm_analysis.assettimezone:asset_time_zone [2023/12/29 13:42] (current) – su
@@ Line 1: / Line 1: @@
-====== Alarm Analysis and Asset Time-Zone ======
+====== Alarm Analysis and Asset Timezone ======
-Most apps on the Industrial App Store assume you want to time-series data in your local time.  This will be derived from the regional settings of the PC, phone or table your accessing the App Store from.
+Most apps on the Industrial App Store assume you want to view time-series data in your local time.  This will be derived from the regional settings of the PC, phone or tablet you access the App Store from.
-Alarm Analysis is a little different however, in that it presents results in the time of the asset and does not assume you will necessarily be accessing the tool from the same region as asset exists.
+Alarm Analysis is a little different however, in that you can override this option and set an explicit timezone. This would be useful if, for example, you were viewing an asset in Perth, Australia from an office in Aberdeen, Scotland and wished to interrogate and view the data as if you were in the control room.
-For example, if you were in the UK viewing an Alarm Analysis Report for an asset in Perth, Australia, a measurement such as the average Alarm Count for 9-10am would refer to the time on the asset.
+To specify an explicit Asset Timezone, select the "cog" configuration icon...
-Similarly, when you select a reporting date-range, it is assumed to be in the asset's local time.
+{{ :alarm_analysis:aatimezone01.png?direct&400 |}}
-===== Configuration =====
+then select an Asset Timezone.
-To configure an Asset Time-Zone, the data source administrator must enter an Asset Time on the Alarm Analysis data source.
+{{ :alarm_analysis:aatimezone02.png?direct&400 |}}
-Users can override this in Alarm Analysis user settings.
+Now all dates are interpreted and presented for that timezone:
+  * Date selectors are interpreted as being in Australian Western Standard Time
+  * Day Counts are for 00:00.00 - 23:59.59 ((Day counts are actually driven for 24hr periods from a starting point. For example, if you were to specify a report starting from 9:00am, the day counts would actually be for consecutive 09:00.00 - 08:59.59 (//next day//) periods)) Australian Western Standard Time
+  * The Sequence of Events View shows all time-stamps in Australian Western Standard Time
+  * etc...
-===== Viewing Alarm Analysis data in other Apps =====
-If you were to view an Alarm Analysis data source in tools such as Facit or SoE Explorer, event time-stamps are presented in the users local time (not asset time).
-If you were to view an Alarm Analysis KPI tag such as "Daily Alarm Count" in Gestalt Trend, the count would be for a 00:00:00-23:59:59 period in the asset's time. But note this value is aggregated on the fly and will only return a complete result if the Gestalt time period emcompasses a full day, and note Gestalt time is local time (not asset time!)