Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

All Date fields are in the Machine’s Time Zone

Each machine in your system is configured with a time zone.

All the date and time fields (e.g., [Dim Dates.Calendar DateTime]) you see in analytics are in that machine’s time zone.

Analytics Portal also stores the Universal time for all machines behind the scenes and uses that to allow analysis across time zones. This means when you ask for “Last 24 hours” from [Dim Recent Shifts], your results will include the last 24 hours of universal time regardless of time zone.

For example,

 Two time zones and Last 24 Hours of Shifts

Plant A - New York (UTC-4)

Plant B - San Jose (UTC-7)

Refreshed at 10:30am New York Time.

The most recent data for New York will be 10am New York Time,

The most recent data for San Jose will be 7am New York Time.

So when you use [Dim Recent Shifts] for “Last 24 hours” you will get the following results:

  • Plant A machines - the displayed data will be in the range: 10am yesterday to 10am today

  • Plant B machines - the displayed data will be in the range: 7am yesterday to 7am today

A free, web-based visualization tool to help with these conversions is available here: https://www.worldtimebuddy.com/

Troubleshooting

If you are seeing unexpected times, and the minutes are correct but your hours are incorrect, your machines have a time zone issue. Please reach out to your customer success contact. The most likely cause is that your machines have not been explicitly assigned time zones.

  • No labels