IBM Support

IJ46610: DOWNTIME REPORT IS NOT CALCULATED CORRECTLY WHEN THERE THE SHIFTS OVERLAP

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • ---------------------------------------------------------------
    ---------
    DESCRIPTION:
    ---------------------------------------------------------------
    ---------
    When an asset have calendar and shift defined and the shifts are
    overlapped for the same day, whenever the user want to report
    downtime, the system does not take in consideration the shift of
    the asset to calculate the downtime, instead it calculates among
    all the shifts in the calendar that are between the start and
    end dates entered when reporting asset downtime.
    
    Steps to Replicate:
    
    1. Go to Calendar application and create CALENDAR starting on
    jan 1st 2023 and ending on dec 31st 2023
    
    2. Under More Actions > Define/Apply Shifts
    Create 2 shifts, both starting on MONDAY and days in pattern 7
    
    SHIFT1 - Define Pattern - Start Time 00:00 - End Time 23:59:59
    SHIFT2 - Define Pattern - Start Time 17:00 - End Time 16:59:59.
    
    Select the both shift created and click on Apply Shift toentire
    calendar.
    OK
    
    Validate that for each day in the calendar you have 48 hours (or
    47:58) set up
    
    3. Go to Assets application and create a new asset and define
    the calendar as the one created in step 1 and one of the 2 shift
    created in step 2, I used SHIFT1
    Change asset status to OPERATING
    
    4. Under More Action > select Report downtime action and enter
    datetimes between the same day:
    Choose Report Downtime
    Start Date: 17/04/23 02:00 AM
    End Date: 17/04/23 05:00 AM
    Hour: 03:00 as expected
    
    or
    
    Start Date: 17/04/23 02:00 AM
    End Date: 17/04/23 02:15 PM
    Hour: 12:15 as expected
    
    but
    
    Start Date: 17/04/23 02:00 AM
    End Date: 17/04/23 06:30 PM
    
    
    CURRENT ERRONEOUS RESULT: The Hour filed is updated to 31:30 (or
    31:29)
    
    EXPECTED RESULT: The Hour field should be updated to 16:30 (or
    16:29)
    
    ---------------------------------------------------------------
    ---------
    Environment:
    ---------------------------------------------------------------
    ---------
    Reported in Version: Maximo 7.6.1.2
    Application within Maximo: Assets
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DOWNTIME REPORT IS NOT CALCULATED CORRECTLY WHEN SHIFTS      *
    * OVERLAP                                                      *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 8.8 Product.
    Introduced shift as a parameter for calculating downtime.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ46610

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-04-28

  • Closed date

    2023-08-15

  • Last modified date

    2023-08-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
15 August 2023