# Prime Time on Different Time Zones

Open iT distinguishes system resource utilization time using Prime Time configuration. It specifically categorizes configured system resource time into prime or non-prime.

# Cause of Deprecation

The accuracy of the Prime Time classification is inefficient since it does not support concurrency calculations for clients or hosts in various time zones.

# Effects of Deprecation

The classification is still present by reporting various supporting data types, but its value will be undef or <empty> in the report.

# Workaround

The classification could still be configured and enabled by modifying specific filters in the server. However, this is not guaranteed to show valid and correct information when used in different time zones.

# End of Life

Starting Open iT version 6.5.1.14.

In Open iT version 9.6.56 (hotfix), activation of Prime Time mapping is supported in LicenseEvents and LicenseEvents2 data types. This is to cater, and ONLY APPLICABLE to, client setups connected to a server with the same time zones. This is DISABLED by default to avoid data inconsistencies in different time zones.