Time localization ensures that the time on the Web LCT is correctly displayed when the Web LCT crosses time zones and Daylight Saving Time (DST).
Universal Time Coordinated (UTC) was formerly called the Greenwich Mean Time (GMT). The UTC is an absolute time and is used in most communications standards.
All data in the Web LCT and NEs are stored based on the UTC. The time on the Web LCT client is displayed in two modes, which are by client local time, and by server local time. The local time displayed on the Web LCT client varies with the different time display modes.
Time zone: The world is split into 24 time zones, each of which spans 15 longitudinal bands. The time offset between adjacent time zones is one hour.
In the time localization policy, if you select the local time of the NE as the standard time, the Web LCT needs to transit the display time of the NE by converting UTC to the local time of the time zone where the NE is located.
DST also known as summer time, is a widely used system of time. During the "longer" days of spring and summer, DST saves energy and fully uses the daylight. Some countries pass legislation to set the clock forward one hour in the spring and revert the clock by one hour in the winter.
The time when data is generated in the Web LCT, is irrelevant to DST. But, when the Web LCT transits the display of history data, the Web LCT may need to implement DST transition for some regions. For example, the Web LCT generated a time stamp "A" for an operation in June. The time stamp "A" is held in the UTC format. Consider that the time zone observes DST and in June the time stamp "A" is adjusted according to DST. When DST ends in October, the time stamp "A" cannot be transited by simply adding or subtracting the time zone, without considering the DST.