Last Updated on November 19, 2022 by maximosecrets
Good morning and welcome to Maximo Bite Size, a podcast on the functionality of Maximo Manage. Today is the eleventh episode in the series on Asset Management and we will be discussing Asset Downtime.
Asset Downtime is one of those features which you will find in the Assets application but not in the Locations application. You will also find that you can report downtime from the Work Order Tracking and Quick Reporting applications. The actions and dialogs are almost the same as they are in the Assets application, with small differences.
In the Assets application at the bottom left corner of the main Asset tab is a Downtime section with three fields which are all read-only, an indicator of the assets up/down status, the status date when this change occurred, and the total downtime that has been accumulated by the asset.
The Report Downtime action is used to either Change Status or to Report Downtime. The Change Status radio button is used to report downtime in real time as the asset status is changed from up to down or vice versa. You can modify the status date to reflect when the change occurred, it could have been earlier in the day. You can change the status date to a later date/time than time now if you knew the asset was going to go down, or back up at a specific time. When you are changing the status, or you might think of it more as changing the asset state, you can also enter a downtime code.
By changing the status, you may find that the downtime hours have not been incremented. For the downtime hours to be calculated automatically the asset needs a calendar and shift that has a work date at the date and time when the status changes are being made. The calculation is made as the asset status is set to up. The hours will also be calculated if there is no calendar, but if the asset has a calendar but no shift then Maximo assumes the asset is not operational and will not calculate downtime hours.
The Report Downtime radio button is used to report downtime after the downtime event has occurred, think of this like entering the downtime period with start date/time and end date/time at the same time. You are reporting the downtime that may have resulted in a work order being created, or you may be reporting the downtime that occurred while work was being performed.
The Manage Downtime History action allows you to see when the asset state was changed and the downtime reporting that has been made either through the Assets application or via a work order. For each record there is a downtime code at the start, when the status is set to down, and the downtime code at the end when the status returns to an up state, the two downtime codes could be different.
The Manage Downtime History dialog is looking at two records of the ASSETSTATUS table. All the fields are modifiable in this dialog, and you will find that there are some validations to ensure the Start Date cannot be later than the End Date or that one records dates cannot overlap another set of dates for the same asset. This is where you can adjust the Downtime Hours and whether it was Operational or Non-Operational time.
In the work order based applications the Manage Downtime History dialog is a little different in that it only shows the downtime records for the work order. There could be multiple records, for example a period marked as Operational and a period marked as Non-Operational.
In the A structural element of a Maximo database which is used for data sharing and is often aligned to a legal entity of an organisation. More application and Work Order Options and the dialog for Work Type you can determine whether a prompt for downtime should occur for each work type. This is a message to inform you if the asset is still down when completing or closing the work order. If you want the message to always be displayed including for work orders that have no work type, then check the field ‘Display Downtime Report Prompt upon WO Completion for Asset in a ‘Down’ Status?’ which you will find under Other Organization Options. At the top of this dialog, you can also determine how the Downtime Start Date should be derived, from the Reported Date, Actual Start Date, or None. This sets the default for the additional fields that you see in the Report Downtime dialog in the Work Order Tracking and Quick Reporting applications.
In the work order based applications you have the same two actions Report Downtime and Manage Downtime History. In the Report Downtime dialog there is an additional section called Start Date Default with a radio button for Reported Date, Actual Start Date, or None. As the section name suggests the setting of this field determines how the Start Date is derived when the Report Downtime radio button is being used. None means that the Start Date is blank. The End Date is set to the current date/time but can be modified and the Hours will be recalculated.
There is a System Property mxe.asset.assetInUserTimeZone, which if set will assume the asset exists in the user’s time zone, if this is not set it will use the server’s time zone. When Maximo reviews the Start Date and End Dates against the calendar and shift on the asset, then you really want the calculation of hours to be based on the time zone of the user who entered the downtime report or who marked the asset as being up, which calculates the downtime period. If you work across multiple time zones then the property should be set to 1, its default is 0 to preserve how it worked.
I hope you enjoyed this podcast episode and I look forward to seeing you on the next episode when we will review Failure Codes and Failure Reporting.
The music is called Busy City from the group called TrackTribe, please check them out on TrackTribe.Com, all one word.
Until another time, goodbye.