This is related to the Asset Rollup process. Today, this requires running a report in Maximo called the Maintenance Cost Rollup Update report which is run from the Asset application. It's important that you choose the Update version or execute the Update version after running the Maintenance Cost Rollup report because the Maintenance Cost Rollup will provide a summary but not execute the updates to the database.
I would recommend trying this in a non-production environment first and running it as a scheduled support during off hours. This is because this report can take a while to run and put a load on the database system if it hasn't been run in a while. I'd also consider disabling the REPORTLOCKRELEASE cron task or extending the LOCKINTERVALINMINUTES parameter to a larger number. If a scheduled report doesn't complete in the defined threshold here (defaults to 15 minutes), Maximo will start running the report again (and again) after that threshold has been exceeded.
The Maximo team is working on a redesigned process for the Asset Rollup that doesn't depend on a report and significantly improve the performance of the process (RFE:
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=25837). There are a few things to be aware of that the new solution still won't address (at least, initially) that may impact your business.
1) Rollups will only rollup to assets. If a transaction references a Location for example, that transaction will never rollup
2) Rollups will only occur on WO based transactions. SRs, POs, etc. can generate transactions that won't get rolled up today
3) Rollups will only occur when WO are closed today. If your users don't close WOs (leave them in COMP for example) they will never roll up
4) Asset costs are based on the main asset on the WO. If you do not associate an asset on the WO or want the costs to be distributed across assets (such as MULTIASSETLOCCI entries) that is not possible.
There are additional things to be aware of but at a high level, those are the critical things.
------------------------------
Steven Shull
------------------------------