IBM Support

IJ46189: METER READING IMPORT ISSUE VIA MIF CAUSES INCORRECT LAST WORK ORDER INFORMATION AND NEXT WORK ORDER PROJECTION IN METER BASED PM

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

  • PROBLEM DESCRIPTION:
Meter Reading import issue via Maximo Integration Framework
(MIF) causes incorrect Last Work Order Information and Next Work
Order Projections in Meter based PMs

STEPS:
1) Go to MXMETERDATA Object Structure , select "support flat
structure" checkbox
2) Create a new Asset e.g. METER2
Attach meter RUNHOURS
Average calculation method: ALL
Rollover: 99999
Reading type: ACTUAL
Save the record
Change the asset status to Operating
3) Go to PM application
Create a PM e.g. METER2
Associate the same asset e.g. METER2
Add the RUNHOURS meter under meter frequency tab
Set the frequency to 1000
Select the following checkboxes:
Use Last Work Order's Start Date to Calculate Next Due Date?

Generate Work Order Based on Meter Readings (Do Not Estimate)?

Generate Work Order When Meter Frequency is Reached?
Change the PM status to ACTIVE
4) Go to Organizations application > PM Options

Select an appropriate site
Select "Use Frequency Criteria" checkbox
select "Base Work Order Generation on Meter Reading Only (Do Not
Estimate)" checkbox
Select "Automatic PM WO generation" checkbox
Enter a where clause e.g.
PMNUM='METER2'
NOTE: replace with the appropriate PMNUM
de-select "Automatic MeasurePoint WO generation" checkbox
Click OK
5) Activate JMSQSEQCONSUMER crontask
6) Activate the PMWoGenCronTask cron task in the Cron Task Setup
application
Set it to run every 2 minutes
7) Create an csv file.  Enter the external system and meter
details as below:
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,500,2023-03-10T11:55:00
8) Go to external system EXTSYS1 and import the csv file from
MXMETERInterface Enterprise Service
De-select use continuous queue checkbox
import the csv file (prepared in step 7)
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,500,2023-03-10T11:55:00
Go to Assets app, filter for asset "METER"
Go to Manage Meter Reading History action
Verify that the meter reading of 500 has been imported

9) Go to PM, filter for "METER2"
Go to Frequency tab and Meter based Frequency tab
Go to "Last Work Order Information section"
Meter Reading is blank
Meter Reading Date is blank
No workorders generated as the frequencies are not reached (as
expected)
Go to the "Next Work Order Projections" section
Next Meter Reading = 1,000.00
Units to go = 500
Estimated Next Due Date is blank

10) Update the newreading to 1000 and newreadingdate to
2023-03-11 in the csv file
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,1000,2023-03-11T11:55:00
11) Import the csv file through the same external system,
MXMETERInterface Enterprise Service

ACTUAL BEHAVIOR:  Go to PM 'METER2' in PM application
Go to Frequency tab and Meter based Frequency tab
In the Last Work Order Information section
Meter Reading = 500
Meter Reading Date = 3/10/23 11:55 AM
In the Next work order projection section:
Next Meter Reading = 1500
Units to Go = 500

EXPECTED BEHAVIOR:

In the Last Work Order Information section
Meter Reading should be 1000
Meter Reading date should be 2023-03-11T11:55:00

In the Next work order projection section:
Next Meter Reading should be 2000
Units to Go should be 1000


NOTE:  This issue is SQL Server specific.  If we manually
entering meter reading from Assets application, then it
populates the Last Work Order Information and Next Work Order
Projections in Meter based PMs.  The problem is with the import
via MIF only.

REPORTED IN VERSION:
Maximo Asset Management 7.6.1.2 IFIX 29
7.6.1.2 MIF IFIX 16

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:                                              *
* Maximo users                                                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* METER READING IMPORT VIA MIF MXMETERDATA OBJECT STRUCTURE    *
* CAUSES INCORRECT LAST WORK ORDER INFORMATION AND NEXT WORK   *
* ORDER PROJECTION IN METER BASED PM                           *
****************************************************************
PROBLEM DESCRIPTION:
Meter Reading import issue via Maximo Integration Framework
(MIF) causes incorrect Last Work Order Information and Next
Work
Order Projections in Meter based PMs
STEPS:
1) Go to MXMETERDATA Object Structure , select "support flat
structure" checkbox
2) Create a new Asset e.g. METER2
Attach meter RUNHOURS
Average calculation method: ALL
Rollover: 99999
Reading type: ACTUAL
Save the record
Change the asset status to Operating
3) Go to PM application
Create a PM e.g. METER2
Associate the same asset e.g. METER2
Add the RUNHOURS meter under meter frequency tab
Set the frequency to 1000
Select the following checkboxes:
Use Last Work Order's Start Date to Calculate Next Due Date?
Generate Work Order Based on Meter Readings (Do Not Estimate)?
Generate Work Order When Meter Frequency is Reached?
Change the PM status to ACTIVE
4) Go to Organizations application > PM Options
Select an appropriate site
Select "Use Frequency Criteria" checkbox
Select "Base Work Order Generation on Meter Reading Only (Do
Not
Estimate)" checkbox
Select "Automatic PM WO generation" checkbox
Enter a where clause e.g.
PMNUM='METER2'
NOTE: replace with the appropriate PMNUM
de-select "Automatic MeasurePoint WO generation" checkbox
Click OK
5) Activate JMSQSEQCONSUMER crontask
6) Activate the PMWoGenCronTask cron task in the Cron Task
Setup
application
Set it to run every 2 minutes
7) Create an csv file. Enter the external system and meter
details as below:
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,500,2023-03-10T11:55:00
8) Go to external system EXTSYS1 and import the csv file from
MXMETERInterface Enterprise Service
De-select use continuous queue checkbox
Import the csv file (prepared in step 7)
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,500,2023-03-10T11:55:00
Go to Assets app, filter for asset "METER"
Go to Manage Meter Reading History action
Verify that the meter reading of 500 has been imported
9) Go to PM, filter for "METER2"
Go to Frequency tab and Meter based Frequency tab
Go to "Last Work Order Information section"
Meter Reading is blank
Meter Reading Date is blank
No workorders generated as the frequencies are not reached (as
expected)
Go to the "Next Work Order Projections" section
Next Meter Reading = 1,000.00
Units to go = 500
Estimated Next Due Date is blank
10) Update the newreading to 1000 and newreadingdate to
2023-03-11 in the csv file
EXTSYS1,MXMETERInterface,AddChange,EN
ASSETNUM,SITEID,METERNAME,INSPECTOR,NEWREADING,NEWREADINGDATE
METER2,BEDFORD,RUNHOURS,MAXADMIN,1000,2023-03-11T11:55:00
11) Import the csv file through the same external system,
MXMETERInterface Enterprise Service
ACTUAL BEHAVIOR:
Go to PM 'METER2' in PM application
Go to Frequency tab and Meter based Frequency tab
In the Last Work Order Information section
Meter Reading = 500
Meter Reading Date = 3/10/23 11:55 AM
In the Next work order projection section:
Next Meter Reading = 1500
Units to Go = 500
EXPECTED BEHAVIOR:
In the Last Work Order Information section
Meter Reading should be 1000
Meter Reading date should be 2023-03-11T11:55:00
In the Next work order projection section:
Next Meter Reading should be 2000
Units to Go should be 1000
NOTE: If we manually entering meter reading from Assets
application, then it
populates the Last Work Order Information and Next Work Order
Projections in Meter based PMs. The problem is with the import
via MIF only.

    



Problem conclusion


    

  • The fix for this APAR will be contained in a future release.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ46189
    • 

  • 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-03-28
    • 

  • Closed date
    2023-04-30
    • 

  • Last modified date
    2023-04-30
    • 





    

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

            01 May 2023
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback