Source of Meter Readings

This document explains how to activate the possibility to report meter readings with a reference to an order.

With this process you can analyze who or in which way a meter reading was reported. If it comes through an API, then the record must be flagged as external source. If it is done on a work order (WO), then the meter reading history must reflect that. A record in the WO event log in 'Event Log' (MOS102) is also required. This way you can check if a meter reading is done against a WO or not.

Outcome

A meter reading history record is created in 'Model/Site Individual. Open Op History' (MOS270) with reference to a work order or maintenance customer order. The fields used are 'Reference order category', 'Reference order number', and 'Reference order line'. A specific operation cycle type can also be used. This can be useful for integrations to an external system when the machine itself sends out meter readings. It could also be a specific meter event if this comes from a rental agreement.

Meter readings can be reported through 'Equipment. Report Meter Reading' (MOS160), MOS160MI (Manual Meter Reporting), 'Equipment. Update History' (MOS290), MOS290MI (Equipment. Update History), 'WO Operation. Report Inspection Result' (MOS085), or MOS085MI (Maintenance inspections). For tools used in manufacturing or maintenance it can also be reported using operation reporting in 'WO Operation. Report' (MOS070) or 'MO Operation. Report' (PMS070) with background programs MOS919 or PMS918. Meter readings for tools can also be done manually through 'WO Operation. Update Tool Transaction' (MOS135).

When meters are reported in this way, a record is created in the WO event log in (MOS102). The events created are called MTR, for normal equipment, and MTT, for tools reported through (MOS070), (PMS070), or (MOS135).

For aircrafts, the flight log functionality in 'Operational Log. Open' (FLS001) is used. In this scenario, the flights are not linked to any reference order. This means that the cycle type defined for the flight log in 'Settings - Operational Log' (FLS788) is used when creating the meter reading history record in (MOS270).

Before you start

Before you start, these settings must be made:

  • A serialized item or tool exists with non-calendar meters, for example, hours, km, or miles. The meters are defined in 'Item. Open' (MMS001), 'Item. Connect Meter' (MMS004) and 'Equipment/Ser Item. Open Meter Reading' (MMS241).
  • Parameter 50-'Source of meter readings' in 'Settings - Maintenance 1' (CRS788) must be activated.

    These are the alternatives:

    0=Not used.

    1=The reference order fields are open for input.

Follow these steps

Follow these steps for (MOS160) or MOS160MI:

  1. Start (MOS160) or MOS160MI.
  2. Ensure you have the necessary information about the work order that you are using as a reference.

    Specify this info:

    • Item number.
    • Serial number.
    • Operating cycle type, if applicable.
    • Reference order category (RORC) set to 6.
    • Reference order number (RORN) set to 'WO number'.
    • Reference order line (RORL) set to 'Operation number'.
    • For MOS160MI only, specify meter event, if connected to a rental agreement.
  3. Press Enter.
  4. Verify in (MOS270) or (MOS271) that a record is created and that the references specified in step 2 is present in (MOS270).
  5. Verify in (MOS102) that a meter event, MTR, has been created for the WO or operation.

Similar workflows and input fields are used in other meter reporting functions.

Related topics