Technical Blog Post
From the Maximo Support Desk - A Few Notes On Asset Year To Date Costs
A few quick notes on the "annual" concerns about the Year To Date Costs field in the Assets application...
- From the Assets application, display the record whose costs you want to reset.
- From the Select Action menu, select Zero Asset Costs.
- In the Zero Asset Costs window, select either of the following options:
- Select the Zero Year to Date Costs check box, to zero all costs to date within the current year.
- Select the Zero Total Costs check box, to zero all costs for the asset.
- Click OK.
- Since the asset resides at the site level, the YTD Cost field only reflect costs incurred at the Asset's current site. In other words, the value will reflect the aggregate cost up to this point, at this Site.
- The YTD Cost field must be manually zeroed out by the user, via Select Action > "Zero Asset Costs?". There is not an automatic, or otherwise installed functionality which automatically performs YTD Cost calculations based on the current date
- To make use of the Asset YTD Costs field, you must run the Maintenance Cost Rollup report. Its primary function is to update the Asset Year to Date & Total Costs fields on the Asset records. This report compiles Labor charges to the Assets (either charged directly to the Asset or to a Workorder assigned to that Asset), Material issues (either Inventory issues or items purchased directly against the Workorder), Service Charges, and Tool charges. Again, this is not run automatically in an out-of-the-box installation, it must be run manually.
Also, I would suggest running the Maintenance Cost Rollup report during an off-peak usage time in your environment, especially if you've never run it before, since it will analyze all transactions up to the run date. Hopefully you'll find this information timely.
Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community. For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer