Reasons to Upgrade to Maximo Asset Management Version 7
Mary Gorczynski 1100006B54 email@example.com | | Tags:  ibmontwitter service-management eam ibmsoftware asset-management maximo tivoli software
3 Comments | 8,135 Visits
Today's blog comes to us from David Havican.
Hello everyone, it’s been a while since I have posted a blog entry. Sorry about that, we’ve been really busy working on the upcoming release. As I was trying to think of a topic for this week’s Maximo Monday Blog, I got a call from someone in Tivoli support asking me how complicated it would be to customize Maximo to prevent their users from entering actual labor transactions in the future. What this support person did not realize is that in version 7 of Maximo, there was a feature added that allows a client to specify a ‘future tolerance’ for actual labor transactions. No customization required at all!
This got me thinking. I figured there were a number of new enhancements in version 7 of Maximo that people just never knew about. I thought it would also be great to highlight a few of them here to let any clients out there who have not yet upgraded to version 7 or who are new to version 7 know what’s available in 7. So I picked three especially nice enhancements that I want to give a brief overview of. Let’s start with the one I just mentioned…
1. Future Tolerance for Labor Reporting
Imagine this scenario:
A utility worker will be driving out 80 miles to fix a switching station. Instead of driving back to the office afterward so he can enter his actual time entries, he will just drive straight home afterward. He needs to enter the time for this activity before he leaves. To do this, Maximo must allow him to enter actual labor transaction that have a future date and time.
We have heard from some clients that want to prevent this absolutely and other clients who would like to allow some leeway, but prevent entry that is too far out in the future.
A new MAXVAR called LABTRANSTOLERANCE was added in version 7 of Maximo that holds the number of hours into the future that Labor Transactions will be allowed.
br />This value can be set in the Organizations app under Labor Options. Out of the box, this value is set to 0 which means that there is no tolerance for any future entries. To allow labor entries in the future, just modify this value to a certain number of hours. A common setting might be something like 12 hours. It gives the user a little leeway, but would prevent someone from accidentally entering a time with a date that is days or even years in the future. This value can be set as high as you like.
2. Multiple Assets and Locations on Work Orders:
This is an enhancement that has been asked for by more clients than I can count. In version 7 of Maximo, you can now define a list of assets or locations on a single work order record without the need to create a work order hierarchy. We still maintained the concept of the ‘primary’ asset and location on a work order, but you can now add as many assets and locations as you like. You can even add assets and locations from different sites together. You can also have Routes that are applied to the work order create entries in this new table instead of creating child work orders or tasks.
This ‘multi table’ as I like to call it, is available on the main work order page of the Work Order Tracking application. By default it is minimized, but can be expanded in the UI.
br />The Move/Modify Asset functionality also uses this new table now which helps reduce the effort of defining your ‘mass moves’ of assets.
The one thing we were not able to also include is distributed costs. This will have to wait for the next major release. For now, the table can hold a list of assets and locations, but the work order will still only have a single GL to charge costs to.
3. Keep Task Status History:
Most clients are very concerned with the status of their work orders, but not always with the status of the tasks on those work orders, especially the history of status changes at the task level. Every time a work order has its status changed, Maximo also updates the status on the tasks and we write status history records for all of these. This ends up being a lot of updates to the database that may not even be useful information for a client. If you are not concerned with the status history of your tasks, you can improve the performance of Maximo and limit the number of status history records in your database to just the ones you care about with this new feature.
Clients can choose to turn this feature on or off. The settings for this are unfortunately not in the UI in version 7. The good news, is that we did add the ability to turn it on and off in the UI in our upcoming release. But for now, you can turn this feature on/off as follows…
There are two places this can be turned on and off. You can set this for each individual Work Type as well as for work orders that have a null Work Type.
A new MAXVAR called KEEPTASKSTATUSHIST turns this feature on or off for work orders with a null Work Type. The WORKTYPE table also has a new field called KEEPTASKSTATUSHIST where you turn it on and off at the Work Type level.
Out of the box, these are all set to 1 (Yes) – this means that all of the status change history will be recorded. If you want to change these settings so that Maximo does not save the task’s status history, execute the following SQL statements against the database:
This statement sets it for all work orders that do not have a Work Type defined:
update maxvars set varvalue = 0 where varname = 'KEEPTASKSTATUSHIST'
This statement sets it for all work orders that have a Work Type defined:
update worktype set keeptaskstatushist = 0
If you just want to set it for a specific Work Type, you can specify a specific
Work Type. The following example would set it for tasks with a Work Type of ‘PM’:
update worktype set keeptaskstatushist = 0 where worktype = 'PM'
Remember, 0 means that no task status history is saved, 1 means that it works like it used to and it WILL continue to save the status history.
Also keep in mind the tasks will still have status fields that will be maintained accurately, but the WOSTATUS records will become optional. So you can see the current status of any task, you just cannot look at the history of status changes made at the task level. None of this will change the status history of the main Work Order records.
Please let me know if there are other features you would like me to explain by commenting on this blog entry.