When we move more towards a decentralized field service organization, with a centralized administration team, it becomes more difficult to handle the hours for different purposes. So for example a technician recording some working hours on site, local time being 08:00 - 12:00 but the centralized office is in a different time-zone (plus 3 hours) then the output from ServiceMax will display as 11:00 - 15:00. Although the duration will be the same it's sometimes important to have the times correct also as we might well share some reports with the customer. For example it's sometimes important for us to send the customer a summary of works, which will be compiled by the centralized admin office and sent to the customer along with an invoice or request for invoice adjustment but any report generated from the centralized office will contain hours 3 hours different from what actually happened in the customers time zone. We try to also be as efficient as possible and capture hours for cost collection, billing and in some cases also for payroll, however the time zone effect can the correct outcome, especially if having hour (time) dependent billing or payroll conditions.
What is the underlying problem do you intend to solve with this idea?
Quality and efficiency
How is the problem being addressed today, if at all?
We have actually only just recently ran into this issue and can only suggest users make some manual changes and/or change their own time zone to mach that of the time zone the actual work was conducted in.