Analysis and Repair Functions for Meter Readings

Outcome

Erroneous or corrupt meter readings for the operational unit and its installed components are recalculated and updated.

If errors occur in the installation, removal, or service history, the meter readings are corrected and recalculated along with all related values.

Before you start

Erroneous or corrupt meter readings are found for the operational unit or its installed components.

Limitations

Meter reading corrections that are applied in these ways do not affect MCO or rental meter-based invoices. If applicable, you must correct these invoices manually.

Follow these steps to recalculate a new meter value

Follow these steps if one of these prerequisites is met:

• A mismatch occurs between 'Cumulative' in (FLS001) and 'New value' in 'Model/Site Individual. Open Op Cycle Readings' (MOS271).
• A record is specified as faulty in (MOS270). In this case, a recalculation function exists to remove the mismatch and realign the values.

1. Select F15='Recalculate' at the operational unit level in (MOS270) to display a pop-up selection window. Specify a start date and time that indicate when the meter readings are accurate. The range can cover the previous week or several years in the past.

2. If required, restrict the recalculation to a specific operation cycle type, such as F records from flight log or C records for correction. Use this option when only certain record types require recalculation.

3. Select a specific meter if required. If you leave the field blank, meters from 'Item. Open' (MMS001/J) are recalculated along with all meters that are calculated based on these meters. If other meters require recalculation, you must specify them individually.

4. Starting from the record before the specified start date and time, all reported meter values in (MOS271) are added to the last correct new meter value, and each later record for 'New value' in (MOS271) is updated.

5. The result is a correct total on the last record in (MOS271) which then updates the 'Since new' field in (MMS241).

Follow these steps to simulate and update meter readings

Follow these steps if a mismatch occurs between the database meter values and the correct values. In this case, simulation and update of the applicable tables in M3 Business Engine (M3 BE) is required.

1. Use sorting order 6 in (MOS266) and F15='Simulate values'.

   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, a start value for the component is searched in 'Equipment. Update History' (MOS290).

   If a start value is not found, the component is assumed to be new, and the start value is 0.

2. These actions are then performed:

   • The 'Sim' columns are populated with the start value, starting from the first installation.
   • A search is performed in (MOS271) for the operational unit, and these actions are performed for each installation record:
     • The meter readings at the installation date and time are returned.
     • The meter values for the operational unit at the removal date and time are returned.
     • The duration for the operational unit is calculated and added to the component value at installation, resulting in the meter value at removal for the component.

3. If the simulated values are correct, select F17='Update' to update the 'Serialized Item. Display Reading Ins/Rem' (MOS267) values at installation and, if applicable, removal.

   If the component remains as installed and no removal record exists after the last installation, the 'Ins op unt' and 'At comp ins' fields in (MMS241) are updated as the final step.

Follow these steps to change a faulty meter value on a single time reporting transaction

Several correction options exist based on the reporting method, reported transactions, and report type.

Follow these steps if a faulty meter value is specified during normal reporting of meters, or if a value becomes corrupt:

1. If a faulty meter is reported, use related option 11='Correction' in (MOS271), or use MOS160MI with transaction CorrMeterRead to update the faulty value. For calculated meters, use related option 12='Correct calculated meter', or use MOS160MI with transaction CorrCalcMeter.

   The steps differ based on the report type:

   • If you use report type 0 (new total), edit the 'New value'. Records up to the next report date and time are updated because the next report can be correct.

     All calculated meters are updated based on the changed meter, if applicable. For example, hours multiplied by 2, if hours are updated.

   • If you use report type 1 (latest usage), edit the 'Mtr value cycle' field.

     The 'New value' is updated for the current record and all later records in (MOS270) and (MOS271). The current 'Since new' value in (MMS241) for the operational unit is also updated.

     All calculated meters are updated based on the changed meter, if applicable. For example, hours multiplied by 2, if hours are updated.

2. If installations, removals, or services depend on the faulty meter reading, use (MOS928) to correct the value.

   The program updates (MOS267) for installations and removals, and (MOS180) and (MMS242) for service history records of the operational unit and installed components.

Correct a faulty date for a meter report in (MOS160) and (MOS270)

If a meter value is reported with an incorrect date or time, you cannot update the date in (MOS270).

In this case, complete these steps:

1. Find the faulty record in (MOS270). Verify whether later transactions are reported.
2. Copy the data in (MOS270) and (MOS271) to record the meter readings and date and time.
3. For the faulty record, use option 11='Meter Details' in (MOS270) and option 11='Correction' option in (MOS271) to correct the meter reading. Set the 'Mtr value cycle' (MVAT) field to zero. Set the 'New value' field to match the previous record.
4. Repeat this step for each meter in the list. Calculated meters are recalculated in the background.
5. Return to (MOS270). Repeat these steps for each later transaction.
6. When the faulty record and all later transactions are set to zero, delete them in (MOS270).
7. Specify each transaction with the correct date and time, using the values saved in step 2.
8. The transactions are now saved with the correct date and time, and the meter values are correct.

Correct a faulty meter value for an installed component in (MMS241)

If a faulty meter value exists in (MMS241) for the 'At comp ins' or 'Ins op unt' field, you can edit the value by using related option 15='Correction'. For calculated meters, you can use related option 16='Correct calculated meter'.

You must set security for this option.

The e-signature functionality in M3 BE is available in (MMS241) to trace corrections. Setup for this functionality is required in 'E-Signature Program. Open' (SES410). Use F14='Generate data' to retrieve (MMS241) to the list. Activate the e-signature functionality with status 20. Define that the functionality is only required on the first panel.

Use related option 11='E-signature Object' in 'E-Signature Object. Open' (SES411) to define which fields trigger the e-signature.

Use related option 11='Signatory' in 'E-Signature Object. Connect Signatory' (SES415) to define who is authorized to sign for this correction.

When activated, the standard e-signature functionality is used for the related option 15='Correction'. You must sign for the correction, and history records are saved.

Exception workflow

The preferred option requires immediate correction of faulty reporting using related option 11='Correction' in (MOS271). If meter readings and the new total are corrupt, use the repair functions in the correct sequence:

1. Select F15='Recalculate' in (MOS270). Specify the start date and time to indicate when the meter readings are accurate.

2. Select F15='Simulation' in (MOS266) to simulate the meter readings for each component.

3. Select F17='Update' in (MOS266) to use the simulated values to update the values at installation, removal, or both.

You can then perform 'Reset approval' and 'Approval' in (MOS180) based on the corrected meter values. This action updates (MOS180) and (MMS242).

Add a historical record in (MOS270)

An OEM can issue a service letter that specifies that a job must be completed a defined number of hours from a specified date. If this date is before the first record in (MOS270), the system cannot calculate the next due values correctly.

Another use case involves a vehicle on a long-term lease, where the meters are not updated continuously. If a removal or installation occurs between two records in (MOS270), you can specify a record for that date to ensure that the removal or installation transaction is correct.

You can use the API transaction AddHistoryMeter in MOS290MI for this purpose.

In the AddHistoryMeter transaction, you can add meter readings before the first existing record in (MOS270), or between two existing records. If no records exist in (MOS270), a stop message is displayed with information to use the default MOS290MI transaction Add instead, (MOS160) or (FLS001). The reason for this behavior is that the new transaction updates only (MOS270) or (MOS271). The current meter readings in (MMS241) are not updated.

Verification is performed to ensure that added meter readings on a specific date and time are reasonable, where the value lies between the meter readings in the previous and the subsequent transaction in (MOS270) or (MOS271).

Records that are added using this transaction are marked with MOS290MI in the 'Changed by' field in (MOS270) or (MOS271). This value is used to identify the transaction type and to enable the DltHistoryMeter transaction to run if the record is specified incorrectly. This value is also used to prevent correction by using (MOS271) functionality and MOS160MI transaction CorrectMeterRead.

When using other meter reporting functions, calculated meters are automatically updated. When using the AddHistoryMeter transaction, you must update the calculated meters manually.