EAM-55383 CLONE - Assets | Meters | Enter Meter Reading - WO gets released with a too low reading caused by Meter Due of nested meter based PM schedule work orders being updated with the wrong interval after it has been bypassed - HxGN EAM - Version 12.0 - Hexagon

HxGN EAM Resolved Issues for 2022

Language
English
Product
HxGN EAM
Search by Category
HxGN EAM Version
12

EAM-55383 CLONE - Assets | Meters | Enter Meter Reading - WO gets released with a too low reading caused by Meter Due of nested meter based PM schedule work orders being updated with the wrong interval after it has been bypassed

 Description 

Meter Due of nested meter based PM schedule work orders is updated with the wrong interval after it has been bypassed. This situation is created when the meter interval on PM schdules | Equipment is different from PM schdeule record view for the minor PM.

Steps to reproduce :

0. Install parameters - Set the Install parameter AUTOPMCL to Yes

1. PM schedules - Register a meter based fixed PM schedule PLAN3 with a meter interval of 1000h and a nesting reference NEST34

2. PM schedules - Register a meter based fixed PM schedule PLAN4 with a meter interval of 3000h and a nesting reference NEST34

3. Assets - Register a new asset ASSET3

4. Assets | Meters - Register for ASSET3 a meter with UOM \"h\"

5 - PM schedules | Equipment - Associate ASSET3 with PLAN3 entering as Meter Interval 1500 and as Meter Due 1500 (note: different from the record view interval!)

6 - PM schedules | Equipment - Associate ASSET3 with PLAN4 entering as \"Meter Due\" 3000

7 - Assets | Meters - Actions menu - Add meter reading - Enter the meter reading 1500h - the PLAN3 work order is released - close it

8 - Assets | Meters - Actions menu - Add meter reading - Enter the meter reading 3000h - the PLAN4 work order is released and the PLAN3 work order is put into status B.

9 - Check the Meter Due of the PLAN3 work order in the database (R5EVENTS.EVT_METERDUE). Then close the PLAN4 work order and check the PLAN3 work order Meter Due. It has become 4000 (4500 is expected)

10. - Assets | Meters - Actions menu - Add meter reading - if you would now add 4000 as meter reading a work order would be released and this is wrong, as it is expected only at 4500.

Apparently the system uses ppm_meter from r5ppms to adjust the Meter Due after bypassing a PPM work order instead of ppo_meter from r5ppmobjects.

Current result - WO gets released with a too low meter reading (based on PM schedules record view interval)

Expected result - WO gets released with a correct meter reading (based on PM schedules - Equipment inetrval)

EAM-55410 ION - Outbound WSPromptTransaction failing with error: ValueConvertorException from IModelMapping.doMapping. - More details: Failed to convert String value(A) to Boolean. when updating Asset's test point