Correcting a runtime reading and replacing a meter

An asset’s cumulative runtime can only be written upwards: a meter does not run backwards, so the normal reading rejects a lower value. Two situations still call for stepping back — you mistyped a value (16000 instead of the real 1600), or the meter was replaced and the new counter starts from zero (or another value). That is what the audited correction is for: the only path that may write backwards, and every step of it leaves a trace.

Before you start

• Permission: cmms:manage.
• Prerequisite: the Maintenance module is on, the Runtime-based frequency switch is on in the policy, and the asset already has a recorded runtime — you can only correct what exists. If there is no reading yet, use the normal Record runtime form.

How to correct

1. Open Maintenance → Asset structure and select the asset (the node).
2. On the Runtime card, click Correct reading / meter replacement.
3. In What happened? choose:
   • Typo correction — the recorded value was wrong; enter the real runtime in Correct value, or new starting value, lower or higher than the recorded one.
   • Meter replacement (new counter) — enter the new meter’s starting value in Correct value, or new starting value. Fill in Final reading of the old meter only if it differs from the recorded value; it cannot be lower, because the old meter also only went up.
4. Enter the Reason — required, at least 5 characters.
5. Click Record correction. The confirmation reads: “Runtime corrected — baseline adjusted for N PM tasks.”

What happens to the PM tasks

Runtime-based preventive maintenance compares the runtime to each task’s baseline (the runtime of its last generation). The correction adjusts the baselines of the asset’s runtime tasks in the same step, so that neither a duplicate nor a missed work order appears afterwards:

• Typo correction: the baseline stays as it is if it is not above the new value. If it is higher — it was set from the wrong reading — it moves to the new value, so the next threshold counts from the real runtime.
• Meter replacement: the runtime elapsed since the last generation is kept, shifted onto the new counter. A threshold already reached on the old meter but not yet generated is generated in the next round.

What the system records

The correction writes an audit entry: the kind (typo or meter replacement), the old and new value, the reason, and the old and new baseline of each affected task. Apart from the correction, nothing changes: the normal reading still does not accept a lower value.

If you see “The recorded runtime changed in the meantime”

You can only correct the value you saw on screen. If someone recorded a new reading meanwhile, the system does not overwrite it silently — reload the page, check the current value and enter the correction again.