IBM Support

Hours field not accepting correct downtime value

Technical Blog Post


Hours field not accepting correct downtime value


Have you tried report downtime in Workorder Tracking application and the hours field was not accepting the correct downtime or not displaying the correct downtime?


Today I have a tip about that.

Unlike Person records, Asset records do not contain a field to specify the Asset's time zone. So, when the Asset's Calendar and Shift are evaluated to calculate downtime, that evaluation must assume that the Calendar and Shift have been entered to describe the Asset's available hours in the database server's time zone. For example, assume that the application server and database server are both in UTC+5:30 (India), and the user is in UTC-4:00 (Eastern US). Maximo does not know where the Asset is. It could be with the user, but this is not guaranteed: a users might report downtime for an Asset on behalf of users in a different time zone, or the user may report downtime on an Asset in a different time zone which he accesses remotely.


So, when a time is entered into the downtime dialog, Maximo assumes that the user has entered times from their own time zone. The time is compared to the Asset's availability as specified in the Asset's Calendar and Shift which Maximo assumes indicates the available hours in the database server's time zone. In short, the behavior observed by the client is correct.


The expected usage of Maximo, which has been successful, is to create Calendar and Shift records for Assets which take into account the difference in time zone between the Asset's location and the database server's. So, again from my example, if the user in the Eastern US is entering time for an Asset at their location which runs from 7:00 AM - 3:00 PM EST, you should apply a Shift to that Asset which runs from 4:30 PM - 12:30 AM. Then, when the user enters downtime from 7:00 AM - 9:00 AM in his time zone, the calculation will correctly return 2 hours. Entering 3:00 PM - 5:00 PM will result in a downtime calculation of 0 hours, because the Asset is offline according to the Shift. On the other hand, if the Asset is in a different time zone, on the Pacific coast of the US (UTC-7:00), then you should give the Asset a Shift from 7:30 PM - 3:30 AM, and still enter the downtime in their own time zone, EST.


That's all folks!

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]