IBM Support

IJ21981: GRAPHICAL SCHEDULING LOAD SPREAD SHOWS LARGE USAGE ON LAST SHIFT

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

  • When one task is interruptible the resource load on it should
    still be spread evenly across the interrupted shifts.    But it
    is not, the first few days will have one value and the last day
    will have a much larger percentage of the load.   For example
    on a task of 32 hours being interrupted on an 8 hour per day
    shift with Planned Labor of 1, days 1, 2 and 3 might have 6
    each and day 4 might have 14 where it should be that each day
    has 8.
    
    Steps to reproduce:
    
    1. Set the skd.laborHours.spreadAcrossTask system Property to 1
    and do a Live Refresh.
    2. Create 4 Shifts
    - Week - 7 days in Pattern, Starting Sunday, works Mon-Friday
    10 hours per day from 7am to 5pm
    - Shift1 - 7 days in Pattern, Starting Sunday, works everyday
    for 8 hours from Midnight to 8am
    - Shift2 - 7 days in Pattern, Starting Sunday, works everyday
    for 8 hours from 8am to 4pm
    - Shift3 - 7 days in Pattern, Starting Sunday, works everyday
    for 8 hours from 4pm to Midnight
    3. Create a Calendar for one year long and apply the 4 new
    shifts to it.
    4. Create a new Craft, name it CRAFTW,with 2 Labor on it.
    Assign the new Calendar and the Shift Week to one Labor and the
    new Calendar and one of the other shifts to the other Labor.
    5. Create another new Craft, call it CRAFTS, with several Labor
    on it.   Assign the new Calendar and different shifts to each
    one.
    6. Create a Work Order with 2 Tasks
     - One of the tasks will be interruptible at WEEK shift and
    have Duration of 40.  For that task add Planned Labor of CRAFTW.
     - The other task will not be interruptible.   Duration 178.
    Planned Labor of CRAFTS.
    7. Create a new schedule in Graphical Scheduling record the new
    Calendar, all 4 Shifts, duration of 60 days and a Query that
    load the Work Order created above.
    8. Click on  the Graphical View tab.
    
    RESULTS:
    In the resource section, you will notice that CRAFTS is spread
    across the 4 shifts.
    The problem is that CRAFTW is not spread evenly and on the last
    day of your work
    order that will be overbooked with a much larger value than the
    earlier days.
    
    EXPECTED RESULT: The spread against the Interruptible by shift
    task with CRAFTW should split evenly according to the load as
    the non-interruptible task does.
    There should not be a larger value on the last day.
    
    REPORTED IN VERSION:
    7.6.1.1 with IFix 003  - reproduced in this version in house.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the Graphical Scheduling application in Scheduler   *
    * 7.6.7.                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * GRAPHICAL SCHEDULING LOAD SPREAD SHOWS LARGE USAGE ON LAST   *
    * SHIFT                                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A code fix has been made.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ21981

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    767

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-08

  • Closed date

    2020-01-13

  • Last modified date

    2020-01-13

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"767","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
13 January 2020