Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Asset downtime

    Posted 11/27/23 02:35 PM

    Hi All,

    In asset application when you delete a downtime record from Managed downtime history action, system is not recalculating downtime on Total Downtime field.

    ASSET.TOTDOWNTIME

    1. Create a new Asset -> Save

    2. More Actions - > Report Downtime - > Start (yesterday) -> End (now) 

    Total downtime field is updated to 24 hours

    3. More Actions - > Report Downtime - > Start (today 10.00 AM) -> End (today 11.00 AM) 

    Now Total downtime field is updated to 25 hours

    4. Go to - > More Actions - > Manage Downtime History -> Delete the record with 1 hour. Click OK.

    The Total Downtime field is not updated and remains 25 hours.

    Results: The Total Downtime field is not updated and remains 25 hours.

    Can someone help on the issue.

    Thanks in Advance

    Iswarya



    ------------------------------
    Iswarya S
    ------------------------------


  • 2.  RE: Asset downtime

    Posted 12/08/23 10:48 AM

    Hi Iswarya,

    This problem was registered in IBM as APAR IJ25476: ASSET TOTAL DOWNTIME NOT UPDATING AFTER ADJUSTING DOWNTIME HISTORY and it was fixed in Maximo 7.6.1.3. I can confirm that in Maximo 7.6.1.3-IFIX20230117-1942 I can't reproduce that bug.



    ------------------------------
    Bartosz Marchewka
    IBM Maximo Consultant
    AFRY
    ------------------------------



  • 3.  RE: Asset downtime

    Posted 12/08/23 10:49 AM

    Hi Iswarya,

    This problem was registered in IBM as APAR IJ25476: ASSET TOTAL DOWNTIME NOT UPDATING AFTER ADJUSTING DOWNTIME HISTORY and it was fixed in Maximo 7.6.1.3. I can confirm that in Maximo 7.6.1.3-IFIX20230117-1942 I can't reproduce that bug.



    ------------------------------
    Bartosz Marchewka
    IBM Maximo Consultant
    AFRY
    ------------------------------



  • 4.  RE: Asset downtime

    Posted 12/14/23 11:12 AM

    Hi Bartosz,

    Thanks for responding. 

    We are currently using the same version as you mentioned above 7.6.1.3-IFIX20230117-1942 but we are facing the issue currently.



    ------------------------------
    Iswarya S
    ------------------------------

    Original Message


  • 5.  RE: Asset downtime

    Posted 12/15/23 07:53 AM

    Hi Iswarya,

    Tried once again reproduce it but without success. Maybe this video will be available for you to see my test: https://youtu.be/CTcC4Ob9yI4

    I think you will need to collect all of the data and ask IBM for support via IBM CASE.



    ------------------------------
    Bartosz Marchewka
    IBM Maximo Consultant
    AFRY
    ------------------------------

    Original Message


  • 6.  RE: Asset downtime

    Posted 01/04/24 05:00 PM

    Hi @Bartosz Marchewka 

    I went through these problem statements and I faced face same issue as you described, so I didn't think it was a kind of IFIX issue.

    I tried to write a script on the MODDOWNTIMEHIST object to get the set from the asset using owner mbo as well, and then using a loop, we will calculate the sum of all the downtime hours in the ASSET.TOTDOWNTIME attribute, but it won't work.

    But if we use the manage downtime history action, the ASSET.TOTDOWNTIME attribute fetches the correct data from that MODDOWNTIMEHIST.

    could yoou please tell what this start/end operational type did. 



    ------------------------------
    Vivek Nagre
    ------------------------------

    Original Message


  • 7.  RE: Asset downtime

    Posted 01/07/24 04:16 AM

    Hi Vivek

    Andrew Jeffery has a great blog on this, see Asset Downtime – Maximo Secrets

    Essentially, when the asset was reported as down did that have an operational impact?  Same for the restart.  Some companies want to recognise the downtime hours only when it has an operational impact i.e. a line goes down, a vehicle needs to come off the road, this about this, if you have two pumps A and B, A goes down and B kicks in.  Yes, the A pump is offline, but there is no operational impact, so why count them?

    Let the great debate kick off.



    ------------------------------
    Regards,
    Craig Kokay
    Principle Consultant
    Cosol
    https://cosol.global/

    Ph: +61-411-682-040
    email: craig.kokay@cosol.global
    ------------------------------

    Original Message


Related Content