Maximo Open Forum

 View Only
  • 1.  Maximo Application Utilization Report

    Posted 08-08-2020 08:23
    Dear Experts,

        I have been trying one report which gives me the application wise utilization per day. But still no luck.
        I mean , the report should give me the total no of record created, updated and workflow routed per application and how many user has  access that application on a particular day.

    Please help me on how to get this report. Is there any out of box report available ?

    Thanks
    Alok
    #Administration
    #EverythingMaximo

    ------------------------------
    Alok Pattnaik
    Praxis Solutions
    ------------------------------


  • 2.  RE: Maximo Application Utilization Report

    Posted 08-09-2020 12:26

    Unfortunately most of the metrics you're looking for aren't easy to do in Maximo. Maximo doesn't track when a user access an application out of the box. And certain records, such as actual labor (LABTRANS) could be created in many different applications (Work Order Tracking, Quick Reporting, Service Request, Labor Reporting, Incidents, etc.) without any indicator of which application. Even which records have been updated isn't always possible out of box, as not all objects have a changedate attribute (or similar). For example, ITEM has no changeby/changedate attributes on it so unless someone changes the status on it or you try and track the rowstamp on these tables, there's no way to identify what has changed. And even if you handle that, you want to be able to track it per day, which means that you would need to keep historical audits of which records were modified daily because a subsequent change on another day would modify the changedate.

    The first step is figuring out which objects you really need this functionality on and ensure you have a way to report against it. If you need to be able to retroactively report (IE what records were modified on Monday), then determine how you are going to audit the records modified each day. There is a concept of e-audit in Maximo, but its purpose is for when critical attributes are modified. If you turn e-audit on every attribute on an object (especially one used often like WORKORDER) that will cause your audit table to grow out of control and drastically increase your database storage and reduce performance of the report to where it will eventually be unusable. You're most likely better off creating custom objects to track this (keeping it to just the smallest data points you need) to minimize storage requirements, like the unique identifier, table name, date modified, etc.

    If you need to track user utilization of an application, consider building a custom bean class where you can log the user and the application. You would need to do this for each application you want to track, so again you would want to restrict it to only the applications you need to track. Or you could investigate doing database inserts (can't use MBOs as you can't call a save) on a MBO initialize automation script, but realize that event fires a lot and will add overhead slowing everyone's performance in your Maximo application. For example, if you have a result set on your start center or if you make a REST API request to Maximo that initialize event will still have to fire on each record and in those cases, won't have an application reference.

    While I understand how these data points can be useful to get a basic understanding of how people use the system, it won't help with licensing (because entitled access matters, not necessarily what they utilize). So there has to be other organization value that outweighs the time spent developing and supporting this, the increases in costs to store this data (including in time it takes to potentially recover in a disaster), etc. And at least for most organizations that isn't there. 



    ------------------------------
    Steven Shull
    Projetech
    ------------------------------