IBM Support

IJ05555: GA - SPATIAL SCHEDULING OPTIMIZATION IS NOT WORKING WHEN START AND END LOCATION IS DIFFERENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM: GA- Spatial optimization is not working when the Start
    and END location are no the same
    PERFORMANCE ISSUE: NO
    STEPS TO REPRODUCE:
     -Map Manager setup with Google, Bing or Spatial map
     -Need at least 3 Crafts and minimum of 2 Labors per Craft
     -Have a calendar with minimum of 120 days and at least one
    Shift applied
    Setup:
        - In System Property set __odmesystem for
    mxe.skd.optimization.adminuser AND maximo for
    mxe.skd.optimization.adminpassword
        - Perform the Live Refresh
     -Create Service Address  UC08SA1 and associate to a valid
    Address
     -Create Service Address  UC08SA2 and associate to a valid
    Address
     -Create Service Address  UC08SA3 and associate to a valid
    Address
     -Create Location UC08LC1 - Operating - All Active Status
     -Associate the UC08SA1 Service Address to the Location
     -Create Asset UC08AS1 - Active Status
     -Associate the UC08LC1 to the UC08AS1
     -Create Location UC08LC2 - Operating - All Active Status
     -Associate the UC08SA2 Service Address to the Location
     -Create Asset UC08AS2 - Active Status
     -Associate the UC08LC2 to the UC08AS2
     -Create Location UC08LC3 - Operating - All Active Status
     -Associate the UC08SA3 Service Address to the Location
     -Create Asset UC08AS3 - Active Status
     -Associate the UC08LC3 to the UC08AS3
     -Create Job Plan UC08JP1  duration 4 hours
     -At the Job Plan create 2 tasks 2 hours each
     -Enter 3 Resources Line for Each Existing Craft
     -Make sure for the 2 lines of resource to the 2 tasks
     -One resource will be without tasks relation and setup that
    for 1 hour
     -Change the status to Active
     -Create a Preventive Maintenance
     -Associate the UC08AS1 asset and  to this PM
     -Associate the UC08JP1 Job Plan to this PM
     -At the Frequency tab use the Frequency to 3 days and Next
    Due Date to Today
     -Set the Target Start time to 7 AM
     -Move to the Forecast tab and check the Reforecast
    Subsequent Dates
     -Change the status of the Preventive Maintenance to Active
     -Run the Generate Forecast for 90 days
     -Run the Generate Work Orders to 30 days (11 Work Order
    generated)
     -Create a Preventive Maintenance
     -Associate the UC08AS2 asset and  to this PM
     -Associate the UC08JP2 Job Plan to this PM
     -At the Frequency tab use the Frequency to 3 days and Next
    Due Date to Today
     -Set the Target Start time to 7 AM
     -Move to the Forecast tab and check the Reforecast
    Subsequent Dates
     -Change the status of the Preventive Maintenance to Active
     -Run the Generate Forecast for 90 days
     -Run the Generate Work Orders to 30 days (11 Work Order
    generated)
     -Create a Preventive Maintenance
     -Associate the UC08AS3 asset and  to this PM
     -Associate the UC08JP3 Job Plan to this PM
     -At the Frequency tab use the Frequency to 3 days and Next
    Due Date to Today
     -Set the Target Start time to 7 AM
     -Move to the Forecast tab and check the Reforecast
    Subsequent Dates
     -Change the status of the Preventive Maintenance to Active
     -Run the Generate Forecast for 90 days
     -Run the Generate Work Orders to 30 days (11 Work Order
    generated)
    Test Steps
     - Go to Graphical Assignment application and create a new
    record
     - Setup with the Calendar, Shift and Org
     - Make sure to have the Work List of 90 days
     - Enter a New Query to look for the PM1, PM2 and PM3
     - Enter a New Query to look for the labors previously
    created
     - Click on Configure Optimization Server
     - Expand the WORKASSIGNMENT765 section and enter
     - URL https://9.32.245.17:9443/odme/
     - Database: DB2
     - DB Instance: MXODME
     - Hostname: 9.32.245.17
     - Port: 50000
     - User: odmea7671
     - Password: @zkaban1
     -Click on Deploy
     - Create Spatial Scheduling Scenario
     - Click on Populate Destination Travel Time Matrix
     - Click on Run Optimization
     - Click on Submit
    CURRENT ERRONEOUS RESULT:  Optimization Failed
    EXPECTED RESULT:  Optimization ran correctly
    ADDITIONAL INFO: NO
    ENVIRONMENT (SYSTEM INFO):
    App Server Weblogic Application Server 12.1.1.0
    Version
    Tivoli's process automation engine 7.6.0.9-IFIX20180330-1643
    Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-04
    IBM TPAE Integration Framework 7.6.0.9 Build 20171127-2330 DB
    Build V7609-32
    IBM Maximo Asset Management Scheduler Plus 7.6.7.0 Build
    20171127-0100 DB Build V7670-01
    IBM Maximo Asset Management Scheduler 7.6.7.0 Build
    20171127-0100 DB Build V7670-56 HFDB Build HF7670-12
    IBM Maximo Asset Management Work Centers 7.6.0.3 Build
    20171121-0723 DB Build V7603-175
    Server OS Windows Server 2012 R2 6.3
    Server DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release 11.2.0.3.0 - 64bit Production With the Partitioning,
    OLAP, Data Mining and Real Application Testing options)
    (c) Copyright IBM Corp. 2017
    LOCAL FIX: N/A
    SECURITY IMPACT (Y/N): N
    

Local fix

  • Leave Start and End Location as the same point
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * maximo scheduler users                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * GA- Spatial optimization is not working when the Start       *
    * and END location are no the same                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixpack  Release 7.6.1.0 of Base Services (Scheduler   *
    * 7671)or request an interim fix                               *
    ****************************************************************
    

Problem conclusion

  • Fix has been made to fix....The fix for this APAR is contained
    in the following maintenance package:
    		 | release\fix pack\interim fix for  Release 7.6.1.0 of Base
    Services(Scheduler 7671)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ05555

  • 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

    2018-04-09

  • Closed date

    2018-04-17

  • Last modified date

    2018-04-17

  • 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 SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

  • R767 PSY

       UP

[{"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:
17 April 2018