Depending on the settings chosen by the system administrator, date fields may be displayed with associated time fields. If this is the case, the time fields include a time zone field. All times are saved in the database using Coordinated Universal Time (UTC), formerly known as Greenwich Mean Time (GMT), which is the current time at 0º longitude. This allows users in various time zones to log and view events accurately and easily.
For example, if an incident is created in Tucson, Arizona and later referenced in Kuala Lumpur, Malaysia, the 15 hour time difference could cause confusion. The incident is created at 2:38 PM on March 9, 2017 in Tucson, Arizona with an occurrence date of March 8, 2017 - 10:30 PM. These times are saved into the database as "2017-03-09 21:38" and "2017-03-09 05:30" respectively. Since Tucson, Arizona is in time zone -7, seven hours have been added to each date/time to get the UTC time. You can see that this changed the date as well as the time of the occurrence date. When redisplayed in Tucson, Arizona, the date/times are adjusted by subtracting seven hours.
If someone in Tucson, Arizona ran a report to find this incident, they could search for an occurrence date of March 8, 2017 with times between 10:00 PM and 11:00 PM. However, if someone in Kuala Lumpur, Malaysia ran the same search, they would get results that do not include this incident because their local time is in time zone +8. They could get the desired result by simply setting the occurrence date time zone for the search to Tucson, Arizona's -7 time zone.
If the user in Kuala Lumpur were then to edit the incident, because all information is saved as UTC, the information would be just as easy to find again in Tucson, Arizona.
Your default time zone is set by the system administrator. You can change your time zone by choosing Options > Settings > User Information.
© 2006-2018. HBM Prenscia Inc. ALL RIGHTS RESERVED.