IBM Support

IJ44442: MASTER TASK CARD CONFIGURATION RULES DON'T WORK ON TASKS CREATED WITHIN OMP

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:
    Master Task Card configuration rules don't work on tasks created
    within OMP
    
    STEPS TO REPRODUCE:
    
    SCENARIO 1: (Working correctly: When you create a Task Card
    outside of the OMP)
    1. Login to Maximo as maxadmin
    
    2. Go to Models --> X-COPTER --> Build Hierarchy and Position
    Rules
    
    3. Expand the Build Hierarchy and select 'APU' build item
    
    4. Scroll down to Part Numbers section
    Part number is 36-150
    
    5. Go to Master Task Card application and create a new Master
    Task Card MTC01
    Master Task Card Type: Component
    Operator: IBM
    
    6. Scroll down to Part Number section --> New Row --> 36-150
    
    7. Go to Frequency Tab --> Intervals and Thersholds --. Standard
    Interval tab --> New Row
    Frequency Type: Meter
    Frequency: 600
    Frequency Units: FH
    
    8. Save the record
    
    9. Change Status of MTC01 to Active
    
    10. Go to Aircraft application --> IBM-XCA
    
    11. Right click on the top level node in the Build Hierarchy -->
    BDI Status
    
    12. Validate Configuration (i.e Run the BDI)
    
    13. Go to BDI Actions tab --> refresh list
    BDI has created a job to create PM from our new Master Task Card
    
    
    14. Click ok to close the dialog
    
    15. Expand the Aircraft Hierarchy --> Select APU build item
    
    16. Scroll down to Maintenance Plan sub-tab
    You can see MTC01 listed here.
    
    Now we want to add this aircraft to an OMP
    
    17. Go to OMP --> Create a New OMP --> X-COPTER
    Operator: IBM
    Authority: EASA
    
    18. Save the OMP
    
    19. Go to Models Tab --> New Row --> X-COPTER
    
    20. Go to Effectivity Tab --> Select Aircraft --> XCOP001
    
    21. Go back to OMP tab --> OMP Tasks --> New Row --> Select
    MTC01 on Master Task Card field --> Save the record
    
    22. Change status --> Submitted for Approval --> Change Status
    --> Active
    
    23. Go to Models --> X-COPTER
    
    24. Go to Configurations Tab --> Expand the variant --> 1
    Variant; X-COPTER is present
    
    25. Go to Build Hierarchy and Position Rules Tab --> Select APU
    position
    
    26. Go to Maintenance Plan sub-tab --> Configuration section -->
    Uncheck the X-COPTER variant
    
    27. Scroll up and go to Advanced Tab
    A rule has been created that the Master Task Card for the part
    number 36-150 is no longer valid for the variant X-COPTER
    
    28. Go back to the Aircraft application --> XCOP001
    
    29. Right click on the top level node in the Build Hierarchy -->
    BDI Status
    
    30. Validate Configuration (i.e Run the BDI)
    
    31. Go to BDI Actions tab --> refresh list
    BDI has created a job to deactivate the Master Task Card status
    
    SCENARIO 2: (PROBLEM: When the Task Card is created from within
    the OMP)
    
    1. Go to Master Task Card (MTC) --> MTC01 --> Duplicate this
    Master Task Card and rename it to MTC02
    
    2. Save the MTC
    
    3. Go to OMP application --> X-COPTER
    
    4. More Actionos --> Revise OMP
    
    5. OMP Tasks --> New Row --> Select MTC01 on Master Task Card
    field --> Save the record
    
    6. Change status --> Submitted for Approval --> Change Status
    --> Active
    
    7. Go to Aircraft application --> IBM-XCA
    
    8. Expand the Aircraft Hierarchy --> Select APU build item
    
    9. Scroll down to Maintenance Plan sub-tab
    You can see MTC02 listed here.
    
    10. Go to Models --> X-COPTER
    
    11. Go to Configurations Tab --> Expand the variant --> 1
    Variant; X-COPTER is present
    
    12. Go to Build Hierarchy and Position Rules Tab --> Select APU
    position
    
    13. Go to Maintenance Plan sub-tab --> Select MTC02 -->
    Configuration section --> Uncheck the X-COPTER variant
    
    14. Scroll up and go to Advanced Tab
    A rule has been created that the Master Task Card for the part
    number 36-150 is no longer valid for the variant X-COPTER
    
    15. Go back to the Aircraft application --> XCOP001
    
    16. Right click on the top level node in the Build Hierarchy -->
    BDI Status
    
    17. Validate Configuration (i.e Run the BDI)
    
    18. Go to BDI Actions tab --> refresh list
    
    RESULT:
    BDI does not create a job to deactivate the Master Tasl Card
    status
    
    EXPECTED RESULT:
    BDI should create a job to deactivate the Master Task Card
    status
    
    PRODUCT:
    Aviation 7682
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MASTER TASK CARD CONFIGURATION RULES DON'T WORK ON TASKS     *
    * CREATED WITHIN OMP                                           *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 8.x Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44442

  • Reported component name

    MAXIMO FOR AVIA

  • Reported component ID

    5725U8700

  • Reported release

    768

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-11-30

  • Closed date

    2023-02-13

  • Last modified date

    2023-02-13

  • 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 FOR AVIA

  • Fixed component ID

    5725U8700

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS5RRF","label":"IBM Maximo for Aviation"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"768","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
13 February 2023