This document describes the recalculation and simulation functionality in 'Model/Site Individual. Open Op History' (MOS270) and 'Serialized Item. Display Install History' (MOS266) that can be used to correct corrupt meter readings on:
Faulty meter readings can be caused by various actions and scenarios such as mistakes made when specifying readings in 'Equipment. Report Meter Reading' (MOS160) or 'Operational Log. Open' (FLS001), system issues, and power outage.
Erroneous or corrupt meter readings for the operational unit and its installed components are recalculated and updated.
If the errors also occurred in installation, removal or service history, the meter readings are corrected and recalculated along with all related values.
Erroneous or corrupt meter readings have been found for the operational unit or its installed components.
Meter reading corrections applied in these ways do not impact MCO or Rental meter based invoices. If applicable, they must be corrected manually.
Follow these steps if:
A mismatch has occurred between 'Operational Log. Open' (FLS001), 'cumulative', and 'Model/Site Individual. Open Op Cycle Readings' (MOS271), 'new meter value - after transaction'.
A record has been specified as faulty in (MOS270). In this case a recalculation function exists to remove the mismatch and realign the values.
Select F15='Recalculate' at the Operational unit level in (MOS270), to display a pop-up selection window where you can specify a start date and time to indicate when the meter readings were accurate. This can range from the previous week to several years in the past.
If required, restrict the recalculation to only include a specific Operation cycle type, such as 'F' records from flightlog or 'C' records for correction. This is useful if only certain types should be recalculated and the corrections deleted or cleared.
Select a specific meter if required. If left blank the meters from 'Item. Open' (MMS001/J) will be recalculated in addition to all meters that are calculated based on those. If other meters should be recalculated, they must be manually specified individually.
Starting from the record before the specified start date and time, all reported meter values in 'Model/Site Individual. Open Op Cycle Readings' (MOS271) will then be added to the last correct 'New meter value' and update each later record in (MOS271) 'New meter value'.
The result is a correct total on the last record in (MOS271) which will then update 'Equipment/Ser Item. Open Meter Reading' (MMS241) 'Since new'.
Follow these steps if a mismatch has occurred between the database meter values and the correct values. In this case, simulation and update of the applicable tables in M3 BE is required.
Use sorting order 6 in 'Serialized Item. Display Install History' (MOS266) and the F15='Simulate values' function.
The sorting order includes fields from (MMS241) in the header and several columns in the list view to display the simulation results.
When using F15, the system searches for a start value for the component in 'Equipment. Update History' (MOS290).
If not found, the component is assumed to be new and the start value is 0.
The function then:
If the simulated values are correct, select F17='Update' to update the 'Serialized Item. Display reading Ins/Rem' (MOS267) values at install and, if applicable, removal.
If the component remains as installed, that is, no removal record after the last install exists, fields 'At install Op unit' and 'At install component' in 'Equipment/Ser Item. Open Meter Reading' (MMS241) are updated as the final step.
Follow these steps if a faulty meter value was specified during normal reporting of meters, or if a value has become corrupt.
Note that several options are available to correct this, depending on the reporting method used, whether later transactions are reported and the report type used:
If a faulty meter reading is reported, either related option 11='Correction' in (MOS271) or MOS160MI, transaction CorrMeterRead, can be used to update the faulty value. Then, depending on the report type:
If report type=0 (new total) is used, the 'New meter value' field will be editable. Note that only those records up to the next report date and time will be updated as the next report may be correct.
It also updates all calculated meters based on the changed meter if applicable. For example hours multiplied by 2 if hours are updated.
If report type=1 (latest usage) is used on the meter, the 'Meter value cycle' field will be editable.
This will then update the 'New meter value' for this record, all later records in (MOS270) and (MOS271), and finally the current 'Since new' value in (MMS241) for the operational unit.
It also updates all calculated meters based on the changed meter if applicable. For example, hours multiplied by 2 if hours are updated.
As there may be installations, removals, and services performed based on the faulty meter reading, a function program (MOS928) is used to correct it. This updates (MOS267) for installations and removals and it also updates (MOS180) and (MMS242) for the service history records of the operational unit and all installed components affected.
The preferred option is for faulty reporting to be corrected immediately using related option 11='Correction' in (MOS271). If, however, meter readings and the new total is corrupt, it is important that the repair functions are used in the correct sequence, which is:
Select F15='Recalculate' in (MOS270) and specify the start date and time to indicate when the meter readings were accurate.
Select F15='Simulation' in (MOS266) to simulate the meter readings for each component.
Select F17='Update' in (MOS266) to use the simulated values to update the values at install or removal, or both.
The 'Reset approval' and 'Approval' in (MOS180) can then be performed based on the corrected meter values. This will update (MOS180) and (MMS242).