Move Asset Cost Rollup Report Functionality to Application

The new Maintenance Cost Rollup capability was delivered in Maximo Application Suite 8.5.

Yes please explain where it exists for everybody's benefit.

Hi Kim,

Can you explain where the functionality already exists? I don���t see an Action in the Assets app to do this nor do I see any Cron Task or Escalation to do it.

I wrote a custom SQL procedure a few years ago to do this but would be happy to get rid of it if there is a way to do it within the application.

Thanks.

At the current site, we no longer use the report due to the large database, long runtime which generally quits and never completes. Currently, they are using a stored procedure with updated and efficient SQL that updates the data nightly. Managing cost is very important to the customer, and having an efficient method should be sought.

You know, you can get each asset's true cost this way:

SELECT SUM(nvl(lt.linecost,0) ), SUM(nvl(mut.linecost,0) ), SUM(nvl(srt.linecost,0) )
FROM asset a
LEFT OUTER JOIN (
SELECT siteid, assetnum, NVL(SUM(linecost),0) linecost FROM labtrans
WHERE assetnum IS NOT NULL AND assetnum = :theAsset AND siteid = :theSite
AND transdate BETWEEN TO_DATE(:startDt,'MM/DD/YY') AND TO_DATE(:endDt'MM/DD/YY')
AND linecost != 0 AND linecost IS NOT NULL AND genapprservreceipt = 1
GROUP BY siteid, assetnum) lt ON a.siteid = lt.siteid AND a.assetnum = lt.assetnum
/* then matusetrans, servrectrans */
WHERE a.siteid = :theSite AND a.assetnum = :theAsset;

If instead you run it over assetancestor instead of asset, you get all of the costs of the asset, and its children.

Building this into an asset screen, you can either make it non-persistent, so it changes over time, or persistent and recalculable (I suppose) based on user-input date ranges. I would probably make the non-persistent fields set for YTD, last year, two years prior, etc.

Not that hard.

The original creation of this RFE is over five years old... come on, this didn't make a single dev list in that time? Can we contribute code to solve it, then, so we can have this delivered to the application?

It is simply amazing to me this RFE is still here and not delivered as a simple escalation or CRON task, or even an ORG setting. If Asset Health is so important and cool that it needs marketed as a "new" capability we need things like Asset Criticality Rankings on the ASSET MBO and we need ASSET costs to populate automatically based on system usage. Really, I can't emphasize enough if the Internet of Things is important to IBM in using Maximo as a system for Facilities and Asset Management, then the system needs to do things automatically to show ASSET details that have been traditionally been acquired manually outside or inside the Maximo system.

This is being targeted for a feature pack in 2017.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Asset Management
Product - Maximo Asset Management (MAM)

For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Asset Management
Product - Maximo Asset Management (MAM)

I agree with rbryant "...You should be able to view costs from asset, location, account code segments, date groupings, etc." cost reporting has been a weak spot in Maximo ands has made upper managment question if we should go to another CMM program. IBM needs to deal with this poor report soon. It has eaten up alot of our time with IBM support. Even IBM support help staff knows this is a poor report yet it does not get fixed. Wonder what the logice behind this is??

I agree with rbryant's comments. The report, in it's current form, provides little value in the way of decision making. Effort should be directed at coming up with a better cost reporting strategy. Apart from that, I would agree that, in it's current form, the rollup belongs as an action in the Asset app, not in a report.

I support all the comments above. It would be nice to see the GL Account info rolled up on a sepperate report. Please add this functionality to Maximo

I support moving this functionality to the application. In the earlier versions of Maximo many corporations never ran the report because it would fail. I have never seen it run without some need for modification or special handling.
Also it is extremely important to document the function of updating “Maintenance Costs”. The documentation should be comprehensive detailing what objects and records are used to update the maintenance costs and where they reside. Timing, calculation, query, events, criteria etc.. that impact the function should be identified in the documentation.
I support moving this

I agree that this should happen in the application. It is my opinion though that this should be part of a bigger effort to provide overall budgeting and cost reporting in the application. You should be able to view costs from asset, location, account code segments, date groupings, etc. Once we have the costing approach worked out, then we should be much closer to a real view of costs and the associated details for an asset, not just a summary number.

I agree with Greg's comments above adding that additional functionality would be great it's what our transportation user having been asking for to be able to view these cost from the ui.

I support moving this functionality to the application vs. the report. I also think that it is a bit weak only displaying the LTD and YTD Costs against the asset. In addtion to updating the LTD and YTD costs, I would like to see something similar to the 7.5 Work Order / View Cost functionality where the costs against the asset can be broken down by Labor Hrs, Labor Costs (Internal and External), Materials, Services, etc.

I assume this solution would be enabled via a cron which could either be enabled or disabled. I'm not clear on how the report currently works (which fields get updated) and am concerned that Asset data (fields unclear to me) would 'start changing' upon implementation of this solution without knowing which data is changing, why the data is changing and when the data is being changed. Since we don't currently run the report, we know that the data is not being changed via reporting.